From hvr at gnu.org  Mon Dec  1 18:32:10 2014
From: hvr at gnu.org (Herbert Valerio Riedel)
Date: Mon, 01 Dec 2014 19:32:10 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
Message-ID: <87iohvfcgl.fsf@gnu.org>

Hello Cabal developers!

To keep it short: GHC 7.10.1 RC1 is planned for a release shortly before
Xmas, and it would be great if there was a Cabal 1.22.x RC to go along
with that.

Is it possible for you to get Cabal (the library) in such a state by
mid-December (i.e. in 2 weeks from now)?

Cheers,
  hvr

From spam at scientician.net  Mon Dec  1 18:40:02 2014
From: spam at scientician.net (Bardur Arantsson)
Date: Mon, 01 Dec 2014 19:40:02 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <87iohvfcgl.fsf@gnu.org>
References: <87iohvfcgl.fsf@gnu.org>
Message-ID: <m5icm2$m37$1@ger.gmane.org>

On 2014-12-01 19:32, Herbert Valerio Riedel wrote:
> Hello Cabal developers!
> 
> To keep it short: GHC 7.10.1 RC1 is planned for a release shortly before
> Xmas, and it would be great if there was a Cabal 1.22.x RC to go along
> with that.
> 
> Is it possible for you to get Cabal (the library) in such a state by
> mid-December (i.e. in 2 weeks from now)?
> 

Mostly out of curiousity: is there *any* conceivable chance of getting
the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
is also on this list.)

Regards,


From stegeman at gmail.com  Tue Dec  2 07:53:21 2014
From: stegeman at gmail.com (Luite Stegeman)
Date: Tue, 2 Dec 2014 08:53:21 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <m5icm2$m37$1@ger.gmane.org>
References: <87iohvfcgl.fsf@gnu.org>
	<m5icm2$m37$1@ger.gmane.org>
Message-ID: <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>

On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
wrote:

>
> Mostly out of curiousity: is there *any* conceivable chance of getting
> the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
> is also on this list.)
>

Yes, I am on this list. A small part has already been merged, and there's a
pull request for the changes in the package description and flags, which
include the GHCJS compiler flavour. While discussing the patch with Duncan,
we agreed that a few changes were in order, which I've made, I'll amend the
pull request later today.

What's left then is the backend itself. The changes there are only in the
build system, so they don't touch the public API / file formats, but on the
other hand they do touch quite a bit of code and require some restructuring
of the GHC backend to allow some of the code to be reused without
copy/pasting the whole backend (smaller customizations are required for
ghc-pkg and haddock).

I'm going to spend some time this week to submit the next part of the code,
test it with my experimental GHC 7.10 branch of GHCJS. The important public
changes have been discussed / prepared already, so it'll mostly come down
to how well this code will stand up to scrutinization of the reviewers.

luite
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/92288e86/attachment.html>

From johan.tibell at gmail.com  Tue Dec  2 10:16:46 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 2 Dec 2014 11:16:46 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>
References: <87iohvfcgl.fsf@gnu.org> <m5icm2$m37$1@ger.gmane.org>
 <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>
Message-ID: <CAK-tuPb26Nmy6KFVEy20SVLkkT2rg_VowCHOwfTcCqtnM_++0A@mail.gmail.com>

I think I can have a RC out without 2 weeks.

On Tue, Dec 2, 2014 at 8:53 AM, Luite Stegeman <stegeman at gmail.com> wrote:

>
>
> On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
> wrote:
>
>>
>> Mostly out of curiousity: is there *any* conceivable chance of getting
>> the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
>> is also on this list.)
>>
>
> Yes, I am on this list. A small part has already been merged, and there's
> a pull request for the changes in the package description and flags, which
> include the GHCJS compiler flavour. While discussing the patch with Duncan,
> we agreed that a few changes were in order, which I've made, I'll amend the
> pull request later today.
>
> What's left then is the backend itself. The changes there are only in the
> build system, so they don't touch the public API / file formats, but on the
> other hand they do touch quite a bit of code and require some restructuring
> of the GHC backend to allow some of the code to be reused without
> copy/pasting the whole backend (smaller customizations are required for
> ghc-pkg and haddock).
>
> I'm going to spend some time this week to submit the next part of the
> code, test it with my experimental GHC 7.10 branch of GHCJS. The important
> public changes have been discussed / prepared already, so it'll mostly come
> down to how well this code will stand up to scrutinization of the reviewers.
>
> luite
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/ae884908/attachment.html>

From spam at scientician.net  Tue Dec  2 16:13:51 2014
From: spam at scientician.net (Bardur Arantsson)
Date: Tue, 02 Dec 2014 17:13:51 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>
References: <87iohvfcgl.fsf@gnu.org>	<m5icm2$m37$1@ger.gmane.org>
 <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>
Message-ID: <m5kofv$835$1@ger.gmane.org>

On 2014-12-02 08:53, Luite Stegeman wrote:
> On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
> wrote:
> 
>>
>> Mostly out of curiousity: is there *any* conceivable chance of getting
>> the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
>> is also on this list.)
>>
> 
> Yes, I am on this list. A small part has already been merged, and there's a
> pull request for the changes in the package description and flags, which
> include the GHCJS compiler flavour. While discussing the patch with Duncan,
> we agreed that a few changes were in order, which I've made, I'll amend the
> pull request later today.
> 
> What's left then is the backend itself. The changes there are only in the
> build system, so they don't touch the public API / file formats, but on the
> other hand they do touch quite a bit of code and require some restructuring
> of the GHC backend to allow some of the code to be reused without
> copy/pasting the whole backend (smaller customizations are required for
> ghc-pkg and haddock).
> 
> I'm going to spend some time this week to submit the next part of the code,
> test it with my experimental GHC 7.10 branch of GHCJS. The important public
> changes have been discussed / prepared already, so it'll mostly come down
> to how well this code will stand up to scrutinization of the reviewers.

Thanks for the status update. Sounds like there may be exciting times
ahead for those of us who are forced to work on front ends as well as
backends!

(I've been experimenting a bit and GHCJS looks *really* promising for
frontend development, especially once the "tooling" support gets merged.)

Here's to hoping the reviewers will be kind! :)

Regards,


