<Apteryx>Hmm... Maybe I had to do "guix environment guix" using my modified versions. It's rebuilding the core tools now (bash, gcc, etc.). I guess due to my change. I'm hoping the crash will be resolved after that!
<cbaines>I thought I'd give installing Guix in a VM from a Debian live ISO a go again, but I've got stuck copying the behaviour of the cow-store service. I can't seem to move the mount, mount --move /.rw-store /gnu/store gives mount: bad option. Note that moving a mount residing under a shared mount is unsupported. Any ideas?
<amz3>I've sent a packaging request on guix-help..
<rekado>amz3: normally a Makefile will install to PREFIX and allow the user to override the PREFIX variable.
<rekado>so in Guix we would to (arguments '(#:make-flags (list (string-append "PREFIX=" (assoc-ref %outputs "out")))))
<roptat>hi, I've got a problem with xfce4-terminal when I want to choose colors, it crashes with "(xfce4-terminal:14965): GLib-GIO-ERROR **: Settings schema 'org.gtk.Settings.ColorChooser' is not installed"
<cbaines>Is there a simpler approach to the cow-store service for installing GuixSD? I'm trying (and failing) to install GuixSD from a Debian live system, and I can't seem to reporoduce a working cow-store service like thing...
<slyfox>at which stage --with-input= tries to perform the rewrite? i thought it changes key/value ~aroud -guile-builder where it's trivial to see all inputs (gcc/cross-gcc): http://dpaste.com/38J55YR.txt
<ng0__>for intel ethernet cards, is the Intel i350-AM2 Gigabit Ethernet supported by linux-libre?
<ng0__>this is on supermicro server if it helps.. I seem to recall that most of my devices have intel ethernet, but I'm not sure
<ng0__> 82579LM Gigabit Network Connection by intel is on another machine which works with linux-libre.. I guess the problem is then just with wifi from intel?
<ng0__>or are there some proprietary mushrooms in chipsets used on server boards?
<mystified>hey guys trying to make bootable installer. decompresssed th file. I now have " guixsd-usb-install-0.13.0.x86_64-linux " Description 'UNKNOWN' "
<janneke>thanks for pointing out the [obvious] pain, it's easy to get blind for your own mess ;-)
<OriansJ>janneke: it is easy for us to forget what is easy for us isn't always easy for others.
<janneke>glad you understand -- i can see how silly this unnecessary complexity is, esp. when trying to get others involved -- of course i have very sound historical reasons for things being as they are ;-)
<OriansJ>janneke: of course, you were by yourself and making progress but now other people want to help.
<janneke>also, src/reader.c did not compile with mescc and moreover, i wanted the C core for bootstrapping as minimal as possible -> not having a reader in C but running a binary scheme program saves some C primitives (and ca 200LOC)
<OriansJ>janneke: actually those things in the reader, aren't C primitives. They are just imported functions
<janneke>OriansJ: hmm...didn't you have a way in your stage2 LISP to make that distinction?
<janneke>i would like that for mes, but did not see how to do it
<OriansJ>janneke: it is easy anything in C that takes the form of name(...) is just an imported function
<OriansJ>janneke: as for the stage2 LISP, only a small number of special things needed to be treated differently than all of the other functions. They are generally referred to as special forms.
<janneke>OriansJ: i like what i hear, i've been searching for something like that, but i cannot see it yet
<brendyyn>guix import cpan is broken I think. Doesn't recognise the SSL cert
<ng0>it's not recent I think. This was the way since forever to ensure that your static build binary is the same on every system
<ng0>there's a follow up commit to one of the recent font-build-system commits which will fix the build of a font.. Strange that lint did not complain about two build-systems in one package :) I will be done in a while
<EuAndreh[m]>I just sent a few duplicated (and a few encrypted) mail to firstname.lastname@example.org
<EuAndreh[m]>Sorry about that, I'm still struggling a bit with the email workflow
<Apteryx>I'm not sure what to do of the translation file updates though; there's a datestring somewhere in there so it's non-reproducible as it stands.
<Apteryx>But there was already a date string there and it didn't seem to affect anything. Maybe it's OK.
<Apteryx>sneek: later tell alezost: Do you think it'd make sense to use search-paths instead of the elisp glue code for module discoveries? I think I've got something working, but I've yet to test it (touching gnu-build-system search-path means rebuilding the world).
<ng0>sigh... apparently GNU wants a trusted key for ftp upload capability. which is not good when you simply ignored the WOT part of GnuPG for a long time. Anyone by any chance living around NRW, Germany of you?
<ng0>or I simply start sending signed emails with the now permanet key I have and maybe some of you want to sign the key as is without meeting