Package: duplicity Followup-For: Bug #830896 It turns out that the bucket name I was using on the command line included Unicode characters: the "-" were actually some Unicode character that looked like "-" but was not. This was because I had copied the bucket name off the backblaze web page after creating it.
While it would be nice if the b2 backend handled Unicode characters (and either matched or failed instead of giving a python error message), this is clearly a lower priority problem than I thought. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages duplicity depends on: ii libc6 2.22-7 ii librsync1 0.9.7-10 ii python 2.7.11-1 ii python-lockfile 1:0.12.2-1 Versions of packages duplicity recommends: ii python-oauthlib 1.0.3-1 ii python-paramiko 1.16.0-1 ii python-urllib3 1.13.1-2 ii rsync 3.1.1-3 Versions of packages duplicity suggests: pn lftp <none> pn ncftp <none> ii python-boto 2.38.0-1 pn python-cloudfiles <none> pn python-gdata <none> pn python-swiftclient <none> pn tahoe-lafs <none> -- no debconf information
