all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: 71828@debbugs.gnu.org
Subject: bug#71828: Commands that pull channels don't cleanly report errors
Date: Fri, 28 Jun 2024 16:20:27 -0400	[thread overview]
Message-ID: <87le2ovmyc.fsf@freakingpenguin.com> (raw)

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.




             reply	other threads:[~2024-06-28 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 20:20 Richard Sent [this message]
2024-06-28 23:00 ` bug#71828: Commands that pull channels don't cleanly report errors jgart via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le2ovmyc.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=71828@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.