Howdy Python SIG and python-lockfile maintainers,
I recently noticed that pylockfile (packaged as python-lockfile in Fedora and EPEL) is no longer maintained upstream (since 2017).
https://github.com/openstack-archive/pylockfile
I see 10 packages that still (build)require this, so retirement is probably premature, but is anyone opposed to me marking the package as deprecated so that new packages can't (build)require it?
https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packag...
Deprecating a non-leaf package does technically require a FESCo approved Change[1]. Considering the upstream project has been archived since 2017 and deprecated since 2015, I would certainly favor deprecating python-lockfile in Fedora.
[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packag...
On 12/13/22 00:06, Carl George wrote:
Howdy Python SIG and python-lockfile maintainers,
I recently noticed that pylockfile (packaged as python-lockfile in Fedora and EPEL) is no longer maintained upstream (since 2017).
https://github.com/openstack-archive/pylockfile
I see 10 packages that still (build)require this, so retirement is probably premature, but is anyone opposed to me marking the package as deprecated so that new packages can't (build)require it?
https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packag...
On 13. 12. 22 6:06, Carl George wrote:
Howdy Python SIG and python-lockfile maintainers,
I recently noticed that pylockfile (packaged as python-lockfile in Fedora and EPEL) is no longer maintained upstream (since 2017).
https://github.com/openstack-archive/pylockfile
I see 10 packages that still (build)require this, so retirement is probably premature, but is anyone opposed to me marking the package as deprecated so that new packages can't (build)require it?
I'd support such change proposal.
I wanted to get rid of it long ago but poetry requires CacheControl[filecache] and that requires this one.
python-devel@lists.fedoraproject.org