From bos at serpentine.com  Tue Dec  2 21:06:50 2014
From: bos at serpentine.com (Bryan O'Sullivan)
Date: Tue, 2 Dec 2014 13:06:50 -0800
Subject: Linker change in GHC 7.8 leads to widespread issues
Message-ID: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>

Hi folks,

It seems that something somewhere in linker-land changed in GHC 7.8 such
that packages that include C components now need to be built with
position-independent code on some platforms.

This affects a number of my packages. I am not sure whether the correct fix
is to pepper all of these packages (and presumably dozens to hundreds of
other packages on Hackage) with "-fPIC" and issue new releases, or to
instead teach Cabal to do this. It would certainly be vastly less
disruptive to all of the affected package authors to have Cabal
automatically do the right thing here.

Could someone who's closer to both piles of code please suggest which
approach they believe is more appropriate?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/56c93242/attachment.html>

From carter.schonwald at gmail.com  Tue Dec  2 21:31:15 2014
From: carter.schonwald at gmail.com (Carter Schonwald)
Date: Tue, 2 Dec 2014 16:31:15 -0500
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
Message-ID: <CAHYVw0ykKLi5OyEp425=Mq94_PO8N+goWqUgNrGWjuiq7KdmiA@mail.gmail.com>

whats an example of such a package?

On Tue, Dec 2, 2014 at 4:06 PM, Bryan O'Sullivan <bos at serpentine.com> wrote:

> Hi folks,
>
> It seems that something somewhere in linker-land changed in GHC 7.8 such
> that packages that include C components now need to be built with
> position-independent code on some platforms.
>
> This affects a number of my packages. I am not sure whether the correct
> fix is to pepper all of these packages (and presumably dozens to hundreds
> of other packages on Hackage) with "-fPIC" and issue new releases, or to
> instead teach Cabal to do this. It would certainly be vastly less
> disruptive to all of the affected package authors to have Cabal
> automatically do the right thing here.
>
> Could someone who's closer to both piles of code please suggest which
> approach they believe is more appropriate?
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/0a1c20ff/attachment.html>

From mietek at bak.io  Tue Dec  2 21:43:47 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Tue, 2 Dec 2014 21:43:47 +0000
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CAHYVw0ykKLi5OyEp425=Mq94_PO8N+goWqUgNrGWjuiq7KdmiA@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CAHYVw0ykKLi5OyEp425=Mq94_PO8N+goWqUgNrGWjuiq7KdmiA@mail.gmail.com>
Message-ID: <D1845D7B-7E6F-40D4-93EE-2E940A4D2B96@bak.io>

On 2014-12-02, at 21:31, Carter Schonwald <carter.schonwald at gmail.com> wrote:

> whats an example of such a package?


text-icu.
https://github.com/bos/text-icu/pull/9

FWIW, I?m in favour of fixing this at the Cabal level.
https://github.com/haskell/cabal/issues/2207

-- 
Mi?tek


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/939dbd24/attachment.bin>

From johan.tibell at gmail.com  Tue Dec  2 22:50:39 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 2 Dec 2014 23:50:39 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <D1845D7B-7E6F-40D4-93EE-2E940A4D2B96@bak.io>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CAHYVw0ykKLi5OyEp425=Mq94_PO8N+goWqUgNrGWjuiq7KdmiA@mail.gmail.com>
 <D1845D7B-7E6F-40D4-93EE-2E940A4D2B96@bak.io>
Message-ID: <CAK-tuPY1=XBZbZW2V+Z1N5EDshKu0_f7k04CqFaXFJkBScTdXg@mail.gmail.com>

If someone can figure out what the right fix is and if it happens to be in
Cabal I'd be happy to merge any changes.

On Tue, Dec 2, 2014 at 10:43 PM, Mi?tek Bak <mietek at bak.io> wrote:

> On 2014-12-02, at 21:31, Carter Schonwald <carter.schonwald at gmail.com>
> wrote:
>
> > whats an example of such a package?
>
>
> text-icu.
> https://github.com/bos/text-icu/pull/9
>
> FWIW, I?m in favour of fixing this at the Cabal level.
> https://github.com/haskell/cabal/issues/2207
>
> --
> Mi?tek
>
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141202/b9c686a4/attachment.html>

From marlowsd at gmail.com  Wed Dec  3 12:03:42 2014
From: marlowsd at gmail.com (Simon Marlow)
Date: Wed, 03 Dec 2014 12:03:42 +0000
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <D1845D7B-7E6F-40D4-93EE-2E940A4D2B96@bak.io>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CAHYVw0ykKLi5OyEp425=Mq94_PO8N+goWqUgNrGWjuiq7KdmiA@mail.gmail.com>
 <D1845D7B-7E6F-40D4-93EE-2E940A4D2B96@bak.io>
Message-ID: <547EFC1E.1030201@gmail.com>

On 02/12/2014 21:43, Mi?tek Bak wrote:
> On 2014-12-02, at 21:31, Carter Schonwald <carter.schonwald at gmail.com> wrote:
>
>> whats an example of such a package?
>
>
> text-icu.
> https://github.com/bos/text-icu/pull/9
>
> FWIW, I?m in favour of fixing this at the Cabal level.
> https://github.com/haskell/cabal/issues/2207

I'm actually rather surprised we got away without doing this up to now. 
  Why haven't there been more complaints?

Cheers,
Simon


From johan.tibell at gmail.com  Wed Dec  3 16:51:22 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Wed, 3 Dec 2014 17:51:22 +0100
Subject: Ready to make release candidates for 1.18 and 1.20 bugfix releases
Message-ID: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>

Hi!

I believe I have merged all the fixes people wanted to see in 1.18 and
1.20. Anyone who's interested please double-check that your fixes are in:

1.18:
https://github.com/haskell/cabal/compare/cabal-install-v1.18.0.5...1.18

1.20:
https://github.com/haskell/cabal/compare/cabal-install-v1.20.0.3...1.20

If everyone are happy with these, I will try to make some releases this
weekend.

-- Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141203/d4231146/attachment.html>

From the.dead.shall.rise at gmail.com  Wed Dec  3 17:04:12 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Wed, 3 Dec 2014 18:04:12 +0100
Subject: Ready to make release candidates for 1.18 and 1.20 bugfix releases
In-Reply-To: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>
References: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>
Message-ID: <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>

Hi,

On 3 December 2014 at 17:51, Johan Tibell <johan.tibell at gmail.com> wrote:
> Hi!
>
> I believe I have merged all the fixes people wanted to see in 1.18 and 1.20.

We probably also want to include a fix for
https://github.com/haskell/cabal/issues/2207
I'll write a patch unless someone beats me to it.

From mietek at bak.io  Wed Dec  3 18:04:47 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Wed, 3 Dec 2014 18:04:47 +0000
Subject: Ready to make release candidates for 1.18 and 1.20 bugfix releases
In-Reply-To: <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>
References: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>
 <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>
Message-ID: <69710285-C411-43DF-8102-BFE4C097F8FF@bak.io>

I don?t see ?Self-constraint not included in frozen constraints? (8ed42ce) on the list for 1.20, and I?d very much like for it to be included.

This commit is included in PR#1990, and is a fix for #1908.

https://github.com/haskell/cabal/pull/1990
https://github.com/haskell/cabal/issues/1908

-- 
Mi?tek




On 2014-12-03, at 17:04, Mikhail Glushenkov <the.dead.shall.rise at gmail.com> wrote:

> Hi,
> 
> On 3 December 2014 at 17:51, Johan Tibell <johan.tibell at gmail.com> wrote:
>> Hi!
>> 
>> I believe I have merged all the fixes people wanted to see in 1.18 and 1.20.
> 
> We probably also want to include a fix for
> https://github.com/haskell/cabal/issues/2207
> I'll write a patch unless someone beats me to it.
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141203/d0193793/attachment.bin>

From mietek at bak.io  Wed Dec  3 18:53:22 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Wed, 3 Dec 2014 18:53:22 +0000
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <1092323127.2788068.1417631113995.JavaMail.yahoo@jws100141.mail.ne1.yahoo.com>
References: <547EFC1E.1030201@gmail.com>
 <1092323127.2788068.1417631113995.JavaMail.yahoo@jws100141.mail.ne1.yahoo.com>
Message-ID: <BBD337ED-FC7C-404C-93AC-EEF3800F5C1A@bak.io>

I agree, and I?m hoping to help improve these matters with my project, Halcyon (https://halcyon.sh/).

Halcyon allows all build-time and run-time dependencies of an application to be explicitly declared and installed with a single invocation.  This builds on the great work done recently in Cabal to get us `cabal freeze`, and works around many long-standing Cabal issues, such as the inability to automatically install missing build-tools.

Halcyon can also be used to restore entire Haskell installations in seconds, and supports GHC versions including 7.8.3, 7.8.2, 7.6.3, 7.6.1, 7.4.2, 7.2.2, and 7.0.4.  Hopefully, being able to swap GHC versions in and out, without needing to have them on disk, should help lessen the amount of work needed for comprehensive testing.

I am currently putting the final touches on my project before announcement.  Please let me know what you think.

-- 
Mi?tek




On 2014-12-03, at 18:25, Howard B. Golden <howard_b_golden at yahoo.com> wrote:

> Hi,
> 
> There aren't more complaints because most people haven't tried 7.8 seriously yet. (I didn't notice the problem since I've only been using GHC 7.8 under Windows.) This points out the need for some sort of regular testing of canaries (full systems producing known results) to test the entire toolchain including common libraries (HP, perhaps) and Cabal.
> 
> At the risk of antagonizing the developers again, I will point out that there is a bit of disconnect between GHC developers, Cabal developers, library developers and users (application developers). Without slowing the GHC developers' creativity, there is a need to look at the experience of the application developers. FWIW, my sense is that there is too much turbulence for many potential application developers to adopt Haskell as their production platform unless they have significant in-house resources to deal with the rapid changes. (As as thought experiment, how many changes have to be made to Real World Haskell's programs to get them to run?)
> 
> 
> Howard
> 
> 
> 
> ----- Original Message -----
> From: Simon Marlow <marlowsd at gmail.com>
> To: Mi?tek Bak <mietek at bak.io>; Carter Schonwald <carter.schonwald at gmail.com>
> Cc: "cabal-devel at haskell.org" <cabal-devel at haskell.org>; "ghc-devs at haskell.org" <ghc-devs at haskell.org>
> Sent: Wednesday, December 3, 2014 4:03 AM
> Subject: Re: Linker change in GHC 7.8 leads to widespread issues
> 
> I'm actually rather surprised we got away without doing this up to now. 
>  Why haven't there been more complaints?
> 
> Cheers,
> Simon
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141203/4a51e11c/attachment-0001.bin>

From the.dead.shall.rise at gmail.com  Wed Dec  3 20:49:20 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Wed, 3 Dec 2014 21:49:20 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
Message-ID: <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>

Hi,

On 2 December 2014 at 22:06, Bryan O'Sullivan <bos at serpentine.com> wrote:
> Hi folks,
>
> It seems that something somewhere in linker-land changed in GHC 7.8 such
> that packages that include C components now need to be built with
> position-independent code on some platforms.

I've now fixed this issue in Cabal HEAD and also pushed the fix to
1.20 and 1.18 branches. 1.20 and 1.18 point releases should be out
soon.

From the.dead.shall.rise at gmail.com  Wed Dec  3 20:50:29 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Wed, 3 Dec 2014 21:50:29 +0100
Subject: Ready to make release candidates for 1.18 and 1.20 bugfix releases
In-Reply-To: <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>
References: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>
 <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>
Message-ID: <CA+tcxkAJY8T+j=WJw2cB2q_Pm7ujkFW7Ucr92L+N04Mrq16F2Q@mail.gmail.com>

Hi,

On 3 December 2014 at 18:04, Mikhail Glushenkov
<the.dead.shall.rise at gmail.com> wrote:
> We probably also want to include a fix for
> https://github.com/haskell/cabal/issues/2207
> I'll write a patch unless someone beats me to it.

This is now fixed both in HEAD and in 1.20/1.18.

From bos at serpentine.com  Wed Dec  3 23:44:09 2014
From: bos at serpentine.com (Bryan O'Sullivan)
Date: Wed, 3 Dec 2014 15:44:09 -0800
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
Message-ID: <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>

On Wed, Dec 3, 2014 at 12:49 PM, Mikhail Glushenkov <
the.dead.shall.rise at gmail.com> wrote:

> I've now fixed this issue in Cabal HEAD and also pushed the fix to
> 1.20 and 1.18 branches. 1.20 and 1.18 point releases should be out
> soon.
>

Thanks, Mikhail! Does this imply that package authors can simply advise bug
reporters to upgrade cabal-install?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141203/fad83aec/attachment.html>

From the.dead.shall.rise at gmail.com  Thu Dec  4 00:08:07 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Thu, 4 Dec 2014 01:08:07 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
Message-ID: <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>

Hi,

On 4 December 2014 at 00:44, Bryan O'Sullivan <bos at serpentine.com> wrote:
> Thanks, Mikhail! Does this imply that package authors can simply advise bug
> reporters to upgrade cabal-install?

Yes, once the new point releases of Cabal/cabal-install are out (in a
week or two, according to Johan).

From mail at joachim-breitner.de  Thu Dec  4 08:45:07 2014
From: mail at joachim-breitner.de (Joachim Breitner)
Date: Thu, 04 Dec 2014 09:45:07 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
Message-ID: <1417682707.1485.1.camel@joachim-breitner.de>

Hi,


Am Donnerstag, den 04.12.2014, 01:08 +0100 schrieb Mikhail Glushenkov:
> On 4 December 2014 at 00:44, Bryan O'Sullivan <bos at serpentine.com> wrote:
> > Thanks, Mikhail! Does this imply that package authors can simply advise bug
> > reporters to upgrade cabal-install?
> 
> Yes, once the new point releases of Cabal/cabal-install are out (in a
> week or two, according to Johan).

is the bug in Cabal or cabal-install? If the former, are we going to
include a fixed version of Cabal in GHC-7.8.4?

Greetings,
Joachim

-- 
Joachim ?nomeata? Breitner
  mail at joachim-breitner.de ? http://www.joachim-breitner.de/
  Jabber: nomeata at joachim-breitner.de  ? GPG-Key: 0xF0FBF51F
  Debian Developer: nomeata at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141204/26546959/attachment.sig>

From johan.tibell at gmail.com  Thu Dec  4 12:16:11 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Thu, 4 Dec 2014 13:16:11 +0100
Subject: Ready to make release candidates for 1.18 and 1.20 bugfix releases
In-Reply-To: <CA+tcxkAJY8T+j=WJw2cB2q_Pm7ujkFW7Ucr92L+N04Mrq16F2Q@mail.gmail.com>
References: <CAK-tuPbzTyFTSMVHXvfOD7E61tQLDAXnv=ozvSd14WWWaxyPkA@mail.gmail.com>
 <CA+tcxkBUrrrj8Xv18oT69RBdgem4FPT9TKktNjcbJwC6+zdxmQ@mail.gmail.com>
 <CA+tcxkAJY8T+j=WJw2cB2q_Pm7ujkFW7Ucr92L+N04Mrq16F2Q@mail.gmail.com>
Message-ID: <CAK-tuPawXazhNAwhNss1uZ3cVO3r+=m72b2FW6==r0dMGPM3Lw@mail.gmail.com>

I've cherry-picked the commit from
https://github.com/haskell/cabal/pull/1990. Are we good to go?

On Wed, Dec 3, 2014 at 9:50 PM, Mikhail Glushenkov <
the.dead.shall.rise at gmail.com> wrote:

> Hi,
>
> On 3 December 2014 at 18:04, Mikhail Glushenkov
> <the.dead.shall.rise at gmail.com> wrote:
> > We probably also want to include a fix for
> > https://github.com/haskell/cabal/issues/2207
> > I'll write a patch unless someone beats me to it.
>
> This is now fixed both in HEAD and in 1.20/1.18.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141204/4178df59/attachment.html>

From johan.tibell at gmail.com  Thu Dec  4 12:52:40 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Thu, 4 Dec 2014 13:52:40 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CAOrUaLa0bv9x-kr6QmyDTDKLWwr3tEN-4mcxWVd8eCn=zAvcWg@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <CAOrUaLa0bv9x-kr6QmyDTDKLWwr3tEN-4mcxWVd8eCn=zAvcWg@mail.gmail.com>
Message-ID: <CAK-tuPZZ33F7GDu4vV132pc0rhepb5WMBFWsfBhj3x4XUtoyYA@mail.gmail.com>

I've merged the patches into the 1.20 branch. Look forward to a patch
release this weekend.

On Thu, Dec 4, 2014 at 1:43 PM, Yitzchak Gale <gale at sefer.org> wrote:

> Bryan O'Sullivan wrote:
> >> It seems that something somewhere in linker-land
> >> changed in GHC 7.8 such that packages that include
> >> C components now need to be built with
> >> position-independent code on some platforms...
> >> I am not sure whether the correct fix is to pepper?
> >> packages... with "-fPIC"... or to instead teach Cabal
> >> to do this.
>
> Aha! Thanks for this explanation of what I have been
> suffering from.
>
> Mikhail Glushenkov wrote:
> > I've now fixed this issue in Cabal HEAD and also pushed the fix to
> > 1.20 and 1.18 branches. 1.20 and 1.18 point releases should be out
> > soon.
>
> Thanks a million for the speedy response to this
> serious issue!
>
> I can't wait for the point releases. I'll go with HEAD on one
> of the branches for now.
>
> -Yitz
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141204/9f1c49ad/attachment.html>

From the.dead.shall.rise at gmail.com  Thu Dec  4 16:44:45 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Thu, 4 Dec 2014 17:44:45 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <1417682707.1485.1.camel@joachim-breitner.de>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <1417682707.1485.1.camel@joachim-breitner.de>
Message-ID: <CA+tcxkBYtPwbofGjb6geb1yDy=ooEmboiyCx-d283xrwHEReSA@mail.gmail.com>

Hi,

On 4 December 2014 at 09:45, Joachim Breitner <mail at joachim-breitner.de> wrote:
> is the bug in Cabal or cabal-install?

It's in Cabal. So once the new point releases are out, the users will
need to run `cabal install cabal-install --constraint="Cabal >
1.20.0.2"`.

From mail at joachim-breitner.de  Thu Dec  4 16:50:00 2014
From: mail at joachim-breitner.de (Joachim Breitner)
Date: Thu, 04 Dec 2014 17:50:00 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CA+tcxkBYtPwbofGjb6geb1yDy=ooEmboiyCx-d283xrwHEReSA@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <1417682707.1485.1.camel@joachim-breitner.de>
 <CA+tcxkBYtPwbofGjb6geb1yDy=ooEmboiyCx-d283xrwHEReSA@mail.gmail.com>
Message-ID: <1417711800.11267.0.camel@joachim-breitner.de>

Hi,


Am Donnerstag, den 04.12.2014, 17:44 +0100 schrieb Mikhail Glushenkov:
> On 4 December 2014 at 09:45, Joachim Breitner <mail at joachim-breitner.de> wrote:
> > is the bug in Cabal or cabal-install?
> 
> It's in Cabal. So once the new point releases are out, the users will
> need to run `cabal install cabal-install --constraint="Cabal >
> 1.20.0.2"`.

in this case, can we get a fixed Cabal in 7.8.4?

Greetings,
Joachim

-- 
Joachim ?nomeata? Breitner
  mail at joachim-breitner.de ? http://www.joachim-breitner.de/
  Jabber: nomeata at joachim-breitner.de  ? GPG-Key: 0xF0FBF51F
  Debian Developer: nomeata at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141204/5442bd46/attachment.sig>

From the.dead.shall.rise at gmail.com  Fri Dec  5 20:10:49 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Fri, 5 Dec 2014 21:10:49 +0100
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <1417711800.11267.0.camel@joachim-breitner.de>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <1417682707.1485.1.camel@joachim-breitner.de>
 <CA+tcxkBYtPwbofGjb6geb1yDy=ooEmboiyCx-d283xrwHEReSA@mail.gmail.com>
 <1417711800.11267.0.camel@joachim-breitner.de>
Message-ID: <CA+tcxkAiCTFk+U6LEHdfg7+xMv3PPxZBP8nWhBU253j+G9sQyA@mail.gmail.com>

Hi,

On 4 December 2014 at 17:50, Joachim Breitner <mail at joachim-breitner.de> wrote:
>
> in this case, can we get a fixed Cabal in 7.8.4?

This is up to whoever manages the release at GHC HQ, which I guess means Austin.

From gale at sefer.org  Sun Dec  7 19:03:01 2014
From: gale at sefer.org (Yitzchak Gale)
Date: Sun, 7 Dec 2014 21:03:01 +0200
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CAOrUaLa0bv9x-kr6QmyDTDKLWwr3tEN-4mcxWVd8eCn=zAvcWg@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <CAOrUaLa0bv9x-kr6QmyDTDKLWwr3tEN-4mcxWVd8eCn=zAvcWg@mail.gmail.com>
Message-ID: <CAOrUaLZEPYfLr8UM1GpE5BEunOCu3aBnVZ_ZoP8GWN=j4iGwGw@mail.gmail.com>

I wrote:
> Aha! Thanks [to Bryan] for this explanation of what I have been
> suffering from...
> I can't wait for the point releases. I'll go with HEAD on one
> of the branches for now.

Unfortunately, this patch did *not* fix what I have been suffering from.
I'm still getting segfaults.

I'll describe what I'm doing. Please let me know if either of the two
problems below are actual problems, or if I'm just missing something.
I'll submit them as issues if they are problems.

Sample code: http://github.com/ygale/test-text-icu

The following procedure worked fine for 32 bit Windows versions of
GHC previous to 7.8.* and with all recent versions of cabal-install.

Using Haskell Platform 2014.2.0.0 (GHC 7.8.3) 64 bit on Windows 7.
Using rev. caf257cd96e766b293943bbac07d766ec2f552dd of cabal,
the latest rev. at the moment, on the 1.20 branch. I locally changed
the version numbers in the cabal files of both Cabal and cabal-install
so I could verify that I really am using cabal.exe from that revision.
I verified in the source code that the -fPIC fix is included.

Clone the above sample code, and unzip ICU4C 54.1 (currently the latest)
for 64 bit Windows in a nearby folder.

***Problem #1 (minor): Relative linker paths don't work anymore

cabal sandbox init
cabal install --extra-lib-dirs=..\relative\path\to\icu\lib64
--extra-include-dirs=..\relative\path\to\icu\include text-icu

This fails with:

Warning: 'extra-lib-dirs: ../relative/path/to/icu/lib64' directory
does not exist.
Warning: 'include-dirs: ../relative/path/to/icu/include' directory
does not exist.
cabal: Missing dependencies on foreign libraries:
* Missing C libraries: icuuc, icuin, icudt

Note: The same problem occurs if you copy the ICU folders into the
source tree. That just gets rid of the warnings that sdist won't work.

***Problem #2 (major): segfault!

cabal install --extra-lib-dirs=C:\absolute\path\to\icu\lib64
--extra-include-dirs=C:\absolute\path\to\icu\include text-icu
cabal install

Now, place .cabal-sandbox\bin\test-text-icu.exe together with the 3 DLLs
icudt54.dll, icuin54.dll, and icuuc54.dll from icu\bin64 all together in the
same folder.
Run test-text-icu.

Kaboom!

Note: The same problem occurs if you place *all* of the DLLs from
icu\bin64 in the folder together with the exe. So it's not a missing DLL.

Thanks,
Yitz

From gale at sefer.org  Wed Dec 10 14:17:02 2014
From: gale at sefer.org (Yitzchak Gale)
Date: Wed, 10 Dec 2014 16:17:02 +0200
Subject: Linker change in GHC 7.8 leads to widespread issues
In-Reply-To: <CAOrUaLZEPYfLr8UM1GpE5BEunOCu3aBnVZ_ZoP8GWN=j4iGwGw@mail.gmail.com>
References: <CACw0niJkw0j=kyX9t-qLMf8sfqpbhPLn9wjk9we0fwmdZ9ArVg@mail.gmail.com>
 <CA+tcxkAT-kWNbKMaBroSF7u+KDRbtuG=SDDV0NNBmiLgLfVy4Q@mail.gmail.com>
 <CACw0niKWf1GgwB_FvWx67nU3My7WHD_dd60Y7Kn8eESQS6_Wtw@mail.gmail.com>
 <CA+tcxkALbcDAeon6yxc0hpRFQmP0OFCit9RBDTiCssOroFRCFQ@mail.gmail.com>
 <CAOrUaLa0bv9x-kr6QmyDTDKLWwr3tEN-4mcxWVd8eCn=zAvcWg@mail.gmail.com>
 <CAOrUaLZEPYfLr8UM1GpE5BEunOCu3aBnVZ_ZoP8GWN=j4iGwGw@mail.gmail.com>
Message-ID: <CAOrUaLandiUqFFJE1YwXO0cTjcgKu3JUbzVsLH=rZywgG_uqsw@mail.gmail.com>

Here's an update to our efforts to get a working build of text-icu
on Windows 64 bits:

I am working together with Kyra on this on the caf? list.
It is becoming clear that GHC is unable to use standard
DLLs on Windows 64 bits. That means FFI is really broken
on that platform at the moment.

By "unable to use standard DLLs" I mean specifically this:
When GHC creates an executable with FFI by linking
against object files, the GHC runtime is unable to use
the DLLs corresponding to the object files if those
DLLs were created by standard Microsoft build tools
and not MingW.

It's not clear yet whether this incompatibility is due to a
change in GHC, or a new incompatibility between MingW's
binutils and Microsoft's native DLL tools.

Currently I am trying create new ICU DLLs from the object
files using binutils so that we can use text-icu. If successful,
that will solve our particular problem in the short term. But
it won't solve the problem of FFI on Windows 64 bits in
general.

Here is the bug report I submitted for text-icu, with a simple
way to reproduce the problem:

https://github.com/bos/text-icu/issues/12

Shall I report that as a GHC bug as well?

Thanks,
Yitz

From johan.tibell at gmail.com  Fri Dec 12 01:22:55 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Fri, 12 Dec 2014 02:22:55 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
Message-ID: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>

I've uploaded release candidates for Cabal/cabal-install patch releases on
the 1.18 and 1.20 branches:

https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz

https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz

Please test, especially if one of your fixes are in this release. You can
install both both lib and exe using: cabal install <Cabal URL>
<cabal-install URL>

Changelogs:

Cabal-1.18.1.5:
e4660ff17f923e999080e21a20062d0df8d24bb6 The download dir on haskell.org
moved
fb3db6313b43632fdc9d598140b3eb5a681eb90b Bump Cabal version number to
1.18.1.5
12a698b6db8a2ca55367c54611a269048f4cef7b Build C sources with -fPIC when
GHC is using dynamic libraries.

cabal-install-1.18.0.6:
79ccaa85bba7957344fb1dca06d84220eff9b73c Bump cabal-install version number
to 1.18.0.6
97dc39636bd547782647cb792ceca6c60a7e5ab1 Merge branch '1.18' of
https://github.com/snoyberg/cabal into 1.18
4fbb20f52c842a7c7c173555ff7f0c8b5b67dfa1 Support for network-2.6
6f74da062e6d1bdc6db51acd55d0e2676fa56bf2 SavedConfig Monoid instance: make
list fields work like Flags.
7380144203a233f81ff67052fc3256cf47b9b71f cabal update: use sandbox config
file #1884

Cabal-1.20.0.3
7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
to 1.20.0.4
813ce2fc23da81b7bf07418a28258a962c44713e Bump Cabal version number to
1.20.0.3
cee305209129480f28190ee7026076962ba9ca97 The download dir on haskell.org
moved
b172747adec9ec8d57d8215e9d1cabb448aa6036 Build C sources with -fPIC when
GHC is using dynamic libraries.
93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
97c6a72984931f4ccf628736024d3459a033af6c.
343257e96fab526da27d143b653433f45c6c1401 s/2.15/2.14.4/

cabal-install-1.20.0.4
7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
to 1.20.0.4
caf257cd96e766b293943bbac07d766ec2f552dd Self-constraint not included in
frozen constraints
b19175519de6fc40683527c1104ce2a513a03612 Merge branch '1.20' of
https://github.com/snoyberg/cabal into 1.20
1c0d8aafbe42921baa56fc36383f34763f69d327 Revert "Remove redundant network
constraint"
58517f76cb2ccb33c007da596ede265f1192d3b8 Remove redundant network constraint
a747778c25bd339fed9c9a7c77eb3adbf0f162e0 Support for network-2.6
5fcf3d994e5c5a0f101ac04e092a8beedadcdc8d SavedConfig Monoid instance: make
list fields work like Flags.
13f9051d34463037569becf6d3f736a8d8a4570e cabal update: use sandbox config
file #1884
93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
97c6a72984931f4ccf628736024d3459a033af6c.
aa0a6979f3223387aae830cf1d21b2c21978d767 Read installed package info file
as UTF-8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141212/e9501134/attachment.html>

From johan.tibell at gmail.com  Fri Dec 12 01:55:46 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Fri, 12 Dec 2014 02:55:46 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
Message-ID: <CAK-tuPZBMEGHucrCP1nFr03ja_aTkMskSoD=0BY=d_=Fs2Gh5A@mail.gmail.com>

Apparently this no longer works:

cabal install
http://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
http://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz

Some change on the web server side means that the web server tries to
redirect to an https page, even though cabal-install doesn't support it.

On Fri, Dec 12, 2014 at 2:22 AM, Johan Tibell <johan.tibell at gmail.com>
wrote:

> I've uploaded release candidates for Cabal/cabal-install patch releases on
> the 1.18 and 1.20 branches:
>
> https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
>
> https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz
>
> https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
>
> https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz
>
> Please test, especially if one of your fixes are in this release. You can
> install both both lib and exe using: cabal install <Cabal URL>
> <cabal-install URL>
>
> Changelogs:
>
> Cabal-1.18.1.5:
> e4660ff17f923e999080e21a20062d0df8d24bb6 The download dir on haskell.org
> moved
> fb3db6313b43632fdc9d598140b3eb5a681eb90b Bump Cabal version number to
> 1.18.1.5
> 12a698b6db8a2ca55367c54611a269048f4cef7b Build C sources with -fPIC when
> GHC is using dynamic libraries.
>
> cabal-install-1.18.0.6:
> 79ccaa85bba7957344fb1dca06d84220eff9b73c Bump cabal-install version number
> to 1.18.0.6
> 97dc39636bd547782647cb792ceca6c60a7e5ab1 Merge branch '1.18' of
> https://github.com/snoyberg/cabal into 1.18
> 4fbb20f52c842a7c7c173555ff7f0c8b5b67dfa1 Support for network-2.6
> 6f74da062e6d1bdc6db51acd55d0e2676fa56bf2 SavedConfig Monoid instance: make
> list fields work like Flags.
> 7380144203a233f81ff67052fc3256cf47b9b71f cabal update: use sandbox config
> file #1884
>
> Cabal-1.20.0.3
> 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
> to 1.20.0.4
> 813ce2fc23da81b7bf07418a28258a962c44713e Bump Cabal version number to
> 1.20.0.3
> cee305209129480f28190ee7026076962ba9ca97 The download dir on haskell.org
> moved
> b172747adec9ec8d57d8215e9d1cabb448aa6036 Build C sources with -fPIC when
> GHC is using dynamic libraries.
> 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
> 97c6a72984931f4ccf628736024d3459a033af6c.
> 343257e96fab526da27d143b653433f45c6c1401 s/2.15/2.14.4/
>
> cabal-install-1.20.0.4
> 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
> to 1.20.0.4
> caf257cd96e766b293943bbac07d766ec2f552dd Self-constraint not included in
> frozen constraints
> b19175519de6fc40683527c1104ce2a513a03612 Merge branch '1.20' of
> https://github.com/snoyberg/cabal into 1.20
> 1c0d8aafbe42921baa56fc36383f34763f69d327 Revert "Remove redundant network
> constraint"
> 58517f76cb2ccb33c007da596ede265f1192d3b8 Remove redundant network
> constraint
> a747778c25bd339fed9c9a7c77eb3adbf0f162e0 Support for network-2.6
> 5fcf3d994e5c5a0f101ac04e092a8beedadcdc8d SavedConfig Monoid instance: make
> list fields work like Flags.
> 13f9051d34463037569becf6d3f736a8d8a4570e cabal update: use sandbox config
> file #1884
> 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
> 97c6a72984931f4ccf628736024d3459a033af6c.
> aa0a6979f3223387aae830cf1d21b2c21978d767 Read installed package info file
> as UTF-8
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141212/1992e37f/attachment.html>

From bgamari.foss at gmail.com  Fri Dec 12 03:52:15 2014
From: bgamari.foss at gmail.com (Ben Gamari)
Date: Thu, 11 Dec 2014 22:52:15 -0500
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
Message-ID: <87wq5xo780.fsf@gmail.com>

Johan Tibell <johan.tibell at gmail.com> writes:

> I've uploaded release candidates for Cabal/cabal-install patch releases on
> the 1.18 and 1.20 branches:
>
> https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
> https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz
>
> https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
> https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz
>
> Please test, especially if one of your fixes are in this release. You can
> install both both lib and exe using: cabal install <Cabal URL>
> <cabal-install URL>
>
First I'll look at Cabal-1.18.1.5 and cabal-install-1.18.0.6.

Unfortunately there still seems to be trouble invoking cabal in a tree
previously used by a previous Cabal version. For instance,

    $ tar -zxf cabal-install-1.18.0.6.tar.gz 
    $ cd cabal-install-1.18.0.6
    $ cabal install
    $ cabal install --enable-tests
    Warning: The package list for 'hackage.haskell.org' is 71 days old.
    Run 'cabal update' to get the latest list of available packages.
    Resolving dependencies...
    Configuring cabal-install-1.18.0.6...
    Building cabal-install-1.18.0.6...
    cabal: dist/package.conf.inplace: inappropriate type
    Failed to install cabal-install-1.18.0.6
    cabal: Error: some packages failed to install:
    cabal-install-1.18.0.6 failed during the building phase. The exception was:
    ExitFailure 1

I have noticed this problem in the past as well. Deleting dist/ resolves
the issue. I seem to recall some discussion where it was claimed this
was fixed although I could be wrong.  This was reproducible on x86_64
(building with GHC 7.8.3 and 7.6.3) and ARM.

After this was resolved I encountered the following,

    $ cabal install --enable-tests
    ...

    Preprocessing test suite 'unit-tests' for cabal-install-1.18.0.6...

    Distribution/Client/Targets.hs:100:8:
        Could not find module `Network.URI'
        It is a member of the hidden package `network-2.4.2.2'.
        Perhaps you need to add `network' to the build-depends in your .cabal file.
        It is a member of the hidden package `network-uri-2.6.0.1'.
        Perhaps you need to add `network-uri' to the build-depends in your .cabal file.
        Use -v to see a list of the files searched for.
    Failed to install cabal-install-1.18.0.6
    cabal: Error: some packages failed to install:

This is fixed in master. It seems you should probably cherry-pick
2826c97d11a495085008c4bddf499fcfd05e0df2 onto the release branch.

After this I was able to run the testsuite. cabal-install was fine;
Cabal failed with,

    TestSuiteExeV10/TestWithHpc:
      : [Failed]
    expected: 'setup build' should succeed
      output: "/opt/exp/haskell-packages/Cabal-1.18.1.5/tests/Setup configure --user -w /opt/exp/ghc/root-ghc-7.8/bin/ghc --enable-tests --enable-library-coverage" in PackageTests/TestSuiteExeV10
    Setup: Option --enable-library-coverage is obsolete! Please use
    --enable-coverage instead.

    ...

    BuildTestSuiteDetailedV09:
      : [Failed]
    build failed!
    expected: False
     but got: True

I didn't investigate into the cause of these any further.

I also used the new cabal executable to install Yesod has progressed
quite (on the ARM, even) far and shows no sign failure.

I'll take a look at the 1.20 releases tomorrow.

Cheers,

 - Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141211/38424c2a/attachment.sig>

From johan.tibell at gmail.com  Fri Dec 12 12:10:36 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Fri, 12 Dec 2014 13:10:36 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <87wq5xo780.fsf@gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
 <87wq5xo780.fsf@gmail.com>
Message-ID: <CAK-tuPZSbk2dgZLufTNydCBTdOcSbfMuVFm5yZGSHbvY4Vcfzw@mail.gmail.com>

Ben,

Is this something that worked in cabal-install 1.18.0.5 and that stopped
working in 1.18.0.6 or is it something that didn't work in 1.18.0.5 but you
expected to be fixed in 1.18.0.6? These 1.18 and 1.20 releases just target
a very few critical bugs. They are not attempts to backport all bugfixes
from master.

In 1.18 the critical fixes are:
12a698b6db8a2ca55367c54611a269048f4cef7b Build C sources with -fPIC when
GHC is using dynamic libraries.
4fbb20f52c842a7c7c173555ff7f0c8b5b67dfa1 Support for network-2.6
6f74da062e6d1bdc6db51acd55d0e2676fa56bf2 SavedConfig Monoid instance: make
list fields work like Flags.
7380144203a233f81ff67052fc3256cf47b9b71f cabal update: use sandbox config
file #1884

As for installing, after downloading the two tarballs to a temp dir this
works for me:

cabal install Cabal-1.18.1.5.tar.gz cabal-install-1.18.0.6.tar.gz

-- Johan

On Fri, Dec 12, 2014 at 4:52 AM, Ben Gamari <bgamari.foss at gmail.com> wrote:
>
> Johan Tibell <johan.tibell at gmail.com> writes:
>
> > I've uploaded release candidates for Cabal/cabal-install patch releases
> on
> > the 1.18 and 1.20 branches:
> >
> >
> https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
> >
> https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz
> >
> >
> https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
> >
> https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz
> >
> > Please test, especially if one of your fixes are in this release. You can
> > install both both lib and exe using: cabal install <Cabal URL>
> > <cabal-install URL>
> >
> First I'll look at Cabal-1.18.1.5 and cabal-install-1.18.0.6.
>
> Unfortunately there still seems to be trouble invoking cabal in a tree
> previously used by a previous Cabal version. For instance,
>
>     $ tar -zxf cabal-install-1.18.0.6.tar.gz
>     $ cd cabal-install-1.18.0.6
>     $ cabal install
>     $ cabal install --enable-tests
>     Warning: The package list for 'hackage.haskell.org' is 71 days old.
>     Run 'cabal update' to get the latest list of available packages.
>     Resolving dependencies...
>     Configuring cabal-install-1.18.0.6...
>     Building cabal-install-1.18.0.6...
>     cabal: dist/package.conf.inplace: inappropriate type
>     Failed to install cabal-install-1.18.0.6
>     cabal: Error: some packages failed to install:
>     cabal-install-1.18.0.6 failed during the building phase. The exception
> was:
>     ExitFailure 1
>
> I have noticed this problem in the past as well. Deleting dist/ resolves
> the issue. I seem to recall some discussion where it was claimed this
> was fixed although I could be wrong.  This was reproducible on x86_64
> (building with GHC 7.8.3 and 7.6.3) and ARM.
>
> After this was resolved I encountered the following,
>
>     $ cabal install --enable-tests
>     ...
>
>     Preprocessing test suite 'unit-tests' for cabal-install-1.18.0.6...
>
>     Distribution/Client/Targets.hs:100:8:
>         Could not find module `Network.URI'
>         It is a member of the hidden package `network-2.4.2.2'.
>         Perhaps you need to add `network' to the build-depends in your
> .cabal file.
>         It is a member of the hidden package `network-uri-2.6.0.1'.
>         Perhaps you need to add `network-uri' to the build-depends in your
> .cabal file.
>         Use -v to see a list of the files searched for.
>     Failed to install cabal-install-1.18.0.6
>     cabal: Error: some packages failed to install:
>
> This is fixed in master. It seems you should probably cherry-pick
> 2826c97d11a495085008c4bddf499fcfd05e0df2 onto the release branch.
>
> After this I was able to run the testsuite. cabal-install was fine;
> Cabal failed with,
>
>     TestSuiteExeV10/TestWithHpc:
>       : [Failed]
>     expected: 'setup build' should succeed
>       output: "/opt/exp/haskell-packages/Cabal-1.18.1.5/tests/Setup
> configure --user -w /opt/exp/ghc/root-ghc-7.8/bin/ghc --enable-tests
> --enable-library-coverage" in PackageTests/TestSuiteExeV10
>     Setup: Option --enable-library-coverage is obsolete! Please use
>     --enable-coverage instead.
>
>     ...
>
>     BuildTestSuiteDetailedV09:
>       : [Failed]
>     build failed!
>     expected: False
>      but got: True
>
> I didn't investigate into the cause of these any further.
>
> I also used the new cabal executable to install Yesod has progressed
> quite (on the ARM, even) far and shows no sign failure.
>
> I'll take a look at the 1.20 releases tomorrow.
>
> Cheers,
>
>  - Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141212/a4d558db/attachment.html>

From ben at smart-cactus.org  Fri Dec 12 13:52:22 2014
From: ben at smart-cactus.org (Ben Gamari)
Date: Fri, 12 Dec 2014 08:52:22 -0500
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPZSbk2dgZLufTNydCBTdOcSbfMuVFm5yZGSHbvY4Vcfzw@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
 <87wq5xo780.fsf@gmail.com>
 <CAK-tuPZSbk2dgZLufTNydCBTdOcSbfMuVFm5yZGSHbvY4Vcfzw@mail.gmail.com>
Message-ID: <878uidm0vd.fsf@gmail.com>

Johan Tibell <johan.tibell at gmail.com> writes:

> Ben,
>
> Is this something that worked in cabal-install 1.18.0.5 and that stopped
> working in 1.18.0.6 or is it something that didn't work in 1.18.0.5 but you
> expected to be fixed in 1.18.0.6? These 1.18 and 1.20 releases just target
> a very few critical bugs. They are not attempts to backport all bugfixes
> from master.
>
Fair enough; ignore the first issue in that case. Nevertheless, given
that the network-2.6 fix made it in I think it would be worth
cherry-picking the network-uri fix as well so that the release can be
properly tested.

Things look pretty good to me otherwise. I'll test 1.20 next.

Cheers,

- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141212/f66c5164/attachment.sig>

From the.dead.shall.rise at gmail.com  Fri Dec 12 19:08:31 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Fri, 12 Dec 2014 20:08:31 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
Message-ID: <CA+tcxkBAktxGd5eBph2COwHN6Mq4OCgcMEoFN0FqvMfRfvMeyg@mail.gmail.com>

Hi Johan,

I pushed a very minor fix to 1.18/1.20. Would be nice to have it
included in the release.

From hvr at gnu.org  Sat Dec 13 08:57:11 2014
From: hvr at gnu.org (Herbert Valerio Riedel)
Date: Sat, 13 Dec 2014 09:57:11 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <CAK-tuPb26Nmy6KFVEy20SVLkkT2rg_VowCHOwfTcCqtnM_++0A@mail.gmail.com>
 (Johan Tibell's message of "Tue, 2 Dec 2014 11:16:46 +0100")
References: <87iohvfcgl.fsf@gnu.org> <m5icm2$m37$1@ger.gmane.org>
 <CALqQuoj9CfOfi6syc5YtrmkOV6m3W9zdEoS0DbaSqjUWtGNY4w@mail.gmail.com>
 <CAK-tuPb26Nmy6KFVEy20SVLkkT2rg_VowCHOwfTcCqtnM_++0A@mail.gmail.com>
Message-ID: <87h9x0apw8.fsf@gnu.org>

Hello Johan,

...how's progress for a Cabal RC to go w/ GHC 7.10.1 RC1? :-)



On 2014-12-02 at 11:16:46 +0100, Johan Tibell wrote:
> I think I can have a RC out without 2 weeks.
>
> On Tue, Dec 2, 2014 at 8:53 AM, Luite Stegeman <stegeman at gmail.com> wrote:
>
>>
>>
>> On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
>> wrote:
>>
>>>
>>> Mostly out of curiousity: is there *any* conceivable chance of getting
>>> the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
>>> is also on this list.)
>>>
>>
>> Yes, I am on this list. A small part has already been merged, and there's
>> a pull request for the changes in the package description and flags, which
>> include the GHCJS compiler flavour. While discussing the patch with Duncan,
>> we agreed that a few changes were in order, which I've made, I'll amend the
>> pull request later today.
>>
>> What's left then is the backend itself. The changes there are only in the
>> build system, so they don't touch the public API / file formats, but on the
>> other hand they do touch quite a bit of code and require some restructuring
>> of the GHC backend to allow some of the code to be reused without
>> copy/pasting the whole backend (smaller customizations are required for
>> ghc-pkg and haddock).
>>
>> I'm going to spend some time this week to submit the next part of the
>> code, test it with my experimental GHC 7.10 branch of GHCJS. The important
>> public changes have been discussed / prepared already, so it'll mostly come
>> down to how well this code will stand up to scrutinization of the reviewers.
>>
>> luite
>>
>> _______________________________________________
>> cabal-devel mailing list
>> cabal-devel at haskell.org
>> http://www.haskell.org/mailman/listinfo/cabal-devel
>>
>>

-- 
"Elegance is not optional" -- Richard O'Keefe

From johan.tibell at gmail.com  Sat Dec 13 15:12:34 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Sat, 13 Dec 2014 16:12:34 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CA+tcxkBAktxGd5eBph2COwHN6Mq4OCgcMEoFN0FqvMfRfvMeyg@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
 <CA+tcxkBAktxGd5eBph2COwHN6Mq4OCgcMEoFN0FqvMfRfvMeyg@mail.gmail.com>
Message-ID: <CAK-tuPa87c+mTYtzECf8Qy5PCPw8b23u9c1_++9V41ZWYLexJA@mail.gmail.com>

I can include it in the release but I rather not make another RC, it takes
an hour or so. Could you please test on your machine that the extra fix
works as intended? Thanks!

P.S. I plan to make the release as soon as Michael says his fix works.

On Fri, Dec 12, 2014 at 8:08 PM, Mikhail Glushenkov <
the.dead.shall.rise at gmail.com> wrote:
>
> Hi Johan,
>
> I pushed a very minor fix to 1.18/1.20. Would be nice to have it
> included in the release.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141213/f46c2742/attachment.html>

From stegeman at gmail.com  Sat Dec 13 15:54:15 2014
From: stegeman at gmail.com (Luite Stegeman)
Date: Sat, 13 Dec 2014 16:54:15 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <m5icm2$m37$1@ger.gmane.org>
References: <87iohvfcgl.fsf@gnu.org>
	<m5icm2$m37$1@ger.gmane.org>
Message-ID: <CALqQuohWgUDwA5VL09y6c+aHfHp=HGXqMBFxyxSz7j2RTk7agA@mail.gmail.com>

Status update:

All functionality from the ghcjs Cabal branch is now in pull requests
[1] [2]. I have changed a few things in the GHCJS command line options
(more consistent with GHC now), and GHCJS produces library archives
(libHSpackage.js_a) for packages now, which makes GHCJS easier and
more similar to GHC to deal with, and provides a better upgrade path
if we need to store information in the future.

I've updated the GHCJS master branch for this, and also the ghcjs
branch of our fork [3] . Anyone upgrading their GHCJS should first
update their Cabal. Use `ghcjs-boot --dev --clean` to upgrade the boot
libraries.

luite

[1] https://github.com/haskell/cabal/pull/2269
[2] https://github.com/haskell/cabal/pull/2273
[3] https://github.com/ghcjs/cabal


On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net> wrote:
> On 2014-12-01 19:32, Herbert Valerio Riedel wrote:
>> Hello Cabal developers!
>>
>> To keep it short: GHC 7.10.1 RC1 is planned for a release shortly before
>> Xmas, and it would be great if there was a Cabal 1.22.x RC to go along
>> with that.
>>
>> Is it possible for you to get Cabal (the library) in such a state by
>> mid-December (i.e. in 2 weeks from now)?
>>
>
> Mostly out of curiousity: is there *any* conceivable chance of getting
> the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
> is also on this list.)
>
> Regards,
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel

From johan.tibell at gmail.com  Sat Dec 13 20:11:22 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Sat, 13 Dec 2014 21:11:22 +0100
Subject: Heads-up: planning to create 1.22 RC on Thursday
Message-ID: <CAK-tuPbYh8+eATy8dwL1AAse0VdmHptMTQnSXkSh9n1yBckhjg@mail.gmail.com>

I plan to create the 1.22 RC on Thursday so it can go in the GHC 7.10 RC.
That means that most pull requests (especially non-trivial ones) should be
merged by then.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141213/34d2ba56/attachment.html>

From mietek at bak.io  Sat Dec 13 20:28:12 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Sat, 13 Dec 2014 20:28:12 +0000
Subject: Heads-up: planning to create 1.22 RC on Thursday
In-Reply-To: <CAK-tuPbYh8+eATy8dwL1AAse0VdmHptMTQnSXkSh9n1yBckhjg@mail.gmail.com>
References: <CAK-tuPbYh8+eATy8dwL1AAse0VdmHptMTQnSXkSh9n1yBckhjg@mail.gmail.com>
Message-ID: <81FE7EFB-A7EA-4EA1-A25C-BF907BED6973@bak.io>

My simple PR has been stuck in review since 1 July.  Does anyone have a moment to spare?

https://github.com/haskell/cabal/pull/1977

-- 
Mi?tek




On 2014-12-13, at 20:11, Johan Tibell <johan.tibell at gmail.com> wrote:

> I plan to create the 1.22 RC on Thursday so it can go in the GHC 7.10 RC. That means that most pull requests (especially non-trivial ones) should be merged by then.
> 
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141213/15bcba39/attachment.bin>

From ben at smart-cactus.org  Sat Dec 13 20:34:24 2014
From: ben at smart-cactus.org (Ben Gamari)
Date: Sat, 13 Dec 2014 15:34:24 -0500
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <878uidm0vd.fsf@gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
 <87wq5xo780.fsf@gmail.com>
 <CAK-tuPZSbk2dgZLufTNydCBTdOcSbfMuVFm5yZGSHbvY4Vcfzw@mail.gmail.com>
 <878uidm0vd.fsf@gmail.com>
Message-ID: <878uibl25r.fsf@gmail.com>

Ben Gamari <ben at smart-cactus.org> writes:

> Johan Tibell <johan.tibell at gmail.com> writes:
>
>> Ben,
>>
>> Is this something that worked in cabal-install 1.18.0.5 and that stopped
>> working in 1.18.0.6 or is it something that didn't work in 1.18.0.5 but you
>> expected to be fixed in 1.18.0.6? These 1.18 and 1.20 releases just target
>> a very few critical bugs. They are not attempts to backport all bugfixes
>> from master.
>>
> Fair enough; ignore the first issue in that case. Nevertheless, given
> that the network-2.6 fix made it in I think it would be worth
> cherry-picking the network-uri fix as well so that the release can be
> properly tested.
>
> Things look pretty good to me otherwise. I'll test 1.20 next.
>
1.20 looks good to me.

Cheers,

- Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141213/585810b6/attachment.sig>

From ttuegel at gmail.com  Sat Dec 13 21:46:11 2014
From: ttuegel at gmail.com (Thomas Tuegel)
Date: Sat, 13 Dec 2014 15:46:11 -0600
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
Message-ID: <CAHgDWkbnM3ffVGK5Eq5mKdgkc31dk_D7ZJS7trEJpU9QnA4cGQ@mail.gmail.com>

Hi all,

Carter Schonwald and I just tracked down a bug with the way Haskell
Program Coverage is handled in the presence of profiling. The short
version is, your tests will break if you use
"--enable-library-coverage" with "--enable-library-profiling
--disable-executable-profiling". I will fix the bug properly for Cabal
1.22, but I would like to provide a warning for 1.18 and 1.20, so I
will push that soon. (I don't want to backport the patch from 1.22
because there have been added features to our HPC support since then.)

Sorry!

On Thu, Dec 11, 2014 at 7:22 PM, Johan Tibell <johan.tibell at gmail.com> wrote:
> I've uploaded release candidates for Cabal/cabal-install patch releases on
> the 1.18 and 1.20 branches:
>
> https://www.haskell.org/cabal/release/cabal-1.18.1.5/Cabal-1.18.1.5.tar.gz
> https://www.haskell.org/cabal/release/cabal-install-1.18.0.6/cabal-install-1.18.0.6.tar.gz
>
> https://www.haskell.org/cabal/release/cabal-1.20.0.3/Cabal-1.20.0.3.tar.gz
> https://www.haskell.org/cabal/release/cabal-install-1.20.0.4/cabal-install-1.20.0.4.tar.gz
>
> Please test, especially if one of your fixes are in this release. You can
> install both both lib and exe using: cabal install <Cabal URL>
> <cabal-install URL>
>
> Changelogs:
>
> Cabal-1.18.1.5:
> e4660ff17f923e999080e21a20062d0df8d24bb6 The download dir on haskell.org
> moved
> fb3db6313b43632fdc9d598140b3eb5a681eb90b Bump Cabal version number to
> 1.18.1.5
> 12a698b6db8a2ca55367c54611a269048f4cef7b Build C sources with -fPIC when GHC
> is using dynamic libraries.
>
> cabal-install-1.18.0.6:
> 79ccaa85bba7957344fb1dca06d84220eff9b73c Bump cabal-install version number
> to 1.18.0.6
> 97dc39636bd547782647cb792ceca6c60a7e5ab1 Merge branch '1.18' of
> https://github.com/snoyberg/cabal into 1.18
> 4fbb20f52c842a7c7c173555ff7f0c8b5b67dfa1 Support for network-2.6
> 6f74da062e6d1bdc6db51acd55d0e2676fa56bf2 SavedConfig Monoid instance: make
> list fields work like Flags.
> 7380144203a233f81ff67052fc3256cf47b9b71f cabal update: use sandbox config
> file #1884
>
> Cabal-1.20.0.3
> 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
> to 1.20.0.4
> 813ce2fc23da81b7bf07418a28258a962c44713e Bump Cabal version number to
> 1.20.0.3
> cee305209129480f28190ee7026076962ba9ca97 The download dir on haskell.org
> moved
> b172747adec9ec8d57d8215e9d1cabb448aa6036 Build C sources with -fPIC when GHC
> is using dynamic libraries.
> 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
> 97c6a72984931f4ccf628736024d3459a033af6c.
> 343257e96fab526da27d143b653433f45c6c1401 s/2.15/2.14.4/
>
> cabal-install-1.20.0.4
> 7d7f560cc84dfe643d916efbab7c382b1df5a9e2 Bump cabal-install version number
> to 1.20.0.4
> caf257cd96e766b293943bbac07d766ec2f552dd Self-constraint not included in
> frozen constraints
> b19175519de6fc40683527c1104ce2a513a03612 Merge branch '1.20' of
> https://github.com/snoyberg/cabal into 1.20
> 1c0d8aafbe42921baa56fc36383f34763f69d327 Revert "Remove redundant network
> constraint"
> 58517f76cb2ccb33c007da596ede265f1192d3b8 Remove redundant network constraint
> a747778c25bd339fed9c9a7c77eb3adbf0f162e0 Support for network-2.6
> 5fcf3d994e5c5a0f101ac04e092a8beedadcdc8d SavedConfig Monoid instance: make
> list fields work like Flags.
> 13f9051d34463037569becf6d3f736a8d8a4570e cabal update: use sandbox config
> file #1884
> 93aba465d35d03b29b1d9bd3a456815272a38a41 Revert
> 97c6a72984931f4ccf628736024d3459a033af6c.
> aa0a6979f3223387aae830cf1d21b2c21978d767 Read installed package info file as
> UTF-8
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>



-- 
Thomas Tuegel

From the.dead.shall.rise at gmail.com  Sun Dec 14 03:37:49 2014
From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov)
Date: Sun, 14 Dec 2014 04:37:49 +0100
Subject: Please test: release candidates for Cabal/cabal-install patch
 releases on the 1.18 and 1.20 branches
