If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
- 1 Description
- 2 Features
- 3 Instalation
- 4 Usage examples
- 5 Repository
bugreporter is the tool that will help users submit bug reports to the developers, allowing even people with limited technical knowledge to fill out a relevant and useful bug report in a quick and simple way. This will reduce the delays, confusions and even frustrations between users and developers.
Helps the user find the relevant package for a selected application. There are two ways provided:
- app - click on a window and find out the app's name
- pkg - enter the application executable's name and find out it's package
Prints out general information about the user's system. This is helpful for providing maintainers with info or supplying it in the bug report.
There are two ways of submitting a bug report via this tool:
- interactive mode - the user is provided with the automatically found data for filling the report and for each she/he is asked if those are correct and if not they are provided with ways of selecting something else (with lists with valid options, "yes/no" prompts etc.)
- less interactive mode - here there are no "yes/no" prompts (except for the final submit question); instead, the user is provided with input prompts that have the automatically found data preselected. If the user enters some invalid data (e.g. an invalid component), he will be warned about it and prompted to select a valid one from a list before submitting the bug (this check is done locally via calls that get the Bugzilla instance's products, components etc)
Also, it does some minor checks/tweaks like: if the summary does not include the package name, it will be prepended to the summary by default to improve future searches.
Returns a list of bug reports that match the given package name and summary - outputted via an "in-house" pager wrote in Python.
When submitting a bug report, the tool first checks to see if there are any other similar reports already on Novell's Bugzilla. This is done via a query for all reports matching the given package and then a sort by relevance is applied following a truncation past a relevance threshold (which is relative to the maximum relevance of the found reports) in order to avoid false positives. The same is used for the query feature.
maintainer and bugowner retrieval
Using osc's python bindings the tool finds the development project & package (if any) for the given package and then uses the bugowner and maintainers for the devel project. If no devel project is found, the people assigned to the regular package are used. If no person is found, the Novell Bugzilla screening team is used as assignee.
Provides completion for subcommands and also for package names.
The tool uses osc's python bindings for this. No extra request for username and password given that they are already stored via osc.
One Click Install
Via OBS repo
gather system data
bugreporter gather > sysdata.txt
submit a bug report
bugreporter submit -p foo -s "foo crashes when it bars"
bugreporter submit -p foo
bugreporter query -p foo
bugreporter query -p foo -s "foo crashes"
find ls's package
bugreporter find pkg
Should follow like this:
Which binary's package do you want to find? You can enter either its name or its absolute path. --> ls The package for /bin/ls is coreutils.