There was an old bug with same error, but fixed in v0.6.15 (2011/08/19). Although (at least on Ubuntu) there were users dealing with the same error even when using newer duplicity versions:
As a workaround when this bug happens, deleting the (remote) files mentioned in the log as “Ignored” seems to work