IRC channel logs


back to list of logs

<kete>hey alfplayer
<alfplayer>hey kete
<rekado->BTW: guix.el works fine after "make install", it just won't work with my git clone.
<vmlinuz88>Hello Guix
<zacts>I finally got around to getting my chat server up and running
<zacts>it's debian jessie (without any non-free debian repos) running on my beaglebone computer
<zacts>anyway, I do have a question about guix, which I'm running on top of debian jessie on my main laptop
<zacts>also, I wonder if I can use guix-arm on-top of debian on my beagle
<zacts>(but this would only work if there are pre-built guix packages for arm, and I don't have to build them myself)
<zacts>anyway, my question is, where does the latest guix.git install the store by default? the doc mentions /gnu/store
<zacts>I don't have a /gnu/store
<zacts>I didn't use any flags other than; ./bootstrap ; ./configure ; make ; make check ; sudo make install
<zacts>note: every single make check passed without even WARNings
<zacts>debian jessie gnu/linux amd64
<civodul>oh, hello Guix!
<iyzsong>civodul: hi! how about non-appendable search-path? (eg: for GDK_PIXBUF_MODULE_FILE, we don't want "$gdk-pixbuf/...:$librsvg/...")
<iyzsong>for those who may interest, gnome-icon-theme (before 3.13) is split into 3 packages. we lack the symbolic one, so the window close icon (eg: gnome-mines) is missing.
<civodul>iyzsong: non-appendable? like with a single item?
<civodul>oh and BTW ->
<taylanub>after a guix pull (maybe also before), I can't use guix download on https URLs. shouldn't this not happen, since it should use guile from guix?
<mark_weaver>guix download uses the guix from your host system, I believe
<mark_weaver>well, it uses whatever guile it was compiled with
<mark_weaver>here's what I do: after I've installed guix on top of another distro, then I set up my environment variables so that I'm only using things from guix itself, and then I recompile guix from clean using that environment.
<davexunit>the new binary tarball will save you a step :)
<taylanub>'which guix' points to ~/.guix-profile/bin/guix which has the shebang of a guile 2.0.11 in /gnu/store. 'which guile' also points to ~/.guix-profile, where it further points to the same guile 2.0.11 in the store. if I launch that guile and enter ",use (gnutls)" it can't find it.
<phant0mas>civodul: when crossbuilding bison-2.7 with target=i686-pc-gnu, m4 can't be found in PATH
<phant0mas>I added it as a native input, but shouldn't the already added propagated-input be enough?
<mark_weaver>taylanub: do you have gnutls in your profile? does GUILE_LOAD_PATH include $HOME/.guix-profile/share/guile/site/2.0 ?
<mark_weaver>civodul: so, hydra is heavily overloaded right now, and I notice that starman has a subprocesses that include bzip2 and nix-store, which I guess maybe is because someone is fetching <>
<mark_weaver>should we disable that functionality? does it even work properly with guix?
<civodul>mark_weaver: good question, probably not
<mark_weaver>is "probably not" in response to my first or second question?
<civodul>it probably doesn't work
<civodul>it's getting slightly less bad according to loadavg
<mark_weaver>I think it must be at least 30 minutes since hydra-evaluator printed the message "created cached eval 104182", and yet I still don't see it on the web interface. maybe the message should be "creating ..."
<civodul>heh, possibly
<mark_weaver>well, I killed the GC process, and the bzip2/nix-store is done
<iyzsong>civodul: basically, I want set the GDK_PIXBUF_MODULE_FILE search-path in gdk-pixbuf. in the builder it should be "$librsvg/.../loader.cache", well I guess that won't happend magically.
<iyzsong>so, please ignore me :-)
<taylanub>my guile load path has ~/.guix-profile/share/guile/site/2.0, but there seems to be no gnutls there. I thought its presence would be ensured by the guix package somehow, since its needed for 'guix download'...
<taylanub>maybe the guix package should propagate gnutls?
<civodul>taylanub: yes, it should (it's not even an input currently)
<civodul>OTOH, that would make the binary tarball bigger
<civodul>not sure if we should do that
<civodul>well, maybe we should anyway
<mark_weaver>I'm trying to update my system, and three times in a row I've gotten an unexpected EOF in the middle of downloading substitutes.
<mark_weaver>with three different files
<mark_weaver> 78: 1 [read-chunk-header #<input-output: socket 10>]
<mark_weaver> ?: 0 [string-index #<eof> ...]
<mark_weaver>ERROR: In procedure string-index: Wrong type argument in position 1 (expecting string): #<eof>
<mark_weaver>bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows.
<mark_weaver>guix substitute: error: corrupt input while restoring '/gnu/store/npnm9js6j9rwhx9lr0j09frpamzyri3b-qt-4.8.6-doc/share/doc/qt-4.8.6/qch/qt.qch' from #{read pipe}#
<mark_weaver>this time it happened with qt. the other two times were openjpeg and clang
<mark_weaver>grep 'corrupt input' screenlog.2
<mark_weaver>guix substitute: error: corrupt input while restoring '/gnu/store/97rfrd5acz4ca2547n6iv7g4ahch81rb-openjpeg-2.0.1' from #{read pipe}#
<mark_weaver>guix substitute: error: corrupt input while restoring '/gnu/store/30a4smwmj5w58agyr5al2bha8rm08pkh-clang-3.6.0' from #{read pipe}#
<mark_weaver>guix substitute: error: corrupt input while restoring '/gnu/store/npnm9js6j9rwhx9lr0j09frpamzyri3b-qt-4.8.6-doc/share/doc/qt-4.8.6/qch/qt.qch' from #{read pipe}#
<mark_weaver>^^ my three consecutive attempts to update my system
<mark_weaver>anyway, I have to go afk for the day. ttyl!
<davexunit>rekado_: good to hear you're giving a talk about guix!
<civodul>mark_weaver: i wouldn't be surprised if was OOM and killed the process
*civodul has to go
<rekado->Installing GuixSD on my main machine now, because I want to use it during the talk. (I'll swap the disks to go back to my previous system if I need to.)
<bavier>rekado-: I'm excited for this talk of yours
<rekado->unfortunately, it's limited to 20 mins.
<rekado->no extra time for Q&A, so I'll probably have to keep it simpler than I had hoped.
*taylanub got two laptops now, could install GuixSD on one
<phant0mas>civodul: ./pre-inst-env guix build --target=i686-pc-gnu mig works now
*DusXMT cheers
<zacts>hello guix
<alezost>rekado-: I've just noticed your yesterday's question about using guix.el without "make install". paroneayea wrote a blogpost about that: <>.
<alezost>paroneayea: Actually there is no need to set 'guix-helper-file' (it is relative to 'guix-load-path' anyway) and to require 'guix-autoloads' (because it is required by 'guix-init')
<paroneayea>alezost: I had problems before I added guix-autoloads, I don't remember what it was...
<paroneayea>but I will try that now
<paroneayea>alezost: seems you're right
<paroneayea>I'll update the post, thanks!
<alezost>paroneayea: thank you for the post! :-)
<paroneayea>alezost: I'm glad others have found it helpful :)
<civodul>rekado-: yay, nice!
<civodul>do report any issues with the installation :-)
<civodul>davexunit: shamelessly, i've just pushed two patches to 'guix publish'
<civodul>feedback welcome
<civodul>minor improvements, but i felt that privilege drop was good to have ;-)
<davexunit>civodul: awesome!
<davexunit>happy to have someone else hacking on it.
<davexunit>I only have so much time :)
<davexunit>I would like to clean up the narinfo rendering, myself.
<davexunit>it's a format string mess right now.
<civodul>heh why not
<civodul>i'll leave that to you anyway :-)
<davexunit>just low on the priority list so I probably won't do it for quite some time
<davexunit>the more important thing is getting compressed output ports to work in multi threaded program
<civodul>yeah, right
<civodul>so, who's willing to contribute GuixSD screenshots of current master with Xfce, showing things similar to ? :-)
<civodul>that would be wonderful
<civodul>davexunit: what was the issue again with HTML tags when using sxml->xml?
<civodul>mark_weaver: so i've respawned 'guix gc' and queue-runner
<civodul>the GC ran a loooong time but didn't find much to collect
<civodul>i believe we have reached maximum capacity
<civodul>so i'm removing 80-day old roots (instead of 85)
<davexunit>civodul: the issue is that HTML has tags that require a closing tag even if they have no contents
<davexunit>for example, <script>
<davexunit><script src="foo.js /> is invalid
<davexunit>it should be: <script src="foo.js"></script>
<civodul>ooh, i see
<davexunit>I have code to dump in there to resolve it, but I haven't had time to hack on it yet.
<davexunit>busy busy. this is actually my final week as web developer at the FSF so I've been trying to wrap up some things.
<civodul>ooh, already?
<zacts>davexunit: are you going to still work at the FSF doing other things, or are you changing jobs totally?
<zacts>(if I may ask)
<davexunit>changing jobs totally.
<davexunit>but I want to be involved on a volunteer basis instead.
<zacts>oh, in the same domain that is tech / software, or a new change altogether?
<davexunit>new job doing more serious software development.
<zacts>oh I see, neat
<zacts>yeah, I guess web-devel versus systems programming, for example, can suit different personality types better than others
<zacts>depending on what you are most interested in
<zacts>for me I think I would also be more interested in systems programming than web-devel
<davexunit>yeah, I'll be working in the web development space still, but more focused on automation, reproducibility, etc.
<zacts>ah cool, yeah
<davexunit>going to promote guix internally
<davexunit>see what happens
<davexunit>and hopefully learn a lot from using the existing automation tools that I don't like very much :)
<civodul>so you've found a job already?
<civodul>i wish i were so efficient
<davexunit>it, of course, isn't 100% free software work, but I will be doing some.
<davexunit>given my background, the company made that part of their offer to me.
<davexunit>so that will be cool. I'm willing to compromise, but I'm not willing to give it all up.
<davexunit>anyway, sorry if I've disappointed anyone for not sticking it out.
<davexunit>it was a tough decision to make, but I think I'll be happier this way, and I will learn about more things that will be applicable to Guix.