Package: duplicity
Version: 0.6.24-1
Severity: normal

Hello

I run Jessie.

Since I updated python-crypto to 2.6.1-5+deb8u1 [1] duplicity prints warnings
every time it runs. Like most user, I suppose, I run from cron. This means I
now receive a daily spam with:
/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: 
FutureWarning: CTR mode needs counter parameter, not IV
  self._cipher = factory.new(key, *args, **kwargs)

I expected program used normally not to emit deprecation warnings.

[1] 
https://tracker.debian.org/media/packages/p/python-crypto/changelog-2.6.1-5%2Bdeb8u1

-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages duplicity depends on:
ii  libc6            2.19-18+deb8u7
ii  librsync1        0.9.7-10
ii  python           2.7.9-1
ii  python-lockfile  1:0.8-2

Versions of packages duplicity recommends:
ii  python-oauthlib  0.6.3-1
ii  python-paramiko  1.15.1-1
ii  python-urllib3   1.9.1-3
ii  rsync            3.1.1-3

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

Reply via email to