bug#73371: Retry worked

I ran the command again, and it succeeded this time.

bug#73192: [PATCH] gnu: icedove-l10n: Fix build.

user guix tags 73192 + patch thanks

bug#73192: [PATCH] gnu: icedove-l10n: Fix build.

Fixes * gnu/packages/gnuzilla.scm (make-l10n-package)[arguments]<#:phases>: On 'build phase unconditionally use 'system*' to invoke 'mach', as 'invoke' does not work for icedove any longer. Reported-by: bdju . --- gnu/packages/gnuzilla.scm | 12 +--- 1

bug#73362: Install failed

The installer says it has uploaded installer-dump-b49f8af

bug#73371: guix system reconfigure -- hash mismatch for world

Trying to build my system after pulling the latest guix fails with sha256 hash mismatch for /tmp/guix-tests/store/53whz0jlbbbnk5cysp8xz3amx7njyass-world: expected hash: 0nq3k75cmck9v9giblhpqrgspbdjv6v019djk4x2jj0bn6zpvsvm actual hash: 0a7pd3rizm1qb3kz1ad1wzrijrhwsnq3lj7

bug#72625: Status: emacs-magit: autoload issue

A non-guix user on #emacs tested this for me and is not able to reproduce the problem on his distro. Said he was running Emacs 31.0.50 and Magit 4.0.0. He also tried 4.1.0. So it is seeming like a guix-specific issue. -- Christopher Howard

bug#72625: emacs-magit: autoload issue

I see this error also when running Emacs 29.4 from the guix package. I used "emacs -q" for the test so it is not an init.el file issue. -- Christopher Howard

bug#72625: emacs-magit: autoload issue

Nicolas Goaziou writes: >> I see magit 4.0 was just released, so if somebody wants to update the >> package, maybe the problem would go away. > > Magit was updated to 4.0 a few hours ago. I cannot reproduce it (but > I didn't try before the update). Did this change anything on your side? > Hi, I

bug#73368: OCaml build failure on i686

Hello OCaml team, There is what looks like a non-deterministic failure early in the ‘check’ phase of ocaml@4.09 and ocaml@5.0 on i686-linux: --8<---cut here---start->8--- starting phase `check' make -C testsuite all make runtime-all make[1]: Entering directory

bug#73366: The syslinux package is not reproductible

Hi, While debugging an unrelated reproducibility issue with an older mtools version I got the idea of testing packages that uses mtools (with the current Guix version) and it turn out not to be reproductible: $ guix challenge syslinux /gnu/store/9gq6bgralqfd1yzkywnr8pkx5il5s99c-syslinux-6.04-pre-

bug#73249: Recovering journal at boot time after reconfiguring the system with Sway

Hi Ludo, yes, it's only after guix system reconfigure. Thank you! Original Message On Sep 19, 2024, 15:13, Ludovic Courtès wrote: > Hi, Oleander skribis: > I'm running Guix with Sway (v1.9) and ext4. When guix > system reconfigure is performed, a filesystem check is triggered

bug#72939: guix import crate produce broken package definition

Hi Aleksandr, (Cc’ing potentially interested parties.) Aleksandr Vityazev skribis: > guix import crate sanakirja-core [...] > (arguments > `(#:cargo-inputs ,(list ("rust-crc32fast" ,rust-crc32fast-1) > ("rust-ed25519-zebra" ,rust-ed25519-zebra-2) >

bug#72792: error: activate-privileged-programs: unbound variable

Hi Roman, Roman Scherer skribis: > with the latest commit on master > > ``` > root@guix ~# guix describe > Generation 13 Aug 24 2024 13:19:20(current) > guix d48af5c > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: master > commit: d48af5cca84914d44b032d

bug#72792: error: activate-privileged-programs: unbound variable

Hi Ludo and Tobias, yes, I think the issue has been resolved in the meantime. On Thu, Sep 19, 2024, 15:06 Ludovic Courtès wrote: > Hi Roman, > > Roman Scherer skribis: > > > with the latest commit on master > > > > ``` > > root@guix ~# guix describe > > Generation 13 Aug 24 2024 13:19:20(

bug#73249: Recovering journal at boot time after reconfiguring the system with Sway

Hi, Oleander <7059...@protonmail.com> skribis: > I'm running Guix with Sway (v1.9) and ext4. When guix system reconfigure is > performed, a filesystem check is triggered on next boot, showing the message: > "Recovering journal" and then "clean...". After this, the system boots just > fine. > >

bug#72277: home-shepherd is flooding tty

Hi, Dariqq skribis: > It would be nice to add an option to home-shepherd-configuration to > autolaunch the shepherd with --silent once it is available in a tagged > release. I believe we can make this change right away since 0.10.x supports ‘--silent’ (it doesn’t have any effect as of 0.10.5 bu

bug#72976: [PATCH v11] gnu: lxc: Update to 6.0.1

* gnu/packages/virtualization.scm (lxc): Update to 6.0.1. [source] Add patch lxc-static-link.patch. [build-system]: Change to meson-build-system. [inputs]: Add dbus. Add apparmor. [arguments]: Replace "--docdir=..." with "-Ddoc-path=...". Replace "--sysconfdir=/etc" with "-Ddistrosysconfdir=/etc".

bug#72976: [PATCH v10] gnu: lxc: Update to 6.0.1

* gnu/packages/virtualization.scm (lxc): Update to 6.0.1. [build-system]: Change to meson-build-system. [inputs]: Add dbus. Add apparmor. [arguments]: Replace "--docdir=..." with "-Ddoc-path=...". Replace "--sysconfdir=/etc" with "-Ddistrosysconfdir=/etc". Remove "--localstatedir=/var". Add "-Dinit