On Wed, 17 Nov 2010, Dmitry E. Oboukhov wrote: > The problem is still reproducible. So or this or 550650 (was done 11 > Oct) or the other RC must be open (for ex against buildd), but You > (You and Julien) prefer to keep your eyes closed. It's a pity.
It's not an RC bug; at most it is severity important.[1] Secondly, this bug only occurs if you've managed to only upgrade jabberd14, and not libidn11. This bug is actually a bug in libidn11, not jabberd14, which has already been fixed, and the solution is rebuilding jabberd14, which has (supposedly) already been queued. As such, there's no point in keeping this bug open at all, once the build has been queued. I was under the mistaken impression that Julien was the maintainer (since I didn't bother to check), but that doesn't change the facts surrounding this bug. Don Armstrong 1: important: a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. [See http://www.debian.org/Bugs/Developer#severities for more details.] -- Debian's not really about the users or the software at all. It's a large flame-generating engine that the cabal uses to heat their coffee -- Andrew Suffield (#debian-devel Fri, 14 Feb 2003 14:34 -0500) http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
