Bump borgmatic from 1.6.6 to 1.7.7 in /base

[dependabot]

Bumps borgmatic from 1.6.6 to 1.7.7.

Release notes

Sourced from borgmatic's releases.

borgmatic 1.7.7

• #642: Add MySQL database hook "add_drop_database" configuration option to control whether dumped MySQL databases get dropped right before restore.
• #643: Fix for potential data loss (data not getting backed up) when dumping large "directory" format PostgreSQL/MongoDB databases. Prior to the fix, these dumps would not finish writing to disk before Borg consumed them. Now, the dumping process completes before Borg starts. This only applies to "directory" format databases; other formats still stream to Borg without using temporary disk space.
• Fix MongoDB "directory" format to work with mongodump/mongorestore without error. Prior to this fix, only the "archive" format worked.

borgmatic 1.7.6

• #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of one combined dump file, allowing more convenient restores of individual databases. You can enable this by specifying the database dump "format" option when the database is named "all".
• #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
• #622: Fix traceback when include merging configuration files on ARM64.
• #629: Skip warning about excluded special files when no special files have been excluded.
• #630: Add configuration options for database command customization: "list_options", "restore_options", and "analyze_options" for PostgreSQL, "restore_options" for MySQL, and "restore_options" for MongoDB.

borgmatic 1.7.5

• #311: Override PostgreSQL dump/restore commands via configuration options.
• #604: Fix traceback when a configuration section is present but lacking any options.
• #607: Clarify documentation examples for include merging and deep merging.
• #611: Fix "data" consistency check to support "check_last" and consistency "prefix" options.
• #613: Clarify documentation about multiple repositories and separate configuration files.

borgmatic 1.7.4

• #596: Fix special file detection erroring when broken symlinks are encountered.
• #597, #598: Fix regression in which "check" action errored on certain systems ("Cannot determine Borg repository ID").

borgmatic 1.7.3

• #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: borgbackup/borg#6994

... (truncated)

Changelog

Sourced from borgmatic's changelog.

1.7.7

• #642: Add MySQL database hook "add_drop_database" configuration option to control whether dumped MySQL databases get dropped right before restore.
• #643: Fix for potential data loss (data not getting backed up) when dumping large "directory" format PostgreSQL/MongoDB databases. Prior to the fix, these dumps would not finish writing to disk before Borg consumed them. Now, the dumping process completes before Borg starts. This only applies to "directory" format databases; other formats still stream to Borg without using temporary disk space.
• Fix MongoDB "directory" format to work with mongodump/mongorestore without error. Prior to this fix, only the "archive" format worked.

1.7.6

• #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of one combined dump file, allowing more convenient restores of individual databases. You can enable this by specifying the database dump "format" option when the database is named "all".
• #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
• #622: Fix traceback when include merging configuration files on ARM64.
• #629: Skip warning about excluded special files when no special files have been excluded.
• #630: Add configuration options for database command customization: "list_options", "restore_options", and "analyze_options" for PostgreSQL, "restore_options" for MySQL, and "restore_options" for MongoDB.

1.7.5

• #311: Override PostgreSQL dump/restore commands via configuration options.
• #604: Fix traceback when a configuration section is present but lacking any options.
• #607: Clarify documentation examples for include merging and deep merging.
• #611: Fix "data" consistency check to support "check_last" and consistency "prefix" options.
• #613: Clarify documentation about multiple repositories and separate configuration files.

1.7.4

• #596: Fix special file detection erroring when broken symlinks are encountered.
• #597, #598: Fix regression in which "check" action errored on certain systems ("Cannot determine Borg repository ID").

1.7.3

• #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: borgbackup/borg#6994

... (truncated)

Commits

• 418ebc8 Add MySQL database hook "add_drop_database" configuration option to control w...
• f5a448c Fix for potential data loss (data not getting backed up) when dumping large "...
• 37ac542 Merge pull request 'setup: Add link to MacPorts package' (#641) from neverpan...
• 8c7d7e3 setup: Add link to MacPorts package
• b811f12 Clarify "checks" configuration documentation for older versions of borgmatic ...
• 061f3e7 Remove related documentation links.
• 6055918 Upgrade documentation image dependencies.
• 4a90e09 Clarify NEWS on database "all" dump feature applying to MySQL as well.
• 301b29e Bump version for release.
• c1eb210 Fix code style flake issue.
• 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)

[dependabot]

Superseded by #22.