Bug 2131244 - request epel 9 branch for coin-or-Sample
Summary: request epel 9 branch for coin-or-Sample
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: coin-or-Sample
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio T. sagitter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-30 12:34 UTC by Tom Rix
Modified: 2022-10-11 10:53 UTC (History)
2 users (show)

Fixed In Version: coin-or-Sample-1.2.12-6.el9
Clone Of:
Environment:
Last Closed: 2022-10-11 10:53:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tom Rix 2022-09-30 12:34:05 UTC
Description of problem:
coin-or-CoinUtils BuildRequires coin-or-Sample
https://src.fedoraproject.org/rpms/coin-or-CoinUtils/blob/rawhide/f/coin-or-CoinUtils.spec
See line 18

coin-or-Sample rawhide builds as-is for epel9


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
https://koji.fedoraproject.org/koji/taskinfo?taskID=92433452


Expected results:


Additional info:
Add me to the project if you need help with epel

Comment 1 Fedora Update System 2022-10-03 20:00:07 UTC
FEDORA-EPEL-2022-531374e46a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-531374e46a

Comment 2 Fedora Update System 2022-10-04 02:25:59 UTC
FEDORA-EPEL-2022-531374e46a 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-531374e46a

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

Comment 3 Fedora Update System 2022-10-11 10:53:41 UTC
FEDORA-EPEL-2022-531374e46a has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.