Jochen, The changelog for net-snmp 5.2.1.2-2 states:
* Added conflicts against all packages using libsnmp5 due to upstream
changing the binary API without increasing SONAME. See: #322500
This is not an appropriate fix for this bug. << Conflicts are
contraindicated by policy, because they will result in the package manager
removing packages instead of upgrading them in order to resolve unsatisfied
dependencies.
If this is indeed an ABI change in the library, and upstream seems unwilling
to change the SONAME (which I hope is not the case, given that libsnmp is
quite a popular library and libsnmp5 shipped with sarge and probably plenty
of other distros since it's been around since at least April 2003), then you
must still rename the Debian package and conflict with the existing libsnmp5
package. Creating a Debian-specific SONAME, e.g. libsnmp.so.5debian1, may
even be a better option than this.
I have asked maintainers of packages depending on libsnmp5 to not spend time
recompiling to avoid this conflict, since another recompile will be
necessary once the library package is renamed.
Thanks,
--
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
