REPORT_OPENSUSE_BUGZ(5)

💖 REPORT_OPENSUSE_BUGZ(5) 💖

LIBREPORT MANUAL, bestie — welcome to the report_opensuse_bugzilla.conf group chat. It's giving config-file main character energy. ✨

🌸 NAME 🌸

report_opensuse_bugzilla.conf — a configuration file for libreport. That's the whole name vibe. 🫶

✨ DESCRIPTION ✨

This configuration file specifies which of the reporting work flow definitions are applicable for all problems types on openSUSE. Yes, all problems types — we don't rewrite the lore. 💅

All applicable reporting work flows are presented to users in User Interface as possibilities for processing of all problem types. It's literally "here are your options, choose your workflow." 🦋

This configuration file consists of one condition per line. Periodt.

Each condition line must start with EVENT=workflow_NAME, where "workflow_" is a constant prefix and "workflow_NAME" is the base name of the path to the reporting work flow configuration file. The prefix is part of the ritual, bestie. 🕯️

The rest of the condition line has one of these forms:

• VAR=VAL
• VAR!=VAL
• VAL~=REGEX

where VAR is a name of problem directory element to be checked — for example, "executable", "package", hostname" etc. 🙈 A condition may consist of as many element checks as it is necessary, so stack 'em if you need to. No cap.

🎀 EXAMPLES 🎀

Condition line:

EVENT=workflow_openSUSEBugzillaCCpp analyzer=Python

The condition line above expects the existence of /usr/share/libreport/workflows/workflow_openSUSEBugzillaPython.xml. Yup, that exact path — don't come for me, I'm just reporting the config lore. 🦋

🦋 SEE ALSO 🦋

• report-gtk(1)

👑 AUTHOR 👑

• ABRT team

---

Okay that's the whole page! This one is from LIBREPORT 2.17.15, dated 07/15/2024, and it ate fr fr. Mwah 💋✨