This bug was fixed in the package deja-dup - 22.0-0ubuntu5
---------------
deja-dup (22.0-0ubuntu5) precise; urgency=low
* debian/patches/kill-lockfile.patch
- Backport patch from trunk that removes the lockfile placed by
duplicity to avoid concurrency. Deja-dup avoid concurrency using
its own method using Dbus (LP: #1281066)
-- Louis Bouchard <[email protected]> Mon, 17 Feb 2014 17:09:35 +0100
** Changed in: deja-dup (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1281066
Title:
Needs to backport trusty's fix to handle duplicity's lockfile
Status in “deja-dup” package in Ubuntu:
Fix Committed
Status in “deja-dup” source package in Precise:
Fix Released
Status in “deja-dup” source package in Saucy:
Fix Released
Bug description:
SRU justification :
Duplicity implements a new lockfile that impacts deja-dup
functionality. A fix to remove the lockfile is already commited
upstream and in Trusty. The SRU is to make the fix available before
duplicity's SRU is completed
Impact :
Without this SRU, duplicity's SRU for LP: #1266763 will cause errors
when backing up after having previously cancelled a backup.
Fix :
Remove the lockfile since concurrency is handled in DBUS in deja-dup
Test Case :
1) Start a backup
2) Cancel it once it begins backing up
3) Start the backup again
If you get an error right at the beginning of (3) about lockfiles,
this bug isn't fixed. If the backup proceeds, it's fixed!
Regression :
None expected as it remove a file that is only present with newer
versions of duplicity
Description of the problem :
See justification
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1281066/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
