Bug 2330107 - perl-File-Next: add to EPEL 10
Summary: perl-File-Next: add to EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-File-Next
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2330106
TreeView+ depends on / blocked
 
Reported: 2024-12-03 05:02 UTC by Carl George 🤠
Modified: 2024-12-13 02:23 UTC (History)
2 users (show)

Fixed In Version: perl-File-Next-1.18-17.el10_0
Clone Of:
Environment:
Last Closed: 2024-12-13 02:23:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🤠 2024-12-03 05:02:49 UTC
Description of problem:
Please add perl-File-Next to EPEL 10.  It is a build requirement for ack.


Additional info:
If you do not wish to maintain perl-File-Next in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS carlwgeorge).

Comment 1 Robin Lee 2024-12-03 10:34:01 UTC
OK. Added as admin.

Comment 2 Fedora Update System 2024-12-04 05:17:39 UTC
FEDORA-EPEL-2024-c3839bd84c (ack-3.7.0-6.el10_0 and perl-File-Next-1.18-17.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c3839bd84c

Comment 3 Fedora Update System 2024-12-05 02:08:49 UTC
FEDORA-EPEL-2024-c3839bd84c has been pushed to the Fedora EPEL 10.0 testing repository.

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

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

Comment 4 Fedora Update System 2024-12-13 02:23:44 UTC
FEDORA-EPEL-2024-c3839bd84c (ack-3.7.0-6.el10_0 and perl-File-Next-1.18-17.el10_0) has been pushed to the Fedora EPEL 10.0 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.