bug#57077: guix-jupyter fails a test

Hi Mădălin, Mădălin Ionel Patrașcu skribis: > Build drops warnings regarding 'guild' and the check phase does not > have write permissions for its tests. > [build]: Remove the warnings generated by the 'guild' by setting the > "GUILE_AUTO_COMPILE" to 0. > [check]: Set the homeless-shelter to

bug#60890: least-authority-wrapper and make-forkexec-constructor composition problem

Hello! Maxim Cournoyer skribis: > It was found that using something like: > > (make-forkexec-constructor > (least-authority > (list (file-append coreutils "/bin/true")) > (mappings (delq 'user %namespaces)) > #:user "nobody" > #:group "nobody")) > > Would fail with EPERM, because

bug#60947: Two different derivations for ‘guix’ depending on whether grafts are enabled

Ludovic Courtès skribis: > We have a problem! Depending on whether grafts are enabled, we end up > building one of two different derivations for ‘guix’ (“real” > derivations; none of them is a mere grafting derivation): > > $ guix describe > Generation 241 Jan 16 2023 00

bug#60947: Two different derivations for ‘guix’ depending on whether grafts are enabled

We have a problem! Depending on whether grafts are enabled, we end up building one of two different derivations for ‘guix’ (“real” derivations; none of them is a mere grafting derivation): --8<---cut here---start->8--- $ guix describe Generation 241 Jan 16

bug#60831: Are our graphs okay?

Liliana Marie Prikler skribis: > The ‘patch-compilation-driver’ phase pulls in libgccjit even though it has > been deliberately removed from emacs-minimal. > > * gnu/packages/emacs.scm (emacs)[#:phases]: Delete ‘patch-compilation-driver’. > --- > Thanks Josselin for pointing this out. Yay,

bug#60141: Stack smashing detected after first guix pull on fresh Ubuntu 22.04 guix install

Hi, "Andrews, Kyle (KC)" skribis: > My system administrator let me know that the terminal I was presented with > was sandboxed by RStudio Server (not running on Guix) and that this was > responsible for causing the error. > > I was able to run the hello command from an unsandboxed shell. I

bug#60852: git-authenticate edge case for certain key setup.

Hi, Hilton Chain skribis: > I encountered the issue when adding a new key to my Guix channel. Though I > haven't figured out what happened exactly, I'm currently able to reproduce the > issue with the following steps. Fishy. Would you be able to write a script to reproduce the whole

bug#60875: Grafting breaks with clang-toolchain@13

Hi, Leo Famulari skribis: > On Tue, Jan 17, 2023 at 11:23:42AM +0100, Ludovic Courtès wrote: >> The file exists but it’s a dangling symlink: >> >> --8<---cut here---start->8--- >> $ ls -l >> /gnu/store/12wnswvdc1mk9cr4

bug#60875: Grafting breaks with clang-toolchain@13

Here’s what happens: --8<---cut here---start->8--- $ guix build clang-toolchain@13 The following grafts will be made: /gnu/store/gsh6dsafxmkh5wp3cq57czmlz2rc0a7m-clang-toolchain-13.0.1.drv

bug#25235: [PATCH 1/1] build-system/pyproject: Do not wrap native-inputs.

Hi, Maxim Cournoyer skribis: > Fixes . > > * guix/build/pyproject-build-system.scm (wrap) [native-inputs]: New argument. > Filter out native inputs from the values in GUIX_PYTHONPATH. Yay, great to see this fixed! > guix/build/pyproject-build-system.scm |

bug#60782: Channels and dependency confusion

Hello, Simon Tournier skribis: > On ven., 13 janv. 2023 at 14:48, Ludovic Courtès > wrote: > >> Nothing, because the ‘guix’ channel always comes first in the module >> search path (see ‘%package-module-path’ in (gnu packages)). Good. >> >> Now same scenari

bug#60566: [PATCH] environment: Fix '--emulate-fhs' option overriding $PATH.

Hi John, John Kehayias skribis: > From beb6f9255fc62fe52e237f82c7e953a21b7f82f4 Mon Sep 17 00:00:00 2001 > From: John Kehayias > Date: Thu, 5 Jan 2023 16:06:19 -0500 > Subject: [PATCH] * environment: Fix '--emulate-fhs' option overriding $PATH. > > Fixes

bug#60786: unsupported mips64el architecture can cause cryptic backtraces

Hi, Maxim Cournoyer skribis: > Maxim Cournoyer writes: [...] >> This issue was triggered by having make-uboot-package uses #:target [0], >> but it already exists on current master. I've spent some time narrowing >> down the issue, and it is caused by the package returned by >>

bug#60782: Channels and dependency confusion

In the light of the “dependency confusion” attack on PyTorch¹, one might wonder how such a thing could affect Guix. The threat model is quite different though because the ‘guix’ channel is peer-reviewed and curated whereas PyPI isn’t. Yet, one way to “translate” the attack to Guix is by looking

bug#41791: [Shepherd] loses track of Tor

Hi Tobias, Tobias Geerinckx-Rice skribis: > ~ λ while :; do sudo herd restart tor; done > Service tor is not running. > Service tor has been started. > Service tor has been stopped. > Service tor could not be started. > Service tor is not running. > Service tor could not be started. > ^C > ~ λ

bug#58290: guile ssh error on guix deploy

A simpler reproducer: --8<---cut here---start->8--- (use-modules (ssh session) (ssh popen) (ssh auth) (rnrs io ports)) (define session (make-session #:host "HOST-OF-YOUR-CHOICE")) (session-parse-config! session)

bug#58290: guile ssh error on guix deploy

Hi, Marius Bakke skribis: > Nov 3 21:50:28 capella sshd[26115]: debug1: server_input_channel_open: ctype > session rchan 66 win 64000 max 32768 > Nov 3 21:50:28 capella sshd[26115]: debug1: input_session_request > Nov 3 21:50:28 capella sshd[26115]: debug1: channel 10: new [server-session]

bug#58813: can't substitute etc/teams.scm command as doc suggests

Hi, Maxim Cournoyer skribis: > Simon Tournier writes: > >> Hi Ludo, >> >> On Tue, 03 Jan 2023 at 23:29, Ludovic Courtès wrote: >> >>> The manual recommends this (info "(guix) Teams"): >>> >>> git send-email --to issu

bug#48468: substitute server connection timeout

Hi, Mathieu Othacehe skribis: >> Instead of an env. var., maybe add a ‘--debug’ command-line option and >> parameterize ‘%debug?’ accordingly? > > The --debug command-line feels better but it involves a guix-daemon > modification so I kept the environment variable, Oh sorry, I was confusing

bug#60566: [PATCH] environment: Fix '--emulate-fhs' option overriding $PATH.

Hi, John Kehayias skribis: > From 57cdc3a8f9c6451aaf17f1fafae0bcf29faeea03 Mon Sep 17 00:00:00 2001 > From: John Kehayias > Date: Thu, 5 Jan 2023 16:06:19 -0500 > Subject: [PATCH] * environment: Fix '--emulate-fhs' option overriding $PATH. > > Fixes where

bug#48468: substitute server connection timeout

Hi Mathieu! Mathieu Othacehe skribis: >> (From .) >> >> Plausible explanations that come to mind: >> >> 1. ‘guix publish’ returning 404, but not due to baking. Instead the >> .drv is simply not in store, hence 404. >> >> 2. Client timeout

bug#58250: guix import json: GUIX_PACKAGE_PATH -- no code for module

itd skribis: > * guix/import/print.scm (package->code)[package-module-name]: Use > file-name->module-name to build the package module name. > --- > This patch updates the JSON importer to use (guix modules)'s > file-name->module-name to determine the module name. > > guix/import/print.scm | 6

bug#58250: guix import json: GUIX_PACKAGE_PATH -- no code for module

Hi, itd skribis: > * guix/modules.scm (file-name->module-name): Ignore load path prefix > when building module name. > --- > It was mentioned on IRC, that (guix modules)'s file-name->module-name > might be function to be used by the JSON importer (and fixed if needed). > This patch attempts to

bug#60106: [Shepherd 0.9.3] ‘system*’ replacement cannot be passed environment variables

Adam Faiz skribis: >> I think we’ll have to add a parameter to ‘spawn-command’ to specify >> environment variables. >> Ludo’. > If you do this, can you add an #:append? flag which adds environment > variables to the inherited environment instead of specifying the > variables declaratively? It

bug#60202: tests/cpio failure

Ludovic Courtès skribis: > At least we can skip this test when that is the case (patch below). > WDYT? I went ahead with this in 2880dc3046170e9129437caca586f13956d0d811. Ludo’.

bug#59907: Replace $ record matching with match-record

Hi, MANCINI Raffael skribis: > https://guix.gnu.org/manual/devel/en/html_node/Service-Types-and-Services.html > still references the $ construct which apparently should be replaced by > match-record which is not sensitive to record slot order. Good idea. Done in

bug#60202: tests/cpio failure

use a 64-bit ‘ino_t’, so fundamentally the cpio format is “wrong”. But what can we do? At least we can skip this test when that is the case (patch below). WDYT? Thanks, Ludo’. diff --git a/tests/cpio.scm b/tests/cpio.scm index 516de0655b..832101d1bb 100644 --- a/tests/cpio.scm +++

bug#60194: Guix (package manager) fails in initramfs

Hi, guix question skribis: > Because guix relies on pivot_root, it doesn't work in initramfs. Could it > be modified to use something else (chroot? switch_root?) to allow for this? Could you clarify what you’re doing? You’re trying to run guix-daemon and guix in the initramfs of some distro,

bug#60165: [1.4.0rc2] Installer doesn't properly render some non-Latin glyphs

Hi, "pelzflorian (Florian Pelz)" skribis: > is it too late to replace by font-gnu-unifont to fix CJK fonts? Oh sure. Could you send a patch? That’ll be in the next release… Thanks, Ludo’.

bug#60164: GNU Guix 1.4.0rc2 available for testing!

Hi Wolf, Wolf skribis: > I booted up the installer under qemu (that is how far my current > knowledge of guix allows me to test :) ), and I did notice that the > first "weird" language is not rendered properly under 1.4.0rc2. I > attached screenshots of 1.3.0 installer and 1.4.0rc2 installer.

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

After spending a few more hours on this, I got convinced that upon restarting guix-daemon, even though we had restored /var/guix/db/db.sqlite, the presence of stale db.sqlite-{wal,shm} files could lead sqlite to do as if transactions in the WAL file had been committed. Commit

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

"pelzflorian (Florian Pelz)" skribis: > I saw a comment >> void LocalStore::registerValidPaths(const ValidPathInfos & infos) >> { >> /* SQLite will fsync by default, but the new valid paths may not be >> fsync-ed. >> * So some may want to fsync them before registering the validity, at

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Ludovic Courtès skribis: > I did reproduce the issue in a VM by running “ifconfig ens3 down” in a > tty, or by killing the ‘guix substitute’ process, to cause failure of > ‘guix system init’. In that case the database is indeed restored, but I > occasionally get errors like “/gnu

bug#60104: Hiccups installing GNU Guix 1.4.0rc2 system

Hi, "J. Sims" skribis: > Ludovic Courtès wrote: > >> What’s crypttab? At which point exactly does this screen appears: >> before GRUB, after GRUB, once the Linux kernel has booted? > > crypttab is some part of the LUKS encryption stuff. This appears to be a

bug#60154: ‘guix substitute’ gets stuck when connection goes down

As noted while debugging , turning off networking while ‘guix substitute’ is downloading (be it with “ifconfig X down” or by physically unplugging the cable) leads it to be stuck in ‘read’ or ‘recvfrom’ for a long time. Most likely this can be addressed by

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Moin! "pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> One finding: when hitting C-c, the dynamic-wind exit handler (the one >> that restores the database and umounts the cow store) is *not* executed. > > Impressive findings. > > Now

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Hi, "pelzflorian (Florian Pelz)" skribis: > Desperately I tried also adding fsync, to no avail, both issues remain. > Non-working patch attached. > > Maybe dynamic-wind is an inappropriate pattern here? > > If I interrupt installation using Ctrl-C (which I normally don’t, > instead I unplug

bug#60116: ‘herd stop guix-daemon’ doesn’t stop running sessions

Suppose you run a bunch of clients, ‘guix shell’, ‘guix build’, whatever. For each of these connections, guix-daemon creates a child process to handle it. (You can see them as “SessionPID” in the output of ‘guix processes’.) ‘herd stop guix-daemon’ won’t stop these guix-daemon child processes,

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

Hi Florian, "pelzflorian (Florian Pelz)" skribis: > Hello Ludo, sorry to say I attempted your modprobe patch that uses > (parameterize ((default-environment-variables … Bah, turns out it’s trickier than this. See . I figured I could test it in a VM. I

bug#60104: Hiccups installing GNU Guix 1.4.0rc2 system

Hi, "J. Sims" skribis: > I managed to successfully install the GNU Guix 1.4.0rc2 system iso on > an HP Dev One laptop (with help from USB stuff for > networking). Everything mostly went as expected, except after the > installation I got a screen saying crypttab couldn't find a specific >

bug#60106: [Shepherd 0.9.3] ‘system*’ replacement cannot be passed environment variables

As we found out while debugging , the Shepherd 0.9.3, with its ‘system*’ replacement (aka. ‘spawn-command’), makes it very hard to spawn a command with different environment variables. The following options don’t work: • Changing shepherd’s own environment

bug#60056: [PATCH RFC 1/6] build: Add gnu-build-system v2.

Hi! Maxim Cournoyer skribis: > * guix/build/gnu-build-system2.scm: New file. > * Makefile.am (MODULES): Register it. > * guix/build-system/gnu2.scm: Use it. I won’t be able to review it in the coming days; a quick note: • Changes to ‘gnu-build-system’ need thorough review, so don’t

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

/final.scm @@ -1,6 +1,6 @@ ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2018, 2020 Mathieu Othacehe -;;; Copyright © 2019, 2020 Ludovic Courtès +;;; Copyright © 2019, 2020, 2022 Ludovic Courtès ;;; ;;; This file is part of GNU Guix. ;;; @@ -196,14 +196,15 @@ (define

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

"pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> Do you see hints as to whether uvesafb gets loaded? >> >> You can do that by adding “console=ttyS0” to the kernel arguments and by >> passing ‘-serial stdio’ to QEMU. > > This serial ou

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

"pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> So my guess is that things will be much better if we swap these two >> lines. > > This was helpful, but not enough. Sorry, I think I wasn’t thinking at full speed. There needs to be zer

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

"pelzflorian (Florian Pelz)" skribis: > (provision '(maybe-uvesafb)) > (requirement '(file-systems)) > (start #~(lambda () > -(or (file-exists? "/dev/fb0") > -(invoke #+(file-append kmod "/bin/modprobe") > -

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

"pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> Specifically, here’s the minimal change we should test:[…] >> +(unless (file-exists? "/dev/fb0") >> + (setenv "LINUX_MODULE_DIRECTORY&q

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

Ludovic Courtès skribis: > So you may need to add: > > (setenv "LINUX_MODULE_DIRECTORY" "/run/booted-system/kernel/lib/modules") Specifically, here’s the minimal change we should test: diff --git a/gnu/system/install.scm b/gnu/system/install.scm index f6f1923121

bug#59913: [tentative PATCH] Failure to guix pull on aarch64 since recent make-linux-libre*

Hi, Pierre Langlois skribis: > I'm not sure I follow, I'd suggest to revert the revert and then apply a > fix in the same commit, that way it can easily be reverted again if it's > problematic, that's probably what you meant already? Sounds good to me. The commit log can be similar to the

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Hi again, Ludovic Courtès skribis: > It looks like the store is in a broken state, with its database not > matching its actual contents. The ‘install-system’ procedure is > supposed to protect against that by making a backup of the database > before starting the installation a

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Hi, "pelzflorian (Florian Pelz)" skribis: > I now uploaded an installer-dump-bade9971 of me reproducing the issue. Here’s the relevant syslog excerpt (this was with 1.4.0rc1) where we can see the point where you unplugged the Ethernet connection: --8<---cut

bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails

Hi Florian, "pelzflorian (Florian Pelz)" skribis: > Just now I tried the installer on an AMD desktop but the graphical > installer screen stays black. Same on an AMD laptop. After switching > to another TTY, dmesg tells me this: > >> [ 11.625264] shepherd[1]: Service host-name has been

bug#59884: ‘gui-installed-desktop-os-encrypted’ test intermittent failures

Ludovic Courtès skribis: > Yeah. One possibility is timing: (restart-service 'guix-daemon) kills > the daemon’s process group, waits for the group leader to terminate, > then starts the daemon. I think there’s a possibility that other > processes in the group (like a ‘guix subst

bug#59823: [1.4.0rc1] Installer fails to identify installation device on Ventoy-made images

¡Hola! Mathieu Othacehe skribis: > Yeah, I agree that open-pipe would be a bit clearer, but as this is > already tested as-is plus we'll switch to the ioctl after the release, I > think we can proceed. Yup, that makes sense to me. > Fixed, added a few comments and pushed. Thank you! Ludo’.

bug#54447: cuirass: missing derivation error

Mathieu Othacehe skribis: > A lot of builds, among them ~20 system tests[1], are failing with: > "cannot build missing derivation > ?/gnu/store/hs6kp1lqgymhyp3jndc0dsp0pn4psgv0-gui-installed-desktop-os-encrypted.drv?" > errors. > > Those derivations are present on the CI head node. This means

bug#48468: substitute server connection timeout

Hi, Ludovic Courtès skribis: > Mathieu Othacehe skribis: [...] >> curl https://ci.guix.gnu.org/lwv2pl0m6dkf6bkzip755w5p71g5akq4.narinfo >> We're baking it: /lwv2pl0m6dkf6bkzip755w5p71g5akq4.narinfo > > Yes, but derivations (.drv) are depend only on “sources” (like >

bug#59884: ‘gui-installed-desktop-os-encrypted’ test intermittent failures

Hi, Mathieu Othacehe skribis: > I spent days on that issue before. It used to show up on all installer > tests, and even on real hardware, then > 8ce6f4dc2879919c12bc76a2f4b01200af97e01 mitigated it. > > The installation is now made in a container to make sure that we are > later on able to

bug#59823: [1.4.0rc1] Installer fails to identify installation device on Ventoy-made images

Hi! Mathieu Othacehe skribis: >>From 0afda5b3ed32e73bece9db96ab970d83f9f2e74b Mon Sep 17 00:00:00 2001 > From: Mathieu Othacehe > Date: Thu, 8 Dec 2022 13:24:02 +0100 > Subject: [PATCH 1/1] installer: Detect mapped installation devices. > > Fixes: > > *

bug#59922: [1.4.0rc1 installer] Progress bar for file copy not shown

Ludovic Courtès skribis: > When installing from RC1, the progress bar that’s normally shown after > the “initializing operating system under '~a'...” message doesn’t show > up, or rather it shows up all of a sudden at the end, suggesting it’s > being buff

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Ludovic Courtès skribis: > 2. That led me to a confusing error screen says “Command cryptsetup > failed” with Ignore/Abort/Retry buttons. Actually it’s “External command ("cryptsetup" "close" "cryptroot") exited with code 5” and “cryptroot device is busy”. Ludo’.

bug#59922: [1.4.0rc1 installer] Progress bar for file copy not shown

When installing from RC1, the progress bar that’s normally shown after the “initializing operating system under '~a'...” message doesn’t show up, or rather it shows up all of a sudden at the end, suggesting it’s being buffered. Everything’s fine when running “guix system init” in a terminal.

bug#59784: [version 1.4.0rc1] Retrying a failed install fails

Hi, "pelzflorian (Florian Pelz)" skribis: > I aborted graphical system installation (Ctrl-C), retried the > installation and got this: > > shepherd: Service guix-daemon has been stopped. > shepherd: Service guix-daemon has been started. > guix system: Fehler: opening file >

bug#49205: [services]: nginx doesn't restart after guix system reconfigure

Hi, Tobias Geerinckx-Rice skribis: > Raghav Gururajan via Bug reports for GNU Guix 写道： >> Throw to key `%exception' with args `("#< program: >> \"/gnu/store/g6nhdp7i1sr51anq86hd6adrsm5ha857-nginx-1.21.0/sbin/nginx\" >> arguments: (\"-c\" >>

bug#59781: [version 1.4.0rc1] install.sh script should authorize bordeaux

keys->acl’ to deduplicate entries. Maybe something along these lines: diff --git a/guix/pki.scm b/guix/pki.scm index 6326e065e9..c5b2fb9634 100644 --- a/guix/pki.scm +++ b/guix/pki.scm @@ -1,5 +1,5 @@ ;;; GNU Guix --- Functional package management for GNU -;;; Copyright © 2013, 2014, 2016 Lud

bug#59781: [version 1.4.0rc1] install.sh script should authorize bordeaux

Hi, "pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> If there are no objections I’d like to push to ‘master’ and >> ‘version-1.4.0’ this modified version of your patch. > > Thank you two, this patch works (on 1.3.0 only ci.guix.gnu.org, on &

bug#59781: bug#50892: [PATCH] guix-install.sh: Authorize all project build farms at once.

: [PATCH] guix-install.sh: Authorize all project build farms at once. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * etc/guix-install.sh (sys_authorize_build_farms): Iterate over all hosts. Co-authored-by: Ludovic Courtès --- etc/guix-install.sh | 22 ++

bug#48468: substitute server connection timeout

Hi, Mathieu Othacehe skribis: >> /gnu/store/qmzr030rzgikdxv3g9msqv0l8qp5j6y2-btrfs-raid-root-os.drv, >> which was marked as failed earlier today due to missing .drv. It’s a >> 4KiB file, and the cache-bypass-threshold is ‘guix publish’ is typically >> set to something much higher than that.

bug#59864: emacs-guix

Ludovic Courtès skribis: > I’ll fix this by upgrading the ‘guix’ package and/or merging the (guix > records) bit in the ‘version-1.4.0’ branch. Done in 81191e3410cc00c6438f532599dd0b96d521982f. Ludo’.

bug#59864: emacs-guix

Hi, Amade Nemes Gmail skribis: > I've updated my guix version today and found that most emacs-guix > interactive commands no longer work. For example, guix-packages-by-name > throws: > > guix-geiser-eval: Error in evaluating guile expression: > ice-9/boot-9.scm:1685:16: In procedure

bug#59884: ‘gui-installed-desktop-os-encrypted’ test intermittent failures

Hi, The ‘gui-installed-desktop-os-encrypted’ test fails intermittently like so: --8<---cut here---start->8--- Dec 7 12:14:01 localhost installer[253]: ^M^[[Kguix system: ^[[1m^[[0mbootloader successfully installed on /dev/vda^M Dec 7 12:14:01 localhost

bug#48468: substitute server connection timeout

Hi, Mathieu Othacehe skribis: >> You mentioned on IRC that nginx logs show that ‘guix publish’ times out. >> Looking at /var/log/nginx/error.log, I see “Connection reset by peer” >> and “Broken pipe”, which could indicate that the client closed the >> connection (which was open) prematurely,

bug#59781: [version 1.4.0rc1] install.sh script should authorize bordeaux

Ludovic Courtès skribis: > Tobias Geerinckx-Rice skribis: > >> pelzflorian (Florian Pelz) 写道： >>> Could you make install.sh add bordeaux to /etc/guix/acl? It is >>> important especially on ARM. >> >> If you mean guix-install.sh: I did so ages ago

bug#59423: Invalid 'location' field generated in dovecot configuration

Hi, Maxim Cournoyer skribis: >> We’ll have to discuss the implications of a possible move to >> ‘define-configuration’. For example, ‘define-configuration’ cannot >> report missing field values (for fields that lack a default value) at >> macro-expansion time, contrary to plain

bug#59781: [version 1.4.0rc1] install.sh script should authorize bordeaux

Hi! Tobias Geerinckx-Rice skribis: > pelzflorian (Florian Pelz) 写道： >> Could you make install.sh add bordeaux to /etc/guix/acl? It is >> important especially on ARM. > > If you mean guix-install.sh: I did so ages ago, but something (valid) > stopped me from pushing it. > > Now I can't for the

bug#59780: [version 1.4.0rc1] reconfigure fails

"pelzflorian (Florian Pelz)" skribis: > Tobias Geerinckx-Rice writes: >> pelzflorian (Florian Pelz) 写道： >>> Having installed the 1.4.0rc1 installer image: After guix pull, it >>> failed to reconfigure, because master is an unrelated commit. >> >> Hah. This should indeed be mentioned in calls

bug#48468: substitute server connection timeout

Hi, Mathieu Othacehe skribis: > I hoped that it would decrease the load of the Cuirass publish server > that was flooded by worker connections. While the situation is better, > there are still a lot of substitute timeout errors on Cuirass. > > I have also observed those timeouts using the

bug#58247: Using guix time-machine results in unsupported manifest format error

Hi, zimoun skribis: > This issue is about the upgrade of manifest version from 3 to 4. For > references, > > > > On Mon, 03 Oct 2022 at 00:10, zimoun wrote: > >> Well, I do not know if a fix is possible. The issue is a >> backward compatibility

bug#59423: Invalid 'location' field generated in dovecot configuration

Maxim Cournoyer skribis: > Thanks for this extra bit of information and for spotting this usage. I > think "location" is likely to conflict for the general purpose > 'define-configuration' generated records, so I've renamed the "location" > *accessor* to "source-location". Thank you. It

bug#59423: Invalid 'location' field generated in dovecot configuration

Ludovic Courtès skribis: > Maxim Cournoyer skribis: [...] >> No :-). I meant why do we even set a default accessor for the *source >> location* information (in the (gnu service configuration) macros); it's >> that one that doesn't seem to get used (or I'm blind to

bug#59512: gtk-4.8.1 grafting fails

Hi, Marek Paśnikowski skribis: > I should be able to heal the system by deleting the bit-flipped > file and reinstalling gtk. Does Guix have the ability to remove or > rewrite a specific file in its store? The file is rooted in the > system configuration - not in a profile. ‘guix gc

bug#59423: Invalid 'location' field generated in dovecot configuration

Hi Maxim, Maxim Cournoyer skribis: > Ludovic Courtès writes: [...] >>>> That generates two accessors called ‘namespace-configuration-location’. >>>> The second one shadows the first one. >>> >>> Yes. You didn't address my question direc

bug#59717: ‘guix’ package fails to build on armhf-linux (OOM)

Hi, "pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> [ 76%] GUILEC gnu/packages/uucp.go >> [ 76%] GUILEC gnu/packages/valgrind.go >> [ 76%] GUILEC gnu/packages/version-control.go >> [ 76%] GUILEC gnu/packages/video.go >> GC

bug#59717: ‘guix’ package fails to build on armhf-linux (OOM)

As of 1bc9d5222f9053fd0ace7b92df0ef9548707cf41 (version-1.4.0), the ‘guix’ package fails to build on armhf-linux, running out of memory: --8<---cut here---start->8--- [ 75%] GUILEC gnu/packages/toolkits.go [ 76%] GUILEC gnu/packages/tor.go [ 76%] GUILEC

bug#59423: Invalid 'location' field generated in dovecot configuration

Hi Maxim, Maxim Cournoyer skribis: >> We have this: >> >> (define-record-type* #,(id #'stem #'< #'stem #'>) >>stem >>#,(id #'stem #'make- #'stem) >>#,(id #'stem #'stem #'?) >>#,@(map (lambda (name getter def) >>

bug#59512: gtk-4.8.1 grafting fails

Hi, Marek Paśnikowski skribis: > grafting '/gnu/store/vp4ybqhxdrf4b2fk37c0s72g6iafqsmz-gtk-4.8.1-doc' -> > '/gnu/store/7hfq1hbhfsmzjil433cjd8mngvxd05xv-gtk-4.8.1-doc'... > ERROR: In procedure fport_fill_input: Input/output error This indicates an error while writing to your storage device,

bug#56398: (guix git) fails to check out repos with nested submodules

Hi André, André Batista skribis: > qui 24 nov 2022 às 12:17:19 (1669303039), nan...@riseup.net enviou: >> Upstream issue #6433 > > Fixed on upstream commit 936b184e7494158c20e522981f4a324cac6ffa47 Excellent. Let’s close this bug once we’ve updated the ‘libgit2’ package to a version that

bug#30948: [PATCH core-updates] guix: Reap finished child processes in build containers.

Maxim Cournoyer skribis: > Ludovic Courtès writes: [...] >> If I write: >> >> (gexp->derivation "foo" #~(mkdir #$output)) >> >> I can be sure that my derivation depends on nothing but (default-guile). >> This is important for tests

bug#59423: Invalid 'location' field generated in dovecot configuration

Hi, Maxim Cournoyer skribis: >>> The issue seems to be with the serialization of the >>> object nested in the >>> record. I tried this at the REPL: >>> >>> scheme@(guile-user)> ,m (gnu services mail) >>> scheme@(gnu services mail)> (namespace-configuration (name "inbox")) >>> $8 = #< name:

bug#59616: Texinfo 6.7 test hangs on i586-gnu (GNU/Hurd)

Hi, Ludovic Courtès skribis: > The childhurd only has this: > > ludo@childhurd /tmp/guix-build-texinfo-6.7.drv-0/texinfo-6.7/info$ ls -l > /dev/ptyp* > crw--w 1 root tty 0, 0 Nov 26 16:05 /dev/ptyp0 > crw--w 1 ludo tty 0, 0 Nov 26 16:05 /dev/ptyp1 > crw--- 1

bug#59515: nginx: Fails to start on boot while upstream service is not yet running

Jonathan Brielmaier skribis: > I added `(shepherd-requirement '(radicale))` to my nginx-configuration. > Sadly the issue is not fixed, the situation is the same as before. > > I assume that radicale takes a fracture of a second to start. And nginx > starts faster up. See this small experiment:

bug#59616: Texinfo 6.7 test hangs on i586-gnu (GNU/Hurd)

The ‘t/malformed-split.sh’ test of Texinfo 6.7 hangs on GNU/Hurd (in a childhurd) as of commit 78f03567f44f704dfbc03cb64368aa42a01e78ad. The test invokes its ‘pseudotty’ program, which creates a pseudo-terminal using ‘posix openpt’. That call fails when not running as root in a childhurd:

bug#59615: Intro video refers to Freenode

The “Asking for help” video refers to Freenode (instead of Libera.Chat): https://guix.gnu.org/en/videos/2020/asking-for-help/ There are screenshots, audio, and slides that would need to be updated. Ludo’.

bug#58803: coreutils-8.32 test failure on i586-gnu

Hi, Samuel Thibault skribis: > It seems that replying on the web interface didn't work, so replying > again here by mail. Weird. > Ludovic Courtès, le mer. 26 oct. 2022 19:20:07 +0200, a ecrit: >> ludo@childhurd ~$ mkfifo fifo >> ludo@childhurd ~$ ls -l fifo >> pr

bug#30948: [PATCH core-updates] guix: Reap finished child processes in build containers.

Hi, Maxim Cournoyer skribis: >> My view is just that this mechanism belongs in “user code”, not in the >> low-level mechanisms such as ‘build-expression->derivation’ and >> ‘gexp->derivation’. It’s a matter of separation of concerns. > > Why? On my Guix System, such signal handling is handled

bug#59493: cuirass-remote-worker crash

Hi, Mathieu Othacehe skribis: >> To me, ideally this would be either multi-threaded or Fiberized. The >> latter would be more fruitful but what might be difficult is >> guile-simple-zmq integration with Fibers (but maybe not: zmq_getsockopt >> + ZMQ_FD lets us get the file descriptor of a

bug#59508: mpv compiled without x11 support

Hi, Saku Laesvuori skribis: > The mpv package from (gnu packages video) is compiled without x11 > support and fails with: > > [vo/gpu] VT_GETMODE failed: Inappropriate ioctl for device > [vo/gpu/opengl] Failed to set up VT switcher. Terminal switching will be > unavailable. > [vo/gpu] Failed

bug#59519: LibreOffice 7.3.5.2 fails to build on i686-linux

The end of the log of the build for commit 2c9635cb47b0f52de635e93ebd137f1f7191c5fd looks like this: --8<---cut here---start->8--- [build LNK] Executable/unopkg.bin [build DEP] LNK:Library/libicglo.so [build LNK] Library/libicglo.so [build MOD] shell [build

bug#59493: cuirass-remote-worker crash

Hi, Mathieu Othacehe skribis: >> 2022-11-21 14:27:24 1685:16 0 (raise-exception _ #:continuable? _) >> 2022-11-21 14:27:24 >> 2022-11-21 14:27:24 ice-9/boot-9.scm:1685:16: In procedure raise-exception: >> 2022-11-21 14:27:24 Throw to key `match-error' with args `("match" "no >> matching

bug#59425: guix shell --container fails to mount host filesystem

Hi, bbb ee skribis: > dev_1@dev_1 /mnt/recoverData$ guix shell --container coreutils -- echo Elmo > guix shell: error: mount: mount "/mnt/recoverData" on > "/tmp/guix-directory.ut68VE//mnt/recoverData": Invalid argument > ``` > > ## environment > ``` > $ uname -a > Linux dev_1 5.18.18 #1 SMP

bug#59510: cuirass-remote-server: put-char encoding failed

Hi, Mathieu Othacehe skribis: > On Cuirass 1.1.0-13.1341725, the fetch workers are experimenting the > following issue: Is this a regression? > 2022-11-22 00:28:15 In cuirass/scripts/remote-server.scm: > 2022-11-22 00:28:15415:12 3 (_) > 2022-11-22 00:28:15 387:7 2 (run-fetch _) >

<    2   3   4   5   6   7   8   9   10   11   >