In-Reply-To: <CAK-tuPa87c+mTYtzECf8Qy5PCPw8b23u9c1_++9V41ZWYLexJA@mail.gmail.com>
References: <CAK-tuPaOWf=KK-P-rRa46EMkwHg25BGra0yAbcuSEZR2bV0TNw@mail.gmail.com>
 <CA+tcxkBAktxGd5eBph2COwHN6Mq4OCgcMEoFN0FqvMfRfvMeyg@mail.gmail.com>
 <CAK-tuPa87c+mTYtzECf8Qy5PCPw8b23u9c1_++9V41ZWYLexJA@mail.gmail.com>
Message-ID: <CA+tcxkCE6EFBUAOyyFUbsa+QYymeTc-VbtBn0SM4MBT36T3oOA@mail.gmail.com>

Hi,

On 13 December 2014 at 16:12, Johan Tibell <johan.tibell at gmail.com> wrote:
> I can include it in the release but I rather not make another RC, it takes
> an hour or so. Could you please test on your machine that the extra fix
> works as intended? Thanks!

I did verify it on my machine previously. It does pass on Travis, so
should be OK.

From johan.tibell at gmail.com  Mon Dec 15 23:16:45 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 16 Dec 2014 00:16:45 +0100
Subject: 1.18 and 1.20 patch releases done
Message-ID: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>

