Hello Kurt, or anyone else affected, Accepted duplicity into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/duplicity/0.6.21-0ubuntu4.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: duplicity (Ubuntu Saucy) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1266753 Title: Boto backend removes local cache if connection cannot be made Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released Status in “duplicity” package in Ubuntu: In Progress Status in “duplicity” source package in Precise: In Progress Status in “duplicity” source package in Quantal: In Progress Status in “duplicity” source package in Saucy: Fix Committed Bug description: SRU Justification [Impact] * When there is no connection to the S3 backend, the local cache files are deleted. [Test Case] 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') [Regression Potential] * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ). -- When there is no connection to the S3 backend, the local cache files are deleted. To reproduce: 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') You'll get a bunch of these: Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend). Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend). This is fatal if you run it in a configuration using GPG and having only the public key for encryption as well as a separate signing key. Then you cannot backup any more, as the decrypted local cache has been deleted and the files on the S3 are encrypted. Probably reason: There is no check if the connection to the backend could be established Workaround: If you replace at http://bazaar.launchpad.net/~duplicity- team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270 the line return [] with return None Then duplicity will crash instead of deleting the local files. Not the proper solution but at least you can do a backup when the connection comes back up. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1266753/+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
