Re: Haskell migration exp to unstable

2013-05-24 Thread Joachim Breitner
Hi, Am Freitag, den 24.05.2013, 01:18 +0200 schrieb Julien Cristau: > On Wed, May 8, 2013 at 23:18:41 +0200, Joachim Breitner wrote: > > > Hi, > > > > Am Mittwoch, den 08.05.2013, 16:51 +0200 schrieb Julien Cristau: > > > I'd like to have the switch to libffi6 (#667906) sorted before that, if >

Re: Haskell migration exp to unstable

2013-05-23 Thread Julien Cristau
On Wed, May 8, 2013 at 23:18:41 +0200, Joachim Breitner wrote: > Hi, > > Am Mittwoch, den 08.05.2013, 16:51 +0200 schrieb Julien Cristau: > > I'd like to have the switch to libffi6 (#667906) sorted before that, if > > possible. > > no problem. Just to make sure I get you right: We should not up

Re: Haskell migration exp to unstable

2013-05-08 Thread Julien Cristau
On Wed, May 8, 2013 at 23:18:41 +0200, Joachim Breitner wrote: > no problem. Just to make sure I get you right: We should not upload > Haskell packages to unstable until libffi6 is safe and sound in jessy? > Pretty much, yes, since we'll have to binNMU all of them to get them off libffi5. Thank

Re: Haskell migration exp to unstable

2013-05-08 Thread Joachim Breitner
Hi, Am Mittwoch, den 08.05.2013, 16:51 +0200 schrieb Julien Cristau: > On Sun, May 5, 2013 at 12:29:00 +0200, Joachim Breitner wrote: > > > The Haskell team has staged the newest version of GHC (7.6.3) together > > with lots of library upgrades in experimental, but we’d like to move out > > of t

Re: Haskell migration exp to unstable

2013-05-08 Thread Julien Cristau
On Sun, May 5, 2013 at 12:29:00 +0200, Joachim Breitner wrote: > The Haskell team has staged the newest version of GHC (7.6.3) together > with lots of library upgrades in experimental, but we’d like to move out > of that ghetto as soon as possible. The transition is mostly > self-contained and, d

Haskell migration exp to unstable

2013-05-05 Thread Joachim Breitner
Hi Release team, thanks for the release! Am Sonntag, den 05.05.2013, 02:16 +0100 schrieb Adam D. Barratt: > As for Squeeze, we'd ask that you co-ordinate particularly large > transitions or changes; if your plans involve major toolchain changes or > otherwise have the potential to cause problems