/[gnats]/gnats/doc/gnats-faq.texi
ViewVC logotype

Diff of /gnats/doc/gnats-faq.texi

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.7 by pdm, Sun Jul 14 17:27:47 2002 UTC revision 1.8 by has, Sun Jul 21 21:47:18 2002 UTC
# Line 93  The most recent version of this FAQ can Line 93  The most recent version of this FAQ can
93  The questions and answers have been compiled by  The questions and answers have been compiled by
94  @email{Hans-Albert@@HA-Schneider.de,Hans-Albert Schneider}, mainly  @email{Hans-Albert@@HA-Schneider.de,Hans-Albert Schneider}, mainly
95  using the help-gnats mailing list and the @sc{gnats} documentation as  using the help-gnats mailing list and the @sc{gnats} documentation as
96  input.  input.  Please report any errors and suggestions to him.
97    
98    
99  @menu  @menu
# Line 289  build utilities you use. Line 289  build utilities you use.
289  @end itemize  @end itemize
290    
291  Providing this information in the initial report avoids further  Providing this information in the initial report avoids further
292  unnecessary communication, saves our limited development resources and  unnecessary communication, saves the limited resources of the
293  helps to track down and fix the problem soon.  developers (keep in mind that they are working on @sc{gnats} and
294    friends in their spare time) and helps to track down and fix the
295    problem soon.
296    
297    
298    @ignore
299    @c @node Upgrading
300    @comment  node-name,  next,  previous,  up
301    @section Upgrading Considerations
302    
303    See @ref{Upgrading,,Upgrading from older versions,gnats,Keeping
304    Track} for the upgrade process from 3.x to 4.x.
305    
306    If you are running a 3.x version older than 3.113.1, and your system
307    is heavily used, you may prefer to upgrade to 3.113.1--there are a lot
308    of changes between 3.113.1 and 4.0-pre, and some parts of the 4.0
309    documentation may still need to be updated.
310    
311    Another consideration is to migrate by running 4.x in parallel to 3.x,
312    as a sort of mirror of the 3.x version.
313    To the best of my knowledge, this has not yet been done practically.
314    
315    The idea is to have the mail
316    aliases on the 3.x server also send the mails to the 4.x server.  To
317    avoid confusing submitters and responsibles by duplicate emails (one
318    from 3.x and one from 4.x), the 4.x server could send its mails to the
319    @sc{gnats} admin, or even to @code{nobody} (usually aliased to
320    @w{@file{/dev/null}}).  As the mail text sent by the 4.x server is
321    configurable, another option is to include an explanatory statement.
322    
323    @smallexample
324    # On the @sc{gnats} 3 server:
325    GreatNewDB-bugs: GreatNewDB-bugs-3, GreatNewDB-bugs-4
326    GreatNewDB-query:  "|/usr/local/lib/gnats/mail-query -d /usr/local/gnats/db2"
327    GreatNewDB-bugs-3: "|/usr/local/lib/gnats/queue-pr -d /usr/local/gnats/db2 -q"
328    # If the @sc{gnats} 4 server is different:
329    GreatNewDB-bugs-4: GreatNewDB-bugs-4@@gnats4-server
330    @end smallexample
331    
332    @smallexample
333    # On the @sc{gnats} 4 server:
334    GreatNewDB-bugs-4: "|/usr/local/libexec/gnats/queue-pr -d GreatNewDB -q"
335    nobody:            /dev/null
336    @end smallexample
337    @end ignore
338    
339    
340  @node     Installation  @node     Installation
# Line 324  please check also @ref{Configuration}. Line 367  please check also @ref{Configuration}.
367  @menu  @menu
368  * Add a database::              How to create a new database  * Add a database::              How to create a new database
369  * Renaming a Category::          * Renaming a Category::        
370    * Changing Fields::            
371  @end menu  @end menu
372    
373  @node Add a database  @node Add a database
# Line 387  this: Line 431  this:
431    
432          @code{/usr/local/gnats/db2:GreatNewDB}          @code{/usr/local/gnats/db2:GreatNewDB}
433    
434  Gnatsd reads it on startup (and as it is started by inetd, this  Gnatsd reads it on startup (and as it is started by inetd, this means
435  means it becomes effective with the next connection to gnatsd).  it becomes effective with the next connection to gnatsd).  Gnatsweb
436  @ref{Gnatsweb} learns the database list from gnatsd, so it will offer  (see @ref{Gnatsweb}) learns the database list from gnatsd, so it will offer
437  you the new database "GreatNewDB" when it is invoked next time.  you the new database "GreatNewDB" when it is invoked next time.
438    
439  If you do not know where @w{@file{gnats-db.conf}} lives, run:  If you do not know where @w{@file{gnats-db.conf}} lives, run:
# Line 435  Then, as the @sc{gnats} user, run @samp{ Line 479  Then, as the @sc{gnats} user, run @samp{
479  database.  Make sure that the directory (in our example,  database.  Make sure that the directory (in our example,
480  @w{@file{/usr/local/gnats/db2}}) can be created by the @sc{gnats} user.  @w{@file{/usr/local/gnats/db2}}) can be created by the @sc{gnats} user.
481    
482    (Note that there @emph{must} be a database named @code{default}.  It
483    is used as a fallback by some tools if no database is specified.  You
484    need not use it actively, but you should have run @samp{mkdb default}.)
485    
486    
487  Gnatsd reads the file @w{@file{databases}} on startup (and as it is  Gnatsd reads the file @w{@file{databases}} on startup (and as it is
488  started by inetd, this means it becomes effective with the next  started by inetd, this means it becomes effective with the next
489  connection to gnatsd).  @ref{Gnatsweb} learns the database list from  connection to gnatsd).  Gnatsweb (see @ref{Gnatsweb}) learns the
490  gnatsd, so it will offer you the new database "GreatNewDB" when it is  database list from gnatsd, so it will offer you the new database
491  invoked next time.  "GreatNewDB" when it is invoked next time.
492    
493  If you do not know where @w{@file{databases}} lives, run:  If you do not know where @w{@file{databases}} lives, run:
494    
# Line 512  something like @samp{obsolete, use categ Line 561  something like @samp{obsolete, use categ
561    
562  @end enumerate  @end enumerate
563    
564    @node Changing Fields
565    @comment  node-name,  next,  previous,  up
566    @subsection How do I add, remove, or rename a PR field?
567    
568    @noindent
569    @b{A: (@sc{gnats} 3.1xx)} The fields and their names are fixed in
570    @sc{gnats} 3.1xx, so this is not possible.
571    
572    @noindent
573    @b{A: (@sc{gnats} 4.x)} Edit the file @file{dbconfig} to reflect your
574    changes.
575    
576    Note that the PR fields with the builtin-names @code{severity},
577    @code{priority} and @code{state} are required if you want automatic
578    reminders (@code{notify-about-expired-prs = true}).  In this case, the
579    file @file{submitters} must also contain a response time.
580    @c The reminder is filed if:
581    @c - "response time" is not -1, and
582    @c - @code{notify-about-expired-prs} = true, and
583    @c - (@code{severity} = @code{critical})
584    @c   or ( @code{severity} = @code{serious}
585    @c        and @code{priority} = @code{high} )
586    The @code{severity} field is checked for values @code{critical} and
587    @code{serious}, and @code{priority} for value @code{high}.
588    This is currently not configurable.
589    
590    
591  @node Gnatsd  @node Gnatsd
592  @comment  node-name,  next,  previous,  up  @comment  node-name,  next,  previous,  up
# Line 865  Tcl/Tk based interface), a @sc{gnats} mo Line 940  Tcl/Tk based interface), a @sc{gnats} mo
940  @comment  node-name,  next,  previous,  up  @comment  node-name,  next,  previous,  up
941  @subsection General Gnatsweb Questions  @subsection General Gnatsweb Questions
942    
943    Currently none.
944    
945    
946  @node Gnatsweb Login Questions  @node Gnatsweb Login Questions

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26