BugHelper

Differences between revisions 1 and 20 (spanning 19 versions)
⇤ ← Revision 1 as of 2006-12-31 14:16:23 →
Size: 1857
Editor: chello080109078174
Comment:
← Revision 20 as of 2007-02-06 18:35:20 → ⇥
Size: 2158
Editor: i59F77EE2
Comment: we don't have '-a' anymore
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * `bzr checkout http://bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main`  * `bzr branch http://bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main`
Line 7: Line 7:
 * Bughelper requires python-apt and python-libxml2

== Development and Discussion ==

 * [:/Dev]
 * https://lists.ubuntu.com/mailman/listinfo/bughelper
Line 10: Line 16:
The suite currently contains(*): ''You may want to start with the [:BugHelper/Tutorial:tutorial].''

Help on [:/Documentation/WritingClueFiles].

The suite currently contains:
Line 14: Line 24:
This tool collects bug numbers from Launchpad. You can either pass it 
 * a Launchpad bug list URL with `-l <URL>`		 This tool collects bug numbers from Launchpad. You can pass it
 * `-V` which will return the version number of the bughelper suite
 * `-l <URL>` for a Launchpad bug list URL
Line 18: Line 29:
It respects the switch `-a` which does not only read the bug numbers from one bug list page (which is currently limited to 75 per list), but uses the 'Next' links to traverse through the following pages also.
Line 21: Line 31:
   bugnumbers -a evolution    bugnumbers -p evolution
Line 28: Line 38:
 * `-A´ which lets it search through all the bug attachments with the mime type `text/plain`.  * `--version` which will return the version number of the bughelper suite
 * `-A` which lets it search through all the bug attachments with the mime type `text/plain`.
Line 31: Line 42:
   bugnumbers -a evolution
   bugnumbers -A -l https://launchpad.net/distros/ubuntu/+source/gcalctool/+bugs		    bughelper -p ubiquity
   bughelper -A -l https://launchpad.net/distros/ubuntu/+source/gcalctool/+bugs
Line 38: Line 49:
 * `-e <string>´ escapes a given string for use in XML files.
 * `-v <file>´ validates a given file against the clue file schema.		  * `-a <source package> <condition> <information>` adds a simple clue to an existing file or creates a new one.
 * `-e <string>` escapes a given string for use in XML files.
 * `-v <file>` validates a given file against the clue file schema.
Line 42: Line 54:
   bugxml -a totem "libxine.so" "This might be a xine problem. Ask the reporter to check with xine-ui."
   bugxml -v packages/ubiquity.info
Line 43: Line 57:
   bugxml -v packages/ubiquity.info
Line 47: Line 60:



== Comments ==

 * (*) Currently only in: https://launchpad.net/people/dholbach/+branch/bughelper/bughelper.dev --DanielHolbach [[DateTime(2006-12-31T13:15:27Z)]]		 ----
Go back to '''[:BugSquad]'''.[[BR]]
[:CategoryBugSquad]

bughelper is a tool written and maintained by Ubuntu's BugSquad.

Download

Development and Discussion

Documentation

You may want to start with the [:BugHelper/Tutorial:tutorial].

Help on [:/Documentation/WritingClueFiles].

The suite currently contains:

./bugnumbers

This tool collects bug numbers from Launchpad. You can pass it

  • -V which will return the version number of the bughelper suite

  • -l <URL> for a Launchpad bug list URL

  • a source package name like evolution

Examples: 

   bugnumbers -p evolution
   bugnumbers -l https://launchpad.net/distros/ubuntu/+source/gcalctool/+bugs

./bughelper

This tool searches through bugs and tries to find matches with data in .info files. It has the same functionality and switches as bugnumber. In addition to that it accepts

  • --version which will return the version number of the bughelper suite

  • -A which lets it search through all the bug attachments with the mime type text/plain.

Examples: 

   bughelper -p ubiquity
   bughelper -A -l https://launchpad.net/distros/ubuntu/+source/gcalctool/+bugs

./bugxml

This tool is primarily intended to help with the editing and creation of .info files. There are currently two use cases:

  • -a <source package> <condition> <information> adds a simple clue to an existing file or creates a new one.

  • -e <string> escapes a given string for use in XML files.

  • -v <file> validates a given file against the clue file schema.

Examples: 

   bugxml -a totem "libxine.so" "This might be a xine problem. Ask the reporter to check with xine-ui."
   bugxml -v packages/ubiquity.info
   bugxml -e This string has some weird characters like ä, ü and ö in it.

Go back to [:BugSquad].BR [:CategoryBugSquad]

BugHelper (last edited 2008-12-01 07:09:42 by i59F771D5)