search

UnkindPartition / tasty

Modern and extensible testing framework for Haskell
640 stars 110 forks source link

Please mark tasty-1.5.1 as "deprecated" on Hackage #426

Closed peti closed 3 months ago

peti commented 4 months ago

The page https://hackage.haskell.org/package/tasty-1.5.1 gives no indication that this release has been deprecated. Could you please mark it appropriately so that Hackage knows this release is not supposed to be used?

phadej commented 4 months ago

I'd rather make hackage-server smarter: https://github.com/haskell/hackage-server/issues/1324

(and FWIW, also stackage curator tools similarly)

peti commented 4 months ago

I'd rather make hackage-server smarter: haskell/hackage-server#1324

(and FWIW, also stackage curator tools similarly)

I'm totally in favor of improving Hackage to recognize such a case automatically. This would greatly benefit users in, like, 6 months from now or so. Marking the deprecated tasty release as such today would greatly benefit users today. And both things aren't even mutually exclusive.

Bodigrim commented 4 months ago

Marking the deprecated tasty release as such today would greatly benefit users today.

What exactly makes status quo unsatisfactory? Version bounds for tasty-1.5.1 are impossible, so Cabal / Stack / Stackage would not pick it up. If someone chooses to ignore version bounds, I would not generally expect them to honor deprecation status.

peti commented 3 months ago

What exactly makes status quo unsatisfactory?

The problem is that there are several semi-automatic tools that generate Haskell package set updates for openSUSE, NixOS, Fedora and probably others and these tools look at that the ~/.cabal/packages/hackage.haskell.org/01-index.tar tarball published by Hackage to determine which versions of which package exist. Since Hackage doesn't know that tasty-1.5.1 is deprecated, it advertises the new version in its database. Which means that probably all of those tools have updated tasty in their respective distributions, which then results in a build error that cannot be fixed. If the deprecated version were marked so on Hackage, the update would have never been attempted and the time and effort of several overloaded volunteers managing those distributions could have been saved.

andreasabel commented 3 months ago

I deprecated tasty-1.5.1 on hackage.

cabal get tasty will download tasty-1.5 now.
(I doubt that cabal get looks at the dependency constraints to figure out which version to download.)