Encrypted bandwidth-efficient backup using the rsync algorithm
Duplicity incrementally backs up files and directories by encrypting
tar-format volumes with GnuPG and uploading them to a remote (or local)
file server. In theory many remote backends are possible; right now
local, ssh/scp, ftp, rsync, HSI, WebDAV, and Amazon S3 backends are
written.
Because duplicity uses librsync, the incremental archives are space
efficient and only record the parts of files that have changed since
the last backup. Currently duplicity supports deleted files, full unix
permissions, directories, symbolic links, fifos, etc., but not hard
links.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout SUSE:SLE-15-SP2:GA/duplicity && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| duplicity-0.8.07.tar.gz | 0001848584 1.76 MB | |
| duplicity-remove_shebang.patch | 0000001125 1.1 KB | |
| duplicity.changes | 0000044315 43.3 KB | |
| duplicity.spec | 0000002759 2.69 KB |
Revision 6 (latest revision is 7)
Gustavo Yokoyama Ribeiro (gyribeiro)
committed
(revision 6)
- Update to version 0.8.07:
+ Added b2sdk to snapcraft.yaml.
+ Fixed bug #1850440 with suggestion from Paolo Montrasio
- TypeError: Can't mix strings and bytes in path components.
+ Fixed bug #1850990 with suggestion from Jon Wilson
- --s3-use-glacier and --no-encryption cause slow backups.
+ Fixed bug #1851167 with help from Aspen Barnes
- Had Popen() to return strings not bytes.
+ Merged in lp:~mterry/duplicity/pydrive-cache-fix
- The pydrive backend had another of the ongoing bytes/string
issues. :)
+ Merged in lp:~mterry/duplicity/resume-encrypt-no-pass
- This branch arose from a Debian patch that has been disabling
the encryption validation of volume1 during restarts for
years. Debian has been preserving the ability to back up
with just an encrypt key and no password (i.e. to have no
secrets on the backup machine).
+ Fixed bug #1851727 - InvalidBackendURL for multi backend
- Encode to utf8 only on Python2, otherwise leave as unicode.
+ Merged in translation updates.
Comments 0