IRC channel logs


back to list of logs

<phant0mas>mig recipe works perfectly,preparing patch
<dxk>Hi. I'm trying to get started with guix. I've installed 0.5 (make check passes all tests) and from git (as of today, which passes all tests except the 'topologically-sorted, more difficult' test in store).
<dxk>guix package -s hello works, but when I try to install it downloads lots of files until guile-2.0.9.tar.xz, then fails with 'guix package: error: build failed: unable to fork: Invalid argument.
<dxk>I've poked around and googled but come up blank. Anyone have any suggestions?
<davexunit>dxk: hmm I don't know what's happening. if no one else responds on this channel, could you write to the guix-devel mailing list?
<dxk>Thanks, I'll give that a try.
<phant0mas>dxk: what distro do you use? Have you installed all the dependencies?
<dxk>I've tried it on two distros, LFS/BLFS and Gentoo. I have the stated dependencies of guile (2.0.9), g++ (4.7.3), libcrypt (3.8.0), sqlite (3.8.2), libbz2 (1.0.6). I also had to install graphviz and some fonts to make today's git.
<dxk>I don't know if it is relevent, but I am getting messages in the system log complaining "guile: Libgcrypt warning: missing initialization - please fix the application"
<civodul>Hello Guix!
<mark_weaver>hi civodul!
<civodul>hey, mark_weaver
<mark_weaver>do we want to have gnutls consult a system-wide certificate store? it looks for one in its configure script, but doesn't find one so it disables that entirely, leaving each individual application to do its own thing. that makes configuration a pain.
<mark_weaver>openssl, on the other hand, searches for them in its /nix/store/ directory, which is always empty.
<mark_weaver>openssl provides environment variables at least, but gnutls doesn't.
<mark_weaver>so for programs that use gnutls, each individual program has to be configured independently.
<mark_weaver>seems like kind of a mess to me.
<civodul>mark_weaver: then i guess we should provide a system-wide place, and just cheat with the configure script so it considers it available
<mark_weaver>no need to cheat, there's a configure option for it.
<civodul>ah, even better :-)
*civodul always thinks of dirty hacks :-)
<mark_weaver>the usual place, and the first place its configure looks, is /etc/ssl/ca-bundle.pem
<mark_weaver>heh :)
<civodul>yes, right
<mark_weaver>should I add that to gnutls's configure arguments?
<civodul>yes, please
<civodul>probably with a comment that explains the situation
<civodul>BTW, i now use DejaVu, and indeed, it's much better for things like λ
<mark_weaver>the foreign language spam in my inbox looks much nicer now too :)
<mark_weaver>especially the russian and arabic :)
<civodul>that's definitely cool
<mark_weaver>civodul: should openssl be configured to look in the same place?
<civodul>probably, yes
<civodul>this is keeping hydra busy :-)
<mark_weaver>hmm, well, it wants a directory with symlinks named by the hashes of the keys, which would normally be in /etc/ssl/certs/
<mark_weaver>I suppose that one is less important, since openssl looks for an environment variable.
<mark_weaver>yeah, in a way I'm sorry to give hydra so much to do, but otoh our crypto stuff needs updating.
<mark_weaver>btw, does 'w3m' do proper certificate checking for you?
<mark_weaver>for me, it tells me everything is valid, even self-signed expires certs. even if I specifically ask for the page info, it gives me a nice detailed display of the expired unverified cert and tells me it's valid :-(
<mark_weaver>I wonder if I just have some bad config file over here or something.
<civodul>i haven't checked what my w3m does
<civodul>but yeah, it's great that you found all these problems
<mark_weaver>hmm, maybe we should look for the trust store in /etc/ssl/certs/ca-certificates.crt instead. That's where debian and ubuntu put it.
<mark_weaver>civodul: does your system have /etc/ssl/ca-bundle.crt or /etc/ssl/certs/ca-certificates.crt ?
<civodul>it has /etc/ssl/certs/ca-bundle.crt
<civodul>a mixture of both, it seems
<mark_weaver>well, gnutls's configure doesn't even look there. the first two places it looks are /etc/ssl/ca-bundle.crt and /etc/ssl/certs/ca-certificates.crt
<mark_weaver>unless anyone objects, I think I'll choose /etc/ssl/certs/ca-certificates.crt.
<mark_weaver>I'll post the patch to give others a chance to weigh in.
<civodul>no objections
<phant0mas>civodul: mig gets generated by the configure command
<phant0mas>that's why we don't need the build
<phant0mas>but I guess I should have put a comment about that....
<phant0mas>still learning :P
<phant0mas>fixing it right away
<civodul>phant0mas: MiG is written in C, right?
<civodul>so 'make' does build things, normally
<phant0mas>I know
<phant0mas>but not with this one
<phant0mas>when you run make
<phant0mas>it says no target
<phant0mas>and it generates mig just after the ./configure
<phant0mas>you just have to pass a flag with the header includes
<phant0mas>let me ask on the hurd channel
<phant0mas>but I trust what I see :P
<mark_weaver>strange. I wonder what devs do when they're working on mig.
<mark_weaver>(maybe no one has worked on mig in decades)
<phant0mas>it's quite old, so that maybe a chance
<mark_weaver>seems broken to me.
<phant0mas>I will ask in the hurd channel, I just hope braunr won't yell at me :P
<civodul>MiG has seen some activity lately
<phant0mas>in the meantime if you have some time download the tar and try it
<civodul>well, i trust you, but i'm trying to understand :-)
<phant0mas>that's why I will be back with a clear answer :-)
<civodul>damn, why isn't qemu available on hydra?