<thomassgn>I'm on a fresh guixsd install with linux-libre-4.14.3 and when I run guix system reconfigure or guix package commands I get 'error: open-file: No such file or directory: "/gnu/store/...-linux-libre-headers-4.4.47.drv"' Why is it looking for these headers, and more importantly - how do I solve that?
<civodul>thomassgn: that's on the installed system or in the installation image?
<thomassgn>it's in the installed system after booting and loging in
<civodul>what does "guix gc --list-live | wc -l" return?
<thomassgn>"guix gc: error: build failed: program `/gnu/store/pii5cimi72lj5l7793h54g5sg0sr2apl-guix-0.14.0/libexec/guix/list-runtime-roots' failed with exit code 1"
<civodul>hmm does this command fail systematically?
<thomassgn>going to redo the install, but remove /var/guix also...
<thomassgn>civodul: not sure if you remember, but you helped troubleshoot this machine some time ago (a month or so) because of a duplicate coreutils in profile. In the end it looked like I had a bad/corrupted disk. I found it to be a bit strange - because everything else worked fine on the system. I discovered when I reinstalled now that I got the same error while on the live disk, and found I had coreutils in my OS
<thomassgn>declarations packages field. Commented that out and haven't seen the error.
<castilma>when I want to start the guix daemon _service_, i get :guix system: error: exception caught while executing 'start' on service 'guix-daemon':
<castilma>ERROR: In procedure delete-file: Is a directory
<castilma>how can i get more info? I mean, it should it least print the filename it wants to delete...
<castilma>(I had multiple errors in the fs. maybe that changed some things I need to correct manually now)
<thomassgn>I've had coreutils there since I started using guix, and the problem appeared in the beginning of september. I'm not sure I should write a bug or something on it, seeing as the error looks nothing like an error in config... ?
<civodul>thomassgn: if you're unsure about your hard disk, you should probably make sure that it's healthy first
<civodul>otherwise you could have all sorts of problems
<clacke[m]>after guix pull the latest definitions are in ~/.config/guix/latest
<clacke[m]>I'm very hazy on where the guix client itself ends and where the pulled guix begins. There's more than the package definitions there, but one still needs to upgrade the guix package from time to time.
<shiranaihito>i'm trying to install GuixSD with a system configuration, but it contains an nginx definition too, and i get an error that says: "ssl-certificate in the nginx configuration for the server with name "(www.example.com)" does not exist"
<shiranaihito>so i guess i should start with some kind of bare bones system config and then move on to a more "fully featured" one once GuixSD is installed?
<shiranaihito>.. or is there some kind of standard workaround for this kind of stuff?
<hulten>shiranaihito, I am quite new to Guix(SD), but I would say doing a more minimal install, and later on adding configuration and then 'guix system reconfigure your-scm-file' should be a good aproach.
<shiranaihito>any ideas about this: "grub-install: error: /gnu/store/[..]-grub-2.02/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory" - it seems i do have a "target" for the bootloader in the config: "(bootloader (bootloader-configuration
<mb[m]1>librsvg 2.40.20 is the last version that does not require rust
<pkill9>hulten: yeah it does that for me, `guix pull` seems to behave differently though, it tried to compile guix instead of just symlinking to the already compiled version which I had created by running `guix pull` as my non-root user
<shiranaihito>civodul i did set something to "UEFI" .. should it be "Legacy BIOS" instead?
<shiranaihito>.. or is there something i can do to fuck things up while following the official installation instructions, with network and partitioning stuff, before the instructions get to "guix system init"?
<ofosos>If you look at the `surfraw' shell script, there's the config lookup beginning line 47. I would assume the configure script gets passed --prefix and surfraw uses that to build the path to the global config
<ofosos>Also, see line 163, if your profile does not contain a perl binary it will flatly fail, since it doesn't include the path to the perl store item that is passed as an input
<rekado_>it really should not look for the config at /etc; if the file at /gnu/store/…/etc/ exists, then this should be diagnosed, not changed.