Closed santiweight closed 2 years ago
Please report this to Hackage maintainers, I have no idea how to debug their build failures
you can upload by hand with something like:
cabal new-haddock all --haddock-for-hackage --haddock-option=--hyperlinked-source
cabal upload -d --publish ./dist-newstyle/*-docs.tar.gz
Needs to be done by a maintainer though.
@jappeace I have heard about this workaround but I think the problem could be about https://hackage.haskell.org/package/bzlib-conduit not having pkgconfig-depends
specified but I'm not sure how to test this hypothesis.
That won't trigger haddocks rebuild though so probably I still need to use the workaround
perhaps a package candidate rebuilds the docs? (without doing a full release)
You could ask Michael to checkout PR in https://github.com/snoyberg/bzlib-conduit
But I could test out with xlsx
of course, I just don't think that it's where this should be fixed
I've a cunning plan, I'll rename packages in the cabal files so I can make my own candidates to debug
hi @jappeace did you have any success with your idea?
well, yes I got it building here: https://hackage.haskell.org/package/bzlib-conduit-jappie but I asked on discourse, and they told me to make an issue on hackage-server repository: https://github.com/haskell/hackage-server/issues/1064
I've uploaded haddocks to Hackage and closing this one in favor of haskell/hackage-server#1064 Thanks @jappeace for your help
The docs worked for version 0.8.4:
https://hackage.haskell.org/package/xlsx-0.8.4
but do not work for version 1.0.0.x:
https://hackage.haskell.org/package/xlsx-1.0.0