RE: HP 2013.2 and GHC 7.6.2

| I just spoiled my day by http://hackage.haskell.org/trac/ghc/ticket/7748 | with ghc-7.6.2 in our large project: | hets: <<loop>> | hets works fine with ghc-7.6.1 (and older versions). I haven't located | the error yet, though. | | Yet, I therefore conclude, GHC 7.6.2 ist not suited for the official HP. Happily I have found and fixed #7748 in the 7.6 branch. Christian, is it possible for you to build the 7.6 branch and test with Hets? Simon

Am 16.04.2013 08:35, schrieb Simon Peyton-Jones:
| I just spoiled my day by http://hackage.haskell.org/trac/ghc/ticket/7748 | with ghc-7.6.2 in our large project: | hets: <<loop>> | hets works fine with ghc-7.6.1 (and older versions). I haven't located | the error yet, though. | | Yet, I therefore conclude, GHC 7.6.2 ist not suited for the official HP.
Happily I have found and fixed #7748 in the 7.6 branch.
Christian, is it possible for you to build the 7.6 branch and test with Hets?
Yes, I see no suitable snapshot distribution, though: http://www.haskell.org/ghc/dist/stable/dist What is the exact command to get the relevant ghc sources. Are you planning to make a ghc 7.6.3 release? Thanks Christian
Simon

On Apr 16, 2013, at 3:43 AM, Christian Maeder
What is the exact command to get the relevant ghc sources.
First, make sure that your installed GHC is *not* a snapshot distribution, but one of the main releases (such as 7.6.1 or 7.6.2). You may also want to check out http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation to make sure you have all the needed software. Then, go somewhere convenient on your computer, and run this (assuming Linux/Mac OS): git clone http://darcs.haskell.org/ghc.git; cd ghc; ./sync-all --testsuite get; perl boot; ./configure; make At the end of that (will probably take about an hour), you will have ghc available in <your convenient location>/ghc/inplace/bin/ghc-stage2 I believe you can use a --with-ghc=... option to cabal to install packages with an uninstalled ghc. Or, you could use a --prefix=... option to ./configure, above, and then run `make install` after building. I hope this helps! Richard

Thanks for all the switft work. Here's my understanding of the situation: - 7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. - SPJ has a fix, that works for the minimal code given in the bug report. - Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. - Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2. If that is the state of the world, then we'll delay the HP 2012.2.0.0 a week for 7.6.3. - Mark

