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-packages/#_prerequisites_for_deprecation
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-packages/
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
