ghc-conduit-extra build fails

  • Done
  • quality assurance status badge
Details
One participant
  • Gabriel Hondet
Owner
unassigned
Submitted by
Gabriel Hondet
Severity
normal

Debbugs page

Gabriel Hondet wrote 6 years ago
(address . bug-guix@gnu.org)
8736qmyl6z.fsf@gmail.com
Hello,

I've been trying to compile ghc-conduit-extra since it is needed by
ghc-xmonad-extra and xmobar. The build fails the following way (sorry
for the poor layout):

Building library for conduit-extra-1.3.0.. [0/1051]
[ 1 of 13] Compiling Data.Conduit.Attoparsec ( Data/Conduit/Attoparsec.hs, dist/build/Data/Conduit/Attoparsec.o )
Data/Conduit/Attoparsec.hs:99:14: error:
• Couldn't match type ‘text-1.2.3.0:Data.Text.Internal.Text’
with ‘TI.Text’
NB: ‘TI.Text’
is defined in ‘Data.Text.Internal’ in package ‘text-1.2.3.0’
‘text-1.2.3.0:Data.Text.Internal.Text’
is defined in ‘Data.Text.Internal’ in package ‘text-1.2.3.0’
Expected type: A.Parser TI.Text b -> TI.Text -> A.IResult TI.Text b
Actual type: Data.Attoparsec.Text.Parser b
-> text-1.2.3.0:Data.Text.Internal.Text
-> Data.Attoparsec.Text.Result b
• In the expression: Data.Attoparsec.Text.parse
In an equation for ‘parseA’: parseA = Data.Attoparsec.Text.parse
In the instance declaration for ‘AttoparsecInput TI.Text’
|
99 | parseA = Data.Attoparsec.Text.parse
|

As far as I'm concerned, the error seems to be in the haskell package
more than in the guix build process, but downgrading to previous version
is not really feasible considering the number of dependencies.
Could someone confirm that the error comes indeed from the haskell
package, and thus motivate a bug report on hackage?

Thanks
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE5ercJXBcjd3P1FcAMbyBBfZZ1CUFAlwhATQACgkQMbyBBfZZ
1CUM2w/8CEIUxcpzL9FcjriBZeZ5hKJupEVUv5LhJXw8rqBj3D9GtP6ULdy8BUnR
YQFY7uwFDNK7pDspqavFlI3JTr8D4SPHThW0IscSMmLyi/iyhkJWK+yBYoozXzwn
lNbLIoVflu71Z+d07E6BU58pqXRp1LJpH/QY/siI5+KKUSy1bgs5e1gkeuqvt7a5
Bvb/S8jRJ5hw1cM2eWWzHdgLcRjZFVZ062Kvg2YCDD6dWXLZjkJg0rW+61TYH74f
rce0oO14gwzDxTwbM745b9PWXU+V8bxlYt4BGhPBOp+EE0G0AetnbqsGN7g+eA+k
DaZs5WiAECbw2HV+IbwsDXI6dz47kW9GB5iUiusByl/FuMQXkk7gmxi6tEO6X3HL
X2NHIu4BgNKHf2S8NriH7/zk2F9GPJT5YibMrgPrwSL8lfdAmYDWrTxHmpXWqoct
tQjnLHAlqLtF/WsT3l5KWNg90i9r+PDjnUc6YgqCqQXSrkjc15bXtPorr+U2Fx7o
3YLCGLeYiO/tKsKHyRdwo1lRYeSP/qg+Ck9httZgyEUhlrJcvoySpwWOZuMu8ecI
mEBUTol180vExJxKfmB7fJHMZVTahVZ7uW0PQ8Y7PbIwT1EgLGCDHVpkGcAZfiRu
todJE3M4L88SJGqOuMSAMkczhY2uqm4pGlQVP7A8aj4UzFrBeJU=
=lAE4
-----END PGP SIGNATURE-----

Gabriel Hondet wrote 6 years ago
(address . 33859-done@debbugs.gnu.org)
8736pjznog.fsf@gmail.com
Builds without problem since 5de93cdba77db3777f8f026c029acadd7b8bdde3
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE5ercJXBcjd3P1FcAMbyBBfZZ1CUFAlxIPl8ACgkQMbyBBfZZ
1CX56hAAhWRZP1+VQYWsoSKCLXoRzwwtkkuy2B/V/BQLy3VuifW00IrW3zg/OBnF
/3hlRj01n/yAMeKo0GiWFQX6oLCeafAiJbMfm2dASFRRLOH5hBKyOH45cd0UIkYr
L3Atz1I6n9pcb3fGL3pUirXAEK1fI9mF2+vssxTVk4ewlP8VyLoiGYp8PrldKYFa
FuTmNPQ6I2rK72ibOHAVA916+Eb7Ty/N1QhDfKq+KQEVGo1vpjcdIAnZsapOX+oD
TX6BXpTR1MW2PW+jyVXKibAyNVyXYHrz2IYWkSu5QINYEpzoYuqxCaVn72DwF20G
4B9C+d6PKs+fDEckDaNJqZqXdQOj5yGDsMHnnNvYvPPDcuhsuwOvu+XgQg5Mr9Ut
jYLwGbBZVTmb33tqxT3YLNF/qOueHvJxSTsP37s7puWhQCUkT2BzaR2eRhcK4Stx
3IJ0PzKqXPdEOB3ymxlbNT01Zb5r2EIGqXoPnHcD9bHp8inleJE04ZAbNUY7AJVu
0rAnFnosfulzRVmhodc3y7iCywkIz7KuJKTjEnZiYWpCe6wTWdUkFrANLFciH+SR
5oO8eUpZ/EKvaUi/vBvznZEzV431YY5UCMgiwyc6lCxULXKeGkfY1IiCqNt9u9Hz
jQ1eyyzInvHs71nde9+zsDVBMtyZMNE6KQt/g473zQrOaftpgRw=
=vcu6
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 33859
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
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help