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

Bug#795517: marked as done (reportbug: gtk2 frontend is usless with -N)

Your message dated Sat, 11 Jul 2020 00:36:04 +0200
with message-id <13c21d65-58e4-11cf-4262-3014786abe56@web.de>
and subject line Re: reportbug: gtk2 frontend is usless with -N
has caused the Debian Bug report #795517,
regarding reportbug: gtk2 frontend is usless with -N
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.)


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

`reportbug -N $bug_number` displays the bug report before allowing the user to
add information. This is of some minor value in making sure you have the
correct bug number. However if you are using the gtk2 front end the only
options at this point are to show the full bug in the web browser (which I
don't need as I already have it open, how do you think I found the bug number?)
or to quit.



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/ben/.reportbugrc:
reportbug_version "6.4.4"
mode advanced
ui gtk2
realname "Ben Hildred"
email "42656e@gmail.com"
no-cc
header "X-Debbugs-CC: ben@hildred.us"
smtphost reportbug.debian.org

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.0.0-2-686-pae (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/dash
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt               1.0.9.10
ii  python            2.7.9-1
ii  python-reportbug  6.6.4
pn  python:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                               <none>
ii  debconf-utils                            1.5.57
ii  debsums                                  2.1.2
ii  dlocate                                  1.02+nmu3
pn  emacs23-bin-common | emacs24-bin-common  <none>
ii  file                                     1:5.22+15-2
ii  gnupg                                    1.4.19-3
ii  pgpgpg [pgp]                             0.13-9
ii  python-gtk2                              2.24.0-4
ii  python-gtkspell                          2.25.3-13
ii  python-urwid                             1.2.1-2+b1
ii  python-vte                               1:0.28.2-5
ii  sendmail-bin [mail-transport-agent]      8.14.9-4
ii  xdg-utils                                1.1.0~rc1+git20111210-7.4

Versions of packages python-reportbug depends on:
ii  apt               1.0.9.10
ii  python-debian     0.1.27
ii  python-debianbts  1.13
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 7.7.0

On Fri, 14 Aug 2015 14:35:15 -0600 Ben Hildred <42656e@gmail.com> wrote:
> Package: reportbug
> Version: 6.6.4
> Severity: normal
> 
> `reportbug -N $bug_number` displays the bug report before allowing the user to
> add information. This is of some minor value in making sure you have the
> correct bug number. However if you are using the gtk2 front end the only
> options at this point are to show the full bug in the web browser (which I
> don't need as I already have it open, how do you think I found the bug number?)
> or to quit.

Thank you for the report. This is fixed in reportbug 7.7.0.

--- End Message ---
Reply to: