<OriansJ>THFKA4: The default and easy configurations are just the ones the active Guix developers want. As Guix is written in Lisp, it be extended to crazy levels; it is just a matter of effort. For example you could put lvm ontop of a single luks and thus the password grub asks for will unlock the entire lvm
<THFKA4>yep, i have that going with NixOS, which also puts the kernel into /boot by default
<THFKA4>i would still need to keep the EFI partition unencrypted with LVM/LUKS i think
<OriansJ>THFKA4: I use coreboot and libreboot myself, so that I am unsure of
<tune>I'd like to have passwordless sudo for the guix command. What is the best way to do this?
<tune>Sometimes I leave my machine and have told it to do a 'sudo guix pull' followed by a 'sudo guix system reconfigure' but then it's stuck at a password prompt and times out instead of getting things done while I'm away
<rekado_>g_bor: core-updates isn’t ready to be built at this point. It’s still changing.
<g_bor>rekado_: ok, I see. Then it would be safe to disable it on berlin. WDYT?
<rekado_>yeah, should be fine, but I’m not comfortable with disabling this in the sqlite database.
<rekado_>hmm, some users have a problem with “offload” failing. They are using the current guix after running “guix pull”, but the shared daemon is from a git checkout, running inside of an environment that has guile-ssh
<rekado_>maybe I should build the daemon in an environment lacking guile-ssh?
<rekado_>we are currently working around this by passing “--no-build-hook”, but it’s not a good look.
<g_bor>rekado_: I have no idea, but if you can try this, then please go ahead.
<rekado_>something completely different: we have a bunch of profile hooks that scan the profile. This happens repeatedly. Can we introduce a higher level abstraction that would allow us to fuse these directory traversals?
<g_bor>The current view could be improved by showing the commit message.
<rekado_>g_bor: isn’t that already displayed well?
<rekado_>so… I’d like to also have a progress indicator. We know the number of derivations that will be built and I guess we also know how many are left to be built (though this may be tricker with parallel builds).
<rekado_>Can we print something like [3/42] in front of the messages?
<efraim>I'd suggest incrementing the [x/42] on the completion
<roptat>civodul, 73.2% substituts disponibles from mirror.hydra
<allana>I'm failing to successfully mount a luks device as my home partition in guixsd. Can another set of eyes help me diagnose my problem? I'm getting the error: device '/dev/mapper/my-home' not found. I am able to successfully mount the device manually. https://paste.debian.net/1056583/
<janneke>allana: i'm afraid you'll have to use the uuid for the device, label won't work
<allana>janneke: Ok, I must have misunderstood the docs regarding the mapped-device target.
<allana>janneke: Thanks. I got really excited seeing that example, but it seems to still fail with the same error. The uuid is the source for the mapped device, but it seems that /dev/mapper/<target> is not created.
<allana>janneke: Also, I am curious how this works. does guix prompt me for the passphrase?
<rekado_>I modified hook-message so that it doesn’t have a fallback; it instead returns #f and the fallback message is printed by the caller with (format port (info (G_ "running profile hook of type '~a'...~%")) hook-type)
<civodul>rekado_: yes the fallback case should be (format #f (G_ "running ... ~a") hook-type)