<codemac>anyone here know how to get better error messages than "source expression failed to match any pattern" ? I'm having trouble figuring out what I've done wrong, and this happens a lot while developing in guile
<lfam>codemac: You should ask in #guile. Sorry I can't help more.
<codemac>I know it means that some syntax can't be expanded or something, wish guile could print what part of the s-exp it couldn't match/expand
<zekerbauw>Hi all, i ended up with 2 GuixSD installations on my machine getting disk crypto working. One was installed from substitutes, and the other from source.
<zekerbauw>However, all the derivations, patch files, guile-builder files, etc. ended up in the /gnu/store/ of the substitute installation.
<zekerbauw>I would like to keep all of these because they are important to understand the origin of the packages on my system.
<zekerbauw>Is it bad to simply copy them into the /gnu/store/ of the GuixSD where they actually were compiled in?
<zekerbauw>I know /gnu/store is normally supposed to be read-only, but in this case the data copied in only came from Guix in the first place.
<zekerbauw>I want to run gix pull, and it would maybe take less time if there are derivations already built that i can copy back in
<jroh>anyone have any luck with setting up the guile-wm package, or getting startx going w/ a .xinitrc ?
<iyzsong>jroh: I did, but guile-wm is not useable for me. startx won't work now (I have some plan for it in my TODOs..)
<jroh>kk. any idea what other WMs than ratpoison and xfce work well atm?
<iyzsong>jroh: all should work, if it doesn't show in the slim menu, you can put it in ~/.xsession. I think openbox (non tiling) and i3 (ttiling) is good start for WMs, and Enlightenment is another choice.
<apa512>i'm new to guix and getting "bzip2: Compressed file ends unexpectedly;" while attempting a system reconfigure.
<codemac>Still stuck with gcc injecting libgcc_s.so deps randomly based on how go execs cgo
<codemac>A coworker has been helping me learn the compiler's implementation, so I may be able to patch things
<lfam>Wild. Do you know if Nix suffered the same problems?
<codemac>See - I haven't actually confirmed that they got cgo working
<codemac>I emailed their maintainer, but he didn't have much to say
<lfam>I use some Go software on NixOS so they did something. But I don't know how they did it. Is your latest try in the guix-pkgs repo on github? I could try to compare it to the Nix packaging and report back.
<codemac>I can check for you real quick, I'd appreciate the feedback
<jroh>codemac apa512 fwiw, I think I used --fallback to get around that error earlier.. but that meant waiting for the kernel to compile
<lfam>jroh: That indirectly answers my question about --fallback earlier. I didn't understand what it did. I interpreted it as falling back to building if substitutes weren't available, but it actually means fall back to building if substituting has an error.
<codemac>the best part about guix is knowing that no matter how disgusting the build process is for an application, if you can get it packaged, *everyone* can do the build. This always seemed silly/stressful with arch dev for me
<efraim>using debian I was taught about the horrors of compiling software myself, that with 20,000+ packages, if it wasn't in the repos you didn't need it.
<efraim>If you did really want it anyway, you should either figure out the whole .deb packaging thing, or run `sudo make checkinstall` instead of `sudo make install` to register it with dpkg/aptitude
<HeisenbergsDog>coming from fink/macosx, i like guix exactly for the same reason
<efraim>xd1le: I've looked at the debian new maintainers handbook several times, and compiling the software is the easy part, but I still have no real idea on the "best practices" for the debian folder, patches, building locally, keeping all the packaging stuff in a separate git repo, etc.
<xd1le>efraim: ah i see. i don't know anything about it hence why i asked.
<civodul>could you run "strace -f -o log guix environment foo --container ; echo $?" and send the output and file 'log' to email@example.com, as well as information about the kernel version and Guix commit?