Bug 2366338 - Please branch and build ragel in epel10
Summary: Please branch and build ragel in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: ragel
Version: epel10
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: JT
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-14 20:49 UTC by bugzilla.redhat.com
Modified: 2025-12-11 10:30 UTC (History)
4 users (show)

Fixed In Version: ragel-7.0.4-8.el10_2
Clone Of:
Environment:
Last Closed: 2025-12-11 10:30:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description bugzilla.redhat.com 2025-05-14 20:49:36 UTC 
Please branch and build ragel in epel10
Comment 1 John Mulligan 2025-06-23 22:41:56 UTC 
Will you be able to branch and build ragel in epel10?
Comment 2 Fedora Admin user for bugzilla script actions 2025-10-03 14:14:11 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 3 JT 2025-10-17 00:58:17 UTC 
Sorry for the delay, I didn't see this BZ. I will work on getting colm and ragel built for epel10.

JT
Comment 4 Fedora Update System 2025-12-02 03:53:06 UTC 
FEDORA-EPEL-2025-c18ed48718 (ragel-7.0.4-8.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c18ed48718
Comment 5 Fedora Update System 2025-12-03 01:46:14 UTC 
FEDORA-EPEL-2025-c18ed48718 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c18ed48718

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2025-12-11 10:30:26 UTC 
FEDORA-EPEL-2025-c18ed48718 (ragel-7.0.4-8.el10_2) has been pushed to the Fedora EPEL 10.2 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.