Package: duplicity Version: 0.6.24-1 Severity: normal Hello,
I'm not certain this problem is in duplicity or in python-crypto. Since yesterday's update to Debian 8.7, all my servers (including the one from which I'm reporting this) throw this message when running duplicity with -v2: /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 use public key encryption with --encrypt-key=XXXX. I have this python-crypto: ii python-crypto 2.6.1-5+deb8 This is more than a mere annoyance. If I receive emails every day I will stop reading them, so I will miss important messages. This is clearly not an option. Otherwise I might increase verbosity to error, in which case I'm worried about missing any important warning messages. So if there is any other idea for a workaround I'm all ears. Thanks! -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=C, 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.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 pn python-paramiko <none> 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> -- no debconf information
