Bug 2387067 - Please branch and build to EPEL10_0
Summary: Please branch and build to EPEL10_0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: restic
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikel Olasagasti Uranga
QA Contact:
URL:
Whiteboard:
Depends On: 2387393
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-08-07 13:55 UTC by Noah Mork
Modified: 2025-09-17 02:00 UTC (History)
2 users (show)

Fixed In Version: restic-0.18.0-4.el10_0
Clone Of:
Environment:
Last Closed: 2025-09-17 02:00:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Noah Mork 2025-08-07 13:55:26 UTC
I noticed that you've built and branched restic for EPEL 10, thank you for your work on that.

Since EPEL 10 now requires builds per minor version, restic currently isn’t available for EL 10.0 through EPEL. Would it be possible for you to also create and build an epel10_0 branch to ensure availability across all EL 10 systems?

Thanks in advance for considering this.

Comment 1 Mikel Olasagasti Uranga 2025-08-08 22:21:15 UTC
`go-vendor-tools` is not available for EPEL10_0 yet, so once it lands there I'll build restic.

Comment 2 Fedora Update System 2025-09-08 07:45:09 UTC
FEDORA-EPEL-2025-dafe56873e (restic-0.18.0-4.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-dafe56873e

Comment 3 Fedora Update System 2025-09-09 02:23:06 UTC
FEDORA-EPEL-2025-dafe56873e 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-dafe56873e

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

Comment 4 Fedora Update System 2025-09-17 02:00:15 UTC
FEDORA-EPEL-2025-dafe56873e (restic-0.18.0-4.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.