I just pushed Cabal and cabal-install releases on both the 1.18 and 1.20
branches live.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141216/4bf082ca/attachment.html>

From mietek at bak.io  Tue Dec 16 03:37:35 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Tue, 16 Dec 2014 03:37:35 +0000
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
Message-ID: <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>

Bootstrapping 1.20.0.4 fails for me:

       Configuring cabal-install-1.20.0.4...
       Setup: At least the following dependencies are missing:
       network-uri <2.6
       
       Error during cabal-install bootstrap:
       Configuring the cabal-install package failed.

-- 
Mi?tek




On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:

> I just pushed Cabal and cabal-install releases on both the 1.18 and 1.20 branches live.
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141216/874895c5/attachment.bin>

From mietek at bak.io  Tue Dec 16 03:47:16 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Tue, 16 Dec 2014 03:47:16 +0000
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
 <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
Message-ID: <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>

I should add ? this is on a bare Ubuntu 14.04 LTS system, with only GHC 7.8.3 installed, and nothing else. 

-- 
Mi?tek




On 2014-12-16, at 03:37, Mi?tek Bak <mietek at bak.io> wrote:

> Bootstrapping 1.20.0.4 fails for me:
> 
>       Configuring cabal-install-1.20.0.4...
>       Setup: At least the following dependencies are missing:
>       network-uri <2.6
> 
>       Error during cabal-install bootstrap:
>       Configuring the cabal-install package failed.
> 
> -- 
> Mi?tek
> 
> 
> 
> 
> On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:
> 
>> I just pushed Cabal and cabal-install releases on both the 1.18 and 1.20 branches live.
>> _______________________________________________
>> cabal-devel mailing list
>> cabal-devel at haskell.org
>> http://www.haskell.org/mailman/listinfo/cabal-devel
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141216/de4a717a/attachment.bin>

