GNU bug report logs - #71828
Commands that pull channels don't cleanly report errors

Previous Next

Package: guix;

Reported by: Richard Sent <richard <at> freakingpenguin.com>

Date: Fri, 28 Jun 2024 20:21:02 UTC

Severity: normal

To reply to this bug, email your comments to 71828 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#71828; Package guix. (Fri, 28 Jun 2024 20:21:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Richard Sent <richard <at> freakingpenguin.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Fri, 28 Jun 2024 20:21:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Richard Sent <richard <at> freakingpenguin.com>
To: bug-guix <at> gnu.org
Subject: Commands that pull channels don't cleanly report errors
Date: Fri, 28 Jun 2024 16:20:27 -0400
Hi Guix!

When a command such as guix time-machine pulls a channel, if there is
invalid scheme code in, say, the .guix-authorizations file, the error
message reported to the user doesn't make it clear where the problem is.

--8<---------------cut here---------------start------------->8---
gibraltar :( temp$ guix time-machine -C channels.scm -- describe
Updating channel 'pita-packs' from Git repository at 'https://codeberg.org/JetpackJackson/guix-pita-packs.git'...
Authenticating channel 'pita-packs', commits 2970fc3 to 429703d (3 new commits)...
▕███████████████████████████████████████████████████▉                                                                                                        ▏ice-9/boot-9.scm:1685:16: In procedure raise-exception:
#<unknown port>:5:1: unexpected end of input while searching for: )
--8<---------------cut here---------------end--------------->8---

In this case, pita-pack's .guix-authorizations file is missing ending
parenthesis.

This error message should be improved to say

a) What channel is causing the problem

b) What file we're parsing that threw the error

See some of the chat log here:
https://logs.guix.gnu.org/guix/2024-06-28.log.

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.




Information forwarded to bug-guix <at> gnu.org:
bug#71828; Package guix. (Fri, 28 Jun 2024 23:01:02 GMT) Full text and rfc822 format available.

Message #8 received at 71828 <at> debbugs.gnu.org (full text, mbox):

From: jgart <jgart <at> dismail.de>
To: 71828 <at> debbugs.gnu.org
Cc: Richard Sent <richard <at> freakingpenguin.com>
Subject: Re: Commands that pull channels don't cleanly report errors
Date: Fri, 28 Jun 2024 18:00:17 -0500
Hi,

That's a great idea. Do you want to send a patch for that?

all best,

jgart




This bug report was last modified 111 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.