Merge lp:~bmerry/duplicity/pydrive-id-cache into lp:~duplicity-team/duplicity/0.7-series
Status: | Merged |
---|---|
Merged at revision: | 1129 |
Proposed branch: | lp:~bmerry/duplicity/pydrive-id-cache |
Merge into: | lp:~duplicity-team/duplicity/0.7-series |
Diff against target: |
152 lines (+85/-23) 1 file modified
duplicity/backends/pydrivebackend.py (+85/-23) |
To merge this branch: | bzr merge lp:~bmerry/duplicity/pydrive-id-cache |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+270903@code.launchpad.net |
Description of the change
Second attempt: I've now merged with the master branch. That merge did some strange things (it undid a whole bunch of my changes, which I had to put back in in the following commit), so please take a quick look to ensure that this merge is sane (I don't normally use bzr so I might be doing it wrong).
This fixes the issue a number of users (including myself) have been having with duplicity creating files with duplicate filenames on Google Drive. It keeps a runtime cache of filename to object ID mappings, so that once it has uploaded an object it won't be fooled by weakly consistent directory listings. I've been using it for a while with no more duplicate filename issues, and another user has reported that it's fixed his issues as well.