Your message dated Mon, 4 Jan 2010 12:00:12 +0100
with message-id <[email protected]>
and subject line Re: [Reportbug-maint] Bug#488476: reportbug: request interface
to browse / search 1800+ bugreports
has caused the Debian Bug report #488476,
regarding reportbug: request interface to browse / search 1800+ bugreports
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 [email protected]
immediately.)
--
488476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488476
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 3.41
Severity: wishlist
When submitting a bugreport, reportbug asks to scan the existing
reports. I'm happy to do so. But scanning all reports becomes a tedious
job. E.g. in the install reports, more than 1800 entries are present.
I would appreciate some means to help me find related issues. The "f"
menu option by reportbug seems to look only in the titles of reports
that are currently displayed. So, it allows you to search in the titles
of 20 tickets rather than in 1800 tickets.
A mechanism to filter out major categories of reports would also be
helpful. E.g. I was pretty confident that a particular problem was
specific to "Lenny", and therefore I would like to filter out all
reports not related to "Lenny".
-- Package-specific info:
** Environment settings:
INTERFACE="urwid"
** /home/paul/.reportbugrc:
reportbug_version "3.41"
mode standard
ui urwid
email "[email protected]"
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (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/bash
Versions of packages reportbug depends on:
ii apt 0.7.14+b1 Advanced front-end for dpkg
ii python 2.5.2-1 An interactive high-level object-o
ii python-central 0.6.7 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Paul,
thanks for your report.
On Sun, Jun 29, 2008 at 09:23, Paul van Haren <[email protected]> wrote:
> When submitting a bugreport, reportbug asks to scan the existing
> reports. I'm happy to do so. But scanning all reports becomes a tedious
> job. E.g. in the install reports, more than 1800 entries are present.
that's why we provide the filtering option :)
> I would appreciate some means to help me find related issues. The "f"
> menu option by reportbug seems to look only in the titles of reports
yes, only the information we download from the BTS at that time, so
the title: we cannot download the whole bug report for all the bugs of
a package, it could be possible for pkgs with few bugs (but what
number of bugs precisely?) but fro 1800 it's simply impossible. You
need a search engine for that.
> that are currently displayed. So, it allows you to search in the titles
> of 20 tickets rather than in 1800 tickets.
No, the filtering options is filtering the whole set of bugs
downloaded from the BTS.
> A mechanism to filter out major categories of reports would also be
how can we group bugs in categories? we are grouping on severities (as
BTS does by default), else there is no reliable way to group bugs.
> helpful. E.g. I was pretty confident that a particular problem was
> specific to "Lenny", and therefore I would like to filter out all
> reports not related to "Lenny".
then filter for Lenny, but it have to be in the subject, as explained above.
That said, I'm closing this report.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
