IRC channel logs

<ph4n70m4s>good morning guix

<ph4n70m4s>yesterday I did a guix gc and I start to believe I shouldn't have done that

<ph4n70m4s>I am starting to get the error that modules are mssing

<civodul>Hello Guix!

<ph4n70m4s>good morning civodul

<ph4n70m4s>yesterday I used guix gc and today I am getting the error;;; Failed to autoload make-session in (gnutls):

<ph4n70m4s>;;; ERROR: missing interface for module (gnutls)

<civodul>ph4n70m4s: probably because you were using guile-gnutls installed from Guix, and that one got deleted?

<civodul>was it in your profile?

<ph4n70m4s>yes, I will reinstall it

<civodul>if it shows up in "guix package -I gnutls", then it cannot be GC'd

<civodul>does it show up here?

<ph4n70m4s>no

<civodul>ok, so how did it work before? :-)

<civodul>anyway, you only get that error when running "guix download https://...", right?

<ph4n70m4s>it used to be in my profile, and then yesterday I decided to run guix gc

<ph4n70m4s>and then everything was missing

<civodul>ph4n70m4s: if it's in ~/.guix-profile, it cannot be deleted

<civodul>and "guix package -I gnutls" would still show it

<ph4n70m4s>then how it worked till now? :P

<civodul>good question :-)

<civodul>does it show up in "guix package --list-generations"?

<ph4n70m4s>I am actually reinstalling everything now

<civodul>everything?

<civodul>did you do the "mv nix guix" thing?

<civodul>that could be the reason

<ph4n70m4s>yeah I did that, that's why I am doing a reinstalation now

<ph4n70m4s>better be safe than sorry

<ph4n70m4s>I am going to a lesson and I will be back

<civodul>ok

<rigelk>hi all :)

<civodul>howdy rigelk

<rigelk>civodul: I have summed up a little the discussions on the mailing here: https://etherpad.fr/p/guixp2p

<civodul>rigelk: cool, thanks!

<civodul>note that there is not/will not be a 'dht-get' command

<civodul>when i wrote 'dht-get', i meant "the 'get' operation on the DHT", in an abstract sense

<rigelk>oh ^^

<rigelk>i took that literally

<civodul>well there's a gnunet-dht-get command

<civodul>you can use that to try out GNUnet

<rigelk>I have ;)

<civodul>but in real life, it'd be better to talk directly to the gnunet-dht service, using GNUnet's remote procedure call (RPC) mechanism

<civodul>BTW, do you have a working installation of Guix?

<civodul>like, were you able to run "guix package -i hello", thinks like that?

<rigelk>civodul: I don't have a working toolchain as my computer is too weak to compile it (atom).

<rigelk>I remember to have tested hello ; Doing that now again to be sure

<civodul>yeah, that's a prerequisite

<civodul>let it run however long it takes, but do it ;-)

<civodul>hydra.gnu.org is currently unavailable, but when it's back, you'll be able to download binaries instead of building everything

<rigelk>ok, i shall run it ; but what if i get errors ? is there a way to resume or so ?

<civodul>of course, it will resume where you leave it

<civodul>so the first thing is to run "./configure && make && make check && make install"

<civodul>if there are test errors, report them

<civodul>and then, run "guix package -i hello"

<civodul>that'll build a load of things, but it should eventually succeed

<civodul>if it doesn't, do tell us

<rigelk>understood ; what about old versions of automake ? Do i need a version >= 1.12 ?

<rigelk>i got an error on another computer telling me this

<civodul>yes, you need >= 1.12

<civodul>if that helps, you can start from guix-0.5.tar.gz (so you don't need auto{conf,make}); install it, then run "guix package -i automake autoconf", then start from guix master

<rigelk>it's a beast so it would really be good to compile on it.

<civodul>sure

<rigelk>civodul: that's a way, but where will automake and autoconf be available ? in the profile ?

<civodul>yes, in ~/.guix-profile

<rigelk>ok ; not used to using it yet.

<civodul>so i think the most important thing now is to make sure you have working installations of Guix and GNUnet 0.10

<civodul>then you'll have to post the proposal on google-melange

<rigelk>GNUnet is installed and i'm running tests by now.

<civodul>ah ok, cool

<civodul>easier than Guix ;-)

