Differences between revisions 15 and 16
Revision 15 as of 2007-04-23 08:09:09
Size: 4042
Editor: chello080109078174
Revision 16 as of 2007-04-30 07:24:33
Size: 4057
Editor: i59F708AA
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
bzr checkout s
bzr checkout s python-launchpad-bugs
bzr checkout s
bzr checkout s python-launchpad-bugs
Line 25: Line 25:
bzr checkout bzr checkout


Since 7.04 (Feisty Fawn)

It's packaged in universe, so installing is easy:

{{{sudo apt-get install bughelper }}}

On other systems

These instructions assume that you have a [ launchpad] account and that you have bzr [ installed and configured].

Get the bughelper source (also python-launchpad-bugs which was split off during development of gutsy) from Launchpad:

bzr checkout s
bzr checkout s python-launchpad-bugs
cd bughelper.main
ln -s ../python-launchpad-bugs/launchpadBugs

If you do not have a [ launchpad] account, you can get the source via:

bzr checkout

This is also the best option if you want to participate in bughelper development, or just test the bleeding edge.

Initial configuration

When you run bughelper for the first time it will create a ~/.bughelper/ directory and a ~/.bughelper/config file. It will also check out a copy of the latest shared clue files from the bughelper project on Launchpad.

A simple search

When you've downloaded the shared clue files you are ready to start searching for bugs fitting certain pre-defined patterns.

Try it first with a small package:

{{{$ bughelper -p vino }}}

The result should be a listing of vino bugs with their status and a suggestion of how they may be related to other known bugs. This type of search, looking for known patterns in open bugs, can be useful in finding new instances of known duplicates.

However, sometimes you may be approaching the problem form the other direction. You are working with a given bug and you want to look for similar bugs, either open or closed. In that case you'll want to define your own search terms:

{{{bughelper -T vino "crash" "A CRASHER BUG" -p vino }}}

Where the first entry in quotes is the string you want to search for and the second is the information that bughelper presents on finding it. By changing the search string you can explore the bug reports filed against a given package for common traits. Note that on larger packages each search will take some time.

Clue files

Once you have found a useful search pattern, you'll probably want to store it for future use, and for that we use clue files. To store the search you have just completed, use bugxml:

{{{bugxml -a vino "crash" "A CRASHER BUG" }}}

This will create a new XML file with the simple clue defined by the search string and text output, like:

{{{<?xml version="1.0"?> <clues version="0.1">

  • <clue>

    • <contains>

      • <op>crash</op>

      </contains> <info>A CRASHER BUG</info>


</clues> }}}

Note: creating clues with bugxml requires that you have added a local package directory to your ~/.bughelper/config file.

Once a clue file has been created, bughelper will include the information it contains in future searches. The above example represents just a simple search string, but you can get more targeted searches by adding more conditions to your clue files. Read [:BugHelper/doc/writing-clue-files:doc/writing-clue-files] for further information on file structure and sharing the search data with others.

Further reading

  1. [:BugHelper/doc/options] - Command line options explained

  2. [:BugHelper/doc/writing-clue-files] - Help on writing your own clues

  3. [:BugHelper/doc/components] - Overiew of component applications of bughelper

Go back to [:BugHelper].BR CategoryBugSquad

BugHelper/doc/getting-started (last edited 2010-01-25 21:19:35 by 39)