Can cabal-install 3.12.1 build with hashable-1.5?

[juhp]

It would be nice to have cabal-install back in Stackage Nightly.

Unfortunately due to hashable-1.5, cabal-install-3.12.1 does not build there.

Is it possible to relax the upper bound?

Otherwise hopefully 3.14+ may improve the situation...

[geekosaur]

We ran into a road bump with updating the dependency, IIRC (and checking PRs agrees). I think hashable-1.5 is okay with cabal-install 3.12.

[geekosaur]

Also 3.14 should have the updated dependency bound already, and I think 3.16-to-come got rid of it entirely. (Correction: the removal got backported, so if Stackage can be updated to a 3.14 release then there should be no problem.)

[juhp]

Stackage can't update (until ghc-9.12) that is the point :-) We always need the cabal-install for the version of ghc Cabal.

Like any good distro :-)

[juhp]

I can try a PR for the 3.12 branch I guess - though really we need a revision.

[geekosaur]

I think PRs for 3.12 are closed since we ditched the LTS thing until we can get GHC to play along with it (little point in an LTS if we have to rev every ghc major version, which are happening rather quickly these days). I would suggest a local validate with --constraint=hashable==1.5 --disable-documentation (the latter due to a bug in validate that was fixed for 3.14) to test, then we can proceed with the revbump.

[juhp]

Hmm okay... couldn't we validate on the branch - anyway sure then I will try to test it locally.

I guess the 3.12 branch could in principle have diverged from the release...

[juhp]

I would argue though that this project really should validate cabal-install releases can build against the corresponding latest ghc minor release - that would be a useful service to distros and the ecosystem.

To put it differently: we should aim to always have cabal-install available in Stackage LTS and Nightly.

[geekosaur]

It's not supposed to have diverged, and in fact I was checking it regularly while we were hoping to use it as an LTS branch.

[geekosaur]

I would argue though that this project really should validate cabal-install releases can build against the corresponding latest ghc minor release - that would be a useful service to distros and the ecosystem.

https://github.com/haskell/cabal/blob/master/.github/workflows/check-sdist.yml

[geekosaur]

hm, actually I think that's the reverse. (We need to ensure it works with the Cabal in the ghc release.) We do validate against latest minor release normally, but someone needs to update that periodically and we've forgotten a few times.

[geekosaur]

I should also note that we don't (and in general can't, without a reorganization of our CI) validate older versions of cabal-install. In particular, validate is pretty brittle. IIRC 3.10.x validate broke some time back, not helped by several breaking changes in some minor releases (notably 3.10.3, which is what led to the check-sdist job).

[juhp]

As a first PoC, at least revising hashable and open-browser (even cabal-install-3.14 doesn't allow 0.4 yet...) builds fine in current Stackage Nightly.