Bug 1886164

Summary: Non-responsive maintainer check for noodles
Product: [Fedora] Fedora EPEL Reporter: Robbie Harwood <rharwood>
Component: gangliaAssignee: Nick <nick>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: epel7CC: germano.massullo, jose.p.oliveira.oss, nick, terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ganglia-3.7.2-33.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-23 22:50:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robbie Harwood 2020-10-07 19:05:12 UTC
This bug is part of the non-responsive maintainer procedure for noodles, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

Please respond if you are still active in Fedora and want to maintain your EPEL packages.

Comment 1 Nick 2020-10-07 19:58:17 UTC
Happy to keep going, but the other maintainers took over a lot of what I was doing so I haven't looked at it for a few years.

Comment 2 Germano Massullo 2020-10-07 20:26:03 UTC
I can keep going of course

Comment 3 Nick 2020-10-07 20:41:45 UTC
Oh sorry, this is for Ganglia. Yes I'm happy to let this go, I haven't worked on this in 5+ years.

Comment 4 Robbie Harwood 2020-10-08 17:49:53 UTC
Thanks for replying.  The problem is that you're currently responsible for EPEL branches of a few packages; ganglia is most notable because there are unfixed bugs on it, including two CVEs ( https://bugzilla.redhat.com/show_bug.cgi?id=1790272 and https://bugzilla.redhat.com/show_bug.cgi?id=1790275 ).  If you're not planning to work on it/these, either the EPEL assignee should be change, or the branch should be `fedpkg retire`d ( https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life ).

Comment 5 Germano Massullo 2020-10-08 20:28:59 UTC
(In reply to Robbie Harwood from comment #4)
> Thanks for replying.  The problem is that you're currently responsible for
> EPEL branches of a few packages; ganglia is most notable because there are
> unfixed bugs on it, including two CVEs (
> https://bugzilla.redhat.com/show_bug.cgi?id=1790272 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1790275 ).  If you're not
> planning to work on it/these, either the EPEL assignee should be change, or
> the branch should be `fedpkg retire`d (
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life ).


I will give a quick look to it and see if I can manage to fix the build errors. Otherwise I will retire the EPEL 7 branch since I joined maintainership to maintain EPEL 8

(In reply to Nick from comment #3)
> Oh sorry, this is for Ganglia. Yes I'm happy to let this go, I haven't
> worked on this in 5+ years.

Hi Nick, if you no longer can maintain the package, can you remove yourself from packagers list? So there will be only active maintainers.

Cheers

Comment 6 Nick 2020-10-08 20:35:28 UTC
All good, have done this now. I tried on the old system to remove myself but it wouldn't let me. The new system seems to have worked though.

Nick

Comment 8 Fedora Update System 2020-10-08 22:14:06 UTC
FEDORA-EPEL-2020-fee165c6a2 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fee165c6a2

Comment 9 Fedora Update System 2020-10-09 00:02:53 UTC
FEDORA-EPEL-2020-fee165c6a2 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fee165c6a2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-10-23 22:50:48 UTC
FEDORA-EPEL-2020-fee165c6a2 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.