bug#31785: Multiple client 'build-paths' RPCs can lead to daemon deadlock

Hey Reepca, Reepca Russelstein skribis: > Here is the reproducer: Brilliant! It works wonderfully well. I moved it to its own file to limit interference with others—plus it’s one of our oldest bugs so it deserves it. ;-) > P.S: If in attempting to turn this into a proper test, you try using

bug#75134: Issue with guix pull

Hi Eric. 8 GiB of RAM must be enough, since guix pull can run on 32-bit i686-linux. Another idea would be to pull on one core guix pull --cores=1 or generally to enable more debug output like guix pull --debug=4 I remember how someone used Guix on Ubuntu in a UTM virtual machine on a Macbook

bug#75175: Request for merging "libgcrypt-gpg-update" branch

Oops, this should have gone to guix-patches. Closing!

bug#63158: packages.guix.gnu.org occasionally wrecks havoc

Oh, I didn't notice this report until today, sorry. A related issue has been reported upstream to Artanis. See https://gitlab.com/hardenedlinux/artanis/-/issues/122. OpenPGP_0x0AB0D067012F08C3.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature

bug#75175: Request for merging "libgcrypt-gpg-update" branch

Hello, I’d like to merge the ‘libgcrypt-gpg-update’ branch. It is partially built at for x86_64-linux and i686-linux (partially only because that’s via the “-full-upgrade” jobs, which include additional upgrades). It’s fairly trivial and safe but

bug#75157: Grafting inconsistency with multiple outputs is causing problems

Hello FLorian, I think you are experiencing a different (related) issue because the problem I seems to vanish by linking to the glib that is used by g-golf instead (the --no-grafts options ensures that only one glib is in my guix shell) On 29.12.24 01:24, pelzflorian (Florian Pelz) wrote: