bug#74941: Acknowledgement (Guix Pull Failure: Git SSL Error, Directory Cleanup Error, and Software Heritage API Timeout)

@@ +70,32 @@ 1009:8 9 (call-with-temporary-directory _) 1330:8 15 (call-with-build-handler # …) 1353:3 16 (_) 1685:16 0 (raise-exception _ #:continuable? _) 1685:16 1 (raise-exception _ #:continuable? _) 1752:10 19 (with-exception-handler _ _ #:unwind? _ # _) 262:4 2 (tls-wrap # "archive.softwa

bug#74952: [PATCH] guix-install.sh: Use "command -v nologin" instead of "which nologin".

On Wed, Dec 18, 2024 at 09:35:27PM +0100, Simon Josefsson via Bug reports for GNU Guix wrote: > Hi! > > In a small container image, I do not have the 'which' tool installed. I > believe 'command -v' is always available since it is /bin/sh standard. > How about changing the idiom for user/group a

bug#74912: Shepherd: Growing number of user shepherds when relogging

Hello, Jake skribis: > I think I'm experiencing a bug in Shepherd since version 1.0. > Whenever I log out and log back in again, my user shepherd from the > previous login session is still present, and a new user shepherd spawns for > the current login session. > So relogging N times results in

bug#74949: guix describe crash if HOME is unset OR /etc/passwd is missing

Hi I get the backtrace below. Setting either HOME to something, or adding an entry to /etc/passwd for the running user, silences this. I don't think it should fail like this, should it? Is a reasonable behaviour to assume HOME means "/" when unset? How to handle missing /etc/passwd entries pro

bug#74912: Shepherd: Growing number of user shepherds when relogging

Ludovic Courtès writes: > Hello, > > Jake skribis: > >> I think I'm experiencing a bug in Shepherd since version 1.0. >> Whenever I log out and log back in again, my user shepherd from the >> previous login session is still present, and a new user shepherd spawns for >> the current login session

bug#74948: guix pack docker environment variable setting

Hi I believe the guix-pack docker format allows setting environment variables in the resulting image, is that right? I can't find any way to set them using the `guix pack` tool, am I missing it? Would a new `guix pack --setenv HOME=/` parameter be useful? Such a parameter could be docker-specif

bug#74877: Close the issue.

It seems to be working for me now.

bug#74942: Computing the guix self derivations can require builds

I wasn't aware of a issue for this, so I'm creating one. I did send some patches in an attempt to fix this to #61363. The derivations used by guix pull, guix time-machine and other operations work differently to package derivations. I might have understood exactly how in the past, but unfortunatel

bug#74941: Guix Pull Failure: Git SSL Error, Directory Cleanup Error, and Software Heritage API Timeout

``` $ guix pull --channels=$PATH/channels.scm _rmtree_safe_fd(dirfd, fullname, onerror) _rmtree_safe_fd(fd, path, onerror) _shutil.rmtree(name, onerror=onerror) do = self.iter(retry_state=retry_state) During handling of the above exception, another exception occurred: File "/opt/swh/.local/lib/pyth

bug#70581: PHP, glibc, and CVE-2024-2961

Hi, Maxim Cournoyer skribis: > * gnu/packages/base.scm (%glibc-patches): New variable. > (glibc) [source]: Use it. > [properties]: Mark CVE-2024-2961 as hidden (resolved). > [replacement]: Add field to graft with... > (glibc/fixed): ... this new package. > > Fixes:

bug#74943: sshd: no hostkeys available -- exiting

I'm having trouble with ssh after reconfiguring, in /var/log/messages I see an error regarding hostkeys. The files seem to be there though, I've tried regenerating the keys but that made no difference. signature.asc Description: PGP signature

bug#70581: PHP, glibc, and CVE-2024-2961

Hi Ludovic, Ludovic Courtès writes: [...] >> + (patches (map search-patch >> +(fold (cut delete <...>) >> + %glibc-patches >> + '("glibc-2.39-git-updates.patch" > > Or: (delete "gl

bug#74832: guix copy incorrectly assumes port is 22

Hi Tomas, Tomas Volf <~@wolfsden.cz> writes: > After update to guile-ssh 0.18.0, options passed to the `make-session' > procedure now take precedence over the configuration file. In few places we > however had code like `(or port 22)' leading to (in absence of alternative > port being specified)

bug#74952: [PATCH] guix-install.sh: Use "command -v nologin" instead of "which nologin".

Hi! In a small container image, I do not have the 'which' tool installed. I believe 'command -v' is always available since it is /bin/sh standard. How about changing the idiom for user/group additions from 'which' to 'command -v'? See attached patch. /Simon From 2bc261126a84a4a9a33acea9f107ad4b

bug#60608: keras is broken –> package bazel?

Hi, I'm in a limbo to upgrade https://github.com/spf13/afero, which requires go-google-golang-org-api, which relays on auto-generated code in https://github.com/googleapis/go-genproto which was built from https://github.com/googleapis/googleapis/ with Bazel, which we don't have in Guix (yet?) An

bug#73979: validate-runpath phases fails when binaries linked to package's own libraries

Hi Ludovic, Ludovic Courtès writes: > Hi, > > Maxim Cournoyer skribis: > >> There's a common pattern in packages where the validate-runpath phases >> fail, which is when a binary is linked to libraries provided by the same >> package. In this case, our ld-wrapper script appears to not bake the