1REPORTER-MANTISBT(1) LIBREPORT MANUAL REPORTER-MANTISBT(1)
2
6 reporter-mantisbt - Reports problem to Mantis Bug Tracker.
7
9 reporter-mantisbt [-vrf] [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d
10 DIR
11 Or:
13 reporter-mantisbt [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE...
15 Or:
17 reporter-mantisbt [-v] [-c CONFFILE]... -h DUPHASH
19
21 The tool reads problem directory DIR. Then it logs in to MantisBT and
22 tries to find an issue with the same duphash HEXSTRING in abrt_hash
23 field.
24 If such issue is not found, then a new issue is created. Elements of
26 DIR are stored in the issue as part of issue description or as
27 attachments, depending on their type and size.
28 Otherwise, if such issue is found and it is marked as CLOSED DUPLICATE,
30 the tool follows the chain of duplicates until it finds a non-DUPLICATE
31 issue. The tool adds a new note to found issue.
32 The URL to new or modified issue is printed to stdout and recorded in
34 reported_to element in DIR.
35 Option -t uploads FILEs to the already created issue on MantisBT site.
37 The issue ID is retrieved from directory specified by -d DIR. If
38 problem data in DIR was never reported to MantisBT, upload will fail.
39 Option -tID uploads FILEs to the issue with specified ID on MantisBT
41 site. -d DIR is ignored.
42 Option -r sets the last url from reporter_to element which is prefixed
44 with TRACKER_NAME to URL field. This option is applied only when a new
45 issue is to be filed. The default value is ABRT Server"
46 Configuration file
48 If not specified, CONFFILE defaults to
49 /etc/libreport/plugins/mantisbt.conf. and to user’s local
50 ~/.config/libreport/mantisbt.conf. Configuration file lines should have
51 PARAM = VALUE format. The parameters are: User’s local configuration
52 overrides the system wide configuration.
53 Login
55 Login to MantisBT account.
56 Password
58 Password to MantisBT account.
59 MantisbtURL
61 MantisBT HTTP(S) address. (default: http://localhost/mantisbt)
62 SSLVerify
64 Use yes/true/on/1 to verify server’s SSL certificate. (default: no)
65 Project
67 Project issue field value. Useful if you needed different project
68 than specified in /etc/os-release
69 ProjectVersion
71 Version issue field value. Useful if you needed different project
72 version than specified in /etc/os-release
73 CreatePrivate
75 Create private MantisBT issue. (default: no)
76 Parameters can be overridden via $Mantisbt_PARAM environment variables.
78 Formatting configuration files
80 Lines starting with # are ignored.
81 Lines can be continued on the next line using trailing backslash.
83 Format:
85 "%summary
87 summary format"
88 "section
90 element1[,element2]..." The literal text line to be added to
91 MantisBT Description or Additional information. Can be empty.
92 (Empty lines are NOT ignored!)
93 Summary format is a line of text, where %element% is replaced by
95 text element's content, and [[...%element%...]] block is used only if
96 %element% exists. [[...]] blocks can nest.
97 Sections can be:
99 - %summary: issue Summary format string.
100 - %attach: a list of elements to attach.
101 - %Additional info: issue Additional Information content.
102 - text, double colon (::) and the list of comma-separated elements.
103 Description and Additional information MantisBT's fields:
105 All text, double colons (::) and lists of comma-separated elements which
106 are placed above the section '%Additional info::' in the configuration file are
107 stored in the 'Description' field in MantisBT. All text etc. which are placed
108 under the '%Additional info::' are stored in the 'Additional information' field.
109 For example:
111 |:: comment | (Description)
112 | | (Description)
113 |Package:: package | (Description)
114 | | (Description)
115 |%Additional_info:: |
116 |%reporter% | (Additional info)
117 |User:: user_name,uid | (Additional info)
118 | | (Additional info)
119 |Directories:: root,cwd | (Additional info)
120 Elements can be:
122 - problem directory element names, which get formatted as
123 <element_name>: <contents>
124 or
125 <element_name>:
126 :<contents>
127 :<contents>
128 :<contents>
129 - problem directory element names prefixed by "%bare_",
130 which is formatted as-is, without "<element_name>:" and colons
131 - %oneline, %multiline, %text wildcards, which select all corresponding
132 elements for output or attachment
133 - %binary wildcard, valid only for %attach section, instructs to attach
134 binary elements
135 - problem directory element names prefixed by "-",
136 which excludes given element from all wildcards
137 Nonexistent elements are silently ignored.
139 If none of elements exists, the section will not be created.
140 Integration with ABRT events
142 reporter-mantisbt can be used as an ABRT reporter. Example fragment for
143 /etc/libreport/report_event.conf:
144 # Report Python crashes
146 EVENT=report_CentOSBugTracker analyzer=Python
147 reporter-mantisbt -d . -c /etc/libreport/plugins/mantisbt.conf
148
150 -d DIR
151 Path to problem directory.
152 -c CONFFILE
154 Path to configuration file.
155 -f
157 Force reporting even if this problem is already reported.
158 -F CONF_FORMAT_FILE
160 Formatting file for new issues. Default:
161 /etc/libreport/plugins/mantisbt_format.conf
162 -A CONF_FORMAT_FILE
164 Formatting file for duplicates. Default:
165 /etc/libreport/plugins/mantisbt_formatdup.conf
166 -t[ID]
168 Upload FILEs to the already created issue on MantisBT site.
169 -h, --duphash DUPHASH
171 Search in MantisBT by abrt’s DUPHASH and print ISSUE_ID.
172 -r TRACKER_NAME
174 Set the last url from reporter_to element which is prefixed with
175 TRACKER_NAME to URL field in MantisBT.
176
178 Environment variables take precedence over values provided in the
179 configuration file.
180 Mantisbt_Login
182 Login to MantisBT account.
183 Mantisbt_Password
185 Password to MantisBT account.
186 Mantisbt_MantisbtURL
188 MantisBT HTTP(S) address. (default: http://localhost/mantisbt)
189 Mantisbt_SSLVerify
191 Use yes/true/on/1 to verify server’s SSL certificate. (default: no)
192 Mantisbt_Project
194 Project issue field value. Useful if you needed different project
195 than specified in /etc/os-release
196 Mantisbt_ProjectVersion
198 Version issue field value. Useful if you needed different project
199 version than specified in /etc/os-release
200 Mantisbt_CreatePrivate
202 Create private MantisBT issue. (default: no)
203
205 /usr/share/libreport/conf.d/plugins/mantisbt.conf
206 Readonly default configuration files.
207 /etc/libreport/plugins/mantisbt.conf
209 Configuration file.
210 ~/.config/libreport/mantisbt.conf
212 User’s local configuration file.
213 /etc/libreport/plugins/mantisbt_format.conf
215 Configure formating for reporting.
216 /etc/libreport/plugins/mantisbt_formatdup.conf
218 Configure formating for reporting duplicates.
219
221 report_event.conf(5), mantisbt_format.conf(5),
222 mantisbt_formatdup.conf(5)
223
225 · ABRT team
226LIBREPORT 2.14.0 12/11/2020 REPORTER-MANTISBT(1)