Hi all,
In July 2021 I retired the FindBugs packages from Fedora:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
This included the findbugs-bcel package, which was an old snapshot of Apache Commons BCEL packaged for use by FindBugs. findbugs-bcel is still present in EPEL 7, but has just had a CVE bug filed against it:
https://bugzilla.redhat.com/show_bug.cgi?id=2142726
Rather than attempt to address this vulnerability, and since FindBugs was never packaged for EPEL 7, I intend to retire findbugs-bcel from EPEL 7.
As per the EPEL Package Retirement guidelines (https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/), I'm sending this email to announce my proposal to retire it.
According to repoquery, no other packages depend on findbugs-bcel.
Regards,
Richard
On Sun, 27 Nov 2022 at 14:32, Richard Fearn richardfearn@gmail.com wrote:
Hi all,
In July 2021 I retired the FindBugs packages from Fedora:
Thanks for announcing the retirement and giving a good example for how people should do so in the future.
It looks like the next step is to get this on the agenda for the EPEL Steering Committee meeting.
Should I create a ticket here? https://pagure.io/epel/issues
Regards,
Richard
Yes, and if you can, tag it with "meeting" If it doesn't let you tag it with meeting, let me know and I'll do it.
On Fri, Dec 2, 2022 at 11:49 AM Richard Fearn richardfearn@gmail.com wrote:
It looks like the next step is to get this on the agenda for the EPEL Steering Committee meeting.
Should I create a ticket here? https://pagure.io/epel/issues
Regards,
Richard
-- Richard Fearn richardfearn@gmail.com _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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/epel-devel@lists.fedoraproject... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hi Troy,
Please add the meeting tag - I can't see a way to do it.
https://pagure.io/epel/issue/210
Thanks!
Richard
On Fri, 2 Dec 2022 at 21:21, Troy Dawson tdawson@redhat.com wrote:
Yes, and if you can, tag it with "meeting" If it doesn't let you tag it with meeting, let me know and I'll do it.
On Fri, Dec 2, 2022 at 11:49 AM Richard Fearn richardfearn@gmail.com wrote:
It looks like the next step is to get this on the agenda for the EPEL Steering Committee meeting.
Should I create a ticket here? https://pagure.io/epel/issues
Regards,
Richard
-- Richard Fearn richardfearn@gmail.com _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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/epel-devel@lists.fedoraproject... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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/epel-devel@lists.fedoraproject... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
epel-devel@lists.fedoraproject.org