Hi Laurent Bigonville píše v Po 17. 07. 2017 v 11:35 +0200: > If you don't have a lot of reverse-dependency, one of the solution is > to > ask to binNMU to rebuild the packages with the proper version of the > symbol then and then wait to see what upstream is saying > > INVHO I wouldn't revert the change without knowing what upstream > will > do, you might end up with carrying a patch forever...
The revert brings the library to the state it was on 0.2.9 version
(which is shipped in stretch), so upgrade from this state anyway will have to
be handled. I've chosen this as it is minimal change which can bring the ABI to
the state we had before. Once upstream decides on fix, we can easily follow (as
it will most likely either make versioning same as we have right now or bump
soname).
Doing binNMU without soname change sounds weird to me and that would
more likely lead to problems on upgrade, that's why I haven't
considered this at all.
--
Michal Čihař | https://cihar.com/ | https://weblate.org/
signature.asc
Description: This is a digitally signed message part
