Upgrade to cabal-install 1.20

[rehno-lindeque]

Cabal 1.20 with cabal freeze has been released!

[begriffs]

Whoo hoo! 🎆

I'll get the new binaries ready.

[rehno-lindeque]

🎉

[begriffs]

Looks like the release is not yet available at http://www.haskell.org/cabal/release/cabal-install-1.20.0.0/cabal-install-1.20.0.0.tar.gz

Also when I run

cabal update
cabal install Cabal-1.20.0.0 cabal-install-1.20.0.0

on one of my Heroku instances it fails saying setup: /usr/bin/ar: permission denied.

Once they make the new version available on haskell.org then I can bump my CABAL_VER environment variable, redeploy and copy the generated files to S3.

[rehno-lindeque]

Aww, too bad... Well I'll keep an eye out for it, shouldn't take long.

[rehno-lindeque]

The release is uploaded :)

[begriffs]

Using the cabal-install release bootstrap gives me the same problem as I had before. After successful compilation it has trouble at the linking step.

Linking Setup ...
Configuring Cabal-1.20.0.0...
Setup: /usr/bin/ar: permission denied

Error during cabal-install bootstrap:
Configuring the Cabal package failed.

To reproduce, heroku config:set CABAL_VER=1.20.0.0 and push a project.

[begriffs]

The problem is happening when trying to configure the cabal library itself. The Setup configure script refuses to use binaries in /usr/bin despite read and execute permissions being fine on all of them. When I copy binaries like /usr/bin/ar to /app/vendor/bin/ar and pass --with-ar=/app/vendor/bin/ar it is OK, but then it complains about GCC. I repeat the process for all binaries it wants but then it gets to the libraries in /usr/lib and freaks out about them too.

Something weird is going on because installing cabal-1.18.1 works just fine from its bootstrap script.

[begriffs]

@puffnfresh have you ever seen this kind of build bug?

[puffnfresh]

@begriffs nope - that's a new one!

[rehno-lindeque]

Yay!