From: Efraim Flashner <efraim@flashner.co.il>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org,
"66964@debbugs.gnu.org" <66964@debbugs.gnu.org>,
Kaelyn <kaelyn.alexi@protonmail.com>
Subject: [bug#66964] Request for merging "mesa-updates" branch
Date: Wed, 15 Nov 2023 08:28:56 +0200 [thread overview]
Message-ID: <ZVRlKCMfEJNxwkiZ@3900XT> (raw)
Message-ID: <20231115062856.SKJnzjD7G9V2WsvsPtvwNX6Lq56qrLJOMGgq763hGJA@z> (raw)
In-Reply-To: <87y1f0t7s9.fsf_-_@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
On Tue, Nov 14, 2023 at 08:11:08PM +0000, John Kehayias wrote:
> Hi Kaelyn,
>
> On Sun, Nov 12, 2023 at 08:01 PM, Kaelyn wrote:
>
> > Hi,
> >
> > I've just submitted a pair of patches for the mesa-updates branch:
> > <https://issues.guix.gnu.org/67136> updating xorgproto and
> > xorg-server-xwayland. The xorgproto is a high-impact update (guix
> > refresh reports rebuilding 8710 packages would ensure 22871 dependent
> > packages are rebuilt), but required to update to the latest xwayland
> > as xwayland requires a newer version of presentproto than in the
> > current guix xorgproto package. The updating and ungrafting of mesa
> > and a number of X.org related libraries seemed like a good time (and
> > place) to update xorgproto as well.
> >
> > Cheers,
> > Kaelyn
>
> Thanks for the patches. I think mesa-updates in this current iteration
> is set on builds (ended up being a lot more due to the ungrafting but
> seems done on our main architectures for several days now). I had to
> make some other changes to fix some larger breakages but at this point I
> think it will just be taking us back in the build queue too much.
>
> So I think it would make more sense on the next big rebuild, either
> core-updates (talk about doing that with more ungrafts right now) or
> I'll do mesa-updates again when the next release of mesa hits. Or maybe
> it makes sense to just do another branch for xwayland?
>
> Open to ideas! I'll send a separate message soon on the status of
> mesa-updates and see what people think, but my thought was to merge this
> to master in the next day or so if there are no objections.
If the mesa branch is ready to merge so soon then I think we should just
get that merged and then I'll rebase the rust-team branch on top of new
master. The rust-team branch is also ready to merge, but we're way
behind on aarch64 substitutes. Either way the substitute servers will
be rebuilding all of rust so I think it'd be better to merge in
mesa-updates and then do rust.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-15 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 4:49 mesa-updates: call for patches John Kehayias
2023-11-12 20:01 ` [bug#66964] " Kaelyn via Guix-patches via
2023-11-14 20:11 ` bug#66964: Request for merging "mesa-updates" branch John Kehayias
2023-11-14 20:36 ` Kaelyn
2023-12-09 19:28 ` Kaelyn
2023-11-15 6:28 ` Efraim Flashner [this message]
2023-11-15 6:28 ` [bug#66964] " Efraim Flashner
2023-11-28 5:29 ` bug#66964: " John Kehayias
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVRlKCMfEJNxwkiZ@3900XT \
--to=efraim@flashner.co.il \
--cc=66964@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=kaelyn.alexi@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).