Skip to content

Releases: borgmatic-collective/borgmatic

borgmatic 1.3.23

01 Oct 19:24
Compare
Choose a tag to compare
  • #174: More detailed error alerting via runtime context available in "on_error" hook.

borgmatic 1.3.22

01 Oct 05:26
Compare
Choose a tag to compare
  • #144: When backups to one of several repositories fails, keep backing up to the other
    repositories and report errors afterwards.

borgmatic 1.3.21

28 Sep 23:20
Compare
Choose a tag to compare

borgmatic 1.3.20

25 Sep 19:05
Compare
Choose a tag to compare
  • #205: More robust sample systemd service: boot delay, network dependency, lowered CPU/IO
    priority, etc.
  • #221: Fix "borgmatic create --progress" output so that it updates on the console in real-time.

borgmatic 1.3.19

23 Sep 20:09
Compare
Choose a tag to compare
  • #219: Fix visibility of "borgmatic prune --stats" output.

borgmatic 1.3.18

22 Sep 18:32
Compare
Choose a tag to compare
  • #220: Fix regression of argument parsing for default actions.

borgmatic 1.3.17

20 Sep 18:46
Compare
Choose a tag to compare
  • #217: Fix error with "borgmatic check --only" command-line flag with "extract" consistency check.

borgmatic 1.3.16

19 Sep 18:46
Compare
Choose a tag to compare
  • #210: Support for Borg check --verify-data flag via borgmatic "data" consistency check.
  • #210: Override configured consistency checks via "borgmatic check --only" command-line flag.
  • When generating sample configuration with generate-borgmatic-config, add a space after each "#"
    comment indicator.

borgmatic 1.3.15

13 Sep 04:36
Compare
Choose a tag to compare
  • #208: Fix for traceback when the "checks" option has an empty value.
  • #209: Bypass Borg error about a moved repository via "relocated_repo_access_is_ok" option in
    borgmatic storage configuration section.
  • #213: Reorder arguments passed to Borg to fix duplicate directories when using Borg patterns.
  • #214: Fix for hook erroring with exit code 1 not being interpreted as an error.

borgmatic 1.3.14

03 Aug 22:26
Compare
Choose a tag to compare
  • #204: Do not treat Borg warnings (exit code 1) as failures.
  • When validating configuration files, require strings instead of allowing any scalar type.