severity 339056 serious reassign 339056 tktable thanks On Mon, Nov 14, 2005 at 02:27:44PM -0500, Justin Pryzby wrote: > Package: tktable-dev > Version: 2.9-1 > Severity: grave > Justification: 8.6: when a package is built which contains any shared > libraries, it must provide a `shlibs' file for other packages to use
> The package doesn't include a .shlibs file. There is some > disagreement about whether this shared library is meant to be used by > other packages; but it seems that since it is a separate package, that > must be the intent, so the requirement to include a shlibs file holds. First, the shlibs file is to be provided by the package which contains the shared lib, not the file that contains the .so -dev symlink; so this bug would belong to tktable, not tktable-dev. Second, policy violations are severity: serious, not severity: grave. Anyway, the problem here is much more involved than just the shlibs file. The shared library in tktable is installed as ./usr/lib/Tktable2.9/libTktable2.9.so, not as /usr/lib/libTktable.so.2.9 as it should be if this is a shared library; there is no .so symlink in /usr/lib usable for linking, one can only link to this library using -L/usr/lib/Tktable2.9 -lTktable2.9; and the shared library doesn't have an SONAME value, which incidentally makes the symlinks that *are* in /usr/lib completely pointless. So if this is supposed to be a public shared library, then it needs to be moved to /usr/lib, have an soname added, and have appropriate symlinks added (to tktable and tktable-dev both); if it's not supposed to be a public shared library, then the symlinks in /usr/lib should just be dropped. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
