Advance warning to package authors of breakage

package authors, I'm preparing to release two new versions of cabal-install. The following packages are broken, and the new cabal-install releases will mean that more users run into the breakage than do so currently. All these packages claim to work with base 3 *and* with base 4, however they actually only work with base 3. The new cabal-install will build them against base 4 and so users will notice that they are broken. I'm emailing the whole libs list because while I was able to build most of hackage, I could not build all of it, so there may be other packages with this same problem. FileManipCompat-0.14 type-level-0.2.3 compact-string-0.3.1 ghc-core-0.5 hsmtpclient-1.0 pointful-1.0.1 show-0.3.3 These packages all use "build-depends: base >= 3 && < 4" (except for ghc-core which cheekily uses "build-depends: base < 10" --- a practise we will ban if it becomes any more popular). Current versions of cabal-install choose base version 3 in this case, the new cabal-install will choose base version 4 in this case. The reason for the somewhat odd current behaviour was to help with packages that only said "build-depends: >=3". Now that we require an upper bound too, the new behaviour is to only apply the backwards compat preferences for version ranges that are unbounded above. For ones that are bounded above we go back to picking the highest version by default. Duncan

On Mon, 2009-11-16 at 00:47 +0000, Duncan Coutts wrote:
These packages all use "build-depends: base >= 3 && < 4"
Sorry, typo. Of course that should have been: "build-depends: base >= 3 && < 5"
Current versions of cabal-install choose base version 3 in this case, the new cabal-install will choose base version 4 in this case.
With the typo fix above this bit is now true. :-) Sorry for the confusion. Duncan

On Mon, 2009-11-16 at 03:49 +0100, Svein Ove Aas wrote:
On Mon, Nov 16, 2009 at 1:47 AM, Duncan Coutts
wrote: package authors,
I'm preparing to release two new versions of cabal-install.
Does this new version happen to work with the GHC 6.12 release candidate?
Version 0.8 will do (the current darcs 0.7.5 works with it already). Version 0.6.4 may or may not, depending on how difficult it is to hack it. If it does, it'll probably only work well enough to let you "cabal install cabal-install" and will probably prompt you to do so frequently. If not, then it'll just break with a better error message. Duncan

On Mon, 2009-11-16 at 00:47 +0000, Duncan Coutts wrote:
package authors,
I'm preparing to release two new versions of cabal-install.
The cabal-install 0.6.4 version has now been released. Users will get prompted to upgrade when they next run cabal update. Note this version still will not work with ghc-6.12. But it will give people a better error message and tell them how to upgrade. The (as yet unreleased) cabal-install 0.8.x version will work with ghc-6.12. This version is only available via darcs at the moment. darcs get --partial http://darcs.haskell.org/cabal-install If you do want to test the ghc-6.12 RC, I recommend upgrading your cabal-install to a 0.8.x version before removing any older ghc version you've currently got. One additional fallout from the cabal-install release is that mtlx-0.1.1 is now broken. The cabal program will refuse to unpack mtlx-0.1.1.tar.gz because it classifies it as a tarbomb. A tarbomb is a tar file that would unpack files into the top level directory rather than all files under the subdirectory ./mtlx-0.1.1/. The tar file contains the stray entry "./._mtlx-0.1.1". This package will need to be re-uploaded. My suggestion is to use cabal sdist since this only selects the required files (but do check all the required files are listed) and it always uses a portable tar format. Duncan
participants (2)
-
Duncan Coutts
-
Svein Ove Aas