xXx

Hexid M1n1 5h3ll MobiLe

proc/2213/cwd/proc/30499/cwd/etc/libreport/plugins/_[ Not.Writable ]

File://proc/2213/cwd/proc/30499/cwd/etc/libreport/plugins/mantisbt_formatdup.conf

# Lines starting with # are ignored.
# Lines can be continued on the next line using trailing backslash.
#
# Format:
# %summary:: summary format
# section:: element1[,element2]...
# The literal text line to be added to Bugzilla comment. Can be empty.
# (IOW: empty lines are NOT ignored!)
#
# Summary format is a line of text, where %element% is replaced by
# text element's content, and [[...%element%...]] block is used only if
# %element% exists. [[...]] blocks can nest.
#
# Sections can be:
# - %summary: bug summary format string.
# - %attach: a list of elements to attach.
# - text, double colon (::) and the list of comma-separated elements.
#   Text can be empty (":: elem1, elem2, elem3" works),
#   in this case "Text:" header line will be omitted.
#
# Elements can be:
# - problem directory element names, which get formatted as
#   <element_name>: <contents>
#   or
#   <element_name>:
#   :<contents>
#   :<contents>
#   :<contents>
# - problem directory element names prefixed by "%bare_",
#   which is formatted as-is, without "<element_name>:" and colons
# - %oneline, %multiline, %text wildcards, which select all corresponding
#   elements for output or attachment
# - %binary wildcard, valid only for %attach section, instructs to attach
#   binary elements
# - problem directory element names prefixed by "-",
#   which excludes given element from all wildcards
#
#   Nonexistent elements are silently ignored.
#   If none of elements exists, the section will not be created.

# When we add a comment to an existing BZ, %summary is ignored
# (it specifies *new bug* summary field):
# %summary:: blah blah

# When dup is detected, BZ reporter adds a comment to it.
# This comment may interrupt an ongoing conversation in the BZ.
# (Three people independently filed a bug against abrt about this).
# Need to clearly explain what this comment is, to prevent confusion.
# Hopefully, this line would suffice:
Another user experienced a similar problem:

# If user filled out comment field, show it:
:: %bare_comment

# var_log_messages has too much variance (time/date),
# we exclude it from message so that dup message elimination has more chances to work
:: \
	-pkg_arch,-pkg_epoch,-pkg_name,-pkg_release,-pkg_version,\
		-component,-architecture,\
	-analyzer,-count,-duphash,-uuid,-abrt_version,\
	-username,-hostname,-os_release,-os_info,\
	-time,-pid,-pwd,-last_occurrence,-ureports_counter,\
	-var_log_messages,\
	%reporter,\
	%oneline

Your Access Expired	Date. in : 14-08-2025
Regist : 09-12-2024	Expired : 01-12-2027