Bug 2394387 - maintenance of python-nagiosplugin for EPEL
Summary: maintenance of python-nagiosplugin for EPEL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-nagiosplugin
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ali Erdinc Koroglu
QA Contact:
URL:
Whiteboard:
: 2370428 (view as bug list)
Depends On:
Blocks: 2418667
TreeView+ depends on / blocked
 
Reported: 2025-09-10 14:13 UTC by Dave Love
Modified: 2026-05-21 04:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-01-16 16:48:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Love 2025-09-10 14:13:16 UTC
As python-nagiosplugin is orphaned in EPEL, could you add me as maintainer for EPEL to branch and build it for plugin dependencies in EPEL 10 which I and others want?  My FAS username is loveshack.  Thanks.

Reproducible: Always

Comment 1 Dave Love 2025-09-10 14:15:19 UTC
*** Bug 2370428 has been marked as a duplicate of this bug. ***

Comment 2 ava robinson 2025-09-13 06:04:49 UTC
Hi, Join the packager group if you are not already a member. The process for this is detailed in the Fedora documentation on becoming a package maintainer. File an "Orphaned Package" ticket in Bugzilla for the python-nagiosplugin package. This is the official way to declare your intent to adopt it. Announce your intent to the epel-devel mailing list. This is a crucial step to ensure the community is aware of your plans and can provide feedback or assistance. Claim the package in the Fedora Git repository. The Fedora documentation provides a fedpkg command for this purpose. https://www.my-wisely.org

Comment 3 Dave Love 2025-09-15 10:50:03 UTC
It's only orphaned for EPEL. I took advice from the devel list with a pointer to the maintainer doc.

Comment 4 Dave Love 2025-10-14 17:09:41 UTC
I should have chased this.

Will you be able to branch and build python-nagiosplugin in epel10?
I would be happy to be a co-maintainer if you do not wish
to build it on epel10 (FAS: loveshack).

Comment 5 Till Hofmann 2025-12-09 18:35:51 UTC
I'd be happy to help maintaining the EPEL branch.

Comment 6 Till Hofmann 2025-12-09 18:39:09 UTC
Dave, I guess you could continue with the stalled EPEL request procedure: https://docs.fedoraproject.org/en-US/epel/epel-package-request/#stalled_epel_requests

Comment 7 Till Hofmann 2026-01-04 15:23:45 UTC
I have created a releng ticket: https://forge.fedoraproject.org/releng/tickets/issues/13148

Comment 8 Dave Love 2026-01-05 10:48:24 UTC
Thanks.  I'd let it slide, but was going to look up the procedure soon; I didn't see the previous comment for some reason.

Comment 9 Till Hofmann 2026-01-17 07:22:04 UTC
Thanks Dave for doing the rest! For some reason, I was never notified that the releng ticket was closed.

Comment 10 Dave Love 2026-01-20 13:38:27 UTC
I didn't get anything either, after setting myself to watch it, or whatever the term was.

Comment 11 Red Hat Bugzilla 2026-05-21 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked


Note You need to log in before you can comment on or make changes to this bug.