bug#70826: [PATCH] system: Allow distinguishing s.

Hi, Ludovic Courtès writes: > Hello 45mg and all, > > I polished the patch I had sent in this thread: > > https://codeberg.org/guix/guix/pulls/1048 Pushed as 14c8728f0d812ea2c396b3c0564fa8da1202f430. Ludo’.

bug#77900: Unprivileged guix-daemon fails to build in Docker/relocatable pack

Hi, David Elsing writes: > Ludovic Courtès writes: > >> But it’s unsatisfactory: I would hope the unprivileged daemon would >> allow us to address that shortcoming. > > Yes it does, as long as the needed syscalls are not restricted. I'm not > sure when this will

bug#78919: ^C'ed --keep-failed build leaves directory owned by root

Hi, Ludovic Courtès writes: > 2025-07-08 22:45:06 note: keeping build directory > `/tmp/guix-build-hello-2.12.2.drv-0' > 2025-07-08 22:45:06 error (ignored): file > `/tmp/guix-build-hello-2.12.2.drv-0/top/GMfifo3392' has an unsupported type > 2025-07-08 22:45:0

bug#48265: Test breakage

Cc: 宋文武 would may otherwise miss your message. Mathieu Othacehe writes: > Hello, > > Commit b7a8f886f5 breaks the gui-installed-desktop-os-encrypted test > evaluation because of the following error: > > guix repl: error: profile contains conflicting entries for mate-polkit > guix repl: error:

bug#35085: Comment for EmacsConf 2024 repro: Reproducibly building Emacs: “Hey your checksum is the same as mine!”

Hi Nicolas, Nicolas Graves writes: > I see that you've cancelled the talk on EmacsConf 2024, is there a place > where we can find information on the subject? We want to tackle this in > Guix and despite using `--disable-build-details`, the profile dump is > still unreproducible on emacs@30.1. I

bug#77132: Shepherd: flaky self tests

Simon Josefsson writes: > Ludovic Courtès writes: > >> Also, I wonder if the problem could be a race condition, which would be >> fixed like this: >> >> diff --git a/tests/services/log-rotation.sh b/tests/services/log-rotation.sh >> index 375f563..178bb4

bug#77900: Unprivileged guix-daemon fails to build in Docker/relocatable pack

Hi, David Elsing writes: > Ludovic Courtès writes: > >> I don’t actually use podman and Docker but I think it would be nice if >> the unprivileged guix-daemon would work out of the box in these >> environments, particularly in CI environments like GitLab-CI where &g

bug#78919: ^C'ed --keep-failed build leaves directory owned by root

Hi Janneke, Wait, indeed, if I C-c during the ‘build’ phase, I end up with: --8<---cut here---start->8--- $ ls -lrtd /tmp/guix-build-hello-2.12.2.drv-0/ drwx-- 3 root root 60 8 juil. 22:44 /tmp/guix-build-hello-2.12.2.drv-0/ --8<---cut here

bug#77900: Unprivileged guix-daemon fails to build in Docker/relocatable pack

Hi David, Cc: Reepca. David Elsing writes: > Ludovic Courtès writes: > >> When running guix-daemon unprivileged in Docker (or, similarly, in a >> ‘guix pack -R’ relocatable pack), it fails to spawn the build process: >> [...] >> The clone(2) man page lists two

bug#78919: ^C'ed --keep-failed build leaves directory owned by root

