Package Release Info

borgmatic-1.5.12-bp154.1.25

Update Info: Base Release
Available in Package Hub : 15 SP4

platforms

AArch64
ppc64le
s390x
x86-64

subpackages

borgmatic

Change Logs

Version: 1.1.15-bp150.1.3
* Tue Mar 27 2018 t.gruner@katodev.de
- Use README.md form source
- Add borgmatic.d folder in /etc for config files
- Update to 1.1.15
  * Support for Borg BORG_PASSCOMMAND environment variable to read a password from an external file.
  * Fix for Borg create error when using borgmatic's --dry-run and --verbosity options together.
  Work-around for behavior introduced in Borg 1.1.3: https://github.com/borgbackup/borg/issues/3298
  * #55: Fix for missing tags/releases on Gitea and GitHub project hosting.
  * #56: Support for Borg --lock-wait option for the maximum wait for a repository/cache lock.
  * #58: Support for using tilde in exclude_patterns to reference home directory.
* Tue Jan 30 2018 alarrosa@suse.com
- Removed _service file. Borgmatic uses to have frequent releases these days.
- Update to 1.1.14
  * Fix for typo in --patterns-from option.
  * Support for Borg --dry-run option via borgmatic command-line.
- Update to 1.1.13
  * Fix for incorrect consistency check flags passed to Borg when all three checks ("repository",
    "archives", and "extract") are specified in borgmatic configuration.
  * Add "local_path" to configuration for specifying an alternative Borg executable path.
  * Support for Borg experimental --patterns-from and --patterns options for specifying mixed
    includes/excludes.
  * Moved issue tracker from Taiga to integrated Gitea tracker at
    https://projects.torsion.org/witten/borgmatic/issues
- Update to 1.1.12
  * Declare dependency on pykwalify 1.6 or above, as older versions yield "Unknown key: version"
    rule errors.
  * Support for Borg --keep-minutely prune option.
- Update to 1.1.11
  * Add "ssh_command" to configuration for specifying a custom SSH command or options.
  * Fix for incorrect /etc/borgmatic.d/ configuration path probing on macOS. This problem manifested
    as an error on startup: "[Errno 2] No such file or directory: '/etc/borgmatic.d'".
- Update to 1.1.10
  * Pass several Unix signals through to child processes like Borg. This means that Borg now properly
    shuts down if borgmatic is terminated (e.g. due to a system suspend).
  * Support for using tilde in repository paths to reference home directory.
  * Support for Borg --files-cache option for setting the files cache operation mode.
  * Support for Borg --remote-ratelimit option for limiting upload rate.
  * Log invoked Borg commands when at highest verbosity level.
* Sun Oct 29 2017 alarrosa@suse.com
- Upstream moved from mercurial to git, so updated _service accordingly,
  updated source code to 6e9e7c4 and set all services mode to disabled.
- Fixed a too restrictive python3-ruamel.yaml version requirement
  in the source code
- Add a rcborgmatic symlink as required by the suse-missing-rclink rpmlint check
* Wed Sep 20 2017 alarrosa@suse.com
- Update to 1.1.9dev0-201
  * #29: Support for using tilde in source directory path to reference home directory.
- python3-ruamel.yaml and python3-pykwalify are now required
- Update to 1.1.8
  * #39: Fix to make /etc/borgmatic/config.yaml optional rather than required when using the default
    config paths.
- Update to 1.1.7
  * #28: Add "archive_name_format" to configuration for customizing archive names.
  * Fix for traceback when "exclude_from" value is empty in configuration file.
  * When pruning, make highest verbosity level list archives kept and pruned.
  * Clarification of Python 3 pip usage in documentation.
- Update to 1.1.6
  * #12, #35: Support for Borg --exclude-from, --exclude-caches, and --exclude-if-present options.
- Update to 1.1.5
  * #34: New "extract" consistency check that performs a dry-run extraction of the most recent
    archive.
- Update to 1.1.4
  * #17: Added command-line flags for performing a borgmatic run with only pruning, creating, or
    checking enabled. This supports use cases like running consistency checks from a different cron
    job with a different frequency, or running pruning with a different verbosity level.
- Update to 1.1.3
  * #14: Support for running multiple config files in /etc/borgmatic.d/ from a single borgmatic run.
  * Fix for generate-borgmatic-config writing config with invalid one_file_system value.
- Update to 1.1.2
  * #32: Fix for passing check_last as integer to subprocess when calling Borg.
- Update to 1.1.1
  * Part of #32: Fix for upgrade-borgmatic-config converting check_last option as a string instead of
    an integer.
  * Fix for upgrade-borgmatic-config erroring when consistency checks option is not present.
