duplicity-team team mailing list archive

[Kenneth Loafman <question150801@xxxxxxxxxxxxxxxxxxxxx>]

Question #150801 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/150801

    Status: Open => Answered

Kenneth Loafman proposed the following answer:
Max,

If you will remove the OO_backup.py from backends, this will allow duplicity
to use the patched version which uses the existing bucket and should not try
to create a new one.

As to Northern California bucket, I don't know that such a thing exists, or
how to specify it.  Currently boto does not have this capability, and
duplicity is dependent on boto for S3.

...Ken

On Fri, Apr 1, 2011 at 4:49 AM, Max
<question150801@xxxxxxxxxxxxxxxxxxxxx>wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
>     Status: Answered => Open
>
> Max is still having a problem:
> Hi,
>
> Thanks for your message.
>
> I'm little bit confused.....
>
> Why all this happens only when I try to make a backup in Northern
> California bucket (empty...created by me only for this test) ?
>
> Why all is OK when I try to make a backup in US Standard bucket (also this
> empty...
> created by me only for this test) ?
>
> What shall I do now ?
>
> Shall I forget forever to have a backup in Northern California bucket
> (with Duplicity) ?
>
> If so..... I'm forced to use only US Standard backup.....
>
> Thanks
> Max
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.