<cybersyn>roptat: it worked! thanks for the advice, I'll clean it up and push it upstream in the morning. have to say the guix packaging system is a lot to take in at first, but already feel that getting through this first non-trivial package taught me how simple it actually is and I'll be able to contribute frequently soon enough.
<cybersyn>my daily driver since winter and have hit some obstacles in my packaging attempts since (because everything i've wanted that isn't already available has been a bit complex), so put it off until a rainy day, and now that we're under lockdowns for the first time since last year I've found the time, but already have some thoughts about better ways to communicate the process to newcomers, will do a post about it it in the near future :)
<hendursaga>How's ZFS support with Guix? I see there's been some activity but how has dogfooding gone so far, if it's at that stage yet?
<dstolfa>hendursaga: i haven't tried it but i guess it just works? partitioning your drive and specifying a mount type "zfs" with whatever options you want should just work (TM)
<marusich>Maybe I messed up somehow, but that is my intent.
<hendursaga>dstolfa: one reason I liked ZFS is it was (at least on FreeBSD) really easy to create different pools of data encrypted with different keys, transparently
<dstolfa>hendursaga: if you like ZFS, use ZFS. there's a guix package with the kernel module (that will be compiled on your machine because of the binary clauses of GPL and CDDL that are a bit of a grey area), and you should be able to just use it
<marusich>civodul, I have to run for now, but I will try some other things, like also running strace to see what gdb is trying to do...
<marusich>Oh, I forgot to say: thank you and everyone for taking a look. I appreciate it!
<marusich>the_tubular, it's tricky because the disk configuration is outside the management of Guix... I suggest examining the system tests for the gpt case and comparing it to what you are trying to do in your own situation.
<marusich>yes, that is what i mean, but you also need to add a "target" field in the bootloader-configuration
<marusich>this will tell grub where to install the bootloader. It should be installing it into /boot/efi; my understanding is that the bios_grub partition you made will not be used at all in an EFI configuration.
<marusich>perhaps you already know, but when grub installs a bootloader to a gpt partitioned disk in bios mode, it can install the bootloader to a bios_grub partition. So that's the purpose of that partition.
<the_tubular>Line 21 still says : (bootloader grub-bootloader) in the pastebin you sent
<the_tubular>Same error as before : error: /gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
<marusich>any other context in the error message, like the grub command being invoked?
<the_tubular>Yes, here it is : guix system: error: '/gnu/store/mb7sg4q398ikdlx56whp2p8msa8pyakw-grub-efi-2.04/sbin/grub-install --boot-directory //boot --bootloader-id=Guix --efi-directory //boot/efi' exited with status 1; output follows:
<marusich>Honestly, I'm not sure. If I were doing this, I'd make sure I had a backup, and then try modifying the partition scheme, but I'm hesitant to recommend that since it could cause your system to become unbootable
<marusich>Is a directory named /sys/firmware/efi visible to your right now in your booted system?
<marusich>e.g. if you run ls /sys/firmware/efi, what do you see?
<marusich>I don't know how grub-install detects whether it should be doing a BIOS install or a UEFI install. I imagine you could probaly invoke grub-install manually somehow, but you'd have to know the arguments to pass to it, and if you used stuff from /gnu/store, they might get GC'd if you run "guix gc" later on (Guix sets up gc roots ensures that won't happen when you run "guix system reconfigure")
<the_tubular>I'll be right back, try to download a fresh guix image and burn it into a USB stick
<marusich>But yeah, if I were investigating, I would make sure I have backups, then try removing stuff related to BIOS (e.g., the bios_grub partition), and if it still doesn't work, I'd try booting Gentoo in UEFI mode and running "guix system init" from within there, to see if grub-install does the right thing there.
<marusich>I'm gonna have to go to sleep, but hopefully somebody else who knows about using Guix System with UEFI can help more.
<jab>civodul: I am currently just going to try out the stateless image.
<jab>I'm surprized at how long it takes to build. I must be getting my $s worth. :)
<jab>civodul: maybe you have to build a stateless childhurd first...then after that exists in the store, then you can build a stateful childhurd...just guessing.
<civodul>jab: the error must be because you have (image (const "/path/to/image")) instead of (image "/path/to/image")
<tissevert>civodul: I'd rather be the one to avoid opam if I can avoid it but the package I was curious about had an opam package and I this time I remembered that guix had an import for opam except…
<tissevert>a ton of things among which: it's not in the official opam repositories, so I'm manually adding dependencies as long as guix build breaks, discovering exotic opam packages which aren't packaged for guix either, or with a bad version
<tissevert>so I'm the one entering the infinite recursion, of manually solving dependencies, then wondering why dependencies of dependencies break, and ending up not even knowing what problem I'm trying to solve in the first place
<dstolfa>tissevert: you can add new versions of dependencies (or update existing ones if reasonable) and use (inherit ...) in all the older versions of the package
<dstolfa>if the dependency that's in guix is too old of a version for you, maybe you can update it, or you can simply add a newer version and then have the old version inherit from the new version
<tissevert>I'd be willing to try that, if, like I said, builds weren't failing here and there leaving me in a state of the deepiest confusion
<dstolfa>well, using `guix import opam ...` will produce a sensible starting point for a package definition, but it might require some tweaks. i'm not sure if i can offer any more advice without digging into it more, but when i do these things, i usually do a `./pre-inst-env guix build --check <package name>` to make sure it builds as a standalone thing, and if it doesn't, then i investigate why
<tissevert>and I was wondering whether there was a way to reproduce what had happened in that environment to make a build process out of it
<tissevert>which is why I asked if someone knew whether opam was distributing source code only or if it had a way to retrieve pre-compiled binaries
<dstolfa>tissevert: i think it's source code, but don't quote me on that. my impression when installing things with opam is that it took way too long to be binary packages
<jab>and a cookbook example would be awesome. I actually want to try to create an MASSIVE cookbook entry to info manual that explains all of the DNS settings.
<jab>I found a guide online that was instrumental in helping me understand it all. I'll email said blog person and see if I can copy his blog for a manual. I think it's configuring rspamd with opensmtpd or something like that.
<apteryx>I'd be interested to proofread it and try it myself when it's ready
<apteryx>On another topic, I think this shebang may be useful to force /etc/profile and Guix environment setup when launching a script via SSH: #!/usr/bin/env -S bash -l
<apteryx>it'll cause /etc/profile to be sourced, which will cause /etc/profile.d/guix.sh to be sourced (on foreign distribution). ~/.bashrc should be sourced as well from ~/.bash_profile
<jab>apteryx I'm actually having fun using org babel to execute remote bits of code with :dir /ssh:joshua@lamora#59605:~/
<jab>I use a non-standard port. endlessh sits on port 22.
<civodul>marusich: the source of tzdata has text files that are very informative
<civodul>maybe not exactly what you're asking for though
<marusich>I see... That's fair. It's such low effort to just look it up on Wikipedia, I've never bothered...
<liltechdude>Hello, I'm recently rise up mail server and now have problem with certificate: "SSL error connecting mx1.liltechdude.xyz (126.96.36.199:993): unable to get local issuer certificate". Sorry for writing in this chat about that problem, but may be it's could somehow to be solved from guix part? I have already make pull and upgrade. Thunderbird works pretty well.