| 192 |
- |
1 |
# Lines starting with # are ignored.
|
|
|
2 |
# Lines can be continued on the next line using trailing backslash.
|
|
|
3 |
#
|
|
|
4 |
# Format:
|
|
|
5 |
# %summary:: summary format
|
|
|
6 |
# section:: element1[,element2]...
|
|
|
7 |
# The literal text line to be added to Bugzilla comment. Can be empty.
|
|
|
8 |
# (IOW: empty lines are NOT ignored!)
|
|
|
9 |
#
|
|
|
10 |
# Summary format is a line of text, where %element% is replaced by
|
|
|
11 |
# text element's content, and [[...%element%...]] block is used only if
|
|
|
12 |
# %element% exists. [[...]] blocks can nest.
|
|
|
13 |
#
|
|
|
14 |
# Sections can be:
|
|
|
15 |
# - %summary: bug summary format string.
|
|
|
16 |
# - %attach: a list of elements to attach.
|
|
|
17 |
# - text, double colon (::) and the list of comma-separated elements.
|
|
|
18 |
# Text can be empty (":: elem1, elem2, elem3" works),
|
|
|
19 |
# in this case "Text:" header line will be omitted.
|
|
|
20 |
#
|
|
|
21 |
# Elements can be:
|
|
|
22 |
# - problem directory element names, which get formatted as
|
|
|
23 |
# <element_name>: <contents>
|
|
|
24 |
# or
|
|
|
25 |
# <element_name>:
|
|
|
26 |
# :<contents>
|
|
|
27 |
# :<contents>
|
|
|
28 |
# :<contents>
|
|
|
29 |
# - problem directory element names prefixed by "%bare_",
|
|
|
30 |
# which is formatted as-is, without "<element_name>:" and colons
|
|
|
31 |
# - %oneline, %multiline, %text wildcards, which select all corresponding
|
|
|
32 |
# elements for output or attachment
|
|
|
33 |
# - %binary wildcard, valid only for %attach section, instructs to attach
|
|
|
34 |
# binary elements
|
|
|
35 |
# - problem directory element names prefixed by "-",
|
|
|
36 |
# which excludes given element from all wildcards
|
|
|
37 |
#
|
|
|
38 |
# Nonexistent elements are silently ignored.
|
|
|
39 |
# If none of elements exists, the section will not be created.
|
|
|
40 |
|
|
|
41 |
# When we add a comment to an existing BZ, %summary is ignored
|
|
|
42 |
# (it specifies *new bug* summary field):
|
|
|
43 |
# %summary:: blah blah
|
|
|
44 |
|
|
|
45 |
# When dup is detected, BZ reporter adds a comment to it.
|
|
|
46 |
# This comment may interrupt an ongoing conversation in the BZ.
|
|
|
47 |
# (Three people independently filed a bug against abrt about this).
|
|
|
48 |
# Need to clearly explain what this comment is, to prevent confusion.
|
|
|
49 |
# Hopefully, this line would suffice:
|
|
|
50 |
Similar problem has been detected:
|
|
|
51 |
|
|
|
52 |
# If user filled out comment field, show it:
|
|
|
53 |
:: %bare_comment
|
|
|
54 |
|
|
|
55 |
# var_log_messages has too much variance (time/date),
|
|
|
56 |
# we exclude it from message so that dup message elimination has more chances to work
|
|
|
57 |
:: \
|
|
|
58 |
reporter,-pkg_arch,-pkg_epoch,-pkg_name,-pkg_release,-pkg_version,\
|
|
|
59 |
-pkg_vendor,-pkg_fingerprint,-component,-architecture,-extra-cc,\
|
|
|
60 |
-analyzer,-count,-duphash,-uuid,-abrt_version,\
|
|
|
61 |
-username,-hostname,-os_release,-last_occurrence,-ureports_counter,\
|
|
|
62 |
-time,-pid,-pwd,\
|
|
|
63 |
-var_log_messages,-type,-core_backtrace,-executable,-tid,\
|
|
|
64 |
%oneline
|