Bug 2264874

Summary: Request EPEL 9
Product: [Fedora] Fedora Reporter: Tom Rix <trix>
Component: onnxAssignee: Diego Herrera <dherrera>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: a.alvarezayllon, dherrera
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: onnx-1.14.1-2.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-06 02:34:26 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:

Description Tom Rix 2024-02-19 12:50:16 UTC
I am building python-torch for epel 9.
It depends on onnx-devel here
https://src.fedoraproject.org/rpms/python-torch/blob/rawhide/f/python-torch.spec#_122

A local build of the onnx rawhide branch on cs9 succeeded without any issues.
Can an official epel9 branch be created ?

I can help maintain the epel side if you need help.
I am doing this for several of my own packages and it is no big deal for me to take one more.  

Reproducible: Always

Comment 1 Fedora Update System 2024-02-26 20:09:36 UTC
FEDORA-EPEL-2024-b338e53868 (onnx-1.14.1-2.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b338e53868

Comment 2 Fedora Update System 2024-02-27 01:33:30 UTC
FEDORA-EPEL-2024-b338e53868 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-2024-b338e53868

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

Comment 3 Tom Rix 2024-02-28 20:40:50 UTC
Looks good to me
Thanks!

Comment 4 Fedora Update System 2024-03-06 02:34:26 UTC
FEDORA-EPEL-2024-b338e53868 (onnx-1.14.1-2.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.