Bug 2407009 - borgmatic check always fails
Summary: borgmatic check always fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: borgmatic
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Felix Kaechele
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2407010 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-29 08:53 UTC by Alexander Groß
Modified: 2025-11-10 02:49 UTC (History)
2 users (show)

Fixed In Version: borgmatic-2.0.10-1.fc43 borgmatic-2.0.10-1.fc42 borgmatic-2.0.10-1.fc41
Clone Of:
Environment:
Last Closed: 2025-11-09 03:07:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alexander Groß 2025-10-29 08:53:15 UTC
Description of problem:

https://projects.torsion.org/borgmatic-collective/borgmatic/issues/1174

There is a bug in 2.0.9 when running on Python 3.14 that has been fixed in 2.10.0. Since F43 upgraded Python to 3.14 borgmatic 2.0.9 is now partially unusable.


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

Comment 1 Alexander Groß 2025-10-29 08:56:05 UTC
*** Bug 2407010 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Update System 2025-11-01 17:57:41 UTC
FEDORA-2025-2001636cc7 (borgmatic-2.0.10-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-2001636cc7

Comment 3 Fedora Update System 2025-11-01 17:57:45 UTC
FEDORA-2025-fcd379a966 (borgmatic-2.0.10-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-fcd379a966

Comment 4 Fedora Update System 2025-11-01 17:57:48 UTC
FEDORA-2025-78429f7ef6 (borgmatic-2.0.10-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-78429f7ef6

Comment 5 Fedora Update System 2025-11-02 01:04:22 UTC
FEDORA-2025-78429f7ef6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-78429f7ef6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-78429f7ef6

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

Comment 6 Fedora Update System 2025-11-02 01:22:43 UTC
FEDORA-2025-fcd379a966 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-fcd379a966`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-fcd379a966

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

Comment 7 Fedora Update System 2025-11-02 03:17:31 UTC
FEDORA-2025-2001636cc7 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2001636cc7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2001636cc7

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

Comment 8 Fedora Update System 2025-11-09 03:07:00 UTC
FEDORA-2025-fcd379a966 (borgmatic-2.0.10-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-11-09 03:18:44 UTC
FEDORA-2025-78429f7ef6 (borgmatic-2.0.10-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-11-10 02:49:29 UTC
FEDORA-2025-2001636cc7 (borgmatic-2.0.10-1.fc41) has been pushed to the Fedora 41 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.