Using b2 backend with duply fails when bucket exists

peterdalydickson commented 8 years ago

Thanks for this duplicity backend.

I am running duplicity 0.7.07.1 and duply version 1.11.3 on CentOS Linux release 7.2.1511.

We've recently moved to b2 and I modified the conf file as indicated in the duplicity man page.

i.e. TARGET='b2://my_account_id:my_application_key@macanta‑backups/testimage127/'

macanta-backups exists as a private bucket in my account.

When I run duply, it fails with...

--- Start running command BKP at 05:32:11.380 ---
/usr/lib64/python2.7/site-packages/duplicity/backends/b2backend.py:211: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
  if bucket_name not in bucket_names:
FatalBackendException: Bucket cannot be created
05:32:12.043 Task 'BKP' failed with exit code '23'.
--- Finished state FAILED 'code 23' at 05:32:12.043 - Runtime 00:00:00.662 ---

Is there anything else I should configure/do different?

Thanks again.

Best regards

Pete

peterdalydickson commented 8 years ago

A quick follow up...

I get the same result when I set TARGET='b2://my_account_id@macanta‑backups/testimage127/' and enter my_application_key at the prompt...

--- Start running command BKP at 05:48:21.195 ---
Password for 'my_account_id@B2':

achedeuzot commented 8 years ago

@peterdalydickson I got the same problem but, as explained in the below link, the problem was that there was a "-" character which was unicode instead of the default ASCII dash/minus character. It would be nice of b2backend to display maybe the character that causes the issue... ?

https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1436576.html

mtbentley / duplicity_b2

Using b2 backend with duply fails when bucket exists #10