Comment 1 for bug 1306242

I have found out the root cause and a fix for this. It only happens when you are backing up into a Google Drive "folder", i.e. not the root collection of Drive. When this is being done, the "delete" action of the gdata api only removes the file from the collection, not from drive, so the file ends up in the root collection instead of being deleted.

The solution is to delete the file by its resource_id, so in gdocsbackend inside the delete function, instead of
> self.client.delete(entry.get_edit_link().href + '?delete=true', force=True)
it needs to read
> self.client.delete(self.client.get_doc(entry.resource_id.text).get_edit_link().href + '?delete=true', force=True)

I have tested and verified that this works with 0.6.18 on Ubuntu 12.04.