[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#784696: marked as done (reportbug ignores -d - sends to Debian anyway)

Your message dated Sun, 3 Jan 2021 17:55:53 +0100
with message-id <ae32a750-f63d-7f98-c8dd-6756d9fc09dd@web.de>
and subject line Re: reportbug ignores -d - sends to Debian anyway
has caused the Debian Bug report #784696,
regarding reportbug ignores -d - sends to Debian anyway
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.)


-- 
784696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784696
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 6.6.3
Severity: normal

Dear Maintainer,

To explore how reportbug worked, and see what info was required to raise an ITP,
I ran:

reportbug -d --email scott@diskfish.org wnpp

I expected reportbug to send an email only to myself, according to the man page:

-d, --debug
 Don't send a real bug  report  to  Debian;  send  it  to  yourself
 instead.  This is primarily used for testing by the maintainer.

Instead, the bug was sent to myself and Debian BTS (raising #784370) and cc'd
to debian-devel.

Luckily, I was happy with the content, but if I had trusted -d to work as
described and entered some junk in reportbug, I would have made a mess.

Could the maintainer please clarify if the man page is incorrect, if reportbug
should in fact support this option, or if there is some user error on my part.


-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
DEBEMAIL="scott@diskfish.org"
DEBFULLNAME="Scott Wakeling"
INTERFACE="text"

** /home/scott/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text

-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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
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:
ii  claws-mail                           3.11.1-3
ii  debconf-utils                        1.5.56
pn  debsums                              <none>
pn  dlocate                              <none>
ii  emacs24-bin-common                   24.4+1-5
ii  file                                 1:5.22+15-2
ii  gnupg                                1.4.18-7
ii  python-gtk2                          2.24.0-4
pn  python-gtkspell                      <none>
pn  python-urwid                         <none>
ii  python-vte                           1:0.28.2-5
ii  sendmail-bin [mail-transport-agent]  8.14.4-8
ii  xdg-utils                            1.1.0~rc1+git20111210-7.4

Versions of packages python-reportbug depends on:
ii  apt               1.0.9.8
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 --- 
On Thu, 07 May 2015 Scott Wakeling wrote:
> 
> To explore how reportbug worked, and see what info was required to raise an ITP,
> I ran:
> 
> reportbug -d --email scott@diskfish.org wnpp
> 
> I expected reportbug to send an email only to myself, according to the man page:
> 
> -d, --debug
>  Don't send a real bug  report  to  Debian;  send  it  to  yourself
>  instead.  This is primarily used for testing by the maintainer.
> 
> Instead, the bug was sent to myself and Debian BTS (raising #784370) and cc'd
> to debian-devel.

> Could the maintainer please clarify if the man page is incorrect, if reportbug
> should in fact support this option, or if there is some user error on my part.

Thank you for the report. Since we cannot reproduce the bug, and no more
information has been provided in the last five years, I am assuming that
it either has been fixed or there was a user error. Closing this bug
now. Please file a new one if the problem turns up again.

--- End Message ---
Reply to: