Package: libc-ares1 Version: 1.5.1-0 Severity: minor The 1.5.1 release of c-ares upstream bumped the major soversion from 1 to 2. However, the packaging was not updated to reflect this, leading to the anomalous situation that libc-ares1 contains /usr/lib/libcares.so.2. This is a violation of a "should" from the Library Packaging Guide, and Lintian picks this up as a warning.
This means that any package built against the 1.4.1 version of libc-ares-dev will in fact mysteriously start failing when the installed version of libc-ares1 is upgraded to 1.5.1, and the file disappears. I've filed this as minor because presumably no packages are suffering from the above problem, which is lucky. There was a fortnight where it was possible to fall over this, according to [1]. If there was such a package suffering this, then I assume there would be such a bug against c-ares already. [1] http://packages.qa.debian.org/c/c-ares.html This issue also affects users looking for the library for third-party apps. If a program is looking for libcares.so.2 according to ldd, then usually one would try to install package libcares2 to resolve this. Of course, this assumption is already broken by the soname libcares differing from the package name libc-ares, but I'm assuming that a good reason for this difference already exists. (Although I don't see a README.Debian or similar in the installed packages documenting this.) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc-ares1 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries libc-ares1 recommends no packages. -- no debconf information -- Paul "TBBle" Hampson, [EMAIL PROTECTED] Shorter .sig for a more eco-friendly paperless office.
pgpK9OLwDkWvR.pgp
Description: PGP signature
