Backport packages for 24.04.2 HWE stack

[Timo Aaltonen]

[Impact]
The graphics HWE stack from oracular needs to be backported for 24.04.2

libdrm
- build-dep of mesa

spirv-llvm-translator
- build-dep of llvm

llvm-toolchain-19
- new source in noble
- build-dep of mesa
- required for new AMD platforms
- needs two uploads:
  * 1st stage bootstrap build
  * 2nd stage after spirv-llvm-translator has built against 1st stage

mesa
- new major release (24.2.x)
- new HW support, Lunar Lake, Battlemage..

meson-1.5
- needed by mesa
- Conflicts/Replaces meson, because otherwise all of the python lib should be
  renamed, along with the includes etc so it's not a trivial amount of work
- tests disabled because four irrelevant ones fail for some reason, doesn't
  affect the mesa backport

[Test case]
We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point.
- AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
- Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2)

Install the new packages and run some tests:
- check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe
- run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition)
- run some games from Steam if possible

and in each case check that there is no gfx corruption happening or worse.

Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI.

[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with noble, we'd already know if there are serious issues.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted libdrm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.122-1~ubuntu0.24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted libdrm (2.4.122-1~ubuntu0.24.04.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libcamera/unknown (ppc64el)
weston/unknown (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#libdrm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-19 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-19/1:19.1.1-1ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Chris Halse Rogers (raof)]

Re: meson-1.5 - is there a reason that it Conflicts/Replaces meson? Or, more specifically: how much effort would it be to make it provide a meson-1.5 binary (and associated files, I guess?) and for Mesa to use that?

Alternatively, I'd *also* feel better about it if we didn't disable the tests because of failures. The current state seems like meson-1.5 would be an attractive nuisance?

[Chris Halse Rogers (raof)]

To be clear: “It actually would be quite a lot of effort” is an acceptable answer; I just want to know that it's been considered.

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted meson-1.5 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/meson-1.5/1.5.1-2ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

I've added a comment about meson conflicts.

thanks!