On Wed, May 08, 2013 at 01:59:38AM +0200, Aurelien Jarno wrote: > > They weren't coordinated within the team. Furthermore I don't consider > that eglibc was ready to go to unstable, as it was known that two > architectures were going to FTBFS, without a real try to get that fixed > (for example by contacting the porters).
I'll absolutely take blame for not trying harder to contact more porters than just you on IRC. On the flip side, I don't think I'm entirely off my rocker in thinking that maybe porters with direct commit access to the packaging might have cared that eglibc has been FTBFS in experimental for four and a half months. This isn't new. And, as we've discovered today, most of the fixes required were really quite trivial (though we're not quite done yet). Anyhow. Arguments are cheap and, generally, pointless. Hopefully Petr has some clever ideas to get us past the last kfreebsd/glibc snag, and I'll have another stab at it tomorrow if this flu subsides and lets me think straight. As I said before, I'm sorry for not coordinating this better outside of Matthias and I. It'll happen differently next time. I can't go back in time and make this time different, so discussing it ad nauseum does no one any good. ... Adam -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130508003516.gg29...@0c3.net
