Created attachment 929407 [details] build.log in commit https://gitweb.gentoo.org/repo/gentoo.git/commit/media-libs/mesa?id=f1206930924e2ea24120f5b2ac20dee013ad70bf you remove all the xa related options but at the end you add "-Dgallium-xa=disabled" with gallium-xa is no longer available in mesa, this leads to a failed build. I think you accidentally added that part I've attached build log and environment
Created attachment 929408 [details] environment
A bug in the live ebuild cannot be critical. Anyway, thanks.
I swear... > $ git show --format="%ci %ct %s" 3be2c47db23 | head -1 > 2025-05-23 12:46:23 -0400 1748018783 delete the XA frontend > $ git show --format="%ci %ct %s" f1206930924e | head -1 > 2025-05-23 13:41:45 -0400 1748022105 media-libs/mesa: Remove IUSE=xa > $ echo $((1748022105-1748018783)) > 3322 I pushed f1206930924e 55 minutes after the upstream commit was made. But this doesn't even account for the time it takes the upstream CI to test the commit before pushing to main, which takes at least 45 minutes. I definitely pushed my commit within 10 minutes of the upstream change. (If someone knows how to tell what time the actual `git push`es happened, let me know) But: > Reported: 2025-05-23 23:07 EDT by Jerome C This is nearly 10 hours after my commit to gentoo.git. I welcome anyone to report issues, but seriously, can you at least use an up-to-date gentoo.git if you're going to file bugs about live ebuilds?
(In reply to Matt Turner from comment #3) > (If someone knows how to tell what time the actual `git push`es happened, > let me know) Figured it out. It's a user preference in Gitlab. With that, I see: > Marge Bot merged May 23, 2025, 1:40 PM So I pushed the update to the live ebuild within 2 minutes.
The issue is present in the GitHub mirror, though: https://github.com/gentoo/gentoo/blob/master/media-libs/mesa/mesa-9999.ebuild#L416 Since gallium-xa is no longer a Meson build option, it's going to trigger that error. Now, maybe GitHub has the wrong ebuild or maybe our Meson is somehow misconfigured to treat this as a major issue but I did a quick search on my system and I see nothing obvious that would have put Meson into a particularly pedantic mode (doesn't mean it's not there).
*** Bug 956557 has been marked as a duplicate of this bug. ***
Please reopen this bug here or remove the failing line. See also https://bugs.gentoo.org/956557
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eac5bd22ee3d43828bdc0c2647cced604ec0419e commit eac5bd22ee3d43828bdc0c2647cced604ec0419e Author: Sam James <sam@gentoo.org> AuthorDate: 2025-05-24 16:13:17 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-05-24 16:13:17 +0000 media-libs/mesa: drop obsolete gallium-xa setting from live We can't disable it if it's gone. Closes: https://bugs.gentoo.org/956508 Signed-off-by: Sam James <sam@gentoo.org> media-libs/mesa/mesa-9999.ebuild | 1 - 1 file changed, 1 deletion(-)
Oh shit, I'm sorry. I intended to completely delete the `-Dgallium-xa=...` line. That's entirely my fault.
