Hi, the package python-cryptopp in factory (https://build.opensuse.org/package/show?package=python-cryptopp&project=openSUSE%3AFactory) contains an embedded copy of cryptopp-5.5.2. I'm quite surprised to see it in factory at all because no other package uses it. In the build service, there is a package of cryptopp-5.6.0 (https://build.opensuse.org/package/show?package=libcryptopp&project=devel%3Alibraries%3Ac_c%2B%2B). Problem: cryptopp does not build a shared library by default and therefore does not have upstream version information for the shared library. The package in the build service is rather naïvely using "libcryptopp.so.5" as the SONAME - I assume that ".so.5" has been chosen because the package version starts with a five, but that will not work because binary compatibility does break between releases. Ubuntu and Debian are currently at ".so.8" for cryptopp-5.6.0 (http://packages.ubuntu.com/source/natty/libcrypto++, http://packages.debian.org/source/sid/libcrypto++) and ".so.9" for cryptopp-5.6.1 (http://packages.debian.org/source/experimental/libcrypto++). Mandriva used to sync with Debian, but is now stuck at cryptopp-5.5.2 and therefore ".so.6". Fedora copied the package from Mandriva at version 5.5.2 and is since then stuck at ".so.6", too, even though Fedora has newer versions that did break the ABI. What should be done in such a situation? I'd suggest to either drop python-cryptopp from factory (it's outdated and broken anyway), or add cryptopp-5.6.1 to factory with the Debian SONAME (since there are so many distibution-invented SONAMES already that we don't to need to invent our own, and Fedora's one is broken) and update python-cryptopp to make it use the external cryptopp package. Andreas -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org