epel

#199 ensure EPEL bugzilla assignees point to valid packagers
Closed: Deferred by carlwgeorge. Opened by dcavalca.

Closed: Deferred
Reopen Issue

dahdi-tools has @jcollie as their BZ gassing for EPEL, so when I filed https://bugzilla.redhat.com/show_bug.cgi?id=2121833 it got assigned to them. They're not actually on the package ACL, so they wouldn't be able to action on the ticket, and they stated they're no longer a packagers in it.

Could we put together a batch job to audit that the EPEL bugzilla assignees are valid? Valid would mean 1) they exist 2) they're a member of the packager group 3) they're on the package ACL with at least collaborator on the EPEL branches

Metadata Update from @carlwgeorge:
- Issue tagged with: meeting

On a related note, I checked for packages that:
- Are orphaned in EPEL but not in Fedora (i.e. the EPEL bugzilla assignee is orphan and the Fedora assignee is not)
- Have EPEL branches which are not retired (i.e. they do not have dead.package files, so they are not blocked in koji and still exist in the repositories)

(This is what @kevin asked for in our last meeting)

I found 111 packages that meet this criteria. Some have multiple active[^1] EPEL branches. It's unclear if these are all unmaintained or if some of the assignees are just set incorrectly.

[^1]: I did not check if the "active" branches were requested but never populated.

I found that I am maintaining a package that has EPEL orphaned.
What happened was the Fedora package was orphaned, which automatically orphans both Fedora and EPEL. Then someone picked up the Fedora package.
But I don't have permissions to change the EPEL orphan state ... so .. I maintain at least one EPEL Orphaned package.
Note: This is rather irritating because I don't get any bug emails. The only reason I know this is because someone pinged me about the package.
Edited by tdawson

So, I think this needs to be more narrow. Packages also have 'watchers' which do NOT need to be packagers and (can be) CC'ed on bugs.

I think if we narrow this to:

  • package has a epel assigneer override
  • that override account is not a packager or not in the admin/commit acls of the package

We should reset the override, or at least warn/notify us

I don't know how to get the list of bugzilla assignee's, but to get the list of package "members" that is listed here:
https://src.fedoraproject.org/extras/pagure_bz.json

I believe it's https://src.fedoraproject.org/extras/pagure_poc.json that you're looking for.

As was said, this is needed in Fedora, not just EPEL.
Someone needs to step forward to actually write this script / program to do this. Putting this on the back burner until someone does.

Metadata Update from @tdawson:
- Issue tagged with: back-burner

Metadata Update from @tdawson:
- Issue untagged with: meeting

As this is needed for Fedora overall, not just EPEL, I don't think this issue is the right place to track the work. Besides, I'm sure this will all get turned on its head when dist-git moves to Forgejo.

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Deferred
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/199

Please continue any further discussion there.
Metadata
None

back-burner

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.