Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#79522 - [borg] 1.25 is buggy + needs manual intervention
Attached to Project:
Arch Linux
Opened by Iyan (iyanmv) - Wednesday, 30 August 2023, 22:38 GMT
Last edited by Toolybird (Toolybird) - Friday, 01 September 2023, 22:53 GMT
Opened by Iyan (iyanmv) - Wednesday, 30 August 2023, 22:38 GMT
Last edited by Toolybird (Toolybird) - Friday, 01 September 2023, 22:53 GMT
|
DetailsDescription:
Updating repos to borg 1.25 requires some manual work. I guess this should be mention as a post_upgrade message. This is important because borg check will fail if upgrade is not done correctly. In addition, those required manual steps will fail if borg rename or borg recreate were used in the past. Instruction to upgrade repo: https://github.com/borgbackup/borg/blob/1.2.5/docs/changes.rst#important-notes Issue: https://github.com/borgbackup/borg/issues/7791 I suggest keeping borg 1.24 until borg 1.26 is released. CVE is not critical, if an attacker has writing permissions to your backup repo, you have bigger problems. |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 01 September 2023, 22:53 GMT
Reason for closing: Fixed
Additional comments about closing: borg 1.2.6-1
Friday, 01 September 2023, 22:53 GMT
Reason for closing: Fixed
Additional comments about closing: borg 1.2.6-1
https://github.com/borgbackup/borg/discussions/7787#discussioncomment-6868575