<lfam>Digit: Regarding hardening, you should find previous discussion in the guix-devel archives. In short, we want to start building C / C++ software with some hardening options that are set by default, but somebody really needs to lead the effort.
<wingo>i am not sure how those numbers will go in the future. on the one hand, native compilation will yield a 2-4X speed improvement in the interpreter (and later, the compiler, when it's compiled). on the other hand, there will be more compiler code.
<efraim>Its a bit wonky between really slow storage and smaller than x86_64 cache, cmake builds faster and with fewer test errors with 2 cores than with 4
<efraim>Most people will end up using distro provided binaries, so its probably not an issue
<efraim>to transfer store contents i want `guix archive --export * | ssh othermachine -q guix archive --import' ?
<efraim>i finally changed the guix-daemon on my aarch64 machine, --no-substitutes --no-build-hook (no guile-ssh installed) and --cores=3
<ArneBab>but going through the guix installation on a foreign system again: the only hard part is that Application setup comes so much later in the manual than the binary install. If the shorter binary install instructions included guix package -i glibc-utf8-locales, adding the GUIX_LOCPATH to the bashrc, and adding build users (essentially the complete minimal install), it would work more easily.
<civodul>ArneBab: "Binary Installation" has links to all these things, no?
<civodul>though i admit that it would be better with fewer manual steps
<civodul>ryanwatkins: i don't recall seeing that, could you paste it?
<ArneBab>it has one link — which I must admit I missed because it came after "this completes"
<civodul>efraim: you should try 'guix copy' for remote transfers
<ArneBab>root-level install still needs the Application setup, so adding step 8 which gives the commands for "Application setup for root" (and the link to there) could avoid that
<civodul>ArneBab: right, we could make "Application Setup" an 8th item in the list
<ArneBab>aside from that, the installation went smoothly
<civodul>this is some sort of social engineering: how can we make sure people will actually read this? ;-)
<civodul>oh sure, we'd happily include them along with the systemd and Upstart files
<jmd>civodul: My reply to your comment on bug 25995 seems to have lost it's context. The answer to your question is, that without it users cannot build Guix without guile-json installed.
<efraim>i have to get `guix package -A` working on the aarch64 board, then I can do `guix package -A | cut -f1 | sort -u | shuf | xargs guix build' to build random things
<wingo>i think it can make sense to make a "guix init" on foreign distros to install dynamically-scoped dependencies into a user profile and to suggest commands to add to the appropriate dot-files like bashrc
<wingo>it might print out a link to the manual too :)
<jmd>If I look here : http://hydra.gnu.org/build/1910273 it lists some "Failed build steps" If I click on the log for step 1 for example, there is no failure. Everything succeeded. That does this mean?
<thomasd>Is there a way to extract a patch that git will apply from the mailing list archives? (via web interface, or another interface?)
<jmd>thomasd: Without downloading that part of the archive, I can't think of a reliable method.
<thomasd>jmd: ah yes, I wasn't aware of the “download” link. thanks.
<efraim>depending on how its laid out, you might be able to `wget download | git am'
<determinator8899>I just wanted to install guixsd, but it seems that herd cow-store start doesn't work for me as I understand correctly everything I write in /gnu/store is written on my /mnt directory but this doesn't happen ?
<wingo>i think there is a chroot in there, could be wrong tho
<wingo>installation is tricky but i think if you follow all the steps to the letter it should work
<ArneBab>ng0: no, the gnunet one looks cleaner. The main difference is that mine is just a start and stop script which the user throws into local.d while the gnunet one is a full init file for /etc/init.d/
<determinator8899>wingo: chroot is not mentioned in the documentation but when I do chroot /mnt it fails to run the command '/gnu/store/something/bin/bash' no such file or directory this is strange.
<civodul>i don't see that because i have getcap in $PATH
<civodul>we should change torsocks to refer to getcap by absolute file name or somethig
<thomassgn>ah, nice. where does getcap live? I mean package?
<lfam>civodul: Is it a good idea to "Cancel all scheduled builds" before starting a new evaluation? I don't want Hydra to try building anything that depends on mesa since mesa has changed since the last evaluation