*rekado runs “guix gc --verify=repair,contents” and waits
<zimoun>yeah, on the other hand thrombocytopenia means your blood clots hardly, right? Well, I agree with you with “little” exaggeration. :-)
<rekado>AFAIUI the blood clots are not due to thrombocytes doing their thing, but due to the immune system attacking thrombocytes and using them up in the process, leaving behind gobs of garbage that clogs up veins.
<rekado>(my bout of thrombocytopenia half a life-time ago was also due to an auto-immune response.)
<zimoun>I am running ssh remote guix archive --generate-key | guix archive --authorize but it returns «guix archive: error: mkdir : Permission non accordée». I am not have root acces to this remote machine. How can I exchange items?
<rekado>the acl is stored in /etc/guix/acl, and authorization writes to it.
<rekado>“guix archive --generate-key” also writes to /etc/guix
<rekado>perhaps you can overwrite the sysconfdir to write elsewhere?
<zimoun>ok, once the key exist on the remote machine, how do I transfer it?
<rekado>you only need the public key at /etc/guix/signing-key.pub; everyone should be able to read it.
<zimoun>so you mean ssh remote cat /etc/guix/signing-key.pub | sudo guix archive –authorize ?
<rekado>I’m now doing this to copy as many useful store items as possible: for p in /gnu/var/guix/profiles/per-user/*/*; do echo $(readlink -f $p); done | grep -v "/gnu/var" | xargs -n 10 guix copy --to=sl-bimsb-p-gxm1
<roelj>zimoun: It is very nice to know that "guix pull" preserves it. The reason I set the above mentioned environment variables was because I want to be able to "guix pull" rather than build-my-own every time.
<zimoun>roelj: it can be error prone too. :-) For instance sysconfdir is not mentioned in the manual and the location is not standard. So the usual “./configure --localstatedir=/var && make && ./pre-env-inst guix pull” leads something different as just “guix pull”. :-)
<rekado>roelj: I switched to “guix pull” for our cluster deployment a year or two ago.
<zimoun>Ouch! It is crazy all concepts Guix has, which are so familiar when one uses it daily. Then how hard it is to explain them… aside to keep the right level without too much details. civodul, about JRES, yeah 1h is nothing. ;-)
<zimoun>qnd for live demo, one really needs to cache all the commands which will be launched :-)
<civodul>zimoun: oh yes, live demos can easily go wrong
<civodul>when i do that during talks, i make sure the packages i'm going to refer to are in the store beforehand
<zimoun>yeah, I do that too. But, you have a question, you slightly tweak and boum! Heavy computations. :-) Some part are slow, we know. Other are just because doing The Right Thing is just costly. But people have never thought about it… and compare to APT, Conda & friend.
<zimoun>And it is the first time I really realize how far the usual scientific is far from the Scientific Method applied to computations. :-)