[ABRT PATCH] stop using the hardcoded event list, use workflows instead rhbz#866027

Jakub Filak jfilak at redhat.com
Tue Jul 16 12:27:50 UTC 2013


Pushed


On Tue, 2013-07-16 at 13:47 +0200, Jiri Moskovcak wrote:
> Signed-off-by: Jiri Moskovcak <jmoskovc at redhat.com>
> ---
>  src/plugins/ccpp_event.conf   | 2 +-
>  src/plugins/koops_event.conf  | 2 +-
>  src/plugins/python_event.conf | 2 +-
>  src/plugins/vmcore_event.conf | 2 +-
>  src/plugins/xorg_event.conf   | 2 +-
>  5 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/src/plugins/ccpp_event.conf b/src/plugins/ccpp_event.conf
> index aa8cdb3..1dacbeb 100644
> --- a/src/plugins/ccpp_event.conf
> +++ b/src/plugins/ccpp_event.conf
> @@ -90,7 +90,7 @@ EVENT=analyze_CCpp analyzer=CCpp
>  
>  # Reporting of C/Cpp problems
>  EVENT=report-gui analyzer=CCpp
> -        report-gtk -e report_uReport -e analyze_CCpp -e "collect_*" -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> +        report-gtk -- "$DUMP_DIR"
>  
>  EVENT=report-cli analyzer=CCpp
>          report-cli -e report_uReport -e analyze_CCpp -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> diff --git a/src/plugins/koops_event.conf b/src/plugins/koops_event.conf
> index 9966775..78f8f4a 100644
> --- a/src/plugins/koops_event.conf
> +++ b/src/plugins/koops_event.conf
> @@ -30,7 +30,7 @@ EVENT=post_report analyzer=Kerneloops
>  
>  # Automatic/simple GUI-based kernel oopses reporting will do this:
>  EVENT=report-gui analyzer=Kerneloops
> -        report-gtk -e report_uReport -e "collect_*" -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> +        report-gtk -- "$DUMP_DIR"
>  
>  EVENT=report-cli analyzer=Kerneloops
>          report-cli -e report_uReport -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> diff --git a/src/plugins/python_event.conf b/src/plugins/python_event.conf
> index 3a45373..f211b30 100644
> --- a/src/plugins/python_event.conf
> +++ b/src/plugins/python_event.conf
> @@ -25,7 +25,7 @@ EVENT=post_report analyzer=Python
>  
>  # Reporting of python exceptions
>  EVENT=report-gui analyzer=Python component!=anaconda
> -        report-gtk -e report_uReport -e "collect_*" -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> +        report-gtk -- "$DUMP_DIR"
>  
>  EVENT=report-cli analyzer=Python component!=anaconda
>          report-cli -e report_uReport -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> diff --git a/src/plugins/vmcore_event.conf b/src/plugins/vmcore_event.conf
> index 5d2d099..68e1d24 100644
> --- a/src/plugins/vmcore_event.conf
> +++ b/src/plugins/vmcore_event.conf
> @@ -24,7 +24,7 @@ EVENT=report_uReport analyzer=vmcore
>          /usr/libexec/abrt-action-ureport
>  
>  EVENT=report-gui analyzer=vmcore
> -    report-gtk -e analyze_VMcore -e report_uReport -e "collect_*" -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> +    report-gtk -- "$DUMP_DIR"
>  
>  EVENT=report-cli analyzer=vmcore
>      report-cli -e analyze_VMcore -e report_uReport -e report_Bugzilla -e post_report -- "$DUMP_DIR"
> diff --git a/src/plugins/xorg_event.conf b/src/plugins/xorg_event.conf
> index 71ca171..1bd7617 100644
> --- a/src/plugins/xorg_event.conf
> +++ b/src/plugins/xorg_event.conf
> @@ -22,7 +22,7 @@ EVENT=report_Bugzilla analyzer=xorg
>  
>  # Automatic/simple GUI-based xorg problems reporting will do this:
>  EVENT=report-gui analyzer=xorg
> -	report-gtk -e report_Bugzilla -- "$DUMP_DIR"
> +	report-gtk -- "$DUMP_DIR"
>  
>  EVENT=report-cli analyzer=xorg
>  	report-cli -e report_Bugzilla -- "$DUMP_DIR"




More information about the Crash-catcher mailing list