Bug 2346399

Summary:	tomlplusplus: Please branch and build for epel10
Product:	[Fedora] Fedora EPEL	Reporter:	Neal Gompa <ngompa13>
Component:	tomlplusplus	Assignee:	Felix Wang <topazus>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	topazus
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tomlplusplus-3.4.0-5.el10_1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-01 01:46:00 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:	2346397

Description Neal Gompa 2025-02-18 22:28:59 UTC

Please branch and build tomlplusplus in epel10.

If you do not wish to maintain tomlplusplus in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS ngompa);
please add me through https://src.fedoraproject.org/rpms/tomlplusplus/adduser

Comment 1 Fedora Update System 2025-02-20 07:09:52 UTC

FEDORA-EPEL-2025-18237be0c3 (tomlplusplus-3.4.0-5.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-18237be0c3

Comment 2 Felix Wang 2025-02-20 08:19:32 UTC

I have also added you the admin of the package.

Comment 3 Fedora Update System 2025-02-21 03:16:44 UTC

FEDORA-EPEL-2025-18237be0c3 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-18237be0c3

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

Comment 4 Fedora Update System 2025-03-01 01:46:00 UTC

FEDORA-EPEL-2025-18237be0c3 (tomlplusplus-3.4.0-5.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.