<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
*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 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.
<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.