libcapi20-3: devel files in a library package
Bug #7770 reported by
Debian Bug Importer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Debian) |
Fix Released
|
Unknown
|
|||
samba (Ubuntu) |
Fix Released
|
High
|
Matthias Klose |
Bug Description
Automatically imported from Debian bug report #269872 http://
Changed in samba: | |
status: | Unknown → Fix Released |
To post a comment you must log in.
# 1 definition found
#
# From WordNet (r) 2.0 [wn]:
#
# unrelated
# adj 1: not connected or associated [ant: {related}]
# 2: not connected by kinship [ant: {related}]
#
severity 269767 grave
clone 269797 -1
retitle -1 libcapi20-3: devel files in a library package
severity -1 serious
thanks
The libcapi20-3 package contains libcapi20.so.2, not libcapi20.so.3 as
its name suggests. This looks very much like there have been
incompatible ABI changes without an soname change -- but with a package
name change, which is quite peculiar!. While the package name change
ensures that other packaged software using this library will function
correctly, library maintainers are expected to provide at least minimal
support for local third-party software by not breaking the
one-soname-one-ABI rule.
This package also contains static libs, libtool .la files, and header
files, all of which belong in a -dev package per policy. You have added
a Conflicts: against older versions of the library to ensure that dpkg
doesn't complain about this state of affairs, but it's nevertheless
contrary to the fundamental goals of providing shared library packages.
Since the packages depending on libcapi20-2 in testing also appear to be
in rather sorry shape right now, including one must-go package that
depends on libtiff3g, I'm planning to remove all of these packages from
testing pending resolution of the isdnutils bugs.
Thanks,
--
Steve Langasek
postmodern programmer