On Wed, Apr 17, 2013 at 02:48:26PM +0100, Duncan Coutts wrote:

In the absence of a GHC-7.6.3, I'm not sure if it's practical for the HP to bump the Cabal version.

My proposal was 7.6.3 was a minimal release in a very short timeframe, to just fix #7748. Any additional changes introduce a possibility of regression. If you think that 7.6.2+1.16.0 would be OK, then it sounds like the fixes in 1.16.0.3 wouldn't be worth the risk (there are a number of GHC fixes that we won't be merging either, for the same reason). Thanks Ian

Even though there's some risk bumping the Cabal version used in GHC, I think it would be worth it given that quite a few people have tripped over the bugs fixed in 1.16.0.3. On Wed, Apr 17, 2013 at 8:20 AM, Iavor Diatchki wrote:

Hello,

cabal-install 1.16.0 and 1.16.0.1 have some serious bugs that one encounters rather quickly. For example, at work I wasted some time until I figured out that cabal was generating a 'Paths_' module that does not compile. Because of this, you can't even use it to install a newer version of itself, where the problem is fixed: you have to manually bootstrap the new version with the script!

I think it would be quite unfortunate to make yet another GHC release that ships with it, let alone add it to the Haskell platform.

-Iavor

On Wed, Apr 17, 2013 at 7:17 AM, Ian Lynagh wrote:

...

On Wed, Apr 17, 2013 at 02:48:26PM +0100, Duncan Coutts wrote:

...

In the absence of a GHC-7.6.3, I'm not sure if it's practical for the HP to bump the Cabal version.

My proposal was 7.6.3 was a minimal release in a very short timeframe, to just fix #7748. Any additional changes introduce a possibility of regression. If you think that 7.6.2+1.16.0 would be OK, then it sounds like the fixes in 1.16.0.3 wouldn't be worth the risk (there are a number of GHC fixes that we won't be merging either, for the same reason).

Thanks Ian

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

On Wed, Apr 17, 2013 at 05:37:37PM +0200, Gabor Greif wrote:

On 4/17/13, Iavor Diatchki wrote:

...

Hello,

cabal-install 1.16.0 and 1.16.0.1 have some serious bugs that one encounters rather quickly. For example, at work I wasted some time until I figured out that cabal was generating a 'Paths_' module that does not compile. Because of this, you can't even use it to install a newer version of itself, where the problem is fixed: you have to manually bootstrap the new version with the script!

I came up with this.

http://heisenbug.blogspot.fr/2013/02/old-cabal-subhell.html

Pretty much what you have experienced.

This doesn't appear to affect the Cabal that GHC 7.6.2 ships with. I get ... catchIO :: IO a -> (Exception.IOException -> IO a) -> IO a catchIO = Exception.catch ... getBinDir = catchIO (getEnv "HTTP_bindir") (\_ -> return bindir) in Paths_HTTP. Thanks Ian

These are the bugs in *Cabal* that got fixed between 1.16.0 and 1.16.0.3 that are relevant: * Fix bug that makes setting "verbose: 1" or "jobs: N" in the ~/.cabal/config file crash (#980) * Fix the logic for building profiled executables with TemplateHaskell. * Fix logic for building dynamic executables with TemplateHaskell Nothing major. We could probably live without these fixes. We do need a new *cabal-install* however, as it fixes: Disable setting the jobs: $nprocs line in default ~/.cabal config It breaks for fresh installs with users who have Cabal-1.6.0 rather than Cabal-1.6.0.1, ie users of ghc-7.6.1. On Wed, Apr 17, 2013 at 10:15 AM, Mark Lentczner wrote:

If the bug is in cabal-install 0.3, that is easy - as HP picks and builds that. If the bug in cabal, that requires a bump in what GHC central builds and packages.

Which is it?

- Mark

On Wed, Apr 17, 2013 at 8:46 AM, Ian Lynagh wrote:

...

On Wed, Apr 17, 2013 at 05:37:37PM +0200, Gabor Greif wrote:

...

On 4/17/13, Iavor Diatchki wrote:

...

Hello,

cabal-install 1.16.0 and 1.16.0.1 have some serious bugs that one encounters rather quickly. For example, at work I wasted some time until I figured out that cabal was generating a 'Paths_' module that does not compile. Because of this, you can't even use it to install a newer version of itself, where the problem is fixed: you have to manually bootstrap the new version with the script!

I came up with this.

http://heisenbug.blogspot.fr/2013/02/old-cabal-subhell.html

Pretty much what you have experienced.

This doesn't appear to affect the Cabal that GHC 7.6.2 ships with. I get

...

catchIO :: IO a -> (Exception.IOException -> IO a) -> IO a catchIO = Exception.catch

...

getBinDir = catchIO (getEnv "HTTP_bindir") (\_ -> return bindir)

in Paths_HTTP.

Thanks Ian

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs