On Sun, Aug 27, 2017 at 03:16:46PM +0200, Anton Gladky wrote: > > Still I believe that this should be "correctly" fixed. > > You mean to increase so-version even if upstream does not do it and > to start the normal transition process? I think it is possible.
That's actually your only option.
Could someone check the symbols of the library before and after the
upload and check whether some have been dropped? If there are, not
bumping SONAME is a bug upstream should deal with by doing another
release and doing so (and failing so, in Debian you should at the very
least rename the binary package (doing somethng alike to the v5 thing
done for libstdc++5)).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
