Bug 2374779 - Please branch and build keepassxc in epel10.0
Summary: Please branch and build keepassxc in epel10.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: keepassxc
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Germano Massullo (Thetra)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-25 16:07 UTC by michel.g.held
Modified: 2025-07-05 01:21 UTC (History)
6 users (show)

Fixed In Version: keepassxc-2.7.10-2.el10_0
Clone Of:
Environment:
Last Closed: 2025-06-25 16:12:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description michel.g.held 2025-06-25 16:07:52 UTC 
Please branch and build keepassxc in epel10.0
Comment 1 Germano Massullo (Thetra) 2025-06-25 16:12:38 UTC 

*** This bug has been marked as a duplicate of bug 2374756 ***
Comment 2 Germano Massullo (Thetra) 2025-06-25 16:13:00 UTC 
excuse me, 10.0 ?
Comment 3 michel.g.held 2025-06-25 16:16:33 UTC 
Yes 10.0. epel10 is built against CentOS Stream 10 epel10.0 against RHEL 10 isn't it?
Comment 4 Fedora Update System 2025-06-26 09:48:06 UTC 
FEDORA-EPEL-2025-0dc3b7322c (keepassxc-2.7.10-2.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0dc3b7322c
Comment 5 Fedora Update System 2025-06-27 02:39:26 UTC 
FEDORA-EPEL-2025-0dc3b7322c 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-0dc3b7322c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2025-07-05 01:21:21 UTC 
FEDORA-EPEL-2025-0dc3b7322c (keepassxc-2.7.10-2.el10_0) has been pushed to the Fedora EPEL 10.0 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.