all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 64369@debbugs.gnu.org
Subject: bug#64369: Request for merging "mesa-updates" branch
Date: Fri, 30 Jun 2023 15:53:28 +0000	[thread overview]
Message-ID: <87o7kx6j62.fsf@protonmail.com> (raw)

Hello all,

This is a request to merge the recently created "mesa-updates" branch. Currently there are just 2 patches on there, fixing/updating mesa only. The main thing to see is how substitute building goes in case anything breaks, but I'm hoping there isn't anything caused by this update.

I believe the "ruby-team" and "tex-team-next" [1] are ahead in the queue, not sure the timing of where those are. In addition/alternatively, would it make sense to have this branch as a separate build job on Cuirass directly as the "kernel-updates" branch? This would need a build roughly every month or so when mesa puts out a new update, we check for breakages, and then merge to master with substitutes available already.

I wasn't sure if this needs formal blockers in debbugs for the other branch merge requests, let me know!

Thanks,
John

[0] <https://issues.guix.gnu.org/63713>

[1] <https://issues.guix.gnu.org/64324>





             reply	other threads:[~2023-06-30 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 15:53 John Kehayias via Bug reports for GNU Guix [this message]
2023-07-01 10:36 ` [bug#64369] Request for merging "mesa-updates" branch Christopher Baines
2023-07-05 20:04   ` John Kehayias via Guix-patches via
2023-07-20 15:54 ` John Kehayias via Guix-patches via
2023-07-20 16:03   ` Christopher Baines
2023-07-20 16:23     ` John Kehayias via Guix-patches via
2023-07-20 17:04       ` Christopher Baines
2023-07-20 19:24         ` John Kehayias via Guix-patches via
2023-07-24 15:14           ` John Kehayias via Guix-patches via
2023-07-28 15:29             ` John Kehayias via Guix-patches via
2023-07-31 15:24               ` bug#64369: " 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=87o7kx6j62.fsf@protonmail.com \
    --to=bug-guix@gnu.org \
    --cc=64369@debbugs.gnu.org \
    --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.