111 |
|
|
112 |
@menu |
@menu |
113 |
* What is GNATS:: A very short overview |
* What is GNATS:: A very short overview |
114 |
* How to pronounce it:: |
* How to pronounce it:: Pronunciation: with or without the "G"? |
115 |
* Get it:: Where to get @sc{gnats} |
* Get it:: Where to get @sc{gnats} |
116 |
* Versions:: Which versions are available? |
* Versions:: Which versions are available? |
117 |
* Mailing Lists:: E-mail discussion lists |
* Mailing Lists:: E-mail discussion lists |
231 |
|
|
232 |
@itemize |
@itemize |
233 |
@item @email{info-gnats@@gnu.org} |
@item @email{info-gnats@@gnu.org} |
|
(formerly gnats-announce@@sources.redhat.com) |
|
234 |
This is a low volume moderated mailing lists for @sc{gnats} related |
This is a low volume moderated mailing lists for @sc{gnats} related |
235 |
announcements, like new releases or important information. |
announcements, like new releases or important information. |
236 |
|
|
237 |
@item @email{help-gnats@@gnu.org} |
@item @email{help-gnats@@gnu.org} |
|
(formerly gnats-devel@@sources.redhat.com) |
|
238 |
A low-to-middle volume mailing list where anything related to @sc{gnats} |
A low-to-middle volume mailing list where anything related to @sc{gnats} |
239 |
can be discussed (development, help, questions, suggestions, etc.). |
can be discussed (development, help, questions, suggestions, etc.). |
240 |
|
|
248 |
|
|
249 |
@itemize |
@itemize |
250 |
@item @email{gnats-prs@@gnu.org} |
@item @email{gnats-prs@@gnu.org} |
|
(formerly gnats-prs@@sources.redhat.com) |
|
251 |
Copies of the bug tracking system messages are sent there. Contrast to |
Copies of the bug tracking system messages are sent there. Contrast to |
252 |
bug-gnats@@gnu.org which only gets new bug reports, this list also gets |
bug-gnats@@gnu.org which only gets new bug reports, this list also gets |
253 |
the follow-ups (Whatever goes into @sc{gnats}' @code{>Audit-Trail:} field). |
the follow-ups (Whatever goes into @sc{gnats}' @code{>Audit-Trail:} field). |
254 |
|
|
255 |
@item @email{gnats-commit@@gnu.org} |
@item @email{gnats-commit@@gnu.org} |
|
(formerly gnats-cvs@@sources.redhat.com) |
|
256 |
CVS commit messages are sent there. |
CVS commit messages are sent there. |
257 |
|
|
258 |
@item @email{gnats-diffs@@gnu.org} |
@item @email{gnats-diffs@@gnu.org} |
393 |
|
|
394 |
@menu |
@menu |
395 |
* Add a database:: How to create a new database |
* Add a database:: How to create a new database |
396 |
* Renaming a Category:: |
* Renaming a Category:: How to rename categories |
397 |
* Changing Fields:: |
* Changing Fields:: Add, remove, or rename a PR field |
|
* Append-only Audit-Trail:: |
|
398 |
@end menu |
@end menu |
399 |
|
|
400 |
@node Add a database |
@node Add a database |
648 |
This is currently not configurable. |
This is currently not configurable. |
649 |
|
|
650 |
|
|
|
@node Append-only Audit-Trail |
|
|
@comment node-name, next, previous, up |
|
|
@subsection How do make Audit-Trail append-only? |
|
|
|
|
|
Mike Hoolehan wanted a "bugzilla-ish appending audit trail", i.e., |
|
|
Audit-Trail can not be changed arbitrarily, only appended. |
|
|
|
|
|
He posted the following solution to the @email{help-gnats@@gnu.org} |
|
|
mailing list: |
|
|
|
|
|
First, set the Audit-Trail field to read-only. Then add this: |
|
|
|
|
|
@example |
|
|
field "Add-To-Audit-Trail" @{ |
|
|
description "Add a log entry to Audit Trail" |
|
|
multitext @{ default "\n" @} |
|
|
on-change @{ |
|
|
add-audit-trail |
|
|
audit-trail-format @{ |
|
|
format "---- Comments by %s on %s ----\n %s\n\n" #whatever you like |
|
|
fields @{ "$EditUserEmailAddr" "$CurrentDate" "$NewValue" @} |
|
|
@} |
|
|
@} |
|
|
on-change @{ |
|
|
set-field "Add-To-Audit-Trail" @{ "\n" @} |
|
|
@} |
|
|
@} |
|
|
@end example |
|
|
|
|
|
|
|
651 |
@node Gnatsd |
@node Gnatsd |
652 |
@comment node-name, next, previous, up |
@comment node-name, next, previous, up |
653 |
@section Gnatsd, the @sc{gnats} Daemon |
@section Gnatsd, the @sc{gnats} Daemon |
778 |
@subsection Gnatsd Messages |
@subsection Gnatsd Messages |
779 |
|
|
780 |
@menu |
@menu |
781 |
* No host access for stdin:: |
* No host access for stdin:: Error when starting gnatsd manually |
782 |
* No host access for remote:: |
* No host access for remote:: Cannot connect from another machine |
783 |
@end menu |
@end menu |
784 |
|
|
785 |
@node No host access for stdin |
@node No host access for stdin |
856 |
# |
# |
857 |
# This is a comment |
# This is a comment |
858 |
# |
# |
859 |
# Grant view access to all hosts with IP adresses |
# Grant view access to all hosts with IP addresses |
860 |
# ranging from 192.168.0.0 to 192.168.255.255: |
# ranging from 192.168.0.0 to 192.168.255.255: |
861 |
192.168.*:view: |
192.168.*:view: |
862 |
# Users on host goedel.example.com get (at least) edit access: |
# Users on host goedel.example.com get (at least) edit access: |
887 |
@section E-Mail Issues |
@section E-Mail Issues |
888 |
|
|
889 |
@menu |
@menu |
890 |
* queue-pr not available:: |
* queue-pr not available:: Sendmail refuses to run queue-pr |
891 |
* Outgoing mail bounces:: |
* Outgoing mail bounces:: Mail system complains on outgoing mail |
892 |
@end menu |
@end menu |
893 |
|
|
894 |
@node queue-pr not available, Outgoing mail bounces, E-Mail, E-Mail |
@node queue-pr not available, Outgoing mail bounces, E-Mail, E-Mail |
1025 |
@comment node-name, next, previous, up |
@comment node-name, next, previous, up |
1026 |
@section Gnatsweb |
@section Gnatsweb |
1027 |
|
|
1028 |
|
See also @ref{Gnatsweb and GNATS} in the chapter on @ref{Installation}. |
1029 |
|
|
1030 |
@menu |
@menu |
|
* General Gnatsweb Questions:: |
|
1031 |
* Gnatsweb Login Questions:: Problems logging in to Gnatsweb |
* Gnatsweb Login Questions:: Problems logging in to Gnatsweb |
1032 |
@end menu |
@end menu |
1033 |
|
|
1034 |
@node General Gnatsweb Questions |
@c @node General Gnatsweb Questions |
1035 |
@comment node-name, next, previous, up |
@comment node-name, next, previous, up |
1036 |
@subsection General Gnatsweb Questions |
@c @subsection General Gnatsweb Questions |
|
|
|
|
See also @ref{Gnatsweb and GNATS} in the chapter on @ref{Installation}. |
|
1037 |
|
|
1038 |
|
|
1039 |
@node Gnatsweb Login Questions |
@node Gnatsweb Login Questions |
1103 |
Cookie Central}. |
Cookie Central}. |
1104 |
|
|
1105 |
|
|
1106 |
@b{Q:} So, why does Gnatsweb send these cookies? |
@b{Q:} So, which cookies does Gnatsweb send, and why? |
1107 |
|
|
1108 |
@b{A:} Gnatsweb uses a cookie @code{gnatsweb-db-}@emph{database_name} to |
@b{A:} Gnatsweb uses a cookie @code{gnatsweb-db-}@emph{database_name} to |
1109 |
store your login information (username, password), and a cookie |
store your login information (username, password), and a cookie |
1117 |
@code{gnatsweb-query-}@emph{queryname}). |
@code{gnatsweb-query-}@emph{queryname}). |
1118 |
|
|
1119 |
It is therefore essential that you allow Gnatsweb to set its cookies. |
It is therefore essential that you allow Gnatsweb to set its cookies. |
1120 |
|
For a typical effect of rejecting them, see @ref{Login Not Remembered}. |
1121 |
|
|
1122 |
|
|
1123 |
@node TkGnats |
@node TkGnats |
1222 |
@printindex cp |
@printindex cp |
1223 |
|
|
1224 |
@bye |
@bye |
1225 |
|
@c LocalWords: ifinfo savannah |