<br><br><div class="gmail_quote">2010/10/20 "Jóhann B. Guđmundsson" <span dir="ltr"><<a href="mailto:johannbg@gmail.com">johannbg@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"> On 10/19/2010 07:00 PM, Michael Schwendt wrote:<br>
> In the opposite direction it doesn't work well either.<br>
> ABRT submits crash reports in Fedora's bugzilla even if 3rd party add-ons<br>
> are the culprit. All the Fedora packager can do is to set CLOSED/CANTFIX<br>
> with a request to submit a bug report in a 3rd party bug tracker. And if<br>
> that isn't done (which happens regularly IMO), 3rd party packagers would<br>
> need to hunt down such reports in Fedora's bugzilla.<br>
<br>
</div>Hum I thought you could point abrt to whatever bugzilla you wanted<br>
atleast it should not be that difficult to change it however I'm not so<br>
sure if it can deal with sending to two different bugzillas as is needed<br>
in the case of Fedora+RpmFusion which I'm guessing it does not based on<br>
your reply.<br>
<br>
However I think its a bit odd if abrt just sends the report to our<br>
bugzilla if the component does not exist there.<br>
<font color="#888888"><br>
JBG<br>
</font><div><div></div><div class="h5">--</div></div></blockquote><div> </div><div>abrt offers at least two places where the bug can be reported (bugzila and logger, from memory). the question is: can more targets be added? if yes, how?</div>
<div><br></div><div>ps</div><div>anybody can tell what "logger" is?</div></div>