Hello all, alas, I couldn’t found any information about who is responsible for the build system on Hackage. So I address this issue to all of you. type-level built fine with GHC 6.8 but failed to build with GHC 6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
The complete log is at http://tinyurl.com/as67x5. This problem has the unfortunate consequence that type-equality-check cannot be built since it depends on type-level and nowadays only GHC 6.10 seems to be used for building packages on Hackage. This, in turn, will make almost all Grapefruit packages unbuildable when they are released (which is expected to happen soon). This, in turn, means almost no Grapefruit documentation on Hackage which, I think, would be very bad. So could someone please take the time and fix this problem soon? Thank you in advance. Best wishes, Wolfgang
On Thu, Feb 05, 2009 at 10:41:20AM +0100, Wolfgang Jeltsch wrote:
type-level built fine with GHC 6.8 but failed to build with GHC 6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
Yes, haddock 2.4.1 (the most recent release) bombs on Data.TypeLevel.Num.Aliases.
Am Donnerstag, 5. Februar 2009 13:16 schrieb Ross Paterson:
On Thu, Feb 05, 2009 at 10:41:20AM +0100, Wolfgang Jeltsch wrote:
type-level built fine with GHC 6.8 but failed to build with GHC
6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
Yes, haddock 2.4.1 (the most recent release) bombs on Data.TypeLevel.Num.Aliases.
Hackage uses Haddock 2.3.0, doesn’t it? Anyway, can something be done so that not all packages depending (directly or indirectly) on type-level are without documentation? For example, type-level could be installed on the Hackage server without documentation instead of not being installed at all. Best wishes, Wolfgang
On Thu, Feb 05, 2009 at 03:03:35PM +0100, Wolfgang Jeltsch wrote:
Am Donnerstag, 5. Februar 2009 13:16 schrieb Ross Paterson:
On Thu, Feb 05, 2009 at 10:41:20AM +0100, Wolfgang Jeltsch wrote:
type-level built fine with GHC 6.8 but failed to build with GHC
6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
Yes, haddock 2.4.1 (the most recent release) bombs on Data.TypeLevel.Num.Aliases.
Hackage uses Haddock 2.3.0, doesn't it?
The build client uses 2.4.1. I just tried with 2.3.0, and saw the same problem.
Anyway, can something be done so that not all packages depending (directly or indirectly) on type-level are without documentation? For example, type-level could be installed on the Hackage server without documentation instead of not being installed at all.
OK, I've done that. parameterized-data-0.1.3 now fails for other reasons, but the earlier ones are OK.
2009/2/5 Ross Paterson
On Thu, Feb 05, 2009 at 03:03:35PM +0100, Wolfgang Jeltsch wrote:
Am Donnerstag, 5. Februar 2009 13:16 schrieb Ross Paterson:
On Thu, Feb 05, 2009 at 10:41:20AM +0100, Wolfgang Jeltsch wrote:
type-level built fine with GHC 6.8 but failed to build with GHC
6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
Yes, haddock 2.4.1 (the most recent release) bombs on Data.TypeLevel.Num.Aliases.
Hackage uses Haddock 2.3.0, doesn't it?
The build client uses 2.4.1. I just tried with 2.3.0, and saw the same problem.
Oh, I'm sorry, seem like the problem was introduced in 2.3.0 (I should have checked the Trac ticket which clearly states that). I think 2.2.2 is fine, if that's of any help. David
Am Donnerstag, 5. Februar 2009 16:16 schrieb Ross Paterson:
On Thu, Feb 05, 2009 at 03:03:35PM +0100, Wolfgang Jeltsch wrote:
Anyway, can something be done so that not all packages depending (directly or indirectly) on type-level are without documentation? For example, type-level could be installed on the Hackage server without documentation instead of not being installed at all.
OK, I've done that. parameterized-data-0.1.3 now fails for other reasons, but the earlier ones are OK.
Thank you very much. Best wishes, Wolfgang
2009/2/5 Ross Paterson
On Thu, Feb 05, 2009 at 10:41:20AM +0100, Wolfgang Jeltsch wrote:
type-level built fine with GHC 6.8 but failed to build with GHC 6.10. The last line of the build log is this:
haddock: internal Haddock or GHC error: Maybe.fromJust: Nothing
Yes, haddock 2.4.1 (the most recent release) bombs on Data.TypeLevel.Num.Aliases.
In Haddock 2.4.0 we switched from using the compilation mode of the GHC API to a mode which does only typchecking. This broke Template Haskell support: http://trac.haskell.org/haddock/ticket/68 The problem is fixed in Haddock 2.4.2 which will be released with GHC 6.10.2. David
On Thu, Feb 05, 2009 at 03:05:44PM +0100, David Waern wrote:
In Haddock 2.4.0 we switched from using the compilation mode of the GHC API to a mode which does only typchecking. This broke Template Haskell support:
http://trac.haskell.org/haddock/ticket/68
The problem is fixed in Haddock 2.4.2 which will be released with GHC 6.10.2.
Haddock 2.4.2 uses a different interface file format, right? (Not an insuperable problem -- just asking.)
2009/2/5 Ross Paterson
On Thu, Feb 05, 2009 at 03:05:44PM +0100, David Waern wrote:
In Haddock 2.4.0 we switched from using the compilation mode of the GHC API to a mode which does only typchecking. This broke Template Haskell support:
http://trac.haskell.org/haddock/ticket/68
The problem is fixed in Haddock 2.4.2 which will be released with GHC 6.10.2.
Haddock 2.4.2 uses a different interface file format, right? (Not an insuperable problem -- just asking.)
Yep, that's right. David
participants (3)
-
David Waern -
Ross Paterson -
Wolfgang Jeltsch