Comment 7 for bug 1170161

Dear all,
I really appreciate this discussion. So far I have been using a dirty workaround to use duplicity along with Amazon Glacier. (see also http://blog.epsilontik.de/?page_id=68).
Inspired by this thread and a comment in the blog I finally took the time to develop the attached patch to change the naming for glacier.

With this patch the naming conventions are changed as follows (if using the --alternate-filenames option)

duplicity-full-signatures.date (stays unchanged)
duplicity-new-signatures.date (stays unchanged)
duplicity-full.date.manifest => duplicity-full-manifest.date
duplicity-inc.date.to.date.manifest => duplicity-inc-manifest.date.to.date.manifest
duplicity-full.date.VOLX.difftar => duplicity-full-difftar.date.VOLX
duplicity-inc.date.to.date.VOLX.difftar => duplicity-inc-difftar.date.to.date.VOLX

This will allow to filter for all file types using the standard lifecycle rules for glacier.

I tested the patch with a standard and an incremental backup and it seems to work fine. I'd appreciate if you could also have a look.

Do you have any standard test cases that you are using in the development of duplicity?

Rgds
-E