Hi Janneke, Janneke Nieuwenhuizen writes: > When running something like > > guix build hello --with-configure-flag=hello=foo=bar --keep-failed > > > and hitting ^C during the `build' phase, the guix-daemon leaves > > $ sudo ls -ld /tmp/guix-build-hello-2.12.2.drv-0 > /tmp/guix-build-hello-2.12.

bug#77132: Shepherd: flaky self tests

Hi Simon, (- guix-devel) Simon Josefsson writes: > I instrumented the Debian package build system to patch the script to > print debug info, below is that log output, is this better? I made a mistake: in ‘file_descriptor_count’, the line to add should be: ls -l /proc/$shepherd_pid/fd/ >&2

bug#70826: [PATCH] system: Allow distinguishing s.

Hello 45mg and all, I polished the patch I had sent in this thread: https://codeberg.org/guix/guix/pulls/1048 As usual, feedback welcome! Ludo’.

bug#71226: ‘guix shell -C’ doesn’t work on Ubuntu 24.04

Hello, "nomike (they/them)" writes: > I've just filed a patch to the apparmor package maintainers for adding > a guix profile to their package: > > https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2111753 > > Was quite a challenge to figure out how to do this, at least compared > to what

bug#77132: Shepherd: flaky self tests

Hi Simon, Simon Josefsson writes: > Below is the log file. > + shepherd --version > ;;; WARNING: loading compiled file > /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/fibers.go failed: > ;;; In procedure load-thunk-from-memory: incompatible bytecode version > ;;; WARNING: loading compiled fi

bug#77132: Shepherd: flaky self tests

Hi Simon, Simon Josefsson writes: > Ludovic Courtès writes: [...] >> ++ wc -l >> + test 22 -le 18 >> >> This is the same as <https://issues.guix.gnu.org/77132>. >> >> Could you instrument it as I suggested there? > > I'm still seein

bug#78852: shepherd: internal syslog records not in chronological order

Hi, bur...@opopop.net writes: > But when ‘system-log’ starts, it would be logical to flush first > /proc/kmesg while keeping on hold it's own messaging until that is > done. OK. As it stands, flushing /dev/kmsg before the other messages get written is hard to implement: /dev/kmsg is considered

bug#78947: Mono dependency issue

Hi, "nomike (they/them)" writes: > When I'm trying to install mono, this happens: > > ```plaintext > $ guix install mono > The following package will be installed: >    mono 6.12.0.206 > > substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0% > substitute: updating substitute

bug#78355: guix-ownership inconsistent state

Hi Rutherther, Ludovic Courtès writes: > Rutherther writes: > >> The guix-ownership service checks /gnu/store ownership to check if the >> whole store and all files important for the daemon (/etc/guix, >> /var/guix) are owned by the appropriate user. >> &

bug#74912: bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi Tomas, Tomas Volf <~@wolfsden.cz> writes: > So my suggestion is that when the socket is deleted, the shepherd > process stops itself. I posted a patch that does exactly that: https://codeberg.org/shepherd/shepherd/pulls/14 Let me know what you think! Ludo’.

bug#78852: shepherd: internal syslog records not in chronological order

Hi, bur...@opopop.net writes: > ... /dev/kmsg and shepherd messages interleaved, but obviously not in > chronological order > > 2025-06-20 16:59:44 localhost shepherd[1]: Service mountall running with > value #t. > 2025-06-20 16:59:44 localhost shepherd[1]: Starting service rsyslogd... > 2025-0

bug#78919: Reporting issues with fj.el

Hi, Just a quick note before looking at the actual bug… Janneke Nieuwenhuizen writes: > PS: I tried several times to report this using M-x fj-create-issue, but > I'm gettting either > > Contacting host: codeberg.org:443 > fedi-http--process-response: > 404 page not found > > > or > > Contactin

bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hi, Danny Milosavljevic writes: > Your change LGTM! Pushed as 436a00be92c53f5054885eebd200153933b63a1d. > P.S. I also found an extra spot in man/NetworkManager.xml : > > > NetworkManager will execute scripts in the > /etc/NetworkManager/dispatcher.d directory or subdirectories in

bug#78283: guix git authenticate is indiscriminant in which branches it applies to

Ludovic Courtès writes: > Vagrant Cascadian writes: > >> So, when I update my local keyring branch with new merges, guix git >> authenticate issues a non-fatal error: >> >> $ git checkout keyring >> Switched to bran

bug#74583: ‘guix git authenticate’ pre-push hook unsuitable in some cases

Ludovic Courtès writes: > Proposed fixes: <https://codeberg.org/guix/guix/pulls/482>. Pushed: 99f85246e19 * git authenticate: Do nothing when invoked from the keyring branch. 0ec5cab1325 * git authenticate: Gracefully handle passing an annotated tag to ‘--end’. 56eb949f

bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi Danny, We can do both: 1. Have ‘shepherd’ stop itself if its socket is removed (for user shepherd), or recreate the socket (for PID 1). 2. Change elogind to potentially allow user shepherd to outlive user sessions. >From the Shepherd’s viewpoint, #1 seems to be the safe thing t

