GNU bug report logs - #48700
guix import fails with unexpected token

Previous Next

Package: guix;

Reported by: "Philip Munksgaard" <philip <at> munksgaard.me>

Date: Thu, 27 May 2021 14:47:01 UTC

Severity: normal

Merged with 48701

Done: "Philip Munksgaard" <philip <at> munksgaard.me>

Bug is archived. No further changes may be made.

Full log


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

From: "Philip Munksgaard" <philip <at> munksgaard.me>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 48700 <at> debbugs.gnu.org
Subject: Re: bug#48700: guix import fails with unexpected token
Date: Thu, 10 Jun 2021 15:29:32 +0200
On Thu, 10 Jun 2021, at 15:02, zimoun wrote:
> On Thu, 10 Jun 2021 at 14:22, Philip Munksgaard <philip <at> munksgaard.me> wrote:
> 
> > If I understand you correctly, you're saying that this issue is an instance of bug#44115 because we get a backtrace instead of a nice error. I agree that the backtrace is ugly, but in this case the error shouldn't happen at all because all the recursively imported packages exist.
> 
> Your point is that parsing the Cabal file of the package "versions"
> fails.  Mine is, somehow, instead of an ugly backtrace (whatever the
> reason), the error for "guix import hackage futhark -r" should be:
> 
>   Syntax error: unexpected token : common (at line 36, column 0)
>   Syntax error: unexpected end of input
>   guix import: error: échec du téléchargement du fichier cabal du
> paquet « versions »
> 
> as it is for "guix import hackage versions".
> 

Good point, I agree that would be nicer. The backtrace was not my concern when submitting this bug, but it doesn't really matter as long as both issues are fixed :-)




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

Previous Next


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