[Duplicity-talk] CollectionsError: No signature chains found

[Henrik Olsen]

I'm getting a CollectionsError: No signature chains found with 0.6.13 when 
doing a list-current-files.

NcFTP version is 3.2.5
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue Aug 23 10:00:02 2011
Traceback (most recent call last):
  File "/usr/local/duplicity/bin/duplicity", line 1250, in <module>
    with_tempdir(main)
  File "/usr/local/duplicity/bin/duplicity", line 1243, in with_tempdir
    fn()
  File "/usr/local/duplicity/bin/duplicity", line 1201, in main
    list_current(col_stats)
  File "/usr/local/duplicity/bin/duplicity", line 514, in list_current
    sig_chain = col_stats.get_signature_chain_at_time(time)
  File "/usr/local/duplicity/lib/python/duplicity/collections.py", line 964, in 
get_signature_chain_at_time
    raise CollectionsError("No signature chains found")
CollectionsError: No signature chains found

Is it because a collection-status reports only secondary chains?

NcFTP version is 3.2.5
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue Aug 23 10:00:02 2011
Collection Status
-----------------
Connecting with backend: FTPBackend
Archive dir: /var/cache/duplicity/macbook_holsen

Found 3 secondary backup chains.
Secondary chain 1 of 3:
-------------------------
Chain start time: Sat Jan 22 11:22:13 2011
Chain end time: Sat Jan 22 11:22:13 2011
Number of contained backup sets: 1
Total number of contained volumes: 165
 Type of backup set:                            Time:      Num volumes:
                Full         Sat Jan 22 11:22:13 2011               165
-------------------------

Secondary chain 2 of 3:
-------------------------
Chain start time: Thu Jun  2 21:18:40 2011
Chain end time: Thu Jun  2 21:18:40 2011
Number of contained backup sets: 1
Total number of contained volumes: 160
 Type of backup set:                            Time:      Num volumes:
                Full         Thu Jun  2 21:18:40 2011               160
-------------------------

Secondary chain 3 of 3:
-------------------------
Chain start time: Tue Aug 23 10:00:02 2011
Chain end time: Tue Aug 23 10:00:02 2011
Number of contained backup sets: 1
Total number of contained volumes: 161
 Type of backup set:                            Time:      Num volumes:
                Full         Tue Aug 23 10:00:02 2011               161
-------------------------

No backup chains with active signatures found
No orphaned or incomplete backup sets found.

I've had issues with duplicity not being able to clean out the backups I 
needed, so I had to manually clean out some files a few days ago directly on 
the ftp destination. I let three full backups stay and ran a clean with --force 
and --extra-clean, and everything seemed fine, reporting the three left full 
backups, and no orphaned or incomplete backup sets anymore. But even though 
latest full backup is from August 23th 2011, duplicity starts a new full 
backup, and not an incremental (using --full-if-older-than 3M), a problem I 
don't usually have. An explanation for this behaviour?

Best regards
Henrik