Comment 3 for bug 423145

Ken, please note the linked Debian report from Gonzalo, a Debian user who is using duplicity 0.6.04 and deja-dup 10.1. Gonzalo says that even with those versions and doing just a single full backup and then restore (i.e. not a long chain of incrementals), he is getting this error.

Are there other sources of problems that would cause this error? And isn't it sort of a design flaw of duplicity that it theoretically is open to this problem? Couldn't it close the file handles on files to which it isn't actively writing? That seems like it would solve the issue.