Den 2017-05-27 kl. 22:38, skrev Dmitry Shachnev:
Yes, the soname is something to consider for upstream. If we think upstream
made an ABI break, we usually do not patch the soname, but instead rename the
package, i.e. append a prefix (“a” or “v5”).

The new upstream release 3.2 solves this. The produced libraries are now (for Python 2.7) -> -> -> -> -> ->

How can I submit my packaging changes for review? Are you using pull requests somewhere?



Reply via email to