Important or serious bug in loudmouth + libasyncns

[Tanguy Ortolo]

Le mercredi 24 novembre 2010, Tanguy Ortolo a écrit :
> I have just faced a bug accros several packages, that has the effect of
> rendering any Jabber client based on loudmouth unusable on armel.
> 
> This is the bug #566143. Here is a summary:
> * loudmouth embeds a copy of libasyncns, version 0.3, that fails on
>   armel;
> * the packages libasyncns is version 0.3 too, so it is affected as well.

So, after all, this bug:
* renders libasyncns unable to resolve anything;
* forbids libloudmouth to resolve the Jabber server name.
I estimated that this deserves two bugs with severity grave as it
renders both packages unusable: #566139 and #566143.

As you can see in these bug reports, I fixed them, by preparing two
NMUs, that:
* libasyncns: backports an upstream fix;
* loudmouth: patches the build system to dynamically link against
  libasyncns instead of embedding it, and updates the package
  dependencies accordingly; this patch is quite important because it
  required to regenerate the configure script.

Now I need sponsoring. Would someone have time to check these
modifications and upload them? Then I shall request freeze exceptions
from the release team.

Regards,

-- 
 ,--.
: /` )   Tanguy Ortolo <xmpp:tanguy at ortolo.eu> <irc://irc.oftc.net/Elessar>
| `-'    Theoretically Debian Maintainer
 \_
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20101125/7eb927c6/attachment.pgp>