From: John Kehayias <john.kehayias@protonmail.com>
To: guix-devel <guix-devel@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Vivien Kraus <vivien@planete-kraus.eu>,
Kaelyn <kaelyn.alexi@protonmail.com>
Subject: xwayland security updates, to mesa- or core-updates or ?
Date: Fri, 15 Dec 2023 06:21:44 +0000 [thread overview]
Message-ID: <871qbornny.fsf@protonmail.com> (raw)
Hi Guix,
In light of (more) CVEs in xwayland, see
<https://lists.x.org/archives/xorg-announce/2023-December/003435.html>,
with already pending security updates, see
<https://issues.guix.gnu.org/67136>, I would like to prioritize
getting that fixed in master. The tricky thing is that, according to
67136, the xwayland update needs newer xorgproto, which corresponds to
many rebuilds. (The related CVEs in xorg-server have been pushed
already as effectively minor version bumps.)
Where is the most efficient branch for this, that could take these
rebuilds to be merged to master soon (whatever soon is for a scope of
something like 22k affected packages)?
I was thinking to put that update and mesa, since it had a new stable
release after the current one never got updates, on mesa-updates and
merge once builds are done assuming no issues. Again, the potential
sore spot is xorgproto I would say. I could see about any other
pending/urgent related changes, but I'm not aware of any off the top
of my head and want to let this move quickly. I also don't want to
jump the queue sending other branches to rebuild everything again.
I'll test things locally in the meantime, but please chime in. If I
don't hear anything too urgent I'll update the mesa-updates branch to
start builds at least. I've also cc'ed some names I think will be
knowledgeable about some current branches.
And thanks to Kaelyn (also cc'ed) for the pending xwayland patches!
Thanks!
John
next reply other threads:[~2023-12-15 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 6:21 John Kehayias [this message]
2023-12-15 17:25 ` xwayland security updates, to mesa- or core-updates or ? Kaelyn
2023-12-18 6:02 ` John Kehayias
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 21:18 John Kehayias
2023-12-22 7:19 ` Efraim Flashner
2023-12-25 6:44 ` Efraim Flashner
2024-01-04 5:13 ` John Kehayias
2024-01-08 5:43 John Kehayias
2024-01-08 8:32 ` Efraim Flashner
2024-01-08 17:24 ` 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=871qbornny.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.com \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
/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).