cabal-install 3.14: allow tar-0.7

[juhp]

Backport of #11225 for commercialhaskell/stackage#7838

[juhp]

error: could not lock config file C:/msys64/home/runneradmin/.gitconfig: No such file or directory

It would be nice to have a Hackage revision for https://hackage.haskell.org/package/cabal-install-3.14.2.0

[ulysses4ever]

I did the revision. Let's try to restart the CI..

[Mikolaj]

@juhp didn't you suggest to revise cabal-install-3.14.1.1 instead in commercialhaskell/stackage#7838 (comment)?

[ulysses4ever]

error: could not lock config file C:/msys64/home/runneradmin/.gitconfig: No such file or directory

The Windows part of CI is deffunct until #11105 is backported...

The macos failure is worrying... https://github.com/haskell/cabal/actions/runs/17941483727/job/51124895929?pr=11226

<command line>: can't load framework: Security (not found)
GHCi exited with ExitFailure 1 (use -v for more information)
<command line>: can't load framework: Security (not found)
GHCi exited with ExitFailure 1 (use -v for more information)
cabal-tests: fd:14: hGetLine: end of file

Of course, it has nothing to do with tar (I hope!).

[juhp]

@juhp didn't you suggest to revise cabal-install-3.14.1.1 instead in commercialhaskell/stackage#7838 (comment)?

You are right I did, but realistically we probably won't lift the tar bound in Stackage before 9.12.3 is released I think: I didn't know it was coming soon.

Regardless older versions should never have newer bounds in my opinion.
But we could also revise 3.14.1.1 I suppose :-)

[juhp]

Since 9.14.3 is taking a bit longer than I expected, it would actually be nice to have a revision for cabal-install-3.14.1.1 too.

I tested locally over Stackage Nightly that this builds fine:
with stack --resolver nightly build tar-0.7.0.0 cabal-install-3.14.1.1 --allow-newer

[ulysses4ever]

@juhp you got it!