<rain>looks like guix pull will keep trying to offload even with a failed config, instead of just moving on...
<rdtc55>I have the same problem. It's infuriating because my password is way too long... Is there a way to use full-disk encryption on a T400 with libreboot without having to type the passphrase twice?
***catonano_ is now known as catonano
<grubles>hmm looks like gcc-mesboot-4.9.4.drv is building using a debian 10 appVM on qubes
<ryanprior>Gooberpatrol66: or for fancier output, guix package -I <pkg name>
<ryanprior>I'm working on packaging some Meson, and I've got one that can see a library (granite, which I've also packaged) and another that can't see the library during its configure step.
<ryanprior>One thing that's different is that the package that sees it delcares the dependency in its root `meson.build` file, while the one that has a problem declares that dependency in its `src/meson.build` file.
<ryanprior>Is there a possibility that the root file is getting some kind of dependency path patching while other build files aren't?
<jas4711>the manual says LVM is missing, but what does that mean? I never bothered to explore LVM usage (which is critical for my deployment of libvirt-based virtual machines) after reading that. Now that I tried 'guix package -i lvm2' and using LVM, it appears to work fine. what am i missing?
<sirmacik>jas4711: docs might be quite dated on that
<jas4711>sirmacik: maybe it refers to being able to specify LVM through config.scm? that is not critical for many uses of LVM though, so the docs is a bit misleading here
<sirmacik>as I remember lvm2 + luks2 update were brought to repo few months ago so I can mount drive from my old arch installation. Probably there wasn't much work done in favour of configuring it through config file for running guix on it
<sirmacik>oh, grub got luks2 support early this year \o/
<sirmacik>might be a good news for running guix on more secure encryption
<jas4711>i think LVM support now just works, and the only thing missing is to add a no-op mapped-device-kind and update documentation. i just tried rebooting with LVM, and /dev/mapper contain them as expected. unlike LUKS or RAID, there is no operation needed to make LVM appear
<jvshahid`>I followed the instructions in section 'Contributing/The Perfect Setup', but when I execute `guix-devel-use-module' (or C-c . u), my CPU fans start spinning for a few minutes. I usually wait like 5 minutes and then kill the process. Is this expected behavior? Am I missing optimization flags?
<Kimapr>the driver (wifi-card) seems to be working but it isn't used by anything :(
***jvshahid` is now known as jvshahid
<raghavgururajan>efraim I fixed some other issues in Xfe. (#40980). Would you be able to push it? Thanks!
<apteryx>I think I may have found a good reason to let users pass root options at the CLI (GRUB -> Linux kernel cmdline -> picked up by our initrd): degraded arrays. I have a degraded array and I'm afraid to reboot because I'm sure I'll get stuck with no way to pass the "degraded" option in GRUB. I have the luxury that my system is still running, so I can reconfigure with that option in my operating system
<apteryx>configuration, but it could have been otherwise.
<apteryx>perhaps a good time to revisit those root file system on a Btrfs submodule patches (some older version of those patches even had that feature :-)
<grubles>ryanprior: installing guix in a debian appvm
<zimoun>Does it exist a function to expand '~' in Guile? Because the long options fail. For example, "guix pull --channels=~/path/to/file.scm"
<ryanprior>zimoun: ~ I think the shell has to handle tilde expansion. Would it work for you to do `--channels=$HOME/path/to/file.scm`?
<zimoun>ryanprior: yes it works. But '~' and '~username' should be expanded. I mean, it is what I expect. :-) Emacs provides "expand-file-name", does Guile have similar?
<bavier>I think there are some shadow utilities that will do that
<bavier>bash, at least, will not expand ~ if it's not preceded by whitespace, it seems
<jvshahid>Asking the same question I asked earlier. I followed the instructions in section 'Contributing/The Perfect Setup', but when I execute `guix-devel-use-module' (or C-c . u), my CPU fans start spinning for a few minutes. I usually wait like 5 minutes and then kill the process. Is this expected behavior? Am I missing optimization flags?
<NieDzejkob>jvshahid: I'd guess that you have to run `make' in your checkout
<NieDzejkob>(this is because loading all the code in the project from source takes a while)