bug#50600: Reminder

Can someone review the patch?

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#59913: branch master updated: Revert "gnu: make-linux-libre*: Remove input labels."

Maxim Cournoyer writes: > Hi Pierre, > > Pierre Langlois writes: > >> Hi Maxim, >> >> guix-comm...@gnu.org writes: >> >>> This is an automated email from the git hooks/post-receive script. >>> >>> apteryx pushed a commit to branch master >>> in repository guix. >>> >>> The following commit(s)

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#59913: branch master updated: Revert "gnu: make-linux-libre*: Remove input labels."

Hi Pierre, Pierre Langlois writes: > Hi Maxim, > > guix-comm...@gnu.org writes: > >> This is an automated email from the git hooks/post-receive script. >> >> apteryx pushed a commit to branch master >> in repository guix. >> >> The following commit(s) were added to refs/heads/master by this

bug#59913: branch master updated: Revert "gnu: make-linux-libre*: Remove input labels."

Hi Maxim, guix-comm...@gnu.org writes: > This is an automated email from the git hooks/post-receive script. > > apteryx pushed a commit to branch master > in repository guix. > > The following commit(s) were added to refs/heads/master by this push: > new 0ffa501f2b Revert "gnu:

bug#44112:

Hi, Thank you for the follow up. On Fri, 25 Nov 2022 at 12:22, Hendursaga via Bug reports for GNU Guix wrote: > The patch[1] has been closed for some time, is there any other pending > patches blocking going forward? > > [1] https://github.com/slime/slime/issues/583 Indeed, but the package

bug#59072: guix pull bug report

Hi, On Sun, 06 Nov 2022 at 12:30, 范啟能 wrote: > -Backtrace: >18 (primitive-load > "/gnu/store/izm5wcncfddbm2a7a05jj50jn43wrfnp-compute-guix-derivation") > In ice-9/eval.scm: > 155:9 17 (_ _) > 159:9 16 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?) ?) > ?) ?) ?) ?) ?) ?) ?) ?)

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 buffered. Fixed in

bug#59926: request: lnav

Package request: lnav (the log navigator) Website: https://lnav.org/

bug#57878: Some further investigation

Hi everyone, On the occasion of a "guix pull", I looked into this issue again, because magit without ido-completing-read+ is less fun. Loading this package runs lots of compilation threads, but it does ultimately terminate, with an error: Debugger entered--Lisp error: (native-compiler-error

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#59864: closed (Re: bug#59864: emacs-guix )

False alarm, is working correctly today. Not sure why it was not working previously. I guess I skipped the tried and tested "have you tried turning it off and on again?" troubleshooting step:) Amade Nemes Gmail writes: > Hi Ludo, > > Thanks for the quick reply! Unfortunately I'm still getting

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

Hi, Tobias Geerinckx-Rice skribis: > (Ugh, this patch is so ugly, all to work around that triplication in > ~/.config/guix/current/share/guix/*.pub… Would it be OK for ‘guix > archive --authorize’ to silently ignore duplicate keys?) Oh, good point. I guess we could change ‘public-keys->acl’

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 > 1.4.0rc1 also bordeaux, except