python-pyside2 fails to build with Python 3.10.0a2.
-- Installing: /builddir/build/BUILDROOT/python-pyside2-5.15.1-1.fc34.x86_64/usr/include/PySide2/Qt3DExtras/pyside2_qt3dextras_python.h
-- Installing: /builddir/build/BUILDROOT/python-pyside2-5.15.1-1.fc34.x86_64/usr/share/PySide2/typesystems/typesystem_3dextras.xml
-- Installing: /builddir/build/BUILDROOT/python-pyside2-5.15.1-1.fc34.x86_64/usr/bin/pyside_tool.py
-- Installing: /builddir/build/BUILDROOT/python-pyside2-5.15.1-1.fc34.x86_64/usr/bin/pyside2-lupdate
-- Installing: /builddir/build/BUILDROOT/python-pyside2-5.15.1-1.fc34.x86_64/usr/share/man/man1/pyside2-lupdate.1
/var/tmp/rpm-tmp.ROewav: line 41: popd: directory stack empty
error: Bad exit status from /var/tmp/rpm-tmp.ROewav (%install)
No idea :/
For the build logs, see:
For all our attempts to build python-pyside2 with Python 3.10, see:
Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
Let us know here if you have any questions.
Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
This was part of a workaround for the stupid^H^H^H^H^H cmake change that only got applied to some releases of Fedora/EL instead of all releases. Working on it...
Ok, the popd problem is fixed but then I ran into this:
***** Exception while trying to prepare bdist_wheel override class: cannot import name 'pep425tags' from 'wheel' (/usr/lib/python3.10/site-packages/wheel/__init__.py). Skipping wheel overriding.
Unsupported python version detected. Only these python versions are supported: [(2, 7), (3, 5), (3, 6), (3, 7), (3, 8), (3, 9)]
error: Bad exit status from /var/tmp/rpm-tmp.BixP5u (%install)
Bad exit status from /var/tmp/rpm-tmp.BixP5u (%install)
Apparently there's one more place 3.10 needs to be added.
I updated the patch to include 3.10. Perhaps I did it incorrectly?
@@ -92,6 +92,8 @@ class Config(object):
'Programming Language :: Python :: 3.6',
'Programming Language :: Python :: 3.7',
'Programming Language :: Python :: 3.8',
+ 'Programming Language :: Python :: 3.9',
+ 'Programming Language :: Python :: 3.10',
self.setup_script_dir = None
@@ -134,7 +135,7 @@ class Config(object):
setup_kwargs['zip_safe'] = False
setup_kwargs['cmdclass'] = cmd_class_dict
setup_kwargs['version'] = package_version
- setup_kwargs['python_requires'] = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, <3.9"
+ setup_kwargs['python_requires'] = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, <=3.10"
Forgot I had disabled the patch because a newer version supported Python 3.9. The patch has now been updated for 3.10 and I was able to complete a build from the referenced mock configuration.
I have pushed the changes into master.