[Duplicity-talk] Sometimes reads manifest from backup location even though it's in cache -- why?

[dcottingham00]

I see that duplicity will sometimes decide to retrieve a manifest from the remote backup location even though there's a copy in the local cache. Can anyone clarify what circumstances cause this to happen, and why?

Here's why I care. I am backing up to Amazon S3 and using a lifecycle rule to transition everything to Glacier. So, of course, nothing can be retrieved without prior manual intervention. I expected this to work since the local cache has everything duplicity needs, and in fact this worked with nightly backups for over two weeks. But now duplicity fails because it is trying to retrieve the last manifest, even though that file is in the cache.

Thanks for any help,
Dave Cottingham