<angelic_sedition>I'm having trouble getting guixsd installed in virtualbox. "guix system init..." says that it completes successfully, but when I reboot I get a kernel panic and just before it 'ERROR: In procedure state: No such file or directory: "/etc/static/localtime"'. Any ideas?
<angelic_sedition>Also, after "guix system init /mnt/etc/config.scm /mnt", config.scm is still the only file in /mnt/etc. Should there be others?
<jrandall>I'm struggling to get guix working from behind a firewall that requires outbound http/https traffic to go via an http proxy. I've spent the past few days developing fixes that make the core of guix work with a proxy (see patches at http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20402), but now I'm stuck because the bootstrap guile is only version 2.0.9, and 2.0.10 or greater is required for proxy support.
<jrandall>Can anyone advise me on how I can move to a newer version of the bootstrap guile?
<bavier>jrandall: have a look in gnu/packages/bootstrap.scm
<jrandall>I was just poking around in there - I see that for armhf it is already using 2.0.11
<mark_weaver>jrandall: if you replace the bootstrap guile, then you'll need to build *every* package from source code, starting with a bootstrap process not unlike that described in Cross [GNU/]Linux From Scratch.
<mark_weaver>jrandall: do you want to be building everything yourself, or do you want to use binaries built by our build farm?
<mark_weaver>I'm afraid I don't have a ready answer for you right now.
<mark_weaver>jrandall: thanks for your patience, and for working on improving it!
<jrandall>mark_weaver: no problem - I suspect not too many people these days are still stuck behind corporate proxy servers (some of our machines are now freed from it, but this particular set is still firmly trapped)
<jrandall>In order to use the pre-built binaries from hydra, do we need to keep the default store path as /gnu/store ?
<jrandall>mark_weaver: only on some of the machines - I was hoping we could run it as a non-root daemon user who owns the store on those machines
<jrandall>we wouldn't be able to do that on some of the machines, at least not without going through a heavy change request process
<mark_weaver>I believe there may be issues with running guix-daemon as a non-root user. in that case it is unable to create a chroot or isolated build environment, and so the builds may pick up things from the host environment and many things may break.
<jrandall>an alternative might be for us to provide our users with the guix environment inside containers
<jrandall>(inside of which we can operate as root)