| 5 May 2026 |
adamcstephens | is the patched version working? | 15:55:35 |
adamcstephens | i'm honestly a bit surprised we are behind on qemu | 15:56:39 |
hexa | https://github.com/lxc/incus/issues/3195 | 15:56:57 |
hexa | disable secureboot on nixos by default? | 15:57:01 |
adamcstephens | there's the secureboot blocker that's handled by the blackbox image server, but it's not setting it off by default. | 15:58:45 |
Tom | i've seen some weirdness with nixpkgs-review where sometimes the incus-lts.client package build failed with errors like the following
@nix { "action": "setPhase", "phase": "installPhase" }
Error:: Failed to load configuration: Unable to decode the configuration: yaml: construct errors:
line 0: yaml: no documents in stream
ERROR: installShellCompletion: installShellCompletion: installed shell completion file `/nix/store/mj80xcnji9x6asr084wm66n08cwg6dwf-incus-lts-client-7.0.0/share/zsh/site-functions/_incus' does not exist or has zero size
But that somehow didn't seem consistent and a nom-build did work. So i guess we'll see if that continues in a relevant way
I've decided myself against the -unstable- approach and instead went with fetchpatches. The benefit is that we can more or less follow the zabbly package for now and then we hopefully don't have to worry about shipping stuff which won't be part of 7.0.1
Otherwise it seems to work as far as i can tell but then i've also only used 7.0.0 so far on an empty test host with a test VM. So no idea what else might be broken
| 16:09:04 |
Tom | there is a draft PR https://github.com/NixOS/nixpkgs/pull/502485 | 16:11:54 |
adamcstephens | odd error. though it makes me realize we're not gating installShellCompletion on stdenv.buildPlatform.canExecute stdenv.hostPlatform | 16:12:43 |
adamcstephens | huh https://github.com/NixOS/nixpkgs/pull/514045 | 16:14:26 |
adamcstephens | i've never looked at the ceph package. is it just me or is this needless complexity? | 16:19:06 |
hexa | Not sure if this is needless, but after seeing the packaging I don't want to use it | 16:38:29 |
Tom | https://github.com/zabbly/incus/commit/8b47b2222b3d5eb4b67417d3586b35ffae630752 🫠| 17:14:03 |
adamcstephens | we use "release" in the loosest of terms i guess | 17:25:32 |
hexa | yay | 17:40:42 |
hexa | the fix for my issue is included | 17:40:50 |
adamcstephens | honestly, this seems to be all the commits since 7.0 except for docs/translations. may be easier to switch back to using an unstable commit | 17:49:13 |
adamcstephens | oh, i guess you added all the patches already... | 17:49:51 |
hexa | https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 | 18:08:18 |
Tom | yeah, would be for now. But i'm just really rather worried to miss the branch off point for 7.0.1 | 18:36:56 |
adamcstephens | i won't miss the tag being created. | 18:53:21 |
adamcstephens | eventually there'll be a release branch for v7, like there is for v6, but i suspect that may not happen until the next "latest" release | 18:53:46 |
| 6 May 2026 |
Tom | https://www.youtube.com/watch?v=Fp0l84fSeP0&t=2067s
probably 6.0.7 rather shortly, 7.1.0 at the end of the month and 7.0.1 probably around that same time | 01:27:01 |
| 7 May 2026 |
adamcstephens | so uhhh... are these security vulnerabilities going to be fixed in v6? | 12:33:14 |
adamcstephens | if i have to DIY patches to an "LTS", I'm inclined to drop supporting it. | 12:34:33 |
Tom | ( https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641/12?u=tomh )
okay i guess that means the incus-lts package on 25.11 will receive a version bump at some point
the remaining question is then what (if anything) we'll do with the incus package on 25.11
a) ignore it
b) mark it vurlnerable
c) backport 7.0
d) combine b) and c) and backport it as incus-lts7 (the primary proplem i have with that is that further 7.0 bumps wouldn't be done via the backport bot) | 21:02:46 |
Tom | uh, wait, we could move pkgs/by-name/in/incus/lts.nix to pkgs/by-name/in/incus/lts6.nix and then add 7.0 to pkgs/by-name/in/incus/lts.nix | 21:08:44 |
adamcstephens | bump latest to 7.0 on 25.11, and leave LTS until if/when upstream patches v6. | 21:14:20 |
adamcstephens | it's not worth adding a third release for the lifetime of 25.11 | 21:15:16 |
adamcstephens | i'd honestly ignore 25.11+latest if it wasn't for the security patches | 21:16:02 |
Tom | yeah, i also noticed i did mess up the filenames up above, i'll do the backport then | 21:16:40 |