[ghc-9.10] Cabal-3.12

[juhp]

Heads-up for ghc-9.10 (current nightly is still 9.8)

Cabal-3.12.0.0 (changelog) is out of bounds for:

• cabal-install-3.12.1.0 (^>=3.12.1.0). Mikolaj Konarski mikolaj.konarski@funktory.com @Mikolaj, Stackage upper bounds. Used by: library
• cabal-install-solver-3.12.1.0 (^>=3.12.1.0). Grandfathered dependencies, Stackage upper bounds. Used by: library
• cabal-rpm-2.2.1 (>1.10 && < 3.11). Jens Petersen juhpetersen@gmail.com @juhp. Used by: executable
• cabal2spec-2.7.1 (>=3.8 && < 3.11). Peter Simons simons@cryp.to @peti. Used by: library
• cuda-0.11.0.1 (>=1.24 && < 3.11). Trevor L. McDonell trevor.mcdonell@gmail.com @tmcdonell. Used by: library
• encoding-0.8.9 (>=2.0 && < 3.11). Grandfathered dependencies. Used by: library
• nvvm-0.10.0.1 (>=1.24 && < 3.11). Trevor L. McDonell trevor.mcdonell@gmail.com @tmcdonell. Used by: library
• polysemy-1.9.2.0 (< 3.11). Torsten Schmits stackage@schmits.me @tek. Used by: library
• polysemy-plugin-0.4.5.2 (< 3.11). Torsten Schmits stackage@schmits.me @tek. Used by: library
• proto-lens-protobuf-types-0.7.2.1 (>=3 && < 3.12). Judah Jacobson judah.jacobson@gmail.com @judah. Used by: library
• proto-lens-setup-0.4.0.8 (>=2.0 && < 3.12). Judah Jacobson judah.jacobson@gmail.com @judah. Used by: library

Cabal-syntax-3.12.0.0 (changelog) is out of bounds for:

• cabal-install-3.12.1.0 (^>=3.12.1.0). Mikolaj Konarski mikolaj.konarski@funktory.com @Mikolaj, Stackage upper bounds. Used by: library
• cabal-install-solver-3.12.1.0 (^>=3.12.1.0). Grandfathered dependencies, Stackage upper bounds. Used by: library
• fourmolu-0.15.0.0 (>=3.10 && < 3.11). Brandon Chinn brandonchinn178@gmail.com @brandonchinn178, Stackage upper bounds. Used by: library
• ormolu-0.7.4.0 (>=3.10 && < 3.11). Mark Karpov markkarpov92@gmail.com @mrkkrp, Stackage upper bounds. Used by: library

[Mikolaj]

Hi! I'm not sure how to interpret this ticket, but OOI, why does it mention Cabal-3.12.0.0 instead of Cabal-3.12.1.0 (or Cabal-3.14.0.0 for that matter)?

[andreasabel]

@Mikolaj The problem is that GHC 9.10.1 ships the 3.12.0.0 edition of Cabal:

$ ghc-pkg-9.10 list | grep Cabal
    Cabal-3.12.0.0
    Cabal-syntax-3.12.0.0

And there is no such edition for cabal-install.

Not sure how to proceed here.

One option would be to wait for GHC 9.10.2 which hopefully ships the 3.12.1.0 edition, but a release does not seem imminent judging from the milestone: https://gitlab.haskell.org/ghc/ghc/-/milestones/399#tab-issues
This would mean postponing the bump of the nightly snapshot to 9.10 for an unknown amount of time.

Can cabal-install-3.12.1.0 be built and work with Cabal-3.12.0.0?
(Seems unlikely, but does not hurt to ask.)

[peti]

cabal2spec-2.7.1 is fixed on Hackage in revision 1.

[juhp]

I don't think cabal-install is a real blocker for bumping Nightly - we didn't have it in nightly before 9.8.3 was released either. Though everything being equal I suppose I would prefer to start with 9.10.2, which might appear before long?
(edit: Okay I had only looked at the pending Backports, on the Milestone page there does seem to be a lot left)

Though I can lament the "instability" of cabal-install and stack in Stackage - it seems a never ending battle/dance to have them available: I wish upstreams were more aware of this, though it sounds like stack HEAD might be okay for 9.10 nightly (it dropped out with 9.8.3).

[Mikolaj]

Oh, I see.

Can cabal-install-3.12.1.0 be built and work with Cabal-3.12.0.0?

We'd need to double-check in cabal-install-3.12.1.0 and Cabal-3.12.1.0 changelogs, but I guess there should be no problem running cabal-install-3.12.1.0 with Cabal-3.12.0.0, once the deps are revised (on Hackage or locally). The changelog for cabal-install-3.12.1.0 even says "this is the first release of cabal-install that is fully compatible with Cabal 3.12.0.0 as released with GHC 9.10.1". @ulysses4ever, what do you think?

[tek]

revised polysemy and polysemy-plugin ✅

[ulysses4ever]

@Mikolaj

there should be no problem running cabal-install-3.12.1.0 with Cabal-3.12.0.0,

Indeed, I just tried it, and, at least, it builds.

Normally the tool is tightly coupled with the library and doesn't guarantee to build with a mismatched version, that's why we bump the lower bounds almost unconsciously. But that does feel a little restrictive, perhaps. I complained about that myself recently to @Kleidukos (I can't remember where and find a link), and he said that's how it's supposed to be. So, I'd be interested to hear what he says about the problem Stackage runs into.

[mrkkrp]

Bumped the bounds via a revision for ormolu-0.7.4.0.

[ysangkok]

Fourmolu 0.16.2.0 supports Cabal 3.12, so it just needs to be bumped, see #7449