On Tue, Jul 18, 2017 at 08:23:01AM +1000, Brian May wrote:
The problem with bumping the SONAME, is this means that we are forever
out of sync with the upstream SONAME.
One possible alternative is renaming the package without actually
bumping SONAME; for example libhdb9a. Then you get to re-sync with
upstream at the next increment.
Random examples: libdkim1d, libmutter0i, various toolchain transitions
(*c2a, *v5).
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.
I think following upstream on this one is the right thing to do. I don't
want to create extra work for you, but I do think we should handle this
breakage somehow since we know it can happen. If that's best achieved by
a change on the openldap side, I'm of course open to that too.
If you were to perform a transition for heimdal (the package rename
technique seems like it could apply to libroken as well), we're probably
at a good point in the release cycle for it...
thanks,
Ryan
