Bug#859450: marked as done (reportbug: first reportbug with package after fresh install crashes)
Your message dated Thu, 28 Jan 2021 23:00:37 +0100
with message-id <98a9d049-e4b0-893c-7245-495436c5f32f@web.de>
and subject line Re: reportbug: first reportbug with package after fresh install crashes
has caused the Debian Bug report #859450,
regarding reportbug: first reportbug with package after fresh install crashes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
859450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859450
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: reportbug: first reportbug with package after fresh install crashes
- From: ben hildred <42656e@gmail.com>
- Date: Mon, 03 Apr 2017 10:56:26 -0600
- Message-id: <20170403165626.2085.50468.reportbug@d199.hildred.us>
Package: reportbug
Version: 6.6.3
Severity: normal
Dear Maintainer,
* What led up to the situation?
netboot test install (minimal testing)
* What exactly did you do (or not do) that was effective (or
ineffective)?
aptitude install reportbug
reportbug installation-reports
* What was the outcome of this action?
crash during bug submission (SMTP)
* What outcome did you expect instead?
success or error
if reportbug is run without a package name and the initial questions are answerd first the problem goes away.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/ben/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text
realname "ben hildred"
email "42656e@gmail.com"
no-cc
header "X-Debbugs-CC: 42656e@gmail.com"
smtphost reportbug.debian.org
-- System Information:
Debian Release: 8.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reportbug depends on:
ii apt 1.0.9.8.4
ii python 2.7.9-1
ii python-reportbug 6.6.3
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 file 1:5.22+15-2+deb8u3
ii gnupg 1.4.18-7+deb8u3
pn postfix | exim4 | mail-transport-agent <none>
pn python-gtk2 <none>
pn python-gtkspell <none>
pn python-urwid <none>
pn python-vte <none>
pn xdg-utils <none>
Versions of packages python-reportbug depends on:
ii apt 1.0.9.8.4
ii python-debian 0.1.27
ii python-debianbts 1.12
pn python:any <none>
python-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 859450-done@bugs.debian.org, ben hildred <42656e@gmail.com>
- Subject: Re: reportbug: first reportbug with package after fresh install crashes
- From: Nis Martensen <nis.martensen@web.de>
- Date: Thu, 28 Jan 2021 23:00:37 +0100
- Message-id: <98a9d049-e4b0-893c-7245-495436c5f32f@web.de>
- In-reply-to: <20170403165626.2085.50468.reportbug@d199.hildred.us>
- References: <20170403165626.2085.50468.reportbug@d199.hildred.us> <20170403165626.2085.50468.reportbug@d199.hildred.us>
Version: 7.9.0
On 03 Apr 2017 ben hildred wrote:
> Package: reportbug
> Version: 6.6.3
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
> netboot test install (minimal testing)
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> aptitude install reportbug
> reportbug installation-reports
> * What was the outcome of this action?
> crash during bug submission (SMTP)
> * What outcome did you expect instead?
> success or error
There are several things contributing:
1. No MTA installed or MTA only configured for local delivery
2. reportbug using the MTA by default if unconfigured
3. reportbug not detecting the 'missing MTA' case.
When a user reports a bug on reportbug, they are presented a list of
"common issues" which mentions the local delivery thing at the very top,
so I don't think this report is meant to reiterate this. I interpret it
as more likely referring to the third part, which has been fixed in
reportbug 7.9.0.
--- End Message ---
Reply to: