borgmatic
No description set
- Sources inherited from project openSUSE:Backports:SLE-15-SP5
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.5:Update/borgmatic && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
borgmatic-1.7.5.tar.gz | 0000329229 322 KB | |
borgmatic.changes | 0000040897 39.9 KB | |
borgmatic.spec | 0000006305 6.16 KB | |
skip-tests.patch | 0000000873 873 Bytes | |
support-python3.6.patch | 0000000314 314 Bytes |
Latest Revision
Yuchen Lin (maxlin_factory)
accepted
request 1060862
from
Antonio Larrosa (alarrosa)
(revision 6)
Update to 1.7.5 which seems to support python 3.6 correctly (at least, all tests pass if the requirement for 3.7 is removed) - Add patch to reduce the requirement of python 3.7 to work with python 3.6 so borgmatic can be used in Leap 15.5 . All the tests work fine so it seems python 3.7 isn't really required: * support-python3.6.patch - Update to 1.7.5: * #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.
Comments 0