|I am still trying to get 0.8.23 running on Mac OS. I moved the dependency from boto to boto3 and it build and ran the local tests. BUT when I tried to use s3 it mentioned that botocore was missing?|
Maybe the changed syntax will fix this but I somehow doubt it. AFAICT I need to install botocore as separate from boto3?
Note: I am using fink as my package manager for installing duplicity.
for those struggling with the changed S3 behavior in duplicity/boto3 regarding the --s3-endpoint-url, I thought I'd give an example. I took my some trial and error to figure out what needed to go where.
So if previously (before 0.8.23) you were using a destination like:
the new syntax (0.8.23+) should be something like:
Hopefully that will save someone some headaches! :-)
We made the following changes and released them in 0.8.23.dev15
development version on GitLab, Launchpad PPA, Snapcraft (edge), and PyPi. If you use the release/stable version, please use this for planning purposes. This will be part of 0.8.23 in a month or so.
Since some users use the dev version, here are the changes:
- boto3 backend is now default s3:// backend. It does not support s3:/// but needs --s3-endpoint-url instead
- boto3 supports --s3-unencrypted-connection option now
- boto backend now usable via boto+s3:// or boto+gs:// only
- boto's s3+http:// scheme was removed, use boto+s3:// instead
- boto supports --s3-endpoint-url. --s3-use-deep-archive options now
- changes are documented in man page
I would suggest that if/when this breaks things, please consult the man page. There are a bunch of much needed updates that will see you through.
Duplicity-talk mailing list
Duplicity-talk mailing listDuplicityemail@example.com