<ofosos>so, i packaged up vagrant, listed the log4r as an input, but vagrant complains about missing log4r. .guix-profile doesn't contain log4r and as far as i understand it shouldn't contain it, but vagrant still complains
<davexunit>putting log4r in 'inputs' wasn't the right thing
<civodul>davexunit: ↑ with syntax highlighting :-)
<SovereignBleak>davexunit: If you figure out how to make `gux system disk-image` output an AMI, I'd love to know. I have an employer who wants to go stateless and easily deployable GuixSD AMI's is the only thing standing in my way. Otherwise it's going to be NixOS.
<wingo>civodul: s/unique view/single view/ i think; "unique" might imply unique to each process
<reggggieee>hi, i'm having trouble setting up my locale env variables for guix. do i need to put anything special in my .bashrc? when i do a locale command LANG and LC_ALL are en_US.utf8 without quotes, whereas everything else listed has "en_US.utf8"
<lfam>Welcome reggggieee! Is this with Guix on another distro or on GuixSD?
<lfam>reggggieee: Make sure that whichever user's profile you are using has a locales package installed. glibc-locales is *all* the locales and it's big. glibc-utf8-locales is a subset used for testing, but it also happens to include en_US.utf8
<lfam>BTW, this warning is basically harmless, but it is annoying :)
<lfam>I'd like to clarify my last sentence, "Make sure that whichever user's profile you are using". What I meant is, "Make sure that whichever user's profile you are using the locales from for the systemd unit file environment declaration..."
<reggggieee>yeah, but like in guile when i do (setlocale LC_ALL "") i get invalid argument
<lfam>You'll need to set GUIX_LOCPATH for each Guix user, too, if you want to avoid locale issues.
<reggggieee>ok, i'm trying the guix-daemon thing you mentioned above. thank you
<lfam>I'm not sure it will affect your Guile REPL, but it's a good thing to do anyways
<efraim>slyfox: sorry, i'm in and out for a while. building gcc-final was no problem, i have it upgrading less, bc, libiconv, libsigsegv, gnutls and libgpg-error and it stops on expat with: checking whether the C compiler works... no
<slyfox>does guix package spec have a knob to disable slow bootstrap process? i guess guile tarball has something that is already bootstrapped for end-users but guix does not use it on purpose,
<sirgazil>Using Guix on a foreing distro, if i want to use Guix API, is it possible to do so by installing the guix package as a normal user? Because I'm getting "ERROR: no code for module (guix packages)" when I try to import that module.
<sirgazil>Or do I have to clone the Guix repository for that?
<bavier>slyfox: the guile-2.2 tarball has precompiled objects for boostrapping, but other versions do not.
<bavier>the guix package for guile-2.2 explicitly removes those precompiled objects before building
<bavier>sirgazil: so if your using the host-native guile, you'll need to set GUILE_LOAD_PATH=~/.guix-profile/lib/guile... yourself
<slyfox>efraim: heh, finally got to the same error in core-updates. libgpg-error gets that backtrace from 'ld' program.
<slyfox>my guess is 'ld-wrapper' does not have some .go files installed after guile update to 2.2
<sirgazil>bavier: I'm using guile from guix, and "guix package --search-paths" tells me to export PATH, GUILE_LOAD_PATH, and GUILE_LOAD_COMPILE_PATH. I already had those variables set, because of the suggestions I got from guix when installing packages.