Borgmatic

Latest version: v1.8.11

Safety actively analyzes 630169 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 28

1.7.3

Not secure
* 357: Add "break-lock" action for removing any repository and cache locks leftover from Borg
aborting.
* 360: To prevent Borg hangs, unconditionally delete stale named pipes before dumping databases.
* 587: When database hooks are enabled, auto-exclude special files from a "create" action to
prevent Borg from hanging. You can override/prevent this behavior by explicitly setting the
"read_special" option to true.
* 587: Warn when ignoring a configured "read_special" value of false, as true is needed when
database hooks are enabled.
* 589: Update sample systemd service file to allow system "idle" (e.g. a video monitor turning
off) while borgmatic is running.
* 590: Fix for potential data loss (data not getting backed up) when the "patterns_from" option
was used with "source_directories" (or the "~/.borgmatic" path existed, which got injected into
"source_directories" implicitly). The fix is for borgmatic to convert "source_directories" into
patterns whenever "patterns_from" is used, working around a Borg bug:
https://github.com/borgbackup/borg/issues/6994
* 590: In "borgmatic create --list" output, display which files get excluded from the backup due
to patterns or excludes.
* 591: Add support for Borg 2's "--match-archives" flag. This replaces "--glob-archives", which
borgmatic now treats as an alias for "--match-archives". But note that the two flags have
slightly different syntax. See the Borg 2 changelog for more information:
https://borgbackup.readthedocs.io/en/2.0.0b3/changes.html#version-2-0-0b3-2022-10-02
* Fix for "borgmatic --archive latest" not finding the latest archive when a verbosity is set.

1.7.2

Not secure
* 577: Fix regression in which "borgmatic info --archive ..." showed repository info instead of
archive info with Borg 1.
* 582: Fix hang when database hooks are enabled and "patterns" contains a parent directory of
"~/.borgmatic".

1.7.1

Not secure
* 542: Make the "source_directories" option optional. This is useful for "check"-only setups or
using "patterns" exclusively.
* 574: Fix for potential data loss (data not getting backed up) when the "patterns" option was
used with "source_directories" (or the "~/.borgmatic" path existed, which got injected into
"source_directories" implicitly). The fix is for borgmatic to convert "source_directories" into
patterns whenever "patterns" is used, working around a Borg bug:
https://github.com/borgbackup/borg/issues/6994

1.7.0

Not secure
* 463: Add "before_actions" and "after_actions" command hooks that run before/after all the
actions for each repository. These new hooks are a good place to run per-repository steps like
mounting/unmounting a remote filesystem.
* 463: Update documentation to cover per-repository configurations:
https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/
* 557: Support for Borg 2 while still working with Borg 1. This includes new borgmatic actions
like "rcreate" (replaces "init"), "rlist" (list archives in repository), "rinfo" (show repository
info), and "transfer" (for upgrading Borg repositories). For the most part, borgmatic tries to
smooth over differences between Borg 1 and 2 to make your upgrade process easier. However, there
are still a few cases where Borg made breaking changes. See the Borg 2.0 changelog for more
information: https://www.borgbackup.org/releases/borg-2.0.html
* 557: If you install Borg 2, you'll need to manually upgrade your existing Borg 1 repositories
before use. Note that Borg 2 stable is not yet released as of this borgmatic release, so don't
use Borg 2 for production until it is! See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/upgrade/#upgrading-borg
* 557: Rename several configuration options to match Borg 2: "remote_rate_limit" is now
"upload_rate_limit", "numeric_owner" is "numeric_ids", and "bsd_flags" is "flags". borgmatic
still works with the old options.
* 557: Remote repository paths without the "ssh://" syntax are deprecated but still supported for
now. Remote repository paths containing "~" are deprecated in borgmatic and no longer work in
Borg 2.
* 557: Omitting the "--archive" flag on the "list" action is deprecated when using Borg 2. Use
the new "rlist" action instead.
* 557: The "--dry-run" flag can now be used with the "rcreate"/"init" action.
* 565: Fix handling of "repository" and "data" consistency checks to prevent invalid Borg flags.
* 566: Modify "mount" and "extract" actions to require the "--repository" flag when multiple
repositories are configured.
* 571: BREAKING: Remove old-style command-line action flags like "--create, "--list", etc. If
you're already using actions like "create" and "list" instead, this change should not affect you.
* 571: BREAKING: Rename "--files" flag on "prune" action to "--list", as it lists archives, not
files.
* 571: Add "--list" as alias for "--files" flag on "create" and "export-tar" actions.
* Add support for disabling TLS verification in Healthchecks monitoring hook with "verify_tls"
option.

1.6.6

Not secure
* 559: Update documentation about configuring multiple consistency checks or multiple databases.
* 560: Fix all database hooks to error when the requested database to restore isn't present in the
Borg archive.
* 561: Fix command-line "--override" flag to continue supporting old configuration file formats.
* 563: Fix traceback with "create" action and "--json" flag when a database hook is configured.

1.6.5

Not secure
* 553: Fix logging to include the full traceback when Borg experiences an internal error, not just
the first few lines.
* 554: Fix all monitoring hooks to warn if the server returns an HTTP 4xx error. This can happen
with Healthchecks, for instance, when using an invalid ping URL.
* 555: Fix environment variable plumbing so options like "encryption_passphrase" and
"encryption_passcommand" in one configuration file aren't used for other configuration files.

Page 5 of 28

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.