Bug 2394954 - rubygem-cucumber: please provide epel10 package
Summary: rubygem-cucumber: please provide epel10 package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-cucumber
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2387070
TreeView+ depends on / blocked
 
Reported: 2025-09-13 14:37 UTC by Denis Fateyev
Modified: 2025-09-25 19:07 UTC (History)
4 users (show)

Fixed In Version: rubygem-cucumber-7.1.0-14.el10_2 rubygem-cucumber-7.1.0-14.el10_1
Clone Of:
Environment:
Last Closed: 2025-09-25 00:23:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Denis Fateyev 2025-09-13 14:37:55 UTC
Description of problem:
Please provide "rubygem-cucumber" package in EPEL10.

Comment 1 Troy Dawson 2025-09-15 13:31:17 UTC
To build rubygem-cucumber we need the following rubygems in epel10

rubygem-aruba
rubygem-builder
rubygem-cucumber-core
rubygem-cucumber-create-meta
rubygem-cucumber-wire
rubygem-mime-types
rubygem-multi_test

I am the EPEL maintainer for all of those, so that's ok, but I don't remember all of those packages dependencies.
This is going to take a few days to work through them all, possibly longer if I don't own all of the dependencies dependencies.

Comment 2 Denis Fateyev 2025-09-15 17:38:08 UTC
Thanks, it's not a high priority task, so take your time.
Users asked me to provide "rubygem-rake-compiler" in epel10, and I stumbled upon unsatisfied 'rubygem(cucumber)' dependency.

Comment 3 Troy Dawson 2025-09-15 18:10:05 UTC
I've finished tracking all the build dependencies, and most of the runtime dependencies.  So far, I own everything, so it shouldn't take me too long.
The hardest part is three circular dependencies.
If I haven't updated this bug by next week, please ping me.
It should only take me a day or two, so if it isn't done by next week, something came up and I'll need a bit of a reminder.

Comment 4 Fedora Update System 2025-09-16 16:18:09 UTC
FEDORA-EPEL-2025-5986a17efd (rubygem-cucumber-7.1.0-14.el10_2, rubygem-cucumber-core-10.1.0-10.el10_2, and 10 more) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5986a17efd

Comment 5 Fedora Update System 2025-09-16 16:18:31 UTC
FEDORA-EPEL-2025-c836ca4d39 (rubygem-cucumber-7.1.0-14.el10_1, rubygem-cucumber-core-10.1.0-10.el10_1, and 10 more) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c836ca4d39

Comment 6 Fedora Update System 2025-09-17 02:25:24 UTC
FEDORA-EPEL-2025-5986a17efd 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-5986a17efd

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

Comment 7 Fedora Update System 2025-09-17 02:39:16 UTC
FEDORA-EPEL-2025-c836ca4d39 has been pushed to the Fedora EPEL 10.1 testing repository.

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

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

Comment 8 Fedora Update System 2025-09-25 00:23:03 UTC
FEDORA-EPEL-2025-5986a17efd (rubygem-cucumber-7.1.0-14.el10_2, rubygem-cucumber-core-10.1.0-10.el10_2, and 10 more) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-09-25 02:11:57 UTC
FEDORA-EPEL-2025-c836ca4d39 (rubygem-cucumber-7.1.0-14.el10_1, rubygem-cucumber-core-10.1.0-10.el10_1, and 10 more) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Denis Fateyev 2025-09-25 19:07:31 UTC
@tdawson, thanks for providing packages!


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