bug#78757: shepherd: dangling file descriptor to /dev/console

Hi, bur...@opopop.net writes: >> ‘shepherd’ marks all previously-opened FDs as O_CLOEXEC upfront—see >> ‘mark-as-close-on-exec’ in ‘shepherd.scm’. Those opened later are >> opened with O_CLOEXEC, except for user code that explicitly omits the >> O_CLOEXEC flag. > > Hmmm I have at one point (

bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi, Tomas Volf <~@wolfsden.cz> writes: > Well, since you have mentioned the GnuPG as an example, we could just > mirror what it does, and what I have suggested before. > > --8<---cut here---start->8--- > $ mkdir /tmp/xxx && cd /tmp/xxx > $ guix shell -u test -C

bug#30986: ‘guix substitute’ spins forever

Hi, l...@gnu.org (Ludovic Courtès) writes: > I’ve stumbled upon a situation where ‘guix substitute’ would spin > endlessly. Tracing the ‘guix substitute’ process shows that the > following two “info” queries would happen in a loop: It may have been due to <https://issues.guix.g

bug#30952: Grafting sometimes include all the outputs of a package

Hi Simon, Simon Tournier writes: > What is the status of this old bug > > https://issues.guix.gnu.org/issue/30952 I’m afraid the problem still exists, after all these years: --8<---cut here---start->8--- $ guix gc -R $(readlink -f /run/current-system) |g

bug#78758: shepherd: herd graph issue

Hi, bur...@opopop.net writes: > It would perhaps make everyone happy to add the root service in the > graph only if #:requirement is empty. I think it would be confusing. It should either always show the ‘root’ node, or never show it. Ludo’.

bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi Danny, Danny Milosavljevic writes: > It's good that the "is a shepherd already running" check is back in > shepherd. It was in shepherd years ago, then got removed without > explanation, then now it's back again (now in a very convoluted but > safer way). This shouldn't have been removed in

bug#78758: shepherd: herd graph issue

Hi, burban--- via Bug reports for GNU Guix writes: > I noticed that "herd graph" always creates a link to root, which IMO > clobbers the picture (I can send pictures if that is allowed on this > list or their source) Yeah I wondered about that at the time but found that not having a clear sourc

bug#78757: shepherd: dangling file descriptor to /dev/console

Hi burban, burban--- via Bug reports for GNU Guix writes: > All shepherd children have an open file descriptor to /dev/console, > probably because of the use of dup2 (and not dup3) in system.scm. I checked the /proc/PID/fd directory of several of my system services on Guix System (nscd, guix-pu

bug#78355: guix-ownership inconsistent state

Hi Rutherther, Rutherther writes: > The guix-ownership service checks /gnu/store ownership to check if the > whole store and all files important for the daemon (/etc/guix, > /var/guix) are owned by the appropriate user. > > If the folder isn't owned by appropriate user, it moves to those steps:

bug#78283: guix git authenticate is indiscriminant in which branches it applies to

Hello, Vagrant Cascadian writes: > So, when I update my local keyring branch with new merges, guix git > authenticate issues a non-fatal error: > > $ git checkout keyring > Switched to branch 'keyring' > $ git reset --hard 21173006e4165d8990b75ca46c78d83448d2e45a > HEAD is now at 2117300

bug#74583: ‘guix git authenticate’ pre-push hook unsuitable in some cases

Proposed fixes: . Feedback welcome! Ludo’.

bug#77545: found bug installing guix-daemon on riscv64-linux (framework laptop)

Hi, Dots writes: > dots@deepcomputing:~/Documents/guix$ guix pull > Updating channel 'guix' from Git repository at > 'https://git.savannah.gnu.org/git/guix.git'... > Authenticating channel 'guix', commits 9edb3f6 to f3a8c28 (17 new commits)... > Building from this channel: > guix htt

bug#77296: guix fails tests on aarch64 after rootless daemon patches

Hi, Efraim Flashner writes: > (ins)ubuntu@ubuntu:~$ unshare -mrnf ifconfig lo up > unshare: write failed /proc/self/uid_map: Operation not permitted > (ins)ubuntu@ubuntu:~$ cat /etc/os-release > PRETTY_NAME="Ubuntu 24.04.2 LTS" It may have to do with Ubuntu’s restrictions on unprivileged user n

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hello! Reepca Russelstein writes: > So if you'll bear with the extreme awkwardness, we could fork a helper > process immediately prior to calling unshare, which, upon receiving a > notification, will initialize the parent process's user namespace. Note > that the naming here is going to be inve

bug#74583: ‘guix git authenticate’ pre-push hook unsuitable in some cases

And when deleting a branch: --8<---cut here---start->8--- guix git: .[1;31merror: .[0mGit error: odb: cannot read object: null OID cannot exist error: failed to push some refs to 'codeberg.org:civodul/guix-science.git' --8<---cut here---

bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hi, Danny Milosavljevic writes: > Maybe for a really really paranoid way we could replace the check by a > check whether geteuid() == st_uid, no ? The idea being that the check > wouldn't change behavior if it's actually run as root and would change > behavior if it's run as your real user. Bu

bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hello, Ludovic Courtès writes: > So I’m tempted to just remove the check, but I’d rather have more > eyeballs on this: > > diff --git a/src/core/nm-core-utils.c b/src/core/nm-core-utils.c > index 895a991..738f8c7 100644 > --- a/src/core/nm-core-utils.c > +++ b/src

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hey Reepca, Reepca Russelstein writes: > Ludovic Courtès writes: [...] >> The attached patch tries to do that, by calling out to ‘newuidmap’, and >> under the assumption that /etc/subgid allows mapping the ‘kvm’ group. >> >> It does the job (a build process

bug#76282: Signal handling (like SIGINT) and guix shell --container: PID 1

Hello, Maxim Cournoyer writes: > Your analysis appears correct; the above 'make' runs with PID 3. > > --8<---cut here---start->8--- > maxim@terra ~/src/forgejo$ guix shell -CNF -m manifest.scm -- env GOPATH=/tmp > TAGS="bindata timetzdata sqlite sqlite_unlock

bug#71645: llhttp package in guix contains generated sources

Hi, "Jelle Licht" writes: > This is still an issue; > should we wait for someone to properly package things, or should be > remove the llhttp package that currently exists along with its only > dependent (restinio)? There’s no policy in place saying that this should be removed, even though it’s

bug#78421: Occasional crashes when resuming from software suspend

Ludovic Courtès writes: > With Linux-libre 6.14.5-gnu (commit > 300d29e69988caf23684f08effa51f621c7ec083), my laptop occasionally > crashes when resuming from software suspend: blank screen, does not > answer to pings, cannot switch ttys, etc. and hard shutdown is the only > way

bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hello, Ludovic Courtès writes: >>> 2025-04-24 10:34:15 localhost NetworkManager[852]: >>> [1745483655.8537] plugin: skip invalid file >>> /gnu/store/agadky1p0ba367avf524sh5wmcdxcxb1-network-manager-1.52.0/lib/NetworkManager/1.52.0/libnm-device-plugin-wwan.so: >>

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hello, (Cc: Reepca.) keinflue writes: > It seems that the "chown to overflowgid" issue is somewhat > widespread. I also see the testsuite for go (bootstrap) failing in the > same way. I'd guess most implementations of "chown" system call > wrappers in various languages will have test cases like

bug#78363: [PATCH 3/3] environment: Make home writable.

Hello, Tomas Volf <~@wolfsden.cz> writes: > * guix/scripts/environment.scm (launch-environment/container): Add tmpfs for > home. > * tests/guix-environment-container.sh: Add test. > > Change-Id: Iadd9b838f6442a8080998ed7e07414db562068bf I added a “Fixes” line referencing the initial bug report a

bug#77610: guix-daemon socket activation does not work on the hurd

Hello, yelni...@tutamail.com writes: > Something like this? I called the patch hurd-socket-activation.patch > to indicate what it is addressing. Do you have a better suggestion? Perfect; applied, thank you. > I added it to master but this will create a minor merge conflict with the > hurd upda

bug#78363: Home is read-only in guix shell container

Tomas Volf <~@wolfsden.cz> writes: > Yeah, I agree. I can try to produce a patch (I should have some time on > Sunday), but obviously anyone feel free to step in. Wonderful, thanks. :-) Ludo’.

bug#78445: meson-build-system's 'shrink-runpath phase fails for guile go files

Hi Dariqq, Dariqq writes: >> Another solution is to arrange so that ‘meson-build-system’ does not >> touch .go files for this package, for instance by skipping the >> ‘shrink-runpath’ phase. >> > > Yeah, that's what I have been doing but I think 'strip-runpath' could > handle this case more gra

bug#78445: meson-build-system's 'shrink-runpath phase fails for guile go files

ch .go files for this package, for instance by skipping the ‘shrink-runpath’ phase. HTH, Ludo’. diff --git a/guix/build/gremlin.scm b/guix/build/gremlin.scm index 2a74d51dd9..ceb1c7bcf5 100644 --- a/guix/build/gremlin.scm +++ b/guix/build/gremlin.scm @@ -1,5 +1,5 @@ ;;; GNU Guix --- Functional p

bug#78421: Occasional crashes when resuming from software suspend

Hello, "Leo Famulari" writes: > What hardware do you see this on? > > On my Thinkpad x260 with an Intel i5, resume stopped working for me in > 6.1, and I'm still using 5.15. The failures are not deterministic for > me. Sometimes it works. It’s on an HP EliteBook Folio 1040 G3/80FA (from 2016).

bug#78440: Unexpected requirement of --writable-root when using --share with guix shell

Hi Ricardo, Ricardo Wurmus writes: > Is this intentional or should we add an exception to make the > in-container home directory created for the user invoking "guix shell" > writable for that same user? This is being discussed in . The conclusion so far is th

bug#74912: bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi Jake, Jake writes: > That commit made a difference but didn't fix the problem for me. > After a couple of relogs since the last reboot: Hmm is /run/user/$UID deleted when logging out? This would explain that the fix in the Shepherd doesn’t make any difference. Ludo’.

bug#78356: Broken system and home containers

Hi Maxim, Maxim Cournoyer writes: > Not sure how minimal that is, but I can trigger this in the readymedia > system test: > > --8<---cut here---start->8--- > make check-system TESTS=readymedia > --8<---cut here---end--->8---

bug#78355: guix-ownership inconsistent state

Hi, Rutherther writes: > I think it would at least be good if there was a script to do what > guix-ownership does, but force it without the /gnu/store ownership > check, to make it easier for users to recover. Maybe even an optional > argument to > guix-ownership, where you could `sudo herd sta

bug#78355: guix-ownership inconsistent state

Hi, Rutherther writes: > There are reports from users with inconsistencies in ownership, it seems that > at > least /var/guix is sometimes left with wrong owner, but maybe even parts > of the store? I cannot verify that. Would be nice to get their reports here, otherwise we’re left speculating

bug#77610: guix-daemon socket activation does not work on the hurd

Hi yelninei, yelni...@tutamail.com writes: > Thank you again for finding the cause.Could we add your patch to our > hurd either for master or core-packages-team as it will be a while > until it is available in a tagged snapshot.It would fix the hurd ci > builders randomly failing, the childhurd s

bug#78194: `guix pull --list-generations' is extremely slow

Ludovic Courtès writes: > Because for each pair of generations, it shows the corresponding news > entries (as per ‘guix pull --news’), and that part is quite expensive > because it involves a Git log traversal. > > I think we should (1) optimize the news code (that’s > ‘chann

bug#73903: [PATCH 0/2] Add shepherd-for-home and make it default

Hi, Dariqq writes: > gnu: Add shepherd-for-home. > gnu: home: Use shepherd-for-home as the default shepherd. For some reasons I had overlooked these patches. Finally applied, with cosmetic modifications to the first one. Thanks! Ludo’.

bug#74912: bug#76998: Guix Home leaves user shepherd on logout, starts new instance on login

Hi, Ludovic Courtès writes: > So shepherd will now refuse to start when it determines that an instance > is already listening on its socket: > > > https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=787d5a33aea061b5052faa0863c96be722440ce3 This commit is in 1.0.4. Closing! Ludo’.

bug#78363: Home is read-only in guix shell container

Hello, Tomas Volf <~@wolfsden.cz> writes: >> As noted in the ‘guix pull’ news, you can use ‘--writable-root’. >> Otherwise, everything but the current directory and /tmp is read-only. > > Does that make sense though? You have already made an exception for > /tmp, I would argue that ~ is another

bug#78194: `guix pull --list-generations' is extremely slow

Hi, Ian Eure writes: > I’ve been frustrated by this before, but decided to measure things: > > `guix home list-generations' takes 3.535s to list 28 items. > `guix system list-generations' takes 1.406s to list 35 items. > `guix pull --list-generations' takes 232.599s to list 41 items. > > Why is

bug#77610: guix-daemon socket activation does not work on the hurd

For the record, this issue is now fixed upstream: https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=029ab7d7b38c76ba14c24fcbf526ccef29af9e88 https://lists.gnu.org/archive/html/bug-hurd/2025-05/msg00016.html Closing! Ludo’.

bug#78421: Occasional crashes when resuming from software suspend

Hello, With Linux-libre 6.14.5-gnu (commit 300d29e69988caf23684f08effa51f621c7ec083), my laptop occasionally crashes when resuming from software suspend: blank screen, does not answer to pings, cannot switch ttys, etc. and hard shutdown is the only way out. /var/log/messages shows software suspen

bug#78356: Broken system and home containers

Hi, Rutherther writes: >> --8<---cut here---start->8--- >> > >> Updating channel 'guix' from Git repository at >> 'https://codeberg.org/guix/guix-mirror'... >> guix home: error: failed to load 'home/home-configuration.scm': >> web/client.scm:338:10:

bug#78356: Broken system and home containers

Hi, Rutherther skribis: >> ./target/guix/bin/guix home container -L ./home/modules >> ./home/home-configuration.scm > guix home: warning: failed to load '(ruther home channels-emacs)': > no code for module (ruther home channels-emacs) > ruther/home/channels-emacs.scm:1:0: warning: module name

bug#78356: Broken system and home containers

Hi, Rutherther writes: > --8<---cut here---start->8--- > [ruther:~/.setup] main(+68/-13)* 15s ± >> ./target/guix/bin/guix home container -L ./home/modules >> ./home/home-configuration.scm > guix home: warning: failed to load '(ruther home channels-emacs)':

bug#78356: Broken system and home containers

Hi, Rutherther writes: > The command was `guix home container -L ./home/modules > ./home/home-container.scm` > in my repository. It's here https://git.ditigal.xyz/~ruther/guix-config. > Any idea what service could cause this behavior with lock-mounts? Would > be good to isolate it, but I am not

bug#78356: Broken system and home containers

Hi, Rutherther writes: > Seems that the recent commit 'Lock mounts by default' > a57ed987ffd1452ba5a4d70feb54893e99b8e076 has broken both guix system > container and guix home container. For system container, the system > container command finishes fine, but then running the run-container > scri

bug#78363: Home is read-only in guix shell container

Hi, keinflue writes: > I am not sure whether this is intended behavior, but it seems weird to > me. Inside e.g. > > guix shell -Cu test coreutils > > /home/test is mounted read-only and I do not see any way to make it > writable without sharing a host directory. As noted in the ‘guix pull’ news

bug#78319: gnu.org/software/guix redirects broken

Hi Florian, "pelzflorian (Florian Pelz)" writes: > Ludovic Courtès writes: >> Looks like the gnu.org webmasters broke our redirects: >> >> $ wget --debug -O/dev/null >> https://www.gnu.org/software/guix/manual/en/html_node/Substitutes.html > > Maybe

bug#70826: [PATCH] system: Allow distinguishing s.

Hi, 45mg <45mg.wri...@gmail.com> writes: > Sorry for the delay, I've been quite busy lately. No worries. > If I understand correctly, your proposal would make > luks-device-mapping-with-options obsolete, so users would have to change > from this: > > --8<---cut here---st

bug#75658: [PATCH 0/4] Fixes for subshells and redirections

Z572 writes: > I'm going to roll back openssl first. BTW, I’d like to ungraft everything on this branch. We should avoid touching packages like OpenSSL anyway since they are outside the scope of ‘core-packages’ and doing so could cause conflicts with ungrafting etc. Thanks, Ludo’.

bug#75658: [PATCH 0/4] Fixes for subshells and redirections

Andreas Enge writes: > Am Thu, May 08, 2025 at 05:36:17PM +0800 schrieb Z572: >> on ci.guix: >> building of >> `/gnu/store/nbb9svpwh2zzqx92xcjbpjznia2mwvbb-gcc-mesboot-4.9.4.drv' timed >> out after 21600 seconds >> I think gcc-mesboot might be necessary to set larger timeout properties. > > My

bug#78319: gnu.org/software/guix redirects broken

Hello, Looks like the gnu.org webmasters broke our redirects: --8<---cut here---start->8--- $ wget --debug -O/dev/null https://www.gnu.org/software/guix/manual/en/html_node/Substitutes.html Setting --output-document (outputdocument) to /dev/null DEBUG output c

bug#78152: [guix-daemon] Build user's pw_dir != HOME

Hello, Maxim Cournoyer writes: >> (Note that the unprivileged daemon does introduce some discrepancies, >> and this is something we should fix as much as possible.) > > Hm, perhaps if the 'as much as possible' != 'everything', we could use > this breaking opportunity to bundle a few changes like

bug#78272: The /tmp in a guix shell container is now read-only

Hi Tomas, Tomas Volf <~@wolfsden.cz> writes: > the /tmp in a shell container is not read only which seems to break a > lot of things. For example when I try to build Guix from source: > > $ guix time-machine -q --commit=4a32b83753b124169003589fae42eff03ff482cc -- > shell -CD guix -- ./bootstrap

bug#70826: [PATCH] system: Allow distinguishing s.

Hi 45mg, Did you have a chance to look into the proposed change below? Thanks, Ludo’. Ludovic Courtès writes: > Hi, > > 45mg <45mg.wri...@gmail.com> skribis: > >> We use records to represent the different types of >> mapped devices (LUKS, RAID, LVM). When v

bug#75658: [PATCH 0/4] Fixes for subshells and redirections

Hi, Andreas Enge writes: > I tried yesterday, but made a mistake (forgot to push the unrebased > branch as core-packages-team-old3 first). Then when reverting the rebase > and trying to push, I realised I could not push a branch without > compiling it first. And this took me one hour on my old t

bug#75658: [PATCH 0/4] Fixes for subshells and redirections

Hello, "Ludovic Courtès" writes: > Timothy, Janneke: could you review/apply these Gash patches and cut a > release? The ‘core-packages-team’ has been blocked on this issue for > months. > > We cannot easily apply patches to the package definitions because > ‘patch

bug#34033: Offloading sometimes hangs

Hello, Andreas Enge writes: > Could this be closed after 5 years with no interaction? I think so! Ludo’.

bug#78067: bug#77968: [PATCH 0/1] gnu: openssh: Trust store items owned by guix-daemon.

Hi Sergey, Sergey Trofimov writes: > * gnu/packages/patches/openssh-trust-guix-store-directory.patch > (openssh): Adjust to trust files in guix store owned by guix-daemon. > * gnu/packages/ssh.scm (openssh): [phases]: Append ending slash when > substituting STORE_DIRECTORY. Use default PRIVSEP_P

bug#67707: Fresh installation leaks details about ISO build environment

Hello, Rutherther via Bug reports for GNU Guix writes: > Ludovic Courtès writes: [...] >> Oh right, it’s probably best to change it there. Something like this? > > Yes, that is exactly what I had in mind. OK, pushed as 94c9e53fa4b45e85c1664a9bab6aea0d5c3ac123. I checked in

bug#78152: [guix-daemon] Build user's pw_dir != HOME

Hi Maxim, Maxim Cournoyer writes: > There is a discrepancy in our build environment, where the build user's > directory is set to '/' while HOME is set to '/homeless-shelter'. > Normally both should match, and it trips some test suite that assumes > this to be the case, as with libssh's [0]. > >

bug#78067: Conversion to unprivileged guix-daemon breaks ssh

Hi Zack, "Zack Weinberg" writes: > I just switched my Guix System-based server over to unprivileged guix- > daemon, after which I was unable to ssh into it. From the client, the > syndrome looks like this (shell variables indicate redactions): [...] > 2025-04-25 20:27:40 localhost shepherd[1]

bug#76554: Laptop screen blank after kexec reboot

Simon Streit writes: > Maxim Cournoyer writes: > >> So just to make sure I got that right, it works correctly on Debian >> but incorrectly (black screen) on Guix System on the *same* hardware? > > correct. Actually we “just” need to set screen brightness at activation-time: https://issues.gu

bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hi, Rodion Goritskov writes: > In logs I can see the following errors: > >> 2025-04-24 10:34:15 localhost NetworkManager[852]: >> [1745483655.8534] plugin: skip invalid file >> /gnu/store/agadky1p0ba367avf524sh5wmcdxcxb1-network-manager-1.52.0/lib/NetworkManager/1.52.0/libnm-device-plugin-ovs.s

bug#73905: [PATCH v2] environment: Restore action for SIGPIPE.

Tomas Volf <~@wolfsden.cz> writes: > Code in `ui.scm' in `initialize-guix' procedure changes the handling of > SIGPIPE to SIG_IGN. So restore the handling to SIG_DFL so that process > executed will have the usual action. Technically we should record what the > handling was, and restore it to the

bug#67707: Fresh installation leaks details about ISO build environment

Hi, Rutherther via Bug reports for GNU Guix writes: > What I had in mind in the first place was replacing it just in the > install.scm, I didn't even think about changing it here. Oh right, it’s probably best to change it there. Something like this? diff --git a/gnu/system/install.scm b/gnu/s

bug#77806: elogind behavior changed: power key turns computer off

Hi, Maxim Cournoyer writes: > Josselin pointed to some problem, which I've now fix (had to use > "drop-ins" files instead of the canonical config file names, which are > looked from the package's sysconfdir in the store instead of under > /etc/elogind). If we find other we can fix them later, b

bug#67707: Fresh installation leaks details about ISO build environment

this: diff --git a/gnu/packages/package-management.scm b/gnu/packages/package-management.scm index f0a9b39e25..46cf9b8512 100644 --- a/gnu/packages/package-management.scm +++ b/gnu/packages/package-management.scm @@ -1,5 +1,5 @@ ;;; GNU Guix --- Functional package management for GNU -;;; Copyright ©

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hi, keinflue writes: > Unfortunately the python package also fails with equivalent test > failures. It also has another failure mode where it expects a syscall > to change ownership to the overflow uid to result in EPERM, while it > will produce EINVAL (which happens even if there are no supplem

bug#77086: Filesystems not unmounted on reboot

Hello, "Ashish SHUKLA" writes: > I just rebuilt kernel and problem happened again after guix system > reconfigure. I made following not so helpful (at least I can not spot > anything) videos (available for at least a week from today): > > https://www.lostca.se/~abbe/VID20250503134553.mp4 (chvt 1

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hello, keinflue writes: > I also had another look and I missed that effectively CAP_SETGID is > required in the _parent_ namespace in order to use setgroups (because > otherwise writing "deny" to /proc/[pid]/setgroups is essentially > forced). > > But the same seems to also be required to map mo

bug#77086: Filesystems not unmounted on reboot

Hello, "Ashish SHUKLA" via Bug reports for GNU Guix writes: > Filesystems not unmounted on reboot, or rather I get filesystem check for "/" > volume after I power on, even though I shut it down (as rebooting was ending > up in this situation almost everytime). This only happens if I do "sudo g

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hi, keinflue writes: >> 2. I’m confused as to what makes the Coreutils test suite fail. > > The result from getgroups includes both the primary gid 3 and a > supplementary gid 65534 (where the repeated 65534 are the overflow gid > produced by viewing supplementary gids that aren't mapped i

bug#77862: guix-daemon run as non-root sets up /etc/group incorrectly in build container

Hi, I committed the /etc/group fix in 0d3bc50b0cffeae05beb12d0c270c6599186c0d7 together with a test. keinflue writes: > I think this happens if the user running guix-daemon has supplementary > groups. These are not mapped via /proc/gid_map in the build container > and therefore are reported as

  1   2   3   4   5   6   7   8   9   10   >