using bug 702723 as an example.. there's a lot of duplicate information there with no extra value. 1. the 'Comment ------' text is superflous. 2. The 'package: kernel' is pointless text. 3. If the architecture is the same as the original filed bug, don't bother reporting it. 4. Likewise for the OS Release. additionally, does abrt's comment box have a "this text will be filed in bugzilla" text ? If not, it should to dissuade people not to write garbage like "don't know" or "dakskmdlsamda"
Sorry for the "dakskmdlsamda" it was a testing bug, that I accidentally send to bz... - the comment field is a problem - some wants it to be mandatory - mainly C/C++ app maintainers and others don't need it at all - kernel + python
This bug has two parts. First one and easy one is remove PACKAGE, ARCH, OS_RELEASE and COMPONENT from initial report (they are superfluous). Done in my local git. commit 1a2d5297108e6a47d6e5ebda5e1d6f745d1dab54 Author: Nikola Pajkovsky <npajkovs> Date: Mon Jun 27 14:49:48 2011 +0200 [libreport] rhbz711591 - exclude information which are filled in bugzilla Signed-off-by: Nikola Pajkovsky <npajkovs> The second part is pretty hard, because I have to parse all history of the bug to determinate if e.g. the architecture was filled in the bug and then don't bother to report it. I put the request to my TODO list
You shouldn't need to parse the history, just read the 'platform' dropdown. If that is set to 'unspecified' then report it. If it is set to 'all' or the reporter is the same as what it is set to, don't report it.
Changing back to assigned as the second part is still not fixed.
Fixed in git commit 93c1aeb02086cfe5dbf6f9201956a7ab5fc1f631 Author: Jiri Moskovcak <jmoskovc> Date: Fri Dec 9 14:28:54 2011 +0100 rhbz: add the architecture to the comment only if it differs from initial comment rhbz#711591
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
libreport-2.0.8-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/libreport-2.0.8-4.fc16
Package libreport-2.0.8-4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.0.8-4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-17263/libreport-2.0.8-4.fc16 then log in and leave karma (feedback).
libreport-2.0.8-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.