I am seeing this bug, too. All I can add is that it seems to happen on a file which is not present in the original full backup. The original full backup can be restored (or at least does not bump out when restoring the directory where the file listed in the assertion error lives).
I am seeing this bug, too. All I can add is that it seems to happen on a file which is not present in the original full backup. The original full backup can be restored (or at least does not bump out when restoring the directory where the file listed in the assertion error lives).
For the record, I am using Fedora and there is a bug in their bugzilla, too: /bugzilla. redhat. com/show_ bug.cgi? id=901420
https:/
There is also another entry on lauchpad which I found when googling for this problem: /bugs.launchpad .net/ubuntu/ +source/ duplicity/ +bug/1222661
https:/
Unfortunately, no resolution in any of these, but the problem looks pretty serious.