From: c4t0 <c4t0@riseup.net>
To: guix-devel@gnu.org
Subject: Re: guix import hackage fails with errors, and failed tests
Date: Wed, 24 Mar 2021 12:13:18 -0300 [thread overview]
Message-ID: <878s6c7fg1.fsf@riseup.net> (raw)
In-Reply-To: <87mtut7a6a.fsf@riseup.net> (c4t0@riseup.net's message of "Tue, 23 Mar 2021 19:54:53 -0300")
c4t0 <c4t0@riseup.net> writes:
it appears to be this bug:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35743
It's marked in the hackage.scm to expected fail, but the layout problem
with cabal files seems pretty ubiquos. I'll try to look at it, and move
the discussion there.
If anyone can give me some tip to how start debugging the test, I'll
appreciate it, since I'm pretty new in scheme hacking with guile in
guix. I must be overlooking something very obvious.
Thanks.
> Hi!
>
> I'm having problems with 'guix import' in my environment:
> $guix import hackage -t ghc-events
> Syntax error: unexpected token : common (at line 44, column 0)
> Syntax error: unexpected end of input
> guix import: error: failed to download cabal file for package 'ghc-events'
>
> so I cloned guix, and:
>
> guix environment guix --pure --ad-hoc help2man git strace --container
> make check TESTS=tests/hackage.scm
>
> (I need to add --container for a problem that I address in another
> email, can be ignored)
>
> I found that two tests are failing with similar error:
>
> Syntax error: unexpected token : (ghc-options (-Wall)) (at line 11, column 2)
> Syntax error: unexpected end of input
>
> ;;; (fail #f #f)
> test-name: hackage->guix-package test mixed layout
> location: ./tests/hackage.scm:295
> source:
> + (test-assert
> + "hackage->guix-package test mixed layout"
> + (eval-test-with-cabal
> + test-cabal-mixed-layout
> + match-ghc-foo))
> actual-value: #f
> result: XFAIL
>
> Syntax error: unexpected token : (buildable (False)) (at line 12, column 4)
> Syntax error: unexpected end of input
>
> ;;; (fail #f #f)
> test-name: hackage->guix-package test flag executable
> location: ./tests/hackage.scm:322
> source:
> + (test-assert
> + "hackage->guix-package test flag executable"
> + (eval-test-with-cabal
> + test-cabal-flag-executable
> + match-ghc-foo))
> actual-value: #f
> result: XFAIL
>
> I'm using guix 5f9b28b231e17749d14a1b95ae9cad68d7315a1e on top of and
> old ubuntu, with all packages upgraded.
>
> How can I start a debugger?
>
> I tried several variations of:
>
> guile -l scripts/guix
> and then
> (main '("import" "hackage" "ghc-events"))
>
> with out success.
>
> I'm interested in checking the tests and the package that fails.
>
> COD.
next prev parent reply other threads:[~2021-03-24 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 22:54 guix import hackage fails with errors, and failed tests c4t0
2021-03-24 15:13 ` c4t0 [this message]
2021-03-24 16:58 ` zimoun
2021-03-24 19:41 ` c4t0
2021-03-24 21:12 ` zimoun
2021-03-25 19:23 ` c4t0
2021-03-26 4:37 ` zimoun
2021-03-26 20:21 ` c4t0
2021-03-26 22:37 ` zimoun
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=878s6c7fg1.fsf@riseup.net \
--to=c4t0@riseup.net \
--cc=guix-devel@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 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.