[ANN] Cabal-3.4.1.0, cabal-install-3.4.1.0, Cabal-3.6.2.0, cabal-install-3.6.2.0

Announcements
#1

The Cabal team is excited to announce the release of Cabal-3.6.2.0, and cabal-install-3.6.2.0.

Changelog for Cabal-3.6.2.0 and cabal-install-3.6.2.0

This is the fifth release of the 3.0 release series for both packages. This minor version release introduces a set of fixes for some regressions seen when the tool interacts with autoconf, as well as some fixes for regressions to the way Paths_ modules interact with non-standard preludes:

  • Making Paths_ modules work with non-standard preludes again #5962

    • Generate Paths_ module with qualified Data.List.last import so that compatibility with non-standard preludes is not regressed compared to cabal 3.4.

  • Windows: redo the fix to breakage caused by new autoconf; the wrong fix made cabal sometimes fail with old autoconf #7494 #7649

    • Reverts #7510 that failed on Windows when used with pre-generated scripts included in packages such as network, time, process.
    • Adds a subtler fix/workaround for the deficiencies of new autoconf versions on Windows.

IMPORTANT NOTE: The last bug affects configuration files generated with autoconf-2.70 or later. They will not work with cabal-3.4.0.0. Please either upgrade to 3.4.1.0 or the new 3.6.2.0 releases.

I’d like to thank the many contributors who offered patches, tickets, and other help in the preparation of this release. We appreciate all of your help!

Happy hacking!

5 Likes
#2

Hi, I notice a couple of potential issues.

  1. Installing from https://downloads.haskell.org/~cabal/cabal-install-3.6.2.0/cabal-install-3.6.2.0-x86_64-linux-deb10.tar.xz and running cabal --version gives me
cabal-install version 3.4.1.0
compiled using version 3.4.1.0 of the Cabal library
  1. The previous 3.6.0.0 release included https://downloads.haskell.org/~cabal/cabal-install-3.6.0.0/cabal-install-3.6.0.0-x86_64-linux.tar.xz which works on debian 9 + 10. However, the new release only has a linux-deb10 variant which does only work on debian 10. Is the intention to drop support for debian 9? Which would be fine, but if it’s intentional it should explicitly noted I think.

Thanks

#3

Hey Alistair thanks for the report - indeed we mixed up one of the binaries! Easy fix and it should be updated by eod

3 Likes
#4

Regarding deb9 - the version was been discontinued by debian over a year ago, and so support has been discontinued in cabal.

2 Likes
#5

There are static bindists for the needy:

4 Likes