It would be nice if there is a way to re-trigger the haddock generation without uploading a new version. I will file an issue requesting for this feature.

BTW, I still wonder how I can specify the build requirements for the Hackage server. For example, I specify c2hs and libenchant-dev as dependencies in .travis.yml for the Travis build:

```

before_install:

- sudo apt-get install -y libenchant-dev c2hs

```

Regards,

Kwang Yul Seo

On Mon, Jun 27, 2016 at 2:53 PM, Harendra Kumar <harendra.kumar@gmail.com> wrote:

I had a similar problem recently. If a candidate package is re-uploaded with the same version again, doc was not being re-generated. I too changed the version to 0.1.0.1 to trigger the doc update. I raised an issue for that (https://github.com/haskell/hackage-server/issues/512).

-harendra

On 27 June 2016 at 09:58, Francesco Ariis <fa-ml@ariis.it> wrote:
On Mon, Jun 27, 2016 at 01:28:57PM +0900, KwangYul Seo wrote:
> Hi,
>
> I uploaded a package named enchant on the Hackage last week, but the
> Haddock documentation is not showing up yet. The Status field says "Docs
> pending" and "Build status unknown".
>
> https://hackage.haskell.org/package/enchant-0.1.0.0
>
> enchant uses c2hs as a build tool to generate the FFI binding and requires
> libenchant-dev to be installed on the machine. I wonder how I can tell
> these build requirements to the Hackage server.

I had a similar problem a few months ago, resolved to upload a 0.1.0.1
version, that triggered the build.

p.s.: I am replying in haskell-cafe@haskell.org , which is probably more
suited (haskell@ is for announcements, etc.)
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.