GNU bug report logs - #23479
CRAN importer: do not print backtrace when package name is invalid

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ricardo Wurmus <rekado <at> elephly.net>
Subject: bug#23479: closed (CRAN importer: do not print backtrace when
 package name is invalid)
Date: Sat, 17 Dec 2016 18:57:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#23479: CRAN importer: do not print backtrace when package name is invalid

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 23479 <at> debbugs.gnu.org.

-- 
23479: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23479
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: 23479-done <at> debbugs.gnu.org
Subject: CRAN importer: do not print backtrace when package name is invalid
Date: Sat, 17 Dec 2016 19:55:57 +0100

Fixed in commit fdbc84b056683204c5832d3740d9b109f31f7cb9.

[Message part 3 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guix <at> gnu.org
Subject: CRAN importer: do not print backtrace when package name is invalid
Date: Sun, 08 May 2016 18:44:12 +0200

The CRAN importer (and possibly other importers) print ugly backtraces
when a package is to be imported that does not exist.  This can happen
when the user mistypes the name or when the package is available on
Bioconductor rather than CRAN.

To fix this we should catch 404 errors in the “fetch-description”
procedure in “guix/import/cran.scm”.

~~ Ricardo

Previous Next

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