Duplicity 0.7.14 Released
Written for Duplicity by Kenneth Loafman on 2017-08-31
New in v0.7.14 (2017/08/31)
-------
* Merged in lp:~dawgfoto/duplicity/skip_sync_collection_status
- collection-status should not sync metadata
- up-to-date local metadata is not needed as collection-status is
generated from remote file list
- syncing metadata might require to download several GBs
* Fixed slowness in 'collection-status' by basing the status on the
remote system only. The local cache is treated as empty.
* Fixed encrypted remote manifest handling to merely put out a non-fatal
error message and continue if the private key is not available.
* Patched in lp:~mterry/duplicity/giobackend-display-name
- giobackend: handle a wider variety of gio backends by making less assumptions;
in particular, this fixes the google-drive: backend
* Fixed bug #1709047 with suggestion from Gary Hasson
- fixed so default was to use original filename
* Fixed PEP8 errors in bin/duplicity
* Merged in lp:~mterry/duplicity/gio_child_for_display_name_0.7
- gio: be slightly more correct and get child GFiles based on display name
* Fixed bug #1711905 with suggestion from Schneider
- log.Warn was invoked with log.warn in webdavbackend.py
* Merged in lp:~mterry/duplicity/gpg-tag-versions
- Support gpg versions numbers that have tags on them.
- This can happen if you build gpg from git trunk (e.g. 2.1.15-beta20). Or if you run
against the freedesktop flatpak runtime (e.g. 2.1.14-unknown).
* Fixed bug #1394386 with new module megabackend.py from Tomas Vondra
- uses megatools from https:/
which has been deprecated
- fixed copyright and PEP8 issues
- replaced subprocess.call() with self.subprocess
* Fixed bug #1713640 with patch from Aleksandar Ivanisevic
- replace 2.7 syntax with 2.6 equivalent
* Fixed bug #1538333 Assertion error in manifest.py: assert filecount == ...
- Made sure to never pass .part files as true manifest files
- Changed assert to log.Error to warn about truncated/corrupt filelist
- Added unit test to make sure detection works
- Note: while this condition is serious, it will not affect the basic backup and restore
functions. Interactive options like --list-
work correctly for this backup set, so it is advised to run a full backup as soon as
possible after this error occurs.
* Fixed bug #1638033 Remove leading slash on --file-to-restore
- code already used rstrip('/') so change to just strip('/')