I think that’s right. Simon From: ghc-devs-bounces@haskell.org [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Mark Lentczner Sent: 16 April 2013 14:18 To: Richard Eisenberg; Haskell Libraries Cc: Christian Maeder; Ian Lynagh; ghc-devs@haskell.org; haskell-platform@projects.haskell.org Subject: Re: HP 2013.2 and GHC 7.6.2 Thanks for all the switft work. Here's my understanding of the situation: * 7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. * SPJ has a fix, that works for the minimal code given in the bug report. * Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. * Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2. If that is the state of the world, then we'll delay the HP 2012.2.0.0 a week for 7.6.3. - Mark

On 16 April 2013 23:17, Mark Lentczner
Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a week for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

Ivan, do you mean a cabal 1.18 release or...? On Tue, Apr 16, 2013 at 8:17 PM, Ivan Lazar Miljenovic < ivan.miljenovic@gmail.com> wrote:
Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in
On 16 April 2013 23:17, Mark Lentczner
wrote: the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a
week
for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

On 17 April 2013 13:29, Carter Schonwald
Ivan, do you mean a cabal 1.18 release or...?
Just 1.16.0.3; there have been some issues with 1.16.0 (which also shipped with 7.6.2).
On Tue, Apr 16, 2013 at 8:17 PM, Ivan Lazar Miljenovic
wrote: On 16 April 2013 23:17, Mark Lentczner
wrote: Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a week for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

Can anyone comment on the state of cabal, and in particular the version that was shipped with 7.6.2? We should only consider bumping that version if, like with 7.6.2, there is a major bug in it that will affect the Platform's users. If there is, we'll want to consider a point release in preference to a major bump to the "latest-n-greatest". Let's try to keep this last minute bumping to a minimum! On Tue, Apr 16, 2013 at 5:17 PM, Ivan Lazar Miljenovic < ivan.miljenovic@gmail.com> wrote:
Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in
On 16 April 2013 23:17, Mark Lentczner
wrote: the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a
week
for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

i'm nearly through getting a build done (soonish)
do i just need to test the loop file on the ticket, or this "hets" package
too? (which i can't seem to find...)
On Tue, Apr 16, 2013 at 11:44 PM, Mark Lentczner
Can anyone comment on the state of cabal, and in particular the version that was shipped with 7.6.2?
We should only consider bumping that version if, like with 7.6.2, there is a major bug in it that will affect the Platform's users. If there is, we'll want to consider a point release in preference to a major bump to the "latest-n-greatest".
Let's try to keep this last minute bumping to a minimum!
On Tue, Apr 16, 2013 at 5:17 PM, Ivan Lazar Miljenovic < ivan.miljenovic@gmail.com> wrote:
Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just
On 16 April 2013 23:17, Mark Lentczner
wrote: this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a
week
for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

On 17 April 2013 13:44, Mark Lentczner
Can anyone comment on the state of cabal, and in particular the version that was shipped with 7.6.2?
We should only consider bumping that version if, like with 7.6.2, there is a major bug in it that will affect the Platform's users. If there is, we'll want to consider a point release in preference to a major bump to the "latest-n-greatest".
Here's one (admittedly small) issue I've come across: https://github.com/haskell/cabal/issues/1065 I don't have bug numbers for the other issues, but there have also been some where "runhaskell Setup.hs configure --enable-executable profiling" didn't properly set the profiling options for an executable that depended on the library shipped with the same package, etc.
Let's try to keep this last minute bumping to a minimum!
On Tue, Apr 16, 2013 at 5:17 PM, Ivan Lazar Miljenovic
wrote: On 16 April 2013 23:17, Mark Lentczner
wrote: Thanks for all the switft work. Here's my understanding of the situation:
7.6.2 has a bug (#7748) in it, which also appears in a lesser form in 7.6.1. SPJ has a fix, that works for the minimal code given in the bug report. Others are now trying to verify it fixes the bug as it was discovered in the wild, in the hets package. Assuming it does fix, Ian will prepare a 7.6.3 release which is just this bug fix as a delta from 7.6.2.
Can we please get the version of Cabal bumped as well?
If that is the state of the world, then we'll delay the HP 2012.2.0.0 a week for 7.6.3.
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

On Tue, 2013-04-16 at 20:44 -0700, Mark Lentczner wrote:
Can anyone comment on the state of cabal, and in particular the version that was shipped with 7.6.2?
GHC-7.6.1 shipped with Cabal-1.16.0 We subsequently found a few bugs and released Cabal-1.16.0.3 (1.16.0.2 was the brown paper bag release, oops). We (cabal devs) assumed that GHC-7.6.2 would just automatically pick up the latest bug fix release in the Cabal-1.16.0.x series but for some reason that did not happen. Yes ideally we should be using Cabal-1.16.0.3 and if there is a GHC-7.6.3 then that should certainly use Cabal-1.16.0.3. 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. Duncan

Well.... based on Christian's excellent news, looks to mee like there is a candidate for a GHC-7.6.3. And so it sounds like that should pick up Cabal-1.16.0.3. I'd like to limit the micro-bumps as much as possible, is that it, everyone? I'd also like to double confirm with all concerned that we agree that this bug in GHC was serious enough to hold the Platform for (only a week), and deal with potential "last minute scrambling" from library devs and packagers that may result. I don't anticipate any real issue, but we are accepting the risk and stepping up to deal with any. For the record: I'm thumbs up. - Mark

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

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
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

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
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

Am 16.04.2013 14:29, schrieb Richard Eisenberg:
On Apr 16, 2013, at 3:43 AM, Christian Maeder
wrote: What is the exact command to get the relevant ghc sources.
First, make sure that your installed GHC is *not* a snapshot distribution, but one of the main releases (such as 7.6.1 or 7.6.2). You may also want to check out http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation to make sure you have all the needed software. Then, go somewhere convenient on your computer, and run this (assuming Linux/Mac OS):
git clone http://darcs.haskell.org/ghc.git; cd ghc; ./sync-all --testsuite get; perl boot; ./configure; make
Thanks, for this. Do I need to give a branch name (which one?) to the "git clone" command (option -b)? C.
At the end of that (will probably take about an hour), you will have ghc available in <your convenient location>/ghc/inplace/bin/ghc-stage2
I believe you can use a --with-ghc=... option to cabal to install packages with an uninstalled ghc. Or, you could use a --prefix=... option to ./configure, above, and then run `make install` after building.
I hope this helps! Richard

Yes you need to be on branch "ghc-7.6", both for the GHC repos and for all the libraries.
Something like
./sync-all checkout ghc-7.6
should do it
Simon
| -----Original Message-----
| From: Christian Maeder [mailto:Christian.Maeder@dfki.de]
| Sent: 16 April 2013 14:18
| To: Richard Eisenberg
| Cc: Simon Peyton-Jones; Ian Lynagh; Haskell Libraries; ghc-
| devs@haskell.org; haskell-platform@projects.haskell.org
| Subject: Re: HP 2013.2 and GHC 7.6.2
|
| Am 16.04.2013 14:29, schrieb Richard Eisenberg:
| >
| > On Apr 16, 2013, at 3:43 AM, Christian Maeder
|

On Tue, Apr 16, 2013 at 03:18:01PM +0200, Christian Maeder wrote:
Am 16.04.2013 14:29, schrieb Richard Eisenberg:
git clone http://darcs.haskell.org/ghc.git; cd ghc; ./sync-all --testsuite get; perl boot; ./configure; make
Thanks, for this. Do I need to give a branch name (which one?) to the "git clone" command (option -b)?
Yes, you need to add "-b ghc-7.6" to both the clone and the sync-all command. Docs are here: http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources#Gettinga... Thanks Ian
participants (10)
-
Carter Schonwald
-
Christian Maeder
-
Duncan Coutts
-
Ian Lynagh
-
Iavor Diatchki
-
Ivan Lazar Miljenovic
-
Johan Tibell
-
Mark Lentczner
-
Richard Eisenberg
-
Simon Peyton-Jones