Dear package maintainer, this bugzilla is automated becasue the number of impacted packages it too high to go trough manually. It appears that your package failed to build with setuptools 74.1.3 and wheel 0.44 in https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-74/package/python-cliff/ While it succeeded with setuptools 69.2.0 and wheel 0.43 in https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-control/package/python-cliff/ This usually means this package fails to build with setuptools 74+ We plan to update setuptools to version 74 or newer in Fedora 42. This is an approved Fedora 42 Change: https://fedoraproject.org/wiki/Changes/Setuptools_74+ Please analyze the failure and fix it in rawhide. Thanks. You can use the builds from the churchyard/setuptools-74 copr for local testing. mock -r fedora-rawhide-x86_64 --addrepo 'https://download.copr.fedorainfracloud.org/results/churchyard/setuptools-74/fedora-rawhide-$basearch/' One of the most common problems is that the setup.py test command cannot be used. If that is the case here, run the tests in %check differently, e.g. via %pytest, %tox, %{python3} -m unittest, etc. If you need help, reach out to me in this bugzilla.
I plan to update setuptools to 74.x in rawhide this week. At that point, this package will fail to build from source if not fixed.
So, I took a look... it's the tests that are not happy with new setuptools. I tried switching to pytest, but that gets: =========================== short test summary info ============================ FAILED cliff/tests/test_commandmanager.py::TestLookupAndFind::test - Failed: ... FAILED cliff/tests/test_commandmanager.py::TestLookupWithRemainder::test - Fa... FAILED cliff/tests/test_commandmanager.py::TestFindInvalidCommand::test - Fai... FAILED cliff/tests/test_commandmanager.py::TestLookupAndFindPartialName::test ================== 4 failed, 201 passed, 13 warnings in 0.69s ================== tox works great if you let it use stestr... but thats undesired due to the circular dependency. Totals ====== Ran: 212 tests in 0.1661 sec. - Passed: 212 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 0 Sum of execute time for each test: 0.7714 sec.
I had a package with similar pytest failures, and switching to just unittest works. Worth a try?
Doesn't seem to help here... it uses tox, we just want to not test the way it's setup to test. I guess we could make our own tox env, but I am not sure what it would look like.
%check # stestr depends on cliff which introduces cyclic dep so i'm avoiding stestr. -PYTHON=python3 python3 setup.py test +%{python3} -m unittest + /usr/bin/python3 -m unittest .................................................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 212 tests in 0.205s OK
Ah ha. Stupidly I was doing: %{python3} -m unittest test/test-*.py for some reason. ;( That seems to work. Will push that fix. Thank you.
FEDORA-2024-dfa81e2f10 (python-cliff-4.7.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-dfa81e2f10
FEDORA-2024-dfa81e2f10 (python-cliff-4.7.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.