abrt server report: 20130321

Jiri Moskovcak jmoskovc at redhat.com
Thu Mar 21 21:58:24 UTC 2013


On 03/21/2013 09:50 PM, Adam Jackson wrote:
> On Thu, 2013-03-21 at 19:16 +0100, Miloslav Trmač wrote:
>> On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak <jmoskovc at redhat.com> wrote:
>>>> How are problem reports like this updated?  How do I say "I built a Mesa
>>>> that I think fixes this problem, please change its state to MODIFIED"?
>>>
>>> - the state is synced with associated bugzilla tickets periodically
>>> - if the problem doesn't have bugzilla ticket it's not possible to change
>>> it's state, would like such option?
>>
>> I wouldn't worry about it too much as such.  Developers typically
>> track their bugs in bugzilla (and you've said that all reports
>> eventually get into bugzilla), encouraging everyone to have one more
>> system to track issues is just added overhead.
>
> That only works if abrt manages to figure out that a given problem
> matches a given bugzilla.
>
> And, uh, as a developer, I already deal with at least two bugzillas
> daily.  And I _like_ that abrt tracks reports outside of bugzilla.  I'm
> entirely comfortable with issuing updates with comments like "fixes
> crash report NNN, fixes bug MMM".
>
> But if I can't ever close old problem reports, then I can't use the
> crash reporting system to tell me what my current hottest problems are.
> So no, I really don't care about one more system to track issues,
> particularly not one that I can already log in to with existing Fedora
> credentials (OpenID even!).
>
> - ajax

- I agree, there is no reason to not provide an option to manually close 
the reports if abrt fails to match it with bugzilla or bodhi update

- that's actually on our todo for some time - allow developer to close 
the problem with some comment (a solution?) which then can be shown in 
abrt client when someone hits the same problem


--Jirka
>
>
>



More information about the devel mailing list