From johan.tibell at gmail.com  Tue Dec 16 07:43:44 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 16 Dec 2014 08:43:44 +0100
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
 <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
 <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>
Message-ID: <CAK-tuPaX-UM3aKn6ik+TQ_rKWpfeLc_jP7zOrwfuPNY1ioVRqA@mail.gmail.com>

Ah, the bootstrap script needs to be updated after the Network.URI split. :/

On Tue, Dec 16, 2014 at 4:47 AM, Mi?tek Bak <mietek at bak.io> wrote:
>
> I should add ? this is on a bare Ubuntu 14.04 LTS system, with only GHC
> 7.8.3 installed, and nothing else.
>
> --
> Mi?tek
>
>
>
>
> On 2014-12-16, at 03:37, Mi?tek Bak <mietek at bak.io> wrote:
>
> > Bootstrapping 1.20.0.4 fails for me:
> >
> >       Configuring cabal-install-1.20.0.4...
> >       Setup: At least the following dependencies are missing:
> >       network-uri <2.6
> >
> >       Error during cabal-install bootstrap:
> >       Configuring the cabal-install package failed.
> >
> > --
> > Mi?tek
> >
> >
> >
> >
> > On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:
> >
> >> I just pushed Cabal and cabal-install releases on both the 1.18 and
> 1.20 branches live.
> >> _______________________________________________
> >> cabal-devel mailing list
> >> cabal-devel at haskell.org
> >> http://www.haskell.org/mailman/listinfo/cabal-devel
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141216/1f077603/attachment.html>

