abrt finding closed bugs
Jiri Moskovcak
jmoskovc at redhat.com
Sat May 28 07:00:23 UTC 2011
On 05/28/2011 07:48 AM, Braden McDaniel wrote:
>> From abrt:
>
> Logging into Bugzilla at https://bugzilla.redhat.com
> Checking for duplicates
> Bug is already reported: 701604
> Logging out
> Status: CLOSED INSUFFICIENT_DATA https://bugzilla.redhat.com/show_bug.cgi?id=701604
>
> Should this have resulted in the bug being reopened with the new stack
> trace attached?
- this is hard to decide, in this case even the original backtrace was
good (despite the warnings at the beginning) and developer closed it as
INSUF. DATA because he wanted more than just a backtrace, so if ABRT
would re-open it and just add another backtrace it would probably just
lead to another pi**ed maintainer. It could re-open the bug in case the
previous bt is bad, but even then we can't be sure the new bt is what
maintainer wants. In this case I would just go to that bug, add the
comments and re-open the bug manually.
Jirka
More information about the devel
mailing list