<apteryx>error reporting is still pretty much an area needing polishing in that area of Guix, so I wouldn't go believing everything it spits out. Better try an actual config that is supposed to work (and complete) at first.
<leoprikler>okay, now try adding (use-service-modules <whatever>) to that config.scm
<g_bor>What I found is that the 408 is intentionally not sent back to the client, so that looks like expected.
<leoprikler>sneek later tell ScaredySquirrel: I've experienced your -6 error before, but IIRC it was not Guix' fault. I think I forgot to `herd start cow-store` or my hard drive was already dying. Not sure which of those it was.
<sneek>ng0_, ArneBab_ says: however this many times slower might be changed by 2.9
<sneek>ng0_, ArneBab_ says: as far as I understood, (read) got much slower with 2.0 — so much slower that some people couldn’t work with it.
<sneek>ng0_, ArneBab_ says: in addition some non-documented tricks used by lilypond stopped to work on 2.0 and some errors appeared multiple times, which cause frustration that led to reduced investment into getting to 2.0. My opinion is that this problem was caused by mistakes on Guiles side (you shouldn’t change things that break the one tool using your language that achieved total domination in its domain). But that’s done now, and I hope it
***ng0_ is now known as ng0
<efraim>sneek! Don't leave us hanging! Tell us Arne's hopes and dreams!
<zimoun>rockandska: ah interesting! So yes please send an update to the mailing list :-)
<rockandska>zimoun: i just realized too, that during my staps, it is always the old daemon who is running since i don't restart between staps, so i take a look if restart it change something too and will upgrade tests cases on ML
<rockandska>didn't try to reproduce this behavior on a VM too and would be interesting if what i see is global or directly related to docker
<nckx>anadon: Could you paste the error? Also, please just use ‘gcc’ instead of ‘C++17+’ and try again. Something might depend on that name. When I said I sometime use a different string than the exact package name, I didn't mean like this — some code may depend on a specific key.
<lispmacs>hi, I've got this problem where, in GnuCash, the Enter key is not doing what it is documented to do (it works fine in Debian). It is supposed to move to next split line in transaction, but it does nothing. I am wondering if this is happening for me only
<anadon>lispmacs I think you're in the wrong channel. I think you want either a channel specific to GnuCash, or Gnu in general. In is for Guix.
<rockandska>test with guix -f docker bash for example, it includes some dependencies not needed in final and the result is ~80mb compress vs 5Mb for the bash docker image (based on alpine)
<Parra>Ludo said this: guix system docker-image config.scm
<nckx>anadon: Does happen when running any Guix-installed software, or only when you run ‘guix’ itself? Maybe the daemon needs to updated, or the Environment= line in /etc/systemd/system/guix-system.service is off.
<nckx>rockandska: That is correct. But: I think these two export commands only make sense on other distributions, and shouldn't we explicitly ask users to add both lines to their ~/.bash_whatever instead?
<nckx>I haven't read the whole chapter. Maybe that's suggested elsewhere.
<nckx>rockandska: These lines can't (simply) be added to ~/.config/guix/current/etc/profile for reasons, but I agree that they should be saved to ~/.bash_profile or similar.
<rockandska>nckx: yeah, but since for package we source .guix_profile/etc/profile, i foudn more elegant to only source .config/guix/current/etc/profile, and in case, someday, guix need other env var to be set/update, the user will not have to be awore of that addition if all of them are in .config/guix/current/etc/profile
<rockandska>nckx: i don't get why INFOPATH can't be set as PATH in .config/guix/current/etc/profile since it only expand it for guix doc, but since i'm not a guix expert i will trust you ^^
<nckx>The short story is that ~/.config/guix/current/etc/profile isn't generated in a way that allows adding random lines like that 🙂 Doing so would be slightly more convenient for users *in this specific case*, but it would make profiles *in general* less pure. I think…
<nckx>I think, instead, the docs should clearly explain to users if and how to create a custom ~/.bash_profile or ~/.bashrc on other distributions. Of course I can't do that.
<nckx>That clearly separates the things that make this a special case from the general code that creates ~/.config/guix/current/etc/profile, and gives the user a clearly supported place to make their own customisations.
<rockandska>Parra: uncompress your image size is 1.17GB where the one i just build seems to be 574MB for the latest guix pull
<nckx>sneek: later tell Minall: Is copying everything to /mnt a deal breaker? Running grub-install --boot-directory /mnt/boot --bootloader-id=Guix --efi-directory /mnt/boot/efi might work fine, it also might result in an unbootable system if not all configuration was installed…
<nckx>Setting it to root is fine, setting it to your user's is fine if you run guix-daemon from your user profile (I used to). What matters is that GUIX_LOCPATH is set in the daemon environment, setting it on the command line will not do anything.
<nckx>Franciman: They are two equal Guix users; ‘root’ is not global.
<g_bor[m]>Mrtn: the main thing here, is that the file pointed to by guix profile is changed. The second line sources the file.
<Mrtn[m]1>nckx: Which locale are you using? I have a suspicion it might be related to that ....
<Mrtn[m]1>g_bor: Oh ok ... so it appears each time the profile changes! That makes sense.
<nckx>Hum, I got dragged into looking at the code (I wasn't going to get dragged into looking at the code 😛), and I don't see a check. Now I'm starting to doubt my own memory. Surely I can't have got hint-blind by running guix too much…