all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
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, 07 Oct 2022 11:50:40 +0200	[thread overview]
Message-ID: <87a668c68f.fsf@gnu.org> (raw)
In-Reply-To: <08897a91-5865-7a4c-6967-4c912c8692f3@telenet.be> (Maxime Devos's message of "Thu, 6 Oct 2022 18:07:34 +0200")

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?

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.

Thanks,
Ludo’.


  reply	other threads:[~2022-10-07  9:52 UTC|newest]

Thread overview: 50+ 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 [this message]
2022-10-07  9:53     ` Maxime Devos
2022-10-07  6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02   ` Ludovic Courtès
2022-10-07 14:24   ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55     ` pelzflorian (Florian Pelz)
2022-10-08 15:33     ` jbranso--- via Guix-patches via
2022-10-10 10:07       ` pelzflorian (Florian Pelz)
2022-10-14 15:12         ` Ludovic Courtès
2022-10-14 15:47           ` kiasoc5 via Guix-patches via
2022-10-15  9:47             ` pelzflorian (Florian Pelz)
2022-10-16 11:53               ` pelzflorian (Florian Pelz)
2022-10-14 17:09           ` pelzflorian (Florian Pelz)
2022-10-15 15:51             ` pelzflorian (Florian Pelz)
2022-10-17 16:35             ` Ludovic Courtès
2022-10-14 19:28           ` jbranso--- via Guix-patches via
2022-11-03 19:21           ` Ludovic Courtès
2022-11-16  0:22     ` pelzflorian (Florian Pelz)
2022-11-16 23:16       ` jbranso--- via Guix-patches via
2022-11-17 16:26         ` pelzflorian (Florian Pelz)
2022-11-19 14:06           ` Joshua Branson via Guix-patches via
2022-12-08 17:02             ` pelzflorian (Florian Pelz)
2023-03-09 21:06       ` pelzflorian (Florian Pelz)
2023-08-20 17:44         ` pelzflorian (Florian Pelz)
2022-10-10  7:57   ` Supported architectures 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a668c68f.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=marius@gnu.org \
    --cc=maximedevos@telenet.be \
    /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.