DA> 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.
DA> It's not an RC bug; at most it is severity important.
User upgrades his system and then jabber-server becomes broken. It is
grave severity:
=quote
makes the package *in question unusable* or mostly so, or causes
data loss, or introduces a security hole allowing access to the
accounts of users who use the package.
=cut
DA> [1] Secondly,
DA> this bug only occurs if you've managed to only upgrade jabberd14,
1. When squeeze is released, many people will do like that.
2. I had the bug without upgrade:
2.1 I had clean lenny
2.2 I added squeeze into sources.list
2.3 I installed jabberd14
2.4 I got the problem
DA> and not libidn11.
DA> This bug is actually a bug in libidn11, not jabberd14,
I agree, but bug against libidn11 was closed 11 Oct,
Now is 17 Nov, bug is still reproducible. So I think that including
version into depends will solve this problem. Or broken libidn11
must be replaced in debian repos.
Until problem is solved a bug must be opened: the problem is exists
and reproducible.
DA> which has already been fixed, and the solution is rebuilding
DA> jabberd14, which has (supposedly) already been queued.
It fits for testing, but I'm afraid that when squeeze is released
and this problem wont be solved: there is no bugreport which is opened.
--
... mpd is off
. ''`. Dmitry E. Oboukhov
: :’ : email: [email protected] jabber://[email protected]
`. `~’ GPGKey: 1024D / F8E26537 2006-11-21
`- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537
signature.asc
Description: Digital signature
