From Mageia wiki
Jump to: navigation, search
Drakconf multiflag.png
Other languages

Deutsch ; Englisch


This page list the powerful tools that can help you every days.


Bugzilla triage plugin

Capture-mageia-bugscript.png

Mageia bugscript, is a Greasemonkey script for Firefox (works maybe on other browser too). It adds buttons to the bugzilla which will help you to make some works faster. Like add some text automatically, add keywords, set the assigned, get the list of all commiters, open a tab of the svn log, set the status or make multiple thinks in only one time.


Support or enhancement request, bugs report about the script itself, should be filed on the dedicated bug, a, or send to the author (aka leuhmanu).

Test Bug: https://bugs.mageia.org/show_bug.cgi?id=3270

Add stock responses

see Stock responses for details

Maintdb

Use an external api to get the maintainer or committers (and replace the Mageia id, by something that bugzilla know) of the package in the rpm field. If there is maintainer the function will add it in the assigned field, and if not it will add the committers in the CC list.
see examples: mplayer (set to nobody) and rpm with a maintainer.
The server side api use the mageia database and some internal list to have something working for the bugzilla.

Svn

This function list the committers of the package, it will add the result in the CC field with the number of change for each people.

Lsvn

This function will open a new tab which go on the svn log of the package or the release of the bug. (example for firefox on mga1)
It can be useful to check quickly where changed the package in the last time.


There is a GUI for all these things in this website: http://freeshell.de/~manu67/mageia/intcom.cgi
(in the script it search the info on the textarea box (rpm package, version, etc) so it's automatic)

Link-widgets Extension

This Firefox extension allow you to use 'alt + page up/down' do browse on search list (and also on ml archive or some other website)

Links

Since the greasemonkey script do that, it's useless for triaging in the bugzilla. But it can help for others work.


Stock responses

  • X logs, add the NEEDINFO keyword and the stock response:
Thanks for the bug report.  
We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance. 
  • Ask for GDB strace (don't valid anymore since mga2)
Check ALL FIXME
1) enable the 'core release debug'
2) install the following packages: FIXME-debug
3) run the following command from a terminal:
  gdb -q FIXME 2>&1 | tee debug.txt
4) then type 'run'
(if it ask for missing packages, install them)
5) when it segfaults, type 'bt'
6) attach the file debug.txt to this bug


* Close as duplicate:
<pre>Thanks for the bug report.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.
In general it is welcome to search for existing reports first to avoid filing duplicates.
  • Ask for the debug report of drakx-installer:
Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.gz as an attachment ?
If you don't have the file, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter.
It will put report.bug on the floppy/key.
  • Stock response for a no answer bug:
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as OLD.
  • Upstream bug:
Hi, thanks for reporting this bug.
We found that this bug has been already registered in the upstream database \n\nand believe that it is more appropriate to let it be resolved upstream.
  • Reminder stock response:
Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
  • Closing as End Of life:
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. 
As a result we are setting this bug to CLOSED:WONTFIX.
  • Stock response for triaging a bug:
Hi, thanks for reporting this bug.
Assigned to the package maintainer.
(Please set the status to 'assigned' if you are working on it)
  • Same as before but if there is no maintainer (or set to nobody)
Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.
(Please set the status to 'assigned' if you are working on it)
  • Stock comment for a QA validation:
Suggested Advisory:
-------------
This update addresses the folloving CVE:
- CVE
bug url:

Updated PACKAGE fix...

-------------
SRPM: 
Could sysadmin please push FIXME from core/updates_testing to core/updates
Thankyou!


Links to other Bug Squad tools

Tools for maintenance of bug reports

Trash

Return to the Bug Squad Portal