python-h5io fails to build with Python 3.13.0a4. =================================== FAILURES =================================== ___________________________ test_state_with_pathlib ____________________________ h5io/tests/test_io.py:415: in test_state_with_pathlib path_obj_reload = read_hdf5( h5io/_h5io.py:529: in read_hdf5 return _read(fid) h5io/_h5io.py:523: in _read return _triage_read(fid[title], slash=slash) h5io/_h5io.py:596: in _triage_read return _setstate( h5io/_h5io.py:944: in _setstate setattr(obj, k, v) E AttributeError: property '_raw_path' of 'PosixPath' object has no setter - generated xml file: /builddir/build/BUILD/h5io-h5io-0.2.2/junit-results.xml -- =========================== short test summary info ============================ SKIPPED [1] h5io/tests/test_io.py:30: could not import 'tables': No module named 'tables' SKIPPED [1] h5io/tests/test_io.py:489: only python3.11 or lower FAILED h5io/tests/test_io.py::test_state_with_pathlib - AttributeError: property '_raw_path' of 'PosixPath' object has no setter =================== 1 failed, 13 passed, 2 skipped in 0.52s ==================== https://docs.python.org/3.13/whatsnew/3.13.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/07033803-python-h5io/ For all our attempts to build python-h5io with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-h5io/ 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.13: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/ Let us know here if you have any questions. Python 3.13 is planned to be included in Fedora 41. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13. 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.
Reported upstream in https://github.com/h5io/h5io/issues/86.
*** Bug 2291727 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.
The one failing test appears to be a real problem, but it’s not clear what the correct fix is, so we might as well unblock dependent packages until upstream figures out what to do (https://github.com/h5io/h5io/issues/86). https://src.fedoraproject.org/rpms/python-h5io/pull-request/9
FEDORA-2024-4ae8ac827d (python-h5io-0.2.3-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ae8ac827d
FEDORA-2024-4ae8ac827d (python-h5io-0.2.3-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.