python-gphoto2 fails to build with Python 3.14.0b1. + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' /builddir/build/BUILD/python-gphoto2-2.0.0-build/gphoto2-2.0.0/setup.py:77: SyntaxWarning: "\d" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\d"? A raw string is also an option. match = re.match(mod_src_dir + '-gp(\d+\.\d+\.\d+)', name) /builddir/build/BUILD/python-gphoto2-2.0.0-build/gphoto2-2.0.0/setup.py:117: SyntaxWarning: "\d" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\d"? A raw string is also an option. match = re.match('libgphoto2-(\d+\.\d+\.\d+)', name) /builddir/build/BUILD/python-gphoto2-2.0.0-build/gphoto2-2.0.0/setup.py:169: SyntaxWarning: "\(" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\("? A raw string is also an option. for match in re.finditer('%feature\("docstring"\) (\w+) \"(.+?)\";', Traceback (most recent call last): File "/builddir/build/BUILD/python-gphoto2-2.0.0-build/gphoto2-2.0.0/setup.py", line 22, in <module> from distutils.command.upload import upload as _upload ModuleNotFoundError: No module named 'distutils.command.upload' https://docs.python.org/3.14/whatsnew/3.14.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.14-b1/fedora-rawhide-x86_64/09024389-python-gphoto2/ For all our attempts to build python-gphoto2 with Python 3.14, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.14-b1/package/python-gphoto2/ 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.14: https://copr.fedorainfracloud.org/coprs/g/python/python3.14-b1/ Let us know here if you have any questions. Python 3.14 is planned to be included in Fedora 43. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14. 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.
*** Bug 2371930 has been marked as a duplicate of this bug. ***
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/python-gphoto2 by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.
Automation has figured out the package is retired in rawhide. If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days