writing-clue-files
⇤ ← Revision 1 as of 2007-02-06 18:47:26
1569
Comment:
|
2046
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
== The simple case == |
|
Line 6: | Line 8: |
sudo apt-get install bzr }}} |
sudo apt-get install bzr}}} |
Line 9: | Line 10: |
mkdir ~/bzr; cd ~/bzr }}} |
mkdir ~/bzr; cd ~/bzr}}} |
Line 12: | Line 12: |
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main }}} |
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main}}} |
Line 16: | Line 15: |
email=Daniel Holbach <daniel.holbach@ubuntu.com> }}} |
email=Daniel Holbach <daniel.holbach@ubuntu.com>}}} |
Line 19: | Line 17: |
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper-data/main bughelper-data }}} |
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper-data/main bughelper-data}}} |
Line 23: | Line 20: |
cd bughelper.main; ./bughelper -T totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug." -p totem }}} |
cd bughelper.main; ./bughelper -T totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug." -p totem}}} |
Line 26: | Line 22: |
./bugxml -a totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug." }}} |
./bugxml -a totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug."}}} 1. run {{{ cd ../bughelper-data; bzr unknowns}}} and see if your clue file is listed there. 1. If yes, run {{{ bzr add <filename>}}} |
Line 29: | Line 28: |
cd ../bughelper-data; bzr commit -m "added a totem clue" }}} |
bzr commit -m "added a totem clue"}}} |
Line 32: | Line 30: |
== Don't list certain bugs == If you add a clue that basically points out, that bug A (which contains a certain condition) is a duplicate of bug B, you probably don't want bughelper to list 'B' every time, you run that query. Therefore you can do the following {{{ ./bugxml -a totem "XRHFAOJAH.so" "This is a duplicate of Bug 13466." -d 13466}} |
The simple case
It's quite easy to write clue files yourself:
Get a Launchpad Account at https://launchpad.net/
Add your SSH keys to https://launchpad.net/~YOUR-LAUNCHPAD-ID/+editsshkeys
Install bzr, it's a nice and handy tool. We use it for developing BugHelper:
sudo apt-get install bzr
mkdir ~/bzr; cd ~/bzr
Get bughelper source:
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main
edit .bazaar/bazaar.conf and add something along the lines of:
[DEFAULT] email=Daniel Holbach <daniel.holbach@ubuntu.com>
Also get a fresh checkout of the clue files:
bzr checkout sftp://YOUR-LAUNCHPAD-ID@bazaar.launchpad.net/~bugsquad/bughelper-data/main bughelper-data
Edit ~/bughelper/config to contain the path to bughelper-data (you just checked out) in the Local-Packages-Dir: line.
Try the clue you want to add. Let's assume that you found out that totem bugs containing 'libxine.so' often are xine bugs.
cd bughelper.main; ./bughelper -T totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug." -p totem
Assuming this query find a lot of things, you might want to add it to the set of clues:
./bugxml -a totem "libxine.so" "You might want to ask the reporter to double check if xine-ui has the problem too. It might be a xine bug."
run
cd ../bughelper-data; bzr unknowns
and see if your clue file is listed there.If yes, run
bzr add <filename>
Commit your change:
bzr commit -m "added a totem clue"
- Done.
Don't list certain bugs
If you add a clue that basically points out, that bug A (which contains a certain condition) is a duplicate of bug B, you probably don't want bughelper to list 'B' every time, you run that query. Therefore you can do the following
BugHelper/doc/writing-clue-files (last edited 2008-08-06 17:00:36 by localhost)