Package: cryptsetup Version: 2:1.0.6-7 Severity: normal Cryptsetup breaks normal unix conventions by being too chatty e.g. this command:
cryptsetup luksOpen /dev/sdc Hitachi_500G_number_2a --key-file - ... outputs: Command successful. to standard error. STDERR is conventionally used for error conditions only. Minimally, the 'Command successful.' string should be directed to stdout, ideally it should not output any message on a normal/successful condition (or make the output conditional on switches like --quiet or --verbose etc.). The current behavior makes scripting (especially in cron jobs) awkward, as the 'Command successful.' message must be manually checked for and discarded (e.g. by piping stderr through grep -v). Thanks, Tim. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
