BugHelper

Differences between revisions 1 and 16 (spanning 15 versions)
Revision 1 as of 2006-12-31 14:16:23
Size: 1857
Editor: chello080109078174
Comment:
Revision 16 as of 2007-01-29 16:28:03
Size: 2159
Editor: c-24-21-235-175
Comment: Added bughelper mailing list which replaced the bugsquad mailing list
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].''

The suite currently contains:
Line 14: Line 22:
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 27:
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. It respects the switch `-a` which not only reads 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 28: Line 37:
 * `-A´ which lets it search through all the bug attachments with the mime type `text/plain`.  * `-V` which will return the version number of the bughelper suite
 * `-a` which will NOT limit the search to just the first 75 bugs
* `-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 -a 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.
 * `-e <string>` escapes a given string for use in XML files.
 * `-v <file>` validates a given file against the clue file schema.
Line 47: Line 58:



== 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].

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

It respects the switch -a which not only reads 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.

Examples:

   bugnumbers -a 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

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

  • -a which will NOT limit the search to just the first 75 bugs

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

Examples:

   bughelper -a 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:

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

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

Examples:

   bugxml -e This string has some weird characters like ä, ü and ö in it.
   bugxml -v packages/ubiquity.info


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

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