GNU bug report logs -
#25138
guix import hackage darcs: fails due to flag executable
Previous Next
Reported by: Dave Love <fx <at> gnu.org>
Date: Thu, 8 Dec 2016 13:57:02 UTC
Severity: normal
Done: Lars-Dominik Braun <lars <at> 6xq.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25138 in the body.
You can then email your comments to 25138 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#25138
; Package
guix
.
(Thu, 08 Dec 2016 13:57:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Dave Love <fx <at> gnu.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 08 Dec 2016 13:57:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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)>
Information forwarded
to
bug-guix <at> gnu.org
:
bug#25138
; Package
guix
.
(Fri, 09 Dec 2016 23:26:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 25138 <at> debbugs.gnu.org (full text, mbox):
Hi,
Dave Love <fx <at> 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’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#25138
; Package
guix
.
(Sat, 10 Dec 2016 00:38:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 25138 <at> debbugs.gnu.org (full text, mbox):
On Fri, Dec 9, 2016 at 9:57 PM, Ludovic Courtès <ludo <at> gnu.org> wrote:
> 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?
The problem is that the name of the flag is 'executable' and the
string 'executable' is also a reserved keyword to define the start of
a cabal file section. The cabal parser incorrectly dismissed this
keyword as a possible flag name (in the code it is referred to as a
test identifier). See line 369 of the file 'guix/import/cabal.scm'.
The predicate 'is-id' should be smarter and recognize if the string
'executable' refers to the start of an 'executable section' or not
(and similarly for some other reserved keywords dismissed by the same
procedure).
The predicate 'is-id' dismisses some specific reserved keywords such
as 'executable' because this check is performed before the ones (based
on full lines) such as 'is-exec' which checks for the start of an
executable section.
HTH,
Fede
Information forwarded
to
bug-guix <at> gnu.org
:
bug#25138
; Package
guix
.
(Mon, 12 Dec 2016 13:42:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 25138 <at> debbugs.gnu.org (full text, mbox):
Ludovic Courtès <ludo <at> gnu.org> writes:
> 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---
That's what I saw with 0.11, but the new version with the backtrace
seemed a worthwhile improvement! (I tried an update after looking for a
way to configure generating backtraces and not finding one for guix or
an environment variable for guile that might have done it.)
Information forwarded
to
bug-guix <at> gnu.org
:
bug#25138
; Package
guix
.
(Wed, 22 May 2019 15:41:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 25138 <at> debbugs.gnu.org (full text, mbox):
These days it’s:
Syntax error: unexpected token : (buildable (False)) (at line 471, column 4)
Syntax error: unexpected end of input
Relevant cabal extract:
469 Executable darcs
470 if !flag(executable)
471 buildable: False
472 else
473 buildable: True
474
Changed bug title to 'guix import hackage darcs: fails due to flag executable' from 'failing hackage import'
Request was from
Robert Vollmert <rob <at> vllmrt.net>
to
control <at> debbugs.gnu.org
.
(Sun, 16 Jun 2019 12:37:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Lars-Dominik Braun <lars <at> 6xq.net>
:
You have taken responsibility.
(Wed, 15 Sep 2021 12:35:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Dave Love <fx <at> gnu.org>
:
bug acknowledged by developer.
(Wed, 15 Sep 2021 12:35:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 25138-done <at> debbugs.gnu.org (full text, mbox):
Hi,
this was fixed by the patch from #50588.
Cheers,
Lars
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 14 Oct 2021 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 194 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.