<rvgn>civodul I wanted to ask you this for long time. I saw that Guix was written in Guile and C++. When I was reading GNU Coding Standards, it seemed more or less similar to Python Coding Standards. So any ideas of porting Guix to Guile and Python instead of Guile and C++? Just a thought.
<jonsger>rvgn: only the daemon itself is written in C++, as it was forked from NixOS. But there is an attempt to rewrite the daemon in Guile. Then Guix will be Guile "only"...
<rekado>I used that branch for a few weeks before.
<rekado>the only problems I had were due to state such as notifications.
<rekado>is there a paredit command to “spill” the contents of an expression one level up?
<rekado>there’s paredit-raise-sexp, but it’s only for one expression (or for N); I’d like this to be automatic.
<rekado>e.g. for all of the contents of a now obsolete let expression
<pinoaffe>btw, setting up guixsd by booting the livedvd in a vm and mounting the actual hardware worked, I'll just have to set up a bootloader myself, but I didn't expect that to work off the bat anyhow
<rekado>civodul: AFAIU the resolution is to be set by the guest operating system.
<mbakke>lfam: Sounds like the failure is still indeterministic, no?
<lfam>mbakke: Depends on what state you account for ;)
<lfam>Previously, it *always* failed for me, so I had stayed on Shepherd 0.3.0, where it still worked. In the past week or so, that workaround stopped working, so I tried updating to Shepherd 0.5.0, but it was still failing.
<lfam>So, I reinstalled Guix. Only after I reconfigured to the latest did it work, and it's worked ~5 times in a row, which is pretty good
<lfam>For me, sshd either starts or it doesn't. Since I filed the bug it has never been inconsistent
<lfam>I think there must be some state not accounted for by Guix
<lfam>Probably related to changes made in the Guix system since I initially installed so long ago
<lfam>Maybe I should have tried deleting all the files associated with OpenSSH and avoided reinstalling, but oh well
<civodul>i mean for hplip-minimal, it seems that we could keep only lib/cups and none of the hp-* tools, no?
<nckx>civodul: They work, if that's what you mean. There are things that only the tools can do (like find out how much ink is in that overpriced little black box, and *I think* I needed hp-something to align my print heads once).
<nckx>If you mean whether standard CUPS features work without them, I'm pretty sure they do.
*nckx is AFP or would have more useful things to say.
<nckx>I'd say it's worth the bet to remove them from -minimal.
<katco>i don't get a lot of chances to hack on guix, so everytime i sit down to do so i realize i've forgotten a bunch of things. i wanted a check on my workflow. i've just created a new local branch with an aim to upgrade go to 1.12.1. i did a `make clean && ./bootstrap && ./configure --localstatedir=/var && make check`. then i do `guix environment guix`. when i ran that last command it kicked off a couple-hour (and counting) process. surely
<katco>there must be an easier way to make changes to packages and test them locally?