Bug#890645: duplicity: Duplicity fails on Backblaze B2 list-current-files
On Mon, 19 Feb 2018 18:37:48 +, Graham Cobb writes: >Are the changes from 0.7.11-1 to 0.7.16-1 sufficiently important that this >regression has to be implemented? please complain to upstream; i don't use backblaze or any of the other commercial storage services, and i don't care much about any of them. the changelogs don't even hint at the new requirements, all they say is "* Fixed bug #1654756 with new b2backend.py module from Vincent Rouille - Faster (big files are uploaded in chunks) - Added upload progress reporting support" the manpages don't say anything about backblaze either. as to 'has to be implemented' - the answer is yes: i use upstream's code, and i make only the absolutely minimum number of required changes to make it fit for debian. consequentially i will not attempt to create, curate and keep alive a totally debian-specific variant of duplicity, just so that module support can be cherry-picked. >Is there any information or testing on whether the out-of-repository workround >described in the error message works? i don't know. backblaze is one of many backends that duplicity claims to support, backblaze is commercial and therefore i don't use it and i don't care about it. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ ...wild Colostomy lurk dangerously in the trees, while out on the prairie, large herds of chocolate brown Bulimia graze contentedly... -- Tanuki signature.asc Description: Digital Signature
Bug#890645: duplicity: Duplicity fails on Backblaze B2 list-current-files
Package: duplicity Version: 0.7.16-1 Followup-For: Bug #890645 The command "pip install b2" does seem to work, although I haven't done exhaustive testing. I ran the following commands (as root): apt install python-arrow python-requests python-six python-tqdm python-dateutil python-funcsigs python-concurrent.futures pip install b2 And then tried a duplicity --collection-status (also as root) which worked. Note: I used apt to install the depencies for b2 which were in the repository. Alternatively, maybe those should bacomee dependencies of duplicity? Of course, the comments that I suggested putting in the README should probably go in a News entry, as you had suggested. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE=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) LSM: AppArmor: enabled Versions of packages duplicity depends on: ii gnupg 2.2.4-3 ii libc6 2.26-6 ii librsync1 0.9.7-10+b1 ii python2.7.14-4 ii python-fasteners 0.12.0-3 ii python-lockfile 1:0.12.2-2 Versions of packages duplicity recommends: ii python-oauthlib 2.0.6-1 ii python-paramiko 2.0.0-1 ii python-pexpect 4.2.1-1 ii python-urllib3 1.22-1 ii rsync3.1.2-2.1 Versions of packages duplicity suggests: ii lftp4.8.1-1 pn ncftp ii python-boto 2.44.0-1 pn python-cloudfiles pn python-gdata pn python-swiftclient pn tahoe-lafs -- no debconf information
Bug#890645: duplicity: Duplicity fails on Backblaze B2 list-current-files
Package: duplicity Version: 0.7.16-1 Followup-For: Bug #890645 I see the same problem, having just upgraded testing. This is a clear regression: there was no requirement for external libraries to use duplicity with B2 in previous versions of duplicity. Note that this will mean that anyone using duplicity in stretch for B2 will lose access to their data when upgrading to buster. Are the changes from 0.7.11-1 to 0.7.16-1 sufficiently important that this regression has to be implemented? If so, please make sure the README, and the buster release notes, warn about the loss of access to duplicity B2 data. Is there any information or testing on whether the out-of-repository workround described in the error message works? Please include the latest information on that in the README as well. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE=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) LSM: AppArmor: enabled Versions of packages duplicity depends on: ii gnupg 2.2.4-3 ii libc6 2.26-6 ii librsync1 0.9.7-10+b1 ii python2.7.14-4 ii python-fasteners 0.12.0-3 ii python-lockfile 1:0.12.2-2 Versions of packages duplicity recommends: ii python-oauthlib 2.0.6-1 ii python-paramiko 2.0.0-1 ii python-pexpect 4.2.1-1 ii python-urllib3 1.22-1 ii rsync3.1.2-2.1 Versions of packages duplicity suggests: ii lftp4.8.1-1 pn ncftp ii python-boto 2.44.0-1 pn python-cloudfiles pn python-gdata pn python-swiftclient pn tahoe-lafs -- no debconf information
Bug#890645: duplicity: Duplicity fails on Backblaze B2 list-current-files
tags 890645 + upstream forwarded 890645 https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/174324 thanks On Fri, 16 Feb 2018 23:50:05 -0800, Charlie Hagedorn writes: >The suggested solution is pulling in the Backblaze API implementation via pip, >but this shouldn't be necessary. as far as i can tell (not being a backblaze user) this *is* necessary because the backblaze api isn't available as debian package. i'll add a note about this to news.debian for the next release; there is nothing else that i can do about this. regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ IBM - "Internally Blackened Machines" -- Bob Vaughan about PSU failures signature.asc Description: Digital Signature
Bug#890645: duplicity: Duplicity fails on Backblaze B2 list-current-files
Package: duplicity Version: 0.7.16-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Running my usual scripts to interact with Backblaze B2, specifically listing the contents of the remote repository. These have worked for months. * What exactly did you do (or not do) that was effective (or ineffective)? Running: duplicity list-current-files B2:// * What was the outcome of this action? BackendException: B2 backend requires B2 Python APIs (pip install b2) * What outcome did you expect instead? A list of all files stored in that B2 bucket. These duplicity bugs add context: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1743247 https://bugs.launchpad.net/duplicity/+bug/1735825 The suggested solution is pulling in the Backblaze API implementation via pip, but this shouldn't be necessary. Thank you! *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (200, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages duplicity depends on: ii gnupg 2.2.4-3 ii libc6 2.26-6 ii librsync1 0.9.7-10+b1 ii python2.7.14-4 ii python-fasteners 0.12.0-3 ii python-lockfile 1:0.12.2-2 Versions of packages duplicity recommends: ii python-oauthlib 2.0.6-1 ii python-paramiko 2.0.0-1 ii python-pexpect 4.2.1-1 ii python-urllib3 1.22-1 ii rsync3.1.2-2.1 Versions of packages duplicity suggests: pn lftp pn ncftp pn python-boto pn python-cloudfiles pn python-gdata pn python-swiftclient pn tahoe-lafs -- no debconf information
