Hi, I had this bug reproduced this morning. I have a script that runs duplicity against different directories. the first few directories went ok, but the last ones failed. Each of the directories have 78 revision in their chain, complete with diffs and sigs.
running the script again with --full, the old sigs of the working dirs got deleted and duplicity recreated the full backup correctly but the other dirs failed as before, with -v9 saying something like ... Ignoring file 'duplicity-new-signatures.2005-10-29T01:02:41+01:00.to.2005-10-30T01:01:15+01:00.sigtar.gpg' Ignoring file 'duplicity-new-signatures.2005-10-30T01:01:15+01:00.to.2005-10-31T01:08:09+01:00.sigtar.gpg' Found signatures but no corresponding backup files where in my case, the backup files are really there. After removing all the old signatures files and the --full option, a new full backup was sucessfully generated. i will keep a test case handy in case that's useful. any suggestions on how to investigate this ? cheers, piem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
