all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 74780@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#74780] Request for merging "mesa-updates" branch
Date: Sat, 04 Jan 2025 18:38:25 +0100	[thread overview]
Message-ID: <87ed1iqy26.fsf@gnu.org> (raw)
In-Reply-To: <87y0zrdtwq.fsf@protonmail.com> (John Kehayias's message of "Sat,  04 Jan 2025 05:34:17 +0000")

Hi John,

John Kehayias <john.kehayias@protonmail.com> skribis:

> QA page still hasn't updated and it has been another 5 days from the
> last message. Unless there are any objections I'll do a rebase and
> merge later this weekend.

Sure.  Please do check the situation at
<https://ci.guix.gnu.org/jobset/mesa-updates> and how it compares to
‘master’.

You can check that direct dependents of packages that were upgraded
still build fine.  For example, “guix build -P1 mesa --no-grafts -n -v1”
will indicate whether substitutes are available for all of the direct
dependents of ‘mesa’, meaning that they were successfully built.

Thanks for working on this!

Ludo’.




  reply	other threads:[~2025-01-04 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  6:30 [bug#74780] Request for merging "mesa-updates" branch John Kehayias via Guix-patches via
2024-12-20 20:31 ` John Kehayias via Guix-patches via
2024-12-21 16:32   ` Efraim Flashner
2024-12-22  9:19   ` Efraim Flashner
2024-12-29 14:57     ` Ludovic Courtès
2024-12-30  2:46       ` John Kehayias via Guix-patches via
2025-01-04  5:34       ` John Kehayias via Guix-patches via
2025-01-04 17:38         ` Ludovic Courtès [this message]
2025-01-06  2:11           ` bug#74780: " 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=87ed1iqy26.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=74780@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=john.kehayias@protonmail.com \
    /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.