55
55
@c Copyright notice
56
56
@vskip 0pt plus 1filll
57
Copyright @copyright{} 2002 Free Software Foundation, Inc.
57
Copyright @copyright{} 2002, 2005 Free Software Foundation, Inc.
59
59
Permission is granted to make and distribute verbatim
60
60
copies of this manual provided the copyright notice and
93
93
The questions and answers have been compiled by
94
@email{Hans-Albert@@HA-Schneider.de,Hans-Albert Schneider}, mainly
94
@email{Gnats-FAQ@@HA-Schneider.de,Hans-Albert Schneider}, mainly
95
95
using the help-gnats mailing list and the @sc{gnats} documentation as
96
96
input. Please report any errors and suggestions to him.
216
217
including multiple database support and customized fields. Among the
217
218
contributed software are comprehensive WWW and Tk based front-ends.
219
The latest 3.x release is 3.113.1.
220
The latest 3.x release is 3.113.1. It is deprecated due to security
221
concerns and lack of maintenance.
221
A first beta of version 4.0 is available since January 10, 2002 (as
222
@uref{ftp://ftp.gnu.org/gnu/gnats/gnats-3.999.1.tar.gz}), and an
223
official release is expected very soon now.
223
@sc{gnats} 4.0 was released in August 2003, and 4.1 was released in March 2005.
224
All released versions are available for download at
225
@uref{http://ftp.gnu.org/pub/gnu/gnats/}.
226
228
@node Mailing Lists
230
232
Currently, the following @sc{gnats} mailing lists exist:
233
@item @email{info-gnats@@gnu.org}
235
@item @uref{http://lists.gnu.org/mailman/listinfo/info-gnats,info-gnats@@gnu.org}
234
236
This is a low volume moderated mailing lists for @sc{gnats} related
235
237
announcements, like new releases or important information.
237
@item @email{help-gnats@@gnu.org}
239
@item @uref{http://lists.gnu.org/mailman/listinfo/help-gnats,help-gnats@@gnu.org}
238
240
A low-to-middle volume mailing list where anything related to @sc{gnats}
239
241
can be discussed (development, help, questions, suggestions, etc.).
241
@item @email{bug-gnats@@gnu.org}
243
@item @uref{http://lists.gnu.org/mailman/listinfo/bug-gnats,bug-gnats@@gnu.org}
242
244
Bug reports can be sent there. Please note that it's preferred to
243
245
submit bug reports via the bug tracking system (@pxref{Bug Reporting}),
244
246
which automatically mirrors them to this list.
247
249
Lists that are of interest mainly for the @sc{gnats} developers:
250
@item @email{gnats-prs@@gnu.org}
252
@item @uref{http://lists.gnu.org/mailman/listinfo/gnats-prs,gnats-prs@@gnu.org}
251
253
Copies of the bug tracking system messages are sent there. Contrast to
252
254
bug-gnats@@gnu.org which only gets new bug reports, this list also gets
253
255
the follow-ups (Whatever goes into @sc{gnats}' @code{>Audit-Trail:} field).
255
@item @email{gnats-commit@@gnu.org}
257
@item @uref{http://lists.gnu.org/mailman/listinfo/gnats-commit,gnats-commit@@gnu.org}
256
258
CVS commit messages are sent there.
258
@item @email{gnats-diffs@@gnu.org}
260
@item @uref{http://lists.gnu.org/mailman/listinfo/gnats-diffs,gnats-diffs@@gnu.org}
259
261
Diffs of committed files are sent automatically to this address.
268
270
Before reporting a bug, make sure it really is a bug, not a simple
269
271
misunderstanding or a misconfiguration. Please check the manual and
270
this FAQ. You may also ask for help on the @email{help-gnats@@gnu.org}
272
this FAQ. You may also ask for help on the
273
@uref{http://lists.gnu.org/mailman/listinfo/help-gnats,help-gnats@@gnu.org}
274
mailing list (you may want to search the list archive first; it is
275
available from @uref{http://lists.gnu.org/mailman/listinfo/help-gnats}).
273
277
If it is a bug, please report it via the bug tracking system. It
308
311
@comment node-name, next, previous, up
309
312
@section Upgrading Considerations
311
314
See @ref{Upgrading,,Upgrading from older versions,gnats,Keeping
312
315
Track} for the upgrade process from 3.x to 4.x.
314
If you are running a 3.x version older than 3.113.1, and your system
315
is heavily used, you may prefer to upgrade to 3.113.1--there are a lot
316
of changes between 3.113.1 and 4.0-pre, and some parts of the 4.0
317
documentation may still need to be updated.
319
Another consideration is to migrate by running 4.x in parallel to 3.x,
317
If you are running a 3.x version, @emph{please consider upgrading to 4.0.}
318
There are some security concerns about the 3.1xx code that have gone
319
with 4.0. Furthermore, the @sc{gnats} 3 branch is not maintained
320
anymore due to lack of capacity.
323
The default format of the reports has not changed during the transition
324
from 3.113.1 to 4.0, though you may add more fields to 4.0 reports (and
325
leave out others). The format of the index file is now binary.
328
However, you have to change the e-mail aliases because the meaning of
329
the @samp{-d} option to the client programs has changed: It took the
330
@emph{directory} of the @sc{gnats} database in 3.1xx, and now takes its
331
@emph{name} (plus, it is now installed into the @file{libexec} directory
332
instead of the @file{lib} directory). I.e., you must change the aliases:
336
ourdb-query: "|/usr/local/lib/gnats/mail-query -d /usr/local/gnats/db2"
337
ourdb-bugs: "|/usr/local/lib/gnats/queue-pr -d /usr/local/gnats/db2 -q"
342
ourdb-query: "|/usr/local/libexec/gnats/mail-query -d ourdb"
343
ourdb-bugs: "|/usr/local/libexec/gnats/queue-pr -d ourdb -q"
347
Also note that the client/server protocol has changed from 3.1xx to
348
4.0; you cannot run clients from one version with the server from the
353
One consideration is to migrate by running 4.x in parallel to 3.x,
320
354
as a sort of mirror of the 3.x version.
321
355
To the best of my knowledge, this has not yet been done practically.
372
406
Gnatsweb 2.9.x is for use with @sc{gnats} 3.113.1.
373
407
With @sc{gnats} 3.999.x, you must use Gnatsweb 3.99.x; it is in the
374
408
contrib subdirectory of the @sc{gnats} distribution.
409
(@sc{gnats} 3.999.x/Gnatsweb 3.99.x were pre-releases of the 4.0
410
releases. As 4.0 is out now, you may consider to upgrade to the
413
For @sc{gnats} 4.x, use Gnatsweb 4.0 or greater.
378
416
@node Configuration
556
596
@w{@file{gnats-queue}}. Note that you need to specify the database to
557
597
@file{queue-pr}, i.e.,
559
@samp{/usr/local/lib/gnats/queue-pr -d GreatNewDB -r}
599
@samp{/usr/local/libexec/gnats/queue-pr -d GreatNewDB -r}
561
601
or, if you prefer the long options,
563
@samp{/usr/local/lib/gnats/queue-pr --database=GreatNewDB --run}
603
@samp{/usr/local/libexec/gnats/queue-pr --database=GreatNewDB --run}
822
862
@b{Q:} Gnatsd rejects connections from a remote host with the error
823
863
message @samp{520 You are not on the host access list}.
825
@b{A:} Check the file @w{@file{gnatsd.conf}} (@sc{gnats} 3.xxx) or
826
@w{@file{gnatsd.host_access}} (@sc{gnats} 4.x). With @sc{gnats} 3,
827
this is usually @w{@file{/usr/local/etc/gnatsd.conf}}; with
828
@sc{gnats} 4, it is usually
865
@b{A:} Check the file @w{@file{gnatsd.host_access}}; if you are using
866
the default locations, this is
829
867
@w{@file{/usr/local/etc/gnats/gnatsd.host_access}}.
868
(If you are still using @sc{gnats} 3.xxx, the file is named
869
@w{@file{gnatsd.conf}}; its default place is
870
@w{@file{/usr/local/etc/gnatsd.conf}}.)
831
872
Each line of the file names a host and its access level, separated by
832
873
colons. Gnatsd tries the lines in turn to match the remote host, and
added
removed
doc/gnats-faq.texi
