search

commercialhaskell / stackage

Stable Haskell package sets: vetted consistent packages from Hackage
https://www.stackage.org/
MIT License
526 stars 802 forks source link

https://www.stackage.org/lts/cabal.config refers to deprecated version of nationstates #819

Closed peti closed 8 years ago

peti commented 9 years ago

I hope this is the right place to report this issue. The file https://www.stackage.org/lts/cabal.config advertises nationstates ==0.2.0.2, but that version has been explicitly deprecated on Hackage: http://hackage.haskell.org/package/nationstates-0.2.0.2 by @lfairy. Is that intentional?

DanBurton commented 9 years ago

Yes, the new nationstates was a major version bump, so it won't be included in the LTS 3.* series. LTS minor version upgrades only include minor version upgrades for the included packages. This is the stability promise of LTS Haskell, which unfortunately means that packages will trail behind their newest versions in circumstances such as this.

nationstates-0.3.0.0 is included in the nightly builds ( https://stackage.org/nightly ) which means it is on track for inclusion in LTS 4.0. No date is set for when that will come out, but I expect it to be November or December of this year.

On Wednesday, September 9, 2015, Peter Simons notifications@github.com wrote:

I hope this is the right place to report this issue. The file https://www.stackage.org/lts/cabal.config advertises nationstates ==0.2.0.2, but that version has been explicitly deprecated on Hackage: http://hackage.haskell.org/package/nationstates-0.2.0.2 by @lfairy https://github.com/lfairy. Is that intentional?

— Reply to this email directly or view it on GitHub https://github.com/fpco/stackage/issues/819.

-- Dan Burton

bergmark commented 9 years ago

I don't think stackage does any deprecation tracking, perhaps it should.

Deprecation doesn't mean a version won't be used, afaik it has lower precedence in Cabal's solver than installed packages. The only safe solution to deprecation I know of is to publish a new undeprecated version with A.B.C.(D+1)

phadej commented 9 years ago

... or a revision with base (>1 && <1) dependency.

lambda-fairy commented 9 years ago

I deprecated 0.2.0.2 because the release accidentally included a breaking change. So I don't think it should have been included in the LTS update.

I've now uploaded 0.2.0.3 which has bug fixes only. That should turn up in the next LTS 3.* release, which will fix the immediate issue.

juhp commented 9 years ago

Thanks!

peti commented 8 years ago

0.2.0.3 landed in LTS 3.6.