This bug was fixed in the package duplicity - 0.6.18-0ubuntu3.5
---------------
duplicity (0.6.18-0ubuntu3.5) precise; urgency=low
* debian/patches/14-lp946988-fix-gnupassphrase-error.dpatch
- Backport upstream modification applied in LP: #946988 that fix
a failure to resume a backup with "bad passphrase" when the proper
passphrase is being used.
* debian/patches/13-lp1266763-add-concurrency-locking.dpatch
- Implement locking mechanism to avoid concurrent execution under the same
cache directory. This functionality adds a dependency to python-lockfile
Fixes LP: #1266763
* debian/patches/12-lp1266753-exception-if-no-s3.dpatch
- Add exception handling in the case where no S3 connection is
available instead of silently deleting the local cache.
Fixes LP: #1266753
-- Louis Bouchard <[email protected]> Thu, 23 Jan 2014 10:16:32 +0100
** Changed in: duplicity (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266763
Title:
Race condition between status and backup
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1266763/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
