Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1301570 - Build perl-Carp-Always for EPEL7
Summary: Build perl-Carp-Always for EPEL7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Carp-Always
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-25 12:06 UTC by Jakub Jedelsky
Modified: 2016-01-29 18:52 UTC (History)
2 users (show)

Fixed In Version: perl-Carp-Always-0.13-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 18:52:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jakub Jedelsky 2016-01-25 12:06:59 UTC 
Please prepare branch and build package perl-Carp-Always for EPEL7.

Thank you.
Comment 1 Fedora Update System 2016-01-25 23:12:24 UTC 
perl-Carp-Always-0.13-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5bfd9fbcc0
Comment 2 Fedora Update System 2016-01-29 07:20:19 UTC 
perl-Carp-Always-0.13-5.el7 has been pushed to the Fedora EPEL 7 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-2016-5bfd9fbcc0
Comment 3 Fedora Update System 2016-01-29 18:52:45 UTC 
perl-Carp-Always-0.13-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, 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.