Comment 62 for bug 1217959

Well, I tried to use duplicity to extract a file and it wasn't found. I then tried to list-current-files and got:

frohro@frohro-e6420:~$ duplicity list-current-files file:///home/frohro
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1500, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1494, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1343, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1432, in do_backup
    list_current(col_stats)
  File "/usr/bin/duplicity", line 665, in list_current
    sig_chain = col_stats.get_signature_chain_at_time(time)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 979, in get_signature_chain_at_time
    raise CollectionsError("No signature chains found")
CollectionsError: No signature chains found

frohro@frohro-e6420:~$

I think something is amiss. I'm going to try to backup again tonight and see what happens with the symbolically linked deja-dup-cache file excluded.

Rob