Bug 2344539 - Please branch and build dropbear in EPEL10
Summary: Please branch and build dropbear in EPEL10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: dropbear
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fedepell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2328890
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-09 12:10 UTC by niklas.baudy
Modified: 2025-06-04 03:53 UTC (History)
4 users (show)

Fixed In Version: dropbear-2025.88-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-06-04 03:53:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description niklas.baudy 2025-02-09 12:10:21 UTC
Please branch and build dropbear in EPEL10

Comment 1 fedepell 2025-02-11 05:25:28 UTC
I wanted to do this, but currently we are missing in EPEL10 libtomcrypt. There is already a bug filled to build it for EPEL10: https://bugzilla.redhat.com/show_bug.cgi?id=2328890
Once that is done, I can try to progress further on this! 

A fast test bundling it inside doesn't show other showstoppers, so hopefully when that is solve we could continue.

Comment 2 Fedora Update System 2025-05-26 03:33:26 UTC
FEDORA-EPEL-2025-12a265935c (dropbear-2025.88-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-12a265935c

Comment 3 Fedora Update System 2025-05-27 02:07:07 UTC
FEDORA-EPEL-2025-12a265935c 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-12a265935c

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

Comment 4 Fedora Update System 2025-06-04 03:53:49 UTC
FEDORA-EPEL-2025-12a265935c (dropbear-2025.88-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.