cabal import parser doesn't support common stanzas

  • Done
  • quality assurance status badge
Details
3 participants
  • Bone Baboon
  • Tobias Geerinckx-Rice
  • Philip Munksgaard
Owner
unassigned
Submitted by
Philip Munksgaard
Severity
normal
Merged with
P
P
Philip Munksgaard wrote on 27 May 2021 15:21
(address . bug-guix@gnu.org)
6f94e4a1-fc27-479e-8c9f-f1cd7542d6f5@www.fastmail.com
As far as I can tell, the cabal parser for the `guix import` command (https://git.savannah.gnu.org/cgit/guix.git/tree/guix/import/cabal.scm)does not support common stanzas, as specified in the cabal specification (https://cabal.readthedocs.io/en/3.4/cabal-package.html#common-stanzas).

This means that some packages, like "versions" (https://hackage.haskell.org/package/versions-5.0.0/src/versions.cabal)and all depending packages cannot be imported using `guix import hackage versions`:

```
$ guix import hackage versions
Syntax error: unexpected token : common (at line 36, column 0)
Syntax error: unexpected end of input
guix import: error: failed to download cabal file for package 'versions'
```
T
T
Tobias Geerinckx-Rice wrote on 30 May 2021 18:46
(no subject)
(address . control@debbugs.gnu.org)
874kek41be.fsf@nckx
merge 48700 48701
P
P
Philip Munksgaard wrote on 1 Jul 2021 17:10
Closed by 48943
(address . 48701-done@debbugs.gnu.org)
179f24db-0e33-4144-9b86-f0b6fdf8bd27@www.fastmail.com
This issue has been fixed by #48943 and should be closed.
Closed
B
B
Bone Baboon wrote on 13 Jul 2021 02:17
(name . Philip Munksgaard)(address . philip@munksgaard.me)
87o8b7hxsy.fsf@disroot.org
Philip Munksgaard writes:

Toggle quote (2 lines)
> This issue has been fixed by #48943 and should be closed.

You can close a bug report by emailing NNN-done@debbugs.gnu.org where
NNN is the bug number.

For the body of the email you can say something like "Closing because
<reason>".
?
Your comment

This issue is archived.

To comment on this conversation send an email to 48701@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 48701
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch