Package: reportbug Version: 3.7.1 Severity: normal Perhaps this should really be wishlist, but it's annoying none the less.
If you configure an smtphost for reportbug, and for some reason, the smtphost is uncontactable, reportbug exits with an error (fortunately after saving a copy of the bug in /tmp). I believe it does the same if sendmail fails to exit cleanly, so the same method described below would be useful all round. It would be really nice if reportbug actually provided the user with a simple prompt to either: Fail does as it currently does Retry tries sending again as already configured re-read Configs then retry eg: for switching from smtphost to sendmail, or changing the smtphost IMHO, this would remind me that I haven't got the smtp tunnel to the mail server running so that I could start it and juts hit "Retry". *grin* -- Package-specific info: -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages reportbug depends on: ii python2.3 2.3.4+2.3.5c1-1 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
