Your message dated Fri, 13 Jan 2017 17:56:06 -0500 with message-id <cab4xwxyfssjsq86udqr33koywspcpj2cn8hpy8zbfg32mr0...@mail.gmail.com> and subject line Re: Bug#851319: reportbug: Reportbug should keep a list of reported bugs for review later has caused the Debian Bug report #851319, regarding reportbug: Reportbug should keep a list of reported bugs for review later 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 ow...@bugs.debian.org immediately.) -- 851319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: reportbug Version: 7.1.2 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When I use reportbug I get frustrated that I can't easily see a list of all the bugs I have reported. * What exactly did you do (or not do) that was effective (or ineffective)? I check the bugreport on email... * What was the outcome of this action? Following up bugreports via mail can be a bit tedious... * What outcome did you expect instead? If reportbug is started without parameters it should present a list of packages you already have reported bugs on. It should also display their status. It would be nice if I the reportee could cathegorize bugs in "important", "overdue", "forgotten" or something simmilar independent from the real bugreport. That way I can easily keep an eye on bugs that are important to me, it would also be easier to add info to exsiting bugs in case you forget about them etc... For example if a package is updated a bug may be resolved but not marked as such. -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/waxhead/.reportbugrc: reportbug_version "6.4.4" mode standard ui text realname "Svein Engelsgjerd" email "waxh...@online.no" no-cc header "X-Debbugs-CC: waxh...@online.no" smtphost reportbug.debian.org -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.4~beta2 ii python3-reportbug 7.1.2 pn python3: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.88-2 ii exim4-daemon-light [mail-transport-agent] 4.88-2 ii file 1:5.29-2 ii gir1.2-gtk-3.0 3.22.5-1 ii gir1.2-vte-2.91 0.46.1-1 ii gnupg 2.1.17-2 ii python3-gi 3.22.0-2 pn python3-gtkspellcheck <none> pn python3-urwid <none> ii xdg-utils 1.1.1-1 Versions of packages python3-reportbug depends on: ii apt 1.4~beta2 ii file 1:5.29-2 ii python3-debian 0.1.29 ii python3-debianbts 2.6.1 ii python3-requests 2.12.4-1 pn python3:any <none> python3-reportbug suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---control: tags -1 +wontfix On Fri, Jan 13, 2017 at 5:46 PM, Svein Engelsgjerd <waxh...@online.no> wrote: > If reportbug is started without parameters it should present a list of > packages you already have reported bugs on. > It should also display their status. > It would be nice if I the reportee could cathegorize bugs in "important", > "overdue", "forgotten" or something simmilar independent from the real > bugreport. > That way I can easily keep an eye on bugs that are important to me, it would > also be easier to add info to exsiting bugs in case you forget about them > etc... > For example if a package is updated a bug may be resolved but not marked as > such. nope the purpose of reportbug is to... report bugs, not being a dashboard for reported bug or a query mining tool. use bts show from:waxh...@online.no for what you need or the various web pages showing the same information -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
--- End Message ---
