On Sun, 04 Oct 2026 21:44:00 +0200
"Tanguy Le Carrour" <[email protected]> wrote:
> I contacted the release team working on the next release. Actually, I
> **joined** the team! 😅
> 
> I’ll be pushing the idea of having a 1.5.1 and keep you posted…
Thanks a lot.

On Sun, 04 Oct 2026 15:23:18 -0700
Vagrant Cascadian <[email protected]> wrote:

> > I contacted the release team working on the next release. Actually,
> > I **joined** the team! 😅
> >
> > I’ll be pushing the idea of having a 1.5.1 and keep you posted…
> 
> At this point, getting a 1.5.1 would be nice, but it might also be
> worth aiming for some git snapshots as 1.6.0 is targeted for
> december,

The problem I have here is that 1.6.0 will not ship with security
vulnerabilities (which is obviously a good thing), so if we wait for
1.6.0, then there will probably be much less interest in having a
process to backport security fixes in Guix, and we would
have nothing real to test the process with, so communication would be
harder in Guix (how can people commit to something they can't see), we
won't be able to tune the process along the way, and finally
distributions will not be able to see it working for real to draw
conclusions (how to know what you can really rely on if you can not
observe it).

> Or we can work on 1.5.x in unstable, and 1.6.x snapshots in
> experimental for the time being...
> 
> I think the problem I had getting 1.5.0 ready was maybe issues with
> apparmor profiles blocking guix-daemon from starting...

I fixed that in the Parabola and Trisquel packages. The most
interesting one is Trisquel, as it is based on Ubuntu, which made
Apparmor stricter on some areas.

The patches for that are in the ecne branch in
https://gitlab.trisquel.org/trisquel/package-helpers.git/ in
helpers/DATA/guix/apparmor.

A valid question here would be if these are fit for backporting. I
personally think they would because the Guix daemon doesn't even start
without these, but if I sent these, I would not be the one making that
judgment (it would be the reviewers and/or people who can push and make
releases).

I think we should also test that if we manage to make a 1.5.1.

Denis.

Attachment: pgpwhDv1oPBXX.pgp
Description: OpenPGP digital signature

Reply via email to