- Update to 1.1.0
  * Switched config file format to YAML. Run upgrade-borgmatic-config to upgrade.
  * Added generate-borgmatic-config command for initial config creation.
  * Dropped Python 2 support. Now Python 3 only.
  * #18: Fix for README mention of sample files not included in package.
  * #22: Sample files for triggering borgmatic from a systemd timer.
  * Support for backing up to multiple repositories.
  * To free up space, now pruning backups prior to creating a new backup.
  * Enabled test coverage output during tox runs.
  * Added logo.
* Wed Mar 08 2017 sfalken@opensuse.org
- Edited %files to clear unpackaged files builderror in
  openSUSE:Factory
* Sun Oct 30 2016 jengelh@inai.de
- Trim and wrap description
* Thu Oct 13 2016 alarrosa@suse.com
- version 1.0.3-dev: initial build
Version: 1.5.12-bp153.1.12
* Tue Feb 09 2021 Antonio Larrosa <alarrosa@suse.com>
- Update to 1.5.12
  * Fix for previous release with incorrect version suffix in
    setup.py. No other changes.
- Update to 1.5.11
  * #341: Add "temporary_directory" option for changing Borg's
    temporary directory.
  * #352: Lock down systemd security settings in sample systemd
    service file.
  * #355: Fix traceback when a database hook value is null in
    a configuration file.
  * #361: Merge override values when specifying the "--override"
    flag multiple times. The previous behavior was to take the
    value of the last "--override" flag only.
  * #367: Fix traceback when upgrading old INI-style configuration
    with upgrade-borgmatic-config.
  * #368: Fix signal forwarding from borgmatic to Borg resulting
    in recursion traceback.
  * #369: Document support for Borg placeholders in repository
    names.
- Replace patch:
  * remove-invalid-test.patch
  with patch from upstream that fixes tests:
  * 0001-Update-versions-of-test-dependencies.patch
* Mon Aug 31 2020 Antonio Larrosa <alarrosa@suse.com>
- Update to 1.5.10
  * #347: Add hooks that run for the "extract" action:
    "before_extract" and "after_extract".
  * #350: Fix traceback when a configuration directory is
    non-readable due to directory permissions.
  * Add documentation navigation links on left side of all
    documentation pages.
  * Clarify documentation on configuration overrides, specifically
    the portion about list syntax:
    http://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#configuration-overrides
  * Clarify documentation overview of monitoring options:
    http://torsion.org/borgmatic/docs/how-to/monitor-your-backups/
* Tue Jul 28 2020 Martin Rey <mrey@suse.com>
- Update to 1.5.9
  * #300: Add ?borgmatic export-tar? action to export an archive to
    a tar-formatted file or stream.
  * #339: Fix for intermittent timing-related test failure of
    logging function.
  * Clarify database documentation about excluding named pipes and
    character/block devices to prevent hangs.
* Tue Jul 07 2020 Martin Rey <mrey@suse.com>
- Update to 1.5.8
  * #336: Fix for traceback when running Cronitor, Cronhub, and
    PagerDuty monitor hooks.
- Update to 1.5.7
  * #327: Fix broken pass-through of BORG_* environment variables
    to Borg.
  * #328: Fix duplicate logging to Healthchecks and send "after_*"
    hooks output to Healthchecks.
  * #331: Add SSL support to PostgreSQL database configuration.
  * #333: Fix for potential data loss (data not getting backed up)
    when borgmatic omitted configured source directories in certain
    situations. Specifically, this occurred when two source
    directories on different filesystems were related by parentage
    (e.g. "/foo" and "/foo/bar/baz") and the one_file_system option
    was enabled.
  * Update documentation code fragments theme to better match the
    rest of the page.
  * Improve configuration reference documentation readability via
    more aggressive word-wrapping in configuration schema
    descriptions.
* Mon Jun 15 2020 Martin Rey <mrey@suse.com>
- Update to 1.5.6
  * #292: Allow before_backup and similiar hooks to exit with a
    soft failure without altering the monitoring status on
    Healthchecks or other providers. Support this by waiting to
    ping monitoring services with a "start" status until after
    before_* hooks finish. Failures in before_* hooks still trigger
    a monitoring "fail" status.
  * #316: Fix hang when a stale database dump named pipe from an
    aborted borgmatic run remains on disk.
  * #323: Fix for certain configuration options like ssh_command
    impacting Borg invocations for separate configuration files.
  * #324: Add "borgmatic extract --strip-components" flag to remove
    leading path components when extracting an archive.
  * Tweak comment indentation in generated configuration file for
    clarity.
  * Link to Borgmacator GNOME AppIndicator from monitoring
    documentation.