Bug 2309215 - Please branch and build perl-asa for EPEL 10
Summary: Please branch and build perl-asa for EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-asa
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-02 16:09 UTC by Xavier Bachelot
Modified: 2024-09-05 04:06 UTC (History)
2 users (show)

Fixed In Version: perl-asa-1.04-18.el10_0
Clone Of:
Environment:
Last Closed: 2024-09-05 04:06:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2024-09-02 16:09:25 UTC 
Hi,

Could you please branch and build perl-asa for EPEL 10 ?
I would need it to build another package.

If you don't want or have time to maintain this package in EPEL, I'd be glad
to be added to the package so I can take care of it.
Indeed, I can help with maintaining this in Fedora too.
My FAS username is xavierb.

Regards,
Xavier
Comment 1 Petr Pisar 2024-09-03 07:58:22 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/66263
Comment 2 Fedora Update System 2024-09-03 08:34:02 UTC 
FEDORA-EPEL-2024-2038c9b151 (perl-asa-1.04-18.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-2038c9b151
Comment 3 Fedora Update System 2024-09-04 04:28:32 UTC 
FEDORA-EPEL-2024-2038c9b151 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-2038c9b151

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2024-09-05 04:06:30 UTC 
FEDORA-EPEL-2024-2038c9b151 (perl-asa-1.04-18.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.