*rekado_ just added a handler for /build/<id>/details to Cuirass
***jje_ is now known as jje
<jgibbons[m]>I tried `guix pack --system=armhf-linux -RR hello` for armhf, aarch64, and mips64el from an x86_64 guixsd install, and they all have failed at proot. I think the problem is with qemu. Does anyone here get similar results or come to a different conclusion?
<jgibbons[m]>Also, since all the tests have nonsense names, isn't the proot test suite nonfree?
<jgibbons[m]>I'm confused because I'm being told I posted twice, so i redacted and now it says I didn't post at all...
<jgibbons[m]>Since the proot test suite has nonsense names, isn't it obfuscated nonfree software?
<apteryx>hello; English grammar question for a Guix package synopsis: would you say "Emacs interface _to_ GNU Go" or "Emacs interface _for_ GNU Go" ?
<nckx>Also, unrelated to your error: GitHub-auto-generated /archive/ tarballs can be regenerated once in a rare while, changing the hash. You should use git-fetch with (commit (string-append "version_" version)) instead.
***nckx changes topic to 'GNU Guix | 1.0.1 is out! get it at https://gnu.org/s/guix/ | videos: https://gnu.org/s/guix/blog/tags/talks/ | bugs and patches: https://issues.guix.gnu.org/ | paste: https://paste.debian.net | Guix in high-performance computing: https://hpc.guixsd.org | This channel is logged: https://bayfront.guixsd.org/.well-known/logs/'
***ChanServ sets mode: -o nckx
***ChanServ sets mode: +o nckx
***nckx changes topic to 'GNU Guix | 1.0.1 is out! get it at https://guix.gnu.org | videos: https://guix.gnu.org/blog/tags/talks/ | bugs and patches: https://issues.guix.gnu.org | paste: https://paste.debian.net | Guix in high-performance computing: https://hpc.guixsd.org | This channel is logged: https://bayfront.guixsd.org/.well-known/logs/'
<nckx>rekado_: Now all we need is hpc.guix.gnu.org and saneirclogs.guix.gnu.org.
***ChanServ sets mode: -o nckx
<nckx>How is general CSS added to Cuirass? All I see is a (presumably stock) bootstrap.css and element-specific style= tweaks.
*nckx hopes their first commit didn't break anything.
<A0x1E>Hello, dear developers of the GuixSD Project! Please, tell why need chain-compilation at the rust package? After 3 days active building, I'm wanna get his to some version in chain, but it's not interactive. I mean, build process not save any version of a package. Thanks!
<vagrantc>A0x1E: have you enabled substitutes? otherwise it will build everything from source, which takes quite a long time
<sneek_>Welcome back vagrantc, you have 1 message.
<sneek_>vagrantc, efraim says: did you install Guix System on your firefly? Or Debian? I'm looking to reflash mine and wanted some pointers
<vagrantc>efraim: i've got some firefly-rk3288 and firefly-rk3399 running Debian; haven't tried Guix System on them
<vagrantc>sneek_: later tell efraim i've got some firefly-rk3288 and firefly-rk3399 running Debian; haven't tried Guix System on them
<vagrantc>the main issue is that if you flash something to eMMC, it defaults to loading the firmware from that, so if you flash something that works well enough to load, but not well enough to actually boot, you have to short the eMMC pads ... there's no jumper or switch or anything
*vagrantc prefers things that default to booting from removable media for this reason
<vagrantc>efraim: so no idea if the firmware that ships with it can readily boot guix or not ... never tried it :)
<efraim>So I'll flash something safe and work on the pine64 booting guix system afterward then
<vagrantc>i've tested pine64+ with guix ... recent kernel versions should be pretty stable
<jaccarmac>Hey there, I submitted a patch series a couple weeks back for the first time and it never got any responses. Wondering what the correct etiquette is: Resubmit the series double checking my format, send another message to the same debbug, or just let it die?
<nckx>jaccarmac: Anything but the latter! A friendly ping after a week or two is fine.
<rekado_>jaccarmac: can you tell us the number you got from the patch tracker?
<nckx>rekado_: Do I want to know how this was done? Or should I just look at the pretty hypertexts and not ask questions.
<bavier>dutchie: builds for me know, with a simple fix: the 'sic' in the 'disable-failing-tests' phase points to a typo in 'jvascript'. The typo was fixed upstream, and if you fix it in our regex, tests pass! :)