Bug 2448052 - add perl-Nmap-Parser package to epel 9 and epel 10
Summary: add perl-Nmap-Parser package to epel 9 and epel 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Nmap-Parser
Version: epel10
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-16 15:23 UTC by Martin VanWinkle
Modified: 2026-03-26 04:13 UTC (History)
3 users (show)

Fixed In Version: perl-Nmap-Parser-1.37-22.el10_3 perl-Nmap-Parser-1.37-22.el10_1 perl-Nmap-Parser-1.37-22.el9 perl-Nmap-Parser-1.37-22.el10_2
Clone Of:
Environment:
Last Closed: 2026-03-26 02:47:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin VanWinkle 2026-03-16 15:23:56 UTC
Please add perl-Nmap-Parser package to epel 9 and epel 10

Comment 1 Fedora Update System 2026-03-17 13:42:28 UTC
FEDORA-EPEL-2026-baa9a68659 (perl-Nmap-Parser-1.37-22.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-baa9a68659

Comment 2 Fedora Update System 2026-03-17 13:42:28 UTC
FEDORA-EPEL-2026-edbaed2458 (perl-Nmap-Parser-1.37-22.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-edbaed2458

Comment 3 Fedora Update System 2026-03-17 13:42:29 UTC
FEDORA-EPEL-2026-0b41586a4d (perl-Nmap-Parser-1.37-22.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-0b41586a4d

Comment 4 Fedora Update System 2026-03-18 01:03:17 UTC
FEDORA-EPEL-2026-edbaed2458 has been pushed to the Fedora EPEL 10.3 testing repository.

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

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

Comment 5 Fedora Update System 2026-03-18 01:19:34 UTC
FEDORA-EPEL-2026-3d5dc202d2 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3d5dc202d2

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

Comment 6 Fedora Update System 2026-03-18 01:25:54 UTC
FEDORA-EPEL-2026-0b41586a4d has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-0b41586a4d

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

Comment 7 Fedora Update System 2026-03-18 01:35:11 UTC
FEDORA-EPEL-2026-baa9a68659 has been pushed to the Fedora EPEL 9 testing repository.

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

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

Comment 8 Fedora Update System 2026-03-26 02:47:00 UTC
FEDORA-EPEL-2026-edbaed2458 (perl-Nmap-Parser-1.37-22.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-03-26 04:05:35 UTC
FEDORA-EPEL-2026-0b41586a4d (perl-Nmap-Parser-1.37-22.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2026-03-26 04:06:30 UTC
FEDORA-EPEL-2026-baa9a68659 (perl-Nmap-Parser-1.37-22.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-03-26 04:13:20 UTC
FEDORA-EPEL-2026-3d5dc202d2 (perl-Nmap-Parser-1.37-22.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.


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