***dysinger_ is now known as dysinger
<CaptainLex>Success, everyone! I chown'd /usr/local/var to captain, reinstalled, and now it's installed! <CaptainLex>Ah, I suppose I'd add /usr/local/var/nix/profiles/per-user/captain/bin to my PATH variable? <Steap>CaptainLex: it would be simpler to add ~/.guix-profile/bin to your PATH :) <Steap>it's a symlink to /path/to/nix/.../bin <Steap>still, it's weird that you cant compile gcc <Steap>hopefully you could use the substituter <Steap>Now, how about you package sl ? :p <CaptainLex>Unfortunately I have a more pressing engagement on this day <CaptainLex>I might be able to take that whack Sunday morning <civodul>CaptainLex: when you have time, can you try to build without going through the substituter? <civodul>like "guix build hello --no-substitute" <civodul>and if hello is already there, run "guix gc --delete /nix/store/...-hello..." <Steap>couldn't he run "guix package -r hello" ? <civodul>that removes it from the profile, not from the store <Steap>would be quite bad if the linker failed for al lpackages indeed <civodul>so if it's in the profile, you need "guix package -r", then remove the previous generations of the profile, then "guix gc --delete xxx" <Steap>I hope the problem is just gcc-related <civodul>i can't see how that can happen in chroot builds <civodul>we've seen all sorts of bugs, but not that kind :-) <CaptainLex>So sometimes after running an install, "XXX operations" ends up being printed in the input line, instead of before it <civodul>CaptainLex: "XXX operations" is printed by the daemon <civodul>i usually run the daemon in a different terminal than the clients <civodul>so that i'm not disturbed by those messages