Bug 2208890 - [rebase] rebase meson to at least 0.60 for mesa 23.1 for RHEL8.9
Summary: [rebase] rebase meson to at least 0.60 for mesa 23.1 for RHEL8.9
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: meson
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: meson-maint
QA Contact: Tomas Pelka
URL:
Whiteboard:
Depends On:
Blocks: 2160691
TreeView+ depends on / blocked
 
Reported: 2023-05-21 23:07 UTC by Dave Airlie
Modified: 2023-05-23 04:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-23 04:06:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-157789 0 None None None 2023-05-21 23:09:05 UTC

Description Dave Airlie 2023-05-21 23:07:54 UTC
mesa 23.1 requires meson 0.60 to be built.

Comment 1 Dave Airlie 2023-05-22 01:50:36 UTC
From my quick look, rebasing to 0.61.4 is probably the lowest friction point, without python versions getting problematic.

Comment 2 Tomas Popela 2023-05-22 08:51:42 UTC
As I've mentioned on the Slack it's not trivial at all to rebase Meson - actually it's trivial if one doesn't care about the packages that are using Meson - see how it went in RHEL 9 where we've rebased Meson and we already had to fix 4 additional packages so they don't start to fail to build from source after the rebase - https://bugzilla.redhat.com/show_bug.cgi?id=2022729#c8 and https://bugzilla.redhat.com/show_bug.cgi?id=2022729#c10. And I'm more worried how the situation will look like with even older packages that we have in RHEL 8. I'm tempted to decline this request, but let's see whether Dave will find a way around this.

Comment 3 Dave Airlie 2023-05-23 04:06:25 UTC
I've given up on this plan, I included a version of meson into the mesa build to get around it.


Note You need to log in before you can comment on or make changes to this bug.