Bug 2092190

Summary: Please build libiodbc for EPEL9
Product: [Fedora] Fedora EPEL Reporter: Orion Poplawski <orion>
Component: libiodbcAssignee: Rex Dieter <rdieter>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: carl, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libiodbc-3.52.15-2.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-29 18:52:47 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: 2135580    

Description Orion Poplawski 2022-06-01 03:50:39 UTC
Please build libiodbc for EPEL9.  Needed for glpk.  Thank you.

Comment 1 Carl George 🤠 2022-07-17 20:00:49 UTC
This is also needed for rnnoise, which is needed for mumble.

If you do not wish to maintain libiodbc in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package.  Myself and Orion are both members of this group.  Please add the epel-packagers-sig group through

https://src.fedoraproject.org/rpms/libiodbc/addgroup

and grant it commit access, or collaborator access on epel* branches.

Comment 2 Carl George 🤠 2022-07-17 20:03:18 UTC
Correction, this is needed for poco (not rnnoise), which is needed by mumble.

Comment 3 Orion Poplawski 2022-07-25 23:01:49 UTC
Second request for build for to add epel-packagers-sig to the package.  Thanks.

Comment 4 Carl George 🤠 2022-10-17 20:58:43 UTC
I've requested [0] access for the EPEL Packagers SIG via the stalled request process [1].  That was completed and now I've requested the epel9 branch [2].

[0] https://pagure.io/releng/issue/11090
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests
[2] https://pagure.io/releng/fedora-scm-requests/issue/48301

Comment 5 Fedora Update System 2022-10-18 00:35:37 UTC
FEDORA-EPEL-2022-e415a3fd93 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e415a3fd93

Comment 6 Fedora Update System 2022-10-18 13:50:23 UTC
FEDORA-EPEL-2022-e415a3fd93 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-e415a3fd93

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

Comment 7 Fedora Update System 2022-10-19 09:22:11 UTC
FEDORA-EPEL-2022-e415a3fd93 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-e415a3fd93

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

Comment 8 Fedora Update System 2022-10-22 15:11:11 UTC
FEDORA-EPEL-2022-e415a3fd93 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-e415a3fd93

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

Comment 9 Fedora Update System 2022-10-29 18:52:47 UTC
FEDORA-EPEL-2022-e415a3fd93 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.