!VhzbGHamdfMiGxpXyg:robins.wtf

NixOS Incus and LXC

51 Members
lxc, lxd, incus discussions related to NixOS19 Servers

Load older messages


SenderMessageTime
9 Mar 2026
@adam:robins.wtfadamcstephensi guess it kinda makes sense to keep them in sync, so have github be the source of truth, since it's a pingable alias too14:16:43
@adam:robins.wtfadamcstephens mkg20001 and aanderse are y'all still using any of the LXC/incus stack? you've been disengaged from this maintenance and we're looking at team membership so i'm inclined to remove you both. 14:17:41
@adam:robins.wtfadamcstephens Tom: i'm good with moving to a github synced team 14:18:06
@adam:robins.wtfadamcstephensi just removed jnsgruk from the github lxc team14:20:51
@mkg20001:mkg20001.iomkg20001Im still using incus, but not really maintaining it14:32:45
@adam:robins.wtfadamcstephensok, if you don't mind we'll remove you from the team14:34:28
@mkg20001:mkg20001.iomkg20001Ok14:35:11
@adam:robins.wtfadamcstephensyou're always welcome back. but it's helpful to keep the team with the active list :)14:35:42
@aanderse:nixos.devaanderse

@adam:robins.wtf: definitely still a big user of lxd but of course as you said not maintaining

the issue is... i really appreciate getting email about all the PRs ... i wish there was a way to subscribe!

15:00:18
@hexa:lossy.networkhexaas a maintainer you get requested for reviews and that should result in an email19:25:49
@hexa:lossy.networkhexamaybe you are ignoring nixpkgs notifications on github?19:26:20
@tom:dragar.deTomi think the emails are sent and received just fine but there is currently just no desire to do maintainer stuff19:35:44
@adam:robins.wtfadamcstephensthat's how i read it too.22:12:05
@adam:robins.wtfadamcstephenswe don't really have any tooling for following specific package events in the ecosystem.22:13:01
@adam:robins.wtfadamcstephensi've worked around it some by using the github commit atom feeds, which you can use on a file in the repo22:13:55
@hexa:lossy.networkhexathe closest thing would be to subscribe to upstream releases then?23:37:41
@hexa:lossy.networkhexaI think you track them quite closely23:37:52
10 Mar 2026
@tom:dragar.deTom Well, to be fair: even upstream struggles keeping pace with the speed by which @adam:robins.wtf opens PRs 😂 🙃 00:13:07
@adam:robins.wtfadamcstephensatom feeds are nice :)02:47:24
@adam:robins.wtfadamcstephensi use miniflux to track releases, and of course other things02:47:49
13 Mar 2026
@hexa:lossy.networkhexaany reason why startsWhenNeeded is enabled on openssh in lxc common?16:28:01
@hexa:lossy.networkhexathat implies socket activation, which uses sshd@ units with instance names containing src/dst address16:28:23
@hexa:lossy.networkhexawhich again land in prometheus :D16:28:31
@adam:robins.wtfadamcstephenspretty sure that's a hold over from before i even started with nixos. there's probably a small argument that it's saving memory, but maybe not worth it17:23:15
14 Mar 2026
@kaledriina:matrix.orgMilja K joined the room.11:10:56
15 Mar 2026
@jykrwn_bot:matrix.org@jykrwn_bot:matrix.org joined the room.01:23:27
@mjolnir:nixos.orgNixOS Moderation Bot banned @jykrwn_bot:matrix.org@jykrwn_bot:matrix.org (disagreement).20:28:00
20 Mar 2026
@hexa:lossy.networkhexathe newest fun time I have is when the ext4 filesystem of a guest gets corrupted during online migration with zfs send, when the host is busy with i/o16:41:46
@hexa:lossy.networkhexain our cast mostly gitlab runner16:41:52
@hexa:lossy.networkhexae.g. when building nix things16:42:08

Show newer messages


Back to Room ListRoom Version: 10