yesodweb / yesod

A RESTful Haskell web framework built on WAI.
http://www.yesodweb.com/
MIT License
2.63k stars 372 forks source link

yesod-core-1.2.17: Fix Haddock on Hackage #775

Closed spl closed 10 years ago

spl commented 10 years ago

No documentation on Hackage means that (at least):

Is it possible to upload a minor version fix to this?

spl commented 10 years ago

Also yesod-static 1.2.2.5, 1.2.3, and 1.2.4.

snoyberg commented 10 years ago

Following this comment, I just tried the following:

curl -X DELETE http://MichaelSnoyman:mypassword@hackage.haskell.org/package/yesod-static-1.2.4/docs

Hopefully that will resolve the issue.

spl commented 10 years ago

Do you think it's a problem with Hackage itself?

Also, there's this.

snoyberg commented 10 years ago

It's usually a safe assumption that it's a problem with Hackage.

Is that link for instructions on uploading my own copy of the docs? I'm not opposed to that.

spl commented 10 years ago

It's usually a safe assumption that it's a problem with Hackage.

Ah, didn't know Hackage was having so much trouble these days. It used to be a safe assumption that the package was doing something different, e.g. with TH or whatever.

Is that link for instructions on uploading my own copy of the docs?

Yes, it's from a thread with other people having trouble with Hackage building the docs. Earlier in the thread Erik Hesselink said the DELETE didn't do the job for him. I haven't tried any of these myself, so I don't know how successful each approach is.

snoyberg commented 10 years ago

I was just being facetious, Hackage isn't usually that bad. I'll give one of those approaches a shot now.

spl commented 10 years ago

Okay, missed that. :smile:

snoyberg commented 10 years ago

Turns out the problem was with building aeson:

http://hackage.haskell.org/package/yesod-core-1.2.17/reports/1/log

I used the script at https://gist.github.com/Fuuzetsu/8276421, which seems to be working pretty well. The docs should now all be working.

spl commented 10 years ago

Great! Thanks so much, @snoyberg.