Hi Brian,
On Mon, Jul 17, 2017 at 05:53:25PM +1000, Brian May wrote:
Looks like this a fix for a previously undetected regression. i.e. it
changes the signature back to what it should have been. I fix that was
included in 7.4.0, that is now in unstable.
Unfortunately, as stable now has the bad signature, I really have no
idea what to do with this.
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.
Suggestions? Maybe I should ask on debian-devel?
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).
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.
thanks,
Ryan