<rigelk>seems like ^^'

<rigelk>civodul: i gotta go (to uni), but when do you usually go on irc ?

<civodul>during work hours, and in the evening

<civodul>local time

<civodul>but you're in France too right?

<rigelk>oui :) the only difference being that I can't access irc on my working hours...

<civodul>yep :-)

<rigelk>anyway, I shall setup my proxy and try to connect to irc so that i can talk from uni beetween two lessons.

<civodul>heheh :-)

<rigelk>ACTION feels like http://is.gd/GeLzgB

<rigelk>ok, gotta go ; see you civodul :)

<civodul>see ya!

<the_scourge>hi all

<Steap>;;; Failed to autoload make-session in (gnutls):

<Steap>;;; ERROR: missing interface for module (gnutls)

<Steap>ERROR: In procedure module-lookup: Unbound variable: make-session

<Steap>Does that ring a bell to anyone ?

<mark_weaver>looks like you're trying to download an HTTPS URL, but don't have the guile gnutls module.

<mark_weaver>unfortunately, I've forgotten the solution.

<Steap>yeah

<Steap>I installed gnutls using guix

<mark_weaver>when I compile guix, I pass --with-libgcrypt-prefix=/nix/store/v9q9d0xlamxhk0062cnp6lhywd9in281-libgcrypt-1.6.1 as an option to configure.

<mark_weaver>the hash will probably be different for you; that hash is from mips64el

<Steap>I'll try reconfiguring

<Steap>or maybe I should start by installing libgcrypt :D

<Steap>Damn, working on core-updates is a pain

<mark_weaver>why do you say that? it seems to work reasonably well for me.

<mark_weaver>I have three of my systems working on building core-updates now: my YeeLoong (100% Guix user environment), and other systems where Guix is built in a Debian wheezy environment: one Loongson 3A machine and a x86_64. All of them seem to be working reasonably well.

<Steap>mark_weaver: mostly because I keep re-building a bunch of things

<mark_weaver>ah yes, that's true :)

<Steap>so I basically see a whole lot of dependencies to re-build

<Steap>I go to bed

<Steap>and the next day, I see some of the dependencies failed to build

<Steap>try to debug, re-run the compilation

<Steap>sometimes I'd like to be able to just work on my stuff :)

<mark_weaver>*nod*, that's been happening to me too, often because of failed downloads.

<ph4n70m4s>I have the same errors today

*Steap just wants to re-send his patch series about Python

<mark_weaver>the xterm build is failing because the hash of the upstream file changed. The URL doesn't have a version number, and I guess that it's probably been updated. I've been too busy in Guile land to look into it yet.

<mark_weaver>the source code for 'shadow' also seems to no longer be available.

<mark_weaver>we need up apply security fixes to 'file' and 'libssh'. not sure if there are new tarballs with the fixes or not.

<mark_weaver>I

<mark_weaver>I can work on these things after guile 2.0.10 is out the door.

<mark_weaver>xterm changed their handling of SHELL a bit, but they still unset SHELL if it's not listed in /etc/shells. So annoying. Why do they feel like they have to take it upon themselves to judge my SHELL setting, and "fix" it for me.

<mark_weaver>there's no mailing list for xterm

<mark_weaver>I should probably find a new terminal emulator to replace xterm.

<ph4n70m4s>why I suddenly keep getting

<ph4n70m4s>checking for suffix of executables... ;;; Failed to autoload make-session in (gnutls):

<ph4n70m4s>;;; ERROR: missing interface for module (gnutls)

<ph4n70m4s>ERROR: In procedure module-lookup: Unbound variable: make-session

<ph4n70m4s> and then dependencies fail to build?

<ph4n70m4s>if I build one of them on it's own it gets built

<mark_weaver>maybe your "guix gc" deleted the gnutls that your guix was using, or something. this is really a question for civodul though.

<mark_weaver>if you build something outside of guix that depends on something within guix, you need to add it manually as a GC root, I think. I haven't used "guix gc" much for various reasons; it would delete too much for my purposes, so I've been avoiding it.

<mark_weaver>but obviously we'll need to improve it at some point.

<ph4n70m4s>it only fails with my recipes

<ph4n70m4s>which before I used guix gc didn't

