Bug 1870769 (perl-Text-RecordParser-epel8)

Summary: EPEL8 Branch Request: perl-Text-RecordParser
Product: [Fedora] Fedora Reporter: Igor Raits <igor.raits>
Component: perl-Text-RecordParserAssignee: Emmanuel Seyman <emmanuel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: emmanuel, iarnell, perl-devel, tremble
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Text-RecordParser-1.6.5-18.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-07 16:29:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1870774    
Bug Blocks: 1870763    

Description Igor Raits 2020-08-20 17:41:02 UTC
I would appreciate if you could build perl-Text-RecordParser for EPEL8. I've checked that master branch builds fine there and according to my testing works. Feel free to add me as co-maintainer. This package and its dependencies are built in https://copr.fedorainfracloud.org/coprs/ignatenkobrain/gdc/packages/.

Comment 2 Fedora Update System 2020-08-23 13:41:14 UTC
FEDORA-EPEL-2020-ce2752c158 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ce2752c158

Comment 3 Fedora Update System 2020-08-24 01:30:49 UTC
FEDORA-EPEL-2020-ce2752c158 has been pushed to the Fedora EPEL 8 testing repository.

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

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

Comment 4 Fedora Update System 2020-09-07 16:29:28 UTC
FEDORA-EPEL-2020-ce2752c158 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.