Steve Langasek wrote: >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. > >
This conflict was added on request by Goswin just to avoid spurious bug reports due to this incompatibility while it's being investigated upstream. The bug is still open (i just pointed to it in the changelog, i didn't close it). >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. > > First of all, i'm waiting for the upstream response. Currently, we check what causes the stack corruption. Upstream isn't aware of any incompatible change they made. >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, Jochen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
