Bug 2031221

Summary:	zimg for EPEL 9
Product:	[Fedora] Fedora EPEL	Reporter:	Xavier Bachelot <xavier>
Component:	zimg	Assignee:	Simone Caronni <negativo17>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	kwizart, negativo17
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	zimg-3.0.3-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-11 13:43:17 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 Xavier Bachelot 2021-12-10 19:07:53 UTC

Hi,

Could you please branch and build zimg for EPEL 9 ?

Regards,
Xavier

Comment 1 Xavier Bachelot 2022-02-23 22:19:53 UTC

*** Bug 2057585 has been marked as a duplicate of this bug. ***

Comment 2 Xavier Bachelot 2022-02-25 17:26:16 UTC

Hi Simone,

Will you be able to branch and build zimg for EPEL 9 ?

Regards,
Xavier

Comment 3 Simone Caronni 2022-03-02 07:21:06 UTC

Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/42654

Comment 4 Fedora Update System 2022-03-02 20:18:20 UTC

FEDORA-EPEL-2022-a8ae1aea0d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a8ae1aea0d

Comment 5 Fedora Update System 2022-03-03 16:49:45 UTC

FEDORA-EPEL-2022-a8ae1aea0d has been pushed to the Fedora EPEL 9 testing repository.

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

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

Comment 6 Fedora Update System 2022-03-11 13:43:17 UTC

FEDORA-EPEL-2022-a8ae1aea0d has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.