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/
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
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/