Skip to content

Documentation not generated #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
crockeea opened this issue Jul 24, 2014 · 11 comments
Closed

Documentation not generated #244

crockeea opened this issue Jul 24, 2014 · 11 comments

Comments

@crockeea
Copy link

I noticed that (for example) repa-3.3.1.2 doesn't have any documentation on hackage. I posted this on a repa forum and the dev responded with

"Thanks, I've pushed a new version. We'll see if that triggers Hackage to rebuild the docs. The docs build locally, so if Hackage isn't building them I suppose it's a Hackage bug."

which I am now dutifully reporting. I've noticed this problem with other packages as well; I'll try to post those as I rediscover them.

Now that I've found three pacakges where this is an issue:

  1. What's causing it?
  2. Is there a way to go back and generate docs for missing versions?
@crockeea
Copy link
Author

For your reference, here's another package for which documentation was not generated: http://hackage.haskell.org/package/open-typerep

@crockeea
Copy link
Author

It looks like repa-3.3.1.2 got documentation after a while, but repa-3.3.1.1 and repa-3.2.5.1 still do not have any documentation.

@crockeea
Copy link
Author

Another package: singletons, before version 0.9.3. I diff'd 0.9.2 (no documentation generated) and 0.9.3 (documentation generated), and the changes to the package are extremely minimal, certainly nothing that should affect doc generation.

@Daniel-Diaz
Copy link

Duplicated issue: #265

@crockeea
Copy link
Author

@Daniel-Diaz Except mine was first :-P

@Daniel-Diaz
Copy link

@crockeea You're right. I didn't see the date.

@svenpanne
Copy link

Duplicate of #265

@svenpanne
Copy link

Hmmm, shouldn't GitHub mark this issue as a duplicate was the syntax in the previous comment wrong?

@gbaz
Copy link
Contributor

gbaz commented Feb 3, 2016

closing this as its an old ticket and it doesn't serve to have lots of redundant ones floating around.

@gbaz gbaz closed this as completed Feb 3, 2016
@svenpanne
Copy link

So what's the "master" ticket for all the doc builder problems? Simply closing tickets doesn't make the problem go away... 😉

@gbaz
Copy link
Contributor

gbaz commented Jun 15, 2016

#478

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants