Bug 2228873

Summary:	Request for updating meson to 1.2.0 for f37 and f38
Product:	[Fedora] Fedora	Reporter:	Rudolf Kastl <che666>
Component:	meson	Assignee:	Kalev Lember <klember>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	asahi-sig, carl, davide, igor.raits, klember, wtaymans
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	meson-1.2.1-1.fc38	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-13 02:35:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rudolf Kastl 2023-08-03 13:48:37 UTC

Description of problem:
Is it possible to update f37 and f38 with meson-1.2.0 as this is a hard requirements for building rustcl with mesa git?

Version-Release number of selected component (if applicable):
current release in f37/f38


Reproducible: Always

Steps to Reproduce:
Steps to Reproduce:
1. checkout mesa git
2. enable rustcl
3. watch build fail on meson 1.2.0 dependency for rustcl

Actual Results:  
Actual results:
dependency check on building fails

Expected Results:  
Expected results:
depending check on building succeeds with meson 1.2.0


Additional info:
This is a requirement for building mesa git with rustcl for https://copr.fedorainfracloud.org/coprs/che/mesa/

Comment 1 Kalev Lember 2023-08-03 14:01:42 UTC

I'd like to be a bit careful here because I've seen several GNOME modules FTBFS with new meson 1.2.0. I am sure most of them get fixed upstream soon, but I think it's best to not rush this to avoid FTBFS issues in stable Fedora branches.

What about a plan that goes something like this:

1) For now, you can take meson 1.2.0 rawhide srpm and build it in your copr.
2) We'll give a month or so for all the upstreams to get meson 1.2.0 compatibility fixes done, and that also gives us time to see if anything major comes up in rawhide
3) Once meson 1.2.1 is released, we build it for both F38 and rawhide (hopefully enough time has passed then so that packages that FTBFS with meson 1.2.0 have fixes at least upstream, if not backported to Fedora yet)
4) F37 stays with older meson

Comment 2 Carl George 🤠 2023-08-12 23:53:32 UTC

An update, meson 1.2.1 has been built and published for F39 and Rawhide.  As far as F38, I spoke with Kalev and a few others about this in Matrix today.  He has built meson 1.2.1 in Copr for F38 for anyone that wants to try it out [0].  He said he plans to do the update in F38 proper after some additional testing.  Since he's working on this I'm going to assign the bug to him.

[0] https://copr.fedorainfracloud.org/coprs/kalev/meson1.2/build/6269185/

Comment 3 Fedora Update System 2023-08-23 21:43:54 UTC

FEDORA-2023-7f02c9b967 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7f02c9b967

Comment 4 Fedora Update System 2023-08-24 01:38:18 UTC

FEDORA-2023-7f02c9b967 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7f02c9b967`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7f02c9b967

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-09-13 02:35:49 UTC

FEDORA-2023-7f02c9b967 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.