From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 25138@debbugs.gnu.org, Federico Beffa <beffa@ieee.org>
Subject: bug#25138: failing hackage import
Date: Fri, 09 Dec 2016 21:57:49 +0100 [thread overview]
Message-ID: <87inqs7rci.fsf@gnu.org> (raw)
In-Reply-To: <87vauu7ceb.fsf@pc102091.liv.ac.uk> (Dave Love's message of "Thu, 08 Dec 2016 13:56:12 +0000")
Hi,
Dave Love <fx@gnu.org> skribis:
> With guix 20161208.12 I see the following, which would probably take me
> a while to debug as I don't know my way around. (With the 0.11.0
> version I got a different error without a backtrace. I upgraded after
> seeing a bug fix for hackage in the tracker.)
>
> $ guix import hackage -t darcs
> Backtrace:
> In ice-9/boot-9.scm:
> 160: 16 [catch #t #<catch-closure 11e6e40> ...]
> In unknown file:
> ?: 15 [apply-smob/1 #<catch-closure 11e6e40>]
> In ice-9/boot-9.scm:
> 66: 14 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 432: 13 [eval # #]
> In ice-9/boot-9.scm:
> 2404: 12 [save-module-excursion #<procedure 1206900 at ice-9/boot-9.scm:4051:3 ()>]
> 4056: 11 [#<procedure 1206900 at ice-9/boot-9.scm:4051:3 ()>]
> 1727: 10 [%start-stack load-stack ...]
> 1732: 9 [#<procedure 1219b70 ()>]
> In unknown file:
> ?: 8 [primitive-load "/gnu/store/hckw4cw3m6r55afrldhn9gf66wrznh7i-guix-0.11.0-8.8d12/bin/.guix-real"]
> In guix/ui.scm:
> 1222: 7 [run-guix-command import "hackage" "-t" "darcs"]
> In guix/scripts/import.scm:
> 110: 6 [guix-import "hackage" "-t" "darcs"]
> In guix/scripts/import/hackage.scm:
> 110: 5 [guix-import-hackage "-t" "darcs"]
> In guix/import/hackage.scm:
> 247: 4 [hackage->guix-package "darcs" #:include-test-dependencies? ...]
> 113: 3 [hackage-fetch "darcs"]
> In guix/import/cabal.scm:
> 580: 2 [read-cabal #<input: r6rs-custom-binary-input-port 38ef8f0> #f]
> In system/base/lalr.upstream.scm:
> 1956: 1 [___run]
> 1851: 0 [___push 1 6 ...]
>
> system/base/lalr.upstream.scm:1851:2: In procedure ___push:
> system/base/lalr.upstream.scm:1851:2: Wrong number of arguments to #<procedure ___push (delta new-category lvalue tok)>
I’m seeing a different error:
--8<---------------cut here---------------start------------->8---
$ git describe
v0.11.0-3322-gf80b4d2
$ ./pre-inst-env guix import hackage -t darcs
Syntax error: unexpected token : (buildable (False)) (at line 494, column 4)
Syntax error: unexpected end of input
guix import: error: failed to download cabal file for package 'darcs'
--8<---------------cut here---------------end--------------->8---
The .cabal file is at
<https://hackage.haskell.org/package/darcs/darcs.cabal> and the faulty
line comes from:
--8<---------------cut here---------------start------------->8---
Executable darcs
if !flag(executable)
buildable: False
else
buildable: True
--8<---------------cut here---------------end--------------->8---
In addition, this .cabal file has “Build-Type: Custom”, which is
currently not supported as noted in <https://bugs.gnu.org/23961>.
Federico, WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-12-09 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 13:56 bug#25138: failing hackage import Dave Love
2016-12-09 20:57 ` Ludovic Courtès [this message]
2016-12-09 22:09 ` Federico Beffa
2016-12-12 13:40 ` Dave Love
2019-05-22 15:39 ` bug#25138: updated import error Robert Vollmert
2021-09-15 12:34 ` bug#25138: guix import hackage darcs: fails due to flag executable Lars-Dominik Braun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inqs7rci.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25138@debbugs.gnu.org \
--cc=beffa@ieee.org \
--cc=fx@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).