stack hackage index out of date?

[Sönke Hahn]

Hi all,

I've just created a stack files that contains the following:

extra-deps:
- http-client-0.5.1

That version of that package is on hackage. It's also in my local hackage index that's used by cabal, as the output of `cabal info http-client` indicates. Yet stack can't find it, output inserted below.

It seems that stack is using its own hackage index separate from the one that cabal is using. It also seems to fetch that index not from hackage but from somewhere else. Is that understanding correct? If so, is it normal that the stack hackage indices online are out of date for some time?

Cheers,

Sönke


Here's stack's output:

Didn't see http-client-0.5.1 in your package indices.
Updating and trying again.
Fetching package index ...remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (1/1), done.
Fetched package index.
The following package identifiers were not found in your indices: http-client-0.5.1
Possible candidates: http-client-0.5.0, http-client-0.5.0.1.

[Michael Snoyman]

There's some bug with the Travis CLI tool, which is causing the previous every-30-minute refresh from Hackage to be delayed to around every 24 hours. I'm working on a fix for this, but in the meanwhile I've manually run the relevant jobs. Hopefully this will be back to normal in the next day or two.

Relevant Github issue: https://github.com/commercialhaskell/all-cabal-files/issues/10

--
You received this message because you are subscribed to the Google Groups "haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stac...@googlegroups.com.
To post to this group, send email to haskel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/0b6014dd-82a9-4be0-8e1e-398944239b68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sönke Hahn]

Yes, works now. Thanks for fixing and for explaining.

And this might also be a good moment to thank you and everyone else working on stack / stackage. So here goes:

Thanks a lot! :)

Cheers,

Sönke