On Tue, Dec 24, 2024 at 09:15:29AM -0500, Ben Beasley wrote: > I agree with the plan, but I wanted to note that deprecating a package that > other packages depend on requires a FESCo-approved Change[1]. > > (It is weird that the deprecation policy is so much more bureaucratic than > the retirement policy. By comparison, I don’t know of any policy that would > forbid summarily retiring a package that others depend on. It’s a bad > practice, and one might be asked to allow someone else to unretire and > maintain the package if the consequences are bad enough, but I’ve never seen > a blanket policy against it.) > > [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/#_prerequisites_for_deprecation > You're right on both counts - I'll file a Change Proposal later today, and if it did not get accepted I can unmark the package as deprecated later. > I opened PR’s (or in some cases committed directly) to remove the > pytest-runner dependency from the following packages for which I am a direct > or group/SIG co-maintainer, sending PR’s upstream where applicable. > Thank you! Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://fedoraproject.org/wiki/User:Salimma#README -- _______________________________________________ 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
