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
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 pyt
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 d
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
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 repos
5 matches
Mail list logo
