Bug 1755062

Summary: [RFE] EPEL8 branch of perl-Devel-PatchPerl
Product: [Fedora] Fedora Reporter: Pat Riehecky <riehecky>
Component: perl-Devel-PatchPerlAssignee: Jitka Plesnikova <jplesnik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: iarnell, jplesnik, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: perl-Devel-PatchPerl-1.64-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-10 16:14:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pat Riehecky 2019-09-24 16:34:19 UTC
Description of problem:

Can perl-Devel-PatchPerl be branched for EPEL8.  This may be very helpful for multi-perl with modularity (and I'd use it today for some of my local code).


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Fedora Update System 2019-09-25 14:49:25 UTC
FEDORA-EPEL-2019-21d5b9238a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-21d5b9238a

Comment 3 Fedora Update System 2019-09-26 03:57:16 UTC
perl-Devel-PatchPerl-1.64-2.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-21d5b9238a

Comment 4 Fedora Update System 2019-10-10 16:14:05 UTC
perl-Devel-PatchPerl-1.64-2.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.