Bump borgbackup from 1.2.1 to 1.2.4 in /base

[dependabot]

Bumps borgbackup from 1.2.1 to 1.2.4.

Release notes

Sourced from borgbackup's releases.

Release 1.2.4

borgbackup 1.2.4 release

Short changelog summary (changes since borg 1.1):

https://www.borgbackup.org/releases/borg-1.2.html

Long changelog (including upgrade and compatibility notes):

https://github.com/borgbackup/borg/blob/1.2.4/docs/changes.rst#version-124-2023-03-24

Installation

If you use pip to install this, use: pip install pkgconfig ; pip install "borgbackup==1.2.4"

For other installation methods and more details, please see: https://borgbackup.org/

Feedback

borgbackup/borg#7472

Release 1.2.3

borgbackup 1.2.3 release

Short changelog summary (changes since borg 1.1):

https://www.borgbackup.org/releases/borg-1.2.html

Long changelog (including upgrade and compatibility notes):

https://github.com/borgbackup/borg/blob/1.2.3/docs/changes.rst#version-123-2022-12-24

Installation

If you use pip to install this, use: pip install pkgconfig ; pip install "borgbackup==1.2.3"

For other installation methods and more details, please see: https://borgbackup.org/

Feedback

borgbackup/borg#7225

Release 1.2.2

borgbackup 1.2.2 release

Short changelog summary (changes since borg 1.1):

https://www.borgbackup.org/releases/borg-1.2.html

Long changelog (including upgrade and compatibility notes):

... (truncated)

Changelog

Sourced from borgbackup's changelog.

Version 1.2.4 (2023-03-24)

Upgrade notes:

Some things can be recommended for the upgrade process from borg 1.1.x (please also read the important compatibility notes below):

• first upgrade to a recent 1.1.x release - especially if you run some older 1.1.* or even 1.0.* borg release.
• using that, run at least one borg create (your normal backup), prune and especially a check to see everything is in a good state.
• check the output of borg check - if there is anything special, consider a borg check --repair followed by another borg check.
• if everything is fine so far (borg check reports no issues), you can consider upgrading to 1.2.x. if not, please first fix any already existing issue.
• if you want to play safer, first create a backup of your borg repository.
• upgrade to latest borg 1.2.x release (you could use the fat binary from github releases page)
• run borg compact --cleanup-commits to clean up a ton of 17 bytes long files in your repo caused by a borg 1.1 bug
• run borg check again (now with borg 1.2.x) and check if there is anything special.
• run borg info (with borg 1.2.x) to build the local pre12-meta cache (can take significant time, but after that it will be fast) - for more details see below.
• check the compatibility notes (see below) and adapt your scripts, if needed.
• if you run into any issues, please check the github issue tracker before posting new issues there or elsewhere.

If you follow this procedure, you can help avoiding that we get a lot of "borg 1.2" issue reports that are not really 1.2 issues, but existed before and maybe just were not noticed.

Compatibility notes:

• matching of path patterns has been aligned with borg storing relative paths. Borg archives file paths without leading slashes. Previously, include/exclude patterns could contain leading slashes. You should check your patterns and remove leading slashes.
• dropped support / testing for older Pythons, minimum requirement is 3.8. In case your OS does not provide Python >= 3.8, consider using our binary, which does not need an external Python interpreter. Or continue using borg 1.1.x, which is still supported.
• freeing repository space only happens when "borg compact" is invoked.
• mount: the default for --numeric-ids is False now (same as borg extract)
• borg create --noatime is deprecated. Not storing atime is the default behaviour now (use --atime if you want to store the atime).
• --prefix is deprecated, use -a / --glob-archives, see #6806
• list: corrected mix-up of "isomtime" and "mtime" formats.

... (truncated)

Commits

• 35d76f9 build_man
• 0d14f3b build_usage
• b81b1ab it's 2023!
• 73ee704 security: 1.1.x is EOL, please upgrade to 1.2.x.
• 391e05a change log: set release date, remove outdated stuff
• af16e19 update CHANGES
• 05bfed5 Merge pull request #7471 from Michael-Girma/bug/issue-7470
• ea08161 Resolved mode bug and added sleep clause for darwin systems. Fixes #7470
• de2f894 Merge pull request #7464 from ThomasWaldmann/docs-borg-key-file-1.2
• 4c230a5 Merge pull request #7465 from dotdoom/1.2-maint-ignorezeros
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)