Please sync meson 0.60.1-1 to jammy fixing various FTBFS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
meson (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
TL;DR_ I think our Delta is present in 0.60.1-1 and we should sync it.
--- details ---
I fond an issue with DPDK builds but it might affect potentially many others as well.
Example build fails with:
ar: `x' cannot be used on thin archives.
Seems this behavior is caused by:
https:/
This broke my build but also many others it seems, so it was reverted in 0.60.1
https:/
Right now we have:
meson | 0.60.1-1 | unstable | source, all
meson | 0.57.0+
meson | 0.60.0-1ubuntu1 | jammy-proposed/
So actually we should not even let 0.60.0-1ubuntu1 in if it causes FTFBFSes.
The only Delta we have right now is:
* Cherry-pick patch to prevent lots of GNOME packages from failing to build
That is https:/
Which is fixed by:
https:/
This fix is in 0.60.1 as it is in Debian
$ git show pkg/ubuntu/
from ..interpreterba
$ git show pkg/debian/
from ..interpreterba
And btw 0.60.1 in Debian also has another breaks-gnome fix
https:/
Which is another +1 on syncing 0.60.1 in preference to the current one in -proposed.
tags: | added: needs-sync |
Changed in meson (Ubuntu): | |
status: | New → In Progress |
Changed in meson (Ubuntu): | |
milestone: | none → jammy-updates |
/me not a core dev, so my review is not authoritative, but I agree 0.60.1-1 has the 0.60.0-1ubuntu1 delta and we can safely make 0.60.1-1 a sync, especially given that 0.60.0-1ubuntu1 never migrated.