all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias <kehayias@sas.upenn.edu>
To: 67876@debbugs.gnu.org
Subject: [bug#67876] request for merging mesa-updates
Date: Sun, 17 Dec 2023 23:50:20 -0500	[thread overview]
Message-ID: <87y1dsqfbr.fsf@sas.upenn.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

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!

             reply	other threads:[~2023-12-18 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18  4:50 John Kehayias [this message]
2024-01-08 19:44 ` bug#67876: request for merging mesa-updates John Kehayias via Guix-patches via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1dsqfbr.fsf@sas.upenn.edu \
    --to=kehayias@sas.upenn.edu \
    --cc=67876@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.