Re: Forcing a rebuild with ghc-6.10.3

Simon Horman wrote: > I would just bump the version to 1.3.5-2 and note something like "rebuilt > with the 6.10.3 compiler" in the changelog. I am guessing that the binary > packages will automatically pick up new dependencies - which is somewhat > akin to a metadata change to my mind. Sure. > Y

Re: Forcing a rebuild with ghc-6.10.3

On Sat, May 30, 2009 at 10:47:31AM +1000, Erik de Castro Lopo wrote: > Hi all, > > I'm a new maintainer and my first haskell package is haskell-curl > version 1.3.5-1 which my sponsor uplaoded on May 18th, a day before > Kari Pahula uploaded the new 6.10.3 compiler. > > Its my understanding that

Forcing a rebuild with ghc-6.10.3

Hi all, I'm a new maintainer and my first haskell package is haskell-curl version 1.3.5-1 which my sponsor uplaoded on May 18th, a day before Kari Pahula uploaded the new 6.10.3 compiler. Its my understanding that to kick off a rebuild of my package with the new compiler I basically need to uplo

Re: (partial) ghc6 6.10.3 library transition

Joachim Breitner wrote: Hi again, this package was tried while a dependency was broken. The bug has been fixed and they can be re-tried: gb haskell-x11-xft-0.3-3+b1 . amd64 sparc given back Cheers Luk -- To UNSUBSCRIBE, email to debian-haskell-requ...@lists.debian.org with a subject of "u

Re: (partial) ghc6 6.10.3 library transition

On Fri, May 29, 2009 at 08:20:39AM +, Joachim Breitner wrote: > Hi again, > > this package was tried while a dependency was broken. The bug has been > fixed and they can be re-tried: > > gb haskell-x11-xft-0.3-3+b1 . amd64 sparc There were alot more packages affected by this, and I will look

Re: (partial) ghc6 6.10.3 library transition

Hi again, this package was tried while a dependency was broken. The bug has been fixed and they can be re-tried: gb haskell-x11-xft-0.3-3+b1 . amd64 sparc Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@jo

Re: Downgrading parsec to 2.x?

Hi, Am Freitag, den 29.05.2009, 15:51 +0300 schrieb Kari Pahula: > I could just bump Parsec back to 2.1.0.1. But I decided to ask for a > second opinion this time around. Anyone want to see 3.x also? Or > only 3.x, after all? I happend to start a new project with parsec 3 (mostly by chance, si

Re: Downgrading parsec to 2.x?

Kari Pahula wrote: > Anyone want to see 3.x also? Or only 3.x, after all? I would like 3.x also so I can port (currently 2.x-only) apps to it. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature

Re: Downgrading parsec to 2.x?

Kari Pahula wrote: > Hi. I upgraded Parsec to version 3.0.0 along with ghc 6.10.1. I got > a bit of flak for doing that. Looks like there's a case for having > 2.1.0.1 around, instead. > > I packaged two versions of QuickCheck, as it's not hard to find > packages in Hackage that use either. Bu

Downgrading parsec to 2.x?

Hi. I upgraded Parsec to version 3.0.0 along with ghc 6.10.1. I got a bit of flak for doing that. Looks like there's a case for having 2.1.0.1 around, instead. I packaged two versions of QuickCheck, as it's not hard to find packages in Hackage that use either. But I don't know if there's a cas

Re: (partial) ghc6 6.10.3 library transition

Hi again, this package was tried while a dependency was broken. The bug has been fixed and they can be re-tried: gb haskell-x11-xft-0.3-3+b1 . amd64 sparc Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@jo