Am Wed, Feb 23, 2022 at 07:01:46AM +0100 schrieb Bjorn Ketelaars:
> A newer version of borgbackup has been made available: 1.2.0, which is
> the first release of the 1.2 branch. This update should play nicely
> together with releases in the 1.1 branch, and strictly taken, nothing
> special is required for upgrading.
>
> Noticeable change is that freeing repository space only happens when
> "borg compact" is invoked. Borg < 1.2 invoked compaction automatically
> at the end of each repository writing command. Borg >= 1.2 does not do
> that any more. Changelog, including upgrade and compatibility notes, can
> be found at
> https://github.com/borgbackup/borg/blob/1.2.0/docs/changes.rst#version-120-2022-02-22-220222--.
>
> For now I propose to maintain both branches. 1.1.x Will get fixes for a
> while, and advantage of offering releases from both branches is that
> people do not have to rush in adopting their scripts.
>
> Diff below moves the current release (1.1.17) to borgbackup/1.1, and
> adds 1.2.0 as borgbackup/1.2. @pkgpath-marker has been added to the
> PLIST of borgbackup/1.1, so nobody is forced to 1.2.0 when using
> `pkg_add -u`.
>
> Testing:
> - `make test` runs successfully for both releases.
> - `pkg_add -u` from 1.1.17 should pick up releases in the 1.1 branch.
> - I have been testing/following the 1.2 branch since the first alpha
> release, and have switched completely since the first release
> candidate. So far, no regression observed.
>
> There is only one consumer of borgbackup, which needs some attention:
> sysutils/borgmatic. I will send a diff for this in a separate mail.
>
> Tests/comments/OK?
Tested 1.2.0 with create, list, extract, delete and check using my
main archive containing 132G of data after deduplication without
errors.
