Hi all, With this Change Proposal having been approved by FESCo: https://fedoraproject.org/wiki/Changes/Retire_PyO3_v0.19,_v0.20,_and_v0.21 I am putting things in motion for the retirement of all packages for PyO3 v0.19, v0.20, and v0.21. Three of the five packages that were listed as affected when I filed the Change Proposal were already updated and / or had patches backported for supporting PyO3 >= 0.22, there are only two affected packages left, for which I just submitted PRs to move to PyO3 >= 0.22 as well: - pyo3 v0.19: python-pendulum: https://src.fedoraproject.org/rpms/python-pendulum/pull-request/6 - pyo3 v0.20: python-libcst: https://src.fedoraproject.org/rpms/python-libcst/pull-request/7 Test rebuilds of dependent packages in COPR are all green (except for an i686 specific failure in hypothesis, which is a noarch package and wouldn't be built on i686 in koji anyway): https://copr.fedorainfracloud.org/coprs/decathorpe/pyo3-bumps/monitor/ I am planning to retire the old PyO3 compat packages in one week, or as soon as the two Pull Requests are merged + built (whichever happens earlier). If there is no response on either of the PRs until then, I would ask package co-maintainers or Python Packagers SIG members to take a look to ensure that the packages don't become FTBFS. Fabio -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
