Hi Jeff,
Good idea, also the opencv package would use this feature for its Python
programming examples. Current ABRT cannot ignore crashes based on paths,
so it must be developed.
Please file a RFE in Bugzilla, and include the filename mask(s) marking
the files you want to exclude. I think it
On Wed, Apr 14, 2010 at 21:53, Karel Klic kk...@redhat.com wrote:
Hi Jeff,
Good idea, also the opencv package would use this feature for its Python
programming examples. Current ABRT cannot ignore crashes based on paths,
so it must be developed.
Please file a RFE in Bugzilla, and include
On Wed, Apr 14, 2010 at 11:53 AM, Karel Klic kk...@redhat.com wrote:
Please file a RFE in Bugzilla, and include the filename mask(s) marking
the files you want to exclude. I think it will be something like:
/usr/lib/python2.6/site-packages/scipy/*/examples/*.py
do you want that in Fedora
Dne 14.4.2010 22:40, Jeff Spaleta napsal(a):
On Wed, Apr 14, 2010 at 11:53 AM, Karel Klickk...@redhat.com wrote:
Please file a RFE in Bugzilla, and include the filename mask(s) marking
the files you want to exclude. I think it will be something like:
Dne 14.4.2010 22:02, Mathieu Bridon napsal(a):
I'm not sure if that could be used for my own issues with ABRT, but
let me explain it.
When I'm developing a TG2 application, I sometimes get a traceback
(well, I'm not perfect :). ABRT sees the traceback, and wants me to
report a bug against
Ideally I think abrt's crash signature stuff ought to find two
characteristic failures are the same, and so send a reporter to
an existing bug report. Then that bug can be marked closed with
an annotation explaining what you need to install. (Of course,
it's also arguably wiser to have a hook in
On Wed, 2010-04-14 at 14:14 -0700, Roland McGrath wrote:
Ideally I think abrt's crash signature stuff ought to find two
characteristic failures are the same, and so send a reporter to
an existing bug report. Then that bug can be marked closed with
an annotation explaining what you need to
So I'm maintaining matplotlib and scipy.. which effectively allows
scientists to pretend they are programmers
So matplotlib includes a large selection of examples to read over as
documentation. Some of these example do some crazy complicated things
which make use of matplotlib and wont work out