Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1997067

Summary: Update meson in RHEL 9 to 0.58.2
Product: Red Hat Enterprise Linux 9 Reporter: Kalev Lember <klember>
Component: mesonAssignee: Eduardo Lima (Etrunko) <elima>
Status: CLOSED ERRATA QA Contact: Tomas Pelka <tpelka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: ddepaula, elima, marcandre.lureau, oholy, pbonzini, tpelka, tpopela, wtaymans
Target Milestone: rcKeywords: Rebase, Triaged
Target Release: ---Flags: elima: needinfo-
elima: needinfo-
pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: meson-0.58.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2006519 (view as bug list) Environment:
Last Closed: 2022-05-17 16:06:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2006519, 2018868, 2022729    

Description Kalev Lember 2021-08-24 11:14:32 UTC
Fedora 34 has meson 0.59.1 and we should probably make sure we ship the same version in RHEL 9. More and more upstreams are starting to use newer meson features and it would be a good time to make sure the toolchain is up to date (so that we can easily backport fixes to other packages as needed).

As an example, gnome-autoar backport last week needed newer meson features than what was available in RHEL 9 meson (it currently has 0.56.2) and needed work to get building with the older meson version.

On the desktop side, we keep GNOME packages synced to F34 versions and it would make sense to do the same for meson as well, as this is the tested combination for us.

Comment 1 Tomas Pelka 2021-08-26 12:14:48 UTC
CC-ing Paolo can you see any potential issue(s) within proposed version of meson?

Im a bit hesitant to update crucial component just before ITM26 milestone. On the other hand it may be easy to justify exception/blocker if needed.

Comment 2 Paolo Bonzini 2021-08-31 11:48:02 UTC
No objections. 0.58.2 might also be a good alternative as that's the last 0.58 release and it's rock solid. Either is fine as long as desktop QE accepts it, since virt packages should be okay with both. We would certainly like to have 0.57 or newer, as that will become a requirement for QEMU 6.2.

Comment 4 Tomas Popela 2021-09-02 07:32:50 UTC
In the end we have come in the conclusion on our SST meeting that it's rather risky to do this at this point. It might be done in the future when there will be a consent from the subsystems involved in meson-maint@.

Comment 5 Paolo Bonzini 2021-09-07 12:39:31 UTC
> In the end we have come in the conclusion on our SST meeting that it's rather risky
> to do this at this point. It might be done in the future when there will be a consent
> from the subsystems involved in meson-maint@.

Danilo, QEMU 6.2 will most likely require 0.57 and IIUC it will be in RHEL9.  Am I correct,
and if so should we prepare for that by upgrading Meson now to 0.58.2?

Comment 6 Paolo Bonzini 2021-09-07 12:40:54 UTC
(Note I am proposing 0.58.2 because it's what QEMU will ship, and I already know of one minor regression in 0.59.x - https://github.com/mesonbuild/meson/pull/9230 - no effect on compiled products, just uglier logs, so 0.59.1 would be okay too).

Comment 7 Kalev Lember 2021-09-08 17:39:35 UTC
+1 from me from the desktop side to update meson to 0.58.2. This is the version we had in F34 build roots for a long time and it was rock solid for building GNOME.

Comment 8 Danilo de Paula 2021-09-21 18:36:52 UTC
(In reply to Paolo Bonzini from comment #5)
> > In the end we have come in the conclusion on our SST meeting that it's rather risky
> > to do this at this point. It might be done in the future when there will be a consent
> > from the subsystems involved in meson-maint@.
> 
> Danilo, QEMU 6.2 will most likely require 0.57 and IIUC it will be in RHEL9.
> Am I correct,
> and if so should we prepare for that by upgrading Meson now to 0.58.2?


Someone pointed out that 0.58.2 is being used by Fedora for a while, right?
Probably that's a better target.

I will bring this to the team.

Comment 9 Danilo de Paula 2021-09-21 18:43:02 UTC
Assigning to Eduardo.

I will run RHEL-8.6 later on (as if it's a requirement for qemu, rhel-8 and 9 should get it)

Comment 10 Eduardo Lima (Etrunko) 2021-09-21 18:44:51 UTC
(In reply to Kalev Lember from comment #7)
> +1 from me from the desktop side to update meson to 0.58.2. This is the
> version we had in F34 build roots for a long time and it was rock solid for
> building GNOME.

F34 has updated to 0.59.1 already, may be better to update to this version then? Paolo, does it impact qemu in some way?

Comment 11 Danilo de Paula 2021-09-21 18:46:29 UTC
@klember is this an ACK from the desktop team to RHEL-8 as well?

Comment 12 Danilo de Paula 2021-09-21 18:46:51 UTC
@klember is this an ACK from the desktop team to RHEL-8 as well?

bz#2006519

Comment 13 Kalev Lember 2021-09-21 18:55:40 UTC
(In reply to Danilo Cesar Lemes de Paula from comment #12)
> @klember is this an ACK from the desktop team to RHEL-8 as well?

Sorry, I can't speak for the desktop team here. I am personally fine with updating it in RHEL 8 as well though.

Comment 14 Eduardo Lima (Etrunko) 2021-09-21 19:01:04 UTC
Merge request

https://gitlab.com/redhat/centos-stream/rpms/meson/-/merge_requests/2

Comment 17 Paolo Bonzini 2021-09-21 20:51:16 UTC
I would be slightly wary of updating to 0.59.1 since a 0.59.2 is planned already at roughly the same time as 0.60.0 (meaning there are probably some known bugs, though none that I know affects QEMU).

Comment 18 Eduardo Lima (Etrunko) 2021-09-22 00:49:05 UTC
(In reply to Paolo Bonzini from comment #17)
> I would be slightly wary of updating to 0.59.1 since a 0.59.2 is planned
> already at roughly the same time as 0.60.0 (meaning there are probably some
> known bugs, though none that I know affects QEMU).

I haven't been following the Meson releases so close, so I agree it is probably better to play it safe here and stay with 0.58 then.

Comment 21 Tomas Pelka 2021-11-01 07:26:20 UTC
*** Bug 2018875 has been marked as a duplicate of this bug. ***

Comment 30 errata-xmlrpc 2022-05-17 16:06:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: meson), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4299