> > I had added register_backend to s3_boto3_backend, keeping it self contained
> > and following the convention in the ssh backends. The backends do not seem
> > entirely consistent on this point, with ssh having the two flavors entirely
> > self contained, and boto and cf separating the
Thanks for merging.
--
https://code.launchpad.net/~carlalex/duplicity/duplicity/+merge/376206
Your team duplicity-team is subscribed to branch lp:duplicity.
___
Mailing list: https://launchpad.net/~duplicity-team
Post to :
> Yes, just push the changes and let us know.
>
> Thanks for the fixes!
The dumb "I've never worked with bzr" question... What do I need to do other
than have all the changes in my branch? There is already a merge request
outstanding between my branch and lp:duplicity
--
> no worries. i think we are still misunderstanding each other. doesn't matter
> though! just leave the botobackend as is and i'll do the changes when i find
> the time :)
>
That seems likely. It'll be apparent when I see the final change. Thanks for
your time.
--
Testing a live backup against S3, I don't see any difference in list returning
strings or byte strings. The only difference I've seen is in the manual test.
I had added register_backend to s3_boto3_backend, keeping it self contained and
following the convention in the ssh backends. The
5 matches
Mail list logo
