Bug 2309222

Summary:	Please branch and build perl-GD for EPEL 10
Product:	[Fedora] Fedora EPEL	Reporter:	Xavier Bachelot <xavier>
Component:	perl-GD	Assignee:	Tom "spot" Callaway <spotrh>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	paul, perl-devel, spotrh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-GD-2.83-1.el10_0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-09-06 04:52:10 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:	2308891
Bug Blocks:	2303880, 2308859

Description Xavier Bachelot 2024-09-02 16:10:06 UTC

Hi,

Could you please branch and build perl-GD for EPEL 10 ?
I would need it to build another package.

If you don't want or have time to maintain this package in EPEL, I'd be glad
to be added to the package so I can take care of it.
Indeed, I can help with maintaining this in Fedora too.
My FAS username is xavierb.

Regards,
Xavier

Comment 1 Fedora Update System 2024-09-04 17:18:07 UTC

FEDORA-EPEL-2024-03a61c20f7 (perl-GD-2.83-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-03a61c20f7

Comment 2 Fedora Update System 2024-09-05 04:20:22 UTC

FEDORA-EPEL-2024-03a61c20f7 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-03a61c20f7

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

Comment 3 Fedora Update System 2024-09-06 04:52:10 UTC

FEDORA-EPEL-2024-03a61c20f7 (perl-GD-2.83-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.