<OriansJ>CharlieBrown: you know if you wanted, you could do a Live conversion. Hot-swapping of the kernel might be an issue though
<CharlieBrown>OriansJ: I also haven't tested to see if my whole workflow works.
<CharlieBrown>I'd probably have to rely on ADFENO's recipe for GNU Ring, to use SIP.
<OriansJ>CharlieBrown: well, simply remove programs as you add them in guix; until you are done or until you reach a wall
<marusich>Hey all. Has anyone ever experienced a problem in GuixSD where the screen goes black, the HDD light goes solid (as if tons of IO is occurring), and a kernel Oops appears in the /var/log/messages?
<marusich>Anecdotally, I have experiened this issue a few times in the past few months - I don't know if the "Oops" is actually related, but I noticed it yesterday when the problem occurred again.
<marusich>The Oops occurred along with a "BUG: unable to handle kernel NULL pointer dereference at (null)". I think this happened wihle I was using Guix to build things.
<numerobis>Hi! I saw earlier this week that guix required quite a lot of RAM for 'guix pull'. I'm thinking of ordering a VPS, and was wondering whether there was a recommended amount of RAM? Would 2GB be enough? Thanks!
<m-o>hi numerobis, i recently had issues with a machine with 2G building guix. Sadly i think you need more, possibly 3-4G min.
<brendyn>numerobis: ng0 said he did it with 512GiB ram + 6GiB swap.
<nee`>I remember that `guix pull` comile times were a much shorter with guile 2.0 which did a lot less analysis and optimization of the code it compiled than 2.2. I don't know the interal workings of the guile compiler, but I guess it's not possible to simply add an argument and save time by doing less optimizations?
<mistnim>m-o, ok I feared doing the install as user as well would start downloading everything again
<nee`>m-o: It's annoying that this is not part of the binary-installation guide. I know no case where you wouldn't want to setup locales, and everyone is always confused by that 'missing locale' error message.
<nee`>Would it be a good idea to change the unpack phase so it removes __MACOSX directories after running unzip? My current workaround is to switch to the zipbomb mode and do a manual chdir, but these zips aren't zipbombs they only have .
<civodul>clacke[m]: dunno, i think it's a graft somewhere
<civodul>nee`: to me that's the definition of a zipbomb, no? :-)
<nee`>I would think that on a zipbomb you are already in the correct build directory. Everything is in root and it's missing a wrapping directory. Here we have the wrapping directory, but OSX also adds it's metadata garbage.
<nee`>It also depends on if the developer who made the zip created it on a mac.
<ng0>hey! we had someone in our community running GuixSD on one of the Hetzner dedicated servers, right?
<efraim>building subversion wouldn't be so bad if the tests were run in parallel