<lfam>The "Build Environment" section has two blocks of commands to execute in the shell. The first one can be executed as-is unless your system has some special way to add users and groups. The second one is really just an example of how to run the daemon. Presumably you will want to run the daemon with your init system / process supervisor
<lfam>Digit: It's just a warning. It's harmless. I believe the issue is that the locales are not available in the environment that the daemon is running in
<lfam>The basic mechanism of providing locales to *some* environment is covered in 2.6 Application Setup
<lfam>And I know this is heresy ;-) but you can look at the file 'etc/guix-daemon.service' in our Git repo for an example of putting the locales in the environment of the guix-daemon
<Digit>hrm. not sure that's my only problem here. locales warning repeated when i tried guix package -i hello, and also "guix package: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused"
<lfam>The second error is a real error. Are you sure the guix-daemon is running?
<Digit>yep. will look into that after getting the daemon into the init system, if i dont fall asleep first. ((why do these bright ideas always come so late in the day?))
<Digit>there we go. sloppy n ugly, n maybe overly simple, but there it is, as dropped in to /etc/init.d http://dpaste.com/2HJ46D3 twill be a while before i discern whether that worked, since i rarely reboot. i think it maybe only really requires the first and last lines.
<lfam>Digit: It's better to use a path that doesn't go directly to /gnu/store. If you use that path, the service will stop working when you upgrade Guix. I recommend '/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon'
<lfam>It's an absolute path so it should work in places where ~root/.guix-profile does not
<fps>hmm, i forgot. how could i set the PREFIX environment var for a make based build again?
<Jookia>htgoebel: I think you have to read the packages and gnu-build-system. If you want to understand what the builder is actually doing, you'd have to find the builder Guile code and format/read it I think
<htgoebel>jookia: I do not want to understand the builder :-) I just need to find out why my build fails.
<xd1le>does GuixSD have concept of stable/unstable? I'm guessing not because it's "beta" software? I just did a fresh 0.11.0 install, and so I'm wondering if to stay on 'stable', I would just have to avoid running `guix pull` under root until a new release? or is that not recommended?
<xd1le>(I know there's rollbacks btw, but just wondering)
<Jookia>htgoebel: I think you want to source the environmental variables file that's left over, cd $PWD and also read what happened before the build failed
<htgoebel>Jookia: Hmm, I'm not convinced, but this may indeed work. No need to set up an guix environment then?
<Jookia>htgoebel: I think sourcing the environment variables will bring you in to the environment, though I could be wrong
<ng0>there is no concept of 'stable' / 'unstable' right now, xd1le. It's just rolling.
<ng0>and the updates which would cause like 300 packages to rebuild are moved into a separate branch and tested for stability etc, so the rolling is smooth for the users
<ng0>generally a regular guix pull + guix package --update should be enough.. and guix system reconfigure /path/to/config.scm for updating kernel etc
<ng0>I still got no reply from the local shop about PSUs.. could just walk there, but: was there any change in PSUs in the last 17 years? can I just plug in a 2016 produced PSU into a 1997 board and it works without producing toasted chips?
<ng0>anywhere I should read up on? PSUs were never my favorit subject
<ng0>ludovic, can't send it as an email comment right now, but I'd suggest for lynx to look into the patches and or pre versions of lynx. that could fix the gnutls problem, changelog has some gnutls items.
<rekado>janneke: we discussed shortly about whether to enable xwidget support in our build, but in my opinion it’s just not mature enough.
<rekado>it depends on the old Webkit API, which means that you have to link Emacs with an unsupported version of WebkitGtk.
<rekado>handling of the xwidget buffer is also kind of frustrating at this point
<Jookia>davexunit: You've reminded me that the hunspell checker already has an environment variable that does the same thing as what I want: DICPATH. But is it worth getting Guix/Nix to set this variable in every profile when it already handles XDG_DATA_DIRS the same way?
<Jookia>Oh, now I remember why DICPATH/HUNSPELL_PATH is a problematic idea: There's also other libraries like hyphen mythes too
<ng0>related to the other thing, rekado I think the first generation of eoma68 a20 is too weak to compile a complete system including X etc..? I mean the only real limiting builds I experienced on machines where I had to compile webkit, libreoffice, or firefox and failed for obvious reasons. so theoretically I could compile X11 on a 1ghz toaster...?
<ng0>or is cross compiling AND system-image something I can outsource?
<Jookia>davexunit: Given hunspell/mythes/hyphen all fit this issue, it seems like the better option to include all three really is just checking XDG_DATA_DIRS
<ng0>but other than that, not that i'm aware of. I'm jus tsubscribed to lists and have an search:RELEASED 'inbox'
<Digit>ACTION gets back to getting reacquainted with guix, after installing guix on devuan before falling asleep last night, and while looking into emacs integrating, installing geiser, thinks "mmm, i really should thank those guys for making this"
<Jookia>davexunit: I'm disappearing for a while but I spent a while surveying all the dictionary software and how it fits together and have concluded that DICPATH is the right way to go, as well as ASPELL_CONF. :) Thanks for your input! I'll write up my reasoning tomorrow in the issue I linked to
<ng0>'commercial ad voice questioning: has this ever happened to? 'you plug in your functional guixsd usb disk in your very old Asus AspireOne. You boot it, you select linux-libre, there is activity on the stick, and then it is giving you the black screen?