On Wed, Nov 17, 2010 at 02:32:47 -0800, Don Armstrong wrote:

> 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.
> 
jcris...@franck:~$ dak ls -a i386 jabberd14
 jabberd14 | 1.6.1.1-5+b1 |       testing | i386
 jabberd14 | 1.6.1.1-5+b1 |      unstable | i386

jcris...@franck:~$ zcat 
/srv/ftp-master.debian.org/ftp/dists/sid/main/binary-i386/Packages.gz 
|grep-dctrl -PX jabberd14 -sPackage,Version,Depends
Package: jabberd14
Version: 1.6.1.1-5+b1
Depends: adduser, lsb-base (>= 3.0-6), openssl, libjabberd2 (= 1.6.1.1-5+b1), 
libc6 (>= 2.3.6-6~), libgcc1 (>= 1:4.1.1), libidn11 (>= 1.13), libmysqlclient16 
(>= 5.1.21-1), libpopt0 (>= 1.16), libpq5 (>= 8.4~), libpth20 (>= 2.0.7), 
libstdc++6 (>= 4.4.0)

There was no point keeping this bug open once the rebuild had been
queued (there was nothing to fix in the source package in the first
place), and there's even less point arguing about it now that it's in
the archive.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature

Reply via email to