Bug 2387393

Summary:	Please branch and build for EPEL 10_0
Product:	[Fedora] Fedora EPEL	Reporter:	Noah Mork <bugs.occupy625>
Component:	go-vendor-tools	Assignee:	Maxwell G <maxwell>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	go-sig, maxwell
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	go-vendor-tools-0.8.0-1.el10_0	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-09-08 01:15:11 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:
Bug Blocks:	2387067

Description Noah Mork 2025-08-09 15:15:01 UTC

I saw that go-vendor-tools is now available for EPEL 9 and 10, thanks for that.

Since EPEL 10 now requires builds for each minor release, it would be great if an epel10_0 branch could be created and built as well. This would make the package available across all EL 10 installations.

Appreciate your time and effort on this.

Comment 1 Fedora Update System 2025-08-30 21:45:16 UTC

FEDORA-EPEL-2025-391e7d82f9 (go-vendor-tools-0.8.0-1.el10_0, python-pyzstd-0.16.2-1.el10_0, and 2 more) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-391e7d82f9

Comment 2 Fedora Update System 2025-08-31 02:02:40 UTC

FEDORA-EPEL-2025-391e7d82f9 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-2025-391e7d82f9

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

Comment 3 Fedora Update System 2025-09-08 01:15:11 UTC

FEDORA-EPEL-2025-391e7d82f9 (go-vendor-tools-0.8.0-1.el10_0, python-pyzstd-0.16.2-1.el10_0, and 2 more) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.