Bump cabal-version allowed in .cabal files

[vmchale]

This is related to #6233. When c2hs handling is fixed, some packages will only build with a recent Cabal.

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.
• If the change is docs-only, [ci skip] is used to avoid triggering the build bots.

Tested it by running on libarchive.

[phadej]

Next `cabal-version: ` will be 3.2 not 3.1. It’s easy to confuse Cabal library version with cabal-version version of the spec, as they are the same for released versions. Do we have anything casing on CabalSpecVersion3_2 yet?

…

On 26 Sep 2019, at 20.54, Vanessa McHale ***@***.***> wrote: This is related to #6233. When c2hs handling is fixed, some packages will only build with a recent Cabal. Patches conform to the coding conventions. Any changes that could be relevant to users have been recorded in the changelog. The documentation has been updated, if necessary. If the change is docs-only, [ci skip] is used to avoid triggering the build bots. Tested it by running on libarchive. You can view, comment on, or merge this pull request online at: #6261 Commit Summary Bump allowed cabal-version File Changes M Cabal/Distribution/PackageDescription/Parsec.hs (2) Patch Links: https://github.com/haskell/cabal/pull/6261.patch https://github.com/haskell/cabal/pull/6261.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[phadej]

I checked, neither #6233 nor nothing already existing cases on CabalSpecV3_2 yet.

[vmchale]

I suppose that depends on whether #6233 is merged, then.

(I have updated the file to use 3.2 instead of 3.1)