Bug 2364316 - borg - would be great to have it back
Summary: borg - would be great to have it back
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: borgbackup
Version: epel10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Felix Schwarz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-06 06:08 UTC by lejeczek
Modified: 2025-05-22 02:27 UTC (History)
1 user (show)

Fixed In Version: borgbackup-1.4.1-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-05-22 02:27:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description lejeczek 2025-05-06 06:08:13 UTC 
Description of problem:

Thanks, L.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Fedora Update System 2025-05-13 05:57:48 UTC 
FEDORA-EPEL-2025-6179460d5f (borgbackup-1.4.1-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6179460d5f
Comment 2 Felix Schwarz 2025-05-13 06:03:48 UTC 
I did not push this initially because RHEL 10 is not out and I wanted to see if borg 2 is closer to release once RHEL 10 is released because we can not easily upgrade borg once it is in EPEL. However borg 2 will still take a while so I pushed the current version to EPEL 10 :-)
Comment 3 Fedora Update System 2025-05-14 02:15:40 UTC 
FEDORA-EPEL-2025-6179460d5f 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-6179460d5f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2025-05-22 02:27:56 UTC 
FEDORA-EPEL-2025-6179460d5f (borgbackup-1.4.1-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.