GNU bug report logs - #35883
guix import hackage: recursive import fails silently on errors

Previous Next

Package: guix;

Reported by: Robert Vollmert <rob <at> vllmrt.net>

Date: Fri, 24 May 2019 14:06:01 UTC

Severity: normal

To reply to this bug, email your comments to 35883 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#35883; Package guix. (Fri, 24 May 2019 14:06:03 GMT) Full text and rfc822 format available.
Acknowledgement sent to Robert Vollmert <rob <at> vllmrt.net>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Fri, 24 May 2019 14:06:03 GMT) Full text and rfc822 format available.

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

From: Robert Vollmert <rob <at> vllmrt.net>
To: bug-guix <at> gnu.org
Subject: guix import hackage: recursive import fails silently on errors
Date: Fri, 24 May 2019 15:59:07 +0200

$ guix import hackage not-a-package
guix import: error: failed to download cabal file for package 'not-a-package’
$ echo $?
1
$ guix import hackage -r not-a-package
$ echo $?
0

It might be argued that the error code is fine, since in general it could be
useful for the recursive import to keep going past failures. However it seems
such failures should be logged, and ideally written to standard output in some
form like

(error “import failed: <package name>”)

so they could be found clearly in the generated expression.
This bug report was last modified 6 years and 19 days ago.

Previous Next

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