Merge lp:~mterry/duplicity/resume-inc into lp:duplicity/0.6
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 820 |
Proposed branch: | lp:~mterry/duplicity/resume-inc |
Merge into: | lp:duplicity/0.6 |
Diff against target: |
51 lines (+26/-5) 2 files modified
bin/duplicity (+6/-5) testing/tests/restarttest.py (+20/-0) |
To merge this branch: | bzr merge lp:~mterry/duplicity/resume-inc |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+84655@code.launchpad.net |
Description of the change
I found a bug while running the deja-dup test suite. If you are resuming an interrupted incremental backup, duplicity will first set the curtime and prevtime to be the same as the existing incremental. But then it will reset the time to be current. Which results in an error message later [1]. This branch fixes that and adds a test for it.
[1] A safety check I added to actually check for mismatches in encryption settings, but it caught this too, thankfully. "Restarting backup, but current encryption settings do not match original settings"
To post a comment you must log in.