From toby at paccrat.org  Wed Dec 17 09:52:07 2014
From: toby at paccrat.org (Toby Goodwin)
Date: 17 Dec 2014 09:52:07 -0000
Subject: Upper bound on "time" in Cabal causes build failure
Message-ID: <1418809927.458.hydrogen.mv6.co.uk@hydrogen.mpv6.com>

Hi cabal developers,

Wasn't sure what best to do with this - please let me know if you'd rather I emailed it elsewhere, or opened an issue against the github project, or...

I'm trying to build haskell-platform-2014.2 from source, with the latest cabal:

  cabal-install version 1.20.0.4
  using version 1.20.0.3 of the Cabal library 

The build plan it constructs for the hptool sandbox includes Cabal-1.2.4! (That's not a typo.) The problem seems to be that it chooses time-1.5, and then discovers that all recent versions of Cabal have the constraint "time < 1.5", so digs up this fossil from the attic.

So I think there are two problems here. The small and simple one is that we need a release of Cabal with "time < 1.6" - you appear to have this in the master branch already; can it go on the 1.20 branch? Do you want me to create an issue / pull request?

The larger problem is that cabal should have found a better build plan. I'm naive about the internals of dependency resolution, but I would have expected it to prefer taking time back 1 release over taking Cabal back 18. It would also be nice if it could have deduced that Cabal-1.2.4 wasn't actually going to build with recent ghc versions.

Thanks for your time,

Toby.

From hesselink at gmail.com  Wed Dec 17 10:14:36 2014
From: hesselink at gmail.com (Erik Hesselink)
Date: Wed, 17 Dec 2014 11:14:36 +0100
Subject: Upper bound on "time" in Cabal causes build failure
In-Reply-To: <1418809927.458.hydrogen.mv6.co.uk@hydrogen.mpv6.com>
References: <1418809927.458.hydrogen.mv6.co.uk@hydrogen.mpv6.com>
Message-ID: <CAPeieQEAKwGmkyovRevyxU7G9KPKYG4Kv=diiDzvEVNuFC6zgg@mail.gmail.com>

It would perhaps be worth it for someone with the right permissions to
edit the (five) old versions on hackage, and add upper bounds. That
way cabal install wouldn't use this very old version assuming it works
(it probably doesn't).

Erik

On Wed, Dec 17, 2014 at 10:52 AM, Toby Goodwin <toby at paccrat.org> wrote:
> Hi cabal developers,
>
> Wasn't sure what best to do with this - please let me know if you'd rather I emailed it elsewhere, or opened an issue against the github project, or...
>
> I'm trying to build haskell-platform-2014.2 from source, with the latest cabal:
>
>   cabal-install version 1.20.0.4
>   using version 1.20.0.3 of the Cabal library
>
> The build plan it constructs for the hptool sandbox includes Cabal-1.2.4! (That's not a typo.) The problem seems to be that it chooses time-1.5, and then discovers that all recent versions of Cabal have the constraint "time < 1.5", so digs up this fossil from the attic.
>
> So I think there are two problems here. The small and simple one is that we need a release of Cabal with "time < 1.6" - you appear to have this in the master branch already; can it go on the 1.20 branch? Do you want me to create an issue / pull request?
>
> The larger problem is that cabal should have found a better build plan. I'm naive about the internals of dependency resolution, but I would have expected it to prefer taking time back 1 release over taking Cabal back 18. It would also be nice if it could have deduced that Cabal-1.2.4 wasn't actually going to build with recent ghc versions.
>
> Thanks for your time,
>
> Toby.
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel

From johan.tibell at gmail.com  Thu Dec 18 14:40:19 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Thu, 18 Dec 2014 15:40:19 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <CALqQuohWgUDwA5VL09y6c+aHfHp=HGXqMBFxyxSz7j2RTk7agA@mail.gmail.com>
References: <87iohvfcgl.fsf@gnu.org> <m5icm2$m37$1@ger.gmane.org>
 <CALqQuohWgUDwA5VL09y6c+aHfHp=HGXqMBFxyxSz7j2RTk7agA@mail.gmail.com>
Message-ID: <CAK-tuPbWMPy6smxhNtfRVRM4xQAoiW=xt2ZtwzB9-CdD2Yzvew@mail.gmail.com>

I went over the outstanding pull requests and merged some and left comments
on others. Unless I hear something from the authors of those pull requests
in the next couple of days, I will put out a 1.22 RC based on current
master.

On Sat, Dec 13, 2014 at 4:54 PM, Luite Stegeman <stegeman at gmail.com> wrote:
>
> Status update:
>
> All functionality from the ghcjs Cabal branch is now in pull requests
> [1] [2]. I have changed a few things in the GHCJS command line options
> (more consistent with GHC now), and GHCJS produces library archives
> (libHSpackage.js_a) for packages now, which makes GHCJS easier and
> more similar to GHC to deal with, and provides a better upgrade path
> if we need to store information in the future.
>
> I've updated the GHCJS master branch for this, and also the ghcjs
> branch of our fork [3] . Anyone upgrading their GHCJS should first
> update their Cabal. Use `ghcjs-boot --dev --clean` to upgrade the boot
> libraries.
>
> luite
>
> [1] https://github.com/haskell/cabal/pull/2269
> [2] https://github.com/haskell/cabal/pull/2273
> [3] https://github.com/ghcjs/cabal
>
>
> On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
> wrote:
> > On 2014-12-01 19:32, Herbert Valerio Riedel wrote:
> >> Hello Cabal developers!
> >>
> >> To keep it short: GHC 7.10.1 RC1 is planned for a release shortly before
> >> Xmas, and it would be great if there was a Cabal 1.22.x RC to go along
> >> with that.
> >>
> >> Is it possible for you to get Cabal (the library) in such a state by
> >> mid-December (i.e. in 2 weeks from now)?
> >>
> >
> > Mostly out of curiousity: is there *any* conceivable chance of getting
> > the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
> > is also on this list.)
> >
> > Regards,
> >
> > _______________________________________________
> > cabal-devel mailing list
> > cabal-devel at haskell.org
> > http://www.haskell.org/mailman/listinfo/cabal-devel
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141218/726622bd/attachment.html>

From johan.tibell at gmail.com  Fri Dec 19 11:07:21 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Fri, 19 Dec 2014 12:07:21 +0100
Subject: Getting Cabal 1.2[12] ready for GHC 7.10.1 RC1
In-Reply-To: <CAK-tuPbWMPy6smxhNtfRVRM4xQAoiW=xt2ZtwzB9-CdD2Yzvew@mail.gmail.com>
References: <87iohvfcgl.fsf@gnu.org> <m5icm2$m37$1@ger.gmane.org>
 <CALqQuohWgUDwA5VL09y6c+aHfHp=HGXqMBFxyxSz7j2RTk7agA@mail.gmail.com>
 <CAK-tuPbWMPy6smxhNtfRVRM4xQAoiW=xt2ZtwzB9-CdD2Yzvew@mail.gmail.com>
Message-ID: <CAK-tuPZr9xPSJ6_s822AZ5ECwSSC8qY5wbsYf6Bjqb2sL4xzyg@mail.gmail.com>

I'm waiting for word from Thomas DuBuisson on
https://github.com/haskell/cabal/pull/1910 then I'm ready to cut a RC.
There's already a 1.22 branch for people who want to test before that (e.g.
GHC HQ).

On Thu, Dec 18, 2014 at 3:40 PM, Johan Tibell <johan.tibell at gmail.com>
wrote:
>
> I went over the outstanding pull requests and merged some and left
> comments on others. Unless I hear something from the authors of those pull
> requests in the next couple of days, I will put out a 1.22 RC based on
> current master.
>
> On Sat, Dec 13, 2014 at 4:54 PM, Luite Stegeman <stegeman at gmail.com>
> wrote:
>>
>> Status update:
>>
>> All functionality from the ghcjs Cabal branch is now in pull requests
>> [1] [2]. I have changed a few things in the GHCJS command line options
>> (more consistent with GHC now), and GHCJS produces library archives
>> (libHSpackage.js_a) for packages now, which makes GHCJS easier and
>> more similar to GHC to deal with, and provides a better upgrade path
>> if we need to store information in the future.
>>
>> I've updated the GHCJS master branch for this, and also the ghcjs
>> branch of our fork [3] . Anyone upgrading their GHCJS should first
>> update their Cabal. Use `ghcjs-boot --dev --clean` to upgrade the boot
>> libraries.
>>
>> luite
>>
>> [1] https://github.com/haskell/cabal/pull/2269
>> [2] https://github.com/haskell/cabal/pull/2273
>> [3] https://github.com/ghcjs/cabal
>>
>>
>> On Mon, Dec 1, 2014 at 7:40 PM, Bardur Arantsson <spam at scientician.net>
>> wrote:
>> > On 2014-12-01 19:32, Herbert Valerio Riedel wrote:
>> >> Hello Cabal developers!
>> >>
>> >> To keep it short: GHC 7.10.1 RC1 is planned for a release shortly
>> before
>> >> Xmas, and it would be great if there was a Cabal 1.22.x RC to go along
>> >> with that.
>> >>
>> >> Is it possible for you to get Cabal (the library) in such a state by
>> >> mid-December (i.e. in 2 weeks from now)?
>> >>
>> >
>> > Mostly out of curiousity: is there *any* conceivable chance of getting
>> > the GHCJS bits merged in? (I'm hoping/guessing the maintainer of GHCJS
>> > is also on this list.)
>> >
>> > Regards,
>> >
>> > _______________________________________________
>> > cabal-devel mailing list
>> > cabal-devel at haskell.org
>> > http://www.haskell.org/mailman/listinfo/cabal-devel
>> _______________________________________________
>> cabal-devel mailing list
>> cabal-devel at haskell.org
>> http://www.haskell.org/mailman/listinfo/cabal-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141219/47303fc0/attachment.html>

From johan.tibell at gmail.com  Sat Dec 20 08:11:31 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Sat, 20 Dec 2014 09:11:31 +0100
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <CAK-tuPaX-UM3aKn6ik+TQ_rKWpfeLc_jP7zOrwfuPNY1ioVRqA@mail.gmail.com>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
 <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
 <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>
 <CAK-tuPaX-UM3aKn6ik+TQ_rKWpfeLc_jP7zOrwfuPNY1ioVRqA@mail.gmail.com>
Message-ID: <CAK-tuPbvAEeMKX6AF=BZabTR3as4MPJVwJ9fCjJr_jwtL1dzjA@mail.gmail.com>

I've spent a considerable amount of time [1] now and I don't think we can
fix it in a way which works with both network < 2.6 and network >=
2.6/network-uri >=26. In fact I don't know if I can get bootstrap.sh
working at all. Without actually using cabal-install to do the
dependency/flag resolution and make sure we build using a consistent set of
packages we end up in problems like these:

Distribution/Client/HttpUtils.hs:68:43:
    Couldn't match expected type ?network-2.4.2.3:Network.URI.URI?
                with actual type ?URI?
    NB: ?network-2.4.2.3:Network.URI.URI?
          is defined in ?Network.URI? in package ?network-2.4.2.3?
        ?URI? is defined in ?Network.URI? in package ?network-uri-2.6.0.1?
    In the ?rqURI? field of a record
    In the expression:
      Request
        {rqURI = uri, rqMethod = GET,
         rqHeaders = Header HdrUserAgent userAgent : ifNoneMatchHdr,
         rqBody = ByteString.empty}

See full log: http://lpaste.net/116892

The cause is the HTTP package and the Cabal package being compiled against
different versions of network. Given how bootstrap.sh works there's no real
avoiding this. We can only hope that the user only has one version of
network installed.

1. See the latest commits on the https://github.com/haskell/cabal/tree/1.18
branch.

On Tue, Dec 16, 2014 at 8:43 AM, Johan Tibell <johan.tibell at gmail.com>
wrote:
>
> Ah, the bootstrap script needs to be updated after the Network.URI split.
> :/
>
> On Tue, Dec 16, 2014 at 4:47 AM, Mi?tek Bak <mietek at bak.io> wrote:
>>
>> I should add ? this is on a bare Ubuntu 14.04 LTS system, with only GHC
>> 7.8.3 installed, and nothing else.
>>
>> --
>> Mi?tek
>>
>>
>>
>>
>> On 2014-12-16, at 03:37, Mi?tek Bak <mietek at bak.io> wrote:
>>
>> > Bootstrapping 1.20.0.4 fails for me:
>> >
>> >       Configuring cabal-install-1.20.0.4...
>> >       Setup: At least the following dependencies are missing:
>> >       network-uri <2.6
>> >
>> >       Error during cabal-install bootstrap:
>> >       Configuring the cabal-install package failed.
>> >
>> > --
>> > Mi?tek
>> >
>> >
>> >
>> >
>> > On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:
>> >
>> >> I just pushed Cabal and cabal-install releases on both the 1.18 and
>> 1.20 branches live.
>> >> _______________________________________________
>> >> cabal-devel mailing list
>> >> cabal-devel at haskell.org
>> >> http://www.haskell.org/mailman/listinfo/cabal-devel
>> >
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141220/3145108f/attachment.html>

From mietek at bak.io  Sat Dec 20 09:02:43 2014
From: mietek at bak.io (=?iso-8859-1?Q?Mi=EBtek_Bak?=)
Date: Sat, 20 Dec 2014 09:02:43 +0000
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <CAK-tuPbvAEeMKX6AF=BZabTR3as4MPJVwJ9fCjJr_jwtL1dzjA@mail.gmail.com>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
 <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
 <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>
 <CAK-tuPaX-UM3aKn6ik+TQ_rKWpfeLc_jP7zOrwfuPNY1ioVRqA@mail.gmail.com>
 <CAK-tuPbvAEeMKX6AF=BZabTR3as4MPJVwJ9fCjJr_jwtL1dzjA@mail.gmail.com>
Message-ID: <F3AB8522-D1F6-4C8F-887E-A0F597599FB0@bak.io>

I?m not sure if I understand the problem.  I believe bootstrap.sh should be expected to be run only on a bare system with nothing but GHC installed.  If the user is already able to install Cabal packages, i.e. has some version cabal-install, they should be using that, not bootstrap.sh.  Does this assumption simplify the problem you?re seeing?

-- 
Mi?tek




On 2014-12-20, at 08:11, Johan Tibell <johan.tibell at gmail.com> wrote:

> I've spent a considerable amount of time [1] now and I don't think we can fix it in a way which works with both network < 2.6 and network >= 2.6/network-uri >=26. In fact I don't know if I can get bootstrap.sh working at all. Without actually using cabal-install to do the dependency/flag resolution and make sure we build using a consistent set of packages we end up in problems like these:
> 
> Distribution/Client/HttpUtils.hs:68:43:
>     Couldn't match expected type ?network-2.4.2.3:Network.URI.URI?
>                 with actual type ?URI?
>     NB: ?network-2.4.2.3:Network.URI.URI?
>           is defined in ?Network.URI? in package ?network-2.4.2.3?
>         ?URI? is defined in ?Network.URI? in package ?network-uri-2.6.0.1?
>     In the ?rqURI? field of a record
>     In the expression:
>       Request
>         {rqURI = uri, rqMethod = GET,
>          rqHeaders = Header HdrUserAgent userAgent : ifNoneMatchHdr,
>          rqBody = ByteString.empty}
> 
> See full log: http://lpaste.net/116892
> 
> The cause is the HTTP package and the Cabal package being compiled against different versions of network. Given how bootstrap.sh works there's no real avoiding this. We can only hope that the user only has one version of network installed.
> 
> 1. See the latest commits on the https://github.com/haskell/cabal/tree/1.18 branch.
> 
> On Tue, Dec 16, 2014 at 8:43 AM, Johan Tibell <johan.tibell at gmail.com> wrote:
> Ah, the bootstrap script needs to be updated after the Network.URI split. :/
> 
> On Tue, Dec 16, 2014 at 4:47 AM, Mi?tek Bak <mietek at bak.io> wrote:
> I should add ? this is on a bare Ubuntu 14.04 LTS system, with only GHC 7.8.3 installed, and nothing else.
> 
> --
> Mi?tek
> 
> 
> 
> 
> On 2014-12-16, at 03:37, Mi?tek Bak <mietek at bak.io> wrote:
> 
> > Bootstrapping 1.20.0.4 fails for me:
> >
> >       Configuring cabal-install-1.20.0.4...
> >       Setup: At least the following dependencies are missing:
> >       network-uri <2.6
> >
> >       Error during cabal-install bootstrap:
> >       Configuring the cabal-install package failed.
> >
> > --
> > Mi?tek
> >
> >
> >
> >
> > On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:
> >
> >> I just pushed Cabal and cabal-install releases on both the 1.18 and 1.20 branches live.
> >> _______________________________________________
> >> cabal-devel mailing list
> >> cabal-devel at haskell.org
> >> http://www.haskell.org/mailman/listinfo/cabal-devel
> >
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4203 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141220/5c226437/attachment.bin>

From hvr at gnu.org  Sat Dec 20 10:21:15 2014
From: hvr at gnu.org (Herbert Valerio Riedel)
Date: Sat, 20 Dec 2014 11:21:15 +0100
Subject: Upper bound on "time" in Cabal causes build failure
In-Reply-To: <CAPeieQEAKwGmkyovRevyxU7G9KPKYG4Kv=diiDzvEVNuFC6zgg@mail.gmail.com>
 (Erik Hesselink's message of "Wed, 17 Dec 2014 11:14:36 +0100")
References: <1418809927.458.hydrogen.mv6.co.uk@hydrogen.mpv6.com>
 <CAPeieQEAKwGmkyovRevyxU7G9KPKYG4Kv=diiDzvEVNuFC6zgg@mail.gmail.com>
Message-ID: <87388a62qs.fsf@gnu.org>

On 2014-12-17 at 11:14:36 +0100, Erik Hesselink wrote:
> It would perhaps be worth it for someone with the right permissions to
> edit the (five) old versions on hackage, and add upper bounds. That
> way cabal install wouldn't use this very old version assuming it works
> (it probably doesn't).

FYI: I've added add a couple of base<4.2 constraints (as GHC
6.12/base-4.2 was the oldest GHC I had installed to prove that Cabal<1.4
is incompatible with base-4.2 ; probably base<4 would be correct as
well, but I have no proof for that)

That should keep Cabal<1.4 versions out of GHC 7.x install-plans...

Cheers,
  hvr

From juhpetersen at gmail.com  Thu Dec 25 03:54:47 2014
From: juhpetersen at gmail.com (Jens Petersen)
Date: Thu, 25 Dec 2014 12:54:47 +0900
Subject: making cabal-install into a library?
Message-ID: <CAEDGBqJ7SmniPVwMPVB82AAxAUuAfrgAVB_FnAjkrXfga31QuA@mail.gmail.com>

Hi,

For a while I have been thinking cabal-install should really be a library.
Has anyone considered or thought about this?
I am wondering how much work it may be?

Best wishes,

Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141225/c1f00836/attachment.html>

From leon.p.smith at gmail.com  Thu Dec 25 16:19:59 2014
From: leon.p.smith at gmail.com (Leon Smith)
Date: Thu, 25 Dec 2014 11:19:59 -0500
Subject: making cabal-install into a library?
In-Reply-To: <CAEDGBqJ7SmniPVwMPVB82AAxAUuAfrgAVB_FnAjkrXfga31QuA@mail.gmail.com>
References: <CAEDGBqJ7SmniPVwMPVB82AAxAUuAfrgAVB_FnAjkrXfga31QuA@mail.gmail.com>
Message-ID: <CAPwAf1=iDfDyEqG546riZ6q4vB35Q+PnV6NDSVyMzxv4+DZ+_Q@mail.gmail.com>

Why not call out to cabal-install as a sub-process?

Best,
Leon

On Wed, Dec 24, 2014 at 10:54 PM, Jens Petersen <juhpetersen at gmail.com>
wrote:

> Hi,
>
> For a while I have been thinking cabal-install should really be a library.
> Has anyone considered or thought about this?
> I am wondering how much work it may be?
>
> Best wishes,
>
> Jens
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141225/506b2c41/attachment.html>

From johan.tibell at gmail.com  Tue Dec 30 14:17:09 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 30 Dec 2014 09:17:09 -0500
Subject: 1.18 and 1.20 patch releases done
In-Reply-To: <F3AB8522-D1F6-4C8F-887E-A0F597599FB0@bak.io>
References: <CAK-tuPaVAu6QMG0+tCdU5PEnT4jpvZwiJCXcLOYs9u5RertkrA@mail.gmail.com>
 <AEB00A47-A002-4C00-91EB-DF587EFD404C@bak.io>
 <C36CB9B2-2AD6-4CEF-8D0F-304C2A60164B@bak.io>
 <CAK-tuPaX-UM3aKn6ik+TQ_rKWpfeLc_jP7zOrwfuPNY1ioVRqA@mail.gmail.com>
 <CAK-tuPbvAEeMKX6AF=BZabTR3as4MPJVwJ9fCjJr_jwtL1dzjA@mail.gmail.com>
 <F3AB8522-D1F6-4C8F-887E-A0F597599FB0@bak.io>
Message-ID: <CAK-tuPZ-bE85KMgxe6eg7YdWzvY6rkdGDERjiMRj29n3CS1RzA@mail.gmail.com>

I've now done 1.18 and 1.20 cabal-install releases that should hopefully
fix this.

On Sat, Dec 20, 2014 at 4:02 AM, Mi?tek Bak <mietek at bak.io> wrote:

> I?m not sure if I understand the problem.  I believe bootstrap.sh should
> be expected to be run only on a bare system with nothing but GHC
> installed.  If the user is already able to install Cabal packages, i.e. has
> some version cabal-install, they should be using that, not bootstrap.sh.
> Does this assumption simplify the problem you?re seeing?
>
> --
> Mi?tek
>
>
>
>
> On 2014-12-20, at 08:11, Johan Tibell <johan.tibell at gmail.com> wrote:
>
> > I've spent a considerable amount of time [1] now and I don't think we
> can fix it in a way which works with both network < 2.6 and network >=
> 2.6/network-uri >=26. In fact I don't know if I can get bootstrap.sh
> working at all. Without actually using cabal-install to do the
> dependency/flag resolution and make sure we build using a consistent set of
> packages we end up in problems like these:
> >
> > Distribution/Client/HttpUtils.hs:68:43:
> >     Couldn't match expected type ?network-2.4.2.3:Network.URI.URI?
> >                 with actual type ?URI?
> >     NB: ?network-2.4.2.3:Network.URI.URI?
> >           is defined in ?Network.URI? in package ?network-2.4.2.3?
> >         ?URI? is defined in ?Network.URI? in package
> ?network-uri-2.6.0.1?
> >     In the ?rqURI? field of a record
> >     In the expression:
> >       Request
> >         {rqURI = uri, rqMethod = GET,
> >          rqHeaders = Header HdrUserAgent userAgent : ifNoneMatchHdr,
> >          rqBody = ByteString.empty}
> >
> > See full log: http://lpaste.net/116892
> >
> > The cause is the HTTP package and the Cabal package being compiled
> against different versions of network. Given how bootstrap.sh works there's
> no real avoiding this. We can only hope that the user only has one version
> of network installed.
> >
> > 1. See the latest commits on the
> https://github.com/haskell/cabal/tree/1.18 branch.
> >
> > On Tue, Dec 16, 2014 at 8:43 AM, Johan Tibell <johan.tibell at gmail.com>
> wrote:
> > Ah, the bootstrap script needs to be updated after the Network.URI
> split. :/
> >
> > On Tue, Dec 16, 2014 at 4:47 AM, Mi?tek Bak <mietek at bak.io> wrote:
> > I should add ? this is on a bare Ubuntu 14.04 LTS system, with only GHC
> 7.8.3 installed, and nothing else.
> >
> > --
> > Mi?tek
> >
> >
> >
> >
> > On 2014-12-16, at 03:37, Mi?tek Bak <mietek at bak.io> wrote:
> >
> > > Bootstrapping 1.20.0.4 fails for me:
> > >
> > >       Configuring cabal-install-1.20.0.4...
> > >       Setup: At least the following dependencies are missing:
> > >       network-uri <2.6
> > >
> > >       Error during cabal-install bootstrap:
> > >       Configuring the cabal-install package failed.
> > >
> > > --
> > > Mi?tek
> > >
> > >
> > >
> > >
> > > On 2014-12-15, at 23:16, Johan Tibell <johan.tibell at gmail.com> wrote:
> > >
> > >> I just pushed Cabal and cabal-install releases on both the 1.18 and
> 1.20 branches live.
> > >> _______________________________________________
> > >> cabal-devel mailing list
> > >> cabal-devel at haskell.org
> > >> http://www.haskell.org/mailman/listinfo/cabal-devel
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141230/5c48fd05/attachment.html>

From johan.tibell at gmail.com  Tue Dec 30 18:17:34 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 30 Dec 2014 13:17:34 -0500
Subject: The bootstrap.sh script has to go
Message-ID: <CAK-tuPZE_3yt5owVbaw8pnC34cFzKNNUHLVmOK7z-2wiuJrYkg@mail.gmail.com>

Hi all,

I've spent more time on the bootstrap.sh script than anything else, making
it emulate cabal flag resolution for the network-uri split and make it deal
with the fact that network-uri makes Haddock choke. this release. That
feels like a somewhat wasteful activity and I'm tired of maintain a
stinking pile of shell script.

Unless someone is willing to rewrite it as a Haskell program (that could be
run using runhaskell), I vote we dump it and instead encourage users to
bootstrap using e.g. the Haskell Platform.

-- Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141230/d565130c/attachment.html>

From johan.tibell at gmail.com  Tue Dec 30 19:35:42 2014
From: johan.tibell at gmail.com (Johan Tibell)
Date: Tue, 30 Dec 2014 14:35:42 -0500
Subject: Cabal 1.22 RC ready to test
Message-ID: <CAK-tuPZFahzk4TkY3_O53_=S3CrnhbGgRZ4j5BHSG2o__YHVQA@mail.gmail.com>

 Hi all,

I've now prepared release candidate for Cabal/cabal-install 1.22. Please
test them and report bugs here and/or on the bug tracker (
https://github.com/haskell/cabal/issues). To install:

    cabal install http://johantibell.com/files/Cabal-1.22.0.0-rc.tar.gz
http://johantibell.com/files/cabal-install-1.22.0.0-rc.tar.gz

Cabal is now such a big project that's used in so many context (e.g.
different OSes) that we need your help to help us test, to make sure that
new releases work for you.

-- Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141230/8315761b/attachment.html>

From jakewheatmail at gmail.com  Tue Dec 30 20:23:19 2014
From: jakewheatmail at gmail.com (Jake Wheat)
Date: Tue, 30 Dec 2014 22:23:19 +0200
Subject: The bootstrap.sh script has to go
In-Reply-To: <CAK-tuPZE_3yt5owVbaw8pnC34cFzKNNUHLVmOK7z-2wiuJrYkg@mail.gmail.com>
References: <CAK-tuPZE_3yt5owVbaw8pnC34cFzKNNUHLVmOK7z-2wiuJrYkg@mail.gmail.com>
Message-ID: <CAGQv8D5Y5-BwaTiK=TSEnJdJGOSFnjFoeM7k2q7+50nZ7F9tdQ@mail.gmail.com>

I have some ideas about how to improve the bootstrap.sh situation.

Rewriting in haskell sounds like a good idea to avoid the shell script
mess.

Simplify the bootstrap.sh process:

* always use a fixed set of versions of packages for the dependencies
* always bootstrap in a sandbox, and ignore packages in the global and
  user package database - only reuse an existing package if it is in
  the bootstrap sandbox and is the exact version expected
* possibly the set of versions of packages can be in an external file,
  and possibly bootstrap can optionally try to download a new
  dependencies version file when bootstrap.sh is run
* possibly the set of dependency package versions can be different for
  different versions of ghc
* there could even be a process which uses a cabal-install to generate
  the list of bootstrap.sh dependency versions in some automatic way
* choose the bootstrap to always do shared or non shared (not sure
  which is best). Don't have options to do profiling, haddock, change
  the prefix, etc. at all.
* if any dependency packages need specific flags, then this can be
  hardcoded in some way linked to in the dependency package versions

This allows more reliable bootstrapping on a new system, and more
reliable bootstrapping e.g. if you delete the cabal-install binary and
also happen to have all sorts of stuff in your user package database.

In this system, if you want the latest cabal-install and you want it
with the latest packages, or with profiling, haddock, etc. then you
can just bootstrap.sh, then use the cabal-install binary to build a
latest and greatest cabal-install with the full constraint solver and
any options you want. I think this is a reasonable compromise to allow
easy maintenance and a reliable and painless bootstrap.sh process.

I can work on some variation of this if it sounds acceptable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20141230/28cf9670/attachment.html>