Package: libssl096 Version: 0.9.6-1 Severity: normal In bug report #78410 entitled "libssl096 does not provide /usr/lib/lib*.so.0", Ivan Moore complains that libssl096 fails to provide libcrypo.so.0 etc.
After several email exchanges, Ivan and the maintainer, Christoph Martin, end up agreeing that libssl096 should NOT provide libcrypto.so.0, presumably for the following reason: Upstream uses the MAJOR and MINOR numbers in the soname rather than the MAJOR number only. Common convention is to use the MAJOR number only in the soname. However, since upstream uses both MAJOR and MINOR, I agree that the maintainer should not modify the soname and he should not cause libssl096 to provide libcrypto.so.0. Now, since the MAJOR and MINOR numbers are both used in the soname, one could presume that libssl09, libssl095a, and libssl096 could all be installed simultaneously. However, libssl09 and libssl095a have been obsoleted and have been removed from sid EVEN THOUGH there are packages that still depend on them. If libssl096 doesn't provide libssl.so.0, the other versions should not be obsoleted by the maintainer. Moreover, the ftp-admins should not have removed them from sid. I have cross-posted this to debian-devel for the purposes of discussing the soname issue. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux tolkien 2.2.18pre23-tolkien #1 Sat Dec 9 17:08:59 PST 2000 i686 Versions of packages libssl096 depends on: ii libc6 2.2.1-1 GNU C Library: Shared libraries an