RFE: Rank bugs by number of dupes

[Henrik Nilsen Omma]

When starting work to triage an unfamiliar package it is useful to start by looking at the bugs most likely to have dupes.

[Daniel Holbach (dholbach)]

Thanks for your suggestion. Do you want to list ALL bugs and rank by number of dupes or just the ones that bughelper has clues about?

[Henrik Nilsen Omma (henrik)]

When starting work on a new package I want to have a list of ALL bugs ever filed on <package> (including closed ones) with more than N(~5) duplicates. Then I will look at those to see which ones may still generate dupes and use that as the basis for my cluefile for <package>.

THEN I will apply bughelper to all the untriaged bugs with my new cluefile and see if any new dupe candidates come up.

[Daniel Holbach (dholbach)]

Good idea. We need command line switches for that. Can you think of what would you would type in (in the future) to achieve this?

[Henrik Nilsen Omma (henrik)]

-dg5 = dupes GT 5
-dl5 = dupes LT 5

?

[Daniel Holbach (dholbach)]

Ok with me.

[Vassilis Pandis (pandisv)]

The regular expression needs a bit of fixing, but otherwise I _guess_ this should be alright. Patch with -p1

[Áron Sisak (asisak)]

What do you think about something like
--duplicates 5- (at least 5 duplicates)
--duplicates -100 (at most 100 duplicates)
--duplicates 3-6 (at least 3 and at most 6 duplicates)

Of course a short option would also be great for this.

[Markus Korn (thekorn)]

This patch against bughelper.main r125 adds a "--nd" option to ./bughelper. This option filters the bugs by given number of duplicates.

Example:
$ ./bughelper -p bughelper --nd "<2"
(less than 2 dups)

$ ./bughelper -p bughelper --nd ">2"
(more than 2 dups)

$ ./bughelper -p bughelper --nd 2
(2 dups)

Please review. As it's using RegEx to get the number of duplicates it needs intensive testing.

Markus

[Daniel Holbach (dholbach)]

Moving back to 'In Progress'. I updated the patch to apply against 152, but it does not seem to work for me.

./bughelper -p gtk+2.0 --nd ">2"
gives
http://launchpad.net/bugs/83278 [gnome-panel upstream: Unconfirmed/Unknown][gtk+2.0 Ubuntu: Fix Committed/Low] - This is probably a dup of bug #82280

[Daniel Holbach (dholbach)]

Ok, the full output is:

daniel@bert:~/bzr/bughelper.main$ ./bughelper -p gtk+2.0 --nd ">2"
Checked at ['/home/daniel/bzr/bughelper-data/ufraw.info', '/home/daniel/.bughelper/packages/ufraw.info'] - no clues found.
Check README on how to create one using the bugxml(1) command.
Checked at ['/home/daniel/bzr/bughelper-data/wifi-radar.info', '/home/daniel/.bughelper/packages/wifi-radar.info'] - no clues found.
Check README on how to create one using the bugxml(1) command.
http://launchpad.net/bugs/83278 [gnome-panel upstream: Unconfirmed/Unknown][gtk+2.0 Ubuntu: Fix Committed/Low] - This is probably a dup of bug #82280

No bugs found.
daniel@bert:~/bzr/bughelper.main$

Is that intended?

[Markus Korn (thekorn)]

Oh, sorry, I somehow lost four lines of code.

This new patch against bughelper.main r152 solves this.

As discussed with dholbach, we should move that --nd option to bugnumbers and generally doing all filtering in BugList

Markus

[Daniel Holbach (dholbach)]

------------------------------------------------------------
revno: 164
committer: Daniel Holbach <email address hidden>
branch nick: bughelper.main
timestamp: Wed 2007-04-25 08:28:49 +0200
message:
  committed bughelper bits of Markus Korn's patch for bug 79140