Package: reportbug Version: 3.45 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Looks like reportbug creates invalid signatures when the bug report includes characters outside us-ascii. Such reports should probably be encoded as quoted-printable before being signed. I guess this report itself will demonstrate the problem since it will include my realname in .reportbugrc contents below... So, I might just as well sign it with Thanks, Bjørn - -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/bjorn/.reportbugrc: reportbug_version "3.2" mode standard ui text realname "Bjørn Mork" email "[EMAIL PROTECTED]" sign gpg - -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-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/bash Versions of packages reportbug depends on: ii apt 0.7.14+b1 Advanced front-end for dpkg ii python 2.5.2-2 An interactive high-level object-o ii python-central 0.6.8 register and build utility for Pyt reportbug recommends no packages. Versions of packages reportbug suggests: ii debconf-utils 1.5.22 debconf utilities pn debsums <none> (no description available) pn dlocate <none> (no description available) ii file 4.25-1 Determines file type using "magic" ii gnupg 1.4.9-3 GNU privacy guard - a free PGP rep pn python-urwid <none> (no description available) ii sendmail-bin [mail-transport- 8.14.3-5 powerful, efficient, and scalable - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAki1PqkACgkQ10rqkowbIsnabQCeMb/pE/12vKHER0ikp6DwjIlQ 8D8AoI/zCcIFvekTOPlSRHyieHme0NjY =/1Ni -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
