Bug 2166725 - Please branch and build perl-Email-Valid in epel9.
Summary: Please branch and build perl-Email-Valid in epel9.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Email-Valid
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-02 18:37 UTC by Todd Zullinger
Modified: 2023-02-22 09:24 UTC (History)
4 users (show)

Fixed In Version: perl-Email-Valid-1.203-1.el9
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-22 09:24:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2166718 0 unspecified ASSIGNED git-email fails to install on ELN due to missing dependency 2023-10-04 00:09:53 UTC

Description Todd Zullinger 2023-02-02 18:37:20 UTC
Would you be willing and able to branch and build perl-Email-Valid in epel9?

We use it as a dependency of the git-email subpackage and it was recently reported to us that it is not available for EPEL9 / ELN (rhbz#2166718).

Thanks!

Comment 1 Fedora Update System 2023-02-13 14:54:23 UTC
FEDORA-EPEL-2023-bd0a88b644 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-bd0a88b644

Comment 2 Fedora Update System 2023-02-14 02:42:38 UTC
FEDORA-EPEL-2023-bd0a88b644 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-2023-bd0a88b644

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

Comment 3 Fedora Update System 2023-02-22 09:24:23 UTC
FEDORA-EPEL-2023-bd0a88b644 has been pushed to the Fedora EPEL 9 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.