On 17/07/10 08:12, Christoph Wickert wrote: ... > It refers to "bugs" and thus *covers* all bugs. You should first try to > fix it yourself and upstream the fix if it's not Fedora specific. If you > cannot fix the problem yourself, ask upstream for help. Many packagers are not programmers, and even those that are, work in entirely different worlds and are not familiar with thousands or 10,000 lines of code. To actually fix one bug might take work in spare over a month to make any progress at all. And it isn't obvious when something goes wrong in a library the app is using, whether it is the usage of the library, or the library itself that is at fault. Could rpm spec have a URL of upstream bug reporting system ? Or maybe just in package database: - link the upstream bug reporting information (ie how the upstream want to receive bug reports) - link to the bug reporting mechanism - whether upstream are happy to receive semi-automated crash traces ? Could abrt / tools list that as the first possible item in the "report this bug where" dialog ? On a different note: does there exist an open bug report system ? ie one were any upstream package can be added, and bug's reported there. Would it it be useful for abrt to automatically submit bugs to such a thing ? This wouldn't pollute either fedora's or upstream bug systems, yet it would capture vital info (backtrace) that would otherwise go missing. With some marketing, it might be possible for upstream developers to "want" to be subscribed to their apps external bug info ? David. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
