<andi-> Deployed a system with the v245 PR (rebased to master) and so far it hasn't exploded in ~3h :)
<flokli> heh
<flokli> my laptop runs that systemd also - dogfooding as its best
<NinjaTrappeur> ooouh :)
<NinjaTrappeur> flokli++ andi-++
<{^_^}> andi-'s karma got increased to 29, flokli's karma got increased to 27
<NinjaTrappeur> Can't wait to use homed + the luks storage!!
<NinjaTrappeur> Did you try homed, will it need further adjustments?
<NinjaTrappeur> Will bump my system tonight after $work
<andi-> NinjaTrappeur: good point, we can probably also change the systemd-networkd restart to reloads now that we have `networctl reconfigure`
<arianvp> alrighty. lets switch!
<NinjaTrappeur> +1
hmpffff has joined #nixos-systemd
<flokli> baby steps here. We restarted networkd before. Let's get 245 in, and then make more use of its features
<flokli> IMHO
pbb has quit [Ping timeout: 272 seconds]
pbb has joined #nixos-systemd
<arianvp> I meant lets switch my computer to v245
<arianvp> but I like your enthousiasm :P
<flokli> andi-: commented on the PR about what I wrote here
<flokli> can you push a commit disabling homed for now, and re-test?
<andi-> I didn't even find the homed binary on my system..
<andi-> Is homed in fact part of v245 and are you pointing at the right git rev? ;)
<NinjaTrappeur> OO
<NinjaTrappeur> I can't find it in the release note
<NinjaTrappeur> For some reason I thought it was part of the v245 release
<NinjaTrappeur> oh no, nevermind, it is
<NinjaTrappeur> > * A small new service systemd-homed.service has been added, that may be
<{^_^}> error: syntax error, unexpected '*', at (string):296:1
<NinjaTrappeur> used to securely manage home directories with built-in encryption.
<NinjaTrappeur> ok, switching my main computer to the brach. Here goes nothing ><
<arianvp> flokli: why not keep homed in?
<arianvp> portabled is in too eventhough it's broken
<arianvp> The fact that I could find out it was broken was because it was in :P
<arianvp> `systemd-repart` looks freakin cool by the way
<arianvp> can finally get rid of all this cloud-init bullshit
<flokli> arianvp: I'm afraid it might currently work half-way, people rely on it, and then it suddenly breaks
<flokli> do you want to walk down the rabbit hole of writing a test to see how it works?
<flokli> s#how#how/if#
<andi-> flokli: again: You want to update to the latest v245 release that is v245.3 ;)
<andi-> before we trip over all the issues that upstream already fixed
<flokli> andi-: missed that part somehow
<flokli> will do
<flokli> and see if I can disable homed as well
<andi-> told you yesterday before yo opened the PR ;)
<flokli> heh
<andi-> If it isn't enabled yet I wouldn't rush it in just yet.
<andi-> There is no need to increase scope
<flokli> /disable/
<andi-> [root@bertha:/nix]# find . -type f -iname 'systemd-homed*' | wc -l
<andi-> 0
<andi-> not sure if there should be anything
<andi-> requires the option `homed` to be passed
<andi-> that then sets the macro/define ENALBE_HOMED
<andi-> defaults to off
<flokli> good
<andi-> mhmmm:
<andi-> option('homed', type : 'combo', choices : ['auto', 'true', 'false'],
<andi-> description : 'install the systemd-homed stack')
<andi-> we might be accidentially missing a dependency and that is why it is not on..
<andi-> should probably just pass false there to be explicit
<flokli> aye
<flokli> andi-: okay, new version with explicitly disabled homed and 245.3 pushed. also rebased against latest staging, hoping this will fix the build.
* andi- depoys
<flokli> hold your horses, another push incoming
* andi- goes buy horses
<flokli> 🐎🐎🐎🐎
<flokli> andi-: you can let go the horses
<flokli> if you have them by now
<andi-> mhm, building ZFS for this non-zfs system.. Where did it sneak in to again?
<flokli> isn't it accidentially part of the minimal installer, and it was decided to leave it like that? :thinking:
<gchristensen> I think it is on purpose part of the minimal image
<andi-> but this isn't an installer... :/
<andi-> I'll run a why-depends when this is done.. it compiled already so that doesn't really bother me much more
<andi-> flokli: most still fails to build on staging :/
<andi-> s/most/mosh/
<flokli> andi-: yeah, bash-completion too
<andi-> that worked here
<flokli> Some python test in test_nproc.py
* flokli kicks off the build again
<andi-> aha! For some reason my grub is being built it zfs support
<flokli> andi-: local override?
<andi-> I have a custom grub fork..
* andi- checks
<andi-> Oh, lol.
<andi-> zfsSupport defaults to `true` in grub.. we explictly override grub with `zfsSupport = true;` if we want zfs.. so someone flipped that default..
<andi-> (in 2015)
<flokli> is there a reason the default is flipped?
<NinjaTrappeur> 245.3 seem to work on my desktop setup as well.