<eacces>first week into this guix adventure, going pretty smoothly thus far. docs have been commendably good
<sturm>Is there anything like `guix build --target=mips64el-linux-gnu [package]` that allows you to build the entire OS? I'm picturing being able `guix system disk-image --target=...` to build an image for, say, a BeagleBone ARM board.
<sturm>(but `guix system` doesn't have a `--target` option)
<reepca>upgrading vlc after a recent "guix pull" fails due to the package trying to download http://www.live555.com/liveMedia/public/live.2017.05.24.tar.gz when the site is only offering live.2017.06.04.tar.gz under that particular directory. I suspect it has less to do with the actual guix pull and more to do with the site maintainers deleting or moving that release. Anyone else have troubles trying to install livemedia-utils or anything that
<snape>As a quickfix, I'll update the package version, but we definitely need to find a solution
<snape>(I think Hydra should have cached the link, it's pretty much unlucky it didn't have time for it)
<roelj>I get this error: "ERROR: no code for module (guix build utils)", when installing a package. (I can guix build <package> it just fine, but guix package -i <package> crashes with the error). What can I do about this?
<jlicht>catonano: Good to know you got something to work with freexl :-)!
<catonano>jlicht: thanks for your concern. It's appreciated. I actually adopted your suggestion, that's all. I couldn't properly read the thread that you indicated to me. I cold read it with new eyes only after giving up
<jlicht>catonano: sometimes you need to take a step back to properly solve a problem ;-)
<jsierles>is there a record of previous profiles used before running 'guix package -i'?
<jsierles>better question - if i use a manifest file with 'guix package', will i always get the same result, even if guix has been updated with 'guix pull'?
<rekado_>eacces: you get this when you’ve changed the code.
<rekado_>it’s a bit weird. I would build mercurial first and then run “--check”
<eacces>hmm, ok, thanks for the advice, will do that.
<sturm>Is it possible to cross compile a disk image? I'm thinking of trying to get GuixSD running on a BeagleBone Black (ARM). Tried `guix system disk-image --system=armhf-linux` but after downloading a whole lot of sources, it said `guix system: error: build failed: a 'armhf-linux' is required to build ...-guile-bootstrap-2.0.drv, but I am 'x86_64-linux'`
<rekado_>sturm: I don’t think GuixSD is available for armhf yet.
<sturm>rekado_: thanks, that would explain it then :)
<davexunit>it will be a glorious day when it is available...
<jsierles>is there a way to generate a docker image with 'guix pack -f docker' that will just mount a global /gnu/store? i guess it doesn't need packages, but needs to at least work to boot up in docker
<janneke>how do i know where `git pull' will bring me / has brought me? i'd like to create alignment between `guix pull' and `running guix from git' setups
<efraim>perhaps ./pre-inst-env guix --version will give you something to work with
<janneke>efraim: perhaps...? i'm just wondering how i can find out which branch/commit guix-latest.tar.gz is built from
<ng0>the memory leak we have, is there a formal bug open for this, or was it jus temails so far? A friend just ran into this and there was nothing obvious in the bug list, I just told him before about this issue that might appear
<janneke>sneek: later tell OriansJ: i have removed 45/51 lambda's from mes's .o output -- hex3 now passes 80% of the test suite. I also have experimental hex2 output. Problem with hex2 is i need several flavours of labels: function-local goto labels, absolute address labels, relative address labels (and 1, 2, 4 bit labels -- that bit is easy and resolved). Usually assembly handles this, but with hex...I could do with some help here going