request for merging mesa-updates

  • Done
  • quality assurance status badge
Details
2 participants
  • John Kehayias
  • John Kehayias
Owner
unassigned
Submitted by
John Kehayias
Severity
normal
J
J
John Kehayias wrote on 18 Dec 2023 05:50
(name . guix-patches@gnu.org)(address . guix-patches@gnu.org)
87y1dsqfbr.fsf@sas.upenn.edu
As mentioned on guix-devel, https://lists.gnu.org/r/guix-devel/2023-12/msg00158.html, this is a hopefully quick branch to update mesa (new stable release as current one we have ended up without updates) and get security updates for xorg-server-xwayland, via https://issues.guix.gnu.org/67136 .

That requires a newer xorgproto which rebuilds (most of) the world. As with libx11 ungrafting, this is due mostly to python as far as I can tell, via the tk dependency. Unfortunately, it seems that can't be easily separated out: https://lists.gnu.org/r/guix-devel/2023-12/msg00165.html

Anyway, there are currently those 3 commits (mesa, xorgproto, xorg-server-xwayland) building away. I'm seeing lots of builds "failing" with "missing derivation" which I've been manually restarting. The biggest real failure I've spotted just clicking around on Cuirass is gtk on i686-linux. A test fails and I have no idea why and don't see how to disable just that test so far. I tried to see about updating glib and gtk from the gnome branch to see if that fixes it, but it required too much local building so far. So, that is one to keep an eye out. At least the dependencies number around 100.

Still waiting to hear from other people about current branches for what the order will be in merging, but figured I'd get things building either way with the CI looking idle.

Thanks!
J
J
John Kehayias wrote on 8 Jan 20:44 +0100
(address . 67876-done@debbugs.gnu.org)
87il431ug6.fsf@protonmail.com
Duplicate and now mesa-updates merged in
7a7c8920aeddaf9ab8d68c572780bc34b404711b
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 67876@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 67876
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch