<rekado_>civodul: the module-import derivation differs in which popen.scm they use. The only difference here is an embedded reference to bash-minimal.
<rekado_>On one machine this reference is "/gnu/store/mm0zclrzj3y7rj74hzyd0f224xly04fh-bash-minimal-4.4.12/bin/bash"
<rekado_>one the other it is "/gnu/store/icz3hd36aqpjz5slyp4hhr8wsfbgiml1-bash-minimal-4.4.12/bin/bash"
<rekado_>I would like to note that my workstation has both of these variants of bash-minimal
<rekado_>the same is true for the other machine whose derivations I’m comparing.
<rekado_>I have to admit that I’m not clear on where that bash-minimal comes from. When I build bash-minimal on both of these machines I get /gnu/store/v1hqynfc538v3gdq5fmr15y1bk939f5k-bash-minimal-4.4.12, which is different from either of these references.
<rekado_>it looks like they ended up with different guile variants from which to pick the popen.scm source file.
<civodul>/gnu/store/mm0zclrzj3y7rj74hzyd0f224xly04fh-bash-minimal-4.4.12 derives from /gnu/store/s3vbai7lawhb2nn73gg2063ilgsvvdyk-bash-minimal-4.4.12.drv which was built from guile-2.0.14 (bootstrap guile)
<civodul>ooh, not bootstrap guile actually, but really firstname.lastname@example.org, which we use for grafts
<civodul>right, /gnu/store/mm0zclrzj3y7rj74hzyd0f224xly04fh-bash-minimal-4.4.12 is a graft
<mbakke>I wonder if Guix can somehow detect when the NSS compatibility layer is used and fail gracefully, instead of giving these "the guixbuilder group does not exist" messages.
<jlicht>What is "icu" and would we want to use the "system" variant of this when building packages? (Specifically, Nodejs bundles an icu dependency, but can be built a `with-intl` flag to point to a systemwide installation)
<bavier`>jlicht: we generally prefer using system packages where possible
<mbakke>jlicht: You'll find ICU in (gnu packages icu4c). It stands for Internationalization Components for Unicode IIRC.
<thorwil>is there a way to chroot into a guix sd installtion and have a fully functional shell?
<jlicht>thanks bavier`, mbakke :-). I am finally making some time to properly delete all bundled cruft from nodejs source packages and this was one of the things that I missed earlier. (Already from 30M to 12M!)
<thorwil>mbakke: `chroot /mnt/guixsd /var/guix/profiles/system/profile/bin/bash` does lead to a shell with no commands available. i can't figure out how to that bind-mount
<thorwil>due to fun like: mount: mount point run/current-system is a symbolic link to nowhere
<mbakke>thorwil: Try to `mount -o bind /mnt/guixsd/var/guix/profiles/system/profile /mnt/guixsd/run/current-system`. Then `chroot /mnt/guixsd /run/current-system/profile/bin/bash` and `source /etc/profile`.
<mbakke>I have never tried chrooting into a GuixSD, but it would be good to have instructions in the manual.
<civodul>mbakke: detecting a faulty nsswitch.conf is hard because this is all within libc
<mbakke>Oh wait, /run/current-system is a symlink to the store.
<thorwil>mbakke: yes, "is a symbolic link to nowhere" again
<mbakke>thorwil: You may get away without bind mounting, and instead just `chroot /mnt/guixsd /run/current-system/profile/bin/bash`, and then sourcing `/etc/profile`.
<thorwil>mbakke: "mount point /media/ssd-alt-system/run/current-system/profile/bin/bash does not exist"
<thorwil>resolving that symlink one level doesn't suffice
<thorwil>sudo mount /media/ssd-alt-system /media/ssd-alt-system/gnu/store/afhf38fwp0clqiv6mv672xmdjp7raici-profile/bin/bash => mount: mount point /media/ssd-alt-system/gnu/store/afhf38fwp0clqiv6mv672xmdjp7raici-profile/bin/bash is a symbolic link to nowhere
<mbakke>thorwil: What do you get if you try to `chroot /mnt/guixsd /run/current-system/profile/bin/bash` ?
<jonsger[m]>civodul: we did buildpacks at work for cloudfoundry. I'm not really sure about the detail but it contains binaries. You could then put your app (ruby based for example) somehow in it and it runs :P
<thorwil>i thought the second path for chroot should be from the point of view of the outer system, too!?
<thorwil>there's a "guile: warning: failed to install locale", though, which i think didn't happen in the "real thing"
<thorwil>what would be a good, quick test for potential issues here?
<mbakke>thorwil: You could try to run `guix-daemon`, and installing something to a profile.
<mbakke>Would you be willing to post a roundup about chrooting into a GuixSD system on email@example.com, or even better add instructions to the manual? :)
<thorwil>mbakke: yes to the first. head to full to attempt the later. thank you!
<mbakke>thorwil: Thank *you* for being so brave ;)
<mbakke>civodul: Is it possible to cancel a Hydra evaluation? The Meson fixes will invalidate most substitutes, and there are still 1300 builds in the queue.
<mbakke>I'll update bluez, mesa and friends as well, since they "only" add ~300 more rebuilds.
<thorwil>mbakke: `su` to a user, `guix` not found. another `source /etc/profile`. than `guix package -i emacs-bash-completion` failed with "guix package: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused"
<mbakke>thorwil: You'll probably need to start the daemon manually first.