Duplicity 0.7.19
Milestone information
- Project:
- Duplicity
- Series:
- 0.7
- Version:
- 0.7.19
- Released:
- Registrant:
- Kenneth Loafman
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 3 Fix Released
Download files for this release
Release notes
New in v0.7.19 (2019/04/29)
-------
* Fixed bug #1798206 and bug #1798504
- Made paramiko a global with import during __init__ so it would
not be loaded unless needed.
* Merged in lp:~mterry/duplicity/pydrive-root-0.7
- Just a tiny fix to clean up the temporary file we create to find the root ID.
It's a little surprising for the user if they wind up with this file called
"i_am_in_root" that they don't know where it came from. Almost sounds like
they were hacked.
* Merged in lp:~yajo/duplicity/duplicity
- Support partial metadata sync.
- Fixes bug #1823858 by letting the user to choose partial syncing. Only the metadata for the target chain
will be downloaded. If older (or newer) chains are encrypted with a different passphrase, the user will
be able to restore to a given time by supplying only the passphrase for the chain selected by
the `--restore-time` option when using this new option.
- A side effect is that using this flag reduces dramatically the sync time when moving files from one to
another location, in cases where big amounts of chains are found.
* Prep for release.
Changelog
0 blueprints and 3 bugs targeted
Bug report | Importance | Assignee | Status | |||
---|---|---|---|---|---|---|
1798206 | #1798206 | ssh_paramiko_backend.py - global name 'paramiko' is not defined | 4 Medium | 10 Fix Released | ||
1798504 | #1798504 | ssh UnsupportedBackendScheme | 4 Medium | 10 Fix Released | ||
1823858 | #1823858 | Cannot restore when passphrase has changed | 4 Medium | 10 Fix Released |