Hi, Lars-Dominik Braun <l...@6xq.net> skribis:
> Alright, let’s see. The command I have been using is > > guix pack -L . -C 'zstd' -f docker -S /bin=bin python-jupyterlab bash > coreutils findutils > > with . being a checkout of guix-science (same applies to `guix > time-machine` though). The first time it’ll fail, but the second time > it succeeds. Running `guix gc` makes it fail again the first time. > > The docker-pack.tar.zst.drv used for the first build is > different from the second one (different hash prefix). For me it’s > /gnu/store/r096cm3np7hbdn853ih35h1a5l39in4s-python-jupyterlab-bash-coreutils-docker-pack.tar.zst.drv > the first time and > /gnu/store/dywspxjshfjhc07i17hkcyrlq8kn7m07-python-jupyterlab-bash-coreutils-docker-pack.tar.zst.drv > the second time. YMMV. Wait, you run the same command twice and it leads a different .drv? The expected behavior is that the .drv is always the same: --8<---------------cut here---------------start------------->8--- $ guix pack -C zstd -f docker bash coreutils findutils -d /gnu/store/gqq2802zy9r6xgb7l5p5smxkwh886x7b-bash-coreutils-findutils-docker-pack.tar.zst.drv $ guix pack -C zstd -f docker bash coreutils findutils -d /gnu/store/gqq2802zy9r6xgb7l5p5smxkwh886x7b-bash-coreutils-findutils-docker-pack.tar.zst.drv $ guix pack -C zstd -f docker bash coreutils findutils -d /gnu/store/gqq2802zy9r6xgb7l5p5smxkwh886x7b-bash-coreutils-findutils-docker-pack.tar.zst.drv $ guix pack -L /data/src/guix-science -C zstd -f docker python-jupyterlab bash coreutils findutils -d --no-grafts /gnu/store/xzp0qrd54sglhrggwn8myl7fd0mfhwln-python-jupyterlab-bash-coreutils-docker-pack.tar.zst.drv $ guix pack -L /data/src/guix-science -C zstd -f docker python-jupyterlab bash coreutils findutils -d --no-grafts /gnu/store/xzp0qrd54sglhrggwn8myl7fd0mfhwln-python-jupyterlab-bash-coreutils-docker-pack.tar.zst.drv $ guix pack -L /data/src/guix-science -C zstd -f docker python-jupyterlab bash coreutils findutils -d --no-grafts /gnu/store/xzp0qrd54sglhrggwn8myl7fd0mfhwln-python-jupyterlab-bash-coreutils-docker-pack.tar.zst.drv --8<---------------cut here---------------end--------------->8--- > Looking at ca-certificate-bundle.drv, the first one lacks any form of > glibc-utf8-locales as an input (neither in the .drv, nor via `guix gc > --references <.drv> | grep glibc-`), so it’s clear it must fail. I’m > not quite sure why though, since the actual builder still has a reference > to the locales and sets LOCPATH. So I’m a little puzzled. Could you send the contents of this “broken” ca-certificate-bundle.drv as well as the ca-certificate-bundle-builder it refers to? Thanks, Ludo’.
