I'm trying to build hpodder 1.1.2 with ghc 6.8.2. I successfully downloaded, built, and installed (the latest versions of) all its dependencies, but when building hpodder itself, I get FeedParser.hs:146:26: `Content' is not applied to enough type arguments Expected kind `??', but `Content' has kind `* -> *' In the type `Content -> Either String String' In the type `String -> Content -> Either String String' In the type signature for `strof_either': strof_either :: String -> Content -> Either String String I don't know enough Haskell to even determine what kind of problem this is -- wrong version of some dependency? Wrong version of ghc? Help appreciated. :-) ( FWIW, the hackage auto-builder thingie seems to have the exact same problem I have: http://hackage.haskell.org/packages/archive/hpodder/1.1.2/logs/failure/ghc-6... ) -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle
On 2008.04.07 00:24:10 +0200, Karl Hasselström
I'm trying to build hpodder 1.1.2 with ghc 6.8.2. I successfully downloaded, built, and installed (the latest versions of) all its dependencies, but when building hpodder itself, I get
FeedParser.hs:146:26: `Content' is not applied to enough type arguments Expected kind `??', but `Content' has kind `* -> *' In the type `Content -> Either String String' In the type `String -> Content -> Either String String' In the type signature for `strof_either': strof_either :: String -> Content -> Either String String
I don't know enough Haskell to even determine what kind of problem this is -- wrong version of some dependency? Wrong version of ghc? Help appreciated. :-)
( FWIW, the hackage auto-builder thingie seems to have the exact same problem I have: http://hackage.haskell.org/packages/archive/hpodder/1.1.2/logs/failure/ghc-6... )
-- Karl Hasselström, kha@treskal.com
The issue here isn't GHC, but I think it's the former. If we open up the FeedParser.hs file, we see that the problem is that the type being inferred from what the code does clashes with the type gotten from what the code says. The issue is this Content type. A quick search shows that Content isn't defined in FeedParser.hs, and so if we comment out imports, we find that Content is coming from Text.XML.HaXml, and is documented here: http://hackage.haskell.org/packages/archive/HaXml/1.19.2/doc/html/Text-XML-H.... So almost certainly the issue is that HaXml has updated and changed things around in a way that broke Hpodder; not surprising, since HaXml-1.19.2 is as recent as 14 January 2008, and Goerzen may simply not have updated and discovered the error before he released Hpodder in February. If the problem is too-recent HaXml, there's an obvious work around. You could install HaXml-1.13.3 http://hackage.haskell.org/cgi-bin/hackage-scripts/package/HaXml-1.13.3 and edit the hpodder.cabal file to replace the 'HaXml>=' bit with 'HaXml==1.13.3'. That works for me. -- gwern Etacs FOSS NTIS SUPIR mindwar NATOA SARA niche DNR 3B2
On Monday 07 April 2008 5:57:39 pm gwern0@gmail.com wrote:
So almost certainly the issue is that HaXml has updated and changed things around in a way that broke Hpodder; not surprising, since HaXml-1.19.2 is as recent as 14 January 2008, and Goerzen may simply not have updated and discovered the error before he released Hpodder in February.
I won't be updating it anytime soon, in fact. 1.19.2 is a development version, according to the author, so I will stick with 1.13.3 -- the stable, released version. Unfortunately, Hackage has no way to indicate stable vs. alpha, I guess. (That would make life easier here.) I suppose I ought to also post something on the hpodder wiki and update the Cabal build-deps so it gets the right HaXml version.
If the problem is too-recent HaXml, there's an obvious work around. You could install HaXml-1.13.3 http://hackage.haskell.org/cgi-bin/hackage-scripts/package/HaXml-1.13.3 and edit the hpodder.cabal file to replace the 'HaXml>=' bit with 'HaXml==1.13.3'. That works for me.
-- gwern Etacs FOSS NTIS SUPIR mindwar NATOA SARA niche DNR 3B2
On 2008-04-07 20:20:24 -0500, John Goerzen wrote:
On Monday 07 April 2008 5:57:39 pm gwern0@gmail.com wrote:
So almost certainly the issue is that HaXml has updated and changed things around in a way that broke Hpodder; not surprising, since HaXml-1.19.2 is as recent as 14 January 2008, and Goerzen may simply not have updated and discovered the error before he released Hpodder in February.
I won't be updating it anytime soon, in fact. 1.19.2 is a development version, according to the author, so I will stick with 1.13.3 -- the stable, released version. Unfortunately, Hackage has no way to indicate stable vs. alpha, I guess. (That would make life easier here.) I suppose I ought to also post something on the hpodder wiki and update the Cabal build-deps so it gets the right HaXml version.
http://www.haskell.org/haskellwiki/Package_versioning_policy seems to have something relevant to say. build-depends: HaXml >= 1.13.3 && < 1.14 ought to do the trick, since any changes in the published interface are supposed to be accompanied by a version bump in one of the first two numbers. -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle
On Tue April 8 2008 3:21:34 pm Karl Hasselström wrote:
http://www.haskell.org/haskellwiki/Package_versioning_policy seems to have something relevant to say. build-depends: HaXml >= 1.13.3 && < 1.14 ought to do the trick, since any changes in the published interface are supposed to be accompanied by a version bump in one of the first two numbers.
That syntax didn't work under testing, but HaXml >= 1.13.2, HaXml < 1.19 did the trick. -- John
On Tue, 2008-04-08 at 15:43 -0500, John Goerzen wrote:
On Tue April 8 2008 3:21:34 pm Karl Hasselström wrote:
http://www.haskell.org/haskellwiki/Package_versioning_policy seems to have something relevant to say. build-depends: HaXml >= 1.13.3 && < 1.14 ought to do the trick, since any changes in the published interface are supposed to be accompanied by a version bump in one of the first two numbers.
That syntax didn't work under testing, but HaXml >= 1.13.2, HaXml < 1.19 did the trick.
Really? That's certainly supposed to work. Can you give more details we can use to reproduce the problem. Duncan
On 2008-04-07 18:57:39 -0400, gwern0@gmail.com wrote:
So almost certainly the issue is that HaXml has updated and changed things around in a way that broke Hpodder; not surprising, since HaXml-1.19.2 is as recent as 14 January 2008, and Goerzen may simply not have updated and discovered the error before he released Hpodder in February.
Yes, with an older HaXml it worked beautifully. Thanks! -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle
participants (4)
-
Duncan Coutts -
gwern0＠gmail.com -
John Goerzen -
Karl Hasselström