Hi all,
It seems that we are having a rather big issue with Hackage in recent
months and I'm sure many of you have noticed: a lot of packages aren't
getting their docs built. As far as I can tell, there can be multiple
reasonable causes:
* Dependencies fail to build so your package does
* Your
Hi,
I now at least twice ran into the issue, that I forgot to add a module
to the 'other-modules' section of the cabal file and uploaded a non
buildable package to hackage.
It would be nice if 'cabal sdist' or 'cabal upload' would warn the user
about missing modules.
I just tried 'cabal upload
On Sun, Jan 5, 2014 at 11:37 AM, Daniel Trstenjak
daniel.trsten...@gmail.com wrote:
It would be nice if 'cabal sdist' or 'cabal upload' would warn the user
about missing modules.
This was built to run during 'cabal build' [0] but deemed too slow.
See the issue for a possible future direction.
I agree. Two of my packages are in your list: easyrender and newsynth
(both have Nothing for a reason in your list).
The problem for me is that, although you seem to have access to build
logs, I don't. I have not found the way to access the hackage build
logs for my packages or their
On 05/01/14 14:14, Sven Panne wrote:
My ALUT package is among the ones without documentation, and I have a
theory what's wrong (probably a missing installed C library/package
libalut-dev, see
https://github.com/haskell-openal/ALUT/blob/master/.travis.yml). Two
questions:
* As a package
On 05/01/14 18:15, Peter Selinger wrote:
I agree. Two of my packages are in your list: easyrender and newsynth
(both have Nothing for a reason in your list).
If a package has Nothing for a reason, that means that no build log is
available. From what I've read yesterday, it's a problem with
