Package: duply Version: 1.9.1-1 Severity: normal Hey, In debian stable, python-crypto complains in stderr that duply is not using it correctly :
/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV This is problematic for multiple reasons: first, if duply is supplying an IV to a CTR mode cypher, something is clearly wrong. Secondly, it writes a line for every duply job in stderr. I (like many others, I guess) happen to be running duply in cron, on multiple machines. This means for each cron run I get 4 emails from cron for each machine telling me this error. This is not ideal. The obvious fix would be to redirect stderr to stdout and be done with it, except that if duply fails a backup I don't get an email then. I haven't checked if newer versions still do this, but I can try it on testing if you want. Thank you in advance for your help, Clément Hertling -- 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/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages duply depends on: ii duplicity 0.6.24-1 ii gnupg 1.4.18-7+deb8u3 duply recommends no packages. Versions of packages duply suggests: ii openssh-client 1:6.7p1-5+deb8u3 -- no debconf information
