Bug 2108314 - Please branch and build glfw in epel9.
Summary: Please branch and build glfw in epel9.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: glfw
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Till Hofmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-18 20:13 UTC by David Koppelman
Modified: 2022-07-29 01:51 UTC (History)
5 users (show)

Fixed In Version: glfw-3.3.7-2.el9
Clone Of:
Environment:
Last Closed: 2022-07-29 01:51:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Koppelman 2022-07-18 20:13:08 UTC
Description of problem:

GLFW not in epel9, is in epel8.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Fedora Update System 2022-07-20 18:17:17 UTC
FEDORA-EPEL-2022-f4a441c51b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f4a441c51b

Comment 3 Fedora Update System 2022-07-21 01:10:45 UTC
FEDORA-EPEL-2022-f4a441c51b 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-f4a441c51b

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

Comment 4 David Koppelman 2022-07-21 15:39:37 UTC
Thank you Till Hoffmann for handling this quickly! I was able to successfully build using the epel9 epel-testing glfw-devel, but due to an unrelated issue (gdm-password:auth on rhel9) I was not able to test that the built code fully works.

Comment 5 Fedora Update System 2022-07-29 01:51:56 UTC
FEDORA-EPEL-2022-f4a441c51b 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.