Hi, On Sun, 12 Jul 2026 06:26:33 +0200 Julien Lepiller <[email protected]> wrote:
> How about applying the security fixes on top of 1.5.0, and releasing > that as 1.5.1? This is exactly what me and some other people are trying to do. I'm not alone in that but *it won't happen without more help*. We are trying to add a backport team and split the task in 3: * People that do the 1.5.1 release. Tanguy is part of the release team now and wants to help with that. * People that review patches for the 1.5.1 release. This is the part that is missing here. So far nobody volunteered for that. * People who backport patches. I have backported the fixes on top of 1.5.1 but they have issues. And this is to be expected: the patches got no review at all, only a quick test of the patch set by some Debian contributor(s). I am realist and so far everybody who tried to do all this work alone failed, and this is exactly why Guix was removed from Debian stable: backporting patches is too much work for only 1 person. And this is precisely why me and other people are working on a plan, and trying to gather support for it. There is even a patch set under review just for that here: https://codeberg.org/guix/guix/pulls/11832 And the goal is to only support the latest release which at the time of writing is 1.5.0, and also rely on volunteers to backport patches (so Guix won't commit to backport patches, but anybody would be able to do that and have proper review, and even a release when all security issues or other issues that need to be fixed for downstream are fixed (example: guix-daemon not starting because of AppArmor incompatibilities). Denis.
pgpH5EpfDB45Z.pgp
Description: OpenPGP digital signature
