Package: reportbug Version: 3.48 Followup-For: Bug #489447 I just lost 20 minutes of composing a bug report (complete with a documentation snippet I wrote) because SMTP failed. Yes, I can write it again. If my editor crashed and lost my code, I could write that code again, too, but I'd consider that a data loss bug as well. Under no circumstances should reportbug delete a bug report until it *successfully* sends it via SMTP or sendmail. I consider this a grave bug, though I will not change the severity again.
- Josh Triplett -- Package-specific info: ** Environment settings: EDITOR="/home/josh/.local/bin/vim-wrapper" DEBEMAIL="[email protected]" EMAIL="[email protected]" DEBFULLNAME="Josh Triplett" NAME="Josh Triplett" INTERFACE="text" ** /home/josh/.reportbugrc: reportbug_version "3.21.2" mode advanced ui text no-cc header "X-Debbugs-CC: [email protected]" smtphost reportbug.debian.org:587 header "X-Debbugs-No-Ack: ack!" -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27-1-amd64 (SMP w/2 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.19 Advanced front-end for dpkg ii python 2.5.2-3 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: pn debconf-utils <none> (no description available) ii debsums 2.0.40 verification of installed package pn dlocate <none> (no description available) ii file 4.26-2 Determines file type using "magic" ii gnupg 1.4.9-3 GNU privacy guard - a free PGP rep pn postfix | exim4 | mail-transp <none> (no description available) pn python-urwid <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
