On Mon, 19 Feb 2018 18:37:48 +0000, 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
