Ryan Tandy <r...@nardis.ca> writes: > Right. Unfortunately the different signature was in Debian for a long > time (since squeeze, I think). I for one always assumed the change was > intentional and it would just stay that way.
Oh, yes, looks like you are right. I thought this was introduced in Stretch, but looks like Wheezy and Jessie has it too. > Possibly, yeah. The pedantic answer is this requires a SONAME bump and > transition; but that may be overkill in this case. smbk5pwd is for sure > the only user in Debian, and I'd be surprised if there are any external > users (maybe an occasional user building their own smbk5pwd). The problem with bumping the SONAME, is this means that we are forever out of sync with the upstream SONAME. > A symbols file update would be nice, so future builds of slapd-smbk5pwd > pick up a minimum dependency. If libhdb would add a Breaks on > slapd-smbk5pwd (<< 2.4.44+dfsg-8), that would fix partial upgrades from > the other direction too. We had a similar issue just before the release of Stretch. See #848694. Two symbols were removed from the upstream library. Adding breaks headers was suggested, but the release team strongly disliked this solution. We ended up patching these symbols back in. I am not particularly keen on maintaining a growing set of patches that maintain backward compatability for eternanity while deliberately breaking compatability with other non-Debian-distributions however. -- Brian May <b...@debian.org>
