4 .\" Copyright (C) 1996-2000 Thomas Roessler <roessler@does-not-exist.org>
6 .\" This program is free software; you can redistribute it and/or modify
7 .\" it under the terms of the GNU General Public License as published by
8 .\" the Free Software Foundation; either version 2 of the License, or
9 .\" (at your option) any later version.
11 .\" This program is distributed in the hope that it will be useful,
12 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
13 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 .\" GNU General Public License for more details.
16 .\" You should have received a copy of the GNU General Public License
17 .\" along with this program; if not, write to the Free Software
18 .\" Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
20 .TH flea 1 "July 2000" Unix "User Manuals"
23 flea \- Report a bug (or rather a flea) in mutt.
30 is a shell script which helps you to submit a bug report against the
36 you'll first be prompted for a short
37 description of the problem you experience. This will be used as the
38 bug report's subject line, so it should be concise, but informative.
40 You are then asked to assign an initial severity level to the
43 will give you a description which severity level is appropriate or
46 Then, you are asked for the location of a core dump (normally named
48 which may have been left over by a crash of your
50 You can just type \(lqno\(rq here, or you can enter the path leading
53 will try to use either
58 to extract some information from this core dump which may be helpful
59 to developers in order to determine the reason for the crash.
61 Finally, you are asked whether or not you want to include personal
64 configuration files with the bug report. If at all possible, we
65 urge you to answer these questions with \(lqyes\(rq, since a
66 reference configuration makes it incredibly easier to track down a
69 If you are using Debian GNU/Linux,
71 will now check whether or not
73 has been installed as a Debian
74 package on your system, and suggest to file the bug against the
76 and Debian bug tracking systems. This option was added since the
78 project uses another instantiation of the Debian bug tracking
79 system, so submitting bugs against both systems in one pass is
82 You are then dropped into your favorite editor as determined by the
86 environment variables.
88 Please give us details about the problem in the empty space below
89 the line reading \(lqPlease type your report below this line\(rq.
90 We are most interested in precise information on what symptoms you
91 observe and what steps may be used to reproduce the bug. Chances
92 are that problems which can easily be reproduced will be fixed
93 quickly. So please take some time when filling out this part of the
96 The remainder of the template contains various kinds of information
97 gathered from your system, including output of the
101 itself, and your system's
103 configuration files. You may wish to browse through this part of
104 the bug report form in order to avoid leaking confidential
105 information to the public.
107 If you leave the editor,
109 will give you the option to review, re-edit, submit, or abandon your
110 bug report. If you decide to submit it, a mail message containing
111 your report will be sent to <submit@bugs.guug.de>. You'll receive a
112 copy of this message.
114 While your bug report is being processed by the bug tracking system,
115 you will receive various e-mail messages from the bug tracking
116 system informing you about what's going on: Once your bug report has
117 been entered into the bug tracking system, it will be assigned a
118 unique serial number about which you are informed via e-mail. If
119 you wish to submit additional information about the bug, you can
120 just send it to the address
121 .BR \fIserial\fP@bugs.guug.de .
123 Later, you will most likely receive questions from the developers
124 about the problem you observed, and you will eventually be informed
125 that your bug report has been closed. This means that the bug has
126 been fixed at least in the
128 repository. If the answers you receive don't satisfy you, don't
129 hesitate to contact the developers directly under
130 .BR mutt-dev@mutt.org.
132 You can also browse your bug report and all additional information
133 and replies connected to it using the bug tracking system's Web
134 interface under the following URL:
140 will use the following environment variables:
142 Your electronic mail address. Will be used to set the bug report's
143 From header, and to send you a copy of the report.
145 Your login name. If the
147 environment variable isn't set, this will be used instead to send
148 you a copy of the report. Setting the sender will be left to
152 If set, the bug report will contain a Reply-To header with the
153 e-mail address contained in this environment variable.
155 If set, the bug report will contain an Organization header with the
156 contents of this environment variable.
158 If set, this environment variable will be expected to contain the
159 path to your favorite pager for viewing the bug report. If unset,
163 If set, this environment variable will be expected to contain the
164 path to your favorite visual editor.
166 If set, this environment variable will be expected to contain the
167 path to your favorite editor. This variable is examined if and only
170 environment variable is unset. If
174 will be used to edit the bug report.
179 If present, this file may contain a post-mortem memory dump of mutt.
180 It will be inspected using the debugger installed on your system.
194 The mutt bug tracking system: http://bugs.guug.de/
199 and this manual page were written by Thomas Roessler
200 <roessler@does-not-exist.org>.