Bug 1557561

Summary:	Please add: perl-Authen-Radius to EPEL 6
Product:	[Fedora] Fedora EPEL	Reporter:	R P Herrold <herrold>
Component:	perl-Authen-Radius	Assignee:	Paul Howarth <paul>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	andreas, extras-qa, paul, perl-devel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-Authen-Radius-0.24-1.el6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1557560	Environment:
Last Closed:	2018-04-05 11:42:33 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:
Bug Depends On:	1557560
Bug Blocks:

Description R P Herrold 2018-03-16 21:39:33 UTC

+++ This bug was initially created as a clone of Bug #1557560 +++

any version is fine .. I have a BR on the path to a fresh / updated Bugzilla, which needs it in EPEL 6

and this package as well

it is blocked by #1557560

Comment 1 Fedora Update System 2018-03-19 13:54:33 UTC

perl-Authen-Radius-0.24-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-648849bf40

Comment 2 Fedora Update System 2018-03-19 18:32:44 UTC

perl-Authen-Radius-0.24-1.el6 has been pushed to the Fedora EPEL 6 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-2018-648849bf40

Comment 3 R P Herrold 2018-03-22 20:17:35 UTC

I added positive karma -- thank you

Comment 4 Fedora Update System 2018-04-05 11:42:33 UTC

perl-Authen-Radius-0.24-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.