Merge lp:~mterry/deja-dup/detect-encryption into lp:deja-dup/30
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 1503 |
Proposed branch: | lp:~mterry/deja-dup/detect-encryption |
Merge into: | lp:deja-dup/30 |
Diff against target: |
357 lines (+62/-91) 11 files modified
libdeja/tests/scripts/delete-just-right.test (+2/-2) libdeja/tests/scripts/delete-too-few.test (+1/-1) libdeja/tests/scripts/delete-too-old.test (+7/-7) libdeja/tests/scripts/disk-full.test (+6/-6) libdeja/tests/scripts/disk-full2.test (+3/-3) libdeja/tests/scripts/encrypt-ask.test (+12/-9) libdeja/tests/scripts/encrypt-detect.test (+8/-6) libdeja/tests/scripts/nag.test (+20/-16) libdeja/tests/scripts/threshold-full.test (+1/-1) libdeja/tests/scripts/threshold-inc.test (+1/-1) libdeja/tools/duplicity/DuplicityJob.vala (+1/-39) |
To merge this branch: | bzr merge lp:~mterry/deja-dup/detect-encryption |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Bruce Park (community) | Approve | ||
Déjà Dup Developers | Pending | ||
Review via email: mp+191484@code.launchpad.net |
Description of the change
Use official duplicity method of declaring that a backup is encrypted.
A while back, I added support to duplicity to announce whether the backup is encrypted or not. I also added support in deja-dup for noticing. Unfortunately, there was a bug with the first implementation, and I never actually turned on deja-dup-side support for the feature.
But I figure it's about time. Our current method is to just scan duplicity debug messages for file names ending in .gpg, which seems brittle.
To post a comment you must log in.
Ok, had to merge trunk in order to get this to compile, but it looks good ;-)