Use a newer ci-images for centos7

[chreekat]

Fix for #10804 designed for backport.

For the next major version of Cabal, I suggest a larger update of supported platforms. But not in this PR. This one is just about maintaining support of platforms that were already supported.

[ulysses4ever]

I wonder if this should have targeted the 3.14 branch rather than master.

[chreekat]

I don't know the workflow, tbh. GHC tries to make sure all patches start on master before being backported. That makes sense to me, do that's what I was assuming here. (It'll fix build failures on master, too, as a bonus) pe 21. maalisk. 2025 klo 15.58 Artem Pelenitsyn ***@***.***> kirjoitti:

…

I wonder if this should have targeted the 3.14 branch rather than master. — Reply to this email directly, view it on GitHub <#10843 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEDPKXWP5N275BSQP3KAIT2VQLIDAVCNFSM6AAAAABZP364VKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBTGQ2DMNJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: ulysses4ever]*ulysses4ever* left a comment (haskell/cabal#10843) <#10843 (comment)> I wonder if this should have targeted the 3.14 branch rather than master. — Reply to this email directly, view it on GitHub <#10843 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEDPKXWP5N275BSQP3KAIT2VQLIDAVCNFSM6AAAAABZP364VKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBTGQ2DMNJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Mikolaj]

I think it's not rules out that we will be using this image in cabal 3.16 as well, so I think merging it first to master makes sense. I'm setting the labels according. Thank you @chreekat!

[chreekat]

For 3.16, I think https://gitlab.haskell.org/ghc/ghc/-/issues/25876 is pertinent. It can be discussed outside this PR though. :)

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.