| 29 May 2026 |
 Tom | https://github.com/NixOS/nixpkgs/pull/525456 | 07:19:51 |
| Tom | it doesn't look like the security fixes have been pushed to a stable-7.0 branch in the incus Repo or the lts-7.0 branch from the zabbly repo yet | 07:45:38 |
| Tom | https://github.com/NixOS/nixpkgs/pull/525461 | 07:45:50 |
 adamcstephens | of course not | 13:24:34 |
| adamcstephens | at what point do we stop offering LTS at all, if it's not going to get sufficient maintenance upstream? | 13:25:28 |
| Tom | that thought crossed my mind as well | 13:26:06 |
| Tom | or we keep it but permanently mark it as insecure. The handfull version bumps shouldn't be too much work 🙃 | 13:32:42 |
| Tom | * or we keep it but permanently mark it as insecure. The handful version bumps shouldn't be too much work 🙃 | 13:33:16 |
| adamcstephens | if it's permanently marked insecure, then it wouldn't be default and almost nobody would use it. could simplify and just drop | 14:01:02 |
| Tom | Yeah, i was coping by joking | 14:15:18 |
| adamcstephens | ;) | 14:24:09 |
 Cobalt | Given than LTS was promised (although from Incus, not nixpkgs) I would presume any users might find a drop surprising. It might be reasonable in 26.11 with a deprecation warning in 26.05 though, if there is no maintenance being done. | 14:31:02 |
| adamcstephens | yeah, we're committed to 26.05. | 14:32:20 |
| 30 May 2026 |
| Tom | https://discuss.linuxcontainers.org/t/incus-7-1-has-been-released/26750 | 07:33:13 |
| Tom |
if you're running on an LTS, especially if you're running on Debian, the security patches are comming we've been working with the security team as usual, those fixes are going to be coming over the next somewhere between hours and days not sure exactly what that timeline looks like
https://www.youtube.com/watch?v=p4ZxwFSgeJ8&t=1617s
https://salsa.debian.org/go-team/packages/incus/-/commit/acc2df6adf97018df26999195d4067222fdaa498
Seems like they've cherry picked them. The 7.0 Release is only in forky and later. I don't quite get why the patches would land there but not in the zabbly lts-7.0 repo.
| 07:58:03 |
| Tom | In reply to @tom:dragar.de
https://github.com/NixOS/nixpkgs/pull/525461 So let's just go with that as well ...? | 08:00:06 |
| Tom | https://github.com/zabbly/incus/commit/36f215545f705b31d4bbc030ff5b387da5221a25 at last | 19:56:53 |
| Tom | https://github.com/lxc/incus/tree/stable-7.0 | 19:58:00 |
| Tom | not yet updated, but at least there now is a branch | 19:58:29 |
| 2 Jun 2026 |
| adamcstephens | https://github.com/NixOS/nixpkgs/pull/527134 | 13:34:41 |
| adamcstephens | oh yeah, it's a list not a boolean | 13:39:36 |
| 4 Jun 2026 |
|  arias 🏳️⚧️ joined the room. | 21:52:15 |
| 5 Jun 2026 |
| adamcstephens | lxc-ci has failed on 25.11 images the last two nights. it's possible this is due to the brief breakage introduced by marking LTS v6 broken, but I haven't investigated yet | 13:48:42 |
 hexa | > error: hash mismatch importing path '/nix/store/pgq2w002im58rdcm40z3lfknsnl9awbj-linux-6.18.34';
> specified: sha256:1lgb938hbydlmfjmapvaikwvh4jhy560sa994w98faj29fs9yg5r
> got: sha256:174irh15f6b66pj2drzbs0sglxzi5ryp517rvpxjijph2dyxfajh
> error: path '/nix/store/pgq2w002im58rdcm40z3lfknsnl9awbj-linux-6.18.34' is required, but there is no substituter that can build it
> error: some references of path '/nix/store/6sc55qvy6vqynh8b71qf2cjf0z0yhcaw-nixos-system-nixos-lxc-metadata-26.11pre708350.gfedcba' could not be realised
For full logs, run:
nix log /nix/store/0a7kkc4j2f0ccr3dqp9v9nsrsksn49cm-nixos-disk-image.drv
| 14:09:56 |
| hexa | lol wot | 14:10:07 |
| hexa | if anything in incus depends on fuse https://github.com/NixOS/nixpkgs/pull/528369 will be relevant | 14:10:23 |
| adamcstephens | only lxcfs | 14:12:22 |
| adamcstephens | which you already merged | 14:12:40 |
| hexa | if it requires /etc/fuse.conf or fusermount3 then it wants programs.fuse.enable | 14:12:47 |
| adamcstephens | https://github.com/NixOS/nixpkgs/blob/6b316287bae2ee04c9b93c8c858d930fd07d7338/nixos/modules/virtualisation/lxcfs.nix#L44 | 14:14:45 |
