Dear Cyril, Am Donnerstag, den 14.06.2012, 11:04 +0200 schrieb Cyril Brulebois: > severity 676970 serious > thanks > > Jonathan Nieder <jrnie...@gmail.com> (10/06/2012): > > Cloning and assigning to ghc. If the way ABI is tracked in ghc is > > causing valid bugs to be thrown away, that's a problem, in my opinion. > > Indeed. And since the package isn't installable right now, bumping > severity to serious.
I’m really not sure what this is about. Who is throwing bugs away (and what does that mean anyways to throw a bug away?)? All I am saying is that at this point of the release cycle, I am very reluctant to do an upload of GHC. I’m sure those of the release team who currently manage the transition will agree that it would be unwise now. I am not saying that I won’t fix GHC (or rather, adjust GHC to changed semantics in dpkg) at all; quite contrary I did announce that I’ll do it on the next upload. It there a deeper misunderstanding here? An in case this bug now hinders the migration that mehdi set up for today: I think this bug can be ignored for wheezy right now, as the dpkg version in wheezy does _not_ make ghc fail to install. We just should make sure that before dpkg 1.16.4 it is turned the error into a warning, e.g. 676874 is closed. (Doesn’t this make 676874 RC?) That fix is required anyways as wheezy’s dpkg needs to be able to install packages from squeeze. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
