From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>,
guix-devel@gnu.org,
"66964@debbugs.gnu.org" <66964@debbugs.gnu.org>
Subject: Re: bug#66964: Request for merging "mesa-updates" branch
Date: Sat, 09 Dec 2023 19:28:46 +0000 [thread overview]
Message-ID: <BHpzRQHJypx3wH0EYnyZTz4bhzimiXCUrKYiusTC8NG_aIUCg24L9CchkJgWusBFVwE1h83k6lpqSEMVJdXW_NqyMxxB1yP6SLcIZLpPsA8=@protonmail.com> (raw)
In-Reply-To: <7k1WKdjeNkQdy2Sn-n5KIRtaueKF5rV_eePjWm6w9cp5wSdgaTiv-siJxwNeX12FUywY_ezumz-LeYDMKR_bBbdFn2YrD-e3-IvyvneN15E=@protonmail.com>
Hi,
On Tuesday, November 14th, 2023 at 12:36 PM, Kaelyn <kaelyn.alexi@protonmail.com> wrote:
>
> Hi John,
>
> On Tuesday, November 14th, 2023 at 12:11 PM, John Kehayias john.kehayias@protonmail.com 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.
> >
> > Thanks!
> > John
>
>
> No worries! I realize I was a little late to the party for the mesa-updates branch (had some ongoing technical issues), so if core-updates is still early enough in the process I think it would be good to push the changes to that branch. The current xwayland is pretty old, and the updated version has quite a few CVEs fixed in comparison (just https://www.phoronix.com/news/X.Org-Halloween-Bugs-2023 and https://www.phoronix.com/news/X.Org-Server-Holiday-2022 list 8 CVEs fixed between xwayland 21.1.3 and 23.2.2).
I forgot to sent an email when I did this, but a few weeks ago I updated the xorgproto/xwayland update ticket (#66964) to refer to core-updates instead of mesa-updates and sent in a v2 of the patches rebased against core-updates.
Cheers,
Kaelyn
next prev parent reply other threads:[~2023-12-09 19:29 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 [this message]
2023-11-15 6:28 ` Efraim Flashner
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='BHpzRQHJypx3wH0EYnyZTz4bhzimiXCUrKYiusTC8NG_aIUCg24L9CchkJgWusBFVwE1h83k6lpqSEMVJdXW_NqyMxxB1yP6SLcIZLpPsA8=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=66964@debbugs.gnu.org \
--cc=guix-devel@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 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).