From: Josselin Poiret <dev@jpoiret.xyz>
To: guix-devel@gnu.org
Subject: Core-updates coordination and plans
Date: Wed, 31 Jan 2024 17:44:21 +0100 [thread overview]
Message-ID: <87h6itzc4a.fsf@jpoiret.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hi everyone,
Since we're a couple people working on core-updates at the same time, it
might be a good idea to coordinate a bit (of course, other volunteers
welcome :) ).
One conundrum we have for now: glibc 2.38 has a couple of new CVEs, and
we have three options:
1) change glibc to track the 2.38 release branch → world rebuild.
2) graft glibc → bad user experience (and we're not supposed to graft
outside of master).
3) switch to 2.39 → world rebuild + possibly more work fixing new build
failures.
glibc 2.39 should hopefully release tomorrow (01/02/2024)
What is everyone's opinion regarding those?
IMO, option 2 is the one I'd like to avoid, and between 1 and 3 I'd
ideally prefer 3 but we don't know yet if there is going to be a lot of
breakage because of that (feels like usually it's toolchain updates, not
glibc updates that cause them the most).
Also, I see that most of the patches that were requested to be merged
into c-u (like the big pages for jemalloc) actually got pushed, are
there any other (well-tested) ones we can go for at the same time as the
glibc rebuild? I will stress that this is about *core* packages now,
I feel that it's too late to introduce more complications and delay the
update any longer.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next reply other threads:[~2024-01-31 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 16:44 Josselin Poiret [this message]
2024-01-31 18:19 ` Core-updates coordination and plans Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 21:59 ` Vivien Kraus
2024-01-31 23:28 ` Eudev in gnome-team [Was: Core-updates coordination and plans] Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 20:18 ` Core-updates coordination and plans Andreas Enge
2024-02-26 15:26 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-27 16:26 ` Andreas Enge
2024-02-27 17:49 ` Vagrant Cascadian
2024-02-27 20:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 22:01 ` Vagrant Cascadian
2024-02-01 17:53 ` Vivien Kraus
2024-02-18 13:51 ` Josselin Poiret
2024-02-24 16:11 ` Ludovic Courtès
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=87h6itzc4a.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
/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.