Bug 2359769 - Please branch and build sparsehash in EPEL 10 [NEEDINFO]
Summary: Please branch and build sparsehash in EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: sparsehash
Version: epel10
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-15 14:24 UTC by Ondrej Mosnáček
Modified: 2025-11-15 01:55 UTC (History)
7 users (show)

Fixed In Version: sparsehash-2.0.4-1.el10_2 sparsehash-2.0.4-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-11-15 01:03:55 UTC
Type: Bug
Embargoed:
steve.traylen: needinfo-
steve.traylen: needinfo? (jgrulich)


Attachments (Terms of Use)

Description Ondrej Mosnáček 2025-04-15 14:24:24 UTC
I would like to build strawberry in EPEL 10, but it depends on sparsehash, which is built for EPEL 9, but not yet for EPEL 10.

Comment 1 Steve Traylen 2025-10-03 12:50:22 UTC
Hi I'd like to see this as well.


If you do not wish to maintain sparsehash in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS stevetraylen );
please add me through https://src.fedoraproject.org/rpms/stevetraylen/adduser

Comment 2 Steve Traylen 2025-10-03 13:09:41 UTC
Should have said for EPEL10.0 and 10.1 also.

The current rawhide package builds okay EPEL10.

As does 2.0.4 version here https://src.fedoraproject.org/rpms/sparsehash/pull-request/1

Comment 3 Steve Traylen 2025-10-29 16:13:54 UTC
Will you be able to branch and build sparsehash in epel10?
I would be happy to be a co-maintainer if you do not wish
to build it on epel10 (FAS: stevetraylen).

Comment 4 Steve Traylen 2025-11-06 09:24:13 UTC
https://pagure.io/releng/issue/13068

Comment 5 Fedora Update System 2025-11-06 14:14:43 UTC
FEDORA-EPEL-2025-2eca9a7e8b (sparsehash-2.0.4-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2eca9a7e8b

Comment 6 Fedora Update System 2025-11-06 14:14:43 UTC
FEDORA-EPEL-2025-fedb25fef9 (sparsehash-2.0.4-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fedb25fef9

Comment 7 Fedora Admin user for bugzilla script actions 2025-11-06 16:56:29 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 8 Fedora Update System 2025-11-07 02:23:16 UTC
FEDORA-EPEL-2025-fedb25fef9 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-fedb25fef9

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

Comment 9 Fedora Update System 2025-11-07 03:22:05 UTC
FEDORA-EPEL-2025-cb94da7b46 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-cb94da7b46

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

Comment 10 Fedora Update System 2025-11-07 03:30:46 UTC
FEDORA-EPEL-2025-2eca9a7e8b has been pushed to the Fedora EPEL 10.0 testing repository.

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

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

Comment 11 Fedora Update System 2025-11-15 01:03:55 UTC
FEDORA-EPEL-2025-fedb25fef9 (sparsehash-2.0.4-1.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.

Comment 12 Fedora Update System 2025-11-15 01:55:04 UTC
FEDORA-EPEL-2025-cb94da7b46 (sparsehash-2.0.4-1.el10_1) has been pushed to the Fedora EPEL 10.1 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.