Skip to content

Support cabal syntax 3.12 #7933

@alaendle

Description

@alaendle

Since I've seen this during nightly builds:

Unable to parse cabal file from package webdriver-precore-0.2.0.1@sha256:2c644f12cb915bd6491da97af448bb74270cdcee8260f4a39f11c7594b6153c4,7407 (from Hackage)- 0:0: Unsupported cabal-version 3.12. See haskell/cabal#4899.

I tried to support the newer cabal syntax, by updating curator to lts 24-11 and moving to stack 3.9.1 - however the package & haddock representation on the stackage-server got corrupted by this change.

Problem 1:
https://www.stackage.org/diff/nightly-2026-01-17/nightly-2026-01-18 - after the change the core libs are missing, but also webdriver-precore which depended on cabal 3.12 syntax disappeared. Everything looks okay if you diff the corresponding YAML's in the snapshot repository.

Problem 2:
The documentation is missing - e.g. https://www.stackage.org/nightly-2026-01-19/package/evm-opcodes-0.3.0, but you could look at any package for this nightly build.

So my guess is this change needs to implement in sync with stackage-server (and maybe other infrastructure). I also tried to build the server against lts-24.11, but I'm really unsure how to validate my changes. I also tend to believe this might be too big for volunteer contribution since it needs a deep understanding of the infrastructure. At least I had no quick win trying to even succesfully run my local stackage-server - so at least some guidance, what changes are needed and how these could be validated would be needed. At least I don't want to struggle with reverse engineering all the code.

Long story short - for now I switch back to stack 3.7.1 and the curator build against lts-22.43 (see commit below) and hope that the mentioned problems disappear on the next nightly build.

Please also note: I haven't reverted the update on curator side - commercialhaskell/curator@28f0bf6 - since I believe we need to support the newer cabal syntax anyway in a not too distant future (cabal 3.12 with the new syntax was released May 2024).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions