Bug#504603: libbobcat1: shlibs file fails to reflect ABI additions
Package: libbobcat1 Version: 1.21.1-1 Severity: serious Justification: Policy 8.6 libbobcat1's shlibs file leads to unversioned dependencies on the library, which (as demonstrated in #504185) are not always sufficient given that it's evidently gained new symbols over time. There are various ways to fix this issue, depending on how much maintenance effort you wish to spend and to what extent (if at all) you care whether dependencies ultimately wind up tighter than strictly necessary. In this case, though, I would suggest simply adding -V to your call to dh_makeshlibs, such that packages built against libbobcat1 always depend on at least the upstream version against which they were built. Although that may be overkill in some instances, it has the advantages of requiring no further maintenance and ensuring that dependencies will always be sufficiently tight (assuming you never extend the ABI from one Debian revision of an upstream version to the next). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages libbobcat1 depends on: ii libc6 2.7-16 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1 GCC support library libbobcat1 recommends no packages. libbobcat1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504603: libbobcat1: shlibs file fails to reflect ABI additions
Dear Aaron M. Ucko, you wrote: Package: libbobcat1 Version: 1.21.1-1 Severity: serious Justification: Policy 8.6 libbobcat1's shlibs file leads to unversioned dependencies on the library, ... In this case, though, I would suggest simply adding -V to your call to dh_makeshlibs, such that packages built against libbobcat1 always depend on at least the upstream version against which they were built. Dear Aaron, Thank you for filing this bug against Bobcat. You're of course absolutely right and I think your suggestion is a valuable one that can easily be met in future releases. Actually the bug filed against xd clarified the (dependency) bug that had crept into the dependencies list. The problem will be attacked along two main approaches: 1. paying more attention to ABI and API breakages; 2. making sure that (at least my :-) packages clearly display the bobcat version against which the package should be linked. This reply was (of course) not written to close the bug; it was primarily sent to let you and others know that I'm aware of the problem and that for now using the latest (now 1.21.1) Bobcat version with packages that depend on Bobcat should be enough to avoid problems. Current work in progress on Bobcat will probably result in version 2.01.1 from which point on more thorough attention will be paid to version dependencies. Cheers, -- Frank B. Brokken Center for Information Technology, University of Groningen (+31) 50 363 9281 Public PGP key: http://pgp.surfnet.nl Key Fingerprint: 8E36 9FC4 1DAA FCDF 1A0D B19F DAC4 BE50 38C6 6170 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
