python3x-pyside2 missing in TW
Hi, I noticed that build-flavours python36/38/39-pyside2 are missing in TW. python3-pyside2 is obviously not considered sufficient (means, build targets of a singlespec python package are 'unresolveable'). Do I need to change the singlespec, or is pyside2 being adjusted? Thanks Axel
Hi Axel, Am 13.05.21 um 19:49 schrieb Axel Braun:
Hi,
I noticed that build-flavours python36/38/39-pyside2 are missing in TW. python3-pyside2 is obviously not considered sufficient (means, build targets of a singlespec python package are 'unresolveable').
Do I need to change the singlespec, or is pyside2 being adjusted?
Do you have a package which really needs PySide2 and cannot use PyQt5 for those flavors? When it is an alternative supported by a package, it often is added as a suggestion to the python3 flavor, but generally there is not a hard runtime requirement. It is possible to change python3-pyside2 to singlespec python-pyside2 [1, 2]. But I am not sure if the Qt5 maintainers are very fond of such a change. And I would not submit it without further changes. I am particularly unhappy about the re-install hack to circumvent Qt's supposedly buggy setup.py install behavior: * Some of the devel tools entry-points are lost, e.g. pyside2-designer. * The egg-info for the installed modules is lost. This could prevent loading PySide2 for downstream packages with entry-points. PySide6 as being prepared by Christophe [3] is also python3 only at the moment.
Thanks Axel
Cheers, Ben [1] https://build.opensuse.org/package/show/home:bnavigator:branches:KDE:Qt5/pyt... [2] Specfile diff to KDE:Qt5/python3-pyside2: https://susepaste.org/46295412 [3] https://build.opensuse.org/package/show/home:cgiboudeaux:Qt6/python-pyside6
Hello Ben, Am Freitag, 14. Mai 2021, 22:00:13 CEST schrieb Ben Greiner:
Am 13.05.21 um 19:49 schrieb Axel Braun:
I noticed that build-flavours python36/38/39-pyside2 are missing in TW. python3-pyside2 is obviously not considered sufficient (means, build targets of a singlespec python package are 'unresolveable').
Do I need to change the singlespec, or is pyside2 being adjusted?
Do you have a package which really needs PySide2 and cannot use PyQt5 for those flavors? When it is an alternative supported by a package, it often is added as a suggestion to the python3 flavor, but generally there is not a hard runtime requirement.
To me it looks that onionshare 2.3.1 is asking for pyside2: https://build.opensuse.org/package/show/ home:DocB:branches:devel:languages:python/python-onionshare
It is possible to change python3-pyside2 to singlespec python-pyside2 [1, 2].
Hm, it would probably be better to have the flavours build - what do you suggest? Cheers Axel
But I am not sure if the Qt5 maintainers are very fond of such a change. And I would not submit it without further changes. I am particularly unhappy about the re-install hack to circumvent Qt's supposedly buggy setup.py install behavior: * Some of the devel tools entry-points are lost, e.g. pyside2-designer. * The egg-info for the installed modules is lost. This could prevent loading PySide2 for downstream packages with entry-points.
PySide6 as being prepared by Christophe [3] is also python3 only at the moment.
Thanks Axel
Cheers, Ben
[1] https://build.opensuse.org/package/show/home:bnavigator:branches:KDE:Qt5/pyt hon-pyside2 [2] Specfile diff to KDE:Qt5/python3-pyside2: https://susepaste.org/46295412 [3] https://build.opensuse.org/package/show/home:cgiboudeaux:Qt6/python-pyside6
Am 15.05.21 um 12:40 schrieb Axel Braun:
Hello Ben,
Am Freitag, 14. Mai 2021, 22:00:13 CEST schrieb Ben Greiner:
Am 13.05.21 um 19:49 schrieb Axel Braun:
To me it looks that onionshare 2.3.1 is asking for pyside2: https://build.opensuse.org/package/show > home:DocB:branches:devel:languages:python/python-onionshare
Ok. But even setting PySide2 aside, you will run into problems for your multiflavor package because you will have conflicts for your desktop file and icon. Very much the same problem as [1]. So why force multiflavor for this "app"? Does anything use the desktop part of onionshare as importable? Not even the cli part does it.
It is possible to change python3-pyside2 to singlespec python-pyside2 [1, 2].
Hm, it would probably be better to have the flavours build - what do you suggest?
Let's hear from the Qt maintainers. Ben [1] https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org/thread...
Hello, On Saturday, 15 May 2021 12:40:48 CEST Axel Braun wrote:
Hello Ben,
Am Freitag, 14. Mai 2021, 22:00:13 CEST schrieb Ben Greiner:
Am 13.05.21 um 19:49 schrieb Axel Braun:
I noticed that build-flavours python36/38/39-pyside2 are missing in TW. python3-pyside2 is obviously not considered sufficient (means, build targets of a singlespec python package are 'unresolveable').
Do I need to change the singlespec, or is pyside2 being adjusted?
Do you have a package which really needs PySide2 and cannot use PyQt5 for those flavors? When it is an alternative supported by a package, it often is added as a suggestion to the python3 flavor, but generally there is not a hard runtime requirement.
To me it looks that onionshare 2.3.1 is asking for pyside2: https://build.opensuse.org/package/show/ home:DocB:branches:devel:languages:python/python-onionshare
It is possible to change python3-pyside2 to singlespec python-pyside2 [1, 2].
Hm, it would probably be better to have the flavours build - what do you suggest?
Why? do you really want to install and run 3 onionshare packages using different python versions? Offering different pyside flavors means using more build resources without real benefit. I doubt the FreeCAD maintainers are interested in flavors. (the other user in factory is python38-enaml) Christophe
Am 15.05.21 um 14:06 schrieb Christophe Giboudeaux:
Hello,
...
Offering different pyside flavors means using more build resources without real benefit. I doubt the FreeCAD maintainers are interested in flavors.
(the other user in factory is python38-enaml)
While python36-enaml and python39-enaml don't use it: %if "%{python_flavor}" == "python3" || "%{python_provides}" == "python3" # pyside is python3 only Requires: (%python_flavor-qt5 or python3-pyside2) %else Requires: python-qt5 %endif ... and whether pyside really works is not tested during build time. Ben
Hello Christophe, Am Samstag, 15. Mai 2021, 14:06:13 CEST schrieb Christophe Giboudeaux: ....
It is possible to change python3-pyside2 to singlespec python-pyside2 [1, 2].
Hm, it would probably be better to have the flavours build - what do you suggest?
Why? do you really want to install and run 3 onionshare packages using different python versions?
No, this multi-flavour stuff was not my idea or preference. I'm fine if it runs with the 'current' python3
participants (3)
-
Axel Braun -
Ben Greiner -
Christophe Giboudeaux