<mark_weaver>do your recipes use https URLs (or http URLs that redirect to https)?

<ph4n70m4s>right now only two fail that they use git-checkout

<mark_weaver>if I were you, I'd rerun ./configure in guix and rebuild it.

<mark_weaver>but admittedly, I'm just making guesses. civodul is the person we need.

<ph4n70m4s>I even tried to reinstall everything

<mark_weaver>(I could figure it out by reading the source, but don't have time at the moment)

<ph4n70m4s>why is it doing this ?

<ph4n70m4s>checking build system type... following redirection to `https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz'...

<civodul>ph4n70m4s: yeah, you need to have GnuTLS with Guile bindings installed and visible in Guile's search path

<civodul>or use wget + guix hash

<ph4n70m4s>I have this problem when building packages

<mark_weaver>+ guix download with a file:// URL.

<civodul>ph4n70m4s: actually an Internet search shows lots of answers, such as http://lists.gnu.org/archive/html/bug-guix/2013-04/msg00157.html

<civodul>it's a common problem ;-)

<civodul>aah, or Steap: could it be that downloads from http://python.org go to https://python.org?

<civodul>and then bam, no GnuTLS

<civodul>while building packages

<civodul>lemme see

<civodul>oh indeed

<civodul>ph4n70m4s: reproduced; sorry for not getting it before!

<civodul>i'll push a fix

<ph4n70m4s>okay

<Steap>civodul: it used to work

<Steap>and now it does not work

<Steap>and I'm tired as hell so I won't be trying to debug that today :D

<civodul>np, i'll just add an 's' in the URL

<civodul>just testing right bnow

<Steap>civodul: oh, it's possible since the Python website changed recently

<Steap>so maybe there's a redirection

<civodul>ph4n70m4s: if you pull from master now, it should work

<civodul>you can try with "guix build -S python"

<ph4n70m4s>let me see

<Steap>civodul: from master ?

<Steap>Can you backport that to core-updates ?

<civodul>right now?

<civodul>ok, done

<Steap>éright when you want

<Steap>I'm just recompiling so much stuff

<Steap>I feel like rm -rfing /nix

<Steap>and switching to /gnu

<civodul>Steap: beware, hydra.gnu.org is still kinda broken

<ph4n70m4s>it's working!! :-)

<ph4n70m4s>at least it's building now

<civodul>good :-)

<Steap>civodul: I sort of noticed

<Steap>:)

<civodul>heh, that's hydra :-)

<rigelk>hi #guix

<ph4n70m4s>civodul: is this right?

<ph4n70m4s> ((#:configure-flags flags)

<ph4n70m4s> `(remove (cut string-match "--host.*" <>)

<ph4n70m4s> ,flags))

<rigelk>i have 'make check' errors ; could someone help me (provided my log file here: http://bpaste.net/show/190143 )

<civodul>ph4n70m4s: looks like it, but i'd need more context

<ph4n70m4s> http://pastebin.com/raw.php?i=EFbZdc45

<civodul>rigelk: never run make and make check as root

<civodul>well do what you want, but that's usually a bad idea

<rigelk>civodul: oh ; i ran the daemon as root, that's why

<rigelk>when getting the 'error: cannot bind to socket `/usr/local/var/guix/daemon-socket/socket': Address already in use', is there a way to purge the socket ?

<civodul>rigelk: for the test errors, please see https://lists.gnu.org/archive/html/guix-devel/2014-03/msg00168.html

<civodul>it's the same issue

<civodul>rigelk: it means there's already a daemon listening to that socket

<rigelk>i know ; i just don't know how to stop... oh wait

<civodul>"killall guix-daemon" works well :-)

<rigelk>yeah, i really need to write that down (used to using htop)

<rigelk>thanks civodul :)

<civodul>you're welcome

<civodul>rigelk: BTW, the test failures are minor

<civodul>you can do "make install && guix build hello"

<civodul>while we investigate

<rigelk>what consequences do they imply ?

<civodul>at worst "guix build --log-file" won't work

<civodul>but most likely the problem is elsewhere

<rigelk>are you sure it's minor ? i mean store.scm, build.sh look important, aren't they ?

<civodul>ooh, i think i found it

IRC channel logs

2014-03-17.log