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/ Your package (python-versioningit) Fails To Install in Fedora 39: can't install python3-versioningit: - nothing provides python(abi) = 3.11 needed by python3-versioningit-2.2.0-1.fc39.noarch - nothing provides python3.11dist(packaging) >= 17.1 needed by python3-versioningit-2.2.0-1.fc39.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-39-x86_64 --config-opts mirrored=False install python3-versioningit P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
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 devel.org if you are unsure how to fix this bug.
Tests fail for test/test_end2end.py: =========================== short test summary info ============================ FAILED test/test_end2end.py::test_end2end[git/added-no-commits-default-tag] FAILED test/test_end2end.py::test_end2end[git/archive-repo-exclude] - Depreca... FAILED test/test_end2end.py::test_end2end[git/archive-repo-match] - Deprecati... FAILED test/test_end2end.py::test_end2end[git/archive-repo-mixed-tags] - Depr... FAILED test/test_end2end.py::test_end2end[git/archive-repo-mixed] - Deprecati... FAILED test/test_end2end.py::test_end2end[git/archive-repo] - DeprecationWarn... FAILED test/test_end2end.py::test_end2end[git/custom-format-dirty] - Deprecat... FAILED test/test_end2end.py::test_end2end[git/custom-format-distance-dirty] FAILED test/test_end2end.py::test_end2end[git/custom-format-distance] - Depre... FAILED test/test_end2end.py::test_end2end[git/custom-method-pkg] - Deprecatio... FAILED test/test_end2end.py::test_end2end[git/custom-method-src] - Deprecatio... FAILED test/test_end2end.py::test_end2end[git/custom-method] - DeprecationWar... FAILED test/test_end2end.py::test_end2end[git/default-tag] - DeprecationWarni... FAILED test/test_end2end.py::test_end2end[git/default-version-onbuild-write] FAILED test/test_end2end.py::test_end2end[git/default-version] - DeprecationW... FAILED test/test_end2end.py::test_end2end[git/detached-exact] - DeprecationWa... FAILED test/test_end2end.py::test_end2end[git/dirty] - DeprecationWarning: Py... FAILED test/test_end2end.py::test_end2end[git/distance-dirty] - DeprecationWa... FAILED test/test_end2end.py::test_end2end[git/distance] - DeprecationWarning:... FAILED test/test_end2end.py::test_end2end[git/exact-annotated] - DeprecationW... FAILED test/test_end2end.py::test_end2end[git/exact] - DeprecationWarning: Py... FAILED test/test_end2end.py::test_end2end[git/exclude] - DeprecationWarning: ... FAILED test/test_end2end.py::test_end2end[git/match] - DeprecationWarning: Py... FAILED test/test_end2end.py::test_end2end[git/onbuild-bases] - DeprecationWar... FAILED test/test_end2end.py::test_end2end[git/onbuild-cfg] - DeprecationWarni... FAILED test/test_end2end.py::test_end2end[git/onbuild-nonidem] - DeprecationW... FAILED test/test_end2end.py::test_end2end[git/onbuild-write-fields] - Depreca... FAILED test/test_end2end.py::test_end2end[git/onbuild-write] - DeprecationWar... FAILED test/test_end2end.py::test_end2end[git/onbuild] - DeprecationWarning: ... FAILED test/test_end2end.py::test_end2end[git/write-encoding] - DeprecationWa... FAILED test/test_end2end.py::test_end2end[git/write-py] - DeprecationWarning:... FAILED test/test_end2end.py::test_end2end[git/write-template] - DeprecationWa... FAILED test/test_end2end.py::test_end2end[git/write-txt] - DeprecationWarning... FAILED test/test_end2end.py::test_end2end[hg/added-no-commits-default-tag] - ... FAILED test/test_end2end.py::test_end2end[hg/default-tag] - DeprecationWarnin... FAILED test/test_end2end.py::test_end2end[hg/dirty] - DeprecationWarning: Pyt... FAILED test/test_end2end.py::test_end2end[hg/distance-dirty] - DeprecationWar... FAILED test/test_end2end.py::test_end2end[hg/distance] - DeprecationWarning: ... FAILED test/test_end2end.py::test_end2end[hg/exact] - DeprecationWarning: Pyt... FAILED test/test_end2end.py::test_end2end[hg/multi-tag] - DeprecationWarning:... FAILED test/test_end2end.py::test_end2end[hg/pattern] - DeprecationWarning: P... FAILED test/test_end2end.py::test_end2end[archives/git-archive-distance] - De... FAILED test/test_end2end.py::test_end2end[archives/git-archive-exact] - Depre... FAILED test/test_end2end.py::test_end2end[archives/hg-archive-default-tag] - ... FAILED test/test_end2end.py::test_end2end[archives/hg-archive-distance] - Dep... FAILED test/test_end2end.py::test_end2end[archives/hg-archive-exact] - Deprec... FAILED test/test_end2end.py::test_end2end_no_versioningit - DeprecationWarnin... FAILED test/test_end2end.py::test_end2end_no_pyproject - DeprecationWarning: ... FAILED test/test_end2end.py::test_build_from_sdist - DeprecationWarning: Pyth... FAILED test/test_end2end.py::test_setup_py - DeprecationWarning: Python 3.14 ... ===== 50 failed, 436 passed, 4 skipped, 2 deselected in 157.07s (0:02:37) ====== Also: !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer, pypa/build or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !!
(In reply to Sandro from comment #2) > Tests fail for test/test_end2end.py: > [...] > FAILED test/test_end2end.py::test_setup_py - DeprecationWarning: Python 3.14 > ... > ===== 50 failed, 436 passed, 4 skipped, 2 deselected in 157.07s (0:02:37) > ====== We should make whatever adjustment is necessary to avoid treating all these DeprecationWarnings as errors. Like a blanket -Werror, this makes sense to get early warning of future issues in upstream CI but is, in my opinion, too strict for downstream builds. We can still report the DeprecationWarning upstream if we like. They are all of the form: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. > Also: > > !! > > > ***************************************************************************** > *** > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer, pypa/build or > other standards-based tools. > > Follow the current Python packaging guidelines when building > Python RPM packages. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > and > https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for > details. > > ***************************************************************************** > *** > > !! One of the tests is explicitly checking that the package works correctly when run via setup.py. We could skip the test to silence the warning, but I think in this case it’s better to ignore it. There’s nothing wrong with testing a deprecated practice.
FEDORA-2023-7d2f85b453 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d2f85b453
FEDORA-2023-7d2f85b453 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.