bug#75423: ansible package fails to build due to some tests failing on python-resolvelib package

2025-01-07 Thread Apoorv Singh
The ansible package fails to build due to some tests failing on python-resolvelib package, here are the logs, starting phase `wrap' find-files: /gnu/store/f05w6gxgi0g6aviarivji3glz7xi1skx-python-resolvelib-0.7.1/bin: No such file or directory find-files: /gnu/store/f05w6gxgi0g6aviarivji3glz7x

bug#75424: docker-compose up/down not working throwing error.

2025-01-07 Thread Apoorv Singh
I use docker-compose for my various projects and after some recent pulls it is not working, here is the error that I get,  docker-compose up -d Traceback (most recent call last): File "/gnu/store/7v8r5c2xf2g6l4k7dfvcxxhm1kfdm9b5-python-docker-5.0.3/lib/python3.10/site-packages/docker/api/cli

bug#75419: python-celery build failed: spurious linebreaks in tests

2025-01-07 Thread Dr. Arne Babenhauserheide
The build of python-celery fails because test TestBackendEcdsaCompatibility.test_public_key_to_pem[ECDSAECKey-CryptographyECKey] fails. The reason seems to be that linebreaks are inserted at different places than expected. End of the logfile /var/log/guix/drvs/fx/d67zlmgm6mh90pdc4db8j22l47r15l-py

bug#75090: Make 'guix pack -f docker' tarballs reproducible?

2025-01-07 Thread Ludovic Courtès
Hi Simon, Simon Josefsson skribis: > 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 betw

bug#74948: guix pack docker environment variable setting

2025-01-07 Thread Ludovic Courtès
Hi, Simon Josefsson skribis: > Would a new `guix pack --setenv HOME=/` parameter be useful? > > Such a parameter could be docker-specific and documented in > --help-docker-format. If other formats support setting environment > variables too, it could instead be a normal `guix pack` parameter. >

bug#63022: I dont can add distrobox repository in guix

2025-01-07 Thread jgart via Bug reports for GNU Guix
Hi, Closing this issue. Feel free to reopen if you have further questions about this topic. -- all the best, jgart

bug#68895: `guix repl` breaks Guile REPL features

2025-01-07 Thread 45mg
Adriel Dumas--Jondeau writes: > (guix-user)> ,use (guix scripts build) > (guix-user)> ,trace (guix-build "hello") ; doesn't output any trace for some > reason It looks like this isn't the only REPL command that doesn't work in `guix repl`. I haven't done anything close to a full investigation (

bug#75288: gnu: xfce4-session: xflock4 fails to run.

2025-01-07 Thread Ricardo Prudon
I am having the same issue. I tried fixing the issue by installing "glib:bin" manually, the error "gdbus" error message now goes away, but the program still shuts down quietly and does not lock the screen.

bug#54495: unexpected download after gc

2025-01-07 Thread David Elsing
Hello, David Elsing writes: > Presently, it is inconvenient to globally run guix gc at all for me, as > many (dependent) packages are deleted and substituted again when > rebuilding several profiles built with grafts. In the meantime, I learned about the '--gc-keep-outputs' and '--gc-keep-deriv

bug#74783:

2025-01-07 Thread Gábor Stefanik
Between 2.35 and 2.38, glibc added the following code to sys/mount.h: > #ifdef __has_include > # if __has_include ("linux/mount.h") > # include "linux/mount.h" > # endif > #endif This is then used to conditionally define structures that would be in linux/mount.h, in case linux/mount.h is either

bug#75392: “Failed to read private key” error with libssh 0.11.1

2025-01-07 Thread Ludovic Courtès
Hello, > It would seem that somehow libssh dismisses whatever gpg-agent tells it > and then goes on to read key files directly. Turns out the problem was sorta between keyboard and chair, but not just! Namely: 1. libssh 0.11.x no longer recognizes DSA keys (which is reasonable), and it w

bug#74455: gcc-toolchain and gfortran-toolchain conflict

2025-01-07 Thread Laurent Gatto
Hi Simon, Thank you for looking into this! > Well, the naive question: Does it make sense to have in the same profile > some C/C++ GCC toolchain at one version and some Fortran GCC toolchain > at another version? These are the versions I ended up with when installing the latest toolchains, and t