Multi back-end doesn't work with hubiC

The fix made this even more broken ;) The hubiC and pyrax use different configuration techniques, pyrax relays on environment variables for Rackspace connection, while hubiC want's a dotfile in `~` dir, with that commit you have to have both - conficting configurations.

Got it. Give it another go.

On Sat, Jul 4, 2015 at 10:18 AM, canni <email address hidden> wrote:

> The fix made this even more broken ;) The hubiC and pyrax use different
> configuration techniques, pyrax relays on environment variables for
> Rackspace connection, while hubiC want's a dotfile in `~` dir, with that
> commit you have to have both - conficting configurations.
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1471348
>
> Title:
> Multi back-end doesn't work with hubiC
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> Fix Committed
>
> Bug description:
> Because hubiC (and pyrax) back-end does not call parent implementation
> of Backend class `__init__` it does not work with multi back-end.
>
> Multi tries to access backend instance `.parsed_url` property witch is
> absent for hubiC and pyrax.
>
> Steps to reproduce:
> - Set hubiC as one of backends in yours Multi backend JSON config
> - Run duplicty
>
> Expected result: Everything works as expected
>
> Actual result:
> Attempt 1 failed. AttributeError: 'HubicBackend' object has no attribute
> 'parsed_url'
>
> Duplicty ver: 0.7.03
> Python 2.7.9
> Ubuntu 15.04 64bit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1471348/+subscriptions
>

+1 now works