[Reportbug-maint] Bug#813660: reportbug: very unobvious that a report was NOT sent

Adam Borowski kilobyte at angband.pl
Thu Feb 4 05:54:41 UTC 2016


Package: reportbug
Version: 6.6.6
Severity: normal


Today I filed a bug report, running reportbug from a recently installed
chroot.  The reporting process looked like always, the last messages being:

=========================================================================
File /tmp/reportbug-libcrypto++-20160204-30442-_ABUoJ saved
Report will be sent to "Debian Bug Tracking System" <submit at bugs.debian.org>
Submit this report on libcrypto++ (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? a
Choose a file to attach: debian/patches/x32.patch
Report will be sent to "Debian Bug Tracking System" <submit at bugs.debian.org>
Attachments:
 debian/patches/x32.patch
Submit this report on libcrypto++ (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? 
Saving a backup of the report at /tmp/reportbug-libcrypto++-backup-20160204-30442-0H7d7t
Bug report written as /var/tmp/libcrypto++.bug

If you want to provide additional information, please wait to receive the bug tracking number via email;
you may then send any extra information to n at bugs.debian.org (e.g. 999999 at bugs.debian.org), where n is
the bug number. Normally you will receive an acknowledgement via email including the bug report number
within an hour; if you haven't received a confirmation, then the bug reporting process failed at some
point (reportbug or MTA failure, BTS maintenance, etc.).
=========================================================================

The message clearly says I'll get the confirmation soon, etc.  Except for
one small detail... reportbug did nothing.  The direct reason being that
there was no MTA in the chroot (nothing depends on it).  I was presented
with no error message.

Thus, in such a case please add a message that the bug was NOT sent.
The paragraph about additional information, in particular, needs to be
suppressed, as what is says is untrue.



-- Package-specific info:
** Environment settings:
EDITOR="jstar"
EMAIL="kilobyte at angband.pl"
INTERFACE="text"

** /home/kilobyte/.reportbugrc:
reportbug_version "3.17"
mode advanced
ui text

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-x32 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt               1.2.1
ii  python-reportbug  6.6.6
pn  python:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs23-bin-common | emacs24-bin-common    <none>
ii  exim4                                      4.86-7
ii  exim4-daemon-light [mail-transport-agent]  4.86-7+b2
ii  file                                       1:5.25-2
ii  gnupg                                      1.4.20-1
ii  python-gtk2                                2.24.0-4
pn  python-gtkspellcheck                       <none>
pn  python-urwid                               <none>
pn  python-vte                                 <none>
ii  xdg-utils                                  1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt               1.2.1
ii  file              1:5.25-2
ii  python-debian     0.1.27
ii  python-debianbts  2.6.0
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information



More information about the Reportbug-maint mailing list