Bug 2031492

Summary:	branch request: perl-Data-MessagePack for epel8
Product:	[Fedora] Fedora EPEL	Reporter:	Saad <s.munir>
Component:	perl-Data-MessagePack	Assignee:	Jitka Plesnikova <jplesnik>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	perl-devel, s.munir
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	perl-Data-MessagePack-1.01-6.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-23 01:58:22 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 Saad 2021-12-12 11:06:02 UTC

Description of problem:
Can we have this component in EPEL 8? Our product depends upon on this component and without this in being EPEL 8, our release for RHEL 8 would be difficult.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jitka Plesnikova 2021-12-12 17:47:28 UTC

https://pagure.io/releng/fedora-scm-requests/issue/39420

Comment 2 Fedora Update System 2021-12-14 07:25:12 UTC

FEDORA-EPEL-2021-50e30ddd6f has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-50e30ddd6f

Comment 3 Fedora Update System 2021-12-15 02:23:34 UTC

FEDORA-EPEL-2021-50e30ddd6f 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-2021-50e30ddd6f

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

Comment 4 Fedora Update System 2021-12-23 01:58:22 UTC

FEDORA-EPEL-2021-50e30ddd6f has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.