From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
guix-maintainers@gnu.org, Julien Lepiller <julien@lepiller.eu>,
Marius Bakke <marius@gnu.org>
Subject: Re: Planning for a release, for real
Date: Fri, 7 Oct 2022 11:53:32 +0200 [thread overview]
Message-ID: <bf439ee2-bb06-ef66-e7eb-a72999ebecde@telenet.be> (raw)
In-Reply-To: <87a668c68f.fsf@gnu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1115 bytes --]
On 07-10-2022 11:50, Ludovic Courtès wrote:
> Hi,
>
> Maxime Devos <maximedevos@telenet.be> skribis:
>
>> I have some unapplied security patches (from before the latest release
>> (1.3.0) (!)) (more precisely, some patches that prepare for actually
>> being able to write the security patches, once the preparation patches
>> are merged, the actual security fixes should be relatively simple); I
>> think it would be rather bad for known security fixes to not be
>> applied for a whole release, especially given how long release cycles
>> are in Guix.
>
> Could you provide links to these?
'These' are the ‘openat’ patches:
> If they depend on ‘openat’ in Guile, that won’t be an option
> unfortunately since we’re not going to upgrade the ‘guile’ package
> during that time frame.
However, upgrading the Guile package is not required, I proposed making
a separate ‘guile-with-openat’ package (= current Guile + some patches),
which can then be used by the service code:
<https://issues.guix.gnu.org/54485> (without world rebuilds).
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-07 9:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07 9:49 ` Ludovic Courtès
2022-10-07 10:14 ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07 9:50 ` Ludovic Courtès
2022-10-07 9:53 ` Maxime Devos [this message]
2022-10-07 6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02 ` Ludovic Courtès
2022-10-10 7:57 ` Csepp
2022-10-12 20:40 ` Vagrant Cascadian
2022-10-13 15:06 ` Ludovic Courtès
2022-10-07 8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09 ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33 ` Efraim Flashner
2022-10-13 15:42 ` Christopher Baines
2022-10-20 13:49 ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07 ` Efraim Flashner
2022-10-21 8:51 ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42 ` Efraim Flashner
2022-10-22 20:22 ` Efraim Flashner
2022-10-26 9:01 ` Efraim Flashner
[not found] ` <87h6zyo811.fsf@gnu.org>
2022-10-21 8:43 ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21 9:30 ` Mathieu Othacehe
2022-10-31 17:40 ` Tobias Platen
2022-10-22 12:18 ` Release progress, week 2 Christopher Baines
2022-10-25 9:50 ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29 ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines
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=bf439ee2-bb06-ef66-e7eb-a72999ebecde@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=julien@lepiller.eu \
--cc=ludo@gnu.org \
--cc=marius@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 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).