Dear all,
cabal-install 3.10.2.0 has been released and is available in ghcup as well as on downloads.haskell.org.
This allowed the cabal team to refine our release process. Especially, the effort put in by our QA testers has been crucial in validating contributions changing user-facing behaviour.
add base to cabal install --lib default env file #8903
This adds base by default to the env file created by cabal install --lib. Further it ensures that packagedbs have been created before adding them to the env file.
Congratulations on this much awaited bug-fix release and thank you @Kleidukos for relentlessly stomping through the undending stream of last minute requests, bugs, fixes and devops overhauls that lead to the 3.10.2.0 release.
@m4dc4p this will have to be Cabal 3.12, which is not scheduled yet. Perhaps, will coincide with the next GHC release. Unless thereās a volunteer to make that release earlier
some repos (such as head.hackage) were not keeping their timestamp.json up to date, and now that cabal-install properly checks this, users may find problems until the repos fix this. in the meantime, the --ignore-expiry flag can be used.
For people who canāt update to 3.10.2.0 (e.g. due to windows regression), I have backported the fix downstream and created a distributor release 3.6.2.0-p1, which now is the new ārecommendedā version, until 3.10 branch fixes the regressions.
To update, run either:
ghcup install cabal 3.6.2.0-p1
or
ghcup install cabal 3.10.2.0
All other vulnerable versions that the user tries to install are going to write a post-install message:
[ Info ] This release is vulnerable: https://github.com/haskell/security-advisories/blob/main/advisories/hackage/cabal-install/HSEC-2023-0015.md
[ ... ] Update to 3.6.2.0-p1 or 3.10.2.0.
[ ... ]
note: weāve made progress on the single windows regression i know of, tracing it to an intermittent failure in cabal run having to do with the compiled script caching mechanism producing (depending on the hash) filepaths which are valid on windows but problematic specifically to llvm-ar. hopefully we can resolve this soon and get out a new version of cabal-install which works well on all platforms, including in this circumstance.