Cabal 3.14.2 depends on Cabal-syntax at least 3.14.2

[ulysses4ever]

fix #10916

---

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[Mikolaj]

Thank you.

[ulysses4ever]

Would be great to discuss at one point how to avoid such slips in the future...

[geekosaur]

check-sdist is supposed to catch these, but currently (a) only considers Cabal, not Cabal-syntax (b) got broken by a PVP-acceptable API change it doesn't currently support. Rewriting it is on the menu.

[ulysses4ever]

Looks like we have a plan -- good! I'm thinking about adding something to the Wiki page anyway. The best place I see is:

C.3.2 Change the dependency constraints on Cabal-syntax and Cabal to the new version where they are needed in the repo (like cabal-testsuite/cabal-testsuite.cabal and bootstrap/cabal-bootstrap-gen.cabal).

I'm not sure why it lists "secondary" packages, which we don't publish, like cabal-testsuite and doesn't mention the main packages that we do publish. In any case, this item already has a sublist with one item, and I want to add another one:

Sometimes this means updating the lower bounds too, even for minor releases (to avoid issues like #10916 and #9833).

Thouths?

[geekosaur]

I think the ones it lists are the ones that are usually forgotten even in major versions, whereas this case only happens when we have unexpected API changes in minor versions.

[ulysses4ever]

@geekosaur, thanks for clarifying! I added a little phrase there so that it doesn't sound like it's only about aux packages (which it sounded to me like that before).

[ffaf1]

Should this be forward ported to master?

[ulysses4ever]

@ffaf1 I was thinking about it. It's not clear to me that it should. Master has 3.15 everywhere, I think. When 3.16 will be cut, we must make sure that dependencies are handled accordingly. But I'm not sure we want 3.14.2 for version bound on master.

[geekosaur]

Ah, right, you've just reminded me why it wasn't forward-ported in the first place.