Comment 11 for bug 1086374

Hello, I am also having this issue, under specific circumstances. I have duplicity 0.7.11 on two machines. From the first, I run

    duplicity --exclude /proc --exclude /tmp --exclude /sys --exclude /run rsync://scott@remote_machine/ destination/folder

It initializes the connection and requests the GPG key:

Command line warning: Selection options --exclude/--include
currently work only when backing up,not restoring.
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
GnuPG passphrase for decryption:

But when I enter the GPG key and hit enter, I get the following error, which is similar to the above, with different line numbers due to the age of this bug.

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1553, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1547, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1398, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1475, in do_backup
    restore(col_stats)
  File "/usr/bin/duplicity", line 738, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/bin/duplicity", line 760, in restore_get_patched_rop_iter
    backup_chain = col_stats.get_backup_chain_at_time(time)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 971, in get_backup_chain_at_time
    raise CollectionsError("No backup chains found")
CollectionsError: No backup chains found

Now this is interesting to me because it's somewhat different from this bug in that it occurs on backup as opposed to on restore, and only occurs when using the 'rsync' protocol.