[dobs@wifi ~]$ duplicity -V
duplicity 0.6.20



Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1403, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1396, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1330, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 624, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 463, in patch_seq2ropath
    assert first.difftype != "diff", patch_seq
AssertionError: [(('home', 'dobs', 'NetBeansProjects', 'Visions CMS', 'api.php') reg), (('home', 'dobs', 'NetBeansProjects', 'Visions CMS', 'api.php') reg)]

I am seeing the same on Fedora 19 with duplicity-0.6.21-1.fc19, just slightly different line numbers:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1338, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 632, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 463, in patch_seq2ropath
    assert first.difftype != "diff", patch_seq
AssertionError: [(('home', 'anne', '.config', 'evolution', '.running') reg), (('home', 'anne', '.config', 'evolution', '.running') reg), (('home', 'anne', '.config', 'evolution', '.running') reg)]

Note: I am using duplicity via deja-dup.
There is also a similar report without resolution on
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1222661

Additional information: I can restore the original full backup.  The file that seems to be referenced in the assertion error does not exist in the original backup.

Here is a more detailed discussion on launchpad, unfortunately no resolution:
https://bugs.launchpad.net/duplicity/+bug/720525?comments=all

Looks like a serious problem as so far there is no apparent workaround.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

For the record, the relevant discussion on Launchpad is at 

https://bugs.launchpad.net/duplicity/+bug/720525?comments=all
https://bugs.launchpad.net/duplicity/+bug/1252484

Apparently the bug led to corrupted archives.  In a separate fix, duplicity is now supposed to not bail out when reading such a corrupted archive, but it's not clear whether this works reliably, and there is still the question of potential data loss in single files.  So it appears that a new full backup is required after applying the upgrade unless it's clear that all increments within the previous backup chain are clean.

I will mark this as a fix for the next update when I push it.  That will make it easier for users affected by this bug(s) to test it out

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.