Ludovic Courtès skribis:
> The ‘static-networking’ service can remain in ‘starting’ state forever
> when it specifies a nonexistent NIC.
>
> This can be reproduced by running a system such as hydra/bayfront.scm
> (in maintenance.git) in ‘guix system vm’: shepherd will wait for
> ‘networking’ to s
So I create a container like this:
guix shell -C -F pango coreutils
Then in that container I do:
ls /lib
ls /lib64
The output is pretty long so I'd rather not send the entire thing, but
the issue is that it doesn't contain libpangocairo-1.0.so.0
When I do guix locate libpangocairo-1.0.so.0 I get:
Hi,
building ruby-puma fails:
Errors & Failures:
1) Failure:
TestPumaServerSSLWithCertPemAndKeyPem#test_server_ssl_with_cert_pem_and_key_pem
[/tmp/g
uix-build-ruby-puma-6.3.0.drv-0/source/test/test_puma_server_ssl.rb:543]:
Expected #peeraddr=127.0.0.1:33
445 state=error: certificate verify f
Hi
I am creating docker archives using:
guix pack guix bash-minimal coreutils-minimal net-base --save-provenance -S
/bin=bin -S /share=share -f docker --image-tag=guix --max-layers=8 --verbosity=2
To my surprise the output was not reproducible between re-runs.
The reason is because of the time
I don't remember if I closed this but I've updated the mrustc snapshot
and now parallel builds are supported by default, on all architectures.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or re
Hi!
I'm running the following commands on a arm64 GitLab shared runner node:
export LC_ALL=C.UTF-8
apt-get update
apt-get install -y guix podman ca-certificates
(guix-daemon --disable-chroot --build-users-group=_guixbuild &
guix pull --url=https://gitlab.com/debdistutils/guix/mirror.git \
|| (ls
