Re: Packaging PythonQt for Qt 5

[Sandro Knauß]

Hey,

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

there is no "formal way" nor pull request. The normal workflow is to use 
mentors and personal repos and send the link around.

* mentors.debian.org
* https://wiki.debian.org/Alioth/Git#Forking_Git_repositories_onto_Alioth

( You can use every other git hosting platform, if you wish)

After some time we will grant you permission to push to git directly. 

Hopefully this works for you.

Best Regards,

sandro


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Packaging PythonQt for Qt 5

[Erik Lundin]

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)


libPythonQt-Qt5-Python2.7.so -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3 -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3.2 -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so.3 -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so.3.2 -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0

libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0

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


/Erik

--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk