Bug 2177879

Summary:	Please branch and build libolm in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Troy Dawson <tdawson>
Component:	libolm	Assignee:	Vitaly <vitaly>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	vitaly
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libolm-3.2.14-2.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-18 00:53:46 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:	2177881

Description Troy Dawson 2023-03-13 18:28:37 UTC

Please branch and build libolm in epel9?

If you do not wish to maintain libolm in epel9,
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 on epel;
Please add me (FES: tdawson) through 
https://src.fedoraproject.org/rpms/libolm/adduser

Comment 1 Troy Dawson 2023-03-13 18:32:58 UTC

I have verified that the F37 version of libolm builds without changes on epel9

Comment 2 Fedora Update System 2023-03-15 12:28:50 UTC

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

Comment 3 Fedora Update System 2023-03-16 19:12:29 UTC

FEDORA-EPEL-2023-a5f70c4315 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-2023-a5f70c4315

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

Comment 4 Fedora Update System 2023-03-18 00:53:46 UTC

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