all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Philip Munksgaard" <philip@munksgaard.me>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 48700@debbugs.gnu.org
Subject: bug#48700: guix import fails with unexpected token
Date: Thu, 10 Jun 2021 15:29:32 +0200	[thread overview]
Message-ID: <a083bbd7-736f-4c58-a49d-8bcdb969fcd6@www.fastmail.com> (raw)
In-Reply-To: <CAJ3okZ3Pdz3nTcaapv1+=qgMY2J83Np6W2ATNibVupjGsko92A@mail.gmail.com>

On Thu, 10 Jun 2021, at 15:02, zimoun wrote:
> On Thu, 10 Jun 2021 at 14:22, Philip Munksgaard <philip@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 :-)




      reply	other threads:[~2021-06-10 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 13:08 bug#48700: guix import fails with unexpected token Philip Munksgaard
2021-05-27 19:54 ` zimoun
2021-05-30 16:38 ` Philip Munksgaard
2021-06-10  9:41   ` zimoun
2021-06-10 12:20 ` Philip Munksgaard
2021-06-10 13:02   ` zimoun
2021-06-10 13:29     ` Philip Munksgaard [this message]

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=a083bbd7-736f-4c58-a49d-8bcdb969fcd6@www.fastmail.com \
    --to=philip@munksgaard.me \
    --cc=48700@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.