bug#63009: /profile/bin missing from PATH for ssh commands
Ludovic Courtès writes: Hello, > This patch had fallen through the cracks… Ah, no problem. > Janneke Nieuwenhuizen skribis: > >>>From 2ac41477dad5699b748acfc72d4e91e0e14fa16a Mon Sep 17 00:00:00 2001 >> From: Janneke Nieuwenhuizen >> Date: Sat, 22 Apr 2023 09:58:48 +0200 >> Subject: [PATCH] gnu: system: Cater for Guix Home in PATH. >> >> * gnu/system.scm (operating-system-etc-service): Also add a user's >> /profile/bin directory to PATH, before /bin. > > LGTM, thanks! Great, pushed to master as ff2e22d1e122eb5b85fd85f8e922e6e8cfb0ee7b Janneke -- Janneke Nieuwenhuizen | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
bug#63427: gdk-pixbuf unable to recognize image formats (JPG, PNG, etc.)
Nathan, could you try running this command: guix shell --pure viewnior gdk-pixbuf -- viewnior For me this works now. My guess is that for you, something else breaks viewnior and --pure can help. Regards, Florian
bug#20255: 'search-paths' should respect both user and system profile.
Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge search-paths from multiple profiles by `guix package --search-paths`, in ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual update). Close now!
bug#63471: python-pytorch has bogus version string
The wheel generated for python-pytorch embeds a bad version string: … Building wheel torch-1.13.0a0+gitUnknown … This lets the version check in downstream packages fail. -- Ricardo
bug#63427: gdk-pixbuf unable to recognize image formats (JPG, PNG, etc.)
Yes, that one works On Fri, May 12, 2023 at 4:27 AM pelzflorian (Florian Pelz) wrote: > > Nathan, could you try running this command: > > guix shell --pure viewnior gdk-pixbuf -- viewnior > > For me this works now. My guess is that for you, something else breaks > viewnior and --pure can help. > > Regards, > Florian
bug#63190: [Shepherd] Nested calls lead to a hang
Ludovic Courtès writes: (Whether that leads to a deadlock depends; at first sight, I’d say there’s no reason for this to deadlock in general, but you can of course end up with a logic bug like A starts B, which spawns a client to start A, which doesn’t start because it’s waiting for B.) It's been a while since I looked at this, but my rough recollection is the deadlock occurs because shepherd can only process one request over its socket at a time. If that request happens to *also* try to talk over the same socket, it'll hang indefinitely waiting for its turn to come off the accept queue. I'm not sure there's much to be done in the 0.9 version of shepherd about it. I'm hoping that 0.10 and up will be able to cope with situations like this without completely deadlocking the shepherd itself. It's obviously pretty bad if pid 1 hangs for any reason at all, even user error. -bjc
bug#58561: Source hash mismatch with aggregator + possible guix bug with hashes.
Issue was fixed and Tobias explained the hash issue.
