Fedora Account System
Red Hat Associate
Red Hat Customer
Please branch and build python-lockfile in epel10. If you do not wish to maintain python-lockfile in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS: neil); please add me through https://src.fedoraproject.org/rpms/python-lockfile/adduser
I have verified that it builds for both epel10.0 and epel10.1 There seems to be some slowness in getting branches made and setup correctly. Otherwise I'd be done by now. If I haven't built this within a week, please ping again. Although I want to built it, sometimes things get in the way and I get distracted.
FEDORA-EPEL-2025-e7453c27bd (python-lockfile-0.12.2-16.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e7453c27bd
FEDORA-EPEL-2025-a6529d610e (python-lockfile-0.12.2-16.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6529d610e
FEDORA-EPEL-2025-e7453c27bd has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e7453c27bd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-a6529d610e has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6529d610e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 2369417 has been marked as a duplicate of this bug. ***
FEDORA-EPEL-2025-e7453c27bd (python-lockfile-0.12.2-16.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-a6529d610e (python-lockfile-0.12.2-16.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.