Package: duplicity
Version: 0.7.05-2
Severity: normal

I understand from

http://mail.ale.org/pipermail/ale/2014-March/146988.html

that the culprit used to be an old version of python-paramiko, but the
problem was to be solved in 1.12.x.

Unfortunately it persists with the current 1.15.3 version of
python-paramiko.

Is there a work-around?

I will appreciate your help.

Best regards

Janusz

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages duplicity depends on:
ii  libc6            2.21-6
ii  librsync1        0.9.7-10
ii  python           2.7.11-1
ii  python-lockfile  1:0.10.2-2

Versions of packages duplicity recommends:
ii  python-oauthlib  1.0.3-1
ii  python-paramiko  1.15.3-1
ii  python-urllib3   1.13.1-1
ii  rsync            3.1.1-3

Versions of packages duplicity suggests:
pn  lftp                <none>
pn  ncftp               <none>
ii  python-boto         2.38.0-1
ii  python-cloudfiles   1.7.11-3
pn  python-gdata        <none>
pn  python-swiftclient  <none>
pn  tahoe-lafs          <none>

-- no debconf information

-- 
                           ,   
Prof. dr hab. Janusz S. Bien -  Uniwersytet Warszawski (Katedra Lingwistyki 
Formalnej)
Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department)
[email protected], [email protected], http://fleksem.klf.uw.edu.pl/~jsbien/

Reply via email to