GNU bug report logs - #51463
Lack of error message in several guix subcommands

Previous Next

Package: guix;

Reported by: Alice BRENON <alice.brenon <at> ens-lyon.fr>

Date: Thu, 28 Oct 2021 17:16:02 UTC

Severity: important

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #12 received at 51463-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Alice BRENON <alice.brenon <at> ens-lyon.fr>
Cc: 51463-done <at> debbugs.gnu.org
Subject: Re: bug#51463: Lack of error message in several guix subcommands
Date: Sun, 07 Nov 2021 23:14:36 +0100
Hi Alice,

Alice BRENON <alice.brenon <at> ens-lyon.fr> skribis:

> I was giving guix shell a try today and noticed this annoying lack of
> relevant feedback from the tool: when running on a particularly
> malformed guix.scm, either by auto-loading or by explicitely passing -f
> guix.scm, guix shell returned in error ($? == 1) without printing any
> error message, which is a bit unhelpful.

I believe commit 4d59596a1c5f6b20870e619cbf67068ac7dd64ff fixes it (the
issue affected ‘read-error’ exceptions for reasons other than missing
closing parentheses).

Let me know if anything’s amiss.

Thanks!

Ludo’.




This bug report was last modified 3 years and 192 days ago.

Previous Next


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