duplicity-team team mailing list archive

[Lee Verberne <lee@xxxxxxxxx>]

That's a good question.  I wrote the patches working with S3 first, and then verifying functionality on GCS afterwards.

That being said, I'd appreciate your advice on what else I should test.

Here's what I've verified so far:

 * testing/run-tests unit tests
 * testing/manual/backendtest.py unit tests
 * manual backup/restore of a large file to S3 using the default flags and comparing checksums after completion
 * manual backup/restore of a large file to S3 using --s3-use-new-style and comparing checksums after completion
 * manual backup/restore of a large file to GCS using the default flags and comparing checksums after completion
 * manual backup/restore of a large file to GCS using --s3-use-new-style and comparing checksums after completion
 * Interchanging the s3:// and s3+http:// duplicity address syntax

I haven't tested --s3-unencrypted-connections or --s3-european-buckets.  I also haven't tested older versions of boto, but that's probably something I should do.  It looks like 1.6a is the current minimum version, so I'll test that and get back to you.
-- 
https://code.launchpad.net/~verb/duplicity/boto-gcs/+merge/178399
Your team duplicity-team is requested to review the proposed merge of lp:~verb/duplicity/boto-gcs into lp:duplicity.