Konrad Hinsen writes:
> I found a simpler one, using a more recent Guix commit:
>
>guix time-machine --commit=7b0863f07a113caef26fea13909bd97d250b629e \
>-- pack -S /etc/ssl=etc/ssl --format=squashfs bash nss-certs
>
> Unfortunately, I have no idea how to debug this, as the image is
> con
Konrad Hinsen writes:
> Here is my most recent experiment:
I found a simpler one, using a more recent Guix commit:
guix time-machine --commit=7b0863f07a113caef26fea13909bd97d250b629e \
-- pack -S /etc/ssl=etc/ssl --format=squashfs bash nss-certs
Unfortunately, I have no idea how to debug
Hi Tomas,
Thanks for your reply!
> I think the relevant part is whether some certificate package is installed
> (via
> propagated inputs) or not. If I explicitly add nss-certs to the command
> above,
> it starts to work:
Sorry, I forgot to add that I always have nss-certs among my packages
wh
On 2024-01-29 10:30:21 +0100, Konrad Hinsen wrote:
> Dear Guix experts,
>
> I am seeing inconsistent behavior with the creation of symbolic links
> in containers and exports, and I wonder whether this is a bug or missing
> documentation.
>
> According to the documentation, there are no constraints
Dear Guix experts,
I am seeing inconsistent behavior with the creation of symbolic links
in containers and exports, and I wonder whether this is a bug or missing
documentation.
According to the documentation, there are no constraints on what I can
link to. In practice, some symbolic link requests
