+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->The Bugzilla Guide - 2.16.4 Release</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><META
-NAME="KEYWORD"
-CONTENT="Bugzilla"><META
-NAME="KEYWORD"
-CONTENT="Guide"><META
-NAME="KEYWORD"
-CONTENT="installation"><META
-NAME="KEYWORD"
-CONTENT="FAQ"><META
-NAME="KEYWORD"
-CONTENT="administration"><META
-NAME="KEYWORD"
-CONTENT="integration"><META
-NAME="KEYWORD"
-CONTENT="MySQL"><META
-NAME="KEYWORD"
-CONTENT="Mozilla"><META
-NAME="KEYWORD"
-CONTENT="webtools"></HEAD
-><BODY
-CLASS="book"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="BOOK"
-><A
-NAME="index"
-></A
-><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="title"
-><A
-NAME="AEN2"
-></A
->The Bugzilla Guide - 2.16.4 Release</H1
-><H3
-CLASS="author"
-><A
-NAME="AEN5"
-></A
->Matthew P. Barnson</H3
-><H3
-CLASS="author"
-><A
-NAME="AEN9"
-></A
->The Bugzilla Team</H3
-><P
-CLASS="pubdate"
->2003-11-01<BR></P
-><DIV
-><DIV
-CLASS="abstract"
-><A
-NAME="AEN14"
-></A
-><P
-></P
-><P
-> This is the documentation for Bugzilla, the mozilla.org
- bug-tracking system.
- Bugzilla is an enterprise-class piece of software
- that powers issue-tracking for hundreds of
- organizations around the world, tracking millions of bugs.
- </P
-><P
->
- This documentation is maintained in DocBook 4.1.2 XML format.
- Changes are best submitted as plain text or XML diffs, attached
- to a bug filed in
- <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->mozilla.org's Bugzilla</A
->.
- </P
-><P
-> The most current version of this document can always be found on the
- <A
-HREF="http://www.bugzilla.org/documentation.html"
-TARGET="_top"
->Bugzilla Documentation Page</A
->.
- </P
-><P
-></P
-></DIV
-></DIV
-><HR></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1. <A
-HREF="#about"
->About This Guide</A
-></DT
-><DD
-><DL
-><DT
->1.1. <A
-HREF="#copyright"
->Copyright Information</A
-></DT
-><DT
->1.2. <A
-HREF="#disclaimer"
->Disclaimer</A
-></DT
-><DT
->1.3. <A
-HREF="#newversions"
->New Versions</A
-></DT
-><DT
->1.4. <A
-HREF="#credits"
->Credits</A
-></DT
-><DT
->1.5. <A
-HREF="#conventions"
->Document Conventions</A
-></DT
-></DL
-></DD
-><DT
->2. <A
-HREF="#introduction"
->Introduction</A
-></DT
-><DD
-><DL
-><DT
->2.1. <A
-HREF="#whatis"
->What is Bugzilla?</A
-></DT
-><DT
->2.2. <A
-HREF="#why"
->Why Should We Use Bugzilla?</A
-></DT
-></DL
-></DD
-><DT
->3. <A
-HREF="#using"
->Using Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->3.1. <A
-HREF="#how"
->How do I use Bugzilla?</A
-></DT
-><DT
->3.2. <A
-HREF="#hintsandtips"
->Hints and Tips</A
-></DT
-><DT
->3.3. <A
-HREF="#userpreferences"
->User Preferences</A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="#installation"
->Installation</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="#stepbystep"
->Step-by-step Install</A
-></DT
-><DT
->4.2. <A
-HREF="#extraconfig"
->Optional Additional Configuration</A
-></DT
-><DT
->4.3. <A
-HREF="#win32"
->Win32 Installation Notes</A
-></DT
-><DT
->4.4. <A
-HREF="#osx"
->Mac OS X Installation Notes</A
-></DT
-><DT
->4.5. <A
-HREF="#troubleshooting"
->Troubleshooting</A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="#administration"
->Administering Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="#parameters"
->Bugzilla Configuration</A
-></DT
-><DT
->5.2. <A
-HREF="#useradmin"
->User Administration</A
-></DT
-><DT
->5.3. <A
-HREF="#programadmin"
->Product, Component, Milestone, and Version Administration</A
-></DT
-><DT
->5.4. <A
-HREF="#voting"
->Voting</A
-></DT
-><DT
->5.5. <A
-HREF="#groups"
->Groups and Group Security</A
-></DT
-><DT
->5.6. <A
-HREF="#security"
->Bugzilla Security</A
-></DT
-><DT
->5.7. <A
-HREF="#cust-templates"
->Template Customisation</A
-></DT
-><DT
->5.8. <A
-HREF="#upgrading"
->Upgrading to New Releases</A
-></DT
-><DT
->5.9. <A
-HREF="#integration"
->Integrating Bugzilla with Third-Party Tools</A
-></DT
-></DL
-></DD
-><DT
->A. <A
-HREF="#faq"
->The Bugzilla FAQ</A
-></DT
-><DT
->B. <A
-HREF="#database"
->The Bugzilla Database</A
-></DT
-><DD
-><DL
-><DT
->B.1. <A
-HREF="#dbschema"
->Database Schema Chart</A
-></DT
-><DT
->B.2. <A
-HREF="#dbdoc"
->MySQL Bugzilla Database Introduction</A
-></DT
-></DL
-></DD
-><DT
->C. <A
-HREF="#patches"
->Useful Patches and Utilities for Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->C.1. <A
-HREF="#rewrite"
->Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</A
-></DT
-><DT
->C.2. <A
-HREF="#cmdline"
->Command-line Bugzilla Queries</A
-></DT
-></DL
-></DD
-><DT
->D. <A
-HREF="#variants"
->Bugzilla Variants and Competitors</A
-></DT
-><DD
-><DL
-><DT
->D.1. <A
-HREF="#variant-redhat"
->Red Hat Bugzilla</A
-></DT
-><DT
->D.2. <A
-HREF="#variant-fenris"
->Loki Bugzilla (Fenris)</A
-></DT
-><DT
->D.3. <A
-HREF="#variant-issuezilla"
->Issuezilla</A
-></DT
-><DT
->D.4. <A
-HREF="#variant-scarab"
->Scarab</A
-></DT
-><DT
->D.5. <A
-HREF="#variant-perforce"
->Perforce SCM</A
-></DT
-><DT
->D.6. <A
-HREF="#variant-sourceforge"
->SourceForge</A
-></DT
-></DL
-></DD
-><DT
->E. <A
-HREF="#gfdl"
->GNU Free Documentation License</A
-></DT
-><DD
-><DL
-><DT
->0. <A
-HREF="#gfdl-0"
->PREAMBLE</A
-></DT
-><DT
->1. <A
-HREF="#gfdl-1"
->APPLICABILITY AND DEFINITIONS</A
-></DT
-><DT
->2. <A
-HREF="#gfdl-2"
->VERBATIM COPYING</A
-></DT
-><DT
->3. <A
-HREF="#gfdl-3"
->COPYING IN QUANTITY</A
-></DT
-><DT
->4. <A
-HREF="#gfdl-4"
->MODIFICATIONS</A
-></DT
-><DT
->5. <A
-HREF="#gfdl-5"
->COMBINING DOCUMENTS</A
-></DT
-><DT
->6. <A
-HREF="#gfdl-6"
->COLLECTIONS OF DOCUMENTS</A
-></DT
-><DT
->7. <A
-HREF="#gfdl-7"
->AGGREGATION WITH INDEPENDENT WORKS</A
-></DT
-><DT
->8. <A
-HREF="#gfdl-8"
->TRANSLATION</A
-></DT
-><DT
->9. <A
-HREF="#gfdl-9"
->TERMINATION</A
-></DT
-><DT
->10. <A
-HREF="#gfdl-10"
->FUTURE REVISIONS OF THIS LICENSE</A
-></DT
-><DT
-><A
-HREF="#gfdl-howto"
->How to use this License for your documents</A
-></DT
-></DL
-></DD
-><DT
-><A
-HREF="#glossary"
->Glossary</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
->List of Figures</B
-></DT
-><DT
->4-1. <A
-HREF="#trouble-filetemp-errors"
->Other File::Temp error messages</A
-></DT
-><DT
->4-2. <A
-HREF="#trouble-filetemp-patch"
->Patch for File::Temp in Perl 5.6.0</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
->List of Examples</B
-></DT
-><DT
->4-1. <A
-HREF="#AEN863"
->Installing ActivePerl ppd Modules on Microsoft
- Windows</A
-></DT
-><DT
->4-2. <A
-HREF="#AEN876"
->Installing OpenInteract ppd Modules manually on Microsoft
- Windows</A
-></DT
-><DT
->4-3. <A
-HREF="#AEN1058"
->Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier</A
-></DT
-><DT
->5-1. <A
-HREF="#upgrade-cvs"
->Upgrading using CVS</A
-></DT
-><DT
->5-2. <A
-HREF="#upgrade-tarball"
->Upgrading using the tarball</A
-></DT
-><DT
->5-3. <A
-HREF="#upgrade-patches"
->Upgrading using patches</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="about"
-></A
->Chapter 1. About This Guide</H1
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="copyright"
-></A
->1.1. Copyright Information</H1
-><A
-NAME="AEN34"
-></A
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
-><P
-> Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation
- License, Version 1.1 or any later version published by the
- Free Software Foundation; with no Invariant Sections, no
- Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included in <A
-HREF="#gfdl"
->Appendix E</A
->.
- </P
-></TD
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN
-></TD
-><TD
-WIDTH="10%"
-> </TD
-></TR
-></TABLE
-><P
-> If you have any questions regarding this document, its
- copyright, or publishing this document in non-electronic form,
- please contact The Bugzilla Team.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="disclaimer"
-></A
->1.2. Disclaimer</H1
-><P
-> No liability for the contents of this document can be accepted.
- Use the concepts, examples, and other content at your own risk.
- This document may contain errors
- and inaccuracies that may damage your system, cause your partner
- to leave you, your boss to fire you, your cats to
- pee on your furniture and clothing, and global thermonuclear
- war. Proceed with caution.
- </P
-><P
-> All copyrights are held by their respective owners, unless
- specifically noted otherwise. Use of a term in this document
- should not be regarded as affecting the validity of any
- trademark or service mark.
- </P
-><P
-> Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". We
- wholeheartedly endorse the use of GNU/Linux in every situation
- where it is appropriate. It is an extremely versatile, stable,
- and robust operating system that offers an ideal operating
- environment for Bugzilla.
- </P
-><P
-> You are strongly recommended to make a backup of your system
- before installing Bugzilla and at regular intervals thereafter.
- If you implement any suggestion in this Guide, implement this one!
- </P
-><P
-> Although the Bugzilla development team has taken great care to
- ensure that all easily-exploitable bugs or options are
- documented or fixed in the code, security holes surely exist.
- Great care should be taken both in the installation and usage of
- this software. Carefully consider the implications of installing
- other network services with Bugzilla. The Bugzilla development
- team members, Netscape Communications, America Online Inc., and
- any affiliated developers or sponsors assume no liability for
- your use of this product. You have the source code to this
- product, and are responsible for auditing it yourself to ensure
- your security needs are met.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="newversions"
-></A
->1.3. New Versions</H1
-><P
-> This is the 2.16.4 version of The Bugzilla Guide. It is so named
- to match the version of Bugzilla it is disributed with. If you are
- reading this from any source other than those below, please
- check one of these mirrors to make sure you are reading an
- up-to-date version of the Guide.
- </P
-><P
-> The newest version of this guide can always be found at <A
-HREF="http://www.bugzilla.org"
-TARGET="_top"
->bugzilla.org</A
->; including
- documentation for past releases and the current development version.
- </P
-><P
-> The documentation for the most recent stable release of Bugzilla can also
- be found at
- <A
-HREF="http://www.tldp.org"
-TARGET="_top"
->The Linux Documentation Project</A
->.
- </P
-><P
-> The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at
- <A
-HREF="http://www.mozilla.org/cvs.html"
-TARGET="_top"
->the Mozilla CVS page</A
->,
- and check out the <TT
-CLASS="filename"
->mozilla/webtools/bugzilla/docs/</TT
->
- subtree.
- </P
-><P
-> The Bugzilla Guide is currently only available in English.
- If you would like to volunteer to translate it, please contact
- <A
-HREF="mailto:justdave@syndicomm.com"
-TARGET="_top"
->Dave Miller</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="credits"
-></A
->1.4. Credits</H1
-><P
-> The people listed below have made enormous contributions to the
- creation of this Guide, through their writing, dedicated hacking efforts,
- numerous e-mail and IRC support sessions, and overall excellent
- contribution to the Bugzilla community:
- </P
-><P
-></P
-><DIV
-CLASS="variablelist"
-><DL
-><DT
->Matthew P. Barnson <TT
-CLASS="email"
-><<A
-HREF="mailto:mbarnson@sisna.com"
->mbarnson@sisna.com</A
->></TT
-></DT
-><DD
-><P
->for the Herculaean task of pulling together the Bugzilla Guide
- and shepherding it to 2.14.
- </P
-></DD
-><DT
->Terry Weissman <TT
-CLASS="email"
-><<A
-HREF="mailto:terry@mozilla.org"
->terry@mozilla.org</A
->></TT
-></DT
-><DD
-><P
->for initially writing Bugzilla and creating the README upon
- which the UNIX installation documentation is largely based.
- </P
-></DD
-><DT
->Tara Hernandez <TT
-CLASS="email"
-><<A
-HREF="mailto:tara@tequilarists.org"
->tara@tequilarists.org</A
->></TT
-></DT
-><DD
-><P
->for keeping Bugzilla development going strong after Terry left
- mozilla.org and for running landfill.
- </P
-></DD
-><DT
->Dave Lawrence <TT
-CLASS="email"
-><<A
-HREF="mailto:dkl@redhat.com"
->dkl@redhat.com</A
->></TT
-></DT
-><DD
-><P
->for providing insight into the key differences between Red
- Hat's customized Bugzilla, and being largely responsible for
- <A
-HREF="#variant-redhat"
->Section D.1</A
->.
- </P
-></DD
-><DT
->Dawn Endico <TT
-CLASS="email"
-><<A
-HREF="mailto:endico@mozilla.org"
->endico@mozilla.org</A
->></TT
-></DT
-><DD
-><P
->for being a hacker extraordinaire and putting up with Matthew's
- incessant questions and arguments on irc.mozilla.org in #mozwebtools
- </P
-></DD
-><DT
->Jacob Steenhagen <TT
-CLASS="email"
-><<A
-HREF="mailto:jake@bugzilla.org"
->jake@bugzilla.org</A
->></TT
-></DT
-><DD
-><P
->for taking over documentation during the 2.17 development
- period and backporting relevent docs changes to this 2.16 branch.
- </P
-></DD
-></DL
-></DIV
-><P
-> Last but not least, all the members of the
- <A
-HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
-TARGET="_top"
->news://news.mozilla.org/netscape/public/mozilla/webtools</A
->
- newsgroup. Without your discussions, insight, suggestions, and patches,
- this could never have happened.
- </P
-><P
-> Thanks also go to the following people for significant contributions
- to this documentation (in alphabetical order):
- Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
- .
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="conventions"
-></A
->1.5. Document Conventions</H1
-><P
->This document uses the following conventions:</P
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN111"
-></A
-><P
-></P
-><TABLE
-BORDER="0"
-CLASS="CALSTABLE"
-><THEAD
-><TR
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Descriptions</TH
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Appearance</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Use caution</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't run with scissors!</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Hint</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Would you like a breath mint?</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Notes</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Dear John...</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Warnings</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Read this or the cat gets it.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->File Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->filename</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Directory Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->directory</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Commands to be typed</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <B
-CLASS="command"
->command</B
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Applications Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <SPAN
-CLASS="application"
->application</SPAN
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of root users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash#</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of user command under tcsh shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->tcsh$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Environment Variables</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="envar"
->VARIABLE</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Emphasized word</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <EM
->word</EM
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Term found in the glossary</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <A
-HREF="#gloss-bugzilla"
-><I
-CLASS="glossterm"
->Bugzilla</I
-></A
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Code Example</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-><TT
-CLASS="sgmltag"
-><para></TT
->
-Beginning and end of paragraph
-<TT
-CLASS="sgmltag"
-></para></TT
-></PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="introduction"
-></A
->Chapter 2. Introduction</H1
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="whatis"
-></A
->2.1. What is Bugzilla?</H1
-><P
-> Bugzilla is a bug- or issue-tracking system. Bug-tracking
- systems allow individual or groups of developers effectively to keep track
- of outstanding problems with their product.
- Bugzilla was originally written by Terry Weissman in a programming language
- called <A
-HREF="#gloss-tcl"
-><I
-CLASS="glossterm"
->TCL</I
-></A
->, to
- replace a rudimentary bug-tracking database used internally by Netscape
- Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
- it remains to this day. Most commercial defect-tracking software vendors
- at the time charged enormous licensing fees, and Bugzilla quickly became
- a favorite of the open-source crowd (with its genesis in the open-source
- browser project, Mozilla). It is now the de-facto standard
- defect-tracking system against which all others are measured.
- </P
-><P
->Bugzilla boasts many advanced features. These include:
- <P
-></P
-><UL
-><LI
-><P
->Powerful searching</P
-></LI
-><LI
-><P
->User-configurable email notifications of bug changes</P
-></LI
-><LI
-><P
->Full change history</P
-></LI
-><LI
-><P
->Inter-bug dependency tracking and graphing</P
-></LI
-><LI
-><P
->Excellent attachment management</P
-></LI
-><LI
-><P
->Integrated, product-based, granular security schema</P
-></LI
-><LI
-><P
->Fully security-audited, and runs under Perl's taint mode</P
-></LI
-><LI
-><P
->A robust, stable RDBMS back-end</P
-></LI
-><LI
-><P
->Web, XML, email and console interfaces</P
-></LI
-><LI
-><P
->Completely customisable and/or localisable web user
- interface</P
-></LI
-><LI
-><P
->Extensive configurability</P
-></LI
-><LI
-><P
->Smooth upgrade pathway between versions</P
-></LI
-></UL
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="why"
-></A
->2.2. Why Should We Use Bugzilla?</H1
-><P
->For many years, defect-tracking software has remained principally
- the domain of large software development houses. Even then, most shops
- never bothered with bug-tracking software, and instead simply relied on
- shared lists and email to monitor the status of defects. This procedure
- is error-prone and tends to cause those bugs judged least significant by
- developers to be dropped or ignored.</P
-><P
->These days, many companies are finding that integrated
- defect-tracking systems reduce downtime, increase productivity, and raise
- customer satisfaction with their systems. Along with full disclosure, an
- open bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout the
- data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support
- accountability, telephone support knowledge bases, and a common,
- well-understood system for accounting for unusual system or software
- issues.</P
-><P
->But why should
- <EM
->you</EM
->
-
- use Bugzilla?</P
-><P
->Bugzilla is very adaptable to various situations. Known uses
- currently include IT support queues, Systems Administration deployment
- management, chip design and development problem tracking (both
- pre-and-post fabrication), and software and hardware bug tracking for
- luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as
- <A
-HREF="http://www.cvshome.org"
-TARGET="_top"
->CVS</A
->,
- <A
-HREF="http://www.mozilla.org/bonsai.html"
-TARGET="_top"
->Bonsai</A
->, or
- <A
-HREF="http://www.perforce.com"
-TARGET="_top"
->Perforce SCM</A
->, Bugzilla
- provides a powerful, easy-to-use solution to configuration management and
- replication problems.</P
-><P
->Bugzilla can dramatically increase the productivity and
- accountability of individual employees by providing a documented workflow
- and positive feedback for good performance. How many times do you wake up
- in the morning, remembering that you were supposed to do
- <EM
->something</EM
->
- today, but you just can't quite remember? Put it in Bugzilla, and you
- have a record of it from which you can extrapolate milestones, predict
- product versions for integration, and follow the discussion trail
- that led to critical decisions.</P
-><P
->Ultimately, Bugzilla puts the power in your hands to improve your
- value to your employer or business while providing a usable framework for
- your natural attention to detail and knowledge store to flourish.</P
-></DIV
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="using"
-></A
->Chapter 3. Using Bugzilla</H1
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="how"
-></A
->3.1. How do I use Bugzilla?</H1
-><P
->This section contains information for end-users of Bugzilla.
- There is a Bugzilla test installation, called
- <A
-HREF="http://landfill.bugzilla.org/"
-TARGET="_top"
->Landfill</A
->,
- which you are welcome to play with (if it's up.)
- However, it does not necessarily
- have all Bugzilla features enabled, and often runs cutting-edge versions
- of Bugzilla for testing, so some things may work slightly differently
- than mentioned here.</P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="myaccount"
-></A
->3.1.1. Create a Bugzilla Account</H2
-><P
->If you want to use Bugzilla, first you need to create an account.
- Consult with the administrator responsible for your installation of
- Bugzilla for the URL you should use to access it. If you're
- test-driving Bugzilla, use this URL:
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
-> http://landfill.bugzilla.org/bugzilla-tip/</A
->
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Click the
- <SPAN
-CLASS="QUOTE"
->"Open a new Bugzilla account"</SPAN
->
-
- link, enter your email address and, optionally, your name in the
- spaces provided, then click
- <SPAN
-CLASS="QUOTE"
->"Create Account"</SPAN
->
-
- .</P
-></LI
-><LI
-><P
->Within moments, you should receive an email to the address
- you provided above, which contains your login name (generally the
- same as the email address), and a password you can use to access
- your account. This password is randomly generated, and can be
- changed to something more memorable.</P
-></LI
-><LI
-><P
->Click the
- <SPAN
-CLASS="QUOTE"
->"Log In"</SPAN
->
- link in the yellow area at the bottom of the page in your browser,
- enter your email address and password into the spaces provided, and
- click
- <SPAN
-CLASS="QUOTE"
->"Login"</SPAN
->.
- </P
-></LI
-></OL
-><P
->You are now logged in. Bugzilla uses cookies for authentication
- so, unless your IP address changes, you should not have to log in
- again.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="bug_page"
-></A
->3.1.2. Anatomy of a Bug</H2
-><P
->The core of Bugzilla is the screen which displays a particular
- bug. It's a good place to explain some Bugzilla concepts.
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"
-TARGET="_top"
-> Bug 1 on Landfill</A
->
-
- is a good example. Note that the labels for most fields are hyperlinks;
- clicking them will take you to context-sensitive help on that
- particular field. Fields marked * may not be present on every
- installation of Bugzilla.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <EM
->Product and Component</EM
->:
- Bugs are divided up by Product and Component, with a Product
- having one or more Components in it. For example,
- bugzilla.mozilla.org's "Bugzilla" Product is composed of several
- Components:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <EM
->Administration:</EM
->
- Administration of a Bugzilla installation.</TD
-></TR
-><TR
-><TD
-> <EM
->Bugzilla-General:</EM
->
- Anything that doesn't fit in the other components, or spans
- multiple components.</TD
-></TR
-><TR
-><TD
-> <EM
->Creating/Changing Bugs:</EM
->
- Creating, changing, and viewing bugs.</TD
-></TR
-><TR
-><TD
-> <EM
->Documentation:</EM
->
- The Bugzilla documentation, including The Bugzilla Guide.</TD
-></TR
-><TR
-><TD
-> <EM
->Email:</EM
->
- Anything to do with email sent by Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->Installation:</EM
->
- The installation process of Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->Query/Buglist:</EM
->
- Anything to do with searching for bugs and viewing the
- buglists.</TD
-></TR
-><TR
-><TD
-> <EM
->Reporting/Charting:</EM
->
- Getting reports from Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->User Accounts:</EM
->
- Anything about managing a user account from the user's perspective.
- Saved queries, creating accounts, changing passwords, logging in,
- etc.</TD
-></TR
-><TR
-><TD
-> <EM
->User Interface:</EM
->
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates,
- etc.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></LI
-><LI
-><P
-> <EM
->Status and Resolution:</EM
->
-
- These define exactly what state the bug is in - from not even
- being confirmed as a bug, through to being fixed and the fix
- confirmed by Quality Assurance. The different possible values for
- Status and Resolution on your installation should be documented in the
- context-sensitive help for those items.</P
-></LI
-><LI
-><P
-> <EM
->Assigned To:</EM
->
- The person responsible for fixing the bug.</P
-></LI
-><LI
-><P
-> <EM
->*URL:</EM
->
- A URL associated with the bug, if any.</P
-></LI
-><LI
-><P
-> <EM
->Summary:</EM
->
- A one-sentence summary of the problem.</P
-></LI
-><LI
-><P
-> <EM
->*Status Whiteboard:</EM
->
- (a.k.a. Whiteboard) A free-form text area for adding short notes
- and tags to a bug.</P
-></LI
-><LI
-><P
-> <EM
->*Keywords:</EM
->
- The administrator can define keywords which you can use to tag and
- categorise bugs - e.g. The Mozilla Project has keywords like crash
- and regression.</P
-></LI
-><LI
-><P
-> <EM
->Platform and OS:</EM
->
- These indicate the computing environment where the bug was
- found.</P
-></LI
-><LI
-><P
-> <EM
->Version:</EM
->
- The "Version" field is usually used for versions of a product which
- have been released, and is set to indicate which versions of a
- Component have the particular problem the bug report is
- about.</P
-></LI
-><LI
-><P
-> <EM
->Priority:</EM
->
- The bug assignee uses this field to prioritise his or her bugs.
- It's a good idea not to change this on other people's bugs.</P
-></LI
-><LI
-><P
-> <EM
->Severity:</EM
->
- This indicates how severe the problem is - from blocker
- ("application unusable") to trivial ("minor cosmetic issue"). You
- can also use this field to indicate whether a bug is an enhancement
- request.</P
-></LI
-><LI
-><P
-> <EM
->*Target:</EM
->
- (a.k.a. Target Milestone) A future version by which the bug is to
- be fixed. e.g. The Bugzilla Project's milestones for future
- Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
- restricted to numbers, thought - you can use any text strings, such
- as dates.</P
-></LI
-><LI
-><P
-> <EM
->Reporter:</EM
->
- The person who filed the bug.</P
-></LI
-><LI
-><P
-> <EM
->CC list:</EM
->
- A list of people who get mail when the bug changes.</P
-></LI
-><LI
-><P
-> <EM
->Attachments:</EM
->
- You can attach files (e.g. testcases or patches) to bugs. If there
- are any attachments, they are listed in this section.</P
-></LI
-><LI
-><P
-> <EM
->*Dependencies:</EM
->
- If this bug cannot be fixed unless other bugs are fixed (depends
- on), or this bug stops other bugs being fixed (blocks), their
- numbers are recorded here.</P
-></LI
-><LI
-><P
-> <EM
->*Votes:</EM
->
- Whether this bug has any votes.</P
-></LI
-><LI
-><P
-> <EM
->Additional Comments:</EM
->
- You can add your two cents to the bug discussion here, if you have
- something worthwhile to say.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="query"
-></A
->3.1.3. Searching for Bugs</H2
-><P
->The Bugzilla Search page is is the interface where you can find
- any bug report, comment, or patch currently in the Bugzilla system. You
- can play with it here:
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"
-TARGET="_top"
-> landfill.bugzilla.org/bugzilla-tip/query.cgi</A
->
-
- .</P
-><P
->The Search page has controls for selecting different possible
- values for all of the fields in a bug, as described above. Once you've
- defined a search, you can either run it, or save it as a Remembered
- Query, which can optionally appear in the footer of your pages.</P
-><P
->Highly advanced querying is done using Boolean Charts, which have
- their own
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html"
-TARGET="_top"
-> context-sensitive help</A
->
-
- .</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="list"
-></A
->3.1.4. Bug Lists</H2
-><P
->If you run a search, a list of matching bugs will be returned.
- The default search is to return all open bugs on the system - don't try
- running this search on a Bugzilla installation with a lot of
- bugs!</P
-><P
->The format of the list is configurable. For example, it can be
- sorted by clicking the column headings. Other useful features can be
- accessed using the links at the bottom of the list:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <EM
->Long Format:</EM
->
-
- this gives you a large page with a non-editable summary of the fields
- of each bug.</TD
-></TR
-><TR
-><TD
-> <EM
->Change Columns:</EM
->
-
- change the bug attributes which appear in the list.</TD
-></TR
-><TR
-><TD
-> <EM
->Change several bugs at once:</EM
->
-
- If your account is sufficiently empowered, you can make the same
- change to all the bugs in the list - for example, changing their
- owner.</TD
-></TR
-><TR
-><TD
-> <EM
->Send mail to bug owners:</EM
->
-
- Sends mail to the owners of all bugs on the list.</TD
-></TR
-><TR
-><TD
-> <EM
->Edit this query:</EM
->
-
- If you didn't get exactly the results you were looking for, you can
- return to the Query page through this link and make small revisions
- to the query you just made so you get more accurate results.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="bugreports"
-></A
->3.1.5. Filing Bugs</H2
-><P
->Years of bug writing experience has been distilled for your
- reading pleasure into the
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"
-TARGET="_top"
-> Bug Writing Guidelines</A
->.
- While some of the advice is Mozilla-specific, the basic principles of
- reporting Reproducible, Specific bugs, isolating the Product you are
- using, the Version of the Product, the Component which failed, the
- Hardware Platform, and Operating System you were using at the time of
- the failure go a long way toward ensuring accurate, responsible fixes
- for the bug that bit you.</P
-><P
->The procedure for filing a test bug is as follows:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Go to
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
-> Landfill</A
->
- in your browser and click
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"
-TARGET="_top"
-> Enter a new bug report</A
->.
- </P
-></LI
-><LI
-><P
->Select a product - any one will do.</P
-></LI
-><LI
-><P
->Fill in the fields. Bugzilla should have made reasonable
- guesses, based upon your browser, for the "Platform" and "OS"
- drop-down boxes. If they are wrong, change them.</P
-></LI
-><LI
-><P
->Select "Commit" and send in your bug report.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="hintsandtips"
-></A
->3.2. Hints and Tips</H1
-><P
->This section distills some Bugzilla tips and best practices
- that have been developed.</P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN372"
-></A
->3.2.1. Autolinkification</H2
-><P
->Bugzilla comments are plain text - so posting HTML will result
- in literal HTML tags rather than being interpreted by a browser.
- However, Bugzilla will automatically make hyperlinks out of certain
- sorts of text in comments. For example, the text
- http://www.bugzilla.org will be turned into
- <A
-HREF="http://www.bugzilla.org"
-TARGET="_top"
->http://www.bugzilla.org</A
->.
- Other strings which get linkified in the obvious manner are:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->bug 12345</TD
-></TR
-><TR
-><TD
->bug 23456, comment 53</TD
-></TR
-><TR
-><TD
->attachment 4321</TD
-></TR
-><TR
-><TD
->mailto:george@example.com</TD
-></TR
-><TR
-><TD
->george@example.com</TD
-></TR
-><TR
-><TD
->ftp://ftp.mozilla.org</TD
-></TR
-><TR
-><TD
->Most other sorts of URL</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->A corollary here is that if you type a bug number in a comment,
- you should put the word "bug" before it, so it gets autolinkified
- for the convenience of others.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="quicksearch"
-></A
->3.2.2. Quicksearch</H2
-><P
->Quicksearch is a single-text-box query tool which uses
- metacharacters to indicate what is to be searched. For example, typing
- "<TT
-CLASS="filename"
->foo|bar</TT
->"
- into Quicksearch would search for "foo" or "bar" in the
- summary and status whiteboard of a bug; adding
- "<TT
-CLASS="filename"
->:BazProduct</TT
->" would
- search only in that product.
- </P
-><P
->You'll find the Quicksearch box on Bugzilla's
- front page, along with a
- <A
-HREF="../../quicksearch.html"
-TARGET="_top"
->Help</A
->
- link which details how to use it.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="commenting"
-></A
->3.2.3. Comments</H2
-><P
->If you are changing the fields on a bug, only comment if
- either you have something pertinent to say, or Bugzilla requires it.
- Otherwise, you may spam people unnecessarily with bug mail.
- To take an example: a user can set up their account to filter out messages
- where someone just adds themselves to the CC field of a bug
- (which happens a lot.) If you come along, add yourself to the CC field,
- and add a comment saying "Adding self to CC", then that person
- gets a pointless piece of mail they would otherwise have avoided.
- </P
-><P
-> Don't use sigs in comments. Signing your name ("Bill") is acceptable,
- particularly if you do it out of habit, but full mail/news-style
- four line ASCII art creations are not.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="attachments"
-></A
->3.2.4. Attachments</H2
-><P
-> Use attachments, rather than comments, for large chunks of ASCII data,
- such as trace, debugging output files, or log files. That way, it doesn't
- bloat the bug for everyone who wants to read it, and cause people to
- receive fat, useless mails.
- </P
-><P
->Trim screenshots. There's no need to show the whole screen if
- you are pointing out a single-pixel problem.
- </P
-><P
->Don't attach simple test cases (e.g. one HTML file, one
- CSS file and an image) as a ZIP file. Instead, upload them in
- reverse order and edit the referring file so that they point to the
- attached files. This way, the test case works immediately
- out of the bug.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN401"
-></A
->3.2.5. Filing Bugs</H2
-><P
->Try to make sure that everything said in the summary is also
- said in the first comment. Summaries are often updated and this will
- ensure your original information is easily accessible.
- </P
-><P
-> You do not need to put "any" or similar strings in the URL field.
- If there is no specific URL associated with the bug, leave this
- field blank.
- </P
-><P
->If you feel a bug you filed was incorrectly marked as a
- DUPLICATE of another, please question it in your bug, not
- the bug it was duped to. Feel free to CC the person who duped it
- if they are not already CCed.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="userpreferences"
-></A
->3.3. User Preferences</H1
-><P
->Once you have logged in, you can customise various aspects of
- Bugzilla via the "Edit prefs" link in the page footer.
- The preferences are split into four tabs:</P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="accountsettings"
-></A
->3.3.1. Account Settings</H2
-><P
->On this tab, you can change your basic account information,
- including your password, email address and real name. For security
- reasons, in order to change anything on this page you must type your
- <EM
->current</EM
->
- password into the
- <SPAN
-CLASS="QUOTE"
->"Password"</SPAN
->
- field at the top of the page.
- If you attempt to change your email address, a confirmation
- email is sent to both the old and new addresses, with a link to use to
- confirm the change. This helps to prevent account hijacking.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="emailsettings"
-></A
->3.3.2. Email Settings</H2
-><P
->On this tab you can reduce or increase the amount of email sent
- you from Bugzilla, opting in our out depending on your relationship to
- the bug and the change that was made to it. (Note that you can also do
- client-side filtering using the X-Bugzilla-Reason header which Bugzilla
- adds to all bugmail.)</P
-><P
->By entering user email names, delineated by commas, into the
- "Users to watch" text entry box you can receive a copy of all the
- bugmail of other users (security settings permitting.) This powerful
- functionality enables seamless transitions as developers change
- projects or users go on holiday.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The ability to watch other users may not be available in all
- Bugzilla installations. If you can't see it, ask your
- administrator.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="footersettings"
-></A
->3.3.3. Page Footer</H2
-><P
->On the Search page, you can store queries in Bugzilla, so if you
- regularly run a particular query it is just a drop-down menu away.
- Once you have a stored query, you can come
- here to request that it also be displayed in your page footer.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="permissionsettings"
-></A
->3.3.4. Permissions</H2
-><P
->This is a purely informative page which outlines your current
- permissions on this installation of Bugzilla - what product groups you
- are in, and whether you can edit bugs or perform various administration
- functions.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="installation"
-></A
->Chapter 4. Installation</H1
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="stepbystep"
-></A
->4.1. Step-by-step Install</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN430"
-></A
->4.1.1. Introduction</H2
-><P
->Bugzilla has been successfully installed under Solaris, Linux,
- and Win32. Win32 is not yet officially supported, but many people
- have got it working fine.
- Please see the
- <A
-HREF="#win32"
->Win32 Installation Notes</A
->
- for further advice on getting Bugzilla to work on Microsoft
- Windows.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN434"
-></A
->4.1.2. Package List</H2
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you are running the very most recent
- version of Perl and MySQL (both the executables and development
- libraries) on your system, you can skip these manual installation
- steps for the Perl modules by using Bundle::Bugzilla; see
- <A
-HREF="#bundlebugzilla"
->Using Bundle::Bugzilla instead of manually installing Perl modules</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The software packages necessary for the proper running of
- Bugzilla (with download links) are:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <A
-HREF="http://www.mysql.com/"
-TARGET="_top"
->MySQL database server</A
->
- (3.22.5 or greater)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.perl.org"
-TARGET="_top"
->Perl</A
->
- (5.005 or greater, 5.6.1 is recommended if you wish to
- use Bundle::Bugzilla)
- </P
-></LI
-><LI
-><P
->Perl Modules (minimum version):
- <P
-></P
-><OL
-TYPE="a"
-><LI
-><P
-> <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template</A
->
- (v2.07)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/AppConfig/"
-TARGET="_top"
->AppConfig
- </A
->
- (v1.52)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar.gz"
-TARGET="_top"
->Text::Wrap</A
->
- (v2001.0131)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://search.cpan.org/search?dist=File-Spec"
-TARGET="_top"
->File::Spec
- </A
->
- (v0.8.2)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Data/"
-TARGET="_top"
->Data::Dumper
- </A
->
- (any)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Mysql/"
-TARGET="_top"
->DBD::mysql
- </A
->
- (v1.2209)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/DBI/"
-TARGET="_top"
->DBI</A
->
- (v1.13)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Date/"
-TARGET="_top"
->Date::Parse
- </A
->
- (any)
- </P
-></LI
-><LI
-><P
-> CGI::Carp
- (any)
- </P
-></LI
-></OL
->
- and, optionally:
- <P
-></P
-><OL
-TYPE="a"
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/GD/"
-TARGET="_top"
->GD</A
->
- (v1.19) for bug charting
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Chart/"
-TARGET="_top"
->Chart::Base
- </A
->
- (v0.99c) for bug charting
- </P
-></LI
-><LI
-><P
-> XML::Parser
- (any) for the XML interface
- </P
-></LI
-><LI
-><P
-> MIME::Parser
- (any) for the email interface
- </P
-></LI
-></OL
->
- </P
-></LI
-><LI
-><P
-> The web server of your choice.
- <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache</A
->
- is highly recommended.
- </P
-></LI
-></OL
->
-
- <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is a good idea, while installing Bugzilla, to ensure that there
- is some kind of firewall between you and the rest of the Internet,
- because your machine may be insecure for periods during the install.
- Many
- installation steps require an active Internet connection to complete,
- but you must take care to ensure that at no point is your machine
- vulnerable to an attack.</P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Linux-Mandrake 8.0 includes every
- required and optional library for Bugzilla. The easiest way to
- install them is by using the
- <TT
-CLASS="filename"
->urpmi</TT
->
-
- utility. If you follow these commands, you should have everything you
- need for Bugzilla, and
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- should not complain about any missing libraries. You may already have
- some of these installed.</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-mysql</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-chart</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-gd</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-MailTools</B
->
-
- (for Bugzilla email integration)</TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi apache-modules</B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="install-mysql"
-></A
->4.1.3. MySQL</H2
-><P
->Visit the MySQL homepage at
- <A
-HREF="http://www.mysql.com"
-TARGET="_top"
->www.mysql.com</A
->
- to grab and install the latest stable release of the server.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Many of the binary
- versions of MySQL store their data files in
- <TT
-CLASS="filename"
->/var</TT
->.
- On some Unix systems, this is part of a smaller root partition,
- and may not have room for your bug database. You can set the data
- directory as an option to <TT
-CLASS="filename"
->configure</TT
->
- if you build MySQL from source yourself.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you install from something other than an RPM or Debian
- package, you will need to add <TT
-CLASS="filename"
->mysqld</TT
->
- to your init scripts so the server daemon will come back up whenever
- your machine reboots. Further discussion of UNIX init sequences are
- beyond the scope of this guide.
- </P
-><P
->Change your init script to start
- <TT
-CLASS="filename"
->mysqld</TT
->
- with the ability to accept large packets. By default,
- <TT
-CLASS="filename"
->mysqld</TT
->
- only accepts packets up to 64K long. This limits the size of
- attachments you may put on bugs. If you add
- <TT
-CLASS="option"
->-O max_allowed_packet=1M</TT
->
- to the command that starts
- <TT
-CLASS="filename"
->mysqld</TT
->
- (or <TT
-CLASS="filename"
->safe_mysqld</TT
->),
- then you will be able to have attachments up to about 1 megabyte.
- There is a Bugzilla parameter for maximum attachment size;
- you should configure it to match the value you choose here.</P
-><P
->If you plan on running Bugzilla and MySQL on the same machine,
- consider using the
- <TT
-CLASS="option"
->--skip-networking</TT
->
- option in the init script. This enhances security by preventing
- network access to MySQL.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="install-perl"
-></A
->4.1.4. Perl</H2
-><P
->Any machine that doesn't have Perl on it is a sad machine indeed.
- Perl can be got in source form from
- <A
-HREF="http://www.perl.com"
-TARGET="_top"
->perl.com</A
-> for the rare
- *nix systems which don't have it.
- Although Bugzilla runs with all post-5.005
- versions of Perl, it's a good idea to be up to the very latest version
- if you can when running Bugzilla. As of this writing, that is Perl
- version 5.6.1.</P
-><DIV
-CLASS="tip"
-><A
-NAME="bundlebugzilla"
-></A
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can skip the following Perl module installation steps by
- installing
- <SPAN
-CLASS="productname"
->Bundle::Bugzilla</SPAN
->
-
- from
- <A
-HREF="#gloss-cpan"
-><I
-CLASS="glossterm"
->CPAN</I
-></A
->,
- which installs all required modules for you.</P
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->perl -MCPAN -e 'install "Bundle::Bugzilla"'</B
->
- </TT
->
- </P
-><P
->Bundle::Bugzilla doesn't include GD, Chart::Base, or
- MIME::Parser, which are not essential to a basic Bugzilla install. If
- installing this bundle fails, you should install each module
- individually to isolate the problem.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="perl-modules"
-></A
->4.1.5. Perl Modules</H2
-><P
->
- All Perl modules can be found on the
- <A
-HREF="http://www.cpan.org"
-TARGET="_top"
->Comprehensive Perl
- Archive Network</A
-> (CPAN). The
- CPAN servers have a real tendency to bog down, so please use mirrors.
- </P
-><P
->Quality, general Perl module installation instructions can be
- found on the CPAN website, but the easy thing to do is to just use the
- CPAN shell which does all the hard work for you.
- To use the CPAN shell to install a module:
- </P
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
- <B
-CLASS="command"
->perl -MCPAN -e 'install "<modulename>"'</B
->
- </TT
->
- </P
-><P
-> To do it the hard way:
- </P
-><P
->Untar the module tarball -- it should create its own
- directory</P
-><P
->CD to the directory just created, and enter the following
- commands:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->perl Makefile.PL</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make test</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make install</B
->
- </TT
->
- </P
-></LI
-></OL
->
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Many people complain that Perl modules will not install for
- them. Most times, the error messages complain that they are missing a
- file in
- <SPAN
-CLASS="QUOTE"
->"@INC"</SPAN
->.
- Virtually every time, this error is due to permissions being set too
- restrictively for you to compile Perl modules or not having the
- necessary Perl development libraries installed on your system.
- Consult your local UNIX systems administrator for help solving these
- permissions issues; if you
- <EM
->are</EM
->
- the local UNIX sysadmin, please consult the newsgroup/mailing list
- for further assistance or hire someone to help you out.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN580"
-></A
->4.1.5.1. DBI</H3
-><P
->The DBI module is a generic Perl module used the
- MySQL-related modules. As long as your Perl installation was done
- correctly the DBI module should be a breeze. It's a mixed Perl/C
- module, but Perl's MakeMaker system simplifies the C compilation
- greatly.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN583"
-></A
->4.1.5.2. Data::Dumper</H3
-><P
->The Data::Dumper module provides data structure persistence for
- Perl (similar to Java's serialization). It comes with later
- sub-releases of Perl 5.004, but a re-installation just to be sure it's
- available won't hurt anything.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN586"
-></A
->4.1.5.3. MySQL-related modules</H3
-><P
->The Perl/MySQL interface requires a few mutually-dependent Perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package.</P
-><P
->The MakeMaker process will ask you a few questions about the
- desired compilation target and your MySQL installation. For most of the
- questions the provided default will be adequate, but when asked if your
- desired target is the MySQL or mSQL packages, you should
- select the MySQL related ones. Later you will be asked if you wish to
- provide backwards compatibility with the older MySQL packages; you
- should answer YES to this question. The default is NO.</P
-><P
->A host of 'localhost' should be fine and a testing user of 'test'
- with a null password should find itself with sufficient access to run
- tests on the 'test' database which MySQL created upon installation.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN591"
-></A
->4.1.5.4. TimeDate modules</H3
-><P
->Many of the more common date/time/calendar related Perl modules
- have been grouped into a bundle similar to the MySQL modules bundle.
- This bundle is stored on the CPAN under the name TimeDate.
- The component module we're most interested in is the Date::Format
- module, but installing all of them is probably a good idea anyway.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN594"
-></A
->4.1.5.5. GD (optional)</H3
-><P
->The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become the
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on millions of web pages to
- generate graphs on the fly. That's what Bugzilla will be using it for
- so you must install it if you want any of the graphing to work.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The Perl GD library requires some other libraries that may or
- may not be installed on your system, including
- <TT
-CLASS="classname"
->libpng</TT
->
- and
- <TT
-CLASS="classname"
->libgd</TT
->.
- The full requirements are listed in the Perl GD library README.
- If compiling GD fails, it's probably because you're
- missing a required library.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN601"
-></A
->4.1.5.6. Chart::Base (optional)</H3
-><P
->The Chart module provides Bugzilla with on-the-fly charting
- abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN.
- Note that earlier versions that 0.99c used GIFs, which are no longer
- supported by the latest versions of GD.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN604"
-></A
->4.1.5.7. Template Toolkit</H3
-><P
->When you install Template Toolkit, you'll get asked various
- questions about features to enable. The defaults are fine, except
- that it is recommended you use the high speed XS Stash of the Template
- Toolkit, in order to achieve best performance. However, there are
- known problems with XS Stash and Perl 5.005_02 and lower. If you
- wish to use these older versions of Perl, please use the regular
- stash.</P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN607"
-></A
->4.1.6. HTTP Server</H2
-><P
->You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can run the web server on a
- different machine than MySQL, but need to adjust the MySQL
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- user permissions accordingly.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->We strongly recommend Apache as the web server to use. The
- Bugzilla Guide installation instructions, in general, assume you are
- using Apache. If you have got Bugzilla working using another webserver,
- please share your experiences with us.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->You'll want to make sure that your web server will run any file
- with the .cgi extension as a CGI and not just display it. If you're
- using Apache that means uncommenting the following line in the httpd.conf
- file:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->AddHandler cgi-script .cgi</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->With Apache you'll also want to make sure that within the
- httpd.conf file the line:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> Options ExecCGI
-AllowOverride Limit
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- is in the stanza that covers the directories into which you intend to
- put the bugzilla .html and .cgi files.
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->AllowOverride Limit allows the use of a Deny statement in the
- .htaccess file generated by checksetup.pl</P
-><P
->Users of older versions of Apache may find the above lines
- in the srm.conf and access.conf files, respecitvely.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are important files and directories that should not be a
- served by the HTTP server - most files in the
- <SPAN
-CLASS="QUOTE"
->"data"</SPAN
->
- and
- <SPAN
-CLASS="QUOTE"
->"shadow"</SPAN
->
- directories and the
- <SPAN
-CLASS="QUOTE"
->"localconfig"</SPAN
->
- file. You should configure your HTTP server to not serve
- these files. Failure to do so will expose critical passwords and
- other data. Please see
- <A
-HREF="#htaccess"
->.htaccess files and security</A
->
- for details on how to do this for Apache; the checksetup.pl
- script should create appropriate .htaccess files for you.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN626"
-></A
->4.1.7. Bugzilla</H2
-><P
->You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->).
- You may decide to put the files in the main web space for your
- web server or perhaps in
- <TT
-CLASS="filename"
->/usr/local</TT
->
- with a symbolic link in the web space that points to the Bugzilla
- directory.</P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you symlink the bugzilla directory into your Apache's HTML
- heirarchy, you may receive
- <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
- errors unless you add the
- <SPAN
-CLASS="QUOTE"
->"FollowSymLinks"</SPAN
->
- directive to the <Directory> entry for the HTML root
- in httpd.conf.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user. This is a temporary step
- until you run the post-install
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
- script, which locks down your installation.</P
-><P
->Lastly, you'll need to set up a symbolic link to
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
->
- for the correct location of your Perl executable (probably
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
->).
- Otherwise you must hack all the .cgi files to change where they look
- for Perl. This can be done using the following Perl one-liner, but
- I suggest using the symlink approach to avoid upgrade hassles.
- </P
-><P
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->perl -pi -e
- 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
- processmail syncshadowdb</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- Change <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> to match the location
- of Perl on your machine.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN643"
-></A
->4.1.8. Setting Up the MySQL Database</H2
-><P
->After you've gotten all the software installed and working you're
- ready to start preparing the database for its life as the back end to
- a high quality bug tracker.</P
-><P
->First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla
- username will be
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->, and will have minimal permissions.
- </P
-><P
->Begin by giving the MySQL root user a password. MySQL passwords are limited
- to 16 characters.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->mysql -u root mysql</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->UPDATE user SET Password=PASSWORD('<new_password>')
- WHERE user='root';</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
- From this point on, if you need to access MySQL as the MySQL root user,
- you will need to use
- <B
-CLASS="command"
->mysql -u root -p</B
->
-
- and enter <new_password>. Remember that MySQL user names have
- nothing to do with Unix user names (login names).</P
-><P
->Next, we use an SQL <B
-CLASS="command"
->GRANT</B
-> command to create a
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- user, and grant sufficient permissions for checksetup.pl, which we'll
- use later, to work its magic. This also restricts the
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- user to operations within a database called
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->, and only allows the account to connect from
- <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->.
- Modify it to reflect your setup if you will be connecting from
- another machine or as a different user.</P
-><P
->Remember to set <bugs_password> to some unique password.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost
- IDENTIFIED BY '<bugs_password>';</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using MySQL 4, the bugs user also needs to be granted
- the LOCK TABLES and CREATE TEMPORARY TABLES permissions.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN681"
-></A
->4.1.9. <TT
-CLASS="filename"
->checksetup.pl</TT
-></H2
-><P
->Next, run the magic checksetup.pl script. (Many thanks to
- <A
-HREF="mailto:holgerschurig@nikocity.de"
-TARGET="_top"
->Holger Schurig </A
->
- for writing this script!)
- This script is designed to make sure your MySQL database and other
- configuration options are consistent with the Bugzilla CGI files.
- It will make sure Bugzilla files and directories have reasonable
- permissions, set up the
- <TT
-CLASS="filename"
->data</TT
->
- directory, and create all the MySQL tables.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->./checksetup.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
- The first time you run it, it will create a file called
- <TT
-CLASS="filename"
->localconfig</TT
->.</P
-><P
->This file contains a variety of settings you may need to tweak
- including how Bugzilla should connect to the MySQL database.</P
-><P
->The connection settings include:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->server's host: just use
- <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->
- if the MySQL server is local</P
-></LI
-><LI
-><P
->database name:
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- if you're following these directions</P
-></LI
-><LI
-><P
->MySQL username:
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- if you're following these directions</P
-></LI
-><LI
-><P
->Password for the
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- MySQL account; (<bugs_password>) above</P
-></LI
-></OL
->
- </P
-><P
->Once you are happy with the settings,
- <TT
-CLASS="filename"
->su</TT
-> to the user
- your web server runs as, and re-run
- <TT
-CLASS="filename"
->checksetup.pl</TT
->. (Note: on some security-conscious
- systems, you may need to change the login shell for the webserver
- account before you can do this.)
- On this second run, it will create the database and an administrator
- account for which you will be prompted to provide information.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The checksetup.pl script is designed so that you can run it at
- any time without causing harm. You should run it after any upgrade to
- Bugzilla.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN713"
-></A
->4.1.10. Configuring Bugzilla</H2
-><P
-> You should run through the parameters on the Edit Parameters page
- (link in the footer) and set them all to appropriate values.
- They key parameters are documented in <A
-HREF="#parameters"
->Section 5.1</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="extraconfig"
-></A
->4.2. Optional Additional Configuration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN719"
-></A
->4.2.1. Dependency Charts</H2
-><P
->As well as the text-based dependency graphs, Bugzilla also
- supports dependency graphing, using a package called 'dot'.
- Exactly how this works is controlled by the 'webdotbase' parameter,
- which can have one of three values:
- </P
-><P
-> <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> A complete file path to the command 'dot' (part of
- <A
-HREF="http://www.graphviz.org/"
-TARGET="_top"
->GraphViz</A
->)
- will generate the graphs locally
- </P
-></LI
-><LI
-><P
-> A URL prefix pointing to an installation of the webdot package will
- generate the graphs remotely
- </P
-></LI
-><LI
-><P
-> A blank value will disable dependency graphing.
- </P
-></LI
-></OL
->
- </P
-><P
->So, to get this working, install
- <A
-HREF="http://www.graphviz.org/"
-TARGET="_top"
->GraphViz</A
->. If you
- do that, you need to
- <A
-HREF="http://httpd.apache.org/docs/mod/mod_imap.html"
-TARGET="_top"
->enable
- server-side image maps</A
-> in Apache.
- Alternatively, you could set up a webdot server, or use the AT&T
- public webdot server (the
- default for the webdotbase param). Note that AT&T's server won't work
- if Bugzilla is only accessible using HTTPS.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN734"
-></A
->4.2.2. Bug Graphs</H2
-><P
->As long as you installed the GD and Graph::Base Perl modules you
- might as well turn on the nifty Bugzilla bug reporting graphs.</P
-><P
->Add a cron entry like this to run
- <TT
-CLASS="filename"
->collectstats.pl</TT
->
- daily at 5 after midnight:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->crontab -e</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
->5 0 * * * cd <your-bugzilla-directory> ;
- ./collectstats.pl</TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->After two days have passed you'll be able to view bug graphs from
- the Bug Reports page.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN747"
-></A
->4.2.3. The Whining Cron</H2
-><P
->By now you have a fully functional Bugzilla, but what good are
- bugs if they're not annoying? To help make those bugs more annoying you
- can set up Bugzilla's automatic whining system to complain at engineers
- which leave their bugs in the NEW state without triaging them.
- </P
-><P
-> This can be done by
- adding the following command as a daily crontab entry (for help on that
- see that crontab man page):
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <B
-CLASS="command"
->cd <your-bugzilla-directory> ;
- ./whineatnews.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Depending on your system, crontab may have several manpages.
- The following command should lead you to the most useful page for
- this purpose:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->man 5 crontab</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="bzldap"
-></A
->4.2.4. LDAP Authentication</H2
-><P
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This information on using the LDAP
- authentication options with Bugzilla is old, and the authors do
- not know of anyone who has tested it. Approach with caution.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
-> The existing authentication
- scheme for Bugzilla uses email addresses as the primary user ID, and a
- password to authenticate that user. All places within Bugzilla where
- you need to deal with user ID (e.g assigning a bug) use the email
- address. The LDAP authentication builds on top of this scheme, rather
- than replacing it. The initial log in is done with a username and
- password for the LDAP directory. This then fetches the email address
- from LDAP and authenticates seamlessly in the standard Bugzilla
- authentication scheme using this email address. If an account for this
- address already exists in your Bugzilla system, it will log in to that
- account. If no account for that email address exists, one is created at
- the time of login. (In this case, Bugzilla will attempt to use the
- "displayName" or "cn" attribute to determine the user's full name.)
- After authentication, all other user-related tasks are still handled by
- email address, not LDAP username. You still assign bugs by email
- address, query on users by email address, etc.
- </P
-><P
->Using LDAP for Bugzilla authentication requires the
- Mozilla::LDAP (aka PerLDAP) Perl module. The
- Mozilla::LDAP module in turn requires Netscape's Directory SDK for C.
- After you have installed the SDK, then install the PerLDAP module.
- Mozilla::LDAP and the Directory SDK for C are both
- <A
-HREF="http://www.mozilla.org/directory/"
-TARGET="_top"
->available for
- download</A
-> from mozilla.org.
- </P
-><P
-> Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
- directory for
- authentication. Be very careful when setting up this parameter; if you
- set LDAP authentication, but do not have a valid LDAP directory set up,
- you will not be able to log back in to Bugzilla once you log out. (If
- this happens, you can get back in by manually editing the data/params
- file, and setting useLDAP back to 0.)
- </P
-><P
->If using LDAP, you must set the
- three additional parameters: Set LDAPserver to the name (and optionally
- port) of your LDAP server. If no port is specified, it defaults to the
- default port of 389. (e.g "ldap.mycompany.com" or
- "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching
- for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids
- must be unique under the DN specified here. Set LDAPmailattribute to
- the name of the attribute in your LDAP directory which contains the
- primary email address. On most directory servers available, this is
- "mail", but you may need to change this.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="content-type"
-></A
->4.2.5. Preventing untrusted Bugzilla content from executing malicious
- Javascript code</H2
-><P
->It is possible for a Bugzilla to execute malicious Javascript
- code. Due to internationalization concerns, we are unable to
- incorporate the code changes necessary to fulfill the CERT advisory
- requirements mentioned in
- <A
-HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3"
-TARGET="_top"
-> http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
->.
- Executing the following code snippet from a UNIX command shell will
- rectify the problem if your Bugzilla installation is intended for an
- English-speaking audience. As always, be sure your Bugzilla
- installation has a good backup before making changes, and I recommend
- you understand what the script is doing before executing it.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->All this one-liner command does is search for all instances of
- <SPAN
-CLASS="QUOTE"
->"Content-type: text/html"</SPAN
->
-
- and replaces it with
- <SPAN
-CLASS="QUOTE"
->"Content-Type: text/html; charset=ISO-8859-1"</SPAN
->
-
- . This specification prevents possible Javascript attacks on the
- browser, and is suggested for all English-speaking sites. For
- non-English-speaking Bugzilla sites, I suggest changing
- <SPAN
-CLASS="QUOTE"
->"ISO-8859-1"</SPAN
->, above, to
- <SPAN
-CLASS="QUOTE"
->"UTF-8"</SPAN
->.</P
-><P
->Note: using <meta> tags to set the charset is not
- recommended, as there's a bug in Netscape 4.x which causes pages
- marked up in this way to load twice.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="htaccess"
-></A
->4.2.6. <TT
-CLASS="filename"
->.htaccess</TT
->
- files and security</H2
-><P
->To enhance the security of your Bugzilla installation, Bugzilla's
- <TT
-CLASS="filename"
->checksetup.pl</TT
-> script will generate
- <I
-CLASS="glossterm"
-> <TT
-CLASS="filename"
->.htaccess</TT
->
- </I
->
-
- files which the Apache webserver can use to restrict access to the
- bugzilla data files.
- These .htaccess files will not work with Apache 1.2.x - but this
- has security holes, so you shouldn't be using it anyway.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using an alternate provider of
- <SPAN
-CLASS="productname"
->webdot</SPAN
->
-
- services for graphing (as described when viewing
- <TT
-CLASS="filename"
->editparams.cgi</TT
->
-
- in your web browser), you will need to change the ip address in
- <TT
-CLASS="filename"
->data/webdot/.htaccess</TT
->
-
- to the ip address of the webdot server that you are using.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->The default .htaccess file may not provide adequate access
- restrictions, depending on your web server configuration. Be sure to
- check the <Directory> entries for your Bugzilla directory so that
- the
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- file is allowed to override web server defaults. For instance, let's
- assume your installation of Bugzilla is installed to
- <TT
-CLASS="filename"
->/usr/local/bugzilla</TT
->
-
- . You should have this <Directory> entry in your
- <TT
-CLASS="filename"
->httpd.conf</TT
->
-
- file:</P
-><P
->
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <Directory /usr/local/bugzilla/>
- Options +FollowSymLinks +Indexes +Includes +ExecCGI
- AllowOverride All
-</Directory>
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- </P
-><P
->The important part above is
- <SPAN
-CLASS="QUOTE"
->"AllowOverride All"</SPAN
->
-
- . Without that, the
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- file created by
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- will not have sufficient permissions to protect your Bugzilla
- installation.</P
-><P
->If you are using Internet Information Server (IIS) or another
- web server which does not observe
- <TT
-CLASS="filename"
->.htaccess</TT
->
- conventions, you can disable their creation by editing
- <TT
-CLASS="filename"
->localconfig</TT
->
- and setting the
- <TT
-CLASS="varname"
->$create_htaccess</TT
->
- variable to
- <TT
-CLASS="parameter"
-><I
->0</I
-></TT
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="mod-throttle"
-></A
->4.2.7. <TT
-CLASS="filename"
->mod_throttle</TT
->
-
- and Security</H2
-><P
->It is possible for a user, by mistake or on purpose, to access
- the database many times in a row which can result in very slow access
- speeds for other users. If your Bugzilla installation is experiencing
- this problem , you may install the Apache module
- <TT
-CLASS="filename"
->mod_throttle</TT
->
-
- which can limit connections by ip-address. You may download this module
- at
- <A
-HREF="http://www.snert.com/Software/mod_throttle/"
-TARGET="_top"
->http://www.snert.com/Software/mod_throttle/</A
->
- Follow the instructions to install into your Apache install.
- <EM
->This module only functions with the Apache web
- server!</EM
->
- You may use the
- <B
-CLASS="command"
->ThrottleClientIP</B
->
-
- command provided by this module to accomplish this goal. See the
- <A
-HREF="http://www.snert.com/Software/mod_throttle/"
-TARGET="_top"
->Module
- Instructions</A
->
- for more information.</P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="win32"
-></A
->4.3. Win32 Installation Notes</H1
-><P
->This section covers installation on Microsoft Windows.
- Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
- wish to emphasise that The easiest way to install Bugzilla on
- Intel-archiecture machines
- is to install some variant of GNU/Linux, then follow the UNIX
- installation instructions in this Guide. If you have any influence in the
- platform choice for running this system, please choose GNU/Linux instead
- of Microsoft Windows.</P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->After that warning, here's the situation for 2.16
- and Windows. It doesn't work at all out of the box.
- You are almost certainly better off getting
- the 2.17 version from CVS (after consultation with the Bugzilla Team to
- make sure you are pulling on a stable day) because we'll be doing a load
- of work to make the Win32 experience more pleasant than it is now.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
-> If you still want to try this, to have any hope of getting it to work,
- you'll need to apply the
- <A
-HREF=""
-TARGET="_top"
->mail patch</A
-> from
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=124174"
-TARGET="_top"
->bug 124174</A
->.
- After that, you'll need to read the (outdated) installation
- instructions below, some (probably a lot better) <A
-HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view"
-TARGET="_top"
->more
- recent ones</A
-> kindly provided by Toms Baugis and Jean-Sebastien
- Guay, and also check the
- <A
-HREF="http://www.bugzilla.org/releases/2.16/docs/win32.html"
-TARGET="_top"
->Bugzilla 2.16 Win32 update page
- </A
->. If we get time,
- we'll write some better installation instructions for 2.16 and put
- them up there. But no promises.
- </P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="wininstall"
-></A
->4.3.1. Win32 Installation: Step-by-step</H2
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You should be familiar with, and cross-reference, the rest of
- the
- <A
-HREF="#installation"
->Bugzilla Installation</A
->
-
- section while performing your Win32 installation.</P
-><P
->Making Bugzilla work on Microsoft Windows is no picnic. Support
- for Win32 has improved dramatically in the last few releases, but, if
- you choose to proceed, you should be a
- <EM
->very</EM
->
-
- skilled Windows Systems Administrator with strong troubleshooting
- abilities, a high tolerance for pain, and moderate perl skills.
- Bugzilla on NT requires hacking source code and implementing some
- advanced utilities. What follows is the recommended installation
- procedure for Win32; additional suggestions are provided in
- <A
-HREF="#faq"
->Appendix A</A
->
-
- .</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->Install
- <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache Web Server</A
->
-
- for Windows, and copy the Bugzilla files somewhere Apache can serve
- them. Please follow all the instructions referenced in
- <A
-HREF="#installation"
->Bugzilla Installation</A
->
-
- regarding your Apache configuration, particularly instructions
- regarding the
- <SPAN
-CLASS="QUOTE"
->"AddHandler"</SPAN
->
-
- parameter and
- <SPAN
-CLASS="QUOTE"
->"ExecCGI"</SPAN
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You may also use Internet Information Server or Personal
- Web Server for this purpose. However, setup is quite different.
- If ActivePerl doesn't seem to handle your file associations
- correctly (for .cgi and .pl files), please consult
- <A
-HREF="#faq"
->Appendix A</A
->
-
- .</P
-><P
->If you are going to use IIS, if on Windows NT you must be
- updated to at least Service Pack 4. Windows 2000 ships with a
- sufficient version of IIS.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Install
- <A
-HREF="http://www.activestate.com/"
-TARGET="_top"
->ActivePerl</A
->
-
- for Windows. Check
- <A
-HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
-TARGET="_top"
-> http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A
->
-
- for a current compiled binary.</P
-><P
->Please also check the following links to fully understand the
- status of ActivePerl on Win32:
- <A
-HREF="http://language.perl.com/newdocs/pod/perlport.html"
-TARGET="_top"
-> Perl Porting</A
->
-
- , and
- <A
-HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
-TARGET="_top"
-> Perl on Win32 FAQ</A
->
- </P
-></LI
-><LI
-><P
->Use ppm from your perl\bin directory to install the following
- packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
- AppConfig, and Template. You may need to extract them from .zip
- format using Winzip or other unzip program first. Most of these
- additional ppm modules can be downloaded from ActiveState, but
- AppConfig and Template should be obtained from OpenInteract using
- <A
-HREF="http://openinteract.sourceforge.net/"
-TARGET="_top"
->the
- instructions on the Template Toolkit web site</A
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can find a list of modules at
- <A
-HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
->
-
- or
- <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The syntax for ppm is:
- <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->ppm <modulename></B
->
- </TT
->
- </P
-><DIV
-CLASS="example"
-><A
-NAME="AEN863"
-></A
-><P
-><B
->Example 4-1. Installing ActivePerl ppd Modules on Microsoft
- Windows</B
-></P
-><P
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->ppm
- <TT
-CLASS="option"
->DBD-Mysql</TT
->
- </B
->
- </P
-><P
->Watch your capitalization!</P
-></DIV
-><P
->ActiveState's 5.6Plus directory also contains an AppConfig
- ppm, so you might see the following error when trying to install
- the version at OpenInteract:</P
-><P
-> <TT
-CLASS="computeroutput"
->Error installing package 'AppConfig': Read a PPD
- for 'AppConfig', but it is not intended for this build of Perl
- (MSWin32-x86-multi-thread)</TT
->
- </P
-><P
->If so, download both
- <A
-HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.tar.gz"
-TARGET="_top"
-> the tarball</A
->
-
- and
- <A
-HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.ppd"
-TARGET="_top"
-> the ppd</A
->
-
- directly from OpenInteract, then run ppm from within the same
- directory to which you downloaded those files and install the
- package by referencing the ppd file explicitly via in the install
- command, f.e.:
- <DIV
-CLASS="example"
-><A
-NAME="AEN876"
-></A
-><P
-><B
->Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
- Windows</B
-></P
-><P
-> <TT
-CLASS="computeroutput"
-> <B
-CLASS="command"
->install
- <TT
-CLASS="filename"
->C:\AppConfig.ppd</TT
->
- </B
->
- </TT
->
- </P
-></DIV
->
- </P
-></LI
-><LI
-><P
->Install MySQL for NT.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can download MySQL for Windows NT from
- <A
-HREF="http://www.mysql.com/"
-TARGET="_top"
->MySQL.com</A
->
-
- . Some find it helpful to use the WinMySqlAdmin utility, included
- with the download, to set up the database.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
->Setup MySQL</P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->C:\mysql\bin\mysql -u root mysql</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->DELETE FROM user WHERE Host='localhost' AND
- User='';</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';</B
->
- </TT
->
- </P
-><P
-> <SPAN
-CLASS="QUOTE"
->"new_password"</SPAN
->
-
- , above, indicates whatever password you wish to use for your
- <SPAN
-CLASS="QUOTE"
->"root"</SPAN
->
-
- user.</P
-></LI
-><LI
-><A
-NAME="ntbugs-password"
-></A
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->GRANT SELECT, INSERT, UPDATE, DELETE, INDEX,
- ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
->
- </TT
->
- </P
-><P
-> <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- , above, indicates whatever password you wish to use for your
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- user.</P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->create database bugs;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->exit;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->C:\mysql\bin\mysqladmin -u root -p
- reload</B
->
- </TT
->
- </P
-></LI
-></OL
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- in your Bugzilla directory. Change this line:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- getgrnam($my_webservergroup);</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->to</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- $my_webservergroup;</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- or the name of the group you wish to own the files explicitly:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- 'Administrators'</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></LI
-><LI
-><P
->Run
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- from the Bugzilla directory.</P
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->localconfig</TT
->
-
- to suit your requirements. Set
- <TT
-CLASS="varname"
->$db_pass</TT
->
-
- to your
- <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- from
- <A
-HREF="#ntbugs-password"
->step 5.d</A
->
-
- , and
- <TT
-CLASS="varname"
->$webservergroup</TT
->
-
- to
- <SPAN
-CLASS="QUOTE"
->"8"</SPAN
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Not sure on the
- <SPAN
-CLASS="QUOTE"
->"8"</SPAN
->
-
- for
- <TT
-CLASS="varname"
->$webservergroup</TT
->
-
- above. If it's wrong, please send corrections.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->defparams.pl</TT
->
-
- to suit your requirements. Particularly, set
- <TT
-CLASS="varname"
->DefParam("maintainer")</TT
->
-
- and
- <TT
-CLASS="varname"
->DefParam("urlbase") to match your install.</TT
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This is yet another step I'm not sure of, since the
- maintainer of this documentation does not maintain Bugzilla on
- NT. If you can confirm or deny that this step is required, please
- let me know.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are several alternatives to Sendmail that will work
- on Win32. The one mentioned here is a
- <EM
->suggestion</EM
->
-
- , not a requirement. Some other mail packages that can work
- include
- <A
-HREF="http://www.blat.net/"
-TARGET="_top"
->BLAT</A
->
-
- ,
- <A
-HREF="http://www.geocel.com/windmail/"
-TARGET="_top"
->Windmail</A
->
-
- ,
- <A
-HREF="http://www.dynamicstate.com/"
-TARGET="_top"
->Mercury
- Sendmail</A
->
-
- , and the CPAN Net::SMTP Perl module (available in .ppm). Every
- option requires some hacking of the Perl scripts for Bugzilla to
- make it work. The option here simply requires the least.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->Download NTsendmail, available from
- <A
-HREF="http://www.ntsendmail.com/"
-TARGET="_top"
-> www.ntsendmail.com</A
->
-
- . You must have a "real" mail server which allows you to relay
- off it in your $ENV{"NTsendmail"} (which you should probably
- place in globals.pl)</P
-></LI
-><LI
-><P
->Put ntsendmail.pm into your .\perl\lib directory.</P
-></LI
-><LI
-><P
->Add to globals.pl:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-># these settings configure the NTsendmail
- process use NTsendmail;
- $ENV{"NTsendmail"}="your.smtpserver.box";
- $ENV{"NTsendmail_debug"}=1;
- $ENV{"NTsendmail_max_tries"}=5;</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some mention to also edit
- <TT
-CLASS="varname"
->$db_pass</TT
->
-
- in
- <TT
-CLASS="filename"
->globals.pl</TT
->
-
- to be your
- <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- . Although this may get you around some problem
- authenticating to your database, since globals.pl is not
- normally restricted by
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- , your database password is exposed to whoever uses your web
- server.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Find and comment out all occurences of
- <SPAN
-CLASS="QUOTE"
->"
- <B
-CLASS="command"
->open(SENDMAIL</B
->
- "</SPAN
->
-
- in your Bugzilla directory. Then replace them with:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-># new sendmail functionality my $mail=new
- NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
- $to=$login; my $subject=$urlbase;
- $mail->send($from,$to,$subject,$msg);</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some have found success using the commercial product,
- <SPAN
-CLASS="productname"
->Windmail</SPAN
->
-
- . You could try replacing your sendmail calls with:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->open SENDMAIL,
- "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
- mail.log";</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- or something to that effect.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-></LI
-><LI
-><P
->Change all references in all files from
- <TT
-CLASS="filename"
->processmail</TT
->
-
- to
- <TT
-CLASS="filename"
->processmail.pl</TT
->
-
- , and rename
- <TT
-CLASS="filename"
->processmail</TT
->
-
- to
- <TT
-CLASS="filename"
->processmail.pl</TT
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Many think this may be a change we want to make for
- main-tree Bugzilla. It's painless for the UNIX folks, and will
- make the Win32 people happier.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some people have suggested using the Net::SMTP Perl module
- instead of NTsendmail or the other options listed here. You can
- change processmail.pl to make this work.
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-
-my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
-$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
-$smtp->to($tolist); # recipient's address
-$smtp->data(); # Start the mail
-$smtp->datasend($msg);
-$smtp->dataend(); # Finish sending the mail
-$smtp->quit; # Close the SMTP connection
-$logstr = "$logstr; mail sent to $tolist $cclist";
-}
-
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- here is a test mail program for Net::SMTP:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-
-use Net::SMTP;
- my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
-=> 1, ); # connect to SMTP server
- $smtp->auth;
- $smtp->mail('you@yourcompany.com');# use the sender's adress
-here
- $smtp->to('someotherAddress@someotherdomain.com'); #
-recipient's address
- $smtp->data(); # Start the mail
- $smtp->datasend('test');
- $smtp->dataend(); # Finish sending the mail
- $smtp->quit; # Close the SMTP connection
-exit;
-
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This step is optional if you are using IIS or another web
- server which only decides on an interpreter based upon the file
- extension (.pl), rather than the
- <SPAN
-CLASS="QUOTE"
->"shebang"</SPAN
->
-
- line (#/usr/bonsaitools/bin/perl)</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Modify the path to perl on the first line (#!) of all files
- to point to your Perl installation, and add
- <SPAN
-CLASS="QUOTE"
->"perl"</SPAN
->
-
- to the beginning of all Perl system calls that use a perl script as
- an argument. This may take you a while. There is a
- <SPAN
-CLASS="QUOTE"
->"setperl.csh"</SPAN
->
-
- utility to speed part of this procedure, available in the
- <A
-HREF="#patches"
->Useful Patches and Utilities for Bugzilla</A
->
-
- section of The Bugzilla Guide. However, it requires the Cygwin
- GNU-compatible environment for Win32 be set up in order to work.
- See
- <A
-HREF="http://www.cygwin.com/"
-TARGET="_top"
->http://www.cygwin.com/</A
->
-
- for details on obtaining Cygwin.</P
-></LI
-><LI
-><P
->Modify the invocation of all system() calls in all perl
- scripts in your Bugzilla directory. You should specify the full
- path to perl for each system() call. For instance, change this line
- in processmail:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-system ("./processmail",@ARGLIST);
- </programlisting> to
- <programlisting>
-system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></LI
-><LI
-><P
->Add
- <TT
-CLASS="function"
->binmode()</TT
->
-
- calls so attachments will work (
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
-TARGET="_top"
->bug
- 62000</A
->
-
- ).</P
-><P
->Because Microsoft Windows based systems handle binary files
- different than Unix based systems, you need to add the following
- lines to
- <TT
-CLASS="filename"
->createattachment.cgi</TT
->
-
- and
- <TT
-CLASS="filename"
->showattachment.cgi</TT
->
-
- before the
- <TT
-CLASS="function"
->require 'CGI.pl';</TT
->
-
- line.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-binmode(STDIN);
-binmode(STDOUT);
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->According to
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
-TARGET="_top"
-> bug 62000</A
->
-
- , the perl documentation says that you should always use
- <TT
-CLASS="function"
->binmode()</TT
->
-
- when dealing with binary files, but never when dealing with text
- files. That seems to suggest that rather than arbitrarily putting
-
- <TT
-CLASS="function"
->binmode()</TT
->
-
- at the beginning of the attachment files, there should be logic
- to determine if
- <TT
-CLASS="function"
->binmode()</TT
->
-
- is needed or not.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using IIS or Personal Web Server, you must add cgi
- relationships to Properties -> Home directory (tab) ->
- Application Settings (section) -> Configuration (button), such
- as:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->.cgi to: <perl install directory>\perl.exe %s
- %s .pl to: <perl install directory>\perl.exe %s %s
- GET,HEAD,POST</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- Change the path to Perl to match your install, of course.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="addlwintips"
-></A
->4.3.2. Additional Windows Tips</H2
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->From Andrew Pearson:
- <A
-NAME="AEN1046"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
- <A
-HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
-TARGET="_top"
-> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
->
- </P
-><P
->Basically you need to add two String Keys in the registry at
- the following location:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->The keys should be called ".pl" and ".cgi", and both should
- have a value something like:
- <B
-CLASS="command"
->c:/perl/bin/perl.exe "%s" "%s"</B
->
- </P
-><P
->The KB article only talks about .pl, but it goes into more
- detail and provides a perl test script.</P
-></BLOCKQUOTE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If attempting to run Bugzilla 2.12 or older, you will need to
- remove encrypt() calls from the Perl source. This is
- <EM
->not necessary</EM
->
-
- for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla 2.16.4.
- <DIV
-CLASS="example"
-><A
-NAME="AEN1058"
-></A
-><P
-><B
->Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier</B
-></P
-><P
->Replace this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
- ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
- $enteredcryptpwd = FetchOneColumn();</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- with this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $enteredcryptpwd = $enteredpwd</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- in cgi.pl.</P
-></DIV
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="osx"
-></A
->4.4. Mac OS X Installation Notes</H1
-><P
->There are a lot of common libraries and utilities out there that
- Apple did not include with Mac OS X, but which run perfectly well on it.
- The GD library, which Bugzilla needs to do bug graphs, is one of
- these.</P
-><P
->The easiest way to get a lot of these is with a program called
- Fink, which is similar in nature to the CPAN installer, but installs
- common GNU utilities. Fink is available from
- <http://sourceforge.net/projects/fink/>.</P
-><P
->Follow the instructions for setting up Fink. Once it's installed,
- you'll want to run the following as root:
- <B
-CLASS="command"
->fink install gd</B
->
- </P
-><P
->It will prompt you for a number of dependencies, type 'y' and hit
- enter to install all of the dependencies. Then watch it work.</P
-><P
->To prevent creating conflicts with the software that Apple installs
- by default, Fink creates its own directory tree at /sw where it installs
- most of the software that it installs. This means your libraries and
- headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
- and /usr/local/include. Because of these changed locations for the
- libraries, the Perl GD module will not install directly via CPAN, because it
- looks for the specific paths instead of getting them from your
- environment. But there's a way around that :-)</P
-><P
->Instead of typing
- <SPAN
-CLASS="QUOTE"
->"install GD"</SPAN
->
- at the
- <TT
-CLASS="prompt"
->cpan></TT
->
- prompt, type
- <B
-CLASS="command"
->look GD</B
->.
- This should go through the motions of downloading the latest version of
- the GD module, then it will open a shell and drop you into the build
- directory. Apply <A
-HREF="../xml/gd-makefile.patch"
-TARGET="_top"
->this patch</A
->
- to the Makefile.PL file (save the
- patch into a file and use the command
- <B
-CLASS="command"
->patch < patchfile</B
->.)
- </P
-><P
->Then, run these commands to finish the installation of the GD
- module:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <B
-CLASS="command"
->perl Makefile.PL</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make test</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make install</B
->
- </TD
-></TR
-><TR
-><TD
->And don't forget to run
- <B
-CLASS="command"
->exit</B
->
-
- to get back to CPAN.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="troubleshooting"
-></A
->4.5. Troubleshooting</H1
-><P
->This section gives solutions to common Bugzilla installation
- problems.
- </P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1092"
-></A
->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
-><P
-> Try executing <B
-CLASS="command"
->perl -MCPAN -e 'install CPAN'</B
->
- and then continuing.
- </P
-><P
-> Certain older versions of the CPAN toolset were somewhat naive about how
- to upgrade Perl modules. When a couple of modules got rolled into the core
- Perl distribution for 5.6.1, CPAN thought that the best way to get those
- modules up to date was to haul down the Perl distribution itself and
- build it. Needless to say, this has caused headaches for just about
- everybody. Upgrading to a newer version of CPAN with the
- commandline above should fix things.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1097"
-></A
->4.5.2. DBD::Sponge::db prepare failed</H2
-><P
-> The following error message may appear due to a bug in DBD::mysql
- (over which the Bugzilla team have no control):
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site/lib/DBD/mysql.pm line 248.
- SV = NULL(0x0) at 0x20fc444
- REFCNT = 1
- FLAGS = (PADBUSY,PADMY)
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> To fix this, go to
- <TT
-CLASS="filename"
-><path-to-perl>/lib/DBD/sponge.pm</TT
->
- in your Perl installation and replace
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAME'}) {
- $numFields = @{$attribs->{NAME}};
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> by
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAMES'}) {
- $numFields = @{$attribs->{NAMES}};
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> (note the S added to NAME.)
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="paranoid-security"
-></A
->4.5.3. cannot chdir(/var/spool/mqueue)</H2
-><P
->If you are installing Bugzilla on SuSE Linux, or some other
- distributions with
- <SPAN
-CLASS="QUOTE"
->"paranoid"</SPAN
->
- security options, it is possible that the checksetup.pl script may fail
- with the error:
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->cannot chdir(/var/spool/mqueue): Permission denied
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> This is because your
- <TT
-CLASS="filename"
->/var/spool/mqueue</TT
->
- directory has a mode of
- <SPAN
-CLASS="QUOTE"
->"drwx------"</SPAN
->. Type
- <B
-CLASS="command"
->chmod 755
- <TT
-CLASS="filename"
->/var/spool/mqueue</TT
->
- </B
->
- as root to fix this problem.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="trouble-filetemp"
-></A
->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
-><P
->This is caused by a bug in the version of
- <SPAN
-CLASS="productname"
->File::Temp</SPAN
-> that is distributed with perl
- 5.6.0. Many minor variations of this error have been reported. Examples
- can be found in <A
-HREF="#trouble-filetemp-errors"
->Figure 4-1</A
->.
- </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-errors"
-></A
-><P
-><B
->Figure 4-1. Other File::Temp error messages</B
-></P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> Your vendor has not defined Fcntl macro O_NOINHERIT, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
-
-Your vendor has not defined Fcntl macro O_EXLOCK, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
-
-Your vendor has not defined Fcntl macro O_TEMPORARY, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Numerous people have reported that upgrading to version 5.6.1
- or higher solved the problem for them. A less involved fix is to apply
- the patch in <A
-HREF="#trouble-filetemp-patch"
->Figure 4-2</A
->. The patch is also
- available as a <A
-HREF="../xml/filetemp.patch"
-TARGET="_top"
->patch file</A
->.
- </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-patch"
-></A
-><P
-><B
->Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
-></P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
-+++ File/Temp.pm Thu Feb 6 16:26:23 2003
-@@ -205,6 +205,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
-+ local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
-@@ -226,6 +227,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
-+ local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="administration"
-></A
->Chapter 5. Administering Bugzilla</H1
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="parameters"
-></A
->5.1. Bugzilla Configuration</H1
-><P
->Bugzilla is configured by changing various parameters, accessed
- from the "Edit parameters" link in the page footer. Here are
- some of the key parameters on that page. You should run down this
- list and set them appropriately after installing Bugzilla.</P
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->
- <B
-CLASS="command"
->maintainer</B
->:
- The maintainer parameter is the email address of the person
- responsible for maintaining this
- Bugzilla installation. The address need not be that of a valid Bugzilla
- account.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->urlbase</B
->:
- This parameter defines the fully qualified domain name and web
- server path to your Bugzilla installation.</P
-><P
->For example, if your Bugzilla query page is
- <TT
-CLASS="filename"
->http://www.foo.com/bugzilla/query.cgi</TT
->,
- set your <SPAN
-CLASS="QUOTE"
->"urlbase"</SPAN
->
- to <TT
-CLASS="filename"
->http://www.foo.com/bugzilla/</TT
->.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usebuggroups</B
->:
- This dictates whether or not to implement group-based security for
- Bugzilla. If set, Bugzilla bugs can have an associated 'group',
- defining which users are allowed to see and edit the
- bug.</P
-><P
->Set "usebuggroups" to "on"
- <EM
->only</EM
->
- if you may wish to restrict access to particular bugs to certain
- groups of users. I suggest leaving
- this parameter <EM
->off</EM
->
- while initially testing your Bugzilla.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usebuggroupsentry</B
->:
- Bugzilla Products can have a group associated with them, so that
- certain users can only see bugs in certain products. When this parameter
- is set to <SPAN
-CLASS="QUOTE"
->"on"</SPAN
->, this places all newly-created bugs in the
- group for their product immediately.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->shadowdb</B
->:
- You run into an interesting problem when Bugzilla reaches a
- high level of continuous activity. MySQL supports only table-level
- write locking. What this means is that if someone needs to make a
- change to a bug, they will lock the entire table until the operation
- is complete. Locking for write also blocks reads until the write is
- complete. The
- <SPAN
-CLASS="QUOTE"
->"shadowdb"</SPAN
->
- parameter was designed to get around this limitation. While only a
- single user is allowed to write to a table at a time, reads can
- continue unimpeded on a read-only shadow copy of the database.
- Although your database size will double, a shadow database can cause
- an enormous performance improvement when implemented on extremely
- high-traffic Bugzilla databases.</P
-><P
-> As a guide, mozilla.org began needing
- <SPAN
-CLASS="QUOTE"
->"shadowdb"</SPAN
->
- when they reached around 40,000 Bugzilla users with several hundred
- Bugzilla bug changes and comments per day.</P
-><P
->The value of the parameter defines the name of the
- shadow bug database.
- Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a
- *very* large installation of Bugzilla.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Enabling "shadowdb" can adversely affect the stability of
- your installation of Bugzilla. You should regularly check that your
- database is in sync. It is often advisable to force a shadow
- database sync nightly via
- <SPAN
-CLASS="QUOTE"
->"cron"</SPAN
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->If you use the "shadowdb" option, it is only natural that you
- should turn the "queryagainstshadowdb" option on as well. Otherwise
- you are replicating data into a shadow database for no reason!</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->shutdownhtml</B
->:
-
- If you need to shut down Bugzilla to perform administration, enter
- some descriptive HTML here and anyone who tries to use Bugzilla will
- receive a page to that effect. Obviously, editparams.cgi will
- still be accessible so you can remove the HTML and re-enable Bugzilla.
- :-)
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->passwordmail</B
->:
-
- Every time a user creates an account, the text of
- this parameter (with substitutions) is sent to the new user along with
- their password message.</P
-><P
->Add any text you wish to the "passwordmail" parameter box. For
- instance, many people choose to use this box to give a quick training
- blurb about how to use Bugzilla at your site.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->useqacontact</B
->:
-
- This allows you to define an email address for each component, in
- addition
- to that of the default owner, who will be sent carbon copies of
- incoming bugs.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usestatuswhiteboard</B
->:
- This defines whether you wish to have a free-form, overwritable field
- associated with each bug. The advantage of the Status Whiteboard is
- that it can be deleted or modified with ease, and provides an
- easily-searchable field for indexing some bugs that have some trait
- in common.
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->whinedays</B
->:
- Set this to the number of days you want to let bugs go
- in the NEW or REOPENED state before notifying people they have
- untouched new bugs. If you do not plan to use this feature, simply do
- not set up the whining cron job described in the installation
- instructions, or set this value to "0" (never whine).</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->commenton*</B
->:
- All these
- fields allow you to dictate what changes can pass without comment,
- and which must have a comment from the person who changed them.
- Often, administrators will allow users to add themselves to the CC
- list, accept bugs, or change the Status Whiteboard without adding a
- comment as to their reasons for the change, yet require that most
- other changes come with an explanation.</P
-><P
->Set the "commenton" options according to your site policy. It
- is a wise idea to require comments when users resolve, reassign, or
- reopen bugs at the very least.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is generally far better to require a developer comment
- when resolving bugs than not. Few things are more annoying to bug
- database users than having a developer mark a bug "fixed" without
- any comment as to what the fix was (or even that it was truly
- fixed!)</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->supportwatchers</B
->:
-
- Turning on this option allows users to ask to receive copies of
- all a particular other user's bug email. This is, of
- course, subject to the groupset restrictions on the bug; if the
- <SPAN
-CLASS="QUOTE"
->"watcher"</SPAN
->
- would not normally be allowed to view a bug, the watcher cannot get
- around the system by setting herself up to watch the bugs of someone
- with bugs outside her privileges. They would still only receive email
- updates for those bugs she could normally view.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="useradmin"
-></A
->5.2. User Administration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="defaultuser"
-></A
->5.2.1. Creating the Default User</H2
-><P
->When you first run checksetup.pl after installing Bugzilla, it
- will prompt you for the administrative username (email address) and
- password for this "super user". If for some reason you delete
- the "super user" account, re-running checksetup.pl will again prompt
- you for this username and password.</P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you wish to add more administrative users, you must use the
- MySQL interface. Run "mysql" from the command line, and use these
- commands:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="prompt"
->mysql></TT
->
- <B
-CLASS="command"
->use bugs;</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
-> update profiles set groupset=0x7ffffffffffffff where login_name =
- "(user's login name)";
- </B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->Yes, that is
- <EM
->fourteen</EM
->
-
- <SPAN
-CLASS="QUOTE"
->"f"</SPAN
->
-
- 's. A whole lot of f-ing going on if you want to create a new
- administator.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="manageusers"
-></A
->5.2.2. Managing Other Users</H2
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="createnewusers"
-></A
->5.2.2.1. Creating new users</H3
-><P
->Your users can create their own user accounts by clicking the
- "New Account" link at the bottom of each page (assuming they
- aren't logged in as someone else already.) However, should you
- desire to create user accounts ahead of time, here is how you do
- it.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->After logging in, click the "Users" link at the footer of
- the query page, and then click "Add a new user".</P
-></LI
-><LI
-><P
->Fill out the form presented. This page is self-explanatory.
- When done, click "Submit".</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Adding a user this way will
- <EM
->not</EM
->
-
- send an email informing them of their username and password.
- While useful for creating dummy accounts (watchers which
- shuttle mail to another system, for instance, or email
- addresses which are a mailing list), in general it is
- preferable to log out and use the
- <SPAN
-CLASS="QUOTE"
->"New Account"</SPAN
->
-
- button to create users, as it will pre-populate all the
- required fields and also notify the user of her account name
- and password.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="modifyusers"
-></A
->5.2.2.2. Modifying Users</H3
-><P
->To see a specific user, search for their login name
- in the box provided on the "Edit Users" page. To see all users,
- leave the box blank.</P
-><P
->You can search in different ways the listbox to the right
- of the text entry box. You can match by
- case-insensitive substring (the default),
- regular expression, or a
- <EM
->reverse</EM
->
- regular expression match, which finds every user name which does NOT
- match the regular expression. (Please see
- the <B
-CLASS="command"
->man regexp</B
->
- manual page for details on regular expression syntax.)
- </P
-><P
->Once you have found your user, you can change the following
- fields:</P
-><P
-></P
-><UL
-><LI
-><P
-> <EM
->Login Name</EM
->:
- This is generally the user's full email address. However, if you
- have are using the emailsuffix Param, this may just be the user's
- login name. Note that users can now change their login names
- themselves (to any valid email address.)
- </P
-></LI
-><LI
-><P
-> <EM
->Real Name</EM
->: The user's real name. Note that
- Bugzilla does not require this to create an account.</P
-></LI
-><LI
-><P
-> <EM
->Password</EM
->:
- You can change the user's password here. Users can automatically
- request a new password, so you shouldn't need to do this often.
- If you want to disable an account, see Disable Text below.
- </P
-></LI
-><LI
-><P
-> <EM
->Disable Text</EM
->:
- If you type anything in this box, including just a space, the
- user is prevented from logging in, or making any changes to
- bugs via the web interface.
- The HTML you type in this box is presented to the user when
- they attempt to perform these actions, and should explain
- why the account was disabled.
- <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't disable the administrator account!</P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The user can still submit bugs via
- the e-mail gateway, if you set it up, even if the disabled text
- field is filled in. The e-mail gateway should
- <EM
->not</EM
->
- be enabled for secure installations of Bugzilla.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> <EM
-><groupname></EM
->:
- If you have created some groups, e.g. "securitysensitive", then
- checkboxes will appear here to allow you to add users to, or
- remove them from, these groups.
- </P
-></LI
-><LI
-><P
-> <EM
->canconfirm</EM
->:
- This field is only used if you have enabled the "unconfirmed"
- status. If you enable this for a user,
- that user can then move bugs from "Unconfirmed" to a "Confirmed"
- status (e.g.: "New" status).</P
-></LI
-><LI
-><P
-> <EM
->creategroups</EM
->:
- This option will allow a user to create and destroy groups in
- Bugzilla.</P
-></LI
-><LI
-><P
-> <EM
->editbugs</EM
->:
- Unless a user has this bit set, they can only edit those bugs
- for which they are the assignee or the reporter. Even if this
- option is unchecked, users can still add comments to bugs.
- </P
-></LI
-><LI
-><P
-> <EM
->editcomponents</EM
->:
- This flag allows a user to create new products and components,
- as well as modify and destroy those that have no bugs associated
- with them. If a product or component has bugs associated with it,
- those bugs must be moved to a different product or component
- before Bugzilla will allow them to be destroyed.
- </P
-></LI
-><LI
-><P
-> <EM
->editkeywords</EM
->:
- If you use Bugzilla's keyword functionality, enabling this
- feature allows a user to create and destroy keywords. As always,
- the keywords for existing bugs containing the keyword the user
- wishes to destroy must be changed before Bugzilla will allow it
- to die.</P
-></LI
-><LI
-><P
-> <EM
->editusers</EM
->:
- This flag allows a user to do what you're doing right now: edit
- other users. This will allow those with the right to do so to
- remove administrator privileges from other users or grant them to
- themselves. Enable with care.</P
-></LI
-><LI
-><P
-> <EM
->tweakparams</EM
->:
- This flag allows a user to change Bugzilla's Params
- (using <TT
-CLASS="filename"
->editparams.cgi</TT
->.)</P
-></LI
-><LI
-><P
-> <EM
-><productname></EM
->:
- This allows an administrator to specify the products in which
- a user can see bugs. The user must still have the
- "editbugs" privilege to edit bugs in these products.</P
-></LI
-></UL
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="programadmin"
-></A
->5.3. Product, Component, Milestone, and Version Administration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="products"
-></A
->5.3.1. Products</H2
-><P
-> <A
-HREF="#gloss-product"
-><I
-CLASS="glossterm"
-> Products</I
-></A
->
-
- are the broadest category in Bugzilla, and tend to represent real-world
- shipping products. E.g. if your company makes computer games,
- you should have one product per game, perhaps a "Common" product for
- units of technology used in multiple games, and maybe a few special
- products (Website, Administration...)</P
-><P
->Many of Bugzilla's settings are configurable on a per-product
- basis. The number of "votes" available to users is set per-product,
- as is the number of votes
- required to move a bug automatically from the UNCONFIRMED status to the
- NEW status.</P
-><P
->To create a new product:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "products" from the footer</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right</P
-></LI
-><LI
-><P
->Enter the name of the product and a description. The
- Description field may contain HTML.</P
-></LI
-></OL
-><P
->Don't worry about the "Closed for bug entry", "Maximum Votes
- per person", "Maximum votes a person can put on a single bug",
- "Number of votes a bug in this Product needs to automatically get out
- of the UNCOMFIRMED state", and "Version" options yet. We'll cover
- those in a few moments.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="components"
-></A
->5.3.2. Components</H2
-><P
->Components are subsections of a Product. E.g. the computer game
- you are designing may have a "UI"
- component, an "API" component, a "Sound System" component, and a
- "Plugins" component, each overseen by a different programmer. It
- often makes sense to divide Components in Bugzilla according to the
- natural divisions of responsibility within your Product or
- company.</P
-><P
-> Each component has a owner and (if you turned it on in the parameters),
- a QA Contact. The owner should be the primary person who fixes bugs in
- that component. The QA Contact should be the person who will ensure
- these bugs are completely fixed. The Owner, QA Contact, and Reporter
- will get email when new bugs are created in this Component and when
- these bugs change. Default Owner and Default QA Contact fields only
- dictate the
- <EM
->default assignments</EM
->;
- these can be changed on bug submission, or at any later point in
- a bug's life.</P
-><P
->To create a new Component:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select the "Edit components" link from the "Edit product"
- page</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Fill out the "Component" field, a short "Description",
- the "Initial Owner" and "Initial QA Contact" (if enabled.)
- The Component and Description fields may contain HTML;
- the "Initial Owner" field must be a login name
- already existing in the database.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="versions"
-></A
->5.3.3. Versions</H2
-><P
->Versions are the revisions of the product, such as "Flinders
- 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
- field; the usual practice is to select the most recent version with
- the bug.
- </P
-><P
->To create and edit Versions:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->From the "Edit product" screen, select "Edit Versions"</P
-></LI
-><LI
-><P
->You will notice that the product already has the default
- version "undefined". Click the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Enter the name of the Version. This field takes text only.
- Then click the "Add" button.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="milestones"
-></A
->5.3.4. Milestones</H2
-><P
->Milestones are "targets" that you plan to get a bug fixed by. For
- example, you have a bug that you plan to fix for your 3.0 release, it
- would be assigned the milestone of 3.0.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Milestone options will only appear for a Product if you turned
- on the "usetargetmilestone" Param in the "Edit Parameters" screen.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->To create new Milestones, set Default Milestones, and set
- Milestone URL:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "Edit milestones" from the "Edit product" page.</P
-></LI
-><LI
-><P
->Select "Add" in the bottom right corner.
- text</P
-></LI
-><LI
-><P
->Enter the name of the Milestone in the "Milestone" field. You
- can optionally set the "sortkey", which is a positive or negative
- number (-255 to 255) that defines where in the list this particular
- milestone appears. This is because milestones often do not
- occur in alphanumeric order For example, "Future" might be
- after "Release 1.2". Select "Add".</P
-></LI
-><LI
-><P
->From the Edit product screen, you can enter the URL of a
- page which gives information about your milestones and what
- they mean. </P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you want your milestone document to be restricted so
- that it can only be viewed by people in a particular Bugzilla
- group, the best way is to attach the document to a bug in that
- group, and make the URL the URL of that attachment.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="voting"
-></A
->5.4. Voting</H1
-><P
->Voting allows users to be given a pot of votes which they can allocate
- to bugs, to indicate that they'd like them fixed.
- This allows developers to gauge
- user need for a particular enhancement or bugfix. By allowing bugs with
- a certain number of votes to automatically move from "UNCONFIRMED" to
- "NEW", users of the bug system can help high-priority bugs garner
- attention so they don't sit for a long time awaiting triage.</P
-><P
->To modify Voting settings:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Navigate to the "Edit product" screen for the Product you
- wish to modify</P
-></LI
-><LI
-><P
-><EM
->Maximum Votes per person</EM
->:
- Setting this field to "0" disables voting.</P
-></LI
-><LI
-><P
-><EM
->Maximum Votes a person can put on a single
- bug"</EM
->:
- It should probably be some number lower than the
- "Maximum votes per person". Don't set this field to "0" if
- "Maximum votes per person" is non-zero; that doesn't make
- any sense.</P
-></LI
-><LI
-><P
-><EM
->Number of votes a bug in this product needs to
- automatically get out of the UNCONFIRMED state</EM
->:
- Setting this field to "0" disables the automatic move of
- bugs from UNCONFIRMED to NEW.
- </P
-></LI
-><LI
-><P
->Once you have adjusted the values to your preference, click
- "Update".</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="groups"
-></A
->5.5. Groups and Group Security</H1
-><P
->Groups allow the administrator
- to isolate bugs or products that should only be seen by certain people.
- There are two types of group - Generic Groups, and Product-Based Groups.
- </P
-><P
-> Product-Based Groups are matched with products, and allow you to restrict
- access to bugs on a per-product basis. They are enabled using the
- usebuggroups Param. Turning on the usebuggroupsentry
- Param will mean bugs automatically get added to their product group when
- filed.
- </P
-><P
-> Generic Groups have no special relationship to products;
- you create them, and put bugs in them
- as required. One example of the use of Generic Groups
- is Mozilla's "Security" group,
- into which security-sensitive bugs are placed until fixed. Only the
- Mozilla Security Team are members of this group.
- </P
-><P
->To create Generic Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select the "groups"
- link in the footer.</P
-></LI
-><LI
-><P
->Take a moment to understand the instructions on the "Edit
- Groups" screen, then select the "Add Group" link.</P
-></LI
-><LI
-><P
->Fill out the "New Name", "New Description", and
- "New User RegExp" fields. "New User RegExp" allows you to automatically
- place all users who fulfill the Regular Expression into the new group.
- When you have finished, click "Add".</P
-></LI
-></OL
-><P
->To use Product-Based Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen.</P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->XXX is this still true?
- "usebuggroupsentry" has the capacity to prevent the
- administrative user from directly altering bugs because of
- conflicting group permissions. If you plan on using
- "usebuggroupsentry", you should plan on restricting
- administrative account usage to administrative duties only. In
- other words, manage bugs with an unpriveleged user account, and
- manage users, groups, Products, etc. with the administrative
- account.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->In future, when you create a Product, a matching group will be
- automatically created. If you need to add a Product Group to
- a Product which was created before you turned on usebuggroups,
- then simply create a new group, as outlined above, with the
- same name as the Product.</P
-></LI
-></OL
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Bugzilla currently has a limit of 64 groups per installation. If
- you have more than about 50 products, you should consider
- running multiple Bugzillas. Ask in the newsgroup for other
- suggestions for working around this restriction.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
-> Note that group permissions are such that you need to be a member
- of <EM
->all</EM
-> the groups a bug is in, for whatever
- reason, to see that bug.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="security"
-></A
->5.6. Bugzilla Security</H1
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Poorly-configured MySQL and Bugzilla installations have
- given attackers full access to systems in the past. Please take these
- guidelines seriously, even for Bugzilla machines hidden away behind
- your firewall. 80% of all computer trespassers are insiders, not
- anonymous crackers.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->These instructions must, of necessity, be somewhat vague since
- Bugzilla runs on so many different platforms. If you have refinements
- of these directions, please submit a bug to <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->Bugzilla</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This is not meant to be a comprehensive list of every possible
- security issue regarding the tools mentioned in this section. There is
- no subsitute for reading the information written by the authors of any
- software running on your system.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="security-networking"
-></A
->5.6.1. TCP/IP Ports</H2
-><P
->TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
- only needs 1... 2 if you need to use features that require e-mail such
- as bug moving or the e-mail interface from contrib. You should audit
- your server and make sure that you aren't listening on any ports you
- don't need to be. You may also wish to use some kind of firewall
- software to be sure that trafic can only be recieved on ports you
- specify.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="security-mysql"
-></A
->5.6.2. MySQL</H2
-><P
->MySQL ships by default with many settings that should be changed.
- By defaults it allows anybody to connect from localhost without a
- password and have full administrative capabilities. It also defaults to
- not have a root password (this is <EM
->not</EM
-> the same as
- the system root). Also, many installations default to running
- <SPAN
-CLASS="application"
->mysqld</SPAN
-> as the system root.
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Make sure you are running at least version 3.22.32 of MySQL
- as earlier versions had notable security holes.
- </P
-></LI
-><LI
-><P
->Consult the documentation that came with your system for
- information on making <SPAN
-CLASS="application"
->mysqld</SPAN
-> run as an
- unprivleged user.
- </P
-></LI
-><LI
-><P
->You should also be sure to disable the anonymous user account
- and set a password for the root user. This is accomplished using the
- following commands:
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <TT
-CLASS="prompt"
->bash$</TT
-> mysql mysql
-<TT
-CLASS="prompt"
->mysql></TT
-> DELETE FROM user WHERE user = '';
-<TT
-CLASS="prompt"
->mysql></TT
-> UPDATE user SET password = password('<TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
->') WHERE user = 'root';
-<TT
-CLASS="prompt"
->mysql></TT
-> FLUSH PRIVILEGES;
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->From this point forward you will need to use
- <B
-CLASS="command"
->mysql -u root -p</B
-> and enter
- <TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
-> when prompted when using the
- mysql client.
- </P
-></LI
-><LI
-><P
->If you run MySQL on the same machine as your httpd server, you
- should consider disabling networking from within MySQL by adding
- the following to your <TT
-CLASS="filename"
->/etc/my.conf</TT
->:
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> [myslqd]
-# Prevent network access to MySQL.
-skip-networking
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->You may also consider running MySQL, or even all of Bugzilla
- in a chroot jail; however, instructions for doing that are beyond
- the scope of this document.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="security-daemon"
-></A
->5.6.3. Daemon Accounts</H2
-><P
->Many daemons, such as Apache's httpd and MySQL's mysqld default to
- running as either <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> or <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->. Running
- as <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> introduces obvious security problems, but the
- problems introduced by running everything as <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> may
- not be so obvious. Basically, if you're running every daemon as
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> and one of them gets comprimised, they all get
- comprimised. For this reason it is recommended that you create a user
- account for each daemon.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will need to set the <TT
-CLASS="varname"
->webservergroup</TT
-> to
- the group you created for your webserver to run as in
- <TT
-CLASS="filename"
->localconfig</TT
->. This will allow
- <B
-CLASS="command"
->./checksetup.pl</B
-> to better adjust the file
- permissions on your Bugzilla install so as to not require making
- anything world-writable.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="security-access"
-></A
->5.6.4. Web Server Access Controls</H2
-><P
->There are many files that are placed in the Bugzilla directory
- area that should not be accessable from the web. Because of the way
- Bugzilla is currently layed out, the list of what should and should
- not be accessible is rather complicated. A new installation method
- is currently in the works which should solve this by allowing files
- that shouldn't be accessible from the web to be placed in directory
- outside the webroot. See
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
-TARGET="_top"
->bug
- 44659</A
-> for more information.
- </P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->In the main Bugzilla directory, you should:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block:
- <TT
-CLASS="filename"
->*.pl</TT
->, <TT
-CLASS="filename"
->*localconfig*</TT
->, <TT
-CLASS="filename"
->runtests.sh</TT
->, <TT
-CLASS="filename"
->processmail</TT
->, <TT
-CLASS="filename"
->syncshadowdb</TT
->
- </P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->localconfig.js</TT
->, <TT
-CLASS="filename"
->localconfig.rdf</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->duplicates.rdf</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data/webdot</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->If you use a remote webdot server:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow
- <TT
-CLASS="filename"
->*.dot</TT
->
- only for the remote webdot server</P
-></LI
-></UL
-></LI
-><LI
-><P
->Otherwise, if you use a local GraphViz:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->*.png</TT
->, <TT
-CLASS="filename"
->*.gif</TT
->, <TT
-CLASS="filename"
->*.jpg</TT
->, <TT
-CLASS="filename"
->*.map</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->And if you don't use any dot:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->Bugzilla</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->template</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Bugzilla ships with the ability to generate
- <TT
-CLASS="filename"
->.htaccess</TT
-> files instructing Apache which files
- should and should not be accessible.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->You should test to make sure that the files mentioned above are
- not accessible from the Internet, especially your
- <TT
-CLASS="filename"
->localconfig</TT
-> file which contains your database
- password. To test, simply point your web browser at the file; for
- example, to test mozilla.org's installation, we'd try to access
- <A
-HREF="http://bugzilla.mozilla.org/localconfig"
-TARGET="_top"
->http://bugzilla.mozilla.org/localconfig</A
->. You should
- get a <SPAN
-CLASS="errorcode"
->403</SPAN
-> <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
- error.
- </P
-><DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Not following the instructions in this section, including
- testing, may result in sensitive information being globally
- accessible.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="cust-templates"
-></A
->5.7. Template Customisation</H1
-><P
-> One of the large changes for 2.16 was the templatisation of the
- entire user-facing UI, using the
- <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template Toolkit</A
->.
- Administrators can now configure the look and feel of Bugzilla without
- having to edit Perl files or face the nightmare of massive merge
- conflicts when they upgrade to a newer version in the future.
- </P
-><P
-> Templatisation also makes localised versions of Bugzilla possible,
- for the first time. In the future, a Bugzilla installation may
- have templates installed for multiple localisations, and select
- which ones to use based on the user's browser language setting.
- </P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1534"
-></A
->5.7.1. What to Edit</H2
-><P
-> There are two different ways of editing of Bugzilla's templates,
- and which you use depends mainly on how you upgrade Bugzilla. The
- template directory structure is that there's a top level directory,
- <TT
-CLASS="filename"
->template</TT
->, which contains a directory for
- each installed localisation. The default English templates are
- therefore in <TT
-CLASS="filename"
->en</TT
->. Underneath that, there
- is the <TT
-CLASS="filename"
->default</TT
-> directory and optionally the
- <TT
-CLASS="filename"
->custom</TT
-> directory. The <TT
-CLASS="filename"
->default</TT
->
- directory contains all the templates shipped with Bugzilla, whereas
- the <TT
-CLASS="filename"
->custom</TT
-> directory does not exist at first and
- must be created if you want to use it.
- </P
-><P
-> The first method of making customisations is to directly edit the
- templates in <TT
-CLASS="filename"
->template/en/default</TT
->. This is
- probably the best method for small changes if you are going to use
- the CVS method of upgrading, because if you then execute a
- <B
-CLASS="command"
->cvs update</B
->, any template fixes will get
- automagically merged into your modified versions.
- </P
-><P
-> If you use this method, your installation will break if CVS conflicts
- occur.
- </P
-><P
-> The other method is to copy the templates into a mirrored directory
- structure under <TT
-CLASS="filename"
->template/en/custom</TT
->. The templates
- in this directory automatically override those in default.
- This is the technique you
- need to use if you use the overwriting method of upgrade, because
- otherwise your changes will be lost. This method is also better if
- you are using the CVS method of upgrading and are going to make major
- changes, because it is guaranteed that the contents of this directory
- will not be touched during an upgrade, and you can then decide whether
- to continue using your own templates, or make the effort to merge your
- changes into the new versions by hand.
- </P
-><P
-> If you use this method, your installation may break if incompatible
- changes are made to the template interface. If such changes are made
- they will be documented in the release notes, provided you are using a
- stable release of Bugzilla. If you use using unstable code, you will
- need to deal with this one yourself, although if possible the changes
- will be mentioned before they occur in the deprecations section of the
- previous stable release's release notes.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Don't directly edit the compiled templates in
- <TT
-CLASS="filename"
->data/template/*</TT
-> - your
- changes will be lost when Template Toolkit recompiles them.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is recommended that you run <B
-CLASS="command"
->./checksetup.pl</B
->
- after any template edits, especially if you've created a new file in
- the <TT
-CLASS="filename"
->custom</TT
-> directory.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1557"
-></A
->5.7.2. How To Edit Templates</H2
-><P
-> The syntax of the Template Toolkit language is beyond the scope of
- this guide. It's reasonably easy to pick up by looking at the current
- templates; or, you can read the manual, available on the
- <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template Toolkit home
- page</A
->. However, you should particularly remember (for security
- reasons) to always HTML filter things which come from the database or
- user input, to prevent cross-site scripting attacks.
- </P
-><P
-> However, one thing you should take particular care about is the need
- to properly HTML filter data that has been passed into the template.
- This means that if the data can possibly contain special HTML characters
- such as <, and the data was not intended to be HTML, they need to be
- converted to entity form, ie &lt;. You use the 'html' filter in the
- Template Toolkit to do this. If you fail to do this, you may open up
- your installation to cross-site scripting attacks.
- </P
-><P
-> Also note that Bugzilla adds a few filters of its own, that are not
- in standard Template Toolkit. In particular, the 'url_quote' filter
- can convert characters that are illegal or have special meaning in URLs,
- such as &, to the encoded form, ie %26. This actually encodes most
- characters (but not the common ones such as letters and numbers and so
- on), including the HTML-special characters, so there's never a need to
- HTML filter afterwards.
- </P
-><P
-> Editing templates is a good way of doing a "poor man's custom fields".
- For example, if you don't use the Status Whiteboard, but want to have
- a free-form text entry box for "Build Identifier", then you can just
- edit the templates to change the field labels. It's still be called
- status_whiteboard internally, but your users don't need to know that.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you are making template changes that you intend on submitting back
- for inclusion in standard Bugzilla, you should read the relevant
- sections of the
- <A
-HREF="http://www.bugzilla.org/developerguide.html"
-TARGET="_top"
->Developers'
- Guide</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1567"
-></A
->5.7.3. Template Formats</H2
-><P
-> Some CGIs have the ability to use more than one template. For
- example, buglist.cgi can output bug lists as RDF or two
- different forms of HTML (complex and simple). (Try this out
- by appending <TT
-CLASS="filename"
->&format=simple</TT
-> to a buglist.cgi
- URL on your Bugzilla installation.) This
- mechanism, called template 'formats', is extensible.
- </P
-><P
-> To see if a CGI supports multiple output formats, grep the
- CGI for "ValidateOutputFormat". If it's not present, adding
- multiple format support isn't too hard - see how it's done in
- other CGIs.
- </P
-><P
-> To make a new format template for a CGI which supports this,
- open a current template for
- that CGI and take note of the INTERFACE comment (if present.) This
- comment defines what variables are passed into this template. If
- there isn't one, I'm afraid you'll have to read the template and
- the code to find out what information you get.
- </P
-><P
-> Write your template in whatever markup or text style is appropriate.
- </P
-><P
-> You now need to decide what content type you want your template
- served as. Open up the <TT
-CLASS="filename"
->localconfig</TT
-> file and find the
- <TT
-CLASS="filename"
->$contenttypes</TT
->
- variable. If your content type is not there, add it. Remember
- the three- or four-letter tag assigned to you content type.
- This tag will be part of the template filename.
- </P
-><P
-> Save the template as <TT
-CLASS="filename"
-><stubname>-<formatname>.<contenttypetag>.tmpl</TT
->.
- Try out the template by calling the CGI as
- <TT
-CLASS="filename"
-><cginame>.cgi?format=<formatname></TT
-> .
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN1580"
-></A
->5.7.4. Particular Templates</H2
-><P
-> There are a few templates you may be particularly interested in
- customising for your installation.
- </P
-><P
-> <B
-CLASS="command"
->index.html.tmpl</B
->:
- This is the Bugzilla front page.
- </P
-><P
-> <B
-CLASS="command"
->global/header.html.tmpl</B
->:
- This defines the header that goes on all Bugzilla pages.
- The header includes the banner, which is what appears to users
- and is probably what you want to edit instead. However the
- header also includes the HTML HEAD section, so you could for
- example add a stylesheet or META tag by editing the header.
- </P
-><P
-> <B
-CLASS="command"
->global/banner.html.tmpl</B
->:
- This contains the "banner", the part of the header that appears
- at the top of all Bugzilla pages. The default banner is reasonably
- barren, so you'll probably want to customise this to give your
- installation a distinctive look and feel. It is recommended you
- preserve the Bugzilla version number in some form so the version
- you are running can be determined, and users know what docs to read.
- </P
-><P
-> <B
-CLASS="command"
->global/footer.html.tmpl</B
->:
- This defines the footer that goes on all Bugzilla pages. Editing
- this is another way to quickly get a distinctive look and feel for
- your Bugzilla installation.
- </P
-><P
-> <B
-CLASS="command"
->bug/create/user-message.html.tmpl</B
->:
- This is a message that appears near the top of the bug reporting page.
- By modifying this, you can tell your users how they should report
- bugs.
- </P
-><P
-> <B
-CLASS="command"
->bug/create/create.html.tmpl</B
-> and
- <B
-CLASS="command"
->bug/create/comment.txt.tmpl</B
->:
- You may wish to get bug submitters to give certain bits of structured
- information, each in a separate input widget, for which there is not a
- field in the database. The bug entry system has been designed in an
- extensible fashion to enable you to define arbitrary fields and widgets,
- and have their values appear formatted in the initial
- Description, rather than in database fields. An example of this
- is the mozilla.org
- <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided"
-TARGET="_top"
->guided
- bug submission form</A
->.
- </P
-><P
-> To make this work, create a custom template for
- <TT
-CLASS="filename"
->enter_bug.cgi</TT
-> (the default template, on which you
- could base it, is <TT
-CLASS="filename"
->create.html.tmpl</TT
->),
- and either call it <TT
-CLASS="filename"
->create.html.tmpl</TT
-> or use a format and
- call it <TT
-CLASS="filename"
->create-<formatname>.html.tmpl</TT
->.
- Put it in the <TT
-CLASS="filename"
->custom/bug/create</TT
->
- directory. In it, add widgets for each piece of information you'd like
- collected - such as a build number, or set of steps to reproduce.
- </P
-><P
-> Then, create a template like
- <TT
-CLASS="filename"
->custom/bug/create/comment.txt.tmpl</TT
->, also named
- after your format if you are using one, which
- references the form fields you have created. When a bug report is
- submitted, the initial comment attached to the bug report will be
- formatted according to the layout of this template.
- </P
-><P
-> For example, if your enter_bug template had a field
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-><input type="text" name="buildid" size="30"></PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- and then your comment.txt.tmpl had
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->BuildID: [% form.buildid %]</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- then
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->BuildID: 20020303</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- would appear in the initial checkin comment.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="upgrading"
-></A
->5.8. Upgrading to New Releases</H1
-><P
->Upgrading Bugzilla is something we all want to do from time to time,
- be it to get new features or pick up the latest security fix. How easy
- it is to update depends on a few factors.
- </P
-><P
-></P
-><UL
-><LI
-><P
->If the new version is a revision or a new point release</P
-></LI
-><LI
-><P
->How many, if any, local changes have been made</P
-></LI
-></UL
-><P
->There are also three different methods to upgrade your installation.
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Using CVS (<A
-HREF="#upgrade-cvs"
->Example 5-1</A
->)</P
-></LI
-><LI
-><P
->Downloading a new tarball (<A
-HREF="#upgrade-tarball"
->Example 5-2</A
->)</P
-></LI
-><LI
-><P
->Applying the relevant patches (<A
-HREF="#upgrade-patches"
->Example 5-3</A
->)</P
-></LI
-></OL
-><P
->Which options are available to you may depend on how large a jump
- you are making and/or your network configuration.
- </P
-><P
->Revisions are normally released to fix security vulnerabilities
- and are distinguished by an increase in the third number. For example,
- when 2.16.2 was released, it was a revision to 2.16.1.
- </P
-><P
->Point releases are normally released when the Bugzilla team feels
- that there has been a significant amount of progress made between the
- last point release and the current time. These are often proceeded by a
- stabilization period and release candidates, however the use of
- development versions or release candidates is beyond the scope of this
- document. Point releases can be distinguished by an increase in the
- second number, or minor version. For example, 2.16.2 is a newer point
- release than 2.14.5.
- </P
-><P
->The examples in this section are written as if you were updating
- to version 2.16.2. The procedures are the same regardless if you are
- updating to a new point release or a new revision. However, the chance
- of running into trouble increases when upgrading to a new point release,
- escpecially if you've made local changes.
- </P
-><P
->These examples also assume that your Bugzilla installation is at
- <TT
-CLASS="filename"
->/var/www/html/bugzilla</TT
->. If that is not the case,
- simply substitute the proper paths where appropriate.
- </P
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-cvs"
-></A
-><P
-><B
->Example 5-1. Upgrading using CVS</B
-></P
-><P
->Every release of Bugzilla, whether it is a revision or a point
- release, is tagged in CVS. Also, every tarball we have distributed
- since version 2.12 has been primed for using CVS. This does, however,
- require that you are able to access cvs-mirror.mozilla.org on port
- 2401.
-
- <DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you can do this, updating using CVS is probably the most
- painless method, especially if you have a lot of local changes.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html/bugzilla</B
->
-bash$ <B
-CLASS="command"
->cvs login</B
->
-Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
-CVS password: <B
-CLASS="command"
->anonymous</B
->
-bash$ <B
-CLASS="command"
->cvs -q update -r BUGZILLA-2_16_2 -dP</B
->
-P checksetup.pl
-P collectstats.pl
-P globals.pl
-P docs/rel_notes.txt
-P template/en/default/list/quips.html.tmpl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If a line in the output from <B
-CLASS="command"
->cvs update</B
->
- begins with a <TT
-CLASS="computeroutput"
->C</TT
-> that represents a
- file with local changes that CVS was unable to properly merge. You
- need to resolve these conflicts manually before Bugzilla (or at
- least the portion using that file) will be usable.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You also need to run <B
-CLASS="command"
->./checksetup.pl</B
->
- before your Bugzilla upgrade will be complete.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-tarball"
-></A
-><P
-><B
->Example 5-2. Upgrading using the tarball</B
-></P
-><P
->If you are unable or unwilling to use CVS, another option that's
- always available is to download the latest tarball. This is the most
- difficult option to use, especially if you have local changes.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html</B
->
-bash$ <B
-CLASS="command"
->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B
->
-<EM
->Output omitted</EM
->
-bash$ <B
-CLASS="command"
->tar xzvf bugzilla-2.16.2.tar.gz</B
->
-bugzilla-2.16.2/
-bugzilla-2.16.2/.cvsignore
-bugzilla-2.16.2/1x1.gif
-<EM
->Output truncated</EM
->
-bash$ <B
-CLASS="command"
->cd bugzilla-2.16.2</B
->
-bash$ <B
-CLASS="command"
->cp ../bugzilla/localconfig* .</B
->
-bash$ <B
-CLASS="command"
->cp -r ../bugzilla/data .</B
->
-bash$ <B
-CLASS="command"
->cd ..</B
->
-bash$ <B
-CLASS="command"
->mv bugzilla bugzilla.old</B
->
-bash$ <B
-CLASS="command"
->mv bugzilla-2.16.2 bugzilla</B
->
-bash$ <B
-CLASS="command"
->cd bugzilla</B
->
-bash$ <B
-CLASS="command"
->./checksetup.pl</B
->
-<EM
->Output omitted</EM
->
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The <B
-CLASS="command"
->cp</B
-> commands both end with periods which
- is a very important detail, it tells the shell that the destination
- directory is the current working directory. Also, the period at the
- beginning of the <B
-CLASS="command"
->./checksetup.pl</B
-> is important and
- can not be omitted.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will now have to reapply any changes you have made to your
- local installation manually.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-patches"
-></A
-><P
-><B
->Example 5-3. Upgrading using patches</B
-></P
-><P
->The Bugzilla team will normally make a patch file available for
- revisions to go from the most recent revision to the new one. You could
- also read the release notes and grab the patches attached to the
- mentioned bug, but it is safer to use the released patch file as
- sometimes patches get changed before they get checked in (for minor
- spelling fixes and the like). It is also theorectically possible to
- scour the fixed bug list and pick and choose which patches to apply
- from a point release, but this is not recommended either as what you'll
- end up with is a hodge podge Bugzilla that isn't really any version.
- This would also make it more difficult to upgrade in the future.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html/bugzilla</B
->
-bash$ <B
-CLASS="command"
->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B
->
-<EM
->Output omitted</EM
->
-bash$ <B
-CLASS="command"
->gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B
->
-bash$ <B
-CLASS="command"
->patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B
->
-patching file checksetup.pl
-patching file collectstats.pl
-patching file globals.pl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you do this, beware that this doesn't change the entires in
- your <TT
-CLASS="filename"
->CVS</TT
-> directory so it may make
- updates using CVS (<A
-HREF="#upgrade-cvs"
->Example 5-1</A
->) more difficult in the
- future.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="integration"
-></A
->5.9. Integrating Bugzilla with Third-Party Tools</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bonsai"
-></A
->5.9.1. Bonsai</H2
-><P
->Bonsai is a web-based tool for managing
- <A
-HREF="#cvs"
->CVS, the Concurrent Versioning System</A
->
-
- . Using Bonsai, administrators can control open/closed status of trees,
- query a fast relational database back-end for change, branch, and comment
- information, and view changes made since the last time the tree was
- closed. Bonsai
- also integrates with
- <A
-HREF="#tinderbox"
->Tinderbox, the Mozilla automated build management system</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="cvs"
-></A
->5.9.2. CVS</H2
-><P
->CVS integration is best accomplished, at this point, using the
- Bugzilla Email Gateway.</P
-><P
->Follow the instructions in this Guide for enabling Bugzilla e-mail
- integration. Ensure that your check-in script sends an email to your
- Bugzilla e-mail gateway with the subject of
- <SPAN
-CLASS="QUOTE"
->"[Bug XXXX]"</SPAN
->,
- and you can have CVS check-in comments append to your Bugzilla bug. If
- you want to have the bug be closed automatically, you'll have to modify
- the <TT
-CLASS="filename"
->contrib/bugzilla_email_append.pl</TT
-> script.
- </P
-><P
->There is also a CVSZilla project, based upon somewhat dated
- Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
- email. Check it out at:
- <A
-HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
-TARGET="_top"
-> http://homepages.kcbbs.gen.nz/~tonyg/</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="scm"
-></A
->5.9.3. Perforce SCM</H2
-><P
->You can find the project page for Bugzilla and Teamtrack Perforce
- integration (p4dti) at:
- <A
-HREF="http://www.ravenbrook.com/project/p4dti/"
-TARGET="_top"
-> http://www.ravenbrook.com/project/p4dti</A
->
-
- .
- <SPAN
-CLASS="QUOTE"
->"p4dti"</SPAN
->
-
- is now an officially supported product from Perforce, and you can find
- the "Perforce Public Depot" p4dti page at
- <A
-HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
-TARGET="_top"
-> http://public.perforce.com/public/perforce/p4dti/index.html</A
->
-
- .</P
-><P
->Integration of Perforce with Bugzilla, once patches are applied, is
- seamless. Perforce replication information will appear below the comments
- of each bug. Be certain you have a matching set of patches for the
- Bugzilla version you are installing. p4dti is designed to support
- multiple defect trackers, and maintains its own documentation for it.
- Please consult the pages linked above for further information.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="tinderbox"
-></A
->5.9.4. Tinderbox/Tinderbox2</H2
-><P
->We need Tinderbox integration information.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="appendix"
-><HR><H1
-><A
-NAME="faq"
-></A
->Appendix A. The Bugzilla FAQ</H1
-><P
-> This FAQ includes questions not covered elsewhere in the Guide.
- </P
-><DIV
-CLASS="qandaset"
-><DL
-><DT
->1. <A
-HREF="#faq-general"
->General Questions</A
-></DT
-><DD
-><DL
-><DT
->A.1.1. <A
-HREF="#faq-general-information"
-> Where can I find information about Bugzilla?</A
-></DT
-><DT
->A.1.2. <A
-HREF="#faq-general-license"
-> What license is Bugzilla distributed under?
- </A
-></DT
-><DT
->A.1.3. <A
-HREF="#faq-general-support"
-> How do I get commercial support for Bugzilla?
- </A
-></DT
-><DT
->A.1.4. <A
-HREF="#faq-general-companies"
-> What major companies or projects are currently using Bugzilla
- for bug-tracking?
- </A
-></DT
-><DT
->A.1.5. <A
-HREF="#faq-general-maintainers"
-> Who maintains Bugzilla?
- </A
-></DT
-><DT
->A.1.6. <A
-HREF="#faq-general-compare"
-> How does Bugzilla stack up against other bug-tracking databases?
- </A
-></DT
-><DT
->A.1.7. <A
-HREF="#faq-general-bzmissing"
-> Why doesn't Bugzilla offer this or that feature or compatibility
- with this other tracking software?
- </A
-></DT
-><DT
->A.1.8. <A
-HREF="#faq-general-mysql"
-> Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- </A
-></DT
-><DT
->A.1.9. <A
-HREF="#faq-general-bonsaitools"
-> Why do the scripts say
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
-> instead of
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> or something else?
- </A
-></DT
-><DT
->A.1.10. <A
-HREF="#faq-general-cookie"
-> Is there an easy way to change the Bugzilla cookie name?
- </A
-></DT
-></DL
-></DD
-><DT
->2. <A
-HREF="#faq-phb"
->Managerial Questions</A
-></DT
-><DD
-><DL
-><DT
->A.2.1. <A
-HREF="#faq-phb-client"
-> Is Bugzilla web-based, or do you have to have specific software or
- a specific operating system on your machine?
- </A
-></DT
-><DT
->A.2.2. <A
-HREF="#faq-phb-integration"
-> Can Bugzilla integrate with
- Perforce (SCM software)?
- </A
-></DT
-><DT
->A.2.3. <A
-HREF="#faq-phb-projects"
-> Does Bugzilla allow the user to track multiple projects?
- </A
-></DT
-><DT
->A.2.4. <A
-HREF="#faq-phb-sorting"
-> If I am on many projects, and search for all bugs assigned to me, will
- Bugzilla list them for me and allow me to sort by project, severity etc?
- </A
-></DT
-><DT
->A.2.5. <A
-HREF="#faq-phb-attachments"
-> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
- are there any that are NOT allowed?
- </A
-></DT
-><DT
->A.2.6. <A
-HREF="#faq-phb-priorities"
-> Does Bugzilla allow us to define our own priorities and levels? Do we
- have complete freedom to change the labels of fields and format of them, and
- the choice of acceptable values?
- </A
-></DT
-><DT
->A.2.7. <A
-HREF="#faq-phb-reporting"
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
- know, the type of stuff that management likes to see. :)
- </A
-></DT
-><DT
->A.2.8. <A
-HREF="#faq-phb-email"
-> Is there email notification and if so, what do you see when you get an
- email?
- </A
-></DT
-><DT
->A.2.9. <A
-HREF="#faq-phb-cclist"
-> Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
- </A
-></DT
-><DT
->A.2.10. <A
-HREF="#faq-phb-emailapp"
-> Do users have to have any particular
- type of email application?
- </A
-></DT
-><DT
->A.2.11. <A
-HREF="#faq-phb-data"
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
- write up a bug report using a MS Word bug template, could that template be
- imported into "matching" fields? If I wanted to take the results of a query
- and export that data to MS Excel, could I do that?
- </A
-></DT
-><DT
->A.2.12. <A
-HREF="#faq-phb-l10n"
-> Has anyone converted Bugzilla to another language to be used in other
- countries? Is it localizable?
- </A
-></DT
-><DT
->A.2.13. <A
-HREF="#faq-phb-reports"
-> Can a user create and save reports? Can they do this in Word format?
- Excel format?
- </A
-></DT
-><DT
->A.2.14. <A
-HREF="#faq-phb-searching"
-> Does Bugzilla have the ability to search by word, phrase, compound
- search?
- </A
-></DT
-><DT
->A.2.15. <A
-HREF="#faq-phb-midair"
-> Does Bugzilla provide record locking when there is simultaneous access
- to the same bug? Does the second person get a notice that the bug is in use
- or how are they notified?
- </A
-></DT
-><DT
->A.2.16. <A
-HREF="#faq-phb-backup"
-> Are there any backup features provided?
- </A
-></DT
-><DT
->A.2.17. <A
-HREF="#faq-phb-livebackup"
-> Can users be on the system while a backup is in progress?
- </A
-></DT
-><DT
->A.2.18. <A
-HREF="#faq-phb-maintenance"
-> What type of human resources are needed to be on staff to install and
- maintain Bugzilla? Specifically, what type of skills does the person need to
- have? I need to find out if we were to go with Bugzilla, what types of
- individuals would we need to hire and how much would that cost vs buying an
- "Out-of-the-Box" solution.
- </A
-></DT
-><DT
->A.2.19. <A
-HREF="#faq-phb-installtime"
-> What time frame are we looking at if we decide to hire people to install
- and maintain the Bugzilla? Is this something that takes hours or weeks to
- install and a couple of hours per week to maintain and customize or is this
- a multi-week install process, plus a full time job for 1 person, 2 people,
- etc?
- </A
-></DT
-><DT
->A.2.20. <A
-HREF="#faq-phb-cost"
-> Is there any licensing fee or other fees for using Bugzilla? Any
- out-of-pocket cost other than the bodies needed as identified above?
- </A
-></DT
-></DL
-></DD
-><DT
->3. <A
-HREF="#faq-security"
->Bugzilla Security</A
-></DT
-><DD
-><DL
-><DT
->A.3.1. <A
-HREF="#faq-security-mysql"
-> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the installation section of this guide)?
- </A
-></DT
-><DT
->A.3.2. <A
-HREF="#faq-security-knownproblems"
-> Are there any security problems with Bugzilla?
- </A
-></DT
-><DT
->A.3.3. <A
-HREF="#faq-security-mysqluser"
-> I've implemented the security fixes mentioned in Chris Yeh's security
- advisory of 5/10/2000 advising not to run MySQL as root, and am running into
- problems with MySQL no longer working correctly.
- </A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="#faq-email"
->Bugzilla Email</A
-></DT
-><DD
-><DL
-><DT
->A.4.1. <A
-HREF="#faq-email-nomail"
-> I have a user who doesn't want to receive any more email from Bugzilla.
- How do I stop it entirely for this user?
- </A
-></DT
-><DT
->A.4.2. <A
-HREF="#faq-email-testing"
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
- anyone but me. How do I do it?
- </A
-></DT
-><DT
->A.4.3. <A
-HREF="#faq-email-whine"
-> I want whineatnews.pl to whine at something more, or other than, only new
- bugs. How do I do it?
- </A
-></DT
-><DT
->A.4.4. <A
-HREF="#faq-email-procmail"
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
- What alternatives do I have?
- </A
-></DT
-><DT
->A.4.5. <A
-HREF="#faq-email-mailif"
-> How do I set up the email interface to submit/change bugs via email?
- </A
-></DT
-><DT
->A.4.6. <A
-HREF="#faq-email-sendmailnow"
-> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
- What gives?
- </A
-></DT
-><DT
->A.4.7. <A
-HREF="#faq-email-nonreceived"
-> How come email from Bugzilla changes never reaches me?
- </A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="#faq-db"
->Bugzilla Database</A
-></DT
-><DD
-><DL
-><DT
->A.5.1. <A
-HREF="#faq-db-oracle"
-> I've heard Bugzilla can be used with Oracle?
- </A
-></DT
-><DT
->A.5.2. <A
-HREF="#faq-db-corrupted"
-> I think my database might be corrupted, or contain invalid entries. What
- do I do?
- </A
-></DT
-><DT
->A.5.3. <A
-HREF="#faq-db-manualedit"
-> I want to manually edit some entries in my database. How?
- </A
-></DT
-><DT
->A.5.4. <A
-HREF="#faq-db-permissions"
-> I think I've set up MySQL permissions correctly, but Bugzilla still can't
- connect.
- </A
-></DT
-><DT
->A.5.5. <A
-HREF="#faq-db-synchronize"
-> How do I synchronize bug information among multiple different Bugzilla
- databases?
- </A
-></DT
-></DL
-></DD
-><DT
->6. <A
-HREF="#faq-nt"
->Bugzilla and Win32</A
-></DT
-><DD
-><DL
-><DT
->A.6.1. <A
-HREF="#faq-nt-easiest"
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
- </A
-></DT
-><DT
->A.6.2. <A
-HREF="#faq-nt-bundle"
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
- </A
-></DT
-><DT
->A.6.3. <A
-HREF="#faq-nt-mappings"
-> CGI's are failing with a "something.cgi is not a valid Windows NT
- application" error. Why?
- </A
-></DT
-><DT
->A.6.4. <A
-HREF="#faq-nt-dbi"
-> I'm having trouble with the perl modules for NT not being able to talk to
- to the database.
- </A
-></DT
-></DL
-></DD
-><DT
->7. <A
-HREF="#faq-use"
->Bugzilla Usage</A
-></DT
-><DD
-><DL
-><DT
->A.7.1. <A
-HREF="#faq-use-changeaddress"
-> How do I change my user name (email address) in Bugzilla?
- </A
-></DT
-><DT
->A.7.2. <A
-HREF="#faq-use-query"
-> The query page is very confusing. Isn't there a simpler way to query?
- </A
-></DT
-><DT
->A.7.3. <A
-HREF="#faq-use-accept"
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
- Why doesn't it assign the bug to me when I accept it?
- </A
-></DT
-><DT
->A.7.4. <A
-HREF="#faq-use-attachment"
-> I can't upload anything into the database via the "Create Attachment"
- link. What am I doing wrong?
- </A
-></DT
-><DT
->A.7.5. <A
-HREF="#faq-use-keyword"
-> How do I change a keyword in Bugzilla, once some bugs are using it?
- </A
-></DT
-><DT
->A.7.6. <A
-HREF="#faq-use-close"
-> Why can't I close bugs from the "Change Several Bugs at Once" page?
- </A
-></DT
-></DL
-></DD
-><DT
->8. <A
-HREF="#faq-hacking"
->Bugzilla Hacking</A
-></DT
-><DD
-><DL
-><DT
->A.8.1. <A
-HREF="#faq-hacking-bugzillabugs"
-> What bugs are in Bugzilla right now?
- </A
-></DT
-><DT
->A.8.2. <A
-HREF="#faq-hacking-priority"
-> How can I change the default priority to a null value? For instance, have the default
- priority be "---" instead of "P2"?
- </A
-></DT
-><DT
->A.8.3. <A
-HREF="#faq-hacking-patches"
-> What's the best way to submit patches? What guidelines should I follow?
- </A
-></DT
-></DL
-></DD
-></DL
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-general"
-></A
->1. General Questions</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-information"
-></A
-><B
->A.1.1. </B
->
- Where can I find information about Bugzilla?</P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can stay up-to-date with the latest Bugzilla
- information at <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
-> http://www.bugzilla.org/</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-license"
-></A
-><B
->A.1.2. </B
->
- What license is Bugzilla distributed under?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla is covered by the Mozilla Public License.
- See details at <A
-HREF="http://www.mozilla.org/MPL/"
-TARGET="_top"
-> http://www.mozilla.org/MPL/</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-support"
-></A
-><B
->A.1.3. </B
->
- How do I get commercial support for Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- <A
-HREF="http://bugzilla.org/consulting.html"
-TARGET="_top"
->http://bugzilla.org/consulting.html</A
->
- is a list of people and companies who have asked us to list them
- as consultants for Bugzilla.
- </P
-><P
-> <A
-HREF="http://www.collab.net/"
-TARGET="_top"
->www.collab.net</A
-> offers
- Bugzilla as part of their standard offering to large projects.
- They do have some minimum fees that are pretty hefty, and generally
- aren't interested in small projects.
- </P
-><P
-> There are several experienced
- Bugzilla hackers on the mailing list/newsgroup who are willing
- to make themselves available for generous compensation.
- Try sending a message to the mailing list asking for a volunteer.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-companies"
-></A
-><B
->A.1.4. </B
->
- What major companies or projects are currently using Bugzilla
- for bug-tracking?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- There are <EM
->dozens</EM
-> of major companies with public
- Bugzilla sites to track bugs in their products. A few include:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Netscape/AOL</TD
-></TR
-><TR
-><TD
->Mozilla.org</TD
-></TR
-><TR
-><TD
->NASA</TD
-></TR
-><TR
-><TD
->Red Hat Software</TD
-></TR
-><TR
-><TD
->SuSe Corp</TD
-></TR
-><TR
-><TD
->The Horde Project</TD
-></TR
-><TR
-><TD
->AbiSource</TD
-></TR
-><TR
-><TD
->Real Time Enterprises, Inc</TD
-></TR
-><TR
-><TD
->Eggheads.org</TD
-></TR
-><TR
-><TD
->Strata Software</TD
-></TR
-><TR
-><TD
->RockLinux</TD
-></TR
-><TR
-><TD
->Creative Labs (makers of SoundBlaster)</TD
-></TR
-><TR
-><TD
->The Apache Foundation</TD
-></TR
-><TR
-><TD
->The Gnome Foundation</TD
-></TR
-><TR
-><TD
->Ximian</TD
-></TR
-><TR
-><TD
->Linux-Mandrake</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
-> Suffice to say, there are more than enough huge projects using Bugzilla
- that we can safely say it's extremely popular.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-maintainers"
-></A
-><B
->A.1.5. </B
->
- Who maintains Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- A
- <A
-HREF="http://www.bugzilla.org/who_we_are.html"
-TARGET="_top"
->core team</A
->,
- led by Dave Miller (justdave@bugzilla.org).
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-compare"
-></A
-><B
->A.1.6. </B
->
- How does Bugzilla stack up against other bug-tracking databases?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- We can't find any head-to-head comparisons of Bugzilla against
- other defect-tracking software. If you know of one, please
- get in touch. However, from the author's personal
- experience with other bug-trackers, Bugzilla offers
- superior performance on commodity hardware, better price
- (free!), more developer- friendly features (such as stored
- queries, email integration, and platform independence),
- improved scalability, open source code, greater
- flexibility, and superior ease-of-use.
- </P
-><P
-> If you happen to be a commercial bug-tracker vendor, please
- step forward with a list of advantages your product has over
- Bugzilla. We'd be happy to include it in the "Competitors"
- section.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-bzmissing"
-></A
-><B
->A.1.7. </B
->
- Why doesn't Bugzilla offer this or that feature or compatibility
- with this other tracking software?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It may be that the support has not been built yet, or that you
- have not yet found it. Bugzilla is making tremendous strides in
- usability, customizability, scalability, and user interface. It
- is widely considered the most complete and popular open-source
- bug-tracking software in existence.
- </P
-><P
-> That doesn't mean it can't use improvement!
- You can help the project along by either hacking a patch yourself
- that supports the functionality you require, or else submitting a
- "Request for Enhancement" (RFE) using the bug submission interface
- at <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
-TARGET="_top"
->bugzilla.mozilla.org</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-mysql"
-></A
-><B
->A.1.8. </B
->
- Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- MySQL was originally chosen because it is free, easy to install,
- and was available for the hardware Netscape intended to run it on.
- </P
-><P
-> There is currently work in progress to make Bugzilla work on
- PostgreSQL and Sybase in the default distribution. You can track
- the progress of these initiatives in bugs <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
-TARGET="_top"
->98304</A
->
- and <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
-TARGET="_top"
->173130</A
->
- respectively.
- </P
-><P
-> Once both of these are done, adding support for additional
- database servers should be trivial.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-bonsaitools"
-></A
-><B
->A.1.9. </B
->
- Why do the scripts say
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
-> instead of
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> or something else?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Mozilla.org used <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
->,
- because originally Terry wanted a place to put a version of Perl
- and other tools that was strictly under his control.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> This convention was abonded during the 2.17 development cycle so
- it will no longer be an issue when 2.18 comes out.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-cookie"
-></A
-><B
->A.1.10. </B
->
- Is there an easy way to change the Bugzilla cookie name?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- At present, no.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-phb"
-></A
->2. Managerial Questions</H3
-><P
-> <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Questions likely to be asked by managers. :-)
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-client"
-></A
-><B
->A.2.1. </B
->
- Is Bugzilla web-based, or do you have to have specific software or
- a specific operating system on your machine?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It is web and e-mail based. You can edit bugs by sending specially
- formatted email to a properly configured Bugzilla, or control via the web.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-integration"
-></A
-><B
->A.2.2. </B
->
- Can Bugzilla integrate with
- Perforce (SCM software)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes! You can find more information elsewhere in "The Bugzilla
- Guide" in the "Integration with Third-Party Products" section.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-projects"
-></A
-><B
->A.2.3. </B
->
- Does Bugzilla allow the user to track multiple projects?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Absolutely! You can track any number of Products that can each be
- composed of any number of Components.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are only 55 groups available in version 2.16 of
- Bugzilla. If you are using product groups, this will also limit
- the number of products you can have. This limit does not exist in
- the current 2.17 development releases and will not exist in 2.18.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-sorting"
-></A
-><B
->A.2.4. </B
->
- If I am on many projects, and search for all bugs assigned to me, will
- Bugzilla list them for me and allow me to sort by project, severity etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-attachments"
-></A
-><B
->A.2.5. </B
->
- Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
- are there any that are NOT allowed?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes - any sort of attachment is allowed, although administrators can
- configure a maximum size.
- Bugzilla gives the user the option of either using the MIME-type
- supplied by the browser, choosing from a pre-defined list or
- manually typing any arbitrary MIME-type.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-priorities"
-></A
-><B
->A.2.6. </B
->
- Does Bugzilla allow us to define our own priorities and levels? Do we
- have complete freedom to change the labels of fields and format of them, and
- the choice of acceptable values?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. However, modifying some fields, notably those related to bug
- progression states, also require adjusting the program logic to
- compensate for the change.
- </P
-><P
-> There is no GUI for adding fields to Bugzilla at this
- time. You can follow development of this feature at
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
-TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-reporting"
-></A
-><B
->A.2.7. </B
->
- Does Bugzilla provide any reporting features, metrics, graphs, etc? You
- know, the type of stuff that management likes to see. :)
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. Look at <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
-TARGET="_top"
->http://bugzilla.mozilla.org/reports.cgi</A
->
- for samples of what Bugzilla can do in reporting and graphing.
- </P
-><P
-> If you can not get the reports you want from the included reporting
- scripts, it is possible to hook up a professional reporting package
- such as Crystal Reports using ODBC. If you choose to do this,
- beware that giving direct access to the database does contain some
- security implications. Even if you give read-only access to the
- bugs database it will bypass the secure bugs features of Bugzilla.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Bugzilla's current development versions can do a lot more in the
- way of reporting. To see examples, check out
- <A
-HREF="http://bugzilla.mozilla.org/report.cgi"
-TARGET="_top"
->http://bugzilla.mozilla.org/report.cgi</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-email"
-></A
-><B
->A.2.8. </B
->
- Is there email notification and if so, what do you see when you get an
- email?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Email notification is user-configurable. By default, the bug id and
- Summary of the bug report accompany each email notification, along with
- a list of the changes made.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-cclist"
-></A
-><B
->A.2.9. </B
->
- Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-emailapp"
-></A
-><B
->A.2.10. </B
->
- Do users have to have any particular
- type of email application?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla email is sent in plain text, the most compatible mail format
- on the planet.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you decide to use the bugzilla_email integration features
- to allow Bugzilla to record responses to mail with the associated bug,
- you may need to caution your users to set their mailer to "respond
- to messages in the format in which they were sent". For security reasons
- Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
- email into Bugzilla the resulting comment looks downright awful.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-data"
-></A
-><B
->A.2.11. </B
->
- Does Bugzilla allow data to be imported and exported? If I had outsiders
- write up a bug report using a MS Word bug template, could that template be
- imported into "matching" fields? If I wanted to take the results of a query
- and export that data to MS Excel, could I do that?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla can only output buglists as HTML in version 2.16. There
- are other formats available (CSV and RDF) in the newer development
- versions.
- </P
-><P
-> Bugzilla can export bugs using <TT
-CLASS="filename"
->xml.cgi</TT
-> with
- either a bug number or list of bug numbers.
- </P
-><P
-> Currently the only script included with Bugzilla that can import
- data is <TT
-CLASS="filename"
->importxml.pl</TT
-> which is intended to be
- used for importing the data generated by <TT
-CLASS="filename"
->xml.cgi</TT
->
- in association with bug moving. Any other use is left as an
- exercise for the user.
- </P
-><P
-> There are also scripts included in the <TT
-CLASS="filename"
->contrib/</TT
->
- directory for using e-mail to import information into Bugzilla,
- but these scripts are not currently supported and included for
- educational purposes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-l10n"
-></A
-><B
->A.2.12. </B
->
- Has anyone converted Bugzilla to another language to be used in other
- countries? Is it localizable?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. For more information including available translated templates,
- see <A
-HREF="http://www.bugzilla.org/download.html#localizations"
-TARGET="_top"
->http://www.bugzilla.org/download.html#localizations</A
->.
- The admin interfaces are still not included in these translated
- templates and is therefore still English only. Also, there may be
- issues with the charset not being declared. See <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
-TARGET="_top"
->bug 126226</A
->
- for more information.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-reports"
-></A
-><B
->A.2.13. </B
->
- Can a user create and save reports? Can they do this in Word format?
- Excel format?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. No. Not in 2.16.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-searching"
-></A
-><B
->A.2.14. </B
->
- Does Bugzilla have the ability to search by word, phrase, compound
- search?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You have no idea. Bugzilla's query interface, particularly with the
- advanced Boolean operators, is incredibly versatile.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-midair"
-></A
-><B
->A.2.15. </B
->
- Does Bugzilla provide record locking when there is simultaneous access
- to the same bug? Does the second person get a notice that the bug is in use
- or how are they notified?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla does not lock records. It provides mid-air collision detection,
- and offers the offending user a choice of options to deal with the conflict.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-backup"
-></A
-><B
->A.2.16. </B
->
- Are there any backup features provided?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- MySQL, the database back-end for Bugzilla, allows hot-backup of data.
- You can find strategies for dealing with backup considerations
- at <A
-HREF="http://www.mysql.com/doc/B/a/Backup.html"
-TARGET="_top"
-> http://www.mysql.com/doc/B/a/Backup.html</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-livebackup"
-></A
-><B
->A.2.17. </B
->
- Can users be on the system while a backup is in progress?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. However, commits to the database must wait
- until the tables are unlocked. Bugzilla databases are typically
- very small, and backups routinely take less than a minute.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-maintenance"
-></A
-><B
->A.2.18. </B
->
- What type of human resources are needed to be on staff to install and
- maintain Bugzilla? Specifically, what type of skills does the person need to
- have? I need to find out if we were to go with Bugzilla, what types of
- individuals would we need to hire and how much would that cost vs buying an
- "Out-of-the-Box" solution.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- If Bugzilla is set up correctly from the start, continuing maintenance
- needs are minimal and can be done easily using the web interface.
- </P
-><P
-> Commercial Bug-tracking software typically costs somewhere upwards
- of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
- is available from skilled members of the newsgroup. Simple questions
- are answered there and then.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-installtime"
-></A
-><B
->A.2.19. </B
->
- What time frame are we looking at if we decide to hire people to install
- and maintain the Bugzilla? Is this something that takes hours or weeks to
- install and a couple of hours per week to maintain and customize or is this
- a multi-week install process, plus a full time job for 1 person, 2 people,
- etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It all depends on your level of commitment. Someone with much Bugzilla
- experience can get you up and running in less than a day, and
- your Bugzilla install can run untended for years. If your
- Bugzilla strategy is critical to your business workflow, hire somebody
- with reasonable UNIX or Perl skills to handle your process management and
- bug-tracking maintenance & customization.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-cost"
-></A
-><B
->A.2.20. </B
->
- Is there any licensing fee or other fees for using Bugzilla? Any
- out-of-pocket cost other than the bodies needed as identified above?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- No. MySQL asks, if you find their product valuable, that you purchase
- a support contract from them that suits your needs.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-security"
-></A
->3. Bugzilla Security</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-mysql"
-></A
-><B
->A.3.1. </B
->
- How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the installation section of this guide)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
->this
- makes MySQL as secure as taping a $100 to the floor of a football stadium
- bathroom for safekeeping.</EM
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-knownproblems"
-></A
-><B
->A.3.2. </B
->
- Are there any security problems with Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The Bugzilla code has undergone a reasonably complete security audit,
- and user-facing CGIs run under Perl's taint mode. However,
- it is recommended that you closely examine permissions on your Bugzilla
- installation, and follow the recommended security guidelines found
- in The Bugzilla Guide.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-mysqluser"
-></A
-><B
->A.3.3. </B
->
- I've implemented the security fixes mentioned in Chris Yeh's security
- advisory of 5/10/2000 advising not to run MySQL as root, and am running into
- problems with MySQL no longer working correctly.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- This is a common problem, related to running out of file descriptors.
- Simply add "ulimit -n unlimited" to the script which starts
- mysqld.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-email"
-></A
->4. Bugzilla Email</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-nomail"
-></A
-><B
->A.4.1. </B
->
- I have a user who doesn't want to receive any more email from Bugzilla.
- How do I stop it entirely for this user?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The user should be able to set
- this in user email preferences (uncheck all boxes) or you can add
- their email address to the <TT
-CLASS="filename"
->data/nomail</TT
-> file.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-testing"
-></A
-><B
->A.4.2. </B
->
- I'm evaluating/testing Bugzilla, and don't want it to send email to
- anyone but me. How do I do it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
- replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-whine"
-></A
-><B
->A.4.3. </B
->
- I want whineatnews.pl to whine at something more, or other than, only new
- bugs. How do I do it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
- You can find it at <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
-TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
->. This
- patch is against an older version of Bugzilla, so you must apply
- the diffs manually.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-procmail"
-></A
-><B
->A.4.4. </B
->
- I don't like/want to use Procmail to hand mail off to bug_email.pl.
- What alternatives do I have?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can call bug_email.pl directly from your aliases file, with
- an entry like this:
- <A
-NAME="AEN1979"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
- </P
-></BLOCKQUOTE
->
- However, this is fairly nasty and subject to problems; you also
- need to set up your smrsh (sendmail restricted shell) to allow
- it. In a pinch, though, it can work.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-mailif"
-></A
-><B
->A.4.5. </B
->
- How do I set up the email interface to submit/change bugs via email?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can find an updated README.mailif file in the contrib/ directory
- of your Bugzilla distribution that walks you through the setup.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-sendmailnow"
-></A
-><B
->A.4.6. </B
->
- Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
- What gives?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- If you are using an alternate Mail Transport Agent (MTA other than
- sendmail), make sure the options given in the "processmail" and other
- scripts for all
- instances of "sendmail" are correct for your MTA.
- </P
-><P
-> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
- If you are using Postfix, you will also need to enable <SPAN
-CLASS="QUOTE"
->"sendmailnow"</SPAN
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-nonreceived"
-></A
-><B
->A.4.7. </B
->
- How come email from Bugzilla changes never reaches me?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Double-check that you have not turned off email in your user preferences.
- Confirm that Bugzilla is able to send email by visiting the "Log In"
- link of your Bugzilla installation and clicking the "Email me a password"
- button after entering your email address.
- </P
-><P
-> If you never receive mail from Bugzilla, chances you do not have
- sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
- to, "/usr/lib/sendmail".
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-db"
-></A
->5. Bugzilla Database</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-oracle"
-></A
-><B
->A.5.1. </B
->
- I've heard Bugzilla can be used with Oracle?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
- Red Hat's newer version (based on 2.17.1 and soon to be merged into
- the main distribution) runs on PostgreSQL. At this time we know of
- no recent ports of Bugzilla to Oracle but do intend to support it
- in the future (possibly the 2.20 time-frame).
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-corrupted"
-></A
-><B
->A.5.2. </B
->
- I think my database might be corrupted, or contain invalid entries. What
- do I do?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Run the <SPAN
-CLASS="QUOTE"
->"sanity check"</SPAN
-> utility
- (<TT
-CLASS="filename"
->./sanitycheck.cgi</TT
-> in the
- Bugzilla_home directory) from your web browser to see! If
- it finishes without errors, you're
- <EM
->probably</EM
-> OK. If it doesn't come back
- OK (i.e. any red letters), there are certain things
- Bugzilla can recover from and certain things it can't. If
- it can't auto-recover, I hope you're familiar with
- mysqladmin commands or have installed another way to
- manage your database. Sanity Check, although it is a good
- basic check on your database integrity, by no means is a
- substitute for competent database administration and
- avoiding deletion of data. It is not exhaustive, and was
- created to do a basic check for the most common problems
- in Bugzilla databases.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-manualedit"
-></A
-><B
->A.5.3. </B
->
- I want to manually edit some entries in my database. How?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- There is no facility in Bugzilla itself to do this. It's also generally
- not a smart thing to do if you don't know exactly what you're doing.
- However, if you understand SQL you can use the <B
-CLASS="command"
->mysql</B
->
- command line utility to manually insert, delete and modify table
- information. There are also more intuitive GUI clients available.
- Personal favorites of the Bugzilla team are <A
-HREF="http://www.phpmyadmin.net/"
-TARGET="_top"
->phpMyAdmin</A
-> and <A
-HREF="http://www.mysql.com/downloads/gui-mycc.html"
-TARGET="_top"
->MySQL Control
- Center</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-permissions"
-></A
-><B
->A.5.4. </B
->
- I think I've set up MySQL permissions correctly, but Bugzilla still can't
- connect.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try running MySQL from its binary: "mysqld --skip-grant-tables". This
- will allow you to completely rule out grant tables as the cause of your
- frustration. If this Bugzilla is able to connect at this point then
- you need to check that you have granted proper permission to the user
- password combo defined in <TT
-CLASS="filename"
->localconfig</TT
->.
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Running MySQL with this command line option is very insecure and
- should only be done when not connected to the external network
- as a troubleshooting step.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-synchronize"
-></A
-><B
->A.5.5. </B
->
- How do I synchronize bug information among multiple different Bugzilla
- databases?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Well, you can synchronize or you can move bugs. Synchronization will
- only work one way -- you can create a read-only copy of the database
- at one site, and have it regularly updated at intervals from the main
- database.
- </P
-><P
-> MySQL has some synchronization features builtin to the latest releases.
- It would be great if someone looked into the possibilities there
- and provided a report to the newsgroup on how to effectively
- synchronize two Bugzilla installations.
- </P
-><P
-> If you simply need to transfer bugs from one Bugzilla to another,
- checkout the "move.pl" script in the Bugzilla distribution.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-nt"
-></A
->6. Bugzilla and Win32</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-easiest"
-></A
-><B
->A.6.1. </B
->
- What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Remove Windows. Install Linux. Install Bugzilla.
- The boss will never know the difference.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-bundle"
-></A
-><B
->A.6.2. </B
->
- Is there a "Bundle::Bugzilla" equivalent for Win32?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
- installation on UNIX systems. If someone can volunteer to
- create a suitable PPM bundle for Win32, it would be appreciated.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-mappings"
-></A
-><B
->A.6.3. </B
->
- CGI's are failing with a "something.cgi is not a valid Windows NT
- application" error. Why?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Depending on what Web server you are using, you will have to configure
- the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
- adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the
- executable.
- </P
-><P
-> Microsoft has some advice on this matter, as well:
- <A
-NAME="AEN2055"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> "Set application mappings. In the ISM, map the extension for the script
- file(s) to the executable for the script interpreter. For example, you might
- map the extension .py to Python.exe, the executable for the Python script
- interpreter. Note For the ActiveState Perl script interpreter, the extension
- .pl is associated with PerlIS.dll by default. If you want to change the
- association of .pl to perl.exe, you need to change the application mapping.
- In the mapping, you must add two percent (%) characters to the end of the
- pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s"
- </P
-></BLOCKQUOTE
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-dbi"
-></A
-><B
->A.6.4. </B
->
- I'm having trouble with the perl modules for NT not being able to talk to
- to the database.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Your modules may be outdated or inaccurate. Try:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Hitting http://www.activestate.com/ActivePerl
- </P
-></LI
-><LI
-><P
-> Download ActivePerl
- </P
-></LI
-><LI
-><P
-> Go to your prompt
- </P
-></LI
-><LI
-><P
-> Type 'ppm'
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="prompt"
->PPM></TT
-> <B
-CLASS="command"
->install DBI DBD-mysql GD</B
->
- </P
-></LI
-></OL
->
- I reckon TimeDate and Data::Dumper come with the activeperl. You can check
- the ActiveState site for packages for installation through PPM.
- <A
-HREF=" http://www.activestate.com/Packages/"
-TARGET="_top"
-> http://www.activestate.com/Packages/</A
->
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-use"
-></A
->7. Bugzilla Usage</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-changeaddress"
-></A
-><B
->A.7.1. </B
->
- How do I change my user name (email address) in Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- New in 2.16 - go to the Account section of the Preferences. You will
- be emailed at both addresses for confirmation.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-query"
-></A
-><B
->A.7.2. </B
->
- The query page is very confusing. Isn't there a simpler way to query?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The interface was simplified by a UI designer for 2.16. Further
- suggestions for improvement are welcome, but we won't sacrifice power for
- simplicity.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-accept"
-></A
-><B
->A.7.3. </B
->
- I'm confused by the behavior of the "accept" button in the Show Bug form.
- Why doesn't it assign the bug to me when I accept it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The current behavior is acceptable to bugzilla.mozilla.org and most
- users. You have your choice of patches
- to change this behavior, however.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
-TARGET="_top"
-> Add a "and accept bug" radio button</A
-></TD
-></TR
-><TR
-><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
-TARGET="_top"
-> "Accept" button automatically assigns to you</A
-></TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- Note that these patches are somewhat dated. You will need to apply
- them manually.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-attachment"
-></A
-><B
->A.7.4. </B
->
- I can't upload anything into the database via the "Create Attachment"
- link. What am I doing wrong?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The most likely cause is a very old browser or a browser that is
- incompatible with file upload via POST. Download the latest Netscape,
- Microsoft, or Mozilla browser to handle uploads correctly.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-keyword"
-></A
-><B
->A.7.5. </B
->
- How do I change a keyword in Bugzilla, once some bugs are using it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- In the Bugzilla administrator UI, edit the keyword and it will let you
- replace the old keyword name with a new one. This will cause a problem
- with the keyword cache. Run sanitycheck.cgi to fix it.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-close"
-></A
-><B
->A.7.6. </B
->
- Why can't I close bugs from the "Change Several Bugs at Once" page?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
- You <EM
->can</EM
-> mass-CLOSE bugs from the change several
- bugs at once page. <EM
->but</EM
->, every bug listed on the
- page has to be in VERIFIED state before the control to do it will show
- up on the form. You can also mass-VERIFY, but every bug listed has to be
- RESOLVED in order for the control to show up on the form. The logic
- behind this is that if you pick one of the bugs that's not VERIFIED and
- try to CLOSE it, the bug change will fail miserably (thus killing any
- changes in the list after it while doing the bulk change) so it doesn't
- even give you the choice.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-hacking"
-></A
->8. Bugzilla Hacking</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-bugzillabugs"
-></A
-><B
->A.8.1. </B
->
- What bugs are in Bugzilla right now?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"
-TARGET="_top"
-> this link</A
-> to view current bugs or requests for
- enhancement for Bugzilla.
- </P
-><P
-> You can view bugs marked for 2.18 release
- <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"
-TARGET="_top"
->here</A
->.
- This list includes bugs for the 2.18 release that have already
- been fixed and checked into CVS. Please consult the
- <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
-> Bugzilla Project Page</A
-> for details on how to
- check current sources out of CVS so you can have these
- bug fixes early!
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-priority"
-></A
-><B
->A.8.2. </B
->
- How can I change the default priority to a null value? For instance, have the default
- priority be "---" instead of "P2"?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- This is well-documented here: <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
-TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
->. Ultimately, it's as easy
- as adding the "---" priority field to your localconfig file in the appropriate area,
- re-running checksetup.pl, and then changing the default priority in your browser using
- "editparams.cgi".
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-patches"
-></A
-><B
->A.8.3. </B
->
- What's the best way to submit patches? What guidelines should I follow?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Enter a bug into bugzilla.mozilla.org for the <SPAN
-CLASS="QUOTE"
->"<A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
-TARGET="_top"
->Bugzilla</A
->"</SPAN
->
- product.
- </P
-></LI
-><LI
-><P
-> Upload your patch as a unified diff (having used "diff -u" against
- the <EM
->current sources</EM
-> checked out of CVS),
- or new source file by clicking
- "Create a new attachment" link on the bug page you've just created, and
- include any descriptions of database changes you may make, into the bug
- ID you submitted in step #1. Be sure and click the "Patch" checkbox
- to indicate the text you are sending is a patch!
- </P
-></LI
-><LI
-><P
-> Announce your patch and the associated URL
- (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
- the newsgroup (netscape.public.mozilla.webtools). You'll get a really
- good, fairly immediate reaction to the implications of your patch,
- which will also give us an idea how well-received the change would
- be.
- </P
-></LI
-><LI
-><P
-> If it passes muster with minimal modification, the person to whom
- the bug is assigned in Bugzilla is responsible for seeing the patch
- is checked into CVS.
- </P
-></LI
-><LI
-><P
-> Bask in the glory of the fact that you helped write the most successful
- open-source bug-tracking software on the planet :)
- </P
-></LI
-></OL
-></P
-></DIV
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="appendix"
-><HR><H1
-><A
-NAME="database"
-></A
->Appendix B. The Bugzilla Database</H1
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This document really needs to be updated with more fleshed out
- information about primary keys, interrelationships, and maybe some nifty
- tables to document dependencies. Any takers?</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="dbschema"
-></A
->B.1. Database Schema Chart</H1
-><P
-> <DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="../images/dbschema.jpg"><DIV
-CLASS="caption"
-><P
->Bugzilla database relationships chart</P
-></DIV
-></P
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="dbdoc"
-></A
->B.2. MySQL Bugzilla Database Introduction</H1
-><P
->This information comes straight from my life. I was forced to learn
- how Bugzilla organizes database because of nitpicky requests from users
- for tiny changes in wording, rather than having people re-educate
- themselves or figure out how to work our procedures around the tool. It
- sucks, but it can and will happen to you, so learn how the schema works
- and deal with it when it comes.</P
-><P
->So, here you are with your brand-new installation of Bugzilla.
- You've got MySQL set up, Apache working right, Perl DBI and DBD talking
- to the database flawlessly. Maybe you've even entered a few test bugs to
- make sure email's working; people seem to be notified of new bugs and
- changes, and you can enter and edit bugs to your heart's content. Perhaps
- you've gone through the trouble of setting up a gateway for people to
- submit bugs to your database via email, have had a few people test it,
- and received rave reviews from your beta testers.</P
-><P
->What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new tool
- you've labored over for hours.</P
-><P
->Your first training session starts off very well! You have a
- captive audience which seems enraptured by the efficiency embodied in
- this thing called "Bugzilla". You are caught up describing the nifty
- features, how people can save favorite queries in the database, set them
- up as headers and footers on their pages, customize their layouts,
- generate reports, track status with greater efficiency than ever before,
- leap tall buildings with a single bound and rescue Jane from the clutches
- of Certain Death!</P
-><P
->But Certain Death speaks up -- a tiny voice, from the dark corners
- of the conference room. "I have a concern," the voice hisses from the
- darkness, "about the use of the word 'verified'.</P
-><P
->The room, previously filled with happy chatter, lapses into
- reverential silence as Certain Death (better known as the Vice President
- of Software Engineering) continues. "You see, for two years we've used
- the word 'verified' to indicate that a developer or quality assurance
- engineer has confirmed that, in fact, a bug is valid. I don't want to
- lose two years of training to a new software product. You need to change
- the bug status of 'verified' to 'approved' as soon as possible. To avoid
- confusion, of course."</P
-><P
->Oh no! Terror strikes your heart, as you find yourself mumbling
- "yes, yes, I don't think that would be a problem," You review the changes
- with Certain Death, and continue to jabber on, "no, it's not too big a
- change. I mean, we have the source code, right? You know, 'Use the
- Source, Luke' and all that... no problem," All the while you quiver
- inside like a beached jellyfish bubbling, burbling, and boiling on a hot
- Jamaican sand dune...</P
-><P
->Thus begins your adventure into the heart of Bugzilla. You've been
- forced to learn about non-portable enum() fields, varchar columns, and
- tinyint definitions. The Adventure Awaits You!</P
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN2175"
-></A
->B.2.1. Bugzilla Database Basics</H2
-><P
->If you were like me, at this point you're totally clueless about
- the internals of MySQL, and if it weren't for this executive order from
- the Vice President you couldn't care less about the difference between
- a
- <SPAN
-CLASS="QUOTE"
->"bigint"</SPAN
->
-
- and a
- <SPAN
-CLASS="QUOTE"
->"tinyint"</SPAN
->
-
- entry in MySQL. I recommend you refer to the MySQL documentation,
- available at
- <A
-HREF="http://www.mysql.com/doc.html"
-TARGET="_top"
->MySQL.com</A
->
-
- . Below are the basics you need to know about the Bugzilla database.
- Check the chart above for more details.</P
-><P
-> <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->To connect to your database:</P
-><P
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->mysql</B
->
-
- <TT
-CLASS="parameter"
-><I
->-u root</I
-></TT
->
- </P
-><P
->If this works without asking you for a password,
- <EM
->shame on you</EM
->
-
- ! You should have locked your security down like the installation
- instructions told you to. You can find details on locking down
- your database in the Bugzilla FAQ in this directory (under
- "Security"), or more robust security generalities in the
- <A
-HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
-TARGET="_top"
->MySQL
- searchable documentation</A
->.
- </P
-></LI
-><LI
-><P
->You should now be at a prompt that looks like this:</P
-><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- </P
-><P
->At the prompt, if
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- is the name you chose in the
- <TT
-CLASS="filename"
->localconfig</TT
->
-
- file for your Bugzilla database, type:</P
-><P
-> <TT
-CLASS="prompt"
->mysql</TT
->
-
- <B
-CLASS="command"
->use bugs;</B
->
- </P
-></LI
-></OL
->
- </P
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="AEN2202"
-></A
->B.2.1.1. Bugzilla Database Tables</H3
-><P
->Imagine your MySQL database as a series of spreadsheets, and
- you won't be too far off. If you use this command:</P
-><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- <B
-CLASS="command"
->show tables from bugs;</B
->
- </P
-><P
->you'll be able to see the names of all the
- <SPAN
-CLASS="QUOTE"
->"spreadsheets"</SPAN
->
- (tables) in your database.</P
-><P
->From the command issued above, ou should have some
- output that looks like this:
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> +-------------------+
-| Tables in bugs |
-+-------------------+
-| attachments |
-| bugs |
-| bugs_activity |
-| cc |
-| components |
-| dependencies |
-| fielddefs |
-| groups |
-| keyworddefs |
-| keywords |
-| logincookies |
-| longdescs |
-| milestones |
-| namedqueries |
-| products |
-| profiles |
-| profiles_activity |
-| shadowlog |
-| tokens |
-| versions |
-| votes |
-| watch |
-+-------------------+
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-</P
-><P
-CLASS="literallayout"
-><br>
- Here's an overview of what each table does. Most columns in each table have<br>
-descriptive names that make it fairly trivial to figure out their jobs.<br>
-<br>
-attachments: This table stores all attachments to bugs. It tends to be your<br>
-largest table, yet also generally has the fewest entries because file<br>
-attachments are so (relatively) large.<br>
-<br>
-bugs: This is the core of your system. The bugs table stores most of the<br>
-current information about a bug, with the exception of the info stored in the<br>
-other tables.<br>
-<br>
-bugs_activity: This stores information regarding what changes are made to bugs<br>
-when -- a history file.<br>
-<br>
-cc: This tiny table simply stores all the CC information for any bug which has<br>
-any entries in the CC field of the bug. Note that, like most other tables in<br>
-Bugzilla, it does not refer to users by their user names, but by their unique<br>
-userid, stored as a primary key in the profiles table.<br>
-<br>
-components: This stores the programs and components (or products and<br>
-components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
-(product) field is the full name of the product, rather than some other unique<br>
-identifier, like bug_id and user_id are elsewhere in the database.<br>
-<br>
-dependencies: Stores data about those cool dependency trees.<br>
-<br>
-fielddefs: A nifty table that defines other tables. For instance, when you<br>
-submit a form that changes the value of "AssignedTo" this table allows<br>
-translation to the actual field name "assigned_to" for entry into MySQL.<br>
-<br>
-groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
-identify group memberships. For instance, say the group that is allowed to<br>
-tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
-users is assigned a "2", and the group that is allowed to create new groups is<br>
-assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
-like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
-parameters and create groups, but not edit users, by giving him a bitmask of<br>
-"5", or a user allowed to edit users and create groups, but not tweak<br>
-parameters, by giving him a bitmask of "6" Simple, huh?<br>
- If this makes no sense to you, try this at the mysql prompt:<br>
-mysql> select * from groups;<br>
- You'll see the list, it makes much more sense that way.<br>
-<br>
-keyworddefs: Definitions of keywords to be used<br>
-<br>
-keywords: Unlike what you'd think, this table holds which keywords are<br>
-associated with which bug id's.<br>
-<br>
-logincookies: This stores every login cookie ever assigned to you for every<br>
-machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
-housecleaning -- I see cookies in this file I've not used for months. However,<br>
-since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
-sense.<br>
-<br>
-longdescs: The meat of bugzilla -- here is where all user comments are stored!<br>
-You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
-sparingly -- that's only the amount of space the Old Testament from the Bible<br>
-would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
-bug_id to which it's attached, so the order is necessarily chronological, for<br>
-comments are played back in the order in which they are received.<br>
-<br>
-milestones: Interesting that milestones are associated with a specific product<br>
-in this table, but Bugzilla does not yet support differing milestones by<br>
-product through the standard configuration interfaces.<br>
-<br>
-namedqueries: This is where everybody stores their "custom queries". Very<br>
-cool feature; it beats the tar out of having to bookmark each cool query you<br>
-construct.<br>
-<br>
-products: What products you have, whether new bug entries are allowed for the<br>
-product, what milestone you're working toward on that product, votes, etc. It<br>
-will be nice when the components table supports these same features, so you<br>
-could close a particular component for bug entry without having to close an<br>
-entire product...<br>
-<br>
-profiles: Ahh, so you were wondering where your precious user information was<br>
-stored? Here it is! With the passwords in plain text for all to see! (but<br>
-sshh... don't tell your users!)<br>
-<br>
-profiles_activity: Need to know who did what when to who's profile? This'll<br>
-tell you, it's a pretty complete history.<br>
-<br>
-shadowlog: I could be mistaken here, but I believe this table tells you when<br>
-your shadow database is updated and what commands were used to update it. We<br>
-don't use a shadow database at our site yet, so it's pretty empty for us.<br>
-<br>
-versions: Version information for every product<br>
-<br>
-votes: Who voted for what when<br>
-<br>
-watch: Who (according to userid) is watching who's bugs (according to their<br>
-userid).<br>
-<br>
-<br>
-===<br>
-THE DETAILS<br>
-===<br>
-<br>
- Ahh, so you're wondering just what to do with the information above? At the<br>
-mysql prompt, you can view any information about the columns in a table with<br>
-this command (where "table" is the name of the table you wish to view):<br>
-<br>
-mysql> show columns from table;<br>
-<br>
- You can also view all the data in a table with this command:<br>
-<br>
-mysql> select * from table;<br>
-<br>
- -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
-you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
-50,000 bugs play across your screen.<br>
-<br>
- You can limit the display from above a little with the command, where<br>
-"column" is the name of the column for which you wish to restrict information:<br>
-<br>
-mysql> select * from table where (column = "some info");<br>
-<br>
- -- or the reverse of this<br>
-<br>
-mysql> select * from table where (column != "some info");<br>
-<br>
- Let's take our example from the introduction, and assume you need to change<br>
-the word "verified" to "approved" in the resolution field. We know from the<br>
-above information that the resolution is likely to be stored in the "bugs"<br>
-table. Note we'll need to change a little perl code as well as this database<br>
-change, but I won't plunge into that in this document. Let's verify the<br>
-information is stored in the "bugs" table:<br>
-<br>
-mysql> show columns from bugs<br>
-<br>
- (exceedingly long output truncated here)<br>
-| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br>
-<br>
- Sorry about that long line. We see from this that the "bug status" column is<br>
-an "enum field", which is a MySQL peculiarity where a string type field can<br>
-only have certain types of entries. While I think this is very cool, it's not<br>
-standard SQL. Anyway, we need to add the possible enum field entry<br>
-'APPROVED' by altering the "bugs" table.<br>
-<br>
-mysql> ALTER table bugs CHANGE bug_status bug_status<br>
- -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br>
- -> "VERIFIED", "APPROVED", "CLOSED") not null;<br>
-<br>
- (note we can take three lines or more -- whatever you put in before the<br>
-semicolon is evaluated as a single expression)<br>
-<br>
-Now if you do this:<br>
-<br>
-mysql> show columns from bugs;<br>
-<br>
- you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
-available! Cool thing, too, is that this is reflected on your query page as<br>
-well -- you can query by the new status. But how's it fit into the existing<br>
-scheme of things?<br>
- Looks like you need to go back and look for instances of the word "verified"<br>
-in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
-"approved" and you're in business (make sure that's a case-insensitive search).<br>
-Although you can query by the enum field, you can't give something a status<br>
-of "APPROVED" until you make the perl changes. Note that this change I<br>
-mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
-this. But you need to know this stuff anyway, right?<br>
- </P
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="appendix"
-><HR><H1
-><A
-NAME="patches"
-></A
->Appendix C. Useful Patches and Utilities for Bugzilla</H1
-><P
->Are you looking for a way to put your Bugzilla into overdrive? Catch
- some of the niftiest tricks here in this section.</P
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="rewrite"
-></A
->C.1. Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</H1
-><P
->Apache's
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- module lets you do some truly amazing things with URL rewriting. Here are
- a couple of examples of what you can do.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Make it so if someone types
- <TT
-CLASS="computeroutput"
->http://www.foo.com/12345</TT
->
-
- , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
- setting up your VirtualHost section for Bugzilla with a rule like
- this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <VirtualHost 12.34.56.78>
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-</VirtualHost>
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->There are many, many more things you can do with mod_rewrite.
- Please refer to the mod_rewrite documentation at
- <A
-HREF="http://www.apache.org"
-TARGET="_top"
->http://www.apache.org</A
->.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="cmdline"
-></A
->C.2. Command-line Bugzilla Queries</H1
-><P
->There are a suite of Unix utilities for querying Bugzilla from the
- command line. They live in the
- <TT
-CLASS="filename"
->contrib/cmdline</TT
->
- directory. However, they
- have not yet been updated to work with 2.16 (post-templatisation.).
- There are three files - <TT
-CLASS="filename"
->query.conf</TT
->,
- <TT
-CLASS="filename"
->buglist</TT
-> and <TT
-CLASS="filename"
->bugs</TT
->.</P
-><P
-><TT
-CLASS="filename"
->query.conf</TT
->
- contains the mapping from options to field
- names and comparison types. Quoted option names are "grepped" for, so it
- should be easy to edit this file. Comments (#) have no effect; you must
- make sure these lines do not contain any quoted "option".</P
-><P
-><TT
-CLASS="filename"
->buglist</TT
->
- is a shell script which submits a Bugzilla query and writes
- the resulting HTML page to stdout. It supports both short options, (such
- as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
- "--reporter=bar"). If the first character of an option is not "-", it is
- treated as if it were prefixed with "--default=".</P
-><P
->The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the "Change Columns" option when you list bugs in
- buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
- in your cookies file to see your current COLUMNLIST setting.</P
-><P
-><TT
-CLASS="filename"
->bugs</TT
-> is a simple shell script which calls
- <TT
-CLASS="filename"
->buglist</TT
-> and extracts the
- bug numbers from the output. Adding the prefix
- "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
- a working link if any bugs are found. Counting bugs is easy. Pipe the
- results through
- <B
-CLASS="command"
->sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
->
- </P
-><P
->Akkana Peck says she has good results piping
- <TT
-CLASS="filename"
->buglist</TT
-> output through
- <B
-CLASS="command"
->w3m -T text/html -dump</B
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="appendix"
-><HR><H1
-><A
-NAME="variants"
-></A
->Appendix D. Bugzilla Variants and Competitors</H1
-><P
->I created this section to answer questions about Bugzilla competitors
- and variants, then found a wonderful site which covers an awful lot of what
- I wanted to discuss. Rather than quote it in its entirety, I'll simply
- refer you here:
- <A
-HREF="http://linas.org/linux/pm.html"
-TARGET="_top"
-> http://linas.org/linux/pm.html</A
->
- </P
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-redhat"
-></A
->D.1. Red Hat Bugzilla</H1
-><P
->Red Hat's old fork of Bugzilla which was based on version 2.8 is now
- obsolete. The newest version in use is based on version 2.17.1 and is in
- the process of being integrated into the main Bugzilla source tree. The
- back-end is modified to work with PostgreSQL instead of MySQL and they have
- custom templates to get their desired look and feel, but other than that it
- is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
- effort to make sure that the changes he made could be integrated back into
- the main tree.
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
-TARGET="_top"
->Bug
- 98304</A
-> exists to track this integration.
- </P
-><P
->URL:
- <A
-HREF="http://bugzilla.redhat.com/bugzilla/"
-TARGET="_top"
-> http://bugzilla.redhat.com/bugzilla/</A
->
- </P
-><P
->This section last updated 24 Dec 2002</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-fenris"
-></A
->D.2. Loki Bugzilla (Fenris)</H1
-><P
->Fenris was a fork from Bugzilla made by Loki Games; when
- Loki went into receivership, it died. While Loki's other code lives on,
- its custodians recommend Bugzilla for future bug-tracker deployments.
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-issuezilla"
-></A
->D.3. Issuezilla</H1
-><P
->Issuezilla was another fork from Bugzilla, made by collab.net and
- hosted at tigris.org. It is also dead; the primary focus of bug-tracking
- at tigris.org is their Java-based bug-tracker,
- <A
-HREF="#variant-scarab"
->Section D.4</A
->.</P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-scarab"
-></A
->D.4. Scarab</H1
-><P
->Scarab is a new open source bug-tracking system built using Java
- Servlet technology. It is currently at version 1.0 beta 13.</P
-><P
->URL:
- <A
-HREF="http://scarab.tigris.org/"
-TARGET="_top"
->http://scarab.tigris.org</A
->
- </P
-><P
->This section last updated 18 Jan 2003</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-perforce"
-></A
->D.5. Perforce SCM</H1
-><P
->Although Perforce isn't really a bug tracker, it can be used as
- such through the <SPAN
-CLASS="QUOTE"
->"jobs"</SPAN
->
- functionality.</P
-><P
->URL:
- <A
-HREF="http://www.perforce.com/perforce/technotes/note052.html"
-TARGET="_top"
-> http://www.perforce.com/perforce/technotes/note052.html
- </A
->
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="variant-sourceforge"
-></A
->D.6. SourceForge</H1
-><P
->SourceForge is a way of coordinating geographically
- distributed free software and open source projects over the Internet.
- It has a built-in bug tracker, but it's not highly thought of.</P
-><P
->URL:
- <A
-HREF="http://www.sourceforge.net"
-TARGET="_top"
-> http://www.sourceforge.net</A
->
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-></DIV
-><DIV
-CLASS="appendix"
-><HR><H1
-><A
-NAME="gfdl"
-></A
->Appendix E. GNU Free Documentation License</H1
-><P
->Version 1.1, March 2000</P
-><A
-NAME="AEN2290"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
- distribute verbatim copies of this license document, but changing it is
- not allowed.</P
-></BLOCKQUOTE
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-0"
-></A
->0. PREAMBLE</H1
-><P
->The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone the
- effective freedom to copy and redistribute it, with or without modifying
- it, either commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit for their
- work, while not being considered responsible for modifications made by
- others.</P
-><P
->This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft license
- designed for free software.</P
-><P
->We have designed this License in order to use it for manuals for
- free software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or whether
- it is published as a printed book. We recommend this License principally
- for works whose purpose is instruction or reference.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-1"
-></A
->1. APPLICABILITY AND DEFINITIONS</H1
-><P
->This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed under
- the terms of this License. The "Document", below, refers to any such
- manual or work. Any member of the public is a licensee, and is addressed
- as "you".</P
-><P
->A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.</P
-><P
->A "Secondary Section" is a named appendix or a front-matter section
- of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall subject
- (or to related matters) and contains nothing that could fall directly
- within that overall subject. (For example, if the Document is in part a
- textbook of mathematics, a Secondary Section may not explain any
- mathematics.) The relationship could be a matter of historical connection
- with the subject or with related matters, or of legal, commercial,
- philosophical, ethical or political position regarding them.</P
-><P
->The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in the
- notice that says that the Document is released under this License.</P
-><P
->The "Cover Texts" are certain short passages of text that are
- listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
- that the Document is released under this License.</P
-><P
->A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the general
- public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or for
- automatic translation to a variety of formats suitable for input to text
- formatters. A copy made in an otherwise Transparent file format whose
- markup has been designed to thwart or discourage subsequent modification
- by readers is not Transparent. A copy that is not "Transparent" is called
- "Opaque".</P
-><P
->Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML or
- XML using a publicly available DTD, and standard-conforming simple HTML
- designed for human modification. Opaque formats include PostScript, PDF,
- proprietary formats that can be read and edited only by proprietary word
- processors, SGML or XML for which the DTD and/or processing tools are not
- generally available, and the machine-generated HTML produced by some word
- processors for output purposes only.</P
-><P
->The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in formats
- which do not have any title page as such, "Title Page" means the text
- near the most prominent appearance of the work's title, preceding the
- beginning of the body of the text.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-2"
-></A
->2. VERBATIM COPYING</H1
-><P
->You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies to
- the Document are reproduced in all copies, and that you add no other
- conditions whatsoever to those of this License. You may not use technical
- measures to obstruct or control the reading or further copying of the
- copies you make or distribute. However, you may accept compensation in
- exchange for copies. If you distribute a large enough number of copies
- you must also follow the conditions in section 3.</P
-><P
->You may also lend copies, under the same conditions stated above,
- and you may publicly display copies.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-3"
-></A
->3. COPYING IN QUANTITY</H1
-><P
->If you publish printed copies of the Document numbering more than
- 100, and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all these
- Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
- on the back cover. Both covers must also clearly and legibly identify you
- as the publisher of these copies. The front cover must present the full
- title with all words of the title equally prominent and visible. You may
- add other material on the covers in addition. Copying with changes
- limited to the covers, as long as they preserve the title of the Document
- and satisfy these conditions, can be treated as verbatim copying in other
- respects.</P
-><P
->If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit reasonably)
- on the actual cover, and continue the rest onto adjacent pages.</P
-><P
->If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with each
- Opaque copy a publicly-accessible computer-network location containing a
- complete Transparent copy of the Document, free of added material, which
- the general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location until
- at least one year after the last time you distribute an Opaque copy
- (directly or through your agents or retailers) of that edition to the
- public.</P
-><P
->It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-4"
-></A
->4. MODIFICATIONS</H1
-><P
->You may copy and distribute a Modified Version of the Document
- under the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution and
- modification of the Modified Version to whoever possesses a copy of it.
- In addition, you must do these things in the Modified Version:</P
-><P
-></P
-><OL
-TYPE="A"
-><LI
-><P
->Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the History
- section of the Document). You may use the same title as a previous
- version if the original publisher of that version gives
- permission.</P
-></LI
-><LI
-><P
->List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has less
- than five).</P
-></LI
-><LI
-><P
->State on the Title page the name of the publisher of the
- Modified Version, as the publisher.</P
-></LI
-><LI
-><P
->Preserve all the copyright notices of the Document.</P
-></LI
-><LI
-><P
->Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.</P
-></LI
-><LI
-><P
->Include, immediately after the copyright notices, a license
- notice giving the public permission to use the Modified Version under
- the terms of this License, in the form shown in the Addendum
- below.</P
-></LI
-><LI
-><P
->Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.</P
-></LI
-><LI
-><P
->Include an unaltered copy of this License.</P
-></LI
-><LI
-><P
->Preserve the section entitled "History", and its title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.</P
-></LI
-><LI
-><P
->Preserve the network location, if any, given in the Document
- for public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions it
- was based on. These may be placed in the "History" section. You may
- omit a network location for a work that was published at least four
- years before the Document itself, or if the original publisher of the
- version it refers to gives permission.</P
-></LI
-><LI
-><P
->In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements and/or
- dedications given therein.</P
-></LI
-><LI
-><P
->Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.</P
-></LI
-><LI
-><P
->Delete any section entitled "Endorsements". Such a section may
- not be included in the Modified Version.</P
-></LI
-><LI
-><P
->Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.</P
-></LI
-></OL
-><P
->If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all of
- these sections as invariant. To do this, add their titles to the list of
- Invariant Sections in the Modified Version's license notice. These titles
- must be distinct from any other section titles.</P
-><P
->You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various parties--for
- example, statements of peer review or that the text has been approved by
- an organization as the authoritative definition of a standard.</P
-><P
->You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of the
- list of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or through
- arrangements made by) any one entity. If the Document already includes a
- cover text for the same cover, previously added by you or by arrangement
- made by the same entity you are acting on behalf of, you may not add
- another; but you may replace the old one, on explicit permission from the
- previous publisher that added the old one.</P
-><P
->The author(s) and publisher(s) of the Document do not by this
- License give permission to use their names for publicity for or to assert
- or imply endorsement of any Modified Version.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-5"
-></A
->5. COMBINING DOCUMENTS</H1
-><P
->You may combine the Document with other documents released under
- this License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and list
- them all as Invariant Sections of your combined work in its license
- notice.</P
-><P
->The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single copy.
- If there are multiple Invariant Sections with the same name but different
- contents, make the title of each such section unique by adding at the end
- of it, in parentheses, the name of the original author or publisher of
- that section if known, or else a unique number. Make the same adjustment
- to the section titles in the list of Invariant Sections in the license
- notice of the combined work.</P
-><P
->In the combination, you must combine any sections entitled
- "History" in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements", and
- any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-6"
-></A
->6. COLLECTIONS OF DOCUMENTS</H1
-><P
->You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual copies
- of this License in the various documents with a single copy that is
- included in the collection, provided that you follow the rules of this
- License for verbatim copying of each of the documents in all other
- respects.</P
-><P
->You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a copy
- of this License into the extracted document, and follow this License in
- all other respects regarding verbatim copying of that document.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-7"
-></A
->7. AGGREGATION WITH INDEPENDENT WORKS</H1
-><P
->A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of a
- storage or distribution medium, does not as a whole count as a Modified
- Version of the Document, provided no compilation copyright is claimed for
- the compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they are
- not themselves derivative works of the Document.</P
-><P
->If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter of
- the entire aggregate, the Document's Cover Texts may be placed on covers
- that surround only the Document within the aggregate. Otherwise they must
- appear on covers around the whole aggregate.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-8"
-></A
->8. TRANSLATION</H1
-><P
->Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include translations
- of some or all Invariant Sections in addition to the original versions of
- these Invariant Sections. You may include a translation of this License
- provided that you also include the original English version of this
- License. In case of a disagreement between the translation and the
- original English version of this License, the original English version
- will prevail.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-9"
-></A
->9. TERMINATION</H1
-><P
->You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt to
- copy, modify, sublicense or distribute the Document is void, and will
- automatically terminate your rights under this License. However, parties
- who have received copies, or rights, from you under this License will not
- have their licenses terminated so long as such parties remain in full
- compliance.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-10"
-></A
->10. FUTURE REVISIONS OF THIS LICENSE</H1
-><P
->The Free Software Foundation may publish new, revised versions of
- the GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- <A
-HREF="http://www.gnu.org/copyleft/"
-TARGET="_top"
-> http://www.gnu.org/copyleft/</A
->
-
- .</P
-><P
->Each version of the License is given a distinguishing version
- number. If the Document specifies that a particular numbered version of
- this License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or of
- any later version that has been published (not as a draft) by the Free
- Software Foundation. If the Document does not specify a version number of
- this License, you may choose any version ever published (not as a draft)
- by the Free Software Foundation.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="gfdl-howto"
-></A
->How to use this License for your documents</H1
-><P
->To use this License in a document you have written, include a copy
- of the License in the document and put the following copyright and
- license notices just after the title page:</P
-><A
-NAME="AEN2380"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU Free
- Documentation License, Version 1.1 or any later version published by
- the Free Software Foundation; with the Invariant Sections being LIST
- THEIR TITLES, with the Front-Cover Texts being LIST, and with the
- Back-Cover Texts being LIST. A copy of the license is included in the
- section entitled "GNU Free Documentation License".</P
-></BLOCKQUOTE
-><P
->If you have no Invariant Sections, write "with no Invariant
- Sections" instead of saying which ones are invariant. If you have no
- Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
- Texts being LIST"; likewise for Back-Cover Texts.</P
-><P
->If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of free
- software license, such as the GNU General Public License, to permit their
- use in free software.</P
-></DIV
-></DIV
-><DIV
-CLASS="GLOSSARY"
-><H1
-><A
-NAME="glossary"
-></A
->Glossary</H1
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="AEN2385"
-></A
->0-9, high ascii</H1
-><DL
-><DT
-><B
->.htaccess</B
-></DT
-><DD
-><P
->Apache web server, and other NCSA-compliant web servers,
- observe the convention of using files in directories called
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- to restrict access to certain files. In Bugzilla, they are used
- to keep secret files which would otherwise
- compromise your installation - e.g. the
- <TT
-CLASS="filename"
->localconfig</TT
->
- file contains the password to your database.
- curious.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-a"
-></A
->A</H1
-><DL
-><DT
-><B
->Apache</B
-></DT
-><DD
-><P
->In this context, Apache is the web server most commonly used
- for serving up
- <I
-CLASS="glossterm"
->Bugzilla</I
->
-
- pages. Contrary to popular belief, the apache web server has nothing
- to do with the ancient and noble Native American tribe, but instead
- derived its name from the fact that it was
- <SPAN
-CLASS="QUOTE"
->"a patchy"</SPAN
->
-
- version of the original
- <SPAN
-CLASS="acronym"
->NCSA</SPAN
->
-
- world-wide-web server.</P
-><P
-></P
-><DIV
-CLASS="variablelist"
-><P
-><B
->Useful Directives when configuring Bugzilla</B
-></P
-><DL
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
-TARGET="_top"
->AddHandler</A
-></TT
-></DT
-><DD
-><P
->Tell Apache that it's OK to run CGI scripts.</P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
-TARGET="_top"
->AllowOverride</A
-></TT
->, <TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
-TARGET="_top"
->Options</A
-></TT
-></DT
-><DD
-><P
->These directives are used to tell Apache many things about
- the directory they apply to. For Bugzilla's purposes, we need
- them to allow script execution and <TT
-CLASS="filename"
->.htaccess</TT
->
- overrides.
- </P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
-TARGET="_top"
->DirectoryIndex</A
-></TT
-></DT
-><DD
-><P
->Used to tell Apache what files are indexes. If you can
- not add <TT
-CLASS="filename"
->index.cgi</TT
-> to the list of valid files,
- you'll need to set <TT
-CLASS="computeroutput"
->$index_html</TT
-> to
- 1 in <TT
-CLASS="filename"
->localconfig</TT
-> so
- <B
-CLASS="command"
->./checksetup.pl</B
-> will create an
- <TT
-CLASS="filename"
->index.html</TT
-> that redirects to
- <TT
-CLASS="filename"
->index.cgi</TT
->.
- </P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
-TARGET="_top"
->ScriptInterpreterSource</A
-></TT
-></DT
-><DD
-><P
->Used when running Apache on windows so the shebang line
- doesn't have to be changed in every Bugzilla script.
- </P
-></DD
-></DL
-></DIV
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-b"
-></A
->B</H1
-><DL
-><DT
-><B
->Bug</B
-></DT
-><DD
-><P
->A
- <SPAN
-CLASS="QUOTE"
->"bug"</SPAN
->
-
- in Bugzilla refers to an issue entered into the database which has an
- associated number, assignments, comments, etc. Some also refer to a
- <SPAN
-CLASS="QUOTE"
->"tickets"</SPAN
->
- or
- <SPAN
-CLASS="QUOTE"
->"issues"</SPAN
->;
- in the context of Bugzilla, they are synonymous.</P
-></DD
-><DT
-><B
->Bug Number</B
-></DT
-><DD
-><P
->Each Bugzilla bug is assigned a number that uniquely identifies
- that bug. The bug associated with a bug number can be pulled up via a
- query, or easily from the very front page by typing the number in the
- "Find" box.</P
-></DD
-><DT
-><A
-NAME="gloss-bugzilla"
-></A
-><B
->Bugzilla</B
-></DT
-><DD
-><P
->Bugzilla is the world-leading free software bug tracking system.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-c"
-></A
->C</H1
-><DL
-><DT
-><A
-NAME="gloss-cgi"
-></A
-><B
->Common Gateway Interface</B
-></DT
-> (CGI)<DD
-><P
-><SPAN
-CLASS="acronym"
->CGI</SPAN
-> is an acronym for Common Gateway Interface.
- This is a standard for interfacing an external application with a web
- server. Bugzilla is an example of a <SPAN
-CLASS="acronym"
->CGI</SPAN
-> application.
- </P
-></DD
-><DT
-><A
-NAME="gloss-component"
-></A
-><B
->Component</B
-></DT
-><DD
-><P
->A Component is a subsection of a Product. It should be a narrow
- category, tailored to your organization. All Products must contain at
- least one Component (and, as a matter of fact, creating a Product
- with no Components will create an error in Bugzilla).</P
-></DD
-><DT
-><A
-NAME="gloss-cpan"
-></A
-><B
-> <SPAN
-CLASS="acronym"
->CPAN</SPAN
->
- </B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="acronym"
->CPAN</SPAN
->
-
- stands for the
- <SPAN
-CLASS="QUOTE"
->"Comprehensive Perl Archive Network"</SPAN
->.
- CPAN maintains a large number of extremely useful
- <I
-CLASS="glossterm"
->Perl</I
->
- modules - encapsulated chunks of code for performing a
- particular task.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-d"
-></A
->D</H1
-><DL
-><DT
-><B
->daemon</B
-></DT
-><DD
-><P
->A daemon is a computer program which runs in the background. In
- general, most daemons are started at boot time via System V init
- scripts, or through RC scripts on BSD-based systems.
- <I
-CLASS="glossterm"
->mysqld</I
->,
- the MySQL server, and
- <I
-CLASS="glossterm"
->apache</I
->,
- a web server, are generally run as daemons.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-g"
-></A
->G</H1
-><DL
-><DT
-><B
->Groups</B
-></DT
-><DD
-><P
->The word
- <SPAN
-CLASS="QUOTE"
->"Groups"</SPAN
->
-
- has a very special meaning to Bugzilla. Bugzilla's main security
- mechanism comes by placing users in groups, and assigning those
- groups certain privileges to view bugs in particular
- <I
-CLASS="glossterm"
->Products</I
->
- in the
- <I
-CLASS="glossterm"
->Bugzilla</I
->
- database.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-m"
-></A
->M</H1
-><DL
-><DT
-><A
-NAME="gloss-mta"
-></A
-><B
->Message Transport Agent</B
-></DT
-> (MTA)<DD
-><P
->A Message Transport Agent is used to control the flow of email
- on a system. Many unix based systems use
- <A
-HREF="http://www.sendmail.org"
-TARGET="_top"
->sendmail</A
-> which is what
- Bugzilla expects to find by default at <TT
-CLASS="filename"
->/usr/sbin/sendmail</TT
->.
- Many other MTA's will work, but they all require that the
- <TT
-CLASS="option"
->sendmailnow</TT
-> param be set to <TT
-CLASS="literal"
->on</TT
->.
- </P
-></DD
-><DT
-><A
-NAME="gloss-mysql"
-></A
-><B
->MySQL</B
-></DT
-><DD
-><P
->MySQL is currently the required
- <A
-HREF="#gloss-rdbms"
-><I
-CLASS="glossterm"
->RDBMS</I
-></A
-> for Bugzilla. MySQL
- can be downloaded from <A
-HREF="http://www.mysql.com"
-TARGET="_top"
->http://www.mysql.com</A
->. While you
- should familiarize yourself with all of the documentation, some high
- points are:
- </P
-><P
-></P
-><UL
-><LI
-><P
-><A
-HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
-TARGET="_top"
->MySQL
- Privilege System</A
-> - Much more detailed information about
- the suggestions in <A
-HREF="#security-mysql"
->Section 5.6.2</A
->.
- </P
-></LI
-></UL
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-p"
-></A
->P</H1
-><DL
-><DT
-><B
->Product</B
-></DT
-><DD
-><P
->A Product is a broad category of types of bugs, normally
- representing a single piece of software or entity. In general,
- there are several Components to a Product. A Product may define a
- group (used for security) for all bugs entered into
- its Components.</P
-></DD
-><DT
-><B
->Perl</B
-></DT
-><DD
-><P
->First written by Larry Wall, Perl is a remarkable program
- language. It has the benefits of the flexibility of an interpreted
- scripting language (such as shell script), combined with the speed
- and power of a compiled language, such as C.
- <I
-CLASS="glossterm"
->Bugzilla</I
->
-
- is maintained in Perl.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-q"
-></A
->Q</H1
-><DL
-><DT
-><B
->QA</B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="QUOTE"
->"QA"</SPAN
->,
- <SPAN
-CLASS="QUOTE"
->"Q/A"</SPAN
->, and
- <SPAN
-CLASS="QUOTE"
->"Q.A."</SPAN
->
- are short for
- <SPAN
-CLASS="QUOTE"
->"Quality Assurance"</SPAN
->.
- In most large software development organizations, there is a team
- devoted to ensuring the product meets minimum standards before
- shipping. This team will also generally want to track the progress of
- bugs over their life cycle, thus the need for the
- <SPAN
-CLASS="QUOTE"
->"QA Contact"</SPAN
->
-
- field in a bug.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-r"
-></A
->R</H1
-><DL
-><DT
-><A
-NAME="gloss-rdbms"
-></A
-><B
->Relational DataBase Managment System</B
-></DT
-> (RDBMS)<DD
-><P
->A relational database management system is a database system
- that stores information in tables that are related to each other.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-s"
-></A
->S</H1
-><DL
-><DT
-><B
-> <SPAN
-CLASS="acronym"
->SGML</SPAN
->
- </B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- stands for
- <SPAN
-CLASS="QUOTE"
->"Standard Generalized Markup Language"</SPAN
->.
- Created in the 1980's to provide an extensible means to maintain
- documentation based upon content instead of presentation,
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- has withstood the test of time as a robust, powerful language.
- <I
-CLASS="glossterm"
-> <SPAN
-CLASS="acronym"
->XML</SPAN
->
- </I
->
-
- is the
- <SPAN
-CLASS="QUOTE"
->"baby brother"</SPAN
->
-
- of SGML; any valid
- <SPAN
-CLASS="acronym"
->XML</SPAN
->
-
- document it, by definition, a valid
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- document. The document you are reading is written and maintained in
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->,
- and is also valid
- <SPAN
-CLASS="acronym"
->XML</SPAN
->
-
- if you modify the Document Type Definition.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-t"
-></A
->T</H1
-><DL
-><DT
-><A
-NAME="gloss-target-milestone"
-></A
-><B
->Target Milestone</B
-></DT
-><DD
-><P
->Target Milestones are Product goals. They are configurable on a
- per-Product basis. Most software development houses have a concept of
-
- <SPAN
-CLASS="QUOTE"
->"milestones"</SPAN
->
-
- where the people funding a project expect certain functionality on
- certain dates. Bugzilla facilitates meeting these milestones by
- giving you the ability to declare by which milestone a bug will be
- fixed, or an enhancement will be implemented.</P
-></DD
-><DT
-><A
-NAME="gloss-tcl"
-></A
-><B
->Tool Command Language</B
-></DT
-> (TCL)<DD
-><P
->TCL is an open source scripting language available for Windows,
- Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
- never released. The first release of Bugzilla was 2.0, which was when
- it was ported to perl.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-z"
-></A
->Z</H1
-><DL
-><DT
-><A
-NAME="gloss-zarro"
-></A
-><B
->Zarro Boogs Found</B
-></DT
-><DD
-><P
->This is just a goofy way of saying that there were no bugs
- found matching your query. When asked to explain this message,
- Terry had the following to say:
- </P
-><A
-NAME="AEN2579"
-></A
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
-><P
->I've been asked to explain this ... way back when, when
- Netscape released version 4.0 of its browser, we had a release
- party. Naturally, there had been a big push to try and fix every
- known bug before the release. Naturally, that hadn't actually
- happened. (This is not unique to Netscape or to 4.0; the same thing
- has happened with every software project I've ever seen.) Anyway,
- at the release party, T-shirts were handed out that said something
- like "Netscape 4.0: Zarro Boogs". Just like the software, the
- T-shirt had no known bugs. Uh-huh.
- </P
-><P
->So, when you query for a list of bugs, and it gets no results,
- you can think of this as a friendly reminder. Of *course* there are
- bugs matching your query, they just aren't in the bugsystem yet...
- </P
-></TD
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Terry Weissman</SPAN
-></TD
-><TD
-WIDTH="10%"
-> </TD
-></TR
-></TABLE
-></DD
-></DL
-></DIV
-></DIV
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->About This Guide</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="NEXT"
-TITLE="Copyright Information"
-HREF="copyright.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="index.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="about"
-></A
->Chapter 1. About This Guide</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1.1. <A
-HREF="copyright.html"
->Copyright Information</A
-></DT
-><DT
->1.2. <A
-HREF="disclaimer.html"
->Disclaimer</A
-></DT
-><DT
->1.3. <A
-HREF="newversions.html"
->New Versions</A
-></DT
-><DT
->1.4. <A
-HREF="credits.html"
->Credits</A
-></DT
-><DT
->1.5. <A
-HREF="conventions.html"
->Document Conventions</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla Guide - 2.16.4 Release</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Copyright Information</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Purpose and Scope of this Guide</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="NEXT"
-TITLE="Copyright Information"
-HREF="copyright.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
-><P
-> Bugzilla is simply the best piece of bug-tracking software the
- world has ever seen. This document is intended to be the
- comprehensive guide to the installation, administration,
- maintenance, and use of the Bugzilla bug-tracking system.
- </P
-><P
-> This release of the Bugzilla Guide is the
- <EM
->2.16</EM
-> release. It is so named that it
- may match the current version of Bugzilla. The numbering
- tradition stems from that used for many free software projects,
- in which <EM
->even-numbered</EM
-> point releases (1.2,
- 1.14, etc.) are considered "stable releases", intended for
- public consumption; on the other hand,
- <EM
->odd-numbered</EM
-> point releases (1.3, 2.09,
- etc.) are considered unstable <EM
->development</EM
->
- releases intended for advanced users, systems administrators,
- developers, and those who enjoy a lot of pain.
- </P
-><P
-> Newer revisions of the Bugzilla Guide follow the numbering
- conventions of the main-tree Bugzilla releases, available at
- <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
->http://www.bugzilla.org/</A
->. Intermediate releases will have
- a minor revision number following a period. The current version
- of Bugzilla, as of this writing (April 2nd, 2002) is 2.16; if
- something were seriously wrong with that edition of the Guide,
- subsequent releases would receive an additional dotted-decimal
- digit to indicate the update (2.16.1, 2.16.2, etc.).
- Got it? Good.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->About This Guide</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Copyright Information</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Administering Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Troubleshooting"
-HREF="troubleshooting.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla Configuration"
-HREF="parameters.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="parameters.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="administration"
-></A
->Chapter 5. Administering Bugzilla</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->5.1. <A
-HREF="parameters.html"
->Bugzilla Configuration</A
-></DT
-><DT
->5.2. <A
-HREF="useradmin.html"
->User Administration</A
-></DT
-><DD
-><DL
-><DT
->5.2.1. <A
-HREF="useradmin.html#defaultuser"
->Creating the Default User</A
-></DT
-><DT
->5.2.2. <A
-HREF="useradmin.html#manageusers"
->Managing Other Users</A
-></DT
-></DL
-></DD
-><DT
->5.3. <A
-HREF="programadmin.html"
->Product, Component, Milestone, and Version Administration</A
-></DT
-><DD
-><DL
-><DT
->5.3.1. <A
-HREF="programadmin.html#products"
->Products</A
-></DT
-><DT
->5.3.2. <A
-HREF="programadmin.html#components"
->Components</A
-></DT
-><DT
->5.3.3. <A
-HREF="programadmin.html#versions"
->Versions</A
-></DT
-><DT
->5.3.4. <A
-HREF="programadmin.html#milestones"
->Milestones</A
-></DT
-></DL
-></DD
-><DT
->5.4. <A
-HREF="voting.html"
->Voting</A
-></DT
-><DT
->5.5. <A
-HREF="groups.html"
->Groups and Group Security</A
-></DT
-><DT
->5.6. <A
-HREF="security.html"
->Bugzilla Security</A
-></DT
-><DD
-><DL
-><DT
->5.6.1. <A
-HREF="security.html#security-networking"
->TCP/IP Ports</A
-></DT
-><DT
->5.6.2. <A
-HREF="security.html#security-mysql"
->MySQL</A
-></DT
-><DT
->5.6.3. <A
-HREF="security.html#security-daemon"
->Daemon Accounts</A
-></DT
-><DT
->5.6.4. <A
-HREF="security.html#security-access"
->Web Server Access Controls</A
-></DT
-></DL
-></DD
-><DT
->5.7. <A
-HREF="cust-templates.html"
->Template Customisation</A
-></DT
-><DD
-><DL
-><DT
->5.7.1. <A
-HREF="cust-templates.html#AEN1534"
->What to Edit</A
-></DT
-><DT
->5.7.2. <A
-HREF="cust-templates.html#AEN1557"
->How To Edit Templates</A
-></DT
-><DT
->5.7.3. <A
-HREF="cust-templates.html#AEN1567"
->Template Formats</A
-></DT
-><DT
->5.7.4. <A
-HREF="cust-templates.html#AEN1580"
->Particular Templates</A
-></DT
-></DL
-></DD
-><DT
->5.8. <A
-HREF="upgrading.html"
->Upgrading to New Releases</A
-></DT
-><DT
->5.9. <A
-HREF="integration.html"
->Integrating Bugzilla with Third-Party Tools</A
-></DT
-><DD
-><DL
-><DT
->5.9.1. <A
-HREF="integration.html#bonsai"
->Bonsai</A
-></DT
-><DT
->5.9.2. <A
-HREF="integration.html#cvs"
->CVS</A
-></DT
-><DT
->5.9.3. <A
-HREF="integration.html#scm"
->Perforce SCM</A
-></DT
-><DT
->5.9.4. <A
-HREF="integration.html#tinderbox"
->Tinderbox/Tinderbox2</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="parameters.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Troubleshooting</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla Configuration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Command-line Bugzilla Queries</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
-REL="PREVIOUS"
-TITLE="Apache
- mod_rewrite
-
- magic"
-HREF="rewrite.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="rewrite.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. Useful Patches and Utilities for Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variants.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="cmdline"
-></A
->C.2. Command-line Bugzilla Queries</H1
-><P
->There are a suite of Unix utilities for querying Bugzilla from the
- command line. They live in the
- <TT
-CLASS="filename"
->contrib/cmdline</TT
->
- directory. However, they
- have not yet been updated to work with 2.16 (post-templatisation.).
- There are three files - <TT
-CLASS="filename"
->query.conf</TT
->,
- <TT
-CLASS="filename"
->buglist</TT
-> and <TT
-CLASS="filename"
->bugs</TT
->.</P
-><P
-><TT
-CLASS="filename"
->query.conf</TT
->
- contains the mapping from options to field
- names and comparison types. Quoted option names are "grepped" for, so it
- should be easy to edit this file. Comments (#) have no effect; you must
- make sure these lines do not contain any quoted "option".</P
-><P
-><TT
-CLASS="filename"
->buglist</TT
->
- is a shell script which submits a Bugzilla query and writes
- the resulting HTML page to stdout. It supports both short options, (such
- as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
- "--reporter=bar"). If the first character of an option is not "-", it is
- treated as if it were prefixed with "--default=".</P
-><P
->The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the "Change Columns" option when you list bugs in
- buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
- in your cookies file to see your current COLUMNLIST setting.</P
-><P
-><TT
-CLASS="filename"
->bugs</TT
-> is a simple shell script which calls
- <TT
-CLASS="filename"
->buglist</TT
-> and extracts the
- bug numbers from the output. Adding the prefix
- "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
- a working link if any bugs are found. Counting bugs is easy. Pipe the
- results through
- <B
-CLASS="command"
->sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
->
- </P
-><P
->Akkana Peck says she has good results piping
- <TT
-CLASS="filename"
->buglist</TT
-> output through
- <B
-CLASS="command"
->w3m -T text/html -dump</B
->
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="rewrite.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla Variants and Competitors</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Document Conventions</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Credits"
-HREF="credits.html"><LINK
-REL="NEXT"
-TITLE="Introduction"
-HREF="introduction.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="conventions"
-></A
->1.5. Document Conventions</H1
-><P
->This document uses the following conventions:</P
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN111"
-></A
-><P
-></P
-><TABLE
-BORDER="0"
-CLASS="CALSTABLE"
-><THEAD
-><TR
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Descriptions</TH
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Appearance</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Use caution</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't run with scissors!</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Hint</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Would you like a breath mint?</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Notes</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Dear John...</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Warnings</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Read this or the cat gets it.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->File Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->filename</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Directory Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->directory</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Commands to be typed</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <B
-CLASS="command"
->command</B
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Applications Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <SPAN
-CLASS="application"
->application</SPAN
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of root users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash#</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of user command under tcsh shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->tcsh$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Environment Variables</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="envar"
->VARIABLE</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Emphasized word</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <EM
->word</EM
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Term found in the glossary</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <A
-HREF="glossary.html#gloss-bugzilla"
-><I
-CLASS="glossterm"
->Bugzilla</I
-></A
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Code Example</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-><TT
-CLASS="sgmltag"
-><para></TT
->
-Beginning and end of paragraph
-<TT
-CLASS="sgmltag"
-></para></TT
-></PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Credits</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Introduction</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Copyright Information</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="NEXT"
-TITLE="Disclaimer"
-HREF="disclaimer.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="copyright"
-></A
->1.1. Copyright Information</H1
-><A
-NAME="AEN34"
-></A
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
-><P
-> Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation
- License, Version 1.1 or any later version published by the
- Free Software Foundation; with no Invariant Sections, no
- Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included in <A
-HREF="gfdl.html"
->Appendix E</A
->.
- </P
-></TD
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN
-></TD
-><TD
-WIDTH="10%"
-> </TD
-></TR
-></TABLE
-><P
-> If you have any questions regarding this document, its
- copyright, or publishing this document in non-electronic form,
- please contact The Bugzilla Team.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->About This Guide</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Disclaimer</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Credits</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="New Versions"
-HREF="newversions.html"><LINK
-REL="NEXT"
-TITLE="Document Conventions"
-HREF="conventions.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="newversions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="conventions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="credits"
-></A
->1.4. Credits</H1
-><P
-> The people listed below have made enormous contributions to the
- creation of this Guide, through their writing, dedicated hacking efforts,
- numerous e-mail and IRC support sessions, and overall excellent
- contribution to the Bugzilla community:
- </P
-><P
-></P
-><DIV
-CLASS="variablelist"
-><DL
-><DT
->Matthew P. Barnson <TT
-CLASS="email"
-><<A
-HREF="mailto:mbarnson@sisna.com"
->mbarnson@sisna.com</A
->></TT
-></DT
-><DD
-><P
->for the Herculaean task of pulling together the Bugzilla Guide
- and shepherding it to 2.14.
- </P
-></DD
-><DT
->Terry Weissman <TT
-CLASS="email"
-><<A
-HREF="mailto:terry@mozilla.org"
->terry@mozilla.org</A
->></TT
-></DT
-><DD
-><P
->for initially writing Bugzilla and creating the README upon
- which the UNIX installation documentation is largely based.
- </P
-></DD
-><DT
->Tara Hernandez <TT
-CLASS="email"
-><<A
-HREF="mailto:tara@tequilarists.org"
->tara@tequilarists.org</A
->></TT
-></DT
-><DD
-><P
->for keeping Bugzilla development going strong after Terry left
- mozilla.org and for running landfill.
- </P
-></DD
-><DT
->Dave Lawrence <TT
-CLASS="email"
-><<A
-HREF="mailto:dkl@redhat.com"
->dkl@redhat.com</A
->></TT
-></DT
-><DD
-><P
->for providing insight into the key differences between Red
- Hat's customized Bugzilla, and being largely responsible for
- <A
-HREF="variant-redhat.html"
->Section D.1</A
->.
- </P
-></DD
-><DT
->Dawn Endico <TT
-CLASS="email"
-><<A
-HREF="mailto:endico@mozilla.org"
->endico@mozilla.org</A
->></TT
-></DT
-><DD
-><P
->for being a hacker extraordinaire and putting up with Matthew's
- incessant questions and arguments on irc.mozilla.org in #mozwebtools
- </P
-></DD
-><DT
->Jacob Steenhagen <TT
-CLASS="email"
-><<A
-HREF="mailto:jake@bugzilla.org"
->jake@bugzilla.org</A
->></TT
-></DT
-><DD
-><P
->for taking over documentation during the 2.17 development
- period and backporting relevent docs changes to this 2.16 branch.
- </P
-></DD
-></DL
-></DIV
-><P
-> Last but not least, all the members of the
- <A
-HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
-TARGET="_top"
->news://news.mozilla.org/netscape/public/mozilla/webtools</A
->
- newsgroup. Without your discussions, insight, suggestions, and patches,
- this could never have happened.
- </P
-><P
-> Thanks also go to the following people for significant contributions
- to this documentation (in alphabetical order):
- Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
- .
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="newversions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="conventions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->New Versions</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Document Conventions</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Template Customisation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Bugzilla Security"
-HREF="security.html"><LINK
-REL="NEXT"
-TITLE="Upgrading to New Releases"
-HREF="upgrading.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="security.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="upgrading.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="cust-templates"
-></A
->5.7. Template Customisation</H1
-><P
-> One of the large changes for 2.16 was the templatisation of the
- entire user-facing UI, using the
- <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template Toolkit</A
->.
- Administrators can now configure the look and feel of Bugzilla without
- having to edit Perl files or face the nightmare of massive merge
- conflicts when they upgrade to a newer version in the future.
- </P
-><P
-> Templatisation also makes localised versions of Bugzilla possible,
- for the first time. In the future, a Bugzilla installation may
- have templates installed for multiple localisations, and select
- which ones to use based on the user's browser language setting.
- </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1534"
-></A
->5.7.1. What to Edit</H2
-><P
-> There are two different ways of editing of Bugzilla's templates,
- and which you use depends mainly on how you upgrade Bugzilla. The
- template directory structure is that there's a top level directory,
- <TT
-CLASS="filename"
->template</TT
->, which contains a directory for
- each installed localisation. The default English templates are
- therefore in <TT
-CLASS="filename"
->en</TT
->. Underneath that, there
- is the <TT
-CLASS="filename"
->default</TT
-> directory and optionally the
- <TT
-CLASS="filename"
->custom</TT
-> directory. The <TT
-CLASS="filename"
->default</TT
->
- directory contains all the templates shipped with Bugzilla, whereas
- the <TT
-CLASS="filename"
->custom</TT
-> directory does not exist at first and
- must be created if you want to use it.
- </P
-><P
-> The first method of making customisations is to directly edit the
- templates in <TT
-CLASS="filename"
->template/en/default</TT
->. This is
- probably the best method for small changes if you are going to use
- the CVS method of upgrading, because if you then execute a
- <B
-CLASS="command"
->cvs update</B
->, any template fixes will get
- automagically merged into your modified versions.
- </P
-><P
-> If you use this method, your installation will break if CVS conflicts
- occur.
- </P
-><P
-> The other method is to copy the templates into a mirrored directory
- structure under <TT
-CLASS="filename"
->template/en/custom</TT
->. The templates
- in this directory automatically override those in default.
- This is the technique you
- need to use if you use the overwriting method of upgrade, because
- otherwise your changes will be lost. This method is also better if
- you are using the CVS method of upgrading and are going to make major
- changes, because it is guaranteed that the contents of this directory
- will not be touched during an upgrade, and you can then decide whether
- to continue using your own templates, or make the effort to merge your
- changes into the new versions by hand.
- </P
-><P
-> If you use this method, your installation may break if incompatible
- changes are made to the template interface. If such changes are made
- they will be documented in the release notes, provided you are using a
- stable release of Bugzilla. If you use using unstable code, you will
- need to deal with this one yourself, although if possible the changes
- will be mentioned before they occur in the deprecations section of the
- previous stable release's release notes.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Don't directly edit the compiled templates in
- <TT
-CLASS="filename"
->data/template/*</TT
-> - your
- changes will be lost when Template Toolkit recompiles them.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is recommended that you run <B
-CLASS="command"
->./checksetup.pl</B
->
- after any template edits, especially if you've created a new file in
- the <TT
-CLASS="filename"
->custom</TT
-> directory.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1557"
-></A
->5.7.2. How To Edit Templates</H2
-><P
-> The syntax of the Template Toolkit language is beyond the scope of
- this guide. It's reasonably easy to pick up by looking at the current
- templates; or, you can read the manual, available on the
- <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template Toolkit home
- page</A
->. However, you should particularly remember (for security
- reasons) to always HTML filter things which come from the database or
- user input, to prevent cross-site scripting attacks.
- </P
-><P
-> However, one thing you should take particular care about is the need
- to properly HTML filter data that has been passed into the template.
- This means that if the data can possibly contain special HTML characters
- such as <, and the data was not intended to be HTML, they need to be
- converted to entity form, ie &lt;. You use the 'html' filter in the
- Template Toolkit to do this. If you fail to do this, you may open up
- your installation to cross-site scripting attacks.
- </P
-><P
-> Also note that Bugzilla adds a few filters of its own, that are not
- in standard Template Toolkit. In particular, the 'url_quote' filter
- can convert characters that are illegal or have special meaning in URLs,
- such as &, to the encoded form, ie %26. This actually encodes most
- characters (but not the common ones such as letters and numbers and so
- on), including the HTML-special characters, so there's never a need to
- HTML filter afterwards.
- </P
-><P
-> Editing templates is a good way of doing a "poor man's custom fields".
- For example, if you don't use the Status Whiteboard, but want to have
- a free-form text entry box for "Build Identifier", then you can just
- edit the templates to change the field labels. It's still be called
- status_whiteboard internally, but your users don't need to know that.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you are making template changes that you intend on submitting back
- for inclusion in standard Bugzilla, you should read the relevant
- sections of the
- <A
-HREF="http://www.bugzilla.org/developerguide.html"
-TARGET="_top"
->Developers'
- Guide</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1567"
-></A
->5.7.3. Template Formats</H2
-><P
-> Some CGIs have the ability to use more than one template. For
- example, buglist.cgi can output bug lists as RDF or two
- different forms of HTML (complex and simple). (Try this out
- by appending <TT
-CLASS="filename"
->&format=simple</TT
-> to a buglist.cgi
- URL on your Bugzilla installation.) This
- mechanism, called template 'formats', is extensible.
- </P
-><P
-> To see if a CGI supports multiple output formats, grep the
- CGI for "ValidateOutputFormat". If it's not present, adding
- multiple format support isn't too hard - see how it's done in
- other CGIs.
- </P
-><P
-> To make a new format template for a CGI which supports this,
- open a current template for
- that CGI and take note of the INTERFACE comment (if present.) This
- comment defines what variables are passed into this template. If
- there isn't one, I'm afraid you'll have to read the template and
- the code to find out what information you get.
- </P
-><P
-> Write your template in whatever markup or text style is appropriate.
- </P
-><P
-> You now need to decide what content type you want your template
- served as. Open up the <TT
-CLASS="filename"
->localconfig</TT
-> file and find the
- <TT
-CLASS="filename"
->$contenttypes</TT
->
- variable. If your content type is not there, add it. Remember
- the three- or four-letter tag assigned to you content type.
- This tag will be part of the template filename.
- </P
-><P
-> Save the template as <TT
-CLASS="filename"
-><stubname>-<formatname>.<contenttypetag>.tmpl</TT
->.
- Try out the template by calling the CGI as
- <TT
-CLASS="filename"
-><cginame>.cgi?format=<formatname></TT
-> .
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1580"
-></A
->5.7.4. Particular Templates</H2
-><P
-> There are a few templates you may be particularly interested in
- customising for your installation.
- </P
-><P
-> <B
-CLASS="command"
->index.html.tmpl</B
->:
- This is the Bugzilla front page.
- </P
-><P
-> <B
-CLASS="command"
->global/header.html.tmpl</B
->:
- This defines the header that goes on all Bugzilla pages.
- The header includes the banner, which is what appears to users
- and is probably what you want to edit instead. However the
- header also includes the HTML HEAD section, so you could for
- example add a stylesheet or META tag by editing the header.
- </P
-><P
-> <B
-CLASS="command"
->global/banner.html.tmpl</B
->:
- This contains the "banner", the part of the header that appears
- at the top of all Bugzilla pages. The default banner is reasonably
- barren, so you'll probably want to customise this to give your
- installation a distinctive look and feel. It is recommended you
- preserve the Bugzilla version number in some form so the version
- you are running can be determined, and users know what docs to read.
- </P
-><P
-> <B
-CLASS="command"
->global/footer.html.tmpl</B
->:
- This defines the footer that goes on all Bugzilla pages. Editing
- this is another way to quickly get a distinctive look and feel for
- your Bugzilla installation.
- </P
-><P
-> <B
-CLASS="command"
->bug/create/user-message.html.tmpl</B
->:
- This is a message that appears near the top of the bug reporting page.
- By modifying this, you can tell your users how they should report
- bugs.
- </P
-><P
-> <B
-CLASS="command"
->bug/create/create.html.tmpl</B
-> and
- <B
-CLASS="command"
->bug/create/comment.txt.tmpl</B
->:
- You may wish to get bug submitters to give certain bits of structured
- information, each in a separate input widget, for which there is not a
- field in the database. The bug entry system has been designed in an
- extensible fashion to enable you to define arbitrary fields and widgets,
- and have their values appear formatted in the initial
- Description, rather than in database fields. An example of this
- is the mozilla.org
- <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided"
-TARGET="_top"
->guided
- bug submission form</A
->.
- </P
-><P
-> To make this work, create a custom template for
- <TT
-CLASS="filename"
->enter_bug.cgi</TT
-> (the default template, on which you
- could base it, is <TT
-CLASS="filename"
->create.html.tmpl</TT
->),
- and either call it <TT
-CLASS="filename"
->create.html.tmpl</TT
-> or use a format and
- call it <TT
-CLASS="filename"
->create-<formatname>.html.tmpl</TT
->.
- Put it in the <TT
-CLASS="filename"
->custom/bug/create</TT
->
- directory. In it, add widgets for each piece of information you'd like
- collected - such as a build number, or set of steps to reproduce.
- </P
-><P
-> Then, create a template like
- <TT
-CLASS="filename"
->custom/bug/create/comment.txt.tmpl</TT
->, also named
- after your format if you are using one, which
- references the form fields you have created. When a bug report is
- submitted, the initial comment attached to the bug report will be
- formatted according to the layout of this template.
- </P
-><P
-> For example, if your enter_bug template had a field
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-><input type="text" name="buildid" size="30"></PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- and then your comment.txt.tmpl had
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->BuildID: [% form.buildid %]</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- then
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->BuildID: 20020303</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- would appear in the initial checkin comment.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="security.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="upgrading.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Security</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Upgrading to New Releases</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->The Bugzilla Database</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla FAQ"
-HREF="faq.html"><LINK
-REL="NEXT"
-TITLE="Database Schema Chart"
-HREF="dbschema.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="faq.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="dbschema.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="database"
-></A
->Appendix B. The Bugzilla Database</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->B.1. <A
-HREF="dbschema.html"
->Database Schema Chart</A
-></DT
-><DT
->B.2. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This document really needs to be updated with more fleshed out
- information about primary keys, interrelationships, and maybe some nifty
- tables to document dependencies. Any takers?</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="faq.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="dbschema.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla FAQ</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Database Schema Chart</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->MySQL Bugzilla Database Introduction</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="PREVIOUS"
-TITLE="Database Schema Chart"
-HREF="dbschema.html"><LINK
-REL="NEXT"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="dbschema.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix B. The Bugzilla Database</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="patches.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="dbdoc"
-></A
->B.2. MySQL Bugzilla Database Introduction</H1
-><P
->This information comes straight from my life. I was forced to learn
- how Bugzilla organizes database because of nitpicky requests from users
- for tiny changes in wording, rather than having people re-educate
- themselves or figure out how to work our procedures around the tool. It
- sucks, but it can and will happen to you, so learn how the schema works
- and deal with it when it comes.</P
-><P
->So, here you are with your brand-new installation of Bugzilla.
- You've got MySQL set up, Apache working right, Perl DBI and DBD talking
- to the database flawlessly. Maybe you've even entered a few test bugs to
- make sure email's working; people seem to be notified of new bugs and
- changes, and you can enter and edit bugs to your heart's content. Perhaps
- you've gone through the trouble of setting up a gateway for people to
- submit bugs to your database via email, have had a few people test it,
- and received rave reviews from your beta testers.</P
-><P
->What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new tool
- you've labored over for hours.</P
-><P
->Your first training session starts off very well! You have a
- captive audience which seems enraptured by the efficiency embodied in
- this thing called "Bugzilla". You are caught up describing the nifty
- features, how people can save favorite queries in the database, set them
- up as headers and footers on their pages, customize their layouts,
- generate reports, track status with greater efficiency than ever before,
- leap tall buildings with a single bound and rescue Jane from the clutches
- of Certain Death!</P
-><P
->But Certain Death speaks up -- a tiny voice, from the dark corners
- of the conference room. "I have a concern," the voice hisses from the
- darkness, "about the use of the word 'verified'.</P
-><P
->The room, previously filled with happy chatter, lapses into
- reverential silence as Certain Death (better known as the Vice President
- of Software Engineering) continues. "You see, for two years we've used
- the word 'verified' to indicate that a developer or quality assurance
- engineer has confirmed that, in fact, a bug is valid. I don't want to
- lose two years of training to a new software product. You need to change
- the bug status of 'verified' to 'approved' as soon as possible. To avoid
- confusion, of course."</P
-><P
->Oh no! Terror strikes your heart, as you find yourself mumbling
- "yes, yes, I don't think that would be a problem," You review the changes
- with Certain Death, and continue to jabber on, "no, it's not too big a
- change. I mean, we have the source code, right? You know, 'Use the
- Source, Luke' and all that... no problem," All the while you quiver
- inside like a beached jellyfish bubbling, burbling, and boiling on a hot
- Jamaican sand dune...</P
-><P
->Thus begins your adventure into the heart of Bugzilla. You've been
- forced to learn about non-portable enum() fields, varchar columns, and
- tinyint definitions. The Adventure Awaits You!</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN2175"
-></A
->B.2.1. Bugzilla Database Basics</H2
-><P
->If you were like me, at this point you're totally clueless about
- the internals of MySQL, and if it weren't for this executive order from
- the Vice President you couldn't care less about the difference between
- a
- <SPAN
-CLASS="QUOTE"
->"bigint"</SPAN
->
-
- and a
- <SPAN
-CLASS="QUOTE"
->"tinyint"</SPAN
->
-
- entry in MySQL. I recommend you refer to the MySQL documentation,
- available at
- <A
-HREF="http://www.mysql.com/doc.html"
-TARGET="_top"
->MySQL.com</A
->
-
- . Below are the basics you need to know about the Bugzilla database.
- Check the chart above for more details.</P
-><P
-> <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->To connect to your database:</P
-><P
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->mysql</B
->
-
- <TT
-CLASS="parameter"
-><I
->-u root</I
-></TT
->
- </P
-><P
->If this works without asking you for a password,
- <EM
->shame on you</EM
->
-
- ! You should have locked your security down like the installation
- instructions told you to. You can find details on locking down
- your database in the Bugzilla FAQ in this directory (under
- "Security"), or more robust security generalities in the
- <A
-HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
-TARGET="_top"
->MySQL
- searchable documentation</A
->.
- </P
-></LI
-><LI
-><P
->You should now be at a prompt that looks like this:</P
-><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- </P
-><P
->At the prompt, if
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- is the name you chose in the
- <TT
-CLASS="filename"
->localconfig</TT
->
-
- file for your Bugzilla database, type:</P
-><P
-> <TT
-CLASS="prompt"
->mysql</TT
->
-
- <B
-CLASS="command"
->use bugs;</B
->
- </P
-></LI
-></OL
->
- </P
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN2202"
-></A
->B.2.1.1. Bugzilla Database Tables</H3
-><P
->Imagine your MySQL database as a series of spreadsheets, and
- you won't be too far off. If you use this command:</P
-><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- <B
-CLASS="command"
->show tables from bugs;</B
->
- </P
-><P
->you'll be able to see the names of all the
- <SPAN
-CLASS="QUOTE"
->"spreadsheets"</SPAN
->
- (tables) in your database.</P
-><P
->From the command issued above, ou should have some
- output that looks like this:
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> +-------------------+
-| Tables in bugs |
-+-------------------+
-| attachments |
-| bugs |
-| bugs_activity |
-| cc |
-| components |
-| dependencies |
-| fielddefs |
-| groups |
-| keyworddefs |
-| keywords |
-| logincookies |
-| longdescs |
-| milestones |
-| namedqueries |
-| products |
-| profiles |
-| profiles_activity |
-| shadowlog |
-| tokens |
-| versions |
-| votes |
-| watch |
-+-------------------+
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-</P
-><P
-CLASS="literallayout"
-><br>
- Here's an overview of what each table does. Most columns in each table have<br>
-descriptive names that make it fairly trivial to figure out their jobs.<br>
-<br>
-attachments: This table stores all attachments to bugs. It tends to be your<br>
-largest table, yet also generally has the fewest entries because file<br>
-attachments are so (relatively) large.<br>
-<br>
-bugs: This is the core of your system. The bugs table stores most of the<br>
-current information about a bug, with the exception of the info stored in the<br>
-other tables.<br>
-<br>
-bugs_activity: This stores information regarding what changes are made to bugs<br>
-when -- a history file.<br>
-<br>
-cc: This tiny table simply stores all the CC information for any bug which has<br>
-any entries in the CC field of the bug. Note that, like most other tables in<br>
-Bugzilla, it does not refer to users by their user names, but by their unique<br>
-userid, stored as a primary key in the profiles table.<br>
-<br>
-components: This stores the programs and components (or products and<br>
-components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
-(product) field is the full name of the product, rather than some other unique<br>
-identifier, like bug_id and user_id are elsewhere in the database.<br>
-<br>
-dependencies: Stores data about those cool dependency trees.<br>
-<br>
-fielddefs: A nifty table that defines other tables. For instance, when you<br>
-submit a form that changes the value of "AssignedTo" this table allows<br>
-translation to the actual field name "assigned_to" for entry into MySQL.<br>
-<br>
-groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
-identify group memberships. For instance, say the group that is allowed to<br>
-tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
-users is assigned a "2", and the group that is allowed to create new groups is<br>
-assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
-like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
-parameters and create groups, but not edit users, by giving him a bitmask of<br>
-"5", or a user allowed to edit users and create groups, but not tweak<br>
-parameters, by giving him a bitmask of "6" Simple, huh?<br>
- If this makes no sense to you, try this at the mysql prompt:<br>
-mysql> select * from groups;<br>
- You'll see the list, it makes much more sense that way.<br>
-<br>
-keyworddefs: Definitions of keywords to be used<br>
-<br>
-keywords: Unlike what you'd think, this table holds which keywords are<br>
-associated with which bug id's.<br>
-<br>
-logincookies: This stores every login cookie ever assigned to you for every<br>
-machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
-housecleaning -- I see cookies in this file I've not used for months. However,<br>
-since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
-sense.<br>
-<br>
-longdescs: The meat of bugzilla -- here is where all user comments are stored!<br>
-You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
-sparingly -- that's only the amount of space the Old Testament from the Bible<br>
-would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
-bug_id to which it's attached, so the order is necessarily chronological, for<br>
-comments are played back in the order in which they are received.<br>
-<br>
-milestones: Interesting that milestones are associated with a specific product<br>
-in this table, but Bugzilla does not yet support differing milestones by<br>
-product through the standard configuration interfaces.<br>
-<br>
-namedqueries: This is where everybody stores their "custom queries". Very<br>
-cool feature; it beats the tar out of having to bookmark each cool query you<br>
-construct.<br>
-<br>
-products: What products you have, whether new bug entries are allowed for the<br>
-product, what milestone you're working toward on that product, votes, etc. It<br>
-will be nice when the components table supports these same features, so you<br>
-could close a particular component for bug entry without having to close an<br>
-entire product...<br>
-<br>
-profiles: Ahh, so you were wondering where your precious user information was<br>
-stored? Here it is! With the passwords in plain text for all to see! (but<br>
-sshh... don't tell your users!)<br>
-<br>
-profiles_activity: Need to know who did what when to who's profile? This'll<br>
-tell you, it's a pretty complete history.<br>
-<br>
-shadowlog: I could be mistaken here, but I believe this table tells you when<br>
-your shadow database is updated and what commands were used to update it. We<br>
-don't use a shadow database at our site yet, so it's pretty empty for us.<br>
-<br>
-versions: Version information for every product<br>
-<br>
-votes: Who voted for what when<br>
-<br>
-watch: Who (according to userid) is watching who's bugs (according to their<br>
-userid).<br>
-<br>
-<br>
-===<br>
-THE DETAILS<br>
-===<br>
-<br>
- Ahh, so you're wondering just what to do with the information above? At the<br>
-mysql prompt, you can view any information about the columns in a table with<br>
-this command (where "table" is the name of the table you wish to view):<br>
-<br>
-mysql> show columns from table;<br>
-<br>
- You can also view all the data in a table with this command:<br>
-<br>
-mysql> select * from table;<br>
-<br>
- -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
-you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
-50,000 bugs play across your screen.<br>
-<br>
- You can limit the display from above a little with the command, where<br>
-"column" is the name of the column for which you wish to restrict information:<br>
-<br>
-mysql> select * from table where (column = "some info");<br>
-<br>
- -- or the reverse of this<br>
-<br>
-mysql> select * from table where (column != "some info");<br>
-<br>
- Let's take our example from the introduction, and assume you need to change<br>
-the word "verified" to "approved" in the resolution field. We know from the<br>
-above information that the resolution is likely to be stored in the "bugs"<br>
-table. Note we'll need to change a little perl code as well as this database<br>
-change, but I won't plunge into that in this document. Let's verify the<br>
-information is stored in the "bugs" table:<br>
-<br>
-mysql> show columns from bugs<br>
-<br>
- (exceedingly long output truncated here)<br>
-| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br>
-<br>
- Sorry about that long line. We see from this that the "bug status" column is<br>
-an "enum field", which is a MySQL peculiarity where a string type field can<br>
-only have certain types of entries. While I think this is very cool, it's not<br>
-standard SQL. Anyway, we need to add the possible enum field entry<br>
-'APPROVED' by altering the "bugs" table.<br>
-<br>
-mysql> ALTER table bugs CHANGE bug_status bug_status<br>
- -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br>
- -> "VERIFIED", "APPROVED", "CLOSED") not null;<br>
-<br>
- (note we can take three lines or more -- whatever you put in before the<br>
-semicolon is evaluated as a single expression)<br>
-<br>
-Now if you do this:<br>
-<br>
-mysql> show columns from bugs;<br>
-<br>
- you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
-available! Cool thing, too, is that this is reflected on your query page as<br>
-well -- you can query by the new status. But how's it fit into the existing<br>
-scheme of things?<br>
- Looks like you need to go back and look for instances of the word "verified"<br>
-in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
-"approved" and you're in business (make sure that's a case-insensitive search).<br>
-Although you can query by the enum field, you can't give something a status<br>
-of "APPROVED" until you make the perl changes. Note that this change I<br>
-mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
-this. But you need to know this stuff anyway, right?<br>
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="dbschema.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Database Schema Chart</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Database Schema Chart</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="NEXT"
-TITLE="MySQL Bugzilla Database Introduction"
-HREF="dbdoc.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="database.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix B. The Bugzilla Database</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="dbschema"
-></A
->B.1. Database Schema Chart</H1
-><P
-> <DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="../images/dbschema.jpg"><DIV
-CLASS="caption"
-><P
->Bugzilla database relationships chart</P
-></DIV
-></P
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla Database</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->MySQL Bugzilla Database Introduction</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Disclaimer</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Copyright Information"
-HREF="copyright.html"><LINK
-REL="NEXT"
-TITLE="New Versions"
-HREF="newversions.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="copyright.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="newversions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="disclaimer"
-></A
->1.2. Disclaimer</H1
-><P
-> No liability for the contents of this document can be accepted.
- Use the concepts, examples, and other content at your own risk.
- This document may contain errors
- and inaccuracies that may damage your system, cause your partner
- to leave you, your boss to fire you, your cats to
- pee on your furniture and clothing, and global thermonuclear
- war. Proceed with caution.
- </P
-><P
-> All copyrights are held by their respective owners, unless
- specifically noted otherwise. Use of a term in this document
- should not be regarded as affecting the validity of any
- trademark or service mark.
- </P
-><P
-> Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". We
- wholeheartedly endorse the use of GNU/Linux in every situation
- where it is appropriate. It is an extremely versatile, stable,
- and robust operating system that offers an ideal operating
- environment for Bugzilla.
- </P
-><P
-> You are strongly recommended to make a backup of your system
- before installing Bugzilla and at regular intervals thereafter.
- If you implement any suggestion in this Guide, implement this one!
- </P
-><P
-> Although the Bugzilla development team has taken great care to
- ensure that all easily-exploitable bugs or options are
- documented or fixed in the code, security holes surely exist.
- Great care should be taken both in the installation and usage of
- this software. Carefully consider the implications of installing
- other network services with Bugzilla. The Bugzilla development
- team members, Netscape Communications, America Online Inc., and
- any affiliated developers or sponsors assume no liability for
- your use of this product. You have the source code to this
- product, and are responsible for auditing it yourself to ensure
- your security needs are met.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="copyright.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="newversions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Copyright Information</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->New Versions</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Optional Additional Configuration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Step-by-step Install"
-HREF="stepbystep.html"><LINK
-REL="NEXT"
-TITLE="Win32 Installation Notes"
-HREF="win32.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="win32.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="extraconfig"
-></A
->4.2. Optional Additional Configuration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN719"
-></A
->4.2.1. Dependency Charts</H2
-><P
->As well as the text-based dependency graphs, Bugzilla also
- supports dependency graphing, using a package called 'dot'.
- Exactly how this works is controlled by the 'webdotbase' parameter,
- which can have one of three values:
- </P
-><P
-> <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> A complete file path to the command 'dot' (part of
- <A
-HREF="http://www.graphviz.org/"
-TARGET="_top"
->GraphViz</A
->)
- will generate the graphs locally
- </P
-></LI
-><LI
-><P
-> A URL prefix pointing to an installation of the webdot package will
- generate the graphs remotely
- </P
-></LI
-><LI
-><P
-> A blank value will disable dependency graphing.
- </P
-></LI
-></OL
->
- </P
-><P
->So, to get this working, install
- <A
-HREF="http://www.graphviz.org/"
-TARGET="_top"
->GraphViz</A
->. If you
- do that, you need to
- <A
-HREF="http://httpd.apache.org/docs/mod/mod_imap.html"
-TARGET="_top"
->enable
- server-side image maps</A
-> in Apache.
- Alternatively, you could set up a webdot server, or use the AT&T
- public webdot server (the
- default for the webdotbase param). Note that AT&T's server won't work
- if Bugzilla is only accessible using HTTPS.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN734"
-></A
->4.2.2. Bug Graphs</H2
-><P
->As long as you installed the GD and Graph::Base Perl modules you
- might as well turn on the nifty Bugzilla bug reporting graphs.</P
-><P
->Add a cron entry like this to run
- <TT
-CLASS="filename"
->collectstats.pl</TT
->
- daily at 5 after midnight:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->crontab -e</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
->5 0 * * * cd <your-bugzilla-directory> ;
- ./collectstats.pl</TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->After two days have passed you'll be able to view bug graphs from
- the Bug Reports page.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN747"
-></A
->4.2.3. The Whining Cron</H2
-><P
->By now you have a fully functional Bugzilla, but what good are
- bugs if they're not annoying? To help make those bugs more annoying you
- can set up Bugzilla's automatic whining system to complain at engineers
- which leave their bugs in the NEW state without triaging them.
- </P
-><P
-> This can be done by
- adding the following command as a daily crontab entry (for help on that
- see that crontab man page):
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <B
-CLASS="command"
->cd <your-bugzilla-directory> ;
- ./whineatnews.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Depending on your system, crontab may have several manpages.
- The following command should lead you to the most useful page for
- this purpose:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->man 5 crontab</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bzldap"
-></A
->4.2.4. LDAP Authentication</H2
-><P
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This information on using the LDAP
- authentication options with Bugzilla is old, and the authors do
- not know of anyone who has tested it. Approach with caution.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
-> The existing authentication
- scheme for Bugzilla uses email addresses as the primary user ID, and a
- password to authenticate that user. All places within Bugzilla where
- you need to deal with user ID (e.g assigning a bug) use the email
- address. The LDAP authentication builds on top of this scheme, rather
- than replacing it. The initial log in is done with a username and
- password for the LDAP directory. This then fetches the email address
- from LDAP and authenticates seamlessly in the standard Bugzilla
- authentication scheme using this email address. If an account for this
- address already exists in your Bugzilla system, it will log in to that
- account. If no account for that email address exists, one is created at
- the time of login. (In this case, Bugzilla will attempt to use the
- "displayName" or "cn" attribute to determine the user's full name.)
- After authentication, all other user-related tasks are still handled by
- email address, not LDAP username. You still assign bugs by email
- address, query on users by email address, etc.
- </P
-><P
->Using LDAP for Bugzilla authentication requires the
- Mozilla::LDAP (aka PerLDAP) Perl module. The
- Mozilla::LDAP module in turn requires Netscape's Directory SDK for C.
- After you have installed the SDK, then install the PerLDAP module.
- Mozilla::LDAP and the Directory SDK for C are both
- <A
-HREF="http://www.mozilla.org/directory/"
-TARGET="_top"
->available for
- download</A
-> from mozilla.org.
- </P
-><P
-> Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
- directory for
- authentication. Be very careful when setting up this parameter; if you
- set LDAP authentication, but do not have a valid LDAP directory set up,
- you will not be able to log back in to Bugzilla once you log out. (If
- this happens, you can get back in by manually editing the data/params
- file, and setting useLDAP back to 0.)
- </P
-><P
->If using LDAP, you must set the
- three additional parameters: Set LDAPserver to the name (and optionally
- port) of your LDAP server. If no port is specified, it defaults to the
- default port of 389. (e.g "ldap.mycompany.com" or
- "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching
- for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids
- must be unique under the DN specified here. Set LDAPmailattribute to
- the name of the attribute in your LDAP directory which contains the
- primary email address. On most directory servers available, this is
- "mail", but you may need to change this.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="content-type"
-></A
->4.2.5. Preventing untrusted Bugzilla content from executing malicious
- Javascript code</H2
-><P
->It is possible for a Bugzilla to execute malicious Javascript
- code. Due to internationalization concerns, we are unable to
- incorporate the code changes necessary to fulfill the CERT advisory
- requirements mentioned in
- <A
-HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3"
-TARGET="_top"
-> http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
->.
- Executing the following code snippet from a UNIX command shell will
- rectify the problem if your Bugzilla installation is intended for an
- English-speaking audience. As always, be sure your Bugzilla
- installation has a good backup before making changes, and I recommend
- you understand what the script is doing before executing it.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->All this one-liner command does is search for all instances of
- <SPAN
-CLASS="QUOTE"
->"Content-type: text/html"</SPAN
->
-
- and replaces it with
- <SPAN
-CLASS="QUOTE"
->"Content-Type: text/html; charset=ISO-8859-1"</SPAN
->
-
- . This specification prevents possible Javascript attacks on the
- browser, and is suggested for all English-speaking sites. For
- non-English-speaking Bugzilla sites, I suggest changing
- <SPAN
-CLASS="QUOTE"
->"ISO-8859-1"</SPAN
->, above, to
- <SPAN
-CLASS="QUOTE"
->"UTF-8"</SPAN
->.</P
-><P
->Note: using <meta> tags to set the charset is not
- recommended, as there's a bug in Netscape 4.x which causes pages
- marked up in this way to load twice.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="htaccess"
-></A
->4.2.6. <TT
-CLASS="filename"
->.htaccess</TT
->
- files and security</H2
-><P
->To enhance the security of your Bugzilla installation, Bugzilla's
- <TT
-CLASS="filename"
->checksetup.pl</TT
-> script will generate
- <I
-CLASS="glossterm"
-> <TT
-CLASS="filename"
->.htaccess</TT
->
- </I
->
-
- files which the Apache webserver can use to restrict access to the
- bugzilla data files.
- These .htaccess files will not work with Apache 1.2.x - but this
- has security holes, so you shouldn't be using it anyway.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using an alternate provider of
- <SPAN
-CLASS="productname"
->webdot</SPAN
->
-
- services for graphing (as described when viewing
- <TT
-CLASS="filename"
->editparams.cgi</TT
->
-
- in your web browser), you will need to change the ip address in
- <TT
-CLASS="filename"
->data/webdot/.htaccess</TT
->
-
- to the ip address of the webdot server that you are using.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->The default .htaccess file may not provide adequate access
- restrictions, depending on your web server configuration. Be sure to
- check the <Directory> entries for your Bugzilla directory so that
- the
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- file is allowed to override web server defaults. For instance, let's
- assume your installation of Bugzilla is installed to
- <TT
-CLASS="filename"
->/usr/local/bugzilla</TT
->
-
- . You should have this <Directory> entry in your
- <TT
-CLASS="filename"
->httpd.conf</TT
->
-
- file:</P
-><P
->
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <Directory /usr/local/bugzilla/>
- Options +FollowSymLinks +Indexes +Includes +ExecCGI
- AllowOverride All
-</Directory>
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- </P
-><P
->The important part above is
- <SPAN
-CLASS="QUOTE"
->"AllowOverride All"</SPAN
->
-
- . Without that, the
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- file created by
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- will not have sufficient permissions to protect your Bugzilla
- installation.</P
-><P
->If you are using Internet Information Server (IIS) or another
- web server which does not observe
- <TT
-CLASS="filename"
->.htaccess</TT
->
- conventions, you can disable their creation by editing
- <TT
-CLASS="filename"
->localconfig</TT
->
- and setting the
- <TT
-CLASS="varname"
->$create_htaccess</TT
->
- variable to
- <TT
-CLASS="parameter"
-><I
->0</I
-></TT
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="mod-throttle"
-></A
->4.2.7. <TT
-CLASS="filename"
->mod_throttle</TT
->
-
- and Security</H2
-><P
->It is possible for a user, by mistake or on purpose, to access
- the database many times in a row which can result in very slow access
- speeds for other users. If your Bugzilla installation is experiencing
- this problem , you may install the Apache module
- <TT
-CLASS="filename"
->mod_throttle</TT
->
-
- which can limit connections by ip-address. You may download this module
- at
- <A
-HREF="http://www.snert.com/Software/mod_throttle/"
-TARGET="_top"
->http://www.snert.com/Software/mod_throttle/</A
->
- Follow the instructions to install into your Apache install.
- <EM
->This module only functions with the Apache web
- server!</EM
->
- You may use the
- <B
-CLASS="command"
->ThrottleClientIP</B
->
-
- command provided by this module to accomplish this goal. See the
- <A
-HREF="http://www.snert.com/Software/mod_throttle/"
-TARGET="_top"
->Module
- Instructions</A
->
- for more information.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="win32.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Step-by-step Install</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Win32 Installation Notes</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->The Bugzilla FAQ</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="NEXT"
-TITLE="The Bugzilla Database"
-HREF="database.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="integration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="database.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="faq"
-></A
->Appendix A. The Bugzilla FAQ</H1
-><P
-> This FAQ includes questions not covered elsewhere in the Guide.
- </P
-><DIV
-CLASS="qandaset"
-><DL
-><DT
->1. <A
-HREF="faq.html#faq-general"
->General Questions</A
-></DT
-><DD
-><DL
-><DT
->A.1.1. <A
-HREF="faq.html#faq-general-information"
-> Where can I find information about Bugzilla?</A
-></DT
-><DT
->A.1.2. <A
-HREF="faq.html#faq-general-license"
-> What license is Bugzilla distributed under?
- </A
-></DT
-><DT
->A.1.3. <A
-HREF="faq.html#faq-general-support"
-> How do I get commercial support for Bugzilla?
- </A
-></DT
-><DT
->A.1.4. <A
-HREF="faq.html#faq-general-companies"
-> What major companies or projects are currently using Bugzilla
- for bug-tracking?
- </A
-></DT
-><DT
->A.1.5. <A
-HREF="faq.html#faq-general-maintainers"
-> Who maintains Bugzilla?
- </A
-></DT
-><DT
->A.1.6. <A
-HREF="faq.html#faq-general-compare"
-> How does Bugzilla stack up against other bug-tracking databases?
- </A
-></DT
-><DT
->A.1.7. <A
-HREF="faq.html#faq-general-bzmissing"
-> Why doesn't Bugzilla offer this or that feature or compatibility
- with this other tracking software?
- </A
-></DT
-><DT
->A.1.8. <A
-HREF="faq.html#faq-general-mysql"
-> Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- </A
-></DT
-><DT
->A.1.9. <A
-HREF="faq.html#faq-general-bonsaitools"
-> Why do the scripts say
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
-> instead of
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> or something else?
- </A
-></DT
-><DT
->A.1.10. <A
-HREF="faq.html#faq-general-cookie"
-> Is there an easy way to change the Bugzilla cookie name?
- </A
-></DT
-></DL
-></DD
-><DT
->2. <A
-HREF="faq.html#faq-phb"
->Managerial Questions</A
-></DT
-><DD
-><DL
-><DT
->A.2.1. <A
-HREF="faq.html#faq-phb-client"
-> Is Bugzilla web-based, or do you have to have specific software or
- a specific operating system on your machine?
- </A
-></DT
-><DT
->A.2.2. <A
-HREF="faq.html#faq-phb-integration"
-> Can Bugzilla integrate with
- Perforce (SCM software)?
- </A
-></DT
-><DT
->A.2.3. <A
-HREF="faq.html#faq-phb-projects"
-> Does Bugzilla allow the user to track multiple projects?
- </A
-></DT
-><DT
->A.2.4. <A
-HREF="faq.html#faq-phb-sorting"
-> If I am on many projects, and search for all bugs assigned to me, will
- Bugzilla list them for me and allow me to sort by project, severity etc?
- </A
-></DT
-><DT
->A.2.5. <A
-HREF="faq.html#faq-phb-attachments"
-> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
- are there any that are NOT allowed?
- </A
-></DT
-><DT
->A.2.6. <A
-HREF="faq.html#faq-phb-priorities"
-> Does Bugzilla allow us to define our own priorities and levels? Do we
- have complete freedom to change the labels of fields and format of them, and
- the choice of acceptable values?
- </A
-></DT
-><DT
->A.2.7. <A
-HREF="faq.html#faq-phb-reporting"
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
- know, the type of stuff that management likes to see. :)
- </A
-></DT
-><DT
->A.2.8. <A
-HREF="faq.html#faq-phb-email"
-> Is there email notification and if so, what do you see when you get an
- email?
- </A
-></DT
-><DT
->A.2.9. <A
-HREF="faq.html#faq-phb-cclist"
-> Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
- </A
-></DT
-><DT
->A.2.10. <A
-HREF="faq.html#faq-phb-emailapp"
-> Do users have to have any particular
- type of email application?
- </A
-></DT
-><DT
->A.2.11. <A
-HREF="faq.html#faq-phb-data"
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
- write up a bug report using a MS Word bug template, could that template be
- imported into "matching" fields? If I wanted to take the results of a query
- and export that data to MS Excel, could I do that?
- </A
-></DT
-><DT
->A.2.12. <A
-HREF="faq.html#faq-phb-l10n"
-> Has anyone converted Bugzilla to another language to be used in other
- countries? Is it localizable?
- </A
-></DT
-><DT
->A.2.13. <A
-HREF="faq.html#faq-phb-reports"
-> Can a user create and save reports? Can they do this in Word format?
- Excel format?
- </A
-></DT
-><DT
->A.2.14. <A
-HREF="faq.html#faq-phb-searching"
-> Does Bugzilla have the ability to search by word, phrase, compound
- search?
- </A
-></DT
-><DT
->A.2.15. <A
-HREF="faq.html#faq-phb-midair"
-> Does Bugzilla provide record locking when there is simultaneous access
- to the same bug? Does the second person get a notice that the bug is in use
- or how are they notified?
- </A
-></DT
-><DT
->A.2.16. <A
-HREF="faq.html#faq-phb-backup"
-> Are there any backup features provided?
- </A
-></DT
-><DT
->A.2.17. <A
-HREF="faq.html#faq-phb-livebackup"
-> Can users be on the system while a backup is in progress?
- </A
-></DT
-><DT
->A.2.18. <A
-HREF="faq.html#faq-phb-maintenance"
-> What type of human resources are needed to be on staff to install and
- maintain Bugzilla? Specifically, what type of skills does the person need to
- have? I need to find out if we were to go with Bugzilla, what types of
- individuals would we need to hire and how much would that cost vs buying an
- "Out-of-the-Box" solution.
- </A
-></DT
-><DT
->A.2.19. <A
-HREF="faq.html#faq-phb-installtime"
-> What time frame are we looking at if we decide to hire people to install
- and maintain the Bugzilla? Is this something that takes hours or weeks to
- install and a couple of hours per week to maintain and customize or is this
- a multi-week install process, plus a full time job for 1 person, 2 people,
- etc?
- </A
-></DT
-><DT
->A.2.20. <A
-HREF="faq.html#faq-phb-cost"
-> Is there any licensing fee or other fees for using Bugzilla? Any
- out-of-pocket cost other than the bodies needed as identified above?
- </A
-></DT
-></DL
-></DD
-><DT
->3. <A
-HREF="faq.html#faq-security"
->Bugzilla Security</A
-></DT
-><DD
-><DL
-><DT
->A.3.1. <A
-HREF="faq.html#faq-security-mysql"
-> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the installation section of this guide)?
- </A
-></DT
-><DT
->A.3.2. <A
-HREF="faq.html#faq-security-knownproblems"
-> Are there any security problems with Bugzilla?
- </A
-></DT
-><DT
->A.3.3. <A
-HREF="faq.html#faq-security-mysqluser"
-> I've implemented the security fixes mentioned in Chris Yeh's security
- advisory of 5/10/2000 advising not to run MySQL as root, and am running into
- problems with MySQL no longer working correctly.
- </A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="faq.html#faq-email"
->Bugzilla Email</A
-></DT
-><DD
-><DL
-><DT
->A.4.1. <A
-HREF="faq.html#faq-email-nomail"
-> I have a user who doesn't want to receive any more email from Bugzilla.
- How do I stop it entirely for this user?
- </A
-></DT
-><DT
->A.4.2. <A
-HREF="faq.html#faq-email-testing"
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
- anyone but me. How do I do it?
- </A
-></DT
-><DT
->A.4.3. <A
-HREF="faq.html#faq-email-whine"
-> I want whineatnews.pl to whine at something more, or other than, only new
- bugs. How do I do it?
- </A
-></DT
-><DT
->A.4.4. <A
-HREF="faq.html#faq-email-procmail"
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
- What alternatives do I have?
- </A
-></DT
-><DT
->A.4.5. <A
-HREF="faq.html#faq-email-mailif"
-> How do I set up the email interface to submit/change bugs via email?
- </A
-></DT
-><DT
->A.4.6. <A
-HREF="faq.html#faq-email-sendmailnow"
-> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
- What gives?
- </A
-></DT
-><DT
->A.4.7. <A
-HREF="faq.html#faq-email-nonreceived"
-> How come email from Bugzilla changes never reaches me?
- </A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="faq.html#faq-db"
->Bugzilla Database</A
-></DT
-><DD
-><DL
-><DT
->A.5.1. <A
-HREF="faq.html#faq-db-oracle"
-> I've heard Bugzilla can be used with Oracle?
- </A
-></DT
-><DT
->A.5.2. <A
-HREF="faq.html#faq-db-corrupted"
-> I think my database might be corrupted, or contain invalid entries. What
- do I do?
- </A
-></DT
-><DT
->A.5.3. <A
-HREF="faq.html#faq-db-manualedit"
-> I want to manually edit some entries in my database. How?
- </A
-></DT
-><DT
->A.5.4. <A
-HREF="faq.html#faq-db-permissions"
-> I think I've set up MySQL permissions correctly, but Bugzilla still can't
- connect.
- </A
-></DT
-><DT
->A.5.5. <A
-HREF="faq.html#faq-db-synchronize"
-> How do I synchronize bug information among multiple different Bugzilla
- databases?
- </A
-></DT
-></DL
-></DD
-><DT
->6. <A
-HREF="faq.html#faq-nt"
->Bugzilla and Win32</A
-></DT
-><DD
-><DL
-><DT
->A.6.1. <A
-HREF="faq.html#faq-nt-easiest"
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
- </A
-></DT
-><DT
->A.6.2. <A
-HREF="faq.html#faq-nt-bundle"
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
- </A
-></DT
-><DT
->A.6.3. <A
-HREF="faq.html#faq-nt-mappings"
-> CGI's are failing with a "something.cgi is not a valid Windows NT
- application" error. Why?
- </A
-></DT
-><DT
->A.6.4. <A
-HREF="faq.html#faq-nt-dbi"
-> I'm having trouble with the perl modules for NT not being able to talk to
- to the database.
- </A
-></DT
-></DL
-></DD
-><DT
->7. <A
-HREF="faq.html#faq-use"
->Bugzilla Usage</A
-></DT
-><DD
-><DL
-><DT
->A.7.1. <A
-HREF="faq.html#faq-use-changeaddress"
-> How do I change my user name (email address) in Bugzilla?
- </A
-></DT
-><DT
->A.7.2. <A
-HREF="faq.html#faq-use-query"
-> The query page is very confusing. Isn't there a simpler way to query?
- </A
-></DT
-><DT
->A.7.3. <A
-HREF="faq.html#faq-use-accept"
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
- Why doesn't it assign the bug to me when I accept it?
- </A
-></DT
-><DT
->A.7.4. <A
-HREF="faq.html#faq-use-attachment"
-> I can't upload anything into the database via the "Create Attachment"
- link. What am I doing wrong?
- </A
-></DT
-><DT
->A.7.5. <A
-HREF="faq.html#faq-use-keyword"
-> How do I change a keyword in Bugzilla, once some bugs are using it?
- </A
-></DT
-><DT
->A.7.6. <A
-HREF="faq.html#faq-use-close"
-> Why can't I close bugs from the "Change Several Bugs at Once" page?
- </A
-></DT
-></DL
-></DD
-><DT
->8. <A
-HREF="faq.html#faq-hacking"
->Bugzilla Hacking</A
-></DT
-><DD
-><DL
-><DT
->A.8.1. <A
-HREF="faq.html#faq-hacking-bugzillabugs"
-> What bugs are in Bugzilla right now?
- </A
-></DT
-><DT
->A.8.2. <A
-HREF="faq.html#faq-hacking-priority"
-> How can I change the default priority to a null value? For instance, have the default
- priority be "---" instead of "P2"?
- </A
-></DT
-><DT
->A.8.3. <A
-HREF="faq.html#faq-hacking-patches"
-> What's the best way to submit patches? What guidelines should I follow?
- </A
-></DT
-></DL
-></DD
-></DL
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-general"
-></A
->1. General Questions</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-information"
-></A
-><B
->A.1.1. </B
->
- Where can I find information about Bugzilla?</P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can stay up-to-date with the latest Bugzilla
- information at <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
-> http://www.bugzilla.org/</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-license"
-></A
-><B
->A.1.2. </B
->
- What license is Bugzilla distributed under?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla is covered by the Mozilla Public License.
- See details at <A
-HREF="http://www.mozilla.org/MPL/"
-TARGET="_top"
-> http://www.mozilla.org/MPL/</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-support"
-></A
-><B
->A.1.3. </B
->
- How do I get commercial support for Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- <A
-HREF="http://bugzilla.org/consulting.html"
-TARGET="_top"
->http://bugzilla.org/consulting.html</A
->
- is a list of people and companies who have asked us to list them
- as consultants for Bugzilla.
- </P
-><P
-> <A
-HREF="http://www.collab.net/"
-TARGET="_top"
->www.collab.net</A
-> offers
- Bugzilla as part of their standard offering to large projects.
- They do have some minimum fees that are pretty hefty, and generally
- aren't interested in small projects.
- </P
-><P
-> There are several experienced
- Bugzilla hackers on the mailing list/newsgroup who are willing
- to make themselves available for generous compensation.
- Try sending a message to the mailing list asking for a volunteer.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-companies"
-></A
-><B
->A.1.4. </B
->
- What major companies or projects are currently using Bugzilla
- for bug-tracking?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- There are <EM
->dozens</EM
-> of major companies with public
- Bugzilla sites to track bugs in their products. A few include:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Netscape/AOL</TD
-></TR
-><TR
-><TD
->Mozilla.org</TD
-></TR
-><TR
-><TD
->NASA</TD
-></TR
-><TR
-><TD
->Red Hat Software</TD
-></TR
-><TR
-><TD
->SuSe Corp</TD
-></TR
-><TR
-><TD
->The Horde Project</TD
-></TR
-><TR
-><TD
->AbiSource</TD
-></TR
-><TR
-><TD
->Real Time Enterprises, Inc</TD
-></TR
-><TR
-><TD
->Eggheads.org</TD
-></TR
-><TR
-><TD
->Strata Software</TD
-></TR
-><TR
-><TD
->RockLinux</TD
-></TR
-><TR
-><TD
->Creative Labs (makers of SoundBlaster)</TD
-></TR
-><TR
-><TD
->The Apache Foundation</TD
-></TR
-><TR
-><TD
->The Gnome Foundation</TD
-></TR
-><TR
-><TD
->Ximian</TD
-></TR
-><TR
-><TD
->Linux-Mandrake</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
-> Suffice to say, there are more than enough huge projects using Bugzilla
- that we can safely say it's extremely popular.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-maintainers"
-></A
-><B
->A.1.5. </B
->
- Who maintains Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- A
- <A
-HREF="http://www.bugzilla.org/who_we_are.html"
-TARGET="_top"
->core team</A
->,
- led by Dave Miller (justdave@bugzilla.org).
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-compare"
-></A
-><B
->A.1.6. </B
->
- How does Bugzilla stack up against other bug-tracking databases?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- We can't find any head-to-head comparisons of Bugzilla against
- other defect-tracking software. If you know of one, please
- get in touch. However, from the author's personal
- experience with other bug-trackers, Bugzilla offers
- superior performance on commodity hardware, better price
- (free!), more developer- friendly features (such as stored
- queries, email integration, and platform independence),
- improved scalability, open source code, greater
- flexibility, and superior ease-of-use.
- </P
-><P
-> If you happen to be a commercial bug-tracker vendor, please
- step forward with a list of advantages your product has over
- Bugzilla. We'd be happy to include it in the "Competitors"
- section.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-bzmissing"
-></A
-><B
->A.1.7. </B
->
- Why doesn't Bugzilla offer this or that feature or compatibility
- with this other tracking software?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It may be that the support has not been built yet, or that you
- have not yet found it. Bugzilla is making tremendous strides in
- usability, customizability, scalability, and user interface. It
- is widely considered the most complete and popular open-source
- bug-tracking software in existence.
- </P
-><P
-> That doesn't mean it can't use improvement!
- You can help the project along by either hacking a patch yourself
- that supports the functionality you require, or else submitting a
- "Request for Enhancement" (RFE) using the bug submission interface
- at <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
-TARGET="_top"
->bugzilla.mozilla.org</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-mysql"
-></A
-><B
->A.1.8. </B
->
- Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- MySQL was originally chosen because it is free, easy to install,
- and was available for the hardware Netscape intended to run it on.
- </P
-><P
-> There is currently work in progress to make Bugzilla work on
- PostgreSQL and Sybase in the default distribution. You can track
- the progress of these initiatives in bugs <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
-TARGET="_top"
->98304</A
->
- and <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
-TARGET="_top"
->173130</A
->
- respectively.
- </P
-><P
-> Once both of these are done, adding support for additional
- database servers should be trivial.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-bonsaitools"
-></A
-><B
->A.1.9. </B
->
- Why do the scripts say
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
-> instead of
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> or something else?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Mozilla.org used <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
->,
- because originally Terry wanted a place to put a version of Perl
- and other tools that was strictly under his control.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> This convention was abonded during the 2.17 development cycle so
- it will no longer be an issue when 2.18 comes out.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-general-cookie"
-></A
-><B
->A.1.10. </B
->
- Is there an easy way to change the Bugzilla cookie name?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- At present, no.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-phb"
-></A
->2. Managerial Questions</H3
-><P
-> <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Questions likely to be asked by managers. :-)
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-client"
-></A
-><B
->A.2.1. </B
->
- Is Bugzilla web-based, or do you have to have specific software or
- a specific operating system on your machine?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It is web and e-mail based. You can edit bugs by sending specially
- formatted email to a properly configured Bugzilla, or control via the web.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-integration"
-></A
-><B
->A.2.2. </B
->
- Can Bugzilla integrate with
- Perforce (SCM software)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes! You can find more information elsewhere in "The Bugzilla
- Guide" in the "Integration with Third-Party Products" section.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-projects"
-></A
-><B
->A.2.3. </B
->
- Does Bugzilla allow the user to track multiple projects?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Absolutely! You can track any number of Products that can each be
- composed of any number of Components.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are only 55 groups available in version 2.16 of
- Bugzilla. If you are using product groups, this will also limit
- the number of products you can have. This limit does not exist in
- the current 2.17 development releases and will not exist in 2.18.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-sorting"
-></A
-><B
->A.2.4. </B
->
- If I am on many projects, and search for all bugs assigned to me, will
- Bugzilla list them for me and allow me to sort by project, severity etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-attachments"
-></A
-><B
->A.2.5. </B
->
- Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
- are there any that are NOT allowed?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes - any sort of attachment is allowed, although administrators can
- configure a maximum size.
- Bugzilla gives the user the option of either using the MIME-type
- supplied by the browser, choosing from a pre-defined list or
- manually typing any arbitrary MIME-type.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-priorities"
-></A
-><B
->A.2.6. </B
->
- Does Bugzilla allow us to define our own priorities and levels? Do we
- have complete freedom to change the labels of fields and format of them, and
- the choice of acceptable values?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. However, modifying some fields, notably those related to bug
- progression states, also require adjusting the program logic to
- compensate for the change.
- </P
-><P
-> There is no GUI for adding fields to Bugzilla at this
- time. You can follow development of this feature at
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
-TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-reporting"
-></A
-><B
->A.2.7. </B
->
- Does Bugzilla provide any reporting features, metrics, graphs, etc? You
- know, the type of stuff that management likes to see. :)
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. Look at <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
-TARGET="_top"
->http://bugzilla.mozilla.org/reports.cgi</A
->
- for samples of what Bugzilla can do in reporting and graphing.
- </P
-><P
-> If you can not get the reports you want from the included reporting
- scripts, it is possible to hook up a professional reporting package
- such as Crystal Reports using ODBC. If you choose to do this,
- beware that giving direct access to the database does contain some
- security implications. Even if you give read-only access to the
- bugs database it will bypass the secure bugs features of Bugzilla.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Bugzilla's current development versions can do a lot more in the
- way of reporting. To see examples, check out
- <A
-HREF="http://bugzilla.mozilla.org/report.cgi"
-TARGET="_top"
->http://bugzilla.mozilla.org/report.cgi</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-email"
-></A
-><B
->A.2.8. </B
->
- Is there email notification and if so, what do you see when you get an
- email?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Email notification is user-configurable. By default, the bug id and
- Summary of the bug report accompany each email notification, along with
- a list of the changes made.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-cclist"
-></A
-><B
->A.2.9. </B
->
- Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-emailapp"
-></A
-><B
->A.2.10. </B
->
- Do users have to have any particular
- type of email application?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla email is sent in plain text, the most compatible mail format
- on the planet.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you decide to use the bugzilla_email integration features
- to allow Bugzilla to record responses to mail with the associated bug,
- you may need to caution your users to set their mailer to "respond
- to messages in the format in which they were sent". For security reasons
- Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
- email into Bugzilla the resulting comment looks downright awful.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-data"
-></A
-><B
->A.2.11. </B
->
- Does Bugzilla allow data to be imported and exported? If I had outsiders
- write up a bug report using a MS Word bug template, could that template be
- imported into "matching" fields? If I wanted to take the results of a query
- and export that data to MS Excel, could I do that?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla can only output buglists as HTML in version 2.16. There
- are other formats available (CSV and RDF) in the newer development
- versions.
- </P
-><P
-> Bugzilla can export bugs using <TT
-CLASS="filename"
->xml.cgi</TT
-> with
- either a bug number or list of bug numbers.
- </P
-><P
-> Currently the only script included with Bugzilla that can import
- data is <TT
-CLASS="filename"
->importxml.pl</TT
-> which is intended to be
- used for importing the data generated by <TT
-CLASS="filename"
->xml.cgi</TT
->
- in association with bug moving. Any other use is left as an
- exercise for the user.
- </P
-><P
-> There are also scripts included in the <TT
-CLASS="filename"
->contrib/</TT
->
- directory for using e-mail to import information into Bugzilla,
- but these scripts are not currently supported and included for
- educational purposes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-l10n"
-></A
-><B
->A.2.12. </B
->
- Has anyone converted Bugzilla to another language to be used in other
- countries? Is it localizable?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. For more information including available translated templates,
- see <A
-HREF="http://www.bugzilla.org/download.html#localizations"
-TARGET="_top"
->http://www.bugzilla.org/download.html#localizations</A
->.
- The admin interfaces are still not included in these translated
- templates and is therefore still English only. Also, there may be
- issues with the charset not being declared. See <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
-TARGET="_top"
->bug 126226</A
->
- for more information.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-reports"
-></A
-><B
->A.2.13. </B
->
- Can a user create and save reports? Can they do this in Word format?
- Excel format?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. No. Not in 2.16.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-searching"
-></A
-><B
->A.2.14. </B
->
- Does Bugzilla have the ability to search by word, phrase, compound
- search?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You have no idea. Bugzilla's query interface, particularly with the
- advanced Boolean operators, is incredibly versatile.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-midair"
-></A
-><B
->A.2.15. </B
->
- Does Bugzilla provide record locking when there is simultaneous access
- to the same bug? Does the second person get a notice that the bug is in use
- or how are they notified?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Bugzilla does not lock records. It provides mid-air collision detection,
- and offers the offending user a choice of options to deal with the conflict.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-backup"
-></A
-><B
->A.2.16. </B
->
- Are there any backup features provided?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- MySQL, the database back-end for Bugzilla, allows hot-backup of data.
- You can find strategies for dealing with backup considerations
- at <A
-HREF="http://www.mysql.com/doc/B/a/Backup.html"
-TARGET="_top"
-> http://www.mysql.com/doc/B/a/Backup.html</A
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-livebackup"
-></A
-><B
->A.2.17. </B
->
- Can users be on the system while a backup is in progress?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Yes. However, commits to the database must wait
- until the tables are unlocked. Bugzilla databases are typically
- very small, and backups routinely take less than a minute.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-maintenance"
-></A
-><B
->A.2.18. </B
->
- What type of human resources are needed to be on staff to install and
- maintain Bugzilla? Specifically, what type of skills does the person need to
- have? I need to find out if we were to go with Bugzilla, what types of
- individuals would we need to hire and how much would that cost vs buying an
- "Out-of-the-Box" solution.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- If Bugzilla is set up correctly from the start, continuing maintenance
- needs are minimal and can be done easily using the web interface.
- </P
-><P
-> Commercial Bug-tracking software typically costs somewhere upwards
- of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
- is available from skilled members of the newsgroup. Simple questions
- are answered there and then.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-installtime"
-></A
-><B
->A.2.19. </B
->
- What time frame are we looking at if we decide to hire people to install
- and maintain the Bugzilla? Is this something that takes hours or weeks to
- install and a couple of hours per week to maintain and customize or is this
- a multi-week install process, plus a full time job for 1 person, 2 people,
- etc?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- It all depends on your level of commitment. Someone with much Bugzilla
- experience can get you up and running in less than a day, and
- your Bugzilla install can run untended for years. If your
- Bugzilla strategy is critical to your business workflow, hire somebody
- with reasonable UNIX or Perl skills to handle your process management and
- bug-tracking maintenance & customization.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-phb-cost"
-></A
-><B
->A.2.20. </B
->
- Is there any licensing fee or other fees for using Bugzilla? Any
- out-of-pocket cost other than the bodies needed as identified above?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- No. MySQL asks, if you find their product valuable, that you purchase
- a support contract from them that suits your needs.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-security"
-></A
->3. Bugzilla Security</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-mysql"
-></A
-><B
->A.3.1. </B
->
- How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the installation section of this guide)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
->this
- makes MySQL as secure as taping a $100 to the floor of a football stadium
- bathroom for safekeeping.</EM
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-knownproblems"
-></A
-><B
->A.3.2. </B
->
- Are there any security problems with Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The Bugzilla code has undergone a reasonably complete security audit,
- and user-facing CGIs run under Perl's taint mode. However,
- it is recommended that you closely examine permissions on your Bugzilla
- installation, and follow the recommended security guidelines found
- in The Bugzilla Guide.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-security-mysqluser"
-></A
-><B
->A.3.3. </B
->
- I've implemented the security fixes mentioned in Chris Yeh's security
- advisory of 5/10/2000 advising not to run MySQL as root, and am running into
- problems with MySQL no longer working correctly.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- This is a common problem, related to running out of file descriptors.
- Simply add "ulimit -n unlimited" to the script which starts
- mysqld.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-email"
-></A
->4. Bugzilla Email</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-nomail"
-></A
-><B
->A.4.1. </B
->
- I have a user who doesn't want to receive any more email from Bugzilla.
- How do I stop it entirely for this user?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The user should be able to set
- this in user email preferences (uncheck all boxes) or you can add
- their email address to the <TT
-CLASS="filename"
->data/nomail</TT
-> file.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-testing"
-></A
-><B
->A.4.2. </B
->
- I'm evaluating/testing Bugzilla, and don't want it to send email to
- anyone but me. How do I do it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
- replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-whine"
-></A
-><B
->A.4.3. </B
->
- I want whineatnews.pl to whine at something more, or other than, only new
- bugs. How do I do it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
- You can find it at <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
-TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
->. This
- patch is against an older version of Bugzilla, so you must apply
- the diffs manually.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-procmail"
-></A
-><B
->A.4.4. </B
->
- I don't like/want to use Procmail to hand mail off to bug_email.pl.
- What alternatives do I have?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can call bug_email.pl directly from your aliases file, with
- an entry like this:
- <A
-NAME="AEN1979"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
- </P
-></BLOCKQUOTE
->
- However, this is fairly nasty and subject to problems; you also
- need to set up your smrsh (sendmail restricted shell) to allow
- it. In a pinch, though, it can work.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-mailif"
-></A
-><B
->A.4.5. </B
->
- How do I set up the email interface to submit/change bugs via email?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- You can find an updated README.mailif file in the contrib/ directory
- of your Bugzilla distribution that walks you through the setup.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-sendmailnow"
-></A
-><B
->A.4.6. </B
->
- Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
- What gives?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- If you are using an alternate Mail Transport Agent (MTA other than
- sendmail), make sure the options given in the "processmail" and other
- scripts for all
- instances of "sendmail" are correct for your MTA.
- </P
-><P
-> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
- If you are using Postfix, you will also need to enable <SPAN
-CLASS="QUOTE"
->"sendmailnow"</SPAN
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-email-nonreceived"
-></A
-><B
->A.4.7. </B
->
- How come email from Bugzilla changes never reaches me?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Double-check that you have not turned off email in your user preferences.
- Confirm that Bugzilla is able to send email by visiting the "Log In"
- link of your Bugzilla installation and clicking the "Email me a password"
- button after entering your email address.
- </P
-><P
-> If you never receive mail from Bugzilla, chances you do not have
- sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
- to, "/usr/lib/sendmail".
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-db"
-></A
->5. Bugzilla Database</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-oracle"
-></A
-><B
->A.5.1. </B
->
- I've heard Bugzilla can be used with Oracle?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
- Red Hat's newer version (based on 2.17.1 and soon to be merged into
- the main distribution) runs on PostgreSQL. At this time we know of
- no recent ports of Bugzilla to Oracle but do intend to support it
- in the future (possibly the 2.20 time-frame).
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-corrupted"
-></A
-><B
->A.5.2. </B
->
- I think my database might be corrupted, or contain invalid entries. What
- do I do?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Run the <SPAN
-CLASS="QUOTE"
->"sanity check"</SPAN
-> utility
- (<TT
-CLASS="filename"
->./sanitycheck.cgi</TT
-> in the
- Bugzilla_home directory) from your web browser to see! If
- it finishes without errors, you're
- <EM
->probably</EM
-> OK. If it doesn't come back
- OK (i.e. any red letters), there are certain things
- Bugzilla can recover from and certain things it can't. If
- it can't auto-recover, I hope you're familiar with
- mysqladmin commands or have installed another way to
- manage your database. Sanity Check, although it is a good
- basic check on your database integrity, by no means is a
- substitute for competent database administration and
- avoiding deletion of data. It is not exhaustive, and was
- created to do a basic check for the most common problems
- in Bugzilla databases.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-manualedit"
-></A
-><B
->A.5.3. </B
->
- I want to manually edit some entries in my database. How?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- There is no facility in Bugzilla itself to do this. It's also generally
- not a smart thing to do if you don't know exactly what you're doing.
- However, if you understand SQL you can use the <B
-CLASS="command"
->mysql</B
->
- command line utility to manually insert, delete and modify table
- information. There are also more intuitive GUI clients available.
- Personal favorites of the Bugzilla team are <A
-HREF="http://www.phpmyadmin.net/"
-TARGET="_top"
->phpMyAdmin</A
-> and <A
-HREF="http://www.mysql.com/downloads/gui-mycc.html"
-TARGET="_top"
->MySQL Control
- Center</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-permissions"
-></A
-><B
->A.5.4. </B
->
- I think I've set up MySQL permissions correctly, but Bugzilla still can't
- connect.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try running MySQL from its binary: "mysqld --skip-grant-tables". This
- will allow you to completely rule out grant tables as the cause of your
- frustration. If this Bugzilla is able to connect at this point then
- you need to check that you have granted proper permission to the user
- password combo defined in <TT
-CLASS="filename"
->localconfig</TT
->.
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Running MySQL with this command line option is very insecure and
- should only be done when not connected to the external network
- as a troubleshooting step.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-db-synchronize"
-></A
-><B
->A.5.5. </B
->
- How do I synchronize bug information among multiple different Bugzilla
- databases?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Well, you can synchronize or you can move bugs. Synchronization will
- only work one way -- you can create a read-only copy of the database
- at one site, and have it regularly updated at intervals from the main
- database.
- </P
-><P
-> MySQL has some synchronization features builtin to the latest releases.
- It would be great if someone looked into the possibilities there
- and provided a report to the newsgroup on how to effectively
- synchronize two Bugzilla installations.
- </P
-><P
-> If you simply need to transfer bugs from one Bugzilla to another,
- checkout the "move.pl" script in the Bugzilla distribution.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-nt"
-></A
->6. Bugzilla and Win32</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-easiest"
-></A
-><B
->A.6.1. </B
->
- What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Remove Windows. Install Linux. Install Bugzilla.
- The boss will never know the difference.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-bundle"
-></A
-><B
->A.6.2. </B
->
- Is there a "Bundle::Bugzilla" equivalent for Win32?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
- installation on UNIX systems. If someone can volunteer to
- create a suitable PPM bundle for Win32, it would be appreciated.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-mappings"
-></A
-><B
->A.6.3. </B
->
- CGI's are failing with a "something.cgi is not a valid Windows NT
- application" error. Why?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Depending on what Web server you are using, you will have to configure
- the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
- adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the
- executable.
- </P
-><P
-> Microsoft has some advice on this matter, as well:
- <A
-NAME="AEN2055"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> "Set application mappings. In the ISM, map the extension for the script
- file(s) to the executable for the script interpreter. For example, you might
- map the extension .py to Python.exe, the executable for the Python script
- interpreter. Note For the ActiveState Perl script interpreter, the extension
- .pl is associated with PerlIS.dll by default. If you want to change the
- association of .pl to perl.exe, you need to change the application mapping.
- In the mapping, you must add two percent (%) characters to the end of the
- pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s"
- </P
-></BLOCKQUOTE
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-nt-dbi"
-></A
-><B
->A.6.4. </B
->
- I'm having trouble with the perl modules for NT not being able to talk to
- to the database.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Your modules may be outdated or inaccurate. Try:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Hitting http://www.activestate.com/ActivePerl
- </P
-></LI
-><LI
-><P
-> Download ActivePerl
- </P
-></LI
-><LI
-><P
-> Go to your prompt
- </P
-></LI
-><LI
-><P
-> Type 'ppm'
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="prompt"
->PPM></TT
-> <B
-CLASS="command"
->install DBI DBD-mysql GD</B
->
- </P
-></LI
-></OL
->
- I reckon TimeDate and Data::Dumper come with the activeperl. You can check
- the ActiveState site for packages for installation through PPM.
- <A
-HREF=" http://www.activestate.com/Packages/"
-TARGET="_top"
-> http://www.activestate.com/Packages/</A
->
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-use"
-></A
->7. Bugzilla Usage</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-changeaddress"
-></A
-><B
->A.7.1. </B
->
- How do I change my user name (email address) in Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- New in 2.16 - go to the Account section of the Preferences. You will
- be emailed at both addresses for confirmation.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-query"
-></A
-><B
->A.7.2. </B
->
- The query page is very confusing. Isn't there a simpler way to query?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The interface was simplified by a UI designer for 2.16. Further
- suggestions for improvement are welcome, but we won't sacrifice power for
- simplicity.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-accept"
-></A
-><B
->A.7.3. </B
->
- I'm confused by the behavior of the "accept" button in the Show Bug form.
- Why doesn't it assign the bug to me when I accept it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The current behavior is acceptable to bugzilla.mozilla.org and most
- users. You have your choice of patches
- to change this behavior, however.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
-TARGET="_top"
-> Add a "and accept bug" radio button</A
-></TD
-></TR
-><TR
-><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
-TARGET="_top"
-> "Accept" button automatically assigns to you</A
-></TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- Note that these patches are somewhat dated. You will need to apply
- them manually.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-attachment"
-></A
-><B
->A.7.4. </B
->
- I can't upload anything into the database via the "Create Attachment"
- link. What am I doing wrong?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The most likely cause is a very old browser or a browser that is
- incompatible with file upload via POST. Download the latest Netscape,
- Microsoft, or Mozilla browser to handle uploads correctly.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-keyword"
-></A
-><B
->A.7.5. </B
->
- How do I change a keyword in Bugzilla, once some bugs are using it?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- In the Bugzilla administrator UI, edit the keyword and it will let you
- replace the old keyword name with a new one. This will cause a problem
- with the keyword cache. Run sanitycheck.cgi to fix it.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-use-close"
-></A
-><B
->A.7.6. </B
->
- Why can't I close bugs from the "Change Several Bugs at Once" page?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
- You <EM
->can</EM
-> mass-CLOSE bugs from the change several
- bugs at once page. <EM
->but</EM
->, every bug listed on the
- page has to be in VERIFIED state before the control to do it will show
- up on the form. You can also mass-VERIFY, but every bug listed has to be
- RESOLVED in order for the control to show up on the form. The logic
- behind this is that if you pick one of the bugs that's not VERIFIED and
- try to CLOSE it, the bug change will fail miserably (thus killing any
- changes in the list after it while doing the bulk change) so it doesn't
- even give you the choice.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-hacking"
-></A
->8. Bugzilla Hacking</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-bugzillabugs"
-></A
-><B
->A.8.1. </B
->
- What bugs are in Bugzilla right now?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"
-TARGET="_top"
-> this link</A
-> to view current bugs or requests for
- enhancement for Bugzilla.
- </P
-><P
-> You can view bugs marked for 2.18 release
- <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"
-TARGET="_top"
->here</A
->.
- This list includes bugs for the 2.18 release that have already
- been fixed and checked into CVS. Please consult the
- <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
-> Bugzilla Project Page</A
-> for details on how to
- check current sources out of CVS so you can have these
- bug fixes early!
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-priority"
-></A
-><B
->A.8.2. </B
->
- How can I change the default priority to a null value? For instance, have the default
- priority be "---" instead of "P2"?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- This is well-documented here: <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
-TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
->. Ultimately, it's as easy
- as adding the "---" priority field to your localconfig file in the appropriate area,
- re-running checksetup.pl, and then changing the default priority in your browser using
- "editparams.cgi".
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="faq-hacking-patches"
-></A
-><B
->A.8.3. </B
->
- What's the best way to submit patches? What guidelines should I follow?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Enter a bug into bugzilla.mozilla.org for the <SPAN
-CLASS="QUOTE"
->"<A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
-TARGET="_top"
->Bugzilla</A
->"</SPAN
->
- product.
- </P
-></LI
-><LI
-><P
-> Upload your patch as a unified diff (having used "diff -u" against
- the <EM
->current sources</EM
-> checked out of CVS),
- or new source file by clicking
- "Create a new attachment" link on the bug page you've just created, and
- include any descriptions of database changes you may make, into the bug
- ID you submitted in step #1. Be sure and click the "Patch" checkbox
- to indicate the text you are sending is a patch!
- </P
-></LI
-><LI
-><P
-> Announce your patch and the associated URL
- (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
- the newsgroup (netscape.public.mozilla.webtools). You'll get a really
- good, fairly immediate reaction to the implications of your patch,
- which will also give us an idea how well-received the change would
- be.
- </P
-></LI
-><LI
-><P
-> If it passes muster with minimal modification, the person to whom
- the bug is assigned in Bugzilla is responsible for seeing the patch
- is checked into CVS.
- </P
-></LI
-><LI
-><P
-> Bask in the glory of the fact that you helped write the most successful
- open-source bug-tracking software on the planet :)
- </P
-></LI
-></OL
-></P
-></DIV
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The Bugzilla Database</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->PREAMBLE</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="NEXT"
-TITLE="APPLICABILITY AND DEFINITIONS"
-HREF="gfdl-1.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-0"
-></A
->0. PREAMBLE</H1
-><P
->The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone the
- effective freedom to copy and redistribute it, with or without modifying
- it, either commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit for their
- work, while not being considered responsible for modifications made by
- others.</P
-><P
->This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft license
- designed for free software.</P
-><P
->We have designed this License in order to use it for manuals for
- free software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or whether
- it is published as a printed book. We recommend this License principally
- for works whose purpose is instruction or reference.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->GNU Free Documentation License</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->APPLICABILITY AND DEFINITIONS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="PREAMBLE"
-HREF="gfdl-0.html"><LINK
-REL="NEXT"
-TITLE="VERBATIM COPYING"
-HREF="gfdl-2.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-1"
-></A
->1. APPLICABILITY AND DEFINITIONS</H1
-><P
->This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed under
- the terms of this License. The "Document", below, refers to any such
- manual or work. Any member of the public is a licensee, and is addressed
- as "you".</P
-><P
->A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.</P
-><P
->A "Secondary Section" is a named appendix or a front-matter section
- of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall subject
- (or to related matters) and contains nothing that could fall directly
- within that overall subject. (For example, if the Document is in part a
- textbook of mathematics, a Secondary Section may not explain any
- mathematics.) The relationship could be a matter of historical connection
- with the subject or with related matters, or of legal, commercial,
- philosophical, ethical or political position regarding them.</P
-><P
->The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in the
- notice that says that the Document is released under this License.</P
-><P
->The "Cover Texts" are certain short passages of text that are
- listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
- that the Document is released under this License.</P
-><P
->A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the general
- public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or for
- automatic translation to a variety of formats suitable for input to text
- formatters. A copy made in an otherwise Transparent file format whose
- markup has been designed to thwart or discourage subsequent modification
- by readers is not Transparent. A copy that is not "Transparent" is called
- "Opaque".</P
-><P
->Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML or
- XML using a publicly available DTD, and standard-conforming simple HTML
- designed for human modification. Opaque formats include PostScript, PDF,
- proprietary formats that can be read and edited only by proprietary word
- processors, SGML or XML for which the DTD and/or processing tools are not
- generally available, and the machine-generated HTML produced by some word
- processors for output purposes only.</P
-><P
->The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in formats
- which do not have any title page as such, "Title Page" means the text
- near the most prominent appearance of the work's title, preceding the
- beginning of the body of the text.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->PREAMBLE</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->VERBATIM COPYING</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->FUTURE REVISIONS OF THIS LICENSE</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="TERMINATION"
-HREF="gfdl-9.html"><LINK
-REL="NEXT"
-TITLE="How to use this License for your documents"
-HREF="gfdl-howto.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-10"
-></A
->10. FUTURE REVISIONS OF THIS LICENSE</H1
-><P
->The Free Software Foundation may publish new, revised versions of
- the GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- <A
-HREF="http://www.gnu.org/copyleft/"
-TARGET="_top"
-> http://www.gnu.org/copyleft/</A
->
-
- .</P
-><P
->Each version of the License is given a distinguishing version
- number. If the Document specifies that a particular numbered version of
- this License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or of
- any later version that has been published (not as a draft) by the Free
- Software Foundation. If the Document does not specify a version number of
- this License, you may choose any version ever published (not as a draft)
- by the Free Software Foundation.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->TERMINATION</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How to use this License for your documents</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->VERBATIM COPYING</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="APPLICABILITY AND DEFINITIONS"
-HREF="gfdl-1.html"><LINK
-REL="NEXT"
-TITLE="COPYING IN QUANTITY"
-HREF="gfdl-3.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-2"
-></A
->2. VERBATIM COPYING</H1
-><P
->You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies to
- the Document are reproduced in all copies, and that you add no other
- conditions whatsoever to those of this License. You may not use technical
- measures to obstruct or control the reading or further copying of the
- copies you make or distribute. However, you may accept compensation in
- exchange for copies. If you distribute a large enough number of copies
- you must also follow the conditions in section 3.</P
-><P
->You may also lend copies, under the same conditions stated above,
- and you may publicly display copies.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COPYING IN QUANTITY</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->COPYING IN QUANTITY</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="VERBATIM COPYING"
-HREF="gfdl-2.html"><LINK
-REL="NEXT"
-TITLE="MODIFICATIONS"
-HREF="gfdl-4.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-3"
-></A
->3. COPYING IN QUANTITY</H1
-><P
->If you publish printed copies of the Document numbering more than
- 100, and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all these
- Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
- on the back cover. Both covers must also clearly and legibly identify you
- as the publisher of these copies. The front cover must present the full
- title with all words of the title equally prominent and visible. You may
- add other material on the covers in addition. Copying with changes
- limited to the covers, as long as they preserve the title of the Document
- and satisfy these conditions, can be treated as verbatim copying in other
- respects.</P
-><P
->If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit reasonably)
- on the actual cover, and continue the rest onto adjacent pages.</P
-><P
->If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with each
- Opaque copy a publicly-accessible computer-network location containing a
- complete Transparent copy of the Document, free of added material, which
- the general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location until
- at least one year after the last time you distribute an Opaque copy
- (directly or through your agents or retailers) of that edition to the
- public.</P
-><P
->It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->VERBATIM COPYING</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->MODIFICATIONS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->MODIFICATIONS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COPYING IN QUANTITY"
-HREF="gfdl-3.html"><LINK
-REL="NEXT"
-TITLE="COMBINING DOCUMENTS"
-HREF="gfdl-5.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-4"
-></A
->4. MODIFICATIONS</H1
-><P
->You may copy and distribute a Modified Version of the Document
- under the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution and
- modification of the Modified Version to whoever possesses a copy of it.
- In addition, you must do these things in the Modified Version:</P
-><P
-></P
-><OL
-TYPE="A"
-><LI
-><P
->Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the History
- section of the Document). You may use the same title as a previous
- version if the original publisher of that version gives
- permission.</P
-></LI
-><LI
-><P
->List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has less
- than five).</P
-></LI
-><LI
-><P
->State on the Title page the name of the publisher of the
- Modified Version, as the publisher.</P
-></LI
-><LI
-><P
->Preserve all the copyright notices of the Document.</P
-></LI
-><LI
-><P
->Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.</P
-></LI
-><LI
-><P
->Include, immediately after the copyright notices, a license
- notice giving the public permission to use the Modified Version under
- the terms of this License, in the form shown in the Addendum
- below.</P
-></LI
-><LI
-><P
->Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.</P
-></LI
-><LI
-><P
->Include an unaltered copy of this License.</P
-></LI
-><LI
-><P
->Preserve the section entitled "History", and its title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.</P
-></LI
-><LI
-><P
->Preserve the network location, if any, given in the Document
- for public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions it
- was based on. These may be placed in the "History" section. You may
- omit a network location for a work that was published at least four
- years before the Document itself, or if the original publisher of the
- version it refers to gives permission.</P
-></LI
-><LI
-><P
->In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements and/or
- dedications given therein.</P
-></LI
-><LI
-><P
->Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.</P
-></LI
-><LI
-><P
->Delete any section entitled "Endorsements". Such a section may
- not be included in the Modified Version.</P
-></LI
-><LI
-><P
->Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.</P
-></LI
-></OL
-><P
->If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all of
- these sections as invariant. To do this, add their titles to the list of
- Invariant Sections in the Modified Version's license notice. These titles
- must be distinct from any other section titles.</P
-><P
->You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various parties--for
- example, statements of peer review or that the text has been approved by
- an organization as the authoritative definition of a standard.</P
-><P
->You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of the
- list of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or through
- arrangements made by) any one entity. If the Document already includes a
- cover text for the same cover, previously added by you or by arrangement
- made by the same entity you are acting on behalf of, you may not add
- another; but you may replace the old one, on explicit permission from the
- previous publisher that added the old one.</P
-><P
->The author(s) and publisher(s) of the Document do not by this
- License give permission to use their names for publicity for or to assert
- or imply endorsement of any Modified Version.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COPYING IN QUANTITY</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COMBINING DOCUMENTS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->COMBINING DOCUMENTS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="MODIFICATIONS"
-HREF="gfdl-4.html"><LINK
-REL="NEXT"
-TITLE="COLLECTIONS OF DOCUMENTS"
-HREF="gfdl-6.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-5"
-></A
->5. COMBINING DOCUMENTS</H1
-><P
->You may combine the Document with other documents released under
- this License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and list
- them all as Invariant Sections of your combined work in its license
- notice.</P
-><P
->The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single copy.
- If there are multiple Invariant Sections with the same name but different
- contents, make the title of each such section unique by adding at the end
- of it, in parentheses, the name of the original author or publisher of
- that section if known, or else a unique number. Make the same adjustment
- to the section titles in the list of Invariant Sections in the license
- notice of the combined work.</P
-><P
->In the combination, you must combine any sections entitled
- "History" in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements", and
- any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MODIFICATIONS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->COLLECTIONS OF DOCUMENTS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COMBINING DOCUMENTS"
-HREF="gfdl-5.html"><LINK
-REL="NEXT"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
-HREF="gfdl-7.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-6"
-></A
->6. COLLECTIONS OF DOCUMENTS</H1
-><P
->You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual copies
- of this License in the various documents with a single copy that is
- included in the collection, provided that you follow the rules of this
- License for verbatim copying of each of the documents in all other
- respects.</P
-><P
->You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a copy
- of this License into the extracted document, and follow this License in
- all other respects regarding verbatim copying of that document.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COMBINING DOCUMENTS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->AGGREGATION WITH INDEPENDENT WORKS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COLLECTIONS OF DOCUMENTS"
-HREF="gfdl-6.html"><LINK
-REL="NEXT"
-TITLE="TRANSLATION"
-HREF="gfdl-8.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-7"
-></A
->7. AGGREGATION WITH INDEPENDENT WORKS</H1
-><P
->A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of a
- storage or distribution medium, does not as a whole count as a Modified
- Version of the Document, provided no compilation copyright is claimed for
- the compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they are
- not themselves derivative works of the Document.</P
-><P
->If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter of
- the entire aggregate, the Document's Cover Texts may be placed on covers
- that surround only the Document within the aggregate. Otherwise they must
- appear on covers around the whole aggregate.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->TRANSLATION</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->TRANSLATION</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
-HREF="gfdl-7.html"><LINK
-REL="NEXT"
-TITLE="TERMINATION"
-HREF="gfdl-9.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-8"
-></A
->8. TRANSLATION</H1
-><P
->Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include translations
- of some or all Invariant Sections in addition to the original versions of
- these Invariant Sections. You may include a translation of this License
- provided that you also include the original English version of this
- License. In case of a disagreement between the translation and the
- original English version of this License, the original English version
- will prevail.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->TERMINATION</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->TERMINATION</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="TRANSLATION"
-HREF="gfdl-8.html"><LINK
-REL="NEXT"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
-HREF="gfdl-10.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-9"
-></A
->9. TERMINATION</H1
-><P
->You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt to
- copy, modify, sublicense or distribute the Document is void, and will
- automatically terminate your rights under this License. However, parties
- who have received copies, or rights, from you under this License will not
- have their licenses terminated so long as such parties remain in full
- compliance.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->TRANSLATION</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->How to use this License for your documents</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
-HREF="gfdl-10.html"><LINK
-REL="NEXT"
-TITLE="Glossary"
-HREF="glossary.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="glossary.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="gfdl-howto"
-></A
->How to use this License for your documents</H1
-><P
->To use this License in a document you have written, include a copy
- of the License in the document and put the following copyright and
- license notices just after the title page:</P
-><A
-NAME="AEN2380"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU Free
- Documentation License, Version 1.1 or any later version published by
- the Free Software Foundation; with the Invariant Sections being LIST
- THEIR TITLES, with the Front-Cover Texts being LIST, and with the
- Back-Cover Texts being LIST. A copy of the license is included in the
- section entitled "GNU Free Documentation License".</P
-></BLOCKQUOTE
-><P
->If you have no Invariant Sections, write "with no Invariant
- Sections" instead of saying which ones are invariant. If you have no
- Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
- Texts being LIST"; likewise for Back-Cover Texts.</P
-><P
->If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of free
- software license, such as the GNU General Public License, to permit their
- use in free software.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="glossary.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Glossary</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->GNU Free Documentation License</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="SourceForge"
-HREF="variant-sourceforge.html"><LINK
-REL="NEXT"
-TITLE="PREAMBLE"
-HREF="gfdl-0.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="gfdl"
-></A
->Appendix E. GNU Free Documentation License</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->0. <A
-HREF="gfdl-0.html"
->PREAMBLE</A
-></DT
-><DT
->1. <A
-HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
-></DT
-><DT
->2. <A
-HREF="gfdl-2.html"
->VERBATIM COPYING</A
-></DT
-><DT
->3. <A
-HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
-></DT
-><DT
->4. <A
-HREF="gfdl-4.html"
->MODIFICATIONS</A
-></DT
-><DT
->5. <A
-HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
-></DT
-><DT
->6. <A
-HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
-></DT
-><DT
->7. <A
-HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
-></DT
-><DT
->8. <A
-HREF="gfdl-8.html"
->TRANSLATION</A
-></DT
-><DT
->9. <A
-HREF="gfdl-9.html"
->TERMINATION</A
-></DT
-><DT
->10. <A
-HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
-></DT
-><DT
-><A
-HREF="gfdl-howto.html"
->How to use this License for your documents</A
-></DT
-></DL
-></DIV
-><P
->Version 1.1, March 2000</P
-><A
-NAME="AEN2290"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
- distribute verbatim copies of this license document, but changing it is
- not allowed.</P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->SourceForge</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->PREAMBLE</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Glossary</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="How to use this License for your documents"
-HREF="gfdl-howto.html"></HEAD
-><BODY
-CLASS="glossary"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-> </TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="GLOSSARY"
-><H1
-><A
-NAME="glossary"
-></A
->Glossary</H1
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="AEN2385"
-></A
->0-9, high ascii</H1
-><DL
-><DT
-><B
->.htaccess</B
-></DT
-><DD
-><P
->Apache web server, and other NCSA-compliant web servers,
- observe the convention of using files in directories called
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- to restrict access to certain files. In Bugzilla, they are used
- to keep secret files which would otherwise
- compromise your installation - e.g. the
- <TT
-CLASS="filename"
->localconfig</TT
->
- file contains the password to your database.
- curious.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-a"
-></A
->A</H1
-><DL
-><DT
-><B
->Apache</B
-></DT
-><DD
-><P
->In this context, Apache is the web server most commonly used
- for serving up
- <I
-CLASS="glossterm"
->Bugzilla</I
->
-
- pages. Contrary to popular belief, the apache web server has nothing
- to do with the ancient and noble Native American tribe, but instead
- derived its name from the fact that it was
- <SPAN
-CLASS="QUOTE"
->"a patchy"</SPAN
->
-
- version of the original
- <SPAN
-CLASS="acronym"
->NCSA</SPAN
->
-
- world-wide-web server.</P
-><P
-></P
-><DIV
-CLASS="variablelist"
-><P
-><B
->Useful Directives when configuring Bugzilla</B
-></P
-><DL
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
-TARGET="_top"
->AddHandler</A
-></TT
-></DT
-><DD
-><P
->Tell Apache that it's OK to run CGI scripts.</P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
-TARGET="_top"
->AllowOverride</A
-></TT
->, <TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
-TARGET="_top"
->Options</A
-></TT
-></DT
-><DD
-><P
->These directives are used to tell Apache many things about
- the directory they apply to. For Bugzilla's purposes, we need
- them to allow script execution and <TT
-CLASS="filename"
->.htaccess</TT
->
- overrides.
- </P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
-TARGET="_top"
->DirectoryIndex</A
-></TT
-></DT
-><DD
-><P
->Used to tell Apache what files are indexes. If you can
- not add <TT
-CLASS="filename"
->index.cgi</TT
-> to the list of valid files,
- you'll need to set <TT
-CLASS="computeroutput"
->$index_html</TT
-> to
- 1 in <TT
-CLASS="filename"
->localconfig</TT
-> so
- <B
-CLASS="command"
->./checksetup.pl</B
-> will create an
- <TT
-CLASS="filename"
->index.html</TT
-> that redirects to
- <TT
-CLASS="filename"
->index.cgi</TT
->.
- </P
-></DD
-><DT
-><TT
-CLASS="computeroutput"
-><A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
-TARGET="_top"
->ScriptInterpreterSource</A
-></TT
-></DT
-><DD
-><P
->Used when running Apache on windows so the shebang line
- doesn't have to be changed in every Bugzilla script.
- </P
-></DD
-></DL
-></DIV
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-b"
-></A
->B</H1
-><DL
-><DT
-><B
->Bug</B
-></DT
-><DD
-><P
->A
- <SPAN
-CLASS="QUOTE"
->"bug"</SPAN
->
-
- in Bugzilla refers to an issue entered into the database which has an
- associated number, assignments, comments, etc. Some also refer to a
- <SPAN
-CLASS="QUOTE"
->"tickets"</SPAN
->
- or
- <SPAN
-CLASS="QUOTE"
->"issues"</SPAN
->;
- in the context of Bugzilla, they are synonymous.</P
-></DD
-><DT
-><B
->Bug Number</B
-></DT
-><DD
-><P
->Each Bugzilla bug is assigned a number that uniquely identifies
- that bug. The bug associated with a bug number can be pulled up via a
- query, or easily from the very front page by typing the number in the
- "Find" box.</P
-></DD
-><DT
-><A
-NAME="gloss-bugzilla"
-></A
-><B
->Bugzilla</B
-></DT
-><DD
-><P
->Bugzilla is the world-leading free software bug tracking system.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-c"
-></A
->C</H1
-><DL
-><DT
-><A
-NAME="gloss-cgi"
-></A
-><B
->Common Gateway Interface</B
-></DT
-> (CGI)<DD
-><P
-><SPAN
-CLASS="acronym"
->CGI</SPAN
-> is an acronym for Common Gateway Interface.
- This is a standard for interfacing an external application with a web
- server. Bugzilla is an example of a <SPAN
-CLASS="acronym"
->CGI</SPAN
-> application.
- </P
-></DD
-><DT
-><A
-NAME="gloss-component"
-></A
-><B
->Component</B
-></DT
-><DD
-><P
->A Component is a subsection of a Product. It should be a narrow
- category, tailored to your organization. All Products must contain at
- least one Component (and, as a matter of fact, creating a Product
- with no Components will create an error in Bugzilla).</P
-></DD
-><DT
-><A
-NAME="gloss-cpan"
-></A
-><B
-> <SPAN
-CLASS="acronym"
->CPAN</SPAN
->
- </B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="acronym"
->CPAN</SPAN
->
-
- stands for the
- <SPAN
-CLASS="QUOTE"
->"Comprehensive Perl Archive Network"</SPAN
->.
- CPAN maintains a large number of extremely useful
- <I
-CLASS="glossterm"
->Perl</I
->
- modules - encapsulated chunks of code for performing a
- particular task.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-d"
-></A
->D</H1
-><DL
-><DT
-><B
->daemon</B
-></DT
-><DD
-><P
->A daemon is a computer program which runs in the background. In
- general, most daemons are started at boot time via System V init
- scripts, or through RC scripts on BSD-based systems.
- <I
-CLASS="glossterm"
->mysqld</I
->,
- the MySQL server, and
- <I
-CLASS="glossterm"
->apache</I
->,
- a web server, are generally run as daemons.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-g"
-></A
->G</H1
-><DL
-><DT
-><B
->Groups</B
-></DT
-><DD
-><P
->The word
- <SPAN
-CLASS="QUOTE"
->"Groups"</SPAN
->
-
- has a very special meaning to Bugzilla. Bugzilla's main security
- mechanism comes by placing users in groups, and assigning those
- groups certain privileges to view bugs in particular
- <I
-CLASS="glossterm"
->Products</I
->
- in the
- <I
-CLASS="glossterm"
->Bugzilla</I
->
- database.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-m"
-></A
->M</H1
-><DL
-><DT
-><A
-NAME="gloss-mta"
-></A
-><B
->Message Transport Agent</B
-></DT
-> (MTA)<DD
-><P
->A Message Transport Agent is used to control the flow of email
- on a system. Many unix based systems use
- <A
-HREF="http://www.sendmail.org"
-TARGET="_top"
->sendmail</A
-> which is what
- Bugzilla expects to find by default at <TT
-CLASS="filename"
->/usr/sbin/sendmail</TT
->.
- Many other MTA's will work, but they all require that the
- <TT
-CLASS="option"
->sendmailnow</TT
-> param be set to <TT
-CLASS="literal"
->on</TT
->.
- </P
-></DD
-><DT
-><A
-NAME="gloss-mysql"
-></A
-><B
->MySQL</B
-></DT
-><DD
-><P
->MySQL is currently the required
- <A
-HREF="glossary.html#gloss-rdbms"
-><I
-CLASS="glossterm"
->RDBMS</I
-></A
-> for Bugzilla. MySQL
- can be downloaded from <A
-HREF="http://www.mysql.com"
-TARGET="_top"
->http://www.mysql.com</A
->. While you
- should familiarize yourself with all of the documentation, some high
- points are:
- </P
-><P
-></P
-><UL
-><LI
-><P
-><A
-HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
-TARGET="_top"
->MySQL
- Privilege System</A
-> - Much more detailed information about
- the suggestions in <A
-HREF="security.html#security-mysql"
->Section 5.6.2</A
->.
- </P
-></LI
-></UL
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-p"
-></A
->P</H1
-><DL
-><DT
-><B
->Product</B
-></DT
-><DD
-><P
->A Product is a broad category of types of bugs, normally
- representing a single piece of software or entity. In general,
- there are several Components to a Product. A Product may define a
- group (used for security) for all bugs entered into
- its Components.</P
-></DD
-><DT
-><B
->Perl</B
-></DT
-><DD
-><P
->First written by Larry Wall, Perl is a remarkable program
- language. It has the benefits of the flexibility of an interpreted
- scripting language (such as shell script), combined with the speed
- and power of a compiled language, such as C.
- <I
-CLASS="glossterm"
->Bugzilla</I
->
-
- is maintained in Perl.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-q"
-></A
->Q</H1
-><DL
-><DT
-><B
->QA</B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="QUOTE"
->"QA"</SPAN
->,
- <SPAN
-CLASS="QUOTE"
->"Q/A"</SPAN
->, and
- <SPAN
-CLASS="QUOTE"
->"Q.A."</SPAN
->
- are short for
- <SPAN
-CLASS="QUOTE"
->"Quality Assurance"</SPAN
->.
- In most large software development organizations, there is a team
- devoted to ensuring the product meets minimum standards before
- shipping. This team will also generally want to track the progress of
- bugs over their life cycle, thus the need for the
- <SPAN
-CLASS="QUOTE"
->"QA Contact"</SPAN
->
-
- field in a bug.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-r"
-></A
->R</H1
-><DL
-><DT
-><A
-NAME="gloss-rdbms"
-></A
-><B
->Relational DataBase Managment System</B
-></DT
-> (RDBMS)<DD
-><P
->A relational database management system is a database system
- that stores information in tables that are related to each other.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-s"
-></A
->S</H1
-><DL
-><DT
-><B
-> <SPAN
-CLASS="acronym"
->SGML</SPAN
->
- </B
-></DT
-><DD
-><P
-> <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- stands for
- <SPAN
-CLASS="QUOTE"
->"Standard Generalized Markup Language"</SPAN
->.
- Created in the 1980's to provide an extensible means to maintain
- documentation based upon content instead of presentation,
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- has withstood the test of time as a robust, powerful language.
- <I
-CLASS="glossterm"
-> <SPAN
-CLASS="acronym"
->XML</SPAN
->
- </I
->
-
- is the
- <SPAN
-CLASS="QUOTE"
->"baby brother"</SPAN
->
-
- of SGML; any valid
- <SPAN
-CLASS="acronym"
->XML</SPAN
->
-
- document it, by definition, a valid
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->
-
- document. The document you are reading is written and maintained in
- <SPAN
-CLASS="acronym"
->SGML</SPAN
->,
- and is also valid
- <SPAN
-CLASS="acronym"
->XML</SPAN
->
-
- if you modify the Document Type Definition.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-t"
-></A
->T</H1
-><DL
-><DT
-><A
-NAME="gloss-target-milestone"
-></A
-><B
->Target Milestone</B
-></DT
-><DD
-><P
->Target Milestones are Product goals. They are configurable on a
- per-Product basis. Most software development houses have a concept of
-
- <SPAN
-CLASS="QUOTE"
->"milestones"</SPAN
->
-
- where the people funding a project expect certain functionality on
- certain dates. Bugzilla facilitates meeting these milestones by
- giving you the ability to declare by which milestone a bug will be
- fixed, or an enhancement will be implemented.</P
-></DD
-><DT
-><A
-NAME="gloss-tcl"
-></A
-><B
->Tool Command Language</B
-></DT
-> (TCL)<DD
-><P
->TCL is an open source scripting language available for Windows,
- Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
- never released. The first release of Bugzilla was 2.0, which was when
- it was ported to perl.
- </P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-z"
-></A
->Z</H1
-><DL
-><DT
-><A
-NAME="gloss-zarro"
-></A
-><B
->Zarro Boogs Found</B
-></DT
-><DD
-><P
->This is just a goofy way of saying that there were no bugs
- found matching your query. When asked to explain this message,
- Terry had the following to say:
- </P
-><A
-NAME="AEN2579"
-></A
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
-><P
->I've been asked to explain this ... way back when, when
- Netscape released version 4.0 of its browser, we had a release
- party. Naturally, there had been a big push to try and fix every
- known bug before the release. Naturally, that hadn't actually
- happened. (This is not unique to Netscape or to 4.0; the same thing
- has happened with every software project I've ever seen.) Anyway,
- at the release party, T-shirts were handed out that said something
- like "Netscape 4.0: Zarro Boogs". Just like the software, the
- T-shirt had no known bugs. Uh-huh.
- </P
-><P
->So, when you query for a list of bugs, and it gets no results,
- you can think of this as a friendly reminder. Of *course* there are
- bugs matching your query, they just aren't in the bugsystem yet...
- </P
-></TD
-><TD
-WIDTH="10%"
-VALIGN="TOP"
-> </TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Terry Weissman</SPAN
-></TD
-><TD
-WIDTH="10%"
-> </TD
-></TR
-></TABLE
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->How to use this License for your documents</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Groups and Group Security</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Voting"
-HREF="voting.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla Security"
-HREF="security.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="voting.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="security.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="groups"
-></A
->5.5. Groups and Group Security</H1
-><P
->Groups allow the administrator
- to isolate bugs or products that should only be seen by certain people.
- There are two types of group - Generic Groups, and Product-Based Groups.
- </P
-><P
-> Product-Based Groups are matched with products, and allow you to restrict
- access to bugs on a per-product basis. They are enabled using the
- usebuggroups Param. Turning on the usebuggroupsentry
- Param will mean bugs automatically get added to their product group when
- filed.
- </P
-><P
-> Generic Groups have no special relationship to products;
- you create them, and put bugs in them
- as required. One example of the use of Generic Groups
- is Mozilla's "Security" group,
- into which security-sensitive bugs are placed until fixed. Only the
- Mozilla Security Team are members of this group.
- </P
-><P
->To create Generic Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select the "groups"
- link in the footer.</P
-></LI
-><LI
-><P
->Take a moment to understand the instructions on the "Edit
- Groups" screen, then select the "Add Group" link.</P
-></LI
-><LI
-><P
->Fill out the "New Name", "New Description", and
- "New User RegExp" fields. "New User RegExp" allows you to automatically
- place all users who fulfill the Regular Expression into the new group.
- When you have finished, click "Add".</P
-></LI
-></OL
-><P
->To use Product-Based Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen.</P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->XXX is this still true?
- "usebuggroupsentry" has the capacity to prevent the
- administrative user from directly altering bugs because of
- conflicting group permissions. If you plan on using
- "usebuggroupsentry", you should plan on restricting
- administrative account usage to administrative duties only. In
- other words, manage bugs with an unpriveleged user account, and
- manage users, groups, Products, etc. with the administrative
- account.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->In future, when you create a Product, a matching group will be
- automatically created. If you need to add a Product Group to
- a Product which was created before you turned on usebuggroups,
- then simply create a new group, as outlined above, with the
- same name as the Product.</P
-></LI
-></OL
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Bugzilla currently has a limit of 64 groups per installation. If
- you have more than about 50 products, you should consider
- running multiple Bugzillas. Ask in the newsgroup for other
- suggestions for working around this restriction.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
-> Note that group permissions are such that you need to be a member
- of <EM
->all</EM
-> the groups a bug is in, for whatever
- reason, to see that bug.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="voting.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="security.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Voting</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla Security</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Hints and Tips</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="How do I use Bugzilla?"
-HREF="how.html"><LINK
-REL="NEXT"
-TITLE="User Preferences"
-HREF="userpreferences.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="how.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="userpreferences.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="hintsandtips"
-></A
->3.2. Hints and Tips</H1
-><P
->This section distills some Bugzilla tips and best practices
- that have been developed.</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN372"
-></A
->3.2.1. Autolinkification</H2
-><P
->Bugzilla comments are plain text - so posting HTML will result
- in literal HTML tags rather than being interpreted by a browser.
- However, Bugzilla will automatically make hyperlinks out of certain
- sorts of text in comments. For example, the text
- http://www.bugzilla.org will be turned into
- <A
-HREF="http://www.bugzilla.org"
-TARGET="_top"
->http://www.bugzilla.org</A
->.
- Other strings which get linkified in the obvious manner are:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->bug 12345</TD
-></TR
-><TR
-><TD
->bug 23456, comment 53</TD
-></TR
-><TR
-><TD
->attachment 4321</TD
-></TR
-><TR
-><TD
->mailto:george@example.com</TD
-></TR
-><TR
-><TD
->george@example.com</TD
-></TR
-><TR
-><TD
->ftp://ftp.mozilla.org</TD
-></TR
-><TR
-><TD
->Most other sorts of URL</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->A corollary here is that if you type a bug number in a comment,
- you should put the word "bug" before it, so it gets autolinkified
- for the convenience of others.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="quicksearch"
-></A
->3.2.2. Quicksearch</H2
-><P
->Quicksearch is a single-text-box query tool which uses
- metacharacters to indicate what is to be searched. For example, typing
- "<TT
-CLASS="filename"
->foo|bar</TT
->"
- into Quicksearch would search for "foo" or "bar" in the
- summary and status whiteboard of a bug; adding
- "<TT
-CLASS="filename"
->:BazProduct</TT
->" would
- search only in that product.
- </P
-><P
->You'll find the Quicksearch box on Bugzilla's
- front page, along with a
- <A
-HREF="../../quicksearch.html"
-TARGET="_top"
->Help</A
->
- link which details how to use it.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="commenting"
-></A
->3.2.3. Comments</H2
-><P
->If you are changing the fields on a bug, only comment if
- either you have something pertinent to say, or Bugzilla requires it.
- Otherwise, you may spam people unnecessarily with bug mail.
- To take an example: a user can set up their account to filter out messages
- where someone just adds themselves to the CC field of a bug
- (which happens a lot.) If you come along, add yourself to the CC field,
- and add a comment saying "Adding self to CC", then that person
- gets a pointless piece of mail they would otherwise have avoided.
- </P
-><P
-> Don't use sigs in comments. Signing your name ("Bill") is acceptable,
- particularly if you do it out of habit, but full mail/news-style
- four line ASCII art creations are not.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="attachments"
-></A
->3.2.4. Attachments</H2
-><P
-> Use attachments, rather than comments, for large chunks of ASCII data,
- such as trace, debugging output files, or log files. That way, it doesn't
- bloat the bug for everyone who wants to read it, and cause people to
- receive fat, useless mails.
- </P
-><P
->Trim screenshots. There's no need to show the whole screen if
- you are pointing out a single-pixel problem.
- </P
-><P
->Don't attach simple test cases (e.g. one HTML file, one
- CSS file and an image) as a ZIP file. Instead, upload them in
- reverse order and edit the referring file so that they point to the
- attached files. This way, the test case works immediately
- out of the bug.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN401"
-></A
->3.2.5. Filing Bugs</H2
-><P
->Try to make sure that everything said in the summary is also
- said in the first comment. Summaries are often updated and this will
- ensure your original information is easily accessible.
- </P
-><P
-> You do not need to put "any" or similar strings in the URL field.
- If there is no specific URL associated with the bug, leave this
- field blank.
- </P
-><P
->If you feel a bug you filed was incorrectly marked as a
- DUPLICATE of another, please question it in your bug, not
- the bug it was duped to. Feel free to CC the person who duped it
- if they are not already CCed.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="how.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="userpreferences.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->How do I use Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->User Preferences</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->How do I use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="NEXT"
-TITLE="Hints and Tips"
-HREF="hintsandtips.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="how"
-></A
->3.1. How do I use Bugzilla?</H1
-><P
->This section contains information for end-users of Bugzilla.
- There is a Bugzilla test installation, called
- <A
-HREF="http://landfill.bugzilla.org/"
-TARGET="_top"
->Landfill</A
->,
- which you are welcome to play with (if it's up.)
- However, it does not necessarily
- have all Bugzilla features enabled, and often runs cutting-edge versions
- of Bugzilla for testing, so some things may work slightly differently
- than mentioned here.</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="myaccount"
-></A
->3.1.1. Create a Bugzilla Account</H2
-><P
->If you want to use Bugzilla, first you need to create an account.
- Consult with the administrator responsible for your installation of
- Bugzilla for the URL you should use to access it. If you're
- test-driving Bugzilla, use this URL:
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
-> http://landfill.bugzilla.org/bugzilla-tip/</A
->
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Click the
- <SPAN
-CLASS="QUOTE"
->"Open a new Bugzilla account"</SPAN
->
-
- link, enter your email address and, optionally, your name in the
- spaces provided, then click
- <SPAN
-CLASS="QUOTE"
->"Create Account"</SPAN
->
-
- .</P
-></LI
-><LI
-><P
->Within moments, you should receive an email to the address
- you provided above, which contains your login name (generally the
- same as the email address), and a password you can use to access
- your account. This password is randomly generated, and can be
- changed to something more memorable.</P
-></LI
-><LI
-><P
->Click the
- <SPAN
-CLASS="QUOTE"
->"Log In"</SPAN
->
- link in the yellow area at the bottom of the page in your browser,
- enter your email address and password into the spaces provided, and
- click
- <SPAN
-CLASS="QUOTE"
->"Login"</SPAN
->.
- </P
-></LI
-></OL
-><P
->You are now logged in. Bugzilla uses cookies for authentication
- so, unless your IP address changes, you should not have to log in
- again.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bug_page"
-></A
->3.1.2. Anatomy of a Bug</H2
-><P
->The core of Bugzilla is the screen which displays a particular
- bug. It's a good place to explain some Bugzilla concepts.
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"
-TARGET="_top"
-> Bug 1 on Landfill</A
->
-
- is a good example. Note that the labels for most fields are hyperlinks;
- clicking them will take you to context-sensitive help on that
- particular field. Fields marked * may not be present on every
- installation of Bugzilla.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <EM
->Product and Component</EM
->:
- Bugs are divided up by Product and Component, with a Product
- having one or more Components in it. For example,
- bugzilla.mozilla.org's "Bugzilla" Product is composed of several
- Components:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <EM
->Administration:</EM
->
- Administration of a Bugzilla installation.</TD
-></TR
-><TR
-><TD
-> <EM
->Bugzilla-General:</EM
->
- Anything that doesn't fit in the other components, or spans
- multiple components.</TD
-></TR
-><TR
-><TD
-> <EM
->Creating/Changing Bugs:</EM
->
- Creating, changing, and viewing bugs.</TD
-></TR
-><TR
-><TD
-> <EM
->Documentation:</EM
->
- The Bugzilla documentation, including The Bugzilla Guide.</TD
-></TR
-><TR
-><TD
-> <EM
->Email:</EM
->
- Anything to do with email sent by Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->Installation:</EM
->
- The installation process of Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->Query/Buglist:</EM
->
- Anything to do with searching for bugs and viewing the
- buglists.</TD
-></TR
-><TR
-><TD
-> <EM
->Reporting/Charting:</EM
->
- Getting reports from Bugzilla.</TD
-></TR
-><TR
-><TD
-> <EM
->User Accounts:</EM
->
- Anything about managing a user account from the user's perspective.
- Saved queries, creating accounts, changing passwords, logging in,
- etc.</TD
-></TR
-><TR
-><TD
-> <EM
->User Interface:</EM
->
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates,
- etc.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></LI
-><LI
-><P
-> <EM
->Status and Resolution:</EM
->
-
- These define exactly what state the bug is in - from not even
- being confirmed as a bug, through to being fixed and the fix
- confirmed by Quality Assurance. The different possible values for
- Status and Resolution on your installation should be documented in the
- context-sensitive help for those items.</P
-></LI
-><LI
-><P
-> <EM
->Assigned To:</EM
->
- The person responsible for fixing the bug.</P
-></LI
-><LI
-><P
-> <EM
->*URL:</EM
->
- A URL associated with the bug, if any.</P
-></LI
-><LI
-><P
-> <EM
->Summary:</EM
->
- A one-sentence summary of the problem.</P
-></LI
-><LI
-><P
-> <EM
->*Status Whiteboard:</EM
->
- (a.k.a. Whiteboard) A free-form text area for adding short notes
- and tags to a bug.</P
-></LI
-><LI
-><P
-> <EM
->*Keywords:</EM
->
- The administrator can define keywords which you can use to tag and
- categorise bugs - e.g. The Mozilla Project has keywords like crash
- and regression.</P
-></LI
-><LI
-><P
-> <EM
->Platform and OS:</EM
->
- These indicate the computing environment where the bug was
- found.</P
-></LI
-><LI
-><P
-> <EM
->Version:</EM
->
- The "Version" field is usually used for versions of a product which
- have been released, and is set to indicate which versions of a
- Component have the particular problem the bug report is
- about.</P
-></LI
-><LI
-><P
-> <EM
->Priority:</EM
->
- The bug assignee uses this field to prioritise his or her bugs.
- It's a good idea not to change this on other people's bugs.</P
-></LI
-><LI
-><P
-> <EM
->Severity:</EM
->
- This indicates how severe the problem is - from blocker
- ("application unusable") to trivial ("minor cosmetic issue"). You
- can also use this field to indicate whether a bug is an enhancement
- request.</P
-></LI
-><LI
-><P
-> <EM
->*Target:</EM
->
- (a.k.a. Target Milestone) A future version by which the bug is to
- be fixed. e.g. The Bugzilla Project's milestones for future
- Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
- restricted to numbers, thought - you can use any text strings, such
- as dates.</P
-></LI
-><LI
-><P
-> <EM
->Reporter:</EM
->
- The person who filed the bug.</P
-></LI
-><LI
-><P
-> <EM
->CC list:</EM
->
- A list of people who get mail when the bug changes.</P
-></LI
-><LI
-><P
-> <EM
->Attachments:</EM
->
- You can attach files (e.g. testcases or patches) to bugs. If there
- are any attachments, they are listed in this section.</P
-></LI
-><LI
-><P
-> <EM
->*Dependencies:</EM
->
- If this bug cannot be fixed unless other bugs are fixed (depends
- on), or this bug stops other bugs being fixed (blocks), their
- numbers are recorded here.</P
-></LI
-><LI
-><P
-> <EM
->*Votes:</EM
->
- Whether this bug has any votes.</P
-></LI
-><LI
-><P
-> <EM
->Additional Comments:</EM
->
- You can add your two cents to the bug discussion here, if you have
- something worthwhile to say.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="query"
-></A
->3.1.3. Searching for Bugs</H2
-><P
->The Bugzilla Search page is is the interface where you can find
- any bug report, comment, or patch currently in the Bugzilla system. You
- can play with it here:
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"
-TARGET="_top"
-> landfill.bugzilla.org/bugzilla-tip/query.cgi</A
->
-
- .</P
-><P
->The Search page has controls for selecting different possible
- values for all of the fields in a bug, as described above. Once you've
- defined a search, you can either run it, or save it as a Remembered
- Query, which can optionally appear in the footer of your pages.</P
-><P
->Highly advanced querying is done using Boolean Charts, which have
- their own
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html"
-TARGET="_top"
-> context-sensitive help</A
->
-
- .</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="list"
-></A
->3.1.4. Bug Lists</H2
-><P
->If you run a search, a list of matching bugs will be returned.
- The default search is to return all open bugs on the system - don't try
- running this search on a Bugzilla installation with a lot of
- bugs!</P
-><P
->The format of the list is configurable. For example, it can be
- sorted by clicking the column headings. Other useful features can be
- accessed using the links at the bottom of the list:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <EM
->Long Format:</EM
->
-
- this gives you a large page with a non-editable summary of the fields
- of each bug.</TD
-></TR
-><TR
-><TD
-> <EM
->Change Columns:</EM
->
-
- change the bug attributes which appear in the list.</TD
-></TR
-><TR
-><TD
-> <EM
->Change several bugs at once:</EM
->
-
- If your account is sufficiently empowered, you can make the same
- change to all the bugs in the list - for example, changing their
- owner.</TD
-></TR
-><TR
-><TD
-> <EM
->Send mail to bug owners:</EM
->
-
- Sends mail to the owners of all bugs on the list.</TD
-></TR
-><TR
-><TD
-> <EM
->Edit this query:</EM
->
-
- If you didn't get exactly the results you were looking for, you can
- return to the Query page through this link and make small revisions
- to the query you just made so you get more accurate results.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bugreports"
-></A
->3.1.5. Filing Bugs</H2
-><P
->Years of bug writing experience has been distilled for your
- reading pleasure into the
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"
-TARGET="_top"
-> Bug Writing Guidelines</A
->.
- While some of the advice is Mozilla-specific, the basic principles of
- reporting Reproducible, Specific bugs, isolating the Product you are
- using, the Version of the Product, the Component which failed, the
- Hardware Platform, and Operating System you were using at the time of
- the failure go a long way toward ensuring accurate, responsible fixes
- for the bug that bit you.</P
-><P
->The procedure for filing a test bug is as follows:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Go to
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
-> Landfill</A
->
- in your browser and click
- <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"
-TARGET="_top"
-> Enter a new bug report</A
->.
- </P
-></LI
-><LI
-><P
->Select a product - any one will do.</P
-></LI
-><LI
-><P
->Fill in the fields. Bugzilla should have made reasonable
- guesses, based upon your browser, for the "Platform" and "OS"
- drop-down boxes. If they are wrong, change them.</P
-></LI
-><LI
-><P
->Select "Commit" and send in your bug report.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Hints and Tips</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->The Bugzilla Guide - 2.16.4 Release</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="NEXT"
-TITLE="About This Guide"
-HREF="about.html"><META
-NAME="KEYWORD"
-CONTENT="Bugzilla"><META
-NAME="KEYWORD"
-CONTENT="Guide"><META
-NAME="KEYWORD"
-CONTENT="installation"><META
-NAME="KEYWORD"
-CONTENT="FAQ"><META
-NAME="KEYWORD"
-CONTENT="administration"><META
-NAME="KEYWORD"
-CONTENT="integration"><META
-NAME="KEYWORD"
-CONTENT="MySQL"><META
-NAME="KEYWORD"
-CONTENT="Mozilla"><META
-NAME="KEYWORD"
-CONTENT="webtools"></HEAD
-><BODY
-CLASS="book"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="BOOK"
-><A
-NAME="index"
-></A
-><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="title"
-><A
-NAME="AEN2"
-></A
->The Bugzilla Guide - 2.16.4 Release</H1
-><H3
-CLASS="author"
-><A
-NAME="AEN5"
-></A
->Matthew P. Barnson</H3
-><H3
-CLASS="author"
-><A
-NAME="AEN9"
-></A
->The Bugzilla Team</H3
-><P
-CLASS="pubdate"
->2003-11-01<BR></P
-><DIV
-><DIV
-CLASS="abstract"
-><A
-NAME="AEN14"
-></A
-><P
-></P
-><P
-> This is the documentation for Bugzilla, the mozilla.org
- bug-tracking system.
- Bugzilla is an enterprise-class piece of software
- that powers issue-tracking for hundreds of
- organizations around the world, tracking millions of bugs.
- </P
-><P
->
- This documentation is maintained in DocBook 4.1.2 XML format.
- Changes are best submitted as plain text or XML diffs, attached
- to a bug filed in
- <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->mozilla.org's Bugzilla</A
->.
- </P
-><P
-> The most current version of this document can always be found on the
- <A
-HREF="http://www.bugzilla.org/documentation.html"
-TARGET="_top"
->Bugzilla Documentation Page</A
->.
- </P
-><P
-></P
-></DIV
-></DIV
-><HR></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1. <A
-HREF="about.html"
->About This Guide</A
-></DT
-><DD
-><DL
-><DT
->1.1. <A
-HREF="copyright.html"
->Copyright Information</A
-></DT
-><DT
->1.2. <A
-HREF="disclaimer.html"
->Disclaimer</A
-></DT
-><DT
->1.3. <A
-HREF="newversions.html"
->New Versions</A
-></DT
-><DT
->1.4. <A
-HREF="credits.html"
->Credits</A
-></DT
-><DT
->1.5. <A
-HREF="conventions.html"
->Document Conventions</A
-></DT
-></DL
-></DD
-><DT
->2. <A
-HREF="introduction.html"
->Introduction</A
-></DT
-><DD
-><DL
-><DT
->2.1. <A
-HREF="whatis.html"
->What is Bugzilla?</A
-></DT
-><DT
->2.2. <A
-HREF="why.html"
->Why Should We Use Bugzilla?</A
-></DT
-></DL
-></DD
-><DT
->3. <A
-HREF="using.html"
->Using Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->3.1. <A
-HREF="how.html"
->How do I use Bugzilla?</A
-></DT
-><DT
->3.2. <A
-HREF="hintsandtips.html"
->Hints and Tips</A
-></DT
-><DT
->3.3. <A
-HREF="userpreferences.html"
->User Preferences</A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="installation.html"
->Installation</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
-></DT
-><DT
->4.2. <A
-HREF="extraconfig.html"
->Optional Additional Configuration</A
-></DT
-><DT
->4.3. <A
-HREF="win32.html"
->Win32 Installation Notes</A
-></DT
-><DT
->4.4. <A
-HREF="osx.html"
->Mac OS X Installation Notes</A
-></DT
-><DT
->4.5. <A
-HREF="troubleshooting.html"
->Troubleshooting</A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="administration.html"
->Administering Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="parameters.html"
->Bugzilla Configuration</A
-></DT
-><DT
->5.2. <A
-HREF="useradmin.html"
->User Administration</A
-></DT
-><DT
->5.3. <A
-HREF="programadmin.html"
->Product, Component, Milestone, and Version Administration</A
-></DT
-><DT
->5.4. <A
-HREF="voting.html"
->Voting</A
-></DT
-><DT
->5.5. <A
-HREF="groups.html"
->Groups and Group Security</A
-></DT
-><DT
->5.6. <A
-HREF="security.html"
->Bugzilla Security</A
-></DT
-><DT
->5.7. <A
-HREF="cust-templates.html"
->Template Customisation</A
-></DT
-><DT
->5.8. <A
-HREF="upgrading.html"
->Upgrading to New Releases</A
-></DT
-><DT
->5.9. <A
-HREF="integration.html"
->Integrating Bugzilla with Third-Party Tools</A
-></DT
-></DL
-></DD
-><DT
->A. <A
-HREF="faq.html"
->The Bugzilla FAQ</A
-></DT
-><DT
->B. <A
-HREF="database.html"
->The Bugzilla Database</A
-></DT
-><DD
-><DL
-><DT
->B.1. <A
-HREF="dbschema.html"
->Database Schema Chart</A
-></DT
-><DT
->B.2. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
-></DT
-></DL
-></DD
-><DT
->C. <A
-HREF="patches.html"
->Useful Patches and Utilities for Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->C.1. <A
-HREF="rewrite.html"
->Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</A
-></DT
-><DT
->C.2. <A
-HREF="cmdline.html"
->Command-line Bugzilla Queries</A
-></DT
-></DL
-></DD
-><DT
->D. <A
-HREF="variants.html"
->Bugzilla Variants and Competitors</A
-></DT
-><DD
-><DL
-><DT
->D.1. <A
-HREF="variant-redhat.html"
->Red Hat Bugzilla</A
-></DT
-><DT
->D.2. <A
-HREF="variant-fenris.html"
->Loki Bugzilla (Fenris)</A
-></DT
-><DT
->D.3. <A
-HREF="variant-issuezilla.html"
->Issuezilla</A
-></DT
-><DT
->D.4. <A
-HREF="variant-scarab.html"
->Scarab</A
-></DT
-><DT
->D.5. <A
-HREF="variant-perforce.html"
->Perforce SCM</A
-></DT
-><DT
->D.6. <A
-HREF="variant-sourceforge.html"
->SourceForge</A
-></DT
-></DL
-></DD
-><DT
->E. <A
-HREF="gfdl.html"
->GNU Free Documentation License</A
-></DT
-><DD
-><DL
-><DT
->0. <A
-HREF="gfdl-0.html"
->PREAMBLE</A
-></DT
-><DT
->1. <A
-HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
-></DT
-><DT
->2. <A
-HREF="gfdl-2.html"
->VERBATIM COPYING</A
-></DT
-><DT
->3. <A
-HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
-></DT
-><DT
->4. <A
-HREF="gfdl-4.html"
->MODIFICATIONS</A
-></DT
-><DT
->5. <A
-HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
-></DT
-><DT
->6. <A
-HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
-></DT
-><DT
->7. <A
-HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
-></DT
-><DT
->8. <A
-HREF="gfdl-8.html"
->TRANSLATION</A
-></DT
-><DT
->9. <A
-HREF="gfdl-9.html"
->TERMINATION</A
-></DT
-><DT
->10. <A
-HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
-></DT
-><DT
-><A
-HREF="gfdl-howto.html"
->How to use this License for your documents</A
-></DT
-></DL
-></DD
-><DT
-><A
-HREF="glossary.html"
->Glossary</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
->List of Figures</B
-></DT
-><DT
->4-1. <A
-HREF="troubleshooting.html#trouble-filetemp-errors"
->Other File::Temp error messages</A
-></DT
-><DT
->4-2. <A
-HREF="troubleshooting.html#trouble-filetemp-patch"
->Patch for File::Temp in Perl 5.6.0</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
->List of Examples</B
-></DT
-><DT
->4-1. <A
-HREF="win32.html#AEN863"
->Installing ActivePerl ppd Modules on Microsoft
- Windows</A
-></DT
-><DT
->4-2. <A
-HREF="win32.html#AEN876"
->Installing OpenInteract ppd Modules manually on Microsoft
- Windows</A
-></DT
-><DT
->4-3. <A
-HREF="win32.html#AEN1058"
->Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier</A
-></DT
-><DT
->5-1. <A
-HREF="upgrading.html#upgrade-cvs"
->Upgrading using CVS</A
-></DT
-><DT
->5-2. <A
-HREF="upgrading.html#upgrade-tarball"
->Upgrading using the tarball</A
-></DT
-><DT
->5-3. <A
-HREF="upgrading.html#upgrade-patches"
->Upgrading using patches</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->About This Guide</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Installation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="User Preferences"
-HREF="userpreferences.html"><LINK
-REL="NEXT"
-TITLE="Step-by-step Install"
-HREF="stepbystep.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="userpreferences.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="installation"
-></A
->Chapter 4. Installation</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->4.1. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
-></DT
-><DD
-><DL
-><DT
->4.1.1. <A
-HREF="stepbystep.html#AEN430"
->Introduction</A
-></DT
-><DT
->4.1.2. <A
-HREF="stepbystep.html#AEN434"
->Package List</A
-></DT
-><DT
->4.1.3. <A
-HREF="stepbystep.html#install-mysql"
->MySQL</A
-></DT
-><DT
->4.1.4. <A
-HREF="stepbystep.html#install-perl"
->Perl</A
-></DT
-><DT
->4.1.5. <A
-HREF="stepbystep.html#perl-modules"
->Perl Modules</A
-></DT
-><DT
->4.1.6. <A
-HREF="stepbystep.html#AEN607"
->HTTP Server</A
-></DT
-><DT
->4.1.7. <A
-HREF="stepbystep.html#AEN626"
->Bugzilla</A
-></DT
-><DT
->4.1.8. <A
-HREF="stepbystep.html#AEN643"
->Setting Up the MySQL Database</A
-></DT
-><DT
->4.1.9. <A
-HREF="stepbystep.html#AEN681"
-><TT
-CLASS="filename"
->checksetup.pl</TT
-></A
-></DT
-><DT
->4.1.10. <A
-HREF="stepbystep.html#AEN713"
->Configuring Bugzilla</A
-></DT
-></DL
-></DD
-><DT
->4.2. <A
-HREF="extraconfig.html"
->Optional Additional Configuration</A
-></DT
-><DD
-><DL
-><DT
->4.2.1. <A
-HREF="extraconfig.html#AEN719"
->Dependency Charts</A
-></DT
-><DT
->4.2.2. <A
-HREF="extraconfig.html#AEN734"
->Bug Graphs</A
-></DT
-><DT
->4.2.3. <A
-HREF="extraconfig.html#AEN747"
->The Whining Cron</A
-></DT
-><DT
->4.2.4. <A
-HREF="extraconfig.html#bzldap"
->LDAP Authentication</A
-></DT
-><DT
->4.2.5. <A
-HREF="extraconfig.html#content-type"
->Preventing untrusted Bugzilla content from executing malicious
- Javascript code</A
-></DT
-><DT
->4.2.6. <A
-HREF="extraconfig.html#htaccess"
-><TT
-CLASS="filename"
->.htaccess</TT
->
- files and security</A
-></DT
-><DT
->4.2.7. <A
-HREF="extraconfig.html#mod-throttle"
-><TT
-CLASS="filename"
->mod_throttle</TT
->
-
- and Security</A
-></DT
-></DL
-></DD
-><DT
->4.3. <A
-HREF="win32.html"
->Win32 Installation Notes</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="win32.html#wininstall"
->Win32 Installation: Step-by-step</A
-></DT
-><DT
->4.3.2. <A
-HREF="win32.html#addlwintips"
->Additional Windows Tips</A
-></DT
-></DL
-></DD
-><DT
->4.4. <A
-HREF="osx.html"
->Mac OS X Installation Notes</A
-></DT
-><DT
->4.5. <A
-HREF="troubleshooting.html"
->Troubleshooting</A
-></DT
-><DD
-><DL
-><DT
->4.5.1. <A
-HREF="troubleshooting.html#AEN1092"
->Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
-></DT
-><DT
->4.5.2. <A
-HREF="troubleshooting.html#AEN1097"
->DBD::Sponge::db prepare failed</A
-></DT
-><DT
->4.5.3. <A
-HREF="troubleshooting.html#paranoid-security"
->cannot chdir(/var/spool/mqueue)</A
-></DT
-><DT
->4.5.4. <A
-HREF="troubleshooting.html#trouble-filetemp"
->Your vendor has not defined Fcntl macro O_NOINHERIT</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="userpreferences.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->User Preferences</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Step-by-step Install</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Integrating Bugzilla with Third-Party Tools</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Upgrading to New Releases"
-HREF="upgrading.html"><LINK
-REL="NEXT"
-TITLE="The Bugzilla FAQ"
-HREF="faq.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="upgrading.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="faq.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="integration"
-></A
->5.9. Integrating Bugzilla with Third-Party Tools</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bonsai"
-></A
->5.9.1. Bonsai</H2
-><P
->Bonsai is a web-based tool for managing
- <A
-HREF="integration.html#cvs"
->CVS, the Concurrent Versioning System</A
->
-
- . Using Bonsai, administrators can control open/closed status of trees,
- query a fast relational database back-end for change, branch, and comment
- information, and view changes made since the last time the tree was
- closed. Bonsai
- also integrates with
- <A
-HREF="integration.html#tinderbox"
->Tinderbox, the Mozilla automated build management system</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="cvs"
-></A
->5.9.2. CVS</H2
-><P
->CVS integration is best accomplished, at this point, using the
- Bugzilla Email Gateway.</P
-><P
->Follow the instructions in this Guide for enabling Bugzilla e-mail
- integration. Ensure that your check-in script sends an email to your
- Bugzilla e-mail gateway with the subject of
- <SPAN
-CLASS="QUOTE"
->"[Bug XXXX]"</SPAN
->,
- and you can have CVS check-in comments append to your Bugzilla bug. If
- you want to have the bug be closed automatically, you'll have to modify
- the <TT
-CLASS="filename"
->contrib/bugzilla_email_append.pl</TT
-> script.
- </P
-><P
->There is also a CVSZilla project, based upon somewhat dated
- Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
- email. Check it out at:
- <A
-HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
-TARGET="_top"
-> http://homepages.kcbbs.gen.nz/~tonyg/</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="scm"
-></A
->5.9.3. Perforce SCM</H2
-><P
->You can find the project page for Bugzilla and Teamtrack Perforce
- integration (p4dti) at:
- <A
-HREF="http://www.ravenbrook.com/project/p4dti/"
-TARGET="_top"
-> http://www.ravenbrook.com/project/p4dti</A
->
-
- .
- <SPAN
-CLASS="QUOTE"
->"p4dti"</SPAN
->
-
- is now an officially supported product from Perforce, and you can find
- the "Perforce Public Depot" p4dti page at
- <A
-HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
-TARGET="_top"
-> http://public.perforce.com/public/perforce/p4dti/index.html</A
->
-
- .</P
-><P
->Integration of Perforce with Bugzilla, once patches are applied, is
- seamless. Perforce replication information will appear below the comments
- of each bug. Be certain you have a matching set of patches for the
- Bugzilla version you are installing. p4dti is designed to support
- multiple defect trackers, and maintains its own documentation for it.
- Please consult the pages linked above for further information.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="tinderbox"
-></A
->5.9.4. Tinderbox/Tinderbox2</H2
-><P
->We need Tinderbox integration information.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="upgrading.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="faq.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Upgrading to New Releases</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The Bugzilla FAQ</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Introduction</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Document Conventions"
-HREF="conventions.html"><LINK
-REL="NEXT"
-TITLE="What is Bugzilla?"
-HREF="whatis.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="conventions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="whatis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="introduction"
-></A
->Chapter 2. Introduction</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->2.1. <A
-HREF="whatis.html"
->What is Bugzilla?</A
-></DT
-><DT
->2.2. <A
-HREF="why.html"
->Why Should We Use Bugzilla?</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="conventions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="whatis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Document Conventions</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->What is Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->New Versions</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Disclaimer"
-HREF="disclaimer.html"><LINK
-REL="NEXT"
-TITLE="Credits"
-HREF="credits.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="credits.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="newversions"
-></A
->1.3. New Versions</H1
-><P
-> This is the 2.16.4 version of The Bugzilla Guide. It is so named
- to match the version of Bugzilla it is disributed with. If you are
- reading this from any source other than those below, please
- check one of these mirrors to make sure you are reading an
- up-to-date version of the Guide.
- </P
-><P
-> The newest version of this guide can always be found at <A
-HREF="http://www.bugzilla.org"
-TARGET="_top"
->bugzilla.org</A
->; including
- documentation for past releases and the current development version.
- </P
-><P
-> The documentation for the most recent stable release of Bugzilla can also
- be found at
- <A
-HREF="http://www.tldp.org"
-TARGET="_top"
->The Linux Documentation Project</A
->.
- </P
-><P
-> The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at
- <A
-HREF="http://www.mozilla.org/cvs.html"
-TARGET="_top"
->the Mozilla CVS page</A
->,
- and check out the <TT
-CLASS="filename"
->mozilla/webtools/bugzilla/docs/</TT
->
- subtree.
- </P
-><P
-> The Bugzilla Guide is currently only available in English.
- If you would like to volunteer to translate it, please contact
- <A
-HREF="mailto:justdave@syndicomm.com"
-TARGET="_top"
->Dave Miller</A
->.
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="credits.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Disclaimer</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Credits</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Mac OS X Installation Notes</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Win32 Installation Notes"
-HREF="win32.html"><LINK
-REL="NEXT"
-TITLE="Troubleshooting"
-HREF="troubleshooting.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="win32.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="osx"
-></A
->4.4. Mac OS X Installation Notes</H1
-><P
->There are a lot of common libraries and utilities out there that
- Apple did not include with Mac OS X, but which run perfectly well on it.
- The GD library, which Bugzilla needs to do bug graphs, is one of
- these.</P
-><P
->The easiest way to get a lot of these is with a program called
- Fink, which is similar in nature to the CPAN installer, but installs
- common GNU utilities. Fink is available from
- <http://sourceforge.net/projects/fink/>.</P
-><P
->Follow the instructions for setting up Fink. Once it's installed,
- you'll want to run the following as root:
- <B
-CLASS="command"
->fink install gd</B
->
- </P
-><P
->It will prompt you for a number of dependencies, type 'y' and hit
- enter to install all of the dependencies. Then watch it work.</P
-><P
->To prevent creating conflicts with the software that Apple installs
- by default, Fink creates its own directory tree at /sw where it installs
- most of the software that it installs. This means your libraries and
- headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
- and /usr/local/include. Because of these changed locations for the
- libraries, the Perl GD module will not install directly via CPAN, because it
- looks for the specific paths instead of getting them from your
- environment. But there's a way around that :-)</P
-><P
->Instead of typing
- <SPAN
-CLASS="QUOTE"
->"install GD"</SPAN
->
- at the
- <TT
-CLASS="prompt"
->cpan></TT
->
- prompt, type
- <B
-CLASS="command"
->look GD</B
->.
- This should go through the motions of downloading the latest version of
- the GD module, then it will open a shell and drop you into the build
- directory. Apply <A
-HREF="../xml/gd-makefile.patch"
-TARGET="_top"
->this patch</A
->
- to the Makefile.PL file (save the
- patch into a file and use the command
- <B
-CLASS="command"
->patch < patchfile</B
->.)
- </P
-><P
->Then, run these commands to finish the installation of the GD
- module:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <B
-CLASS="command"
->perl Makefile.PL</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make test</B
->
- </TD
-></TR
-><TR
-><TD
-> <B
-CLASS="command"
->make install</B
->
- </TD
-></TR
-><TR
-><TD
->And don't forget to run
- <B
-CLASS="command"
->exit</B
->
-
- to get back to CPAN.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="win32.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Win32 Installation Notes</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Troubleshooting</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Bugzilla Configuration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="NEXT"
-TITLE="User Administration"
-HREF="useradmin.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="administration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="useradmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="parameters"
-></A
->5.1. Bugzilla Configuration</H1
-><P
->Bugzilla is configured by changing various parameters, accessed
- from the "Edit parameters" link in the page footer. Here are
- some of the key parameters on that page. You should run down this
- list and set them appropriately after installing Bugzilla.</P
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->
- <B
-CLASS="command"
->maintainer</B
->:
- The maintainer parameter is the email address of the person
- responsible for maintaining this
- Bugzilla installation. The address need not be that of a valid Bugzilla
- account.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->urlbase</B
->:
- This parameter defines the fully qualified domain name and web
- server path to your Bugzilla installation.</P
-><P
->For example, if your Bugzilla query page is
- <TT
-CLASS="filename"
->http://www.foo.com/bugzilla/query.cgi</TT
->,
- set your <SPAN
-CLASS="QUOTE"
->"urlbase"</SPAN
->
- to <TT
-CLASS="filename"
->http://www.foo.com/bugzilla/</TT
->.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usebuggroups</B
->:
- This dictates whether or not to implement group-based security for
- Bugzilla. If set, Bugzilla bugs can have an associated 'group',
- defining which users are allowed to see and edit the
- bug.</P
-><P
->Set "usebuggroups" to "on"
- <EM
->only</EM
->
- if you may wish to restrict access to particular bugs to certain
- groups of users. I suggest leaving
- this parameter <EM
->off</EM
->
- while initially testing your Bugzilla.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usebuggroupsentry</B
->:
- Bugzilla Products can have a group associated with them, so that
- certain users can only see bugs in certain products. When this parameter
- is set to <SPAN
-CLASS="QUOTE"
->"on"</SPAN
->, this places all newly-created bugs in the
- group for their product immediately.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->shadowdb</B
->:
- You run into an interesting problem when Bugzilla reaches a
- high level of continuous activity. MySQL supports only table-level
- write locking. What this means is that if someone needs to make a
- change to a bug, they will lock the entire table until the operation
- is complete. Locking for write also blocks reads until the write is
- complete. The
- <SPAN
-CLASS="QUOTE"
->"shadowdb"</SPAN
->
- parameter was designed to get around this limitation. While only a
- single user is allowed to write to a table at a time, reads can
- continue unimpeded on a read-only shadow copy of the database.
- Although your database size will double, a shadow database can cause
- an enormous performance improvement when implemented on extremely
- high-traffic Bugzilla databases.</P
-><P
-> As a guide, mozilla.org began needing
- <SPAN
-CLASS="QUOTE"
->"shadowdb"</SPAN
->
- when they reached around 40,000 Bugzilla users with several hundred
- Bugzilla bug changes and comments per day.</P
-><P
->The value of the parameter defines the name of the
- shadow bug database.
- Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a
- *very* large installation of Bugzilla.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Enabling "shadowdb" can adversely affect the stability of
- your installation of Bugzilla. You should regularly check that your
- database is in sync. It is often advisable to force a shadow
- database sync nightly via
- <SPAN
-CLASS="QUOTE"
->"cron"</SPAN
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->If you use the "shadowdb" option, it is only natural that you
- should turn the "queryagainstshadowdb" option on as well. Otherwise
- you are replicating data into a shadow database for no reason!</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->shutdownhtml</B
->:
-
- If you need to shut down Bugzilla to perform administration, enter
- some descriptive HTML here and anyone who tries to use Bugzilla will
- receive a page to that effect. Obviously, editparams.cgi will
- still be accessible so you can remove the HTML and re-enable Bugzilla.
- :-)
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->passwordmail</B
->:
-
- Every time a user creates an account, the text of
- this parameter (with substitutions) is sent to the new user along with
- their password message.</P
-><P
->Add any text you wish to the "passwordmail" parameter box. For
- instance, many people choose to use this box to give a quick training
- blurb about how to use Bugzilla at your site.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->useqacontact</B
->:
-
- This allows you to define an email address for each component, in
- addition
- to that of the default owner, who will be sent carbon copies of
- incoming bugs.</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->usestatuswhiteboard</B
->:
- This defines whether you wish to have a free-form, overwritable field
- associated with each bug. The advantage of the Status Whiteboard is
- that it can be deleted or modified with ease, and provides an
- easily-searchable field for indexing some bugs that have some trait
- in common.
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->whinedays</B
->:
- Set this to the number of days you want to let bugs go
- in the NEW or REOPENED state before notifying people they have
- untouched new bugs. If you do not plan to use this feature, simply do
- not set up the whining cron job described in the installation
- instructions, or set this value to "0" (never whine).</P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->commenton*</B
->:
- All these
- fields allow you to dictate what changes can pass without comment,
- and which must have a comment from the person who changed them.
- Often, administrators will allow users to add themselves to the CC
- list, accept bugs, or change the Status Whiteboard without adding a
- comment as to their reasons for the change, yet require that most
- other changes come with an explanation.</P
-><P
->Set the "commenton" options according to your site policy. It
- is a wise idea to require comments when users resolve, reassign, or
- reopen bugs at the very least.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is generally far better to require a developer comment
- when resolving bugs than not. Few things are more annoying to bug
- database users than having a developer mark a bug "fixed" without
- any comment as to what the fix was (or even that it was truly
- fixed!)</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> <B
-CLASS="command"
->supportwatchers</B
->:
-
- Turning on this option allows users to ask to receive copies of
- all a particular other user's bug email. This is, of
- course, subject to the groupset restrictions on the bug; if the
- <SPAN
-CLASS="QUOTE"
->"watcher"</SPAN
->
- would not normally be allowed to view a bug, the watcher cannot get
- around the system by setting herself up to watch the bugs of someone
- with bugs outside her privileges. They would still only receive email
- updates for those bugs she could normally view.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="useradmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Administering Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->User Administration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Useful Patches and Utilities for Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="MySQL Bugzilla Database Introduction"
-HREF="dbdoc.html"><LINK
-REL="NEXT"
-TITLE="Apache
- mod_rewrite
-
- magic"
-HREF="rewrite.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="rewrite.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="patches"
-></A
->Appendix C. Useful Patches and Utilities for Bugzilla</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->C.1. <A
-HREF="rewrite.html"
->Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</A
-></DT
-><DT
->C.2. <A
-HREF="cmdline.html"
->Command-line Bugzilla Queries</A
-></DT
-></DL
-></DIV
-><P
->Are you looking for a way to put your Bugzilla into overdrive? Catch
- some of the niftiest tricks here in this section.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="rewrite.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MySQL Bugzilla Database Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Product, Component, Milestone, and Version Administration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="User Administration"
-HREF="useradmin.html"><LINK
-REL="NEXT"
-TITLE="Voting"
-HREF="voting.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="useradmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="voting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="programadmin"
-></A
->5.3. Product, Component, Milestone, and Version Administration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="products"
-></A
->5.3.1. Products</H2
-><P
-> <A
-HREF="glossary.html#gloss-product"
-><I
-CLASS="glossterm"
-> Products</I
-></A
->
-
- are the broadest category in Bugzilla, and tend to represent real-world
- shipping products. E.g. if your company makes computer games,
- you should have one product per game, perhaps a "Common" product for
- units of technology used in multiple games, and maybe a few special
- products (Website, Administration...)</P
-><P
->Many of Bugzilla's settings are configurable on a per-product
- basis. The number of "votes" available to users is set per-product,
- as is the number of votes
- required to move a bug automatically from the UNCONFIRMED status to the
- NEW status.</P
-><P
->To create a new product:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "products" from the footer</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right</P
-></LI
-><LI
-><P
->Enter the name of the product and a description. The
- Description field may contain HTML.</P
-></LI
-></OL
-><P
->Don't worry about the "Closed for bug entry", "Maximum Votes
- per person", "Maximum votes a person can put on a single bug",
- "Number of votes a bug in this Product needs to automatically get out
- of the UNCOMFIRMED state", and "Version" options yet. We'll cover
- those in a few moments.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="components"
-></A
->5.3.2. Components</H2
-><P
->Components are subsections of a Product. E.g. the computer game
- you are designing may have a "UI"
- component, an "API" component, a "Sound System" component, and a
- "Plugins" component, each overseen by a different programmer. It
- often makes sense to divide Components in Bugzilla according to the
- natural divisions of responsibility within your Product or
- company.</P
-><P
-> Each component has a owner and (if you turned it on in the parameters),
- a QA Contact. The owner should be the primary person who fixes bugs in
- that component. The QA Contact should be the person who will ensure
- these bugs are completely fixed. The Owner, QA Contact, and Reporter
- will get email when new bugs are created in this Component and when
- these bugs change. Default Owner and Default QA Contact fields only
- dictate the
- <EM
->default assignments</EM
->;
- these can be changed on bug submission, or at any later point in
- a bug's life.</P
-><P
->To create a new Component:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select the "Edit components" link from the "Edit product"
- page</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Fill out the "Component" field, a short "Description",
- the "Initial Owner" and "Initial QA Contact" (if enabled.)
- The Component and Description fields may contain HTML;
- the "Initial Owner" field must be a login name
- already existing in the database.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="versions"
-></A
->5.3.3. Versions</H2
-><P
->Versions are the revisions of the product, such as "Flinders
- 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
- field; the usual practice is to select the most recent version with
- the bug.
- </P
-><P
->To create and edit Versions:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->From the "Edit product" screen, select "Edit Versions"</P
-></LI
-><LI
-><P
->You will notice that the product already has the default
- version "undefined". Click the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Enter the name of the Version. This field takes text only.
- Then click the "Add" button.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="milestones"
-></A
->5.3.4. Milestones</H2
-><P
->Milestones are "targets" that you plan to get a bug fixed by. For
- example, you have a bug that you plan to fix for your 3.0 release, it
- would be assigned the milestone of 3.0.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Milestone options will only appear for a Product if you turned
- on the "usetargetmilestone" Param in the "Edit Parameters" screen.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->To create new Milestones, set Default Milestones, and set
- Milestone URL:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "Edit milestones" from the "Edit product" page.</P
-></LI
-><LI
-><P
->Select "Add" in the bottom right corner.
- text</P
-></LI
-><LI
-><P
->Enter the name of the Milestone in the "Milestone" field. You
- can optionally set the "sortkey", which is a positive or negative
- number (-255 to 255) that defines where in the list this particular
- milestone appears. This is because milestones often do not
- occur in alphanumeric order For example, "Future" might be
- after "Release 1.2". Select "Add".</P
-></LI
-><LI
-><P
->From the Edit product screen, you can enter the URL of a
- page which gives information about your milestones and what
- they mean. </P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you want your milestone document to be restricted so
- that it can only be viewed by people in a particular Bugzilla
- group, the best way is to attach the document to a bug in that
- group, and make the URL the URL of that attachment.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="useradmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="voting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->User Administration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Voting</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Apache
- mod_rewrite
-
- magic</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
-REL="PREVIOUS"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
-REL="NEXT"
-TITLE="Command-line Bugzilla Queries"
-HREF="cmdline.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="patches.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. Useful Patches and Utilities for Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="rewrite"
-></A
->C.1. Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</H1
-><P
->Apache's
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- module lets you do some truly amazing things with URL rewriting. Here are
- a couple of examples of what you can do.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Make it so if someone types
- <TT
-CLASS="computeroutput"
->http://www.foo.com/12345</TT
->
-
- , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
- setting up your VirtualHost section for Bugzilla with a rule like
- this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <VirtualHost 12.34.56.78>
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-</VirtualHost>
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->There are many, many more things you can do with mod_rewrite.
- Please refer to the mod_rewrite documentation at
- <A
-HREF="http://www.apache.org"
-TARGET="_top"
->http://www.apache.org</A
->.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Bugzilla Security</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Groups and Group Security"
-HREF="groups.html"><LINK
-REL="NEXT"
-TITLE="Template Customisation"
-HREF="cust-templates.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="groups.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="cust-templates.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="security"
-></A
->5.6. Bugzilla Security</H1
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Poorly-configured MySQL and Bugzilla installations have
- given attackers full access to systems in the past. Please take these
- guidelines seriously, even for Bugzilla machines hidden away behind
- your firewall. 80% of all computer trespassers are insiders, not
- anonymous crackers.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->These instructions must, of necessity, be somewhat vague since
- Bugzilla runs on so many different platforms. If you have refinements
- of these directions, please submit a bug to <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->Bugzilla</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This is not meant to be a comprehensive list of every possible
- security issue regarding the tools mentioned in this section. There is
- no subsitute for reading the information written by the authors of any
- software running on your system.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-networking"
-></A
->5.6.1. TCP/IP Ports</H2
-><P
->TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
- only needs 1... 2 if you need to use features that require e-mail such
- as bug moving or the e-mail interface from contrib. You should audit
- your server and make sure that you aren't listening on any ports you
- don't need to be. You may also wish to use some kind of firewall
- software to be sure that trafic can only be recieved on ports you
- specify.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-mysql"
-></A
->5.6.2. MySQL</H2
-><P
->MySQL ships by default with many settings that should be changed.
- By defaults it allows anybody to connect from localhost without a
- password and have full administrative capabilities. It also defaults to
- not have a root password (this is <EM
->not</EM
-> the same as
- the system root). Also, many installations default to running
- <SPAN
-CLASS="application"
->mysqld</SPAN
-> as the system root.
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Make sure you are running at least version 3.22.32 of MySQL
- as earlier versions had notable security holes.
- </P
-></LI
-><LI
-><P
->Consult the documentation that came with your system for
- information on making <SPAN
-CLASS="application"
->mysqld</SPAN
-> run as an
- unprivleged user.
- </P
-></LI
-><LI
-><P
->You should also be sure to disable the anonymous user account
- and set a password for the root user. This is accomplished using the
- following commands:
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <TT
-CLASS="prompt"
->bash$</TT
-> mysql mysql
-<TT
-CLASS="prompt"
->mysql></TT
-> DELETE FROM user WHERE user = '';
-<TT
-CLASS="prompt"
->mysql></TT
-> UPDATE user SET password = password('<TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
->') WHERE user = 'root';
-<TT
-CLASS="prompt"
->mysql></TT
-> FLUSH PRIVILEGES;
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->From this point forward you will need to use
- <B
-CLASS="command"
->mysql -u root -p</B
-> and enter
- <TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
-> when prompted when using the
- mysql client.
- </P
-></LI
-><LI
-><P
->If you run MySQL on the same machine as your httpd server, you
- should consider disabling networking from within MySQL by adding
- the following to your <TT
-CLASS="filename"
->/etc/my.conf</TT
->:
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> [myslqd]
-# Prevent network access to MySQL.
-skip-networking
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->You may also consider running MySQL, or even all of Bugzilla
- in a chroot jail; however, instructions for doing that are beyond
- the scope of this document.
- </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-daemon"
-></A
->5.6.3. Daemon Accounts</H2
-><P
->Many daemons, such as Apache's httpd and MySQL's mysqld default to
- running as either <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> or <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->. Running
- as <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> introduces obvious security problems, but the
- problems introduced by running everything as <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> may
- not be so obvious. Basically, if you're running every daemon as
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> and one of them gets comprimised, they all get
- comprimised. For this reason it is recommended that you create a user
- account for each daemon.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will need to set the <TT
-CLASS="varname"
->webservergroup</TT
-> to
- the group you created for your webserver to run as in
- <TT
-CLASS="filename"
->localconfig</TT
->. This will allow
- <B
-CLASS="command"
->./checksetup.pl</B
-> to better adjust the file
- permissions on your Bugzilla install so as to not require making
- anything world-writable.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-access"
-></A
->5.6.4. Web Server Access Controls</H2
-><P
->There are many files that are placed in the Bugzilla directory
- area that should not be accessable from the web. Because of the way
- Bugzilla is currently layed out, the list of what should and should
- not be accessible is rather complicated. A new installation method
- is currently in the works which should solve this by allowing files
- that shouldn't be accessible from the web to be placed in directory
- outside the webroot. See
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
-TARGET="_top"
->bug
- 44659</A
-> for more information.
- </P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->In the main Bugzilla directory, you should:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block:
- <TT
-CLASS="filename"
->*.pl</TT
->, <TT
-CLASS="filename"
->*localconfig*</TT
->, <TT
-CLASS="filename"
->runtests.sh</TT
->, <TT
-CLASS="filename"
->processmail</TT
->, <TT
-CLASS="filename"
->syncshadowdb</TT
->
- </P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->localconfig.js</TT
->, <TT
-CLASS="filename"
->localconfig.rdf</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->duplicates.rdf</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data/webdot</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->If you use a remote webdot server:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow
- <TT
-CLASS="filename"
->*.dot</TT
->
- only for the remote webdot server</P
-></LI
-></UL
-></LI
-><LI
-><P
->Otherwise, if you use a local GraphViz:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
- <TT
-CLASS="filename"
->*.png</TT
->, <TT
-CLASS="filename"
->*.gif</TT
->, <TT
-CLASS="filename"
->*.jpg</TT
->, <TT
-CLASS="filename"
->*.map</TT
->
- </P
-></LI
-></UL
-></LI
-><LI
-><P
->And if you don't use any dot:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->Bugzilla</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->template</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Bugzilla ships with the ability to generate
- <TT
-CLASS="filename"
->.htaccess</TT
-> files instructing Apache which files
- should and should not be accessible.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->You should test to make sure that the files mentioned above are
- not accessible from the Internet, especially your
- <TT
-CLASS="filename"
->localconfig</TT
-> file which contains your database
- password. To test, simply point your web browser at the file; for
- example, to test mozilla.org's installation, we'd try to access
- <A
-HREF="http://bugzilla.mozilla.org/localconfig"
-TARGET="_top"
->http://bugzilla.mozilla.org/localconfig</A
->. You should
- get a <SPAN
-CLASS="errorcode"
->403</SPAN
-> <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
- error.
- </P
-><DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Not following the instructions in this section, including
- testing, may result in sensitive information being globally
- accessible.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="groups.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="cust-templates.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Groups and Group Security</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Template Customisation</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Step-by-step Install</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="NEXT"
-TITLE="Optional Additional Configuration"
-HREF="extraconfig.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="stepbystep"
-></A
->4.1. Step-by-step Install</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN430"
-></A
->4.1.1. Introduction</H2
-><P
->Bugzilla has been successfully installed under Solaris, Linux,
- and Win32. Win32 is not yet officially supported, but many people
- have got it working fine.
- Please see the
- <A
-HREF="win32.html"
->Win32 Installation Notes</A
->
- for further advice on getting Bugzilla to work on Microsoft
- Windows.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN434"
-></A
->4.1.2. Package List</H2
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you are running the very most recent
- version of Perl and MySQL (both the executables and development
- libraries) on your system, you can skip these manual installation
- steps for the Perl modules by using Bundle::Bugzilla; see
- <A
-HREF="stepbystep.html#bundlebugzilla"
->Using Bundle::Bugzilla instead of manually installing Perl modules</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The software packages necessary for the proper running of
- Bugzilla (with download links) are:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <A
-HREF="http://www.mysql.com/"
-TARGET="_top"
->MySQL database server</A
->
- (3.22.5 or greater)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.perl.org"
-TARGET="_top"
->Perl</A
->
- (5.005 or greater, 5.6.1 is recommended if you wish to
- use Bundle::Bugzilla)
- </P
-></LI
-><LI
-><P
->Perl Modules (minimum version):
- <P
-></P
-><OL
-TYPE="a"
-><LI
-><P
-> <A
-HREF="http://www.template-toolkit.org"
-TARGET="_top"
->Template</A
->
- (v2.07)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/AppConfig/"
-TARGET="_top"
->AppConfig
- </A
->
- (v1.52)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar.gz"
-TARGET="_top"
->Text::Wrap</A
->
- (v2001.0131)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://search.cpan.org/search?dist=File-Spec"
-TARGET="_top"
->File::Spec
- </A
->
- (v0.8.2)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Data/"
-TARGET="_top"
->Data::Dumper
- </A
->
- (any)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Mysql/"
-TARGET="_top"
->DBD::mysql
- </A
->
- (v1.2209)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/DBI/"
-TARGET="_top"
->DBI</A
->
- (v1.13)
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Date/"
-TARGET="_top"
->Date::Parse
- </A
->
- (any)
- </P
-></LI
-><LI
-><P
-> CGI::Carp
- (any)
- </P
-></LI
-></OL
->
- and, optionally:
- <P
-></P
-><OL
-TYPE="a"
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/GD/"
-TARGET="_top"
->GD</A
->
- (v1.19) for bug charting
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.cpan.org/modules/by-module/Chart/"
-TARGET="_top"
->Chart::Base
- </A
->
- (v0.99c) for bug charting
- </P
-></LI
-><LI
-><P
-> XML::Parser
- (any) for the XML interface
- </P
-></LI
-><LI
-><P
-> MIME::Parser
- (any) for the email interface
- </P
-></LI
-></OL
->
- </P
-></LI
-><LI
-><P
-> The web server of your choice.
- <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache</A
->
- is highly recommended.
- </P
-></LI
-></OL
->
-
- <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->It is a good idea, while installing Bugzilla, to ensure that there
- is some kind of firewall between you and the rest of the Internet,
- because your machine may be insecure for periods during the install.
- Many
- installation steps require an active Internet connection to complete,
- but you must take care to ensure that at no point is your machine
- vulnerable to an attack.</P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Linux-Mandrake 8.0 includes every
- required and optional library for Bugzilla. The easiest way to
- install them is by using the
- <TT
-CLASS="filename"
->urpmi</TT
->
-
- utility. If you follow these commands, you should have everything you
- need for Bugzilla, and
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- should not complain about any missing libraries. You may already have
- some of these installed.</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-mysql</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-chart</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-gd</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi perl-MailTools</B
->
-
- (for Bugzilla email integration)</TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->urpmi apache-modules</B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="install-mysql"
-></A
->4.1.3. MySQL</H2
-><P
->Visit the MySQL homepage at
- <A
-HREF="http://www.mysql.com"
-TARGET="_top"
->www.mysql.com</A
->
- to grab and install the latest stable release of the server.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Many of the binary
- versions of MySQL store their data files in
- <TT
-CLASS="filename"
->/var</TT
->.
- On some Unix systems, this is part of a smaller root partition,
- and may not have room for your bug database. You can set the data
- directory as an option to <TT
-CLASS="filename"
->configure</TT
->
- if you build MySQL from source yourself.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you install from something other than an RPM or Debian
- package, you will need to add <TT
-CLASS="filename"
->mysqld</TT
->
- to your init scripts so the server daemon will come back up whenever
- your machine reboots. Further discussion of UNIX init sequences are
- beyond the scope of this guide.
- </P
-><P
->Change your init script to start
- <TT
-CLASS="filename"
->mysqld</TT
->
- with the ability to accept large packets. By default,
- <TT
-CLASS="filename"
->mysqld</TT
->
- only accepts packets up to 64K long. This limits the size of
- attachments you may put on bugs. If you add
- <TT
-CLASS="option"
->-O max_allowed_packet=1M</TT
->
- to the command that starts
- <TT
-CLASS="filename"
->mysqld</TT
->
- (or <TT
-CLASS="filename"
->safe_mysqld</TT
->),
- then you will be able to have attachments up to about 1 megabyte.
- There is a Bugzilla parameter for maximum attachment size;
- you should configure it to match the value you choose here.</P
-><P
->If you plan on running Bugzilla and MySQL on the same machine,
- consider using the
- <TT
-CLASS="option"
->--skip-networking</TT
->
- option in the init script. This enhances security by preventing
- network access to MySQL.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="install-perl"
-></A
->4.1.4. Perl</H2
-><P
->Any machine that doesn't have Perl on it is a sad machine indeed.
- Perl can be got in source form from
- <A
-HREF="http://www.perl.com"
-TARGET="_top"
->perl.com</A
-> for the rare
- *nix systems which don't have it.
- Although Bugzilla runs with all post-5.005
- versions of Perl, it's a good idea to be up to the very latest version
- if you can when running Bugzilla. As of this writing, that is Perl
- version 5.6.1.</P
-><DIV
-CLASS="tip"
-><A
-NAME="bundlebugzilla"
-></A
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can skip the following Perl module installation steps by
- installing
- <SPAN
-CLASS="productname"
->Bundle::Bugzilla</SPAN
->
-
- from
- <A
-HREF="glossary.html#gloss-cpan"
-><I
-CLASS="glossterm"
->CPAN</I
-></A
->,
- which installs all required modules for you.</P
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->perl -MCPAN -e 'install "Bundle::Bugzilla"'</B
->
- </TT
->
- </P
-><P
->Bundle::Bugzilla doesn't include GD, Chart::Base, or
- MIME::Parser, which are not essential to a basic Bugzilla install. If
- installing this bundle fails, you should install each module
- individually to isolate the problem.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="perl-modules"
-></A
->4.1.5. Perl Modules</H2
-><P
->
- All Perl modules can be found on the
- <A
-HREF="http://www.cpan.org"
-TARGET="_top"
->Comprehensive Perl
- Archive Network</A
-> (CPAN). The
- CPAN servers have a real tendency to bog down, so please use mirrors.
- </P
-><P
->Quality, general Perl module installation instructions can be
- found on the CPAN website, but the easy thing to do is to just use the
- CPAN shell which does all the hard work for you.
- To use the CPAN shell to install a module:
- </P
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
- <B
-CLASS="command"
->perl -MCPAN -e 'install "<modulename>"'</B
->
- </TT
->
- </P
-><P
-> To do it the hard way:
- </P
-><P
->Untar the module tarball -- it should create its own
- directory</P
-><P
->CD to the directory just created, and enter the following
- commands:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->perl Makefile.PL</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make test</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->make install</B
->
- </TT
->
- </P
-></LI
-></OL
->
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Many people complain that Perl modules will not install for
- them. Most times, the error messages complain that they are missing a
- file in
- <SPAN
-CLASS="QUOTE"
->"@INC"</SPAN
->.
- Virtually every time, this error is due to permissions being set too
- restrictively for you to compile Perl modules or not having the
- necessary Perl development libraries installed on your system.
- Consult your local UNIX systems administrator for help solving these
- permissions issues; if you
- <EM
->are</EM
->
- the local UNIX sysadmin, please consult the newsgroup/mailing list
- for further assistance or hire someone to help you out.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN580"
-></A
->4.1.5.1. DBI</H3
-><P
->The DBI module is a generic Perl module used the
- MySQL-related modules. As long as your Perl installation was done
- correctly the DBI module should be a breeze. It's a mixed Perl/C
- module, but Perl's MakeMaker system simplifies the C compilation
- greatly.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN583"
-></A
->4.1.5.2. Data::Dumper</H3
-><P
->The Data::Dumper module provides data structure persistence for
- Perl (similar to Java's serialization). It comes with later
- sub-releases of Perl 5.004, but a re-installation just to be sure it's
- available won't hurt anything.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN586"
-></A
->4.1.5.3. MySQL-related modules</H3
-><P
->The Perl/MySQL interface requires a few mutually-dependent Perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package.</P
-><P
->The MakeMaker process will ask you a few questions about the
- desired compilation target and your MySQL installation. For most of the
- questions the provided default will be adequate, but when asked if your
- desired target is the MySQL or mSQL packages, you should
- select the MySQL related ones. Later you will be asked if you wish to
- provide backwards compatibility with the older MySQL packages; you
- should answer YES to this question. The default is NO.</P
-><P
->A host of 'localhost' should be fine and a testing user of 'test'
- with a null password should find itself with sufficient access to run
- tests on the 'test' database which MySQL created upon installation.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN591"
-></A
->4.1.5.4. TimeDate modules</H3
-><P
->Many of the more common date/time/calendar related Perl modules
- have been grouped into a bundle similar to the MySQL modules bundle.
- This bundle is stored on the CPAN under the name TimeDate.
- The component module we're most interested in is the Date::Format
- module, but installing all of them is probably a good idea anyway.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN594"
-></A
->4.1.5.5. GD (optional)</H3
-><P
->The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become the
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on millions of web pages to
- generate graphs on the fly. That's what Bugzilla will be using it for
- so you must install it if you want any of the graphing to work.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The Perl GD library requires some other libraries that may or
- may not be installed on your system, including
- <TT
-CLASS="classname"
->libpng</TT
->
- and
- <TT
-CLASS="classname"
->libgd</TT
->.
- The full requirements are listed in the Perl GD library README.
- If compiling GD fails, it's probably because you're
- missing a required library.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN601"
-></A
->4.1.5.6. Chart::Base (optional)</H3
-><P
->The Chart module provides Bugzilla with on-the-fly charting
- abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN.
- Note that earlier versions that 0.99c used GIFs, which are no longer
- supported by the latest versions of GD.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="AEN604"
-></A
->4.1.5.7. Template Toolkit</H3
-><P
->When you install Template Toolkit, you'll get asked various
- questions about features to enable. The defaults are fine, except
- that it is recommended you use the high speed XS Stash of the Template
- Toolkit, in order to achieve best performance. However, there are
- known problems with XS Stash and Perl 5.005_02 and lower. If you
- wish to use these older versions of Perl, please use the regular
- stash.</P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN607"
-></A
->4.1.6. HTTP Server</H2
-><P
->You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can run the web server on a
- different machine than MySQL, but need to adjust the MySQL
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- user permissions accordingly.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->We strongly recommend Apache as the web server to use. The
- Bugzilla Guide installation instructions, in general, assume you are
- using Apache. If you have got Bugzilla working using another webserver,
- please share your experiences with us.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><P
->You'll want to make sure that your web server will run any file
- with the .cgi extension as a CGI and not just display it. If you're
- using Apache that means uncommenting the following line in the httpd.conf
- file:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->AddHandler cgi-script .cgi</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->With Apache you'll also want to make sure that within the
- httpd.conf file the line:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> Options ExecCGI
-AllowOverride Limit
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- is in the stanza that covers the directories into which you intend to
- put the bugzilla .html and .cgi files.
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->AllowOverride Limit allows the use of a Deny statement in the
- .htaccess file generated by checksetup.pl</P
-><P
->Users of older versions of Apache may find the above lines
- in the srm.conf and access.conf files, respecitvely.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are important files and directories that should not be a
- served by the HTTP server - most files in the
- <SPAN
-CLASS="QUOTE"
->"data"</SPAN
->
- and
- <SPAN
-CLASS="QUOTE"
->"shadow"</SPAN
->
- directories and the
- <SPAN
-CLASS="QUOTE"
->"localconfig"</SPAN
->
- file. You should configure your HTTP server to not serve
- these files. Failure to do so will expose critical passwords and
- other data. Please see
- <A
-HREF="extraconfig.html#htaccess"
->.htaccess files and security</A
->
- for details on how to do this for Apache; the checksetup.pl
- script should create appropriate .htaccess files for you.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN626"
-></A
->4.1.7. Bugzilla</H2
-><P
->You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->).
- You may decide to put the files in the main web space for your
- web server or perhaps in
- <TT
-CLASS="filename"
->/usr/local</TT
->
- with a symbolic link in the web space that points to the Bugzilla
- directory.</P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you symlink the bugzilla directory into your Apache's HTML
- heirarchy, you may receive
- <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
- errors unless you add the
- <SPAN
-CLASS="QUOTE"
->"FollowSymLinks"</SPAN
->
- directive to the <Directory> entry for the HTML root
- in httpd.conf.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user. This is a temporary step
- until you run the post-install
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
- script, which locks down your installation.</P
-><P
->Lastly, you'll need to set up a symbolic link to
- <TT
-CLASS="filename"
->/usr/bonsaitools/bin/perl</TT
->
- for the correct location of your Perl executable (probably
- <TT
-CLASS="filename"
->/usr/bin/perl</TT
->).
- Otherwise you must hack all the .cgi files to change where they look
- for Perl. This can be done using the following Perl one-liner, but
- I suggest using the symlink approach to avoid upgrade hassles.
- </P
-><P
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->perl -pi -e
- 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
- processmail syncshadowdb</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- Change <TT
-CLASS="filename"
->/usr/bin/perl</TT
-> to match the location
- of Perl on your machine.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN643"
-></A
->4.1.8. Setting Up the MySQL Database</H2
-><P
->After you've gotten all the software installed and working you're
- ready to start preparing the database for its life as the back end to
- a high quality bug tracker.</P
-><P
->First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla
- username will be
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->, and will have minimal permissions.
- </P
-><P
->Begin by giving the MySQL root user a password. MySQL passwords are limited
- to 16 characters.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->mysql -u root mysql</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->UPDATE user SET Password=PASSWORD('<new_password>')
- WHERE user='root';</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
- From this point on, if you need to access MySQL as the MySQL root user,
- you will need to use
- <B
-CLASS="command"
->mysql -u root -p</B
->
-
- and enter <new_password>. Remember that MySQL user names have
- nothing to do with Unix user names (login names).</P
-><P
->Next, we use an SQL <B
-CLASS="command"
->GRANT</B
-> command to create a
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- user, and grant sufficient permissions for checksetup.pl, which we'll
- use later, to work its magic. This also restricts the
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- user to operations within a database called
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->, and only allows the account to connect from
- <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->.
- Modify it to reflect your setup if you will be connecting from
- another machine or as a different user.</P
-><P
->Remember to set <bugs_password> to some unique password.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost
- IDENTIFIED BY '<bugs_password>';</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using MySQL 4, the bugs user also needs to be granted
- the LOCK TABLES and CREATE TEMPORARY TABLES permissions.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN681"
-></A
->4.1.9. <TT
-CLASS="filename"
->checksetup.pl</TT
-></H2
-><P
->Next, run the magic checksetup.pl script. (Many thanks to
- <A
-HREF="mailto:holgerschurig@nikocity.de"
-TARGET="_top"
->Holger Schurig </A
->
- for writing this script!)
- This script is designed to make sure your MySQL database and other
- configuration options are consistent with the Bugzilla CGI files.
- It will make sure Bugzilla files and directories have reasonable
- permissions, set up the
- <TT
-CLASS="filename"
->data</TT
->
- directory, and create all the MySQL tables.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->./checksetup.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
- The first time you run it, it will create a file called
- <TT
-CLASS="filename"
->localconfig</TT
->.</P
-><P
->This file contains a variety of settings you may need to tweak
- including how Bugzilla should connect to the MySQL database.</P
-><P
->The connection settings include:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->server's host: just use
- <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->
- if the MySQL server is local</P
-></LI
-><LI
-><P
->database name:
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- if you're following these directions</P
-></LI
-><LI
-><P
->MySQL username:
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- if you're following these directions</P
-></LI
-><LI
-><P
->Password for the
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
- MySQL account; (<bugs_password>) above</P
-></LI
-></OL
->
- </P
-><P
->Once you are happy with the settings,
- <TT
-CLASS="filename"
->su</TT
-> to the user
- your web server runs as, and re-run
- <TT
-CLASS="filename"
->checksetup.pl</TT
->. (Note: on some security-conscious
- systems, you may need to change the login shell for the webserver
- account before you can do this.)
- On this second run, it will create the database and an administrator
- account for which you will be prompted to provide information.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The checksetup.pl script is designed so that you can run it at
- any time without causing harm. You should run it after any upgrade to
- Bugzilla.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN713"
-></A
->4.1.10. Configuring Bugzilla</H2
-><P
-> You should run through the parameters on the Edit Parameters page
- (link in the footer) and set them all to appropriate values.
- They key parameters are documented in <A
-HREF="parameters.html"
->Section 5.1</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Optional Additional Configuration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Troubleshooting</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Mac OS X Installation Notes"
-HREF="osx.html"><LINK
-REL="NEXT"
-TITLE="Administering Bugzilla"
-HREF="administration.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="osx.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="administration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="troubleshooting"
-></A
->4.5. Troubleshooting</H1
-><P
->This section gives solutions to common Bugzilla installation
- problems.
- </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1092"
-></A
->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
-><P
-> Try executing <B
-CLASS="command"
->perl -MCPAN -e 'install CPAN'</B
->
- and then continuing.
- </P
-><P
-> Certain older versions of the CPAN toolset were somewhat naive about how
- to upgrade Perl modules. When a couple of modules got rolled into the core
- Perl distribution for 5.6.1, CPAN thought that the best way to get those
- modules up to date was to haul down the Perl distribution itself and
- build it. Needless to say, this has caused headaches for just about
- everybody. Upgrading to a newer version of CPAN with the
- commandline above should fix things.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN1097"
-></A
->4.5.2. DBD::Sponge::db prepare failed</H2
-><P
-> The following error message may appear due to a bug in DBD::mysql
- (over which the Bugzilla team have no control):
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site/lib/DBD/mysql.pm line 248.
- SV = NULL(0x0) at 0x20fc444
- REFCNT = 1
- FLAGS = (PADBUSY,PADMY)
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> To fix this, go to
- <TT
-CLASS="filename"
-><path-to-perl>/lib/DBD/sponge.pm</TT
->
- in your Perl installation and replace
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAME'}) {
- $numFields = @{$attribs->{NAME}};
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> by
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAMES'}) {
- $numFields = @{$attribs->{NAMES}};
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> (note the S added to NAME.)
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="paranoid-security"
-></A
->4.5.3. cannot chdir(/var/spool/mqueue)</H2
-><P
->If you are installing Bugzilla on SuSE Linux, or some other
- distributions with
- <SPAN
-CLASS="QUOTE"
->"paranoid"</SPAN
->
- security options, it is possible that the checksetup.pl script may fail
- with the error:
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->cannot chdir(/var/spool/mqueue): Permission denied
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> This is because your
- <TT
-CLASS="filename"
->/var/spool/mqueue</TT
->
- directory has a mode of
- <SPAN
-CLASS="QUOTE"
->"drwx------"</SPAN
->. Type
- <B
-CLASS="command"
->chmod 755
- <TT
-CLASS="filename"
->/var/spool/mqueue</TT
->
- </B
->
- as root to fix this problem.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="trouble-filetemp"
-></A
->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
-><P
->This is caused by a bug in the version of
- <SPAN
-CLASS="productname"
->File::Temp</SPAN
-> that is distributed with perl
- 5.6.0. Many minor variations of this error have been reported. Examples
- can be found in <A
-HREF="troubleshooting.html#trouble-filetemp-errors"
->Figure 4-1</A
->.
- </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-errors"
-></A
-><P
-><B
->Figure 4-1. Other File::Temp error messages</B
-></P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> Your vendor has not defined Fcntl macro O_NOINHERIT, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
-
-Your vendor has not defined Fcntl macro O_EXLOCK, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
-
-Your vendor has not defined Fcntl macro O_TEMPORARY, used
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Numerous people have reported that upgrading to version 5.6.1
- or higher solved the problem for them. A less involved fix is to apply
- the patch in <A
-HREF="troubleshooting.html#trouble-filetemp-patch"
->Figure 4-2</A
->. The patch is also
- available as a <A
-HREF="../xml/filetemp.patch"
-TARGET="_top"
->patch file</A
->.
- </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-patch"
-></A
-><P
-><B
->Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
-></P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
-+++ File/Temp.pm Thu Feb 6 16:26:23 2003
-@@ -205,6 +205,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
-+ local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
-@@ -226,6 +227,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
-+ local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="osx.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Mac OS X Installation Notes</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Administering Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Upgrading to New Releases</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Template Customisation"
-HREF="cust-templates.html"><LINK
-REL="NEXT"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cust-templates.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="integration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="upgrading"
-></A
->5.8. Upgrading to New Releases</H1
-><P
->Upgrading Bugzilla is something we all want to do from time to time,
- be it to get new features or pick up the latest security fix. How easy
- it is to update depends on a few factors.
- </P
-><P
-></P
-><UL
-><LI
-><P
->If the new version is a revision or a new point release</P
-></LI
-><LI
-><P
->How many, if any, local changes have been made</P
-></LI
-></UL
-><P
->There are also three different methods to upgrade your installation.
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Using CVS (<A
-HREF="upgrading.html#upgrade-cvs"
->Example 5-1</A
->)</P
-></LI
-><LI
-><P
->Downloading a new tarball (<A
-HREF="upgrading.html#upgrade-tarball"
->Example 5-2</A
->)</P
-></LI
-><LI
-><P
->Applying the relevant patches (<A
-HREF="upgrading.html#upgrade-patches"
->Example 5-3</A
->)</P
-></LI
-></OL
-><P
->Which options are available to you may depend on how large a jump
- you are making and/or your network configuration.
- </P
-><P
->Revisions are normally released to fix security vulnerabilities
- and are distinguished by an increase in the third number. For example,
- when 2.16.2 was released, it was a revision to 2.16.1.
- </P
-><P
->Point releases are normally released when the Bugzilla team feels
- that there has been a significant amount of progress made between the
- last point release and the current time. These are often proceeded by a
- stabilization period and release candidates, however the use of
- development versions or release candidates is beyond the scope of this
- document. Point releases can be distinguished by an increase in the
- second number, or minor version. For example, 2.16.2 is a newer point
- release than 2.14.5.
- </P
-><P
->The examples in this section are written as if you were updating
- to version 2.16.2. The procedures are the same regardless if you are
- updating to a new point release or a new revision. However, the chance
- of running into trouble increases when upgrading to a new point release,
- escpecially if you've made local changes.
- </P
-><P
->These examples also assume that your Bugzilla installation is at
- <TT
-CLASS="filename"
->/var/www/html/bugzilla</TT
->. If that is not the case,
- simply substitute the proper paths where appropriate.
- </P
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-cvs"
-></A
-><P
-><B
->Example 5-1. Upgrading using CVS</B
-></P
-><P
->Every release of Bugzilla, whether it is a revision or a point
- release, is tagged in CVS. Also, every tarball we have distributed
- since version 2.12 has been primed for using CVS. This does, however,
- require that you are able to access cvs-mirror.mozilla.org on port
- 2401.
-
- <DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you can do this, updating using CVS is probably the most
- painless method, especially if you have a lot of local changes.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html/bugzilla</B
->
-bash$ <B
-CLASS="command"
->cvs login</B
->
-Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
-CVS password: <B
-CLASS="command"
->anonymous</B
->
-bash$ <B
-CLASS="command"
->cvs -q update -r BUGZILLA-2_16_2 -dP</B
->
-P checksetup.pl
-P collectstats.pl
-P globals.pl
-P docs/rel_notes.txt
-P template/en/default/list/quips.html.tmpl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If a line in the output from <B
-CLASS="command"
->cvs update</B
->
- begins with a <TT
-CLASS="computeroutput"
->C</TT
-> that represents a
- file with local changes that CVS was unable to properly merge. You
- need to resolve these conflicts manually before Bugzilla (or at
- least the portion using that file) will be usable.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You also need to run <B
-CLASS="command"
->./checksetup.pl</B
->
- before your Bugzilla upgrade will be complete.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-tarball"
-></A
-><P
-><B
->Example 5-2. Upgrading using the tarball</B
-></P
-><P
->If you are unable or unwilling to use CVS, another option that's
- always available is to download the latest tarball. This is the most
- difficult option to use, especially if you have local changes.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html</B
->
-bash$ <B
-CLASS="command"
->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B
->
-<EM
->Output omitted</EM
->
-bash$ <B
-CLASS="command"
->tar xzvf bugzilla-2.16.2.tar.gz</B
->
-bugzilla-2.16.2/
-bugzilla-2.16.2/.cvsignore
-bugzilla-2.16.2/1x1.gif
-<EM
->Output truncated</EM
->
-bash$ <B
-CLASS="command"
->cd bugzilla-2.16.2</B
->
-bash$ <B
-CLASS="command"
->cp ../bugzilla/localconfig* .</B
->
-bash$ <B
-CLASS="command"
->cp -r ../bugzilla/data .</B
->
-bash$ <B
-CLASS="command"
->cd ..</B
->
-bash$ <B
-CLASS="command"
->mv bugzilla bugzilla.old</B
->
-bash$ <B
-CLASS="command"
->mv bugzilla-2.16.2 bugzilla</B
->
-bash$ <B
-CLASS="command"
->cd bugzilla</B
->
-bash$ <B
-CLASS="command"
->./checksetup.pl</B
->
-<EM
->Output omitted</EM
->
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The <B
-CLASS="command"
->cp</B
-> commands both end with periods which
- is a very important detail, it tells the shell that the destination
- directory is the current working directory. Also, the period at the
- beginning of the <B
-CLASS="command"
->./checksetup.pl</B
-> is important and
- can not be omitted.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will now have to reapply any changes you have made to your
- local installation manually.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="example"
-><A
-NAME="upgrade-patches"
-></A
-><P
-><B
->Example 5-3. Upgrading using patches</B
-></P
-><P
->The Bugzilla team will normally make a patch file available for
- revisions to go from the most recent revision to the new one. You could
- also read the release notes and grab the patches attached to the
- mentioned bug, but it is safer to use the released patch file as
- sometimes patches get changed before they get checked in (for minor
- spelling fixes and the like). It is also theorectically possible to
- scour the fixed bug list and pick and choose which patches to apply
- from a point release, but this is not recommended either as what you'll
- end up with is a hodge podge Bugzilla that isn't really any version.
- This would also make it more difficult to upgrade in the future.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> bash$ <B
-CLASS="command"
->cd /var/www/html/bugzilla</B
->
-bash$ <B
-CLASS="command"
->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B
->
-<EM
->Output omitted</EM
->
-bash$ <B
-CLASS="command"
->gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B
->
-bash$ <B
-CLASS="command"
->patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B
->
-patching file checksetup.pl
-patching file collectstats.pl
-patching file globals.pl
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you do this, beware that this doesn't change the entires in
- your <TT
-CLASS="filename"
->CVS</TT
-> directory so it may make
- updates using CVS (<A
-HREF="upgrading.html#upgrade-cvs"
->Example 5-1</A
->) more difficult in the
- future.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cust-templates.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Template Customisation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->User Administration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Bugzilla Configuration"
-HREF="parameters.html"><LINK
-REL="NEXT"
-TITLE="Product, Component, Milestone, and Version Administration"
-HREF="programadmin.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="parameters.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="programadmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="useradmin"
-></A
->5.2. User Administration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="defaultuser"
-></A
->5.2.1. Creating the Default User</H2
-><P
->When you first run checksetup.pl after installing Bugzilla, it
- will prompt you for the administrative username (email address) and
- password for this "super user". If for some reason you delete
- the "super user" account, re-running checksetup.pl will again prompt
- you for this username and password.</P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you wish to add more administrative users, you must use the
- MySQL interface. Run "mysql" from the command line, and use these
- commands:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="prompt"
->mysql></TT
->
- <B
-CLASS="command"
->use bugs;</B
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
-> update profiles set groupset=0x7fffffffffffffff where login_name =
- "(user's login name)";
- </B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
->Yes, that is
- <EM
->fifteen</EM
->
-
- <SPAN
-CLASS="QUOTE"
->"f"</SPAN
->
-
- 's. A whole lot of f-ing going on if you want to create a new
- administator.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="manageusers"
-></A
->5.2.2. Managing Other Users</H2
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="createnewusers"
-></A
->5.2.2.1. Creating new users</H3
-><P
->Your users can create their own user accounts by clicking the
- "New Account" link at the bottom of each page (assuming they
- aren't logged in as someone else already.) However, should you
- desire to create user accounts ahead of time, here is how you do
- it.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->After logging in, click the "Users" link at the footer of
- the query page, and then click "Add a new user".</P
-></LI
-><LI
-><P
->Fill out the form presented. This page is self-explanatory.
- When done, click "Submit".</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Adding a user this way will
- <EM
->not</EM
->
-
- send an email informing them of their username and password.
- While useful for creating dummy accounts (watchers which
- shuttle mail to another system, for instance, or email
- addresses which are a mailing list), in general it is
- preferable to log out and use the
- <SPAN
-CLASS="QUOTE"
->"New Account"</SPAN
->
-
- button to create users, as it will pre-populate all the
- required fields and also notify the user of her account name
- and password.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="modifyusers"
-></A
->5.2.2.2. Modifying Users</H3
-><P
->To see a specific user, search for their login name
- in the box provided on the "Edit Users" page. To see all users,
- leave the box blank.</P
-><P
->You can search in different ways the listbox to the right
- of the text entry box. You can match by
- case-insensitive substring (the default),
- regular expression, or a
- <EM
->reverse</EM
->
- regular expression match, which finds every user name which does NOT
- match the regular expression. (Please see
- the <B
-CLASS="command"
->man regexp</B
->
- manual page for details on regular expression syntax.)
- </P
-><P
->Once you have found your user, you can change the following
- fields:</P
-><P
-></P
-><UL
-><LI
-><P
-> <EM
->Login Name</EM
->:
- This is generally the user's full email address. However, if you
- have are using the emailsuffix Param, this may just be the user's
- login name. Note that users can now change their login names
- themselves (to any valid email address.)
- </P
-></LI
-><LI
-><P
-> <EM
->Real Name</EM
->: The user's real name. Note that
- Bugzilla does not require this to create an account.</P
-></LI
-><LI
-><P
-> <EM
->Password</EM
->:
- You can change the user's password here. Users can automatically
- request a new password, so you shouldn't need to do this often.
- If you want to disable an account, see Disable Text below.
- </P
-></LI
-><LI
-><P
-> <EM
->Disable Text</EM
->:
- If you type anything in this box, including just a space, the
- user is prevented from logging in, or making any changes to
- bugs via the web interface.
- The HTML you type in this box is presented to the user when
- they attempt to perform these actions, and should explain
- why the account was disabled.
- <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't disable the administrator account!</P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The user can still submit bugs via
- the e-mail gateway, if you set it up, even if the disabled text
- field is filled in. The e-mail gateway should
- <EM
->not</EM
->
- be enabled for secure installations of Bugzilla.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> <EM
-><groupname></EM
->:
- If you have created some groups, e.g. "securitysensitive", then
- checkboxes will appear here to allow you to add users to, or
- remove them from, these groups.
- </P
-></LI
-><LI
-><P
-> <EM
->canconfirm</EM
->:
- This field is only used if you have enabled the "unconfirmed"
- status. If you enable this for a user,
- that user can then move bugs from "Unconfirmed" to a "Confirmed"
- status (e.g.: "New" status).</P
-></LI
-><LI
-><P
-> <EM
->creategroups</EM
->:
- This option will allow a user to create and destroy groups in
- Bugzilla.</P
-></LI
-><LI
-><P
-> <EM
->editbugs</EM
->:
- Unless a user has this bit set, they can only edit those bugs
- for which they are the assignee or the reporter. Even if this
- option is unchecked, users can still add comments to bugs.
- </P
-></LI
-><LI
-><P
-> <EM
->editcomponents</EM
->:
- This flag allows a user to create new products and components,
- as well as modify and destroy those that have no bugs associated
- with them. If a product or component has bugs associated with it,
- those bugs must be moved to a different product or component
- before Bugzilla will allow them to be destroyed.
- </P
-></LI
-><LI
-><P
-> <EM
->editkeywords</EM
->:
- If you use Bugzilla's keyword functionality, enabling this
- feature allows a user to create and destroy keywords. As always,
- the keywords for existing bugs containing the keyword the user
- wishes to destroy must be changed before Bugzilla will allow it
- to die.</P
-></LI
-><LI
-><P
-> <EM
->editusers</EM
->:
- This flag allows a user to do what you're doing right now: edit
- other users. This will allow those with the right to do so to
- remove administrator privileges from other users or grant them to
- themselves. Enable with care.</P
-></LI
-><LI
-><P
-> <EM
->tweakparams</EM
->:
- This flag allows a user to change Bugzilla's Params
- (using <TT
-CLASS="filename"
->editparams.cgi</TT
->.)</P
-></LI
-><LI
-><P
-> <EM
-><productname></EM
->:
- This allows an administrator to specify the products in which
- a user can see bugs. The user must still have the
- "editbugs" privilege to edit bugs in these products.</P
-></LI
-></UL
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="parameters.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="programadmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Configuration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Product, Component, Milestone, and Version Administration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->User Preferences</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Hints and Tips"
-HREF="hintsandtips.html"><LINK
-REL="NEXT"
-TITLE="Installation"
-HREF="installation.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="installation.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="userpreferences"
-></A
->3.3. User Preferences</H1
-><P
->Once you have logged in, you can customise various aspects of
- Bugzilla via the "Edit prefs" link in the page footer.
- The preferences are split into four tabs:</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="accountsettings"
-></A
->3.3.1. Account Settings</H2
-><P
->On this tab, you can change your basic account information,
- including your password, email address and real name. For security
- reasons, in order to change anything on this page you must type your
- <EM
->current</EM
->
- password into the
- <SPAN
-CLASS="QUOTE"
->"Password"</SPAN
->
- field at the top of the page.
- If you attempt to change your email address, a confirmation
- email is sent to both the old and new addresses, with a link to use to
- confirm the change. This helps to prevent account hijacking.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="emailsettings"
-></A
->3.3.2. Email Settings</H2
-><P
->On this tab you can reduce or increase the amount of email sent
- you from Bugzilla, opting in our out depending on your relationship to
- the bug and the change that was made to it. (Note that you can also do
- client-side filtering using the X-Bugzilla-Reason header which Bugzilla
- adds to all bugmail.)</P
-><P
->By entering user email names, delineated by commas, into the
- "Users to watch" text entry box you can receive a copy of all the
- bugmail of other users (security settings permitting.) This powerful
- functionality enables seamless transitions as developers change
- projects or users go on holiday.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The ability to watch other users may not be available in all
- Bugzilla installations. If you can't see it, ask your
- administrator.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="footersettings"
-></A
->3.3.3. Page Footer</H2
-><P
->On the Search page, you can store queries in Bugzilla, so if you
- regularly run a particular query it is just a drop-down menu away.
- Once you have a stored query, you can come
- here to request that it also be displayed in your page footer.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="permissionsettings"
-></A
->3.3.4. Permissions</H2
-><P
->This is a purely informative page which outlines your current
- permissions on this installation of Bugzilla - what product groups you
- are in, and whether you can edit bugs or perform various administration
- functions.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Hints and Tips</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Installation</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Using Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Why Should We Use Bugzilla?"
-HREF="why.html"><LINK
-REL="NEXT"
-TITLE="How do I use Bugzilla?"
-HREF="how.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="how.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="using"
-></A
->Chapter 3. Using Bugzilla</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->3.1. <A
-HREF="how.html"
->How do I use Bugzilla?</A
-></DT
-><DD
-><DL
-><DT
->3.1.1. <A
-HREF="how.html#myaccount"
->Create a Bugzilla Account</A
-></DT
-><DT
->3.1.2. <A
-HREF="how.html#bug_page"
->Anatomy of a Bug</A
-></DT
-><DT
->3.1.3. <A
-HREF="how.html#query"
->Searching for Bugs</A
-></DT
-><DT
->3.1.4. <A
-HREF="how.html#list"
->Bug Lists</A
-></DT
-><DT
->3.1.5. <A
-HREF="how.html#bugreports"
->Filing Bugs</A
-></DT
-></DL
-></DD
-><DT
->3.2. <A
-HREF="hintsandtips.html"
->Hints and Tips</A
-></DT
-><DD
-><DL
-><DT
->3.2.1. <A
-HREF="hintsandtips.html#AEN372"
->Autolinkification</A
-></DT
-><DT
->3.2.2. <A
-HREF="hintsandtips.html#quicksearch"
->Quicksearch</A
-></DT
-><DT
->3.2.3. <A
-HREF="hintsandtips.html#commenting"
->Comments</A
-></DT
-><DT
->3.2.4. <A
-HREF="hintsandtips.html#attachments"
->Attachments</A
-></DT
-><DT
->3.2.5. <A
-HREF="hintsandtips.html#AEN401"
->Filing Bugs</A
-></DT
-></DL
-></DD
-><DT
->3.3. <A
-HREF="userpreferences.html"
->User Preferences</A
-></DT
-><DD
-><DL
-><DT
->3.3.1. <A
-HREF="userpreferences.html#accountsettings"
->Account Settings</A
-></DT
-><DT
->3.3.2. <A
-HREF="userpreferences.html#emailsettings"
->Email Settings</A
-></DT
-><DT
->3.3.3. <A
-HREF="userpreferences.html#footersettings"
->Page Footer</A
-></DT
-><DT
->3.3.4. <A
-HREF="userpreferences.html#permissionsettings"
->Permissions</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="how.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Why Should We Use Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How do I use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Loki Bugzilla (Fenris)</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Red Hat Bugzilla"
-HREF="variant-redhat.html"><LINK
-REL="NEXT"
-TITLE="Issuezilla"
-HREF="variant-issuezilla.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-fenris"
-></A
->D.2. Loki Bugzilla (Fenris)</H1
-><P
->Fenris was a fork from Bugzilla made by Loki Games; when
- Loki went into receivership, it died. While Loki's other code lives on,
- its custodians recommend Bugzilla for future bug-tracker deployments.
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Red Hat Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Issuezilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Issuezilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Loki Bugzilla (Fenris)"
-HREF="variant-fenris.html"><LINK
-REL="NEXT"
-TITLE="Scarab"
-HREF="variant-scarab.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-issuezilla"
-></A
->D.3. Issuezilla</H1
-><P
->Issuezilla was another fork from Bugzilla, made by collab.net and
- hosted at tigris.org. It is also dead; the primary focus of bug-tracking
- at tigris.org is their Java-based bug-tracker,
- <A
-HREF="variant-scarab.html"
->Section D.4</A
->.</P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Loki Bugzilla (Fenris)</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Scarab</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Perforce SCM</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Scarab"
-HREF="variant-scarab.html"><LINK
-REL="NEXT"
-TITLE="SourceForge"
-HREF="variant-sourceforge.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-perforce"
-></A
->D.5. Perforce SCM</H1
-><P
->Although Perforce isn't really a bug tracker, it can be used as
- such through the <SPAN
-CLASS="QUOTE"
->"jobs"</SPAN
->
- functionality.</P
-><P
->URL:
- <A
-HREF="http://www.perforce.com/perforce/technotes/note052.html"
-TARGET="_top"
-> http://www.perforce.com/perforce/technotes/note052.html
- </A
->
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Scarab</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->SourceForge</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Red Hat Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="NEXT"
-TITLE="Loki Bugzilla (Fenris)"
-HREF="variant-fenris.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-redhat"
-></A
->D.1. Red Hat Bugzilla</H1
-><P
->Red Hat's old fork of Bugzilla which was based on version 2.8 is now
- obsolete. The newest version in use is based on version 2.17.1 and is in
- the process of being integrated into the main Bugzilla source tree. The
- back-end is modified to work with PostgreSQL instead of MySQL and they have
- custom templates to get their desired look and feel, but other than that it
- is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
- effort to make sure that the changes he made could be integrated back into
- the main tree.
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
-TARGET="_top"
->Bug
- 98304</A
-> exists to track this integration.
- </P
-><P
->URL:
- <A
-HREF="http://bugzilla.redhat.com/bugzilla/"
-TARGET="_top"
-> http://bugzilla.redhat.com/bugzilla/</A
->
- </P
-><P
->This section last updated 24 Dec 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Loki Bugzilla (Fenris)</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Scarab</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Issuezilla"
-HREF="variant-issuezilla.html"><LINK
-REL="NEXT"
-TITLE="Perforce SCM"
-HREF="variant-perforce.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-scarab"
-></A
->D.4. Scarab</H1
-><P
->Scarab is a new open source bug-tracking system built using Java
- Servlet technology. It is currently at version 1.0 beta 13.</P
-><P
->URL:
- <A
-HREF="http://scarab.tigris.org/"
-TARGET="_top"
->http://scarab.tigris.org</A
->
- </P
-><P
->This section last updated 18 Jan 2003</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Issuezilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Perforce SCM</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->SourceForge</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Perforce SCM"
-HREF="variant-perforce.html"><LINK
-REL="NEXT"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-sourceforge"
-></A
->D.6. SourceForge</H1
-><P
->SourceForge is a way of coordinating geographically
- distributed free software and open source projects over the Internet.
- It has a built-in bug tracker, but it's not highly thought of.</P
-><P
->URL:
- <A
-HREF="http://www.sourceforge.net"
-TARGET="_top"
-> http://www.sourceforge.net</A
->
- </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Perforce SCM</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->GNU Free Documentation License</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Bugzilla Variants and Competitors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Command-line Bugzilla Queries"
-HREF="cmdline.html"><LINK
-REL="NEXT"
-TITLE="Red Hat Bugzilla"
-HREF="variant-redhat.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="variants"
-></A
->Appendix D. Bugzilla Variants and Competitors</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->D.1. <A
-HREF="variant-redhat.html"
->Red Hat Bugzilla</A
-></DT
-><DT
->D.2. <A
-HREF="variant-fenris.html"
->Loki Bugzilla (Fenris)</A
-></DT
-><DT
->D.3. <A
-HREF="variant-issuezilla.html"
->Issuezilla</A
-></DT
-><DT
->D.4. <A
-HREF="variant-scarab.html"
->Scarab</A
-></DT
-><DT
->D.5. <A
-HREF="variant-perforce.html"
->Perforce SCM</A
-></DT
-><DT
->D.6. <A
-HREF="variant-sourceforge.html"
->SourceForge</A
-></DT
-></DL
-></DIV
-><P
->I created this section to answer questions about Bugzilla competitors
- and variants, then found a wonderful site which covers an awful lot of what
- I wanted to discuss. Rather than quote it in its entirety, I'll simply
- refer you here:
- <A
-HREF="http://linas.org/linux/pm.html"
-TARGET="_top"
-> http://linas.org/linux/pm.html</A
->
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Red Hat Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Voting</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Product, Component, Milestone, and Version Administration"
-HREF="programadmin.html"><LINK
-REL="NEXT"
-TITLE="Groups and Group Security"
-HREF="groups.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="programadmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="groups.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="voting"
-></A
->5.4. Voting</H1
-><P
->Voting allows users to be given a pot of votes which they can allocate
- to bugs, to indicate that they'd like them fixed.
- This allows developers to gauge
- user need for a particular enhancement or bugfix. By allowing bugs with
- a certain number of votes to automatically move from "UNCONFIRMED" to
- "NEW", users of the bug system can help high-priority bugs garner
- attention so they don't sit for a long time awaiting triage.</P
-><P
->To modify Voting settings:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Navigate to the "Edit product" screen for the Product you
- wish to modify</P
-></LI
-><LI
-><P
-><EM
->Maximum Votes per person</EM
->:
- Setting this field to "0" disables voting.</P
-></LI
-><LI
-><P
-><EM
->Maximum Votes a person can put on a single
- bug"</EM
->:
- It should probably be some number lower than the
- "Maximum votes per person". Don't set this field to "0" if
- "Maximum votes per person" is non-zero; that doesn't make
- any sense.</P
-></LI
-><LI
-><P
-><EM
->Number of votes a bug in this product needs to
- automatically get out of the UNCONFIRMED state</EM
->:
- Setting this field to "0" disables the automatic move of
- bugs from UNCONFIRMED to NEW.
- </P
-></LI
-><LI
-><P
->Once you have adjusted the values to your preference, click
- "Update".</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="programadmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="groups.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Product, Component, Milestone, and Version Administration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Groups and Group Security</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->What is Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="NEXT"
-TITLE="Why Should We Use Bugzilla?"
-HREF="why.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="whatis"
-></A
->2.1. What is Bugzilla?</H1
-><P
-> Bugzilla is a bug- or issue-tracking system. Bug-tracking
- systems allow individual or groups of developers effectively to keep track
- of outstanding problems with their product.
- Bugzilla was originally written by Terry Weissman in a programming language
- called <A
-HREF="glossary.html#gloss-tcl"
-><I
-CLASS="glossterm"
->TCL</I
-></A
->, to
- replace a rudimentary bug-tracking database used internally by Netscape
- Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
- it remains to this day. Most commercial defect-tracking software vendors
- at the time charged enormous licensing fees, and Bugzilla quickly became
- a favorite of the open-source crowd (with its genesis in the open-source
- browser project, Mozilla). It is now the de-facto standard
- defect-tracking system against which all others are measured.
- </P
-><P
->Bugzilla boasts many advanced features. These include:
- <P
-></P
-><UL
-><LI
-><P
->Powerful searching</P
-></LI
-><LI
-><P
->User-configurable email notifications of bug changes</P
-></LI
-><LI
-><P
->Full change history</P
-></LI
-><LI
-><P
->Inter-bug dependency tracking and graphing</P
-></LI
-><LI
-><P
->Excellent attachment management</P
-></LI
-><LI
-><P
->Integrated, product-based, granular security schema</P
-></LI
-><LI
-><P
->Fully security-audited, and runs under Perl's taint mode</P
-></LI
-><LI
-><P
->A robust, stable RDBMS back-end</P
-></LI
-><LI
-><P
->Web, XML, email and console interfaces</P
-></LI
-><LI
-><P
->Completely customisable and/or localisable web user
- interface</P
-></LI
-><LI
-><P
->Extensive configurability</P
-></LI
-><LI
-><P
->Smooth upgrade pathway between versions</P
-></LI
-></UL
->
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Why Should We Use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Why Should We Use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="What is Bugzilla?"
-HREF="whatis.html"><LINK
-REL="NEXT"
-TITLE="Using Bugzilla"
-HREF="using.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="whatis.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="why"
-></A
->2.2. Why Should We Use Bugzilla?</H1
-><P
->For many years, defect-tracking software has remained principally
- the domain of large software development houses. Even then, most shops
- never bothered with bug-tracking software, and instead simply relied on
- shared lists and email to monitor the status of defects. This procedure
- is error-prone and tends to cause those bugs judged least significant by
- developers to be dropped or ignored.</P
-><P
->These days, many companies are finding that integrated
- defect-tracking systems reduce downtime, increase productivity, and raise
- customer satisfaction with their systems. Along with full disclosure, an
- open bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout the
- data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support
- accountability, telephone support knowledge bases, and a common,
- well-understood system for accounting for unusual system or software
- issues.</P
-><P
->But why should
- <EM
->you</EM
->
-
- use Bugzilla?</P
-><P
->Bugzilla is very adaptable to various situations. Known uses
- currently include IT support queues, Systems Administration deployment
- management, chip design and development problem tracking (both
- pre-and-post fabrication), and software and hardware bug tracking for
- luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as
- <A
-HREF="http://www.cvshome.org"
-TARGET="_top"
->CVS</A
->,
- <A
-HREF="http://www.mozilla.org/bonsai.html"
-TARGET="_top"
->Bonsai</A
->, or
- <A
-HREF="http://www.perforce.com"
-TARGET="_top"
->Perforce SCM</A
->, Bugzilla
- provides a powerful, easy-to-use solution to configuration management and
- replication problems.</P
-><P
->Bugzilla can dramatically increase the productivity and
- accountability of individual employees by providing a documented workflow
- and positive feedback for good performance. How many times do you wake up
- in the morning, remembering that you were supposed to do
- <EM
->something</EM
->
- today, but you just can't quite remember? Put it in Bugzilla, and you
- have a record of it from which you can extrapolate milestones, predict
- product versions for integration, and follow the discussion trail
- that led to critical decisions.</P
-><P
->Ultimately, Bugzilla puts the power in your hands to improve your
- value to your employer or business while providing a usable framework for
- your natural attention to detail and knowledge store to flourish.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="whatis.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->What is Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->Win32 Installation Notes</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.16.4 Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Optional Additional Configuration"
-HREF="extraconfig.html"><LINK
-REL="NEXT"
-TITLE="Mac OS X Installation Notes"
-HREF="osx.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.16.4 Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="osx.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="win32"
-></A
->4.3. Win32 Installation Notes</H1
-><P
->This section covers installation on Microsoft Windows.
- Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
- wish to emphasise that The easiest way to install Bugzilla on
- Intel-archiecture machines
- is to install some variant of GNU/Linux, then follow the UNIX
- installation instructions in this Guide. If you have any influence in the
- platform choice for running this system, please choose GNU/Linux instead
- of Microsoft Windows.</P
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->After that warning, here's the situation for 2.16
- and Windows. It doesn't work at all out of the box.
- You are almost certainly better off getting
- the 2.17 version from CVS (after consultation with the Bugzilla Team to
- make sure you are pulling on a stable day) because we'll be doing a load
- of work to make the Win32 experience more pleasant than it is now.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
-> If you still want to try this, to have any hope of getting it to work,
- you'll need to apply the
- <A
-HREF=""
-TARGET="_top"
->mail patch</A
-> from
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=124174"
-TARGET="_top"
->bug 124174</A
->.
- After that, you'll need to read the (outdated) installation
- instructions below, some (probably a lot better) <A
-HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view"
-TARGET="_top"
->more
- recent ones</A
-> kindly provided by Toms Baugis and Jean-Sebastien
- Guay, and also check the
- <A
-HREF="http://www.bugzilla.org/releases/2.16/docs/win32.html"
-TARGET="_top"
->Bugzilla 2.16 Win32 update page
- </A
->. If we get time,
- we'll write some better installation instructions for 2.16 and put
- them up there. But no promises.
- </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="wininstall"
-></A
->4.3.1. Win32 Installation: Step-by-step</H2
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You should be familiar with, and cross-reference, the rest of
- the
- <A
-HREF="installation.html"
->Bugzilla Installation</A
->
-
- section while performing your Win32 installation.</P
-><P
->Making Bugzilla work on Microsoft Windows is no picnic. Support
- for Win32 has improved dramatically in the last few releases, but, if
- you choose to proceed, you should be a
- <EM
->very</EM
->
-
- skilled Windows Systems Administrator with strong troubleshooting
- abilities, a high tolerance for pain, and moderate perl skills.
- Bugzilla on NT requires hacking source code and implementing some
- advanced utilities. What follows is the recommended installation
- procedure for Win32; additional suggestions are provided in
- <A
-HREF="faq.html"
->Appendix A</A
->
-
- .</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->Install
- <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache Web Server</A
->
-
- for Windows, and copy the Bugzilla files somewhere Apache can serve
- them. Please follow all the instructions referenced in
- <A
-HREF="installation.html"
->Bugzilla Installation</A
->
-
- regarding your Apache configuration, particularly instructions
- regarding the
- <SPAN
-CLASS="QUOTE"
->"AddHandler"</SPAN
->
-
- parameter and
- <SPAN
-CLASS="QUOTE"
->"ExecCGI"</SPAN
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You may also use Internet Information Server or Personal
- Web Server for this purpose. However, setup is quite different.
- If ActivePerl doesn't seem to handle your file associations
- correctly (for .cgi and .pl files), please consult
- <A
-HREF="faq.html"
->Appendix A</A
->
-
- .</P
-><P
->If you are going to use IIS, if on Windows NT you must be
- updated to at least Service Pack 4. Windows 2000 ships with a
- sufficient version of IIS.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Install
- <A
-HREF="http://www.activestate.com/"
-TARGET="_top"
->ActivePerl</A
->
-
- for Windows. Check
- <A
-HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
-TARGET="_top"
-> http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A
->
-
- for a current compiled binary.</P
-><P
->Please also check the following links to fully understand the
- status of ActivePerl on Win32:
- <A
-HREF="http://language.perl.com/newdocs/pod/perlport.html"
-TARGET="_top"
-> Perl Porting</A
->
-
- , and
- <A
-HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
-TARGET="_top"
-> Perl on Win32 FAQ</A
->
- </P
-></LI
-><LI
-><P
->Use ppm from your perl\bin directory to install the following
- packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
- AppConfig, and Template. You may need to extract them from .zip
- format using Winzip or other unzip program first. Most of these
- additional ppm modules can be downloaded from ActiveState, but
- AppConfig and Template should be obtained from OpenInteract using
- <A
-HREF="http://openinteract.sourceforge.net/"
-TARGET="_top"
->the
- instructions on the Template Toolkit web site</A
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can find a list of modules at
- <A
-HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
->
-
- or
- <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The syntax for ppm is:
- <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->ppm <modulename></B
->
- </TT
->
- </P
-><DIV
-CLASS="example"
-><A
-NAME="AEN863"
-></A
-><P
-><B
->Example 4-1. Installing ActivePerl ppd Modules on Microsoft
- Windows</B
-></P
-><P
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->ppm
- <TT
-CLASS="option"
->DBD-Mysql</TT
->
- </B
->
- </P
-><P
->Watch your capitalization!</P
-></DIV
-><P
->ActiveState's 5.6Plus directory also contains an AppConfig
- ppm, so you might see the following error when trying to install
- the version at OpenInteract:</P
-><P
-> <TT
-CLASS="computeroutput"
->Error installing package 'AppConfig': Read a PPD
- for 'AppConfig', but it is not intended for this build of Perl
- (MSWin32-x86-multi-thread)</TT
->
- </P
-><P
->If so, download both
- <A
-HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.tar.gz"
-TARGET="_top"
-> the tarball</A
->
-
- and
- <A
-HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.ppd"
-TARGET="_top"
-> the ppd</A
->
-
- directly from OpenInteract, then run ppm from within the same
- directory to which you downloaded those files and install the
- package by referencing the ppd file explicitly via in the install
- command, f.e.:
- <DIV
-CLASS="example"
-><A
-NAME="AEN876"
-></A
-><P
-><B
->Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
- Windows</B
-></P
-><P
-> <TT
-CLASS="computeroutput"
-> <B
-CLASS="command"
->install
- <TT
-CLASS="filename"
->C:\AppConfig.ppd</TT
->
- </B
->
- </TT
->
- </P
-></DIV
->
- </P
-></LI
-><LI
-><P
->Install MySQL for NT.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You can download MySQL for Windows NT from
- <A
-HREF="http://www.mysql.com/"
-TARGET="_top"
->MySQL.com</A
->
-
- . Some find it helpful to use the WinMySqlAdmin utility, included
- with the download, to set up the database.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
->Setup MySQL</P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->C:\mysql\bin\mysql -u root mysql</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->DELETE FROM user WHERE Host='localhost' AND
- User='';</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';</B
->
- </TT
->
- </P
-><P
-> <SPAN
-CLASS="QUOTE"
->"new_password"</SPAN
->
-
- , above, indicates whatever password you wish to use for your
- <SPAN
-CLASS="QUOTE"
->"root"</SPAN
->
-
- user.</P
-></LI
-><LI
-><A
-NAME="ntbugs-password"
-></A
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->GRANT SELECT, INSERT, UPDATE, DELETE, INDEX,
- ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
->
- </TT
->
- </P
-><P
-> <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- , above, indicates whatever password you wish to use for your
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- user.</P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->create database bugs;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->exit;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->C:></TT
->
-
- <B
-CLASS="command"
->C:\mysql\bin\mysqladmin -u root -p
- reload</B
->
- </TT
->
- </P
-></LI
-></OL
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- in your Bugzilla directory. Change this line:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- getgrnam($my_webservergroup);</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->to</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- $my_webservergroup;</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- or the name of the group you wish to own the files explicitly:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $webservergid =
- 'Administrators'</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></LI
-><LI
-><P
->Run
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
-
- from the Bugzilla directory.</P
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->localconfig</TT
->
-
- to suit your requirements. Set
- <TT
-CLASS="varname"
->$db_pass</TT
->
-
- to your
- <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- from
- <A
-HREF="win32.html#ntbugs-password"
->step 5.d</A
->
-
- , and
- <TT
-CLASS="varname"
->$webservergroup</TT
->
-
- to
- <SPAN
-CLASS="QUOTE"
->"8"</SPAN
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Not sure on the
- <SPAN
-CLASS="QUOTE"
->"8"</SPAN
->
-
- for
- <TT
-CLASS="varname"
->$webservergroup</TT
->
-
- above. If it's wrong, please send corrections.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Edit
- <TT
-CLASS="filename"
->defparams.pl</TT
->
-
- to suit your requirements. Particularly, set
- <TT
-CLASS="varname"
->DefParam("maintainer")</TT
->
-
- and
- <TT
-CLASS="varname"
->DefParam("urlbase") to match your install.</TT
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This is yet another step I'm not sure of, since the
- maintainer of this documentation does not maintain Bugzilla on
- NT. If you can confirm or deny that this step is required, please
- let me know.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->There are several alternatives to Sendmail that will work
- on Win32. The one mentioned here is a
- <EM
->suggestion</EM
->
-
- , not a requirement. Some other mail packages that can work
- include
- <A
-HREF="http://www.blat.net/"
-TARGET="_top"
->BLAT</A
->
-
- ,
- <A
-HREF="http://www.geocel.com/windmail/"
-TARGET="_top"
->Windmail</A
->
-
- ,
- <A
-HREF="http://www.dynamicstate.com/"
-TARGET="_top"
->Mercury
- Sendmail</A
->
-
- , and the CPAN Net::SMTP Perl module (available in .ppm). Every
- option requires some hacking of the Perl scripts for Bugzilla to
- make it work. The option here simply requires the least.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->Download NTsendmail, available from
- <A
-HREF="http://www.ntsendmail.com/"
-TARGET="_top"
-> www.ntsendmail.com</A
->
-
- . You must have a "real" mail server which allows you to relay
- off it in your $ENV{"NTsendmail"} (which you should probably
- place in globals.pl)</P
-></LI
-><LI
-><P
->Put ntsendmail.pm into your .\perl\lib directory.</P
-></LI
-><LI
-><P
->Add to globals.pl:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-># these settings configure the NTsendmail
- process use NTsendmail;
- $ENV{"NTsendmail"}="your.smtpserver.box";
- $ENV{"NTsendmail_debug"}=1;
- $ENV{"NTsendmail_max_tries"}=5;</PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some mention to also edit
- <TT
-CLASS="varname"
->$db_pass</TT
->
-
- in
- <TT
-CLASS="filename"
->globals.pl</TT
->
-
- to be your
- <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->
-
- . Although this may get you around some problem
- authenticating to your database, since globals.pl is not
- normally restricted by
- <TT
-CLASS="filename"
->.htaccess</TT
->
-
- , your database password is exposed to whoever uses your web
- server.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Find and comment out all occurences of
- <SPAN
-CLASS="QUOTE"
->"
- <B
-CLASS="command"
->open(SENDMAIL</B
->
- "</SPAN
->
-
- in your Bugzilla directory. Then replace them with:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-># new sendmail functionality my $mail=new
- NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
- $to=$login; my $subject=$urlbase;
- $mail->send($from,$to,$subject,$msg);</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some have found success using the commercial product,
- <SPAN
-CLASS="productname"
->Windmail</SPAN
->
-
- . You could try replacing your sendmail calls with:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->open SENDMAIL,
- "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
- mail.log";</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- or something to that effect.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-></LI
-><LI
-><P
->Change all references in all files from
- <TT
-CLASS="filename"
->processmail</TT
->
-
- to
- <TT
-CLASS="filename"
->processmail.pl</TT
->
-
- , and rename
- <TT
-CLASS="filename"
->processmail</TT
->
-
- to
- <TT
-CLASS="filename"
->processmail.pl</TT
->
-
- .</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Many think this may be a change we want to make for
- main-tree Bugzilla. It's painless for the UNIX folks, and will
- make the Win32 people happier.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Some people have suggested using the Net::SMTP Perl module
- instead of NTsendmail or the other options listed here. You can
- change processmail.pl to make this work.
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-
-my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
-$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
-$smtp->to($tolist); # recipient's address
-$smtp->data(); # Start the mail
-$smtp->datasend($msg);
-$smtp->dataend(); # Finish sending the mail
-$smtp->quit; # Close the SMTP connection
-$logstr = "$logstr; mail sent to $tolist $cclist";
-}
-
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- here is a test mail program for Net::SMTP:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-
-use Net::SMTP;
- my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
-=> 1, ); # connect to SMTP server
- $smtp->auth;
- $smtp->mail('you@yourcompany.com');# use the sender's adress
-here
- $smtp->to('someotherAddress@someotherdomain.com'); #
-recipient's address
- $smtp->data(); # Start the mail
- $smtp->datasend('test');
- $smtp->dataend(); # Finish sending the mail
- $smtp->quit; # Close the SMTP connection
-exit;
-
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This step is optional if you are using IIS or another web
- server which only decides on an interpreter based upon the file
- extension (.pl), rather than the
- <SPAN
-CLASS="QUOTE"
->"shebang"</SPAN
->
-
- line (#/usr/bonsaitools/bin/perl)</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Modify the path to perl on the first line (#!) of all files
- to point to your Perl installation, and add
- <SPAN
-CLASS="QUOTE"
->"perl"</SPAN
->
-
- to the beginning of all Perl system calls that use a perl script as
- an argument. This may take you a while. There is a
- <SPAN
-CLASS="QUOTE"
->"setperl.csh"</SPAN
->
-
- utility to speed part of this procedure, available in the
- <A
-HREF="patches.html"
->Useful Patches and Utilities for Bugzilla</A
->
-
- section of The Bugzilla Guide. However, it requires the Cygwin
- GNU-compatible environment for Win32 be set up in order to work.
- See
- <A
-HREF="http://www.cygwin.com/"
-TARGET="_top"
->http://www.cygwin.com/</A
->
-
- for details on obtaining Cygwin.</P
-></LI
-><LI
-><P
->Modify the invocation of all system() calls in all perl
- scripts in your Bugzilla directory. You should specify the full
- path to perl for each system() call. For instance, change this line
- in processmail:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-system ("./processmail",@ARGLIST);
- </programlisting> to
- <programlisting>
-system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-></LI
-><LI
-><P
->Add
- <TT
-CLASS="function"
->binmode()</TT
->
-
- calls so attachments will work (
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
-TARGET="_top"
->bug
- 62000</A
->
-
- ).</P
-><P
->Because Microsoft Windows based systems handle binary files
- different than Unix based systems, you need to add the following
- lines to
- <TT
-CLASS="filename"
->createattachment.cgi</TT
->
-
- and
- <TT
-CLASS="filename"
->showattachment.cgi</TT
->
-
- before the
- <TT
-CLASS="function"
->require 'CGI.pl';</TT
->
-
- line.</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->
-binmode(STDIN);
-binmode(STDOUT);
-
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->According to
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
-TARGET="_top"
-> bug 62000</A
->
-
- , the perl documentation says that you should always use
- <TT
-CLASS="function"
->binmode()</TT
->
-
- when dealing with binary files, but never when dealing with text
- files. That seems to suggest that rather than arbitrarily putting
-
- <TT
-CLASS="function"
->binmode()</TT
->
-
- at the beginning of the attachment files, there should be logic
- to determine if
- <TT
-CLASS="function"
->binmode()</TT
->
-
- is needed or not.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using IIS or Personal Web Server, you must add cgi
- relationships to Properties -> Home directory (tab) ->
- Application Settings (section) -> Configuration (button), such
- as:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->.cgi to: <perl install directory>\perl.exe %s
- %s .pl to: <perl install directory>\perl.exe %s %s
- GET,HEAD,POST</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- Change the path to Perl to match your install, of course.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="addlwintips"
-></A
->4.3.2. Additional Windows Tips</H2
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->From Andrew Pearson:
- <A
-NAME="AEN1046"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
- <A
-HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
-TARGET="_top"
-> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
->
- </P
-><P
->Basically you need to add two String Keys in the registry at
- the following location:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
- </P
-><P
->The keys should be called ".pl" and ".cgi", and both should
- have a value something like:
- <B
-CLASS="command"
->c:/perl/bin/perl.exe "%s" "%s"</B
->
- </P
-><P
->The KB article only talks about .pl, but it goes into more
- detail and provides a perl test script.</P
-></BLOCKQUOTE
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If attempting to run Bugzilla 2.12 or older, you will need to
- remove encrypt() calls from the Perl source. This is
- <EM
->not necessary</EM
->
-
- for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla 2.16.4.
- <DIV
-CLASS="example"
-><A
-NAME="AEN1058"
-></A
-><P
-><B
->Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier</B
-></P
-><P
->Replace this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
- ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
- $enteredcryptpwd = FetchOneColumn();</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- with this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->my $enteredcryptpwd = $enteredpwd</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-
- in cgi.pl.</P
-></DIV
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="osx.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Optional Additional Configuration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Mac OS X Installation Notes</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-The Bugzilla Guide - 2.16.4 Release
-
-Matthew P. Barnson
-
-The Bugzilla Team
-
- 2003-11-01
-
- This is the documentation for Bugzilla, the mozilla.org bug-tracking
- system. Bugzilla is an enterprise-class piece of software that powers
- issue-tracking for hundreds of organizations around the world,
- tracking millions of bugs.
-
- This documentation is maintained in DocBook 4.1.2 XML format. Changes
- are best submitted as plain text or XML diffs, attached to a bug filed
- in mozilla.org's Bugzilla.
-
- The most current version of this document can always be found on the
- Bugzilla Documentation Page.
- _________________________________________________________________
-
- Table of Contents
- 1. About This Guide
-
- 1.1. Copyright Information
- 1.2. Disclaimer
- 1.3. New Versions
- 1.4. Credits
- 1.5. Document Conventions
-
- 2. Introduction
-
- 2.1. What is Bugzilla?
- 2.2. Why Should We Use Bugzilla?
-
- 3. Using Bugzilla
-
- 3.1. How do I use Bugzilla?
- 3.2. Hints and Tips
- 3.3. User Preferences
-
- 4. Installation
-
- 4.1. Step-by-step Install
- 4.2. Optional Additional Configuration
- 4.3. Win32 Installation Notes
- 4.4. Mac OS X Installation Notes
- 4.5. Troubleshooting
-
- 5. Administering Bugzilla
-
- 5.1. Bugzilla Configuration
- 5.2. User Administration
- 5.3. Product, Component, Milestone, and Version Administration
- 5.4. Voting
- 5.5. Groups and Group Security
- 5.6. Bugzilla Security
- 5.7. Template Customisation
- 5.8. Upgrading to New Releases
- 5.9. Integrating Bugzilla with Third-Party Tools
-
- A. The Bugzilla FAQ
- B. The Bugzilla Database
-
- B.1. Database Schema Chart
- B.2. MySQL Bugzilla Database Introduction
-
- C. Useful Patches and Utilities for Bugzilla
-
- C.1. Apache mod_rewrite magic
- C.2. Command-line Bugzilla Queries
-
- D. Bugzilla Variants and Competitors
-
- D.1. Red Hat Bugzilla
- D.2. Loki Bugzilla (Fenris)
- D.3. Issuezilla
- D.4. Scarab
- D.5. Perforce SCM
- D.6. SourceForge
-
- E. GNU Free Documentation License
-
- 0. PREAMBLE
- 1. APPLICABILITY AND DEFINITIONS
- 2. VERBATIM COPYING
- 3. COPYING IN QUANTITY
- 4. MODIFICATIONS
- 5. COMBINING DOCUMENTS
- 6. COLLECTIONS OF DOCUMENTS
- 7. AGGREGATION WITH INDEPENDENT WORKS
- 8. TRANSLATION
- 9. TERMINATION
- 10. FUTURE REVISIONS OF THIS LICENSE
- How to use this License for your documents
-
- Glossary
-
- List of Figures
- 4-1. Other File::Temp error messages
- 4-2. Patch for File::Temp in Perl 5.6.0
-
- List of Examples
- 4-1. Installing ActivePerl ppd Modules on Microsoft Windows
- 4-2. Installing OpenInteract ppd Modules manually on Microsoft Windows
- 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier
-
- 5-1. Upgrading using CVS
- 5-2. Upgrading using the tarball
- 5-3. Upgrading using patches
- _________________________________________________________________
-
-Chapter 1. About This Guide
-
-1.1. Copyright Information
-
-
-
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with no
- Invariant Sections, no Front-Cover Texts, and with no Back-Cover
- Texts. A copy of the license is included in Appendix E.
-
- --Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team
-
- If you have any questions regarding this document, its copyright, or
- publishing this document in non-electronic form, please contact The
- Bugzilla Team.
- _________________________________________________________________
-
-1.2. Disclaimer
-
- No liability for the contents of this document can be accepted. Use
- the concepts, examples, and other content at your own risk. This
- document may contain errors and inaccuracies that may damage your
- system, cause your partner to leave you, your boss to fire you, your
- cats to pee on your furniture and clothing, and global thermonuclear
- war. Proceed with caution.
-
- All copyrights are held by their respective owners, unless
- specifically noted otherwise. Use of a term in this document should
- not be regarded as affecting the validity of any trademark or service
- mark.
-
- Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". We
- wholeheartedly endorse the use of GNU/Linux in every situation where
- it is appropriate. It is an extremely versatile, stable, and robust
- operating system that offers an ideal operating environment for
- Bugzilla.
-
- You are strongly recommended to make a backup of your system before
- installing Bugzilla and at regular intervals thereafter. If you
- implement any suggestion in this Guide, implement this one!
-
- Although the Bugzilla development team has taken great care to ensure
- that all easily-exploitable bugs or options are documented or fixed in
- the code, security holes surely exist. Great care should be taken both
- in the installation and usage of this software. Carefully consider the
- implications of installing other network services with Bugzilla. The
- Bugzilla development team members, Netscape Communications, America
- Online Inc., and any affiliated developers or sponsors assume no
- liability for your use of this product. You have the source code to
- this product, and are responsible for auditing it yourself to ensure
- your security needs are met.
- _________________________________________________________________
-
-1.3. New Versions
-
- This is the 2.16.4 version of The Bugzilla Guide. It is so named to
- match the version of Bugzilla it is disributed with. If you are
- reading this from any source other than those below, please check one
- of these mirrors to make sure you are reading an up-to-date version of
- the Guide.
-
- The newest version of this guide can always be found at bugzilla.org;
- including documentation for past releases and the current development
- version.
-
- The documentation for the most recent stable release of Bugzilla can
- also be found at The Linux Documentation Project.
-
- The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at the Mozilla CVS page, and
- check out the mozilla/webtools/bugzilla/docs/ subtree.
-
- The Bugzilla Guide is currently only available in English. If you
- would like to volunteer to translate it, please contact Dave Miller.
- _________________________________________________________________
-
-1.4. Credits
-
- The people listed below have made enormous contributions to the
- creation of this Guide, through their writing, dedicated hacking
- efforts, numerous e-mail and IRC support sessions, and overall
- excellent contribution to the Bugzilla community:
-
- Matthew P. Barnson <mbarnson@sisna.com>
- for the Herculaean task of pulling together the Bugzilla Guide
- and shepherding it to 2.14.
-
- Terry Weissman <terry@mozilla.org>
- for initially writing Bugzilla and creating the README upon
- which the UNIX installation documentation is largely based.
-
- Tara Hernandez <tara@tequilarists.org>
- for keeping Bugzilla development going strong after Terry left
- mozilla.org and for running landfill.
-
- Dave Lawrence <dkl@redhat.com>
- for providing insight into the key differences between Red
- Hat's customized Bugzilla, and being largely responsible for
- Section D.1.
-
- Dawn Endico <endico@mozilla.org>
- for being a hacker extraordinaire and putting up with Matthew's
- incessant questions and arguments on irc.mozilla.org in
- #mozwebtools
-
- Jacob Steenhagen <jake@bugzilla.org>
- for taking over documentation during the 2.17 development
- period and backporting relevent docs changes to this 2.16
- branch.
-
- Last but not least, all the members of the
- news://news.mozilla.org/netscape/public/mozilla/webtools newsgroup.
- Without your discussions, insight, suggestions, and patches, this
- could never have happened.
-
- Thanks also go to the following people for significant contributions
- to this documentation (in alphabetical order): Andrew Pearson, Ben
- FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen,
- Ron Teitelbaum, Spencer Smith, Zach Liption .
- _________________________________________________________________
-
-1.5. Document Conventions
-
- This document uses the following conventions:
-
- Descriptions Appearance
- Use caution
-
-
- Caution
-
- Don't run with scissors!
- Hint
-
-
- Tip
-
- Would you like a breath mint?
- Notes
-
-
- Note
-
- Dear John...
- Warnings
-
-
- Warning
-
- Read this or the cat gets it.
- File Names filename
- Directory Names directory
- Commands to be typed command
- Applications Names application
- Prompt of users command under bash shell bash$
- Prompt of root users command under bash shell bash#
- Prompt of user command under tcsh shell tcsh$
- Environment Variables VARIABLE
- Emphasized word word
- Term found in the glossary Bugzilla
- Code Example
- <para>
- Beginning and end of paragraph
- </para>
- _________________________________________________________________
-
-Chapter 2. Introduction
-
-2.1. What is Bugzilla?
-
- Bugzilla is a bug- or issue-tracking system. Bug-tracking systems
- allow individual or groups of developers effectively to keep track of
- outstanding problems with their product. Bugzilla was originally
- written by Terry Weissman in a programming language called TCL, to
- replace a rudimentary bug-tracking database used internally by
- Netscape Communications. Terry later ported Bugzilla to Perl from TCL,
- and in Perl it remains to this day. Most commercial defect-tracking
- software vendors at the time charged enormous licensing fees, and
- Bugzilla quickly became a favorite of the open-source crowd (with its
- genesis in the open-source browser project, Mozilla). It is now the
- de-facto standard defect-tracking system against which all others are
- measured.
-
- Bugzilla boasts many advanced features. These include:
-
- * Powerful searching
- * User-configurable email notifications of bug changes
- * Full change history
- * Inter-bug dependency tracking and graphing
- * Excellent attachment management
- * Integrated, product-based, granular security schema
- * Fully security-audited, and runs under Perl's taint mode
- * A robust, stable RDBMS back-end
- * Web, XML, email and console interfaces
- * Completely customisable and/or localisable web user interface
- * Extensive configurability
- * Smooth upgrade pathway between versions
- _________________________________________________________________
-
-2.2. Why Should We Use Bugzilla?
-
- For many years, defect-tracking software has remained principally the
- domain of large software development houses. Even then, most shops
- never bothered with bug-tracking software, and instead simply relied
- on shared lists and email to monitor the status of defects. This
- procedure is error-prone and tends to cause those bugs judged least
- significant by developers to be dropped or ignored.
-
- These days, many companies are finding that integrated defect-tracking
- systems reduce downtime, increase productivity, and raise customer
- satisfaction with their systems. Along with full disclosure, an open
- bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout
- the data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support
- accountability, telephone support knowledge bases, and a common,
- well-understood system for accounting for unusual system or software
- issues.
-
- But why should you use Bugzilla?
-
- Bugzilla is very adaptable to various situations. Known uses currently
- include IT support queues, Systems Administration deployment
- management, chip design and development problem tracking (both
- pre-and-post fabrication), and software and hardware bug tracking for
- luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
- provides a powerful, easy-to-use solution to configuration management
- and replication problems.
-
- Bugzilla can dramatically increase the productivity and accountability
- of individual employees by providing a documented workflow and
- positive feedback for good performance. How many times do you wake up
- in the morning, remembering that you were supposed to do something
- today, but you just can't quite remember? Put it in Bugzilla, and you
- have a record of it from which you can extrapolate milestones, predict
- product versions for integration, and follow the discussion trail that
- led to critical decisions.
-
- Ultimately, Bugzilla puts the power in your hands to improve your
- value to your employer or business while providing a usable framework
- for your natural attention to detail and knowledge store to flourish.
- _________________________________________________________________
-
-Chapter 3. Using Bugzilla
-
-3.1. How do I use Bugzilla?
-
- This section contains information for end-users of Bugzilla. There is
- a Bugzilla test installation, called Landfill, which you are welcome
- to play with (if it's up.) However, it does not necessarily have all
- Bugzilla features enabled, and often runs cutting-edge versions of
- Bugzilla for testing, so some things may work slightly differently
- than mentioned here.
- _________________________________________________________________
-
-3.1.1. Create a Bugzilla Account
-
- If you want to use Bugzilla, first you need to create an account.
- Consult with the administrator responsible for your installation of
- Bugzilla for the URL you should use to access it. If you're
- test-driving Bugzilla, use this URL:
- http://landfill.bugzilla.org/bugzilla-tip/
-
- 1. Click the "Open a new Bugzilla account" link, enter your email
- address and, optionally, your name in the spaces provided, then
- click "Create Account" .
- 2. Within moments, you should receive an email to the address you
- provided above, which contains your login name (generally the same
- as the email address), and a password you can use to access your
- account. This password is randomly generated, and can be changed
- to something more memorable.
- 3. Click the "Log In" link in the yellow area at the bottom of the
- page in your browser, enter your email address and password into
- the spaces provided, and click "Login".
-
- You are now logged in. Bugzilla uses cookies for authentication so,
- unless your IP address changes, you should not have to log in again.
- _________________________________________________________________
-
-3.1.2. Anatomy of a Bug
-
- The core of Bugzilla is the screen which displays a particular bug.
- It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill
- is a good example. Note that the labels for most fields are
- hyperlinks; clicking them will take you to context-sensitive help on
- that particular field. Fields marked * may not be present on every
- installation of Bugzilla.
-
- 1. Product and Component: Bugs are divided up by Product and
- Component, with a Product having one or more Components in it. For
- example, bugzilla.mozilla.org's "Bugzilla" Product is composed of
- several Components:
-
- Administration: Administration of a Bugzilla installation.
- Bugzilla-General: Anything that doesn't fit in the other components,
- or spans multiple components.
- Creating/Changing Bugs: Creating, changing, and viewing bugs.
- Documentation: The Bugzilla documentation, including The Bugzilla
- Guide.
- Email: Anything to do with email sent by Bugzilla.
- Installation: The installation process of Bugzilla.
- Query/Buglist: Anything to do with searching for bugs and viewing the
- buglists.
- Reporting/Charting: Getting reports from Bugzilla.
- User Accounts: Anything about managing a user account from the user's
- perspective. Saved queries, creating accounts, changing passwords,
- logging in, etc.
- User Interface: General issues having to do with the user interface
- cosmetics (not functionality) including cosmetic issues, HTML
- templates, etc.
- 2. Status and Resolution: These define exactly what state the bug is
- in - from not even being confirmed as a bug, through to being
- fixed and the fix confirmed by Quality Assurance. The different
- possible values for Status and Resolution on your installation
- should be documented in the context-sensitive help for those
- items.
- 3. Assigned To: The person responsible for fixing the bug.
- 4. *URL: A URL associated with the bug, if any.
- 5. Summary: A one-sentence summary of the problem.
- 6. *Status Whiteboard: (a.k.a. Whiteboard) A free-form text area for
- adding short notes and tags to a bug.
- 7. *Keywords: The administrator can define keywords which you can use
- to tag and categorise bugs - e.g. The Mozilla Project has keywords
- like crash and regression.
- 8. Platform and OS: These indicate the computing environment where
- the bug was found.
- 9. Version: The "Version" field is usually used for versions of a
- product which have been released, and is set to indicate which
- versions of a Component have the particular problem the bug report
- is about.
- 10. Priority: The bug assignee uses this field to prioritise his or
- her bugs. It's a good idea not to change this on other people's
- bugs.
- 11. Severity: This indicates how severe the problem is - from blocker
- ("application unusable") to trivial ("minor cosmetic issue"). You
- can also use this field to indicate whether a bug is an
- enhancement request.
- 12. *Target: (a.k.a. Target Milestone) A future version by which the
- bug is to be fixed. e.g. The Bugzilla Project's milestones for
- future Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
- not restricted to numbers, thought - you can use any text strings,
- such as dates.
- 13. Reporter: The person who filed the bug.
- 14. CC list: A list of people who get mail when the bug changes.
- 15. Attachments: You can attach files (e.g. testcases or patches) to
- bugs. If there are any attachments, they are listed in this
- section.
- 16. *Dependencies: If this bug cannot be fixed unless other bugs are
- fixed (depends on), or this bug stops other bugs being fixed
- (blocks), their numbers are recorded here.
- 17. *Votes: Whether this bug has any votes.
- 18. Additional Comments: You can add your two cents to the bug
- discussion here, if you have something worthwhile to say.
- _________________________________________________________________
-
-3.1.3. Searching for Bugs
-
- The Bugzilla Search page is is the interface where you can find any
- bug report, comment, or patch currently in the Bugzilla system. You
- can play with it here: landfill.bugzilla.org/bugzilla-tip/query.cgi .
-
- The Search page has controls for selecting different possible values
- for all of the fields in a bug, as described above. Once you've
- defined a search, you can either run it, or save it as a Remembered
- Query, which can optionally appear in the footer of your pages.
-
- Highly advanced querying is done using Boolean Charts, which have
- their own context-sensitive help .
- _________________________________________________________________
-
-3.1.4. Bug Lists
-
- If you run a search, a list of matching bugs will be returned. The
- default search is to return all open bugs on the system - don't try
- running this search on a Bugzilla installation with a lot of bugs!
-
- The format of the list is configurable. For example, it can be sorted
- by clicking the column headings. Other useful features can be accessed
- using the links at the bottom of the list:
-
- Long Format: this gives you a large page with a non-editable summary
- of the fields of each bug.
- Change Columns: change the bug attributes which appear in the list.
- Change several bugs at once: If your account is sufficiently
- empowered, you can make the same change to all the bugs in the list -
- for example, changing their owner.
- Send mail to bug owners: Sends mail to the owners of all bugs on the
- list.
- Edit this query: If you didn't get exactly the results you were
- looking for, you can return to the Query page through this link and
- make small revisions to the query you just made so you get more
- accurate results.
- _________________________________________________________________
-
-3.1.5. Filing Bugs
-
- Years of bug writing experience has been distilled for your reading
- pleasure into the Bug Writing Guidelines. While some of the advice is
- Mozilla-specific, the basic principles of reporting Reproducible,
- Specific bugs, isolating the Product you are using, the Version of the
- Product, the Component which failed, the Hardware Platform, and
- Operating System you were using at the time of the failure go a long
- way toward ensuring accurate, responsible fixes for the bug that bit
- you.
-
- The procedure for filing a test bug is as follows:
-
- 1. Go to Landfill in your browser and click Enter a new bug report.
- 2. Select a product - any one will do.
- 3. Fill in the fields. Bugzilla should have made reasonable guesses,
- based upon your browser, for the "Platform" and "OS" drop-down
- boxes. If they are wrong, change them.
- 4. Select "Commit" and send in your bug report.
- _________________________________________________________________
-
-3.2. Hints and Tips
-
- This section distills some Bugzilla tips and best practices that have
- been developed.
- _________________________________________________________________
-
-3.2.1. Autolinkification
-
- Bugzilla comments are plain text - so posting HTML will result in
- literal HTML tags rather than being interpreted by a browser. However,
- Bugzilla will automatically make hyperlinks out of certain sorts of
- text in comments. For example, the text http://www.bugzilla.org will
- be turned into http://www.bugzilla.org. Other strings which get
- linkified in the obvious manner are:
-
- bug 12345
- bug 23456, comment 53
- attachment 4321
- mailto:george@example.com
- george@example.com
- ftp://ftp.mozilla.org
- Most other sorts of URL
-
- A corollary here is that if you type a bug number in a comment, you
- should put the word "bug" before it, so it gets autolinkified for the
- convenience of others.
- _________________________________________________________________
-
-3.2.2. Quicksearch
-
- Quicksearch is a single-text-box query tool which uses metacharacters
- to indicate what is to be searched. For example, typing "foo|bar" into
- Quicksearch would search for "foo" or "bar" in the summary and status
- whiteboard of a bug; adding ":BazProduct" would search only in that
- product.
-
- You'll find the Quicksearch box on Bugzilla's front page, along with a
- Help link which details how to use it.
- _________________________________________________________________
-
-3.2.3. Comments
-
- If you are changing the fields on a bug, only comment if either you
- have something pertinent to say, or Bugzilla requires it. Otherwise,
- you may spam people unnecessarily with bug mail. To take an example: a
- user can set up their account to filter out messages where someone
- just adds themselves to the CC field of a bug (which happens a lot.)
- If you come along, add yourself to the CC field, and add a comment
- saying "Adding self to CC", then that person gets a pointless piece of
- mail they would otherwise have avoided.
-
- Don't use sigs in comments. Signing your name ("Bill") is acceptable,
- particularly if you do it out of habit, but full mail/news-style four
- line ASCII art creations are not.
- _________________________________________________________________
-
-3.2.4. Attachments
-
- Use attachments, rather than comments, for large chunks of ASCII data,
- such as trace, debugging output files, or log files. That way, it
- doesn't bloat the bug for everyone who wants to read it, and cause
- people to receive fat, useless mails.
-
- Trim screenshots. There's no need to show the whole screen if you are
- pointing out a single-pixel problem.
-
- Don't attach simple test cases (e.g. one HTML file, one CSS file and
- an image) as a ZIP file. Instead, upload them in reverse order and
- edit the referring file so that they point to the attached files. This
- way, the test case works immediately out of the bug.
- _________________________________________________________________
-
-3.2.5. Filing Bugs
-
- Try to make sure that everything said in the summary is also said in
- the first comment. Summaries are often updated and this will ensure
- your original information is easily accessible.
-
- You do not need to put "any" or similar strings in the URL field. If
- there is no specific URL associated with the bug, leave this field
- blank.
-
- If you feel a bug you filed was incorrectly marked as a DUPLICATE of
- another, please question it in your bug, not the bug it was duped to.
- Feel free to CC the person who duped it if they are not already CCed.
- _________________________________________________________________
-
-3.3. User Preferences
-
- Once you have logged in, you can customise various aspects of Bugzilla
- via the "Edit prefs" link in the page footer. The preferences are
- split into four tabs:
- _________________________________________________________________
-
-3.3.1. Account Settings
-
- On this tab, you can change your basic account information, including
- your password, email address and real name. For security reasons, in
- order to change anything on this page you must type your current
- password into the "Password" field at the top of the page. If you
- attempt to change your email address, a confirmation email is sent to
- both the old and new addresses, with a link to use to confirm the
- change. This helps to prevent account hijacking.
- _________________________________________________________________
-
-3.3.2. Email Settings
-
- On this tab you can reduce or increase the amount of email sent you
- from Bugzilla, opting in our out depending on your relationship to the
- bug and the change that was made to it. (Note that you can also do
- client-side filtering using the X-Bugzilla-Reason header which
- Bugzilla adds to all bugmail.)
-
- By entering user email names, delineated by commas, into the "Users to
- watch" text entry box you can receive a copy of all the bugmail of
- other users (security settings permitting.) This powerful
- functionality enables seamless transitions as developers change
- projects or users go on holiday.
-
- Note
-
- The ability to watch other users may not be available in all Bugzilla
- installations. If you can't see it, ask your administrator.
- _________________________________________________________________
-
-3.3.3. Page Footer
-
- On the Search page, you can store queries in Bugzilla, so if you
- regularly run a particular query it is just a drop-down menu away.
- Once you have a stored query, you can come here to request that it
- also be displayed in your page footer.
- _________________________________________________________________
-
-3.3.4. Permissions
-
- This is a purely informative page which outlines your current
- permissions on this installation of Bugzilla - what product groups you
- are in, and whether you can edit bugs or perform various
- administration functions.
- _________________________________________________________________
-
-Chapter 4. Installation
-
-4.1. Step-by-step Install
-
-4.1.1. Introduction
-
- Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. Win32 is not yet officially supported, but many people have got
- it working fine. Please see the Win32 Installation Notes for further
- advice on getting Bugzilla to work on Microsoft Windows.
- _________________________________________________________________
-
-4.1.2. Package List
-
- Note
-
- If you are running the very most recent version of Perl and MySQL
- (both the executables and development libraries) on your system, you
- can skip these manual installation steps for the Perl modules by using
- Bundle::Bugzilla; see Using Bundle::Bugzilla instead of manually
- installing Perl modules.
-
- The software packages necessary for the proper running of Bugzilla
- (with download links) are:
-
- 1. MySQL database server (3.22.5 or greater)
- 2. Perl (5.005 or greater, 5.6.1 is recommended if you wish to use
- Bundle::Bugzilla)
- 3. Perl Modules (minimum version):
- a. Template (v2.07)
- b. AppConfig (v1.52)
- c. Text::Wrap (v2001.0131)
- d. File::Spec (v0.8.2)
- e. Data::Dumper (any)
- f. DBD::mysql (v1.2209)
- g. DBI (v1.13)
- h. Date::Parse (any)
- i. CGI::Carp (any)
- and, optionally:
- a. GD (v1.19) for bug charting
- b. Chart::Base (v0.99c) for bug charting
- c. XML::Parser (any) for the XML interface
- d. MIME::Parser (any) for the email interface
- 4. The web server of your choice. Apache is highly recommended.
-
- Warning
-
- It is a good idea, while installing Bugzilla, to ensure that there is
- some kind of firewall between you and the rest of the Internet,
- because your machine may be insecure for periods during the install.
- Many installation steps require an active Internet connection to
- complete, but you must take care to ensure that at no point is your
- machine vulnerable to an attack.
-
- Note
-
- Linux-Mandrake 8.0 includes every required and optional library for
- Bugzilla. The easiest way to install them is by using the urpmi
- utility. If you follow these commands, you should have everything you
- need for Bugzilla, and checksetup.pl should not complain about any
- missing libraries. You may already have some of these installed.
-
-
- bash# urpmi perl-mysql
- bash# urpmi perl-chart
- bash# urpmi perl-gd
- bash# urpmi perl-MailTools (for Bugzilla email integration)
- bash# urpmi apache-modules
- _________________________________________________________________
-
-4.1.3. MySQL
-
- Visit the MySQL homepage at www.mysql.com to grab and install the
- latest stable release of the server.
-
- Note
-
- Many of the binary versions of MySQL store their data files in /var.
- On some Unix systems, this is part of a smaller root partition, and
- may not have room for your bug database. You can set the data
- directory as an option to configure if you build MySQL from source
- yourself.
-
- If you install from something other than an RPM or Debian package, you
- will need to add mysqld to your init scripts so the server daemon will
- come back up whenever your machine reboots. Further discussion of UNIX
- init sequences are beyond the scope of this guide.
-
- Change your init script to start mysqld with the ability to accept
- large packets. By default, mysqld only accepts packets up to 64K long.
- This limits the size of attachments you may put on bugs. If you add -O
- max_allowed_packet=1M to the command that starts mysqld (or
- safe_mysqld), then you will be able to have attachments up to about 1
- megabyte. There is a Bugzilla parameter for maximum attachment size;
- you should configure it to match the value you choose here.
-
- If you plan on running Bugzilla and MySQL on the same machine,
- consider using the --skip-networking option in the init script. This
- enhances security by preventing network access to MySQL.
- _________________________________________________________________
-
-4.1.4. Perl
-
- Any machine that doesn't have Perl on it is a sad machine indeed. Perl
- can be got in source form from perl.com for the rare *nix systems
- which don't have it. Although Bugzilla runs with all post-5.005
- versions of Perl, it's a good idea to be up to the very latest version
- if you can when running Bugzilla. As of this writing, that is Perl
- version 5.6.1.
-
- Tip
-
- You can skip the following Perl module installation steps by
- installing Bundle::Bugzilla from CPAN, which installs all required
- modules for you.
-
- bash# perl -MCPAN -e 'install "Bundle::Bugzilla"'
-
- Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
- which are not essential to a basic Bugzilla install. If installing
- this bundle fails, you should install each module individually to
- isolate the problem.
- _________________________________________________________________
-
-4.1.5. Perl Modules
-
- All Perl modules can be found on the Comprehensive Perl Archive
- Network (CPAN). The CPAN servers have a real tendency to bog down, so
- please use mirrors.
-
- Quality, general Perl module installation instructions can be found on
- the CPAN website, but the easy thing to do is to just use the CPAN
- shell which does all the hard work for you. To use the CPAN shell to
- install a module:
-
- bash# perl -MCPAN -e 'install "<modulename>"'
-
- To do it the hard way:
-
- Untar the module tarball -- it should create its own directory
-
- CD to the directory just created, and enter the following commands:
-
- 1. bash# perl Makefile.PL
- 2. bash# make
- 3. bash# make test
- 4. bash# make install
-
- Warning
-
- Many people complain that Perl modules will not install for them. Most
- times, the error messages complain that they are missing a file in
- "@INC". Virtually every time, this error is due to permissions being
- set too restrictively for you to compile Perl modules or not having
- the necessary Perl development libraries installed on your system.
- Consult your local UNIX systems administrator for help solving these
- permissions issues; if you are the local UNIX sysadmin, please consult
- the newsgroup/mailing list for further assistance or hire someone to
- help you out.
- _________________________________________________________________
-
-4.1.5.1. DBI
-
- The DBI module is a generic Perl module used the MySQL-related
- modules. As long as your Perl installation was done correctly the DBI
- module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
- _________________________________________________________________
-
-4.1.5.2. Data::Dumper
-
- The Data::Dumper module provides data structure persistence for Perl
- (similar to Java's serialization). It comes with later sub-releases of
- Perl 5.004, but a re-installation just to be sure it's available won't
- hurt anything.
- _________________________________________________________________
-
-4.1.5.3. MySQL-related modules
-
- The Perl/MySQL interface requires a few mutually-dependent Perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package.
-
- The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For most of the
- questions the provided default will be adequate, but when asked if
- your desired target is the MySQL or mSQL packages, you should select
- the MySQL related ones. Later you will be asked if you wish to provide
- backwards compatibility with the older MySQL packages; you should
- answer YES to this question. The default is NO.
-
- A host of 'localhost' should be fine and a testing user of 'test' with
- a null password should find itself with sufficient access to run tests
- on the 'test' database which MySQL created upon installation.
- _________________________________________________________________
-
-4.1.5.4. TimeDate modules
-
- Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. The component
- module we're most interested in is the Date::Format module, but
- installing all of them is probably a good idea anyway.
- _________________________________________________________________
-
-4.1.5.5. GD (optional)
-
- The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become the
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on millions of web pages to
- generate graphs on the fly. That's what Bugzilla will be using it for
- so you must install it if you want any of the graphing to work.
-
- Note
-
- The Perl GD library requires some other libraries that may or may not
- be installed on your system, including libpng and libgd. The full
- requirements are listed in the Perl GD library README. If compiling GD
- fails, it's probably because you're missing a required library.
- _________________________________________________________________
-
-4.1.5.6. Chart::Base (optional)
-
- The Chart module provides Bugzilla with on-the-fly charting abilities.
- It can be installed in the usual fashion after it has been fetched
- from CPAN. Note that earlier versions that 0.99c used GIFs, which are
- no longer supported by the latest versions of GD.
- _________________________________________________________________
-
-4.1.5.7. Template Toolkit
-
- When you install Template Toolkit, you'll get asked various questions
- about features to enable. The defaults are fine, except that it is
- recommended you use the high speed XS Stash of the Template Toolkit,
- in order to achieve best performance. However, there are known
- problems with XS Stash and Perl 5.005_02 and lower. If you wish to use
- these older versions of Perl, please use the regular stash.
- _________________________________________________________________
-
-4.1.6. HTTP Server
-
- You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can run the web server on a different
- machine than MySQL, but need to adjust the MySQL "bugs" user
- permissions accordingly.
-
- Note
-
- We strongly recommend Apache as the web server to use. The Bugzilla
- Guide installation instructions, in general, assume you are using
- Apache. If you have got Bugzilla working using another webserver,
- please share your experiences with us.
-
- You'll want to make sure that your web server will run any file with
- the .cgi extension as a CGI and not just display it. If you're using
- Apache that means uncommenting the following line in the httpd.conf
- file:
- AddHandler cgi-script .cgi
-
- With Apache you'll also want to make sure that within the httpd.conf
- file the line:
- Options ExecCGI
- AllowOverride Limit
-
- is in the stanza that covers the directories into which you intend to
- put the bugzilla .html and .cgi files.
-
- Note
-
- AllowOverride Limit allows the use of a Deny statement in the
- .htaccess file generated by checksetup.pl
-
- Users of older versions of Apache may find the above lines in the
- srm.conf and access.conf files, respecitvely.
-
- Warning
-
- There are important files and directories that should not be a served
- by the HTTP server - most files in the "data" and "shadow" directories
- and the "localconfig" file. You should configure your HTTP server to
- not serve these files. Failure to do so will expose critical passwords
- and other data. Please see .htaccess files and security for details on
- how to do this for Apache; the checksetup.pl script should create
- appropriate .htaccess files for you.
- _________________________________________________________________
-
-4.1.7. Bugzilla
-
- You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- "nobody"). You may decide to put the files in the main web space for
- your web server or perhaps in /usr/local with a symbolic link in the
- web space that points to the Bugzilla directory.
-
- Tip
-
- If you symlink the bugzilla directory into your Apache's HTML
- heirarchy, you may receive Forbidden errors unless you add the
- "FollowSymLinks" directive to the <Directory> entry for the HTML root
- in httpd.conf.
-
- Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user. This is a temporary step
- until you run the post-install checksetup.pl script, which locks down
- your installation.
-
- Lastly, you'll need to set up a symbolic link to
- /usr/bonsaitools/bin/perl for the correct location of your Perl
- executable (probably /usr/bin/perl). Otherwise you must hack all the
- .cgi files to change where they look for Perl. This can be done using
- the following Perl one-liner, but I suggest using the symlink approach
- to avoid upgrade hassles.
-
- perl -pi -e
- 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
- processmail syncshadowdb
-
- Change /usr/bin/perl to match the location of Perl on your machine.
- _________________________________________________________________
-
-4.1.8. Setting Up the MySQL Database
-
- After you've gotten all the software installed and working you're
- ready to start preparing the database for its life as the back end to
- a high quality bug tracker.
-
- First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla
- username will be "bugs", and will have minimal permissions.
-
- Begin by giving the MySQL root user a password. MySQL passwords are
- limited to 16 characters.
-
- bash# mysql -u root mysql
- mysql> UPDATE user SET Password=PASSWORD('<new_password>') WHERE
- user='root';
- mysql> FLUSH PRIVILEGES;
-
- From this point on, if you need to access MySQL as the MySQL root
- user, you will need to use mysql -u root -p and enter <new_password>.
- Remember that MySQL user names have nothing to do with Unix user names
- (login names).
-
- Next, we use an SQL GRANT command to create a "bugs" user, and grant
- sufficient permissions for checksetup.pl, which we'll use later, to
- work its magic. This also restricts the "bugs" user to operations
- within a database called "bugs", and only allows the account to
- connect from "localhost". Modify it to reflect your setup if you will
- be connecting from another machine or as a different user.
-
- Remember to set <bugs_password> to some unique password.
-
- mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
- '<bugs_password>';
- mysql> FLUSH PRIVILEGES;
-
- Note
-
- If you are using MySQL 4, the bugs user also needs to be granted the
- LOCK TABLES and CREATE TEMPORARY TABLES permissions.
- _________________________________________________________________
-
-4.1.9. checksetup.pl
-
- Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig for writing this script!) This script is designed to make sure
- your MySQL database and other configuration options are consistent
- with the Bugzilla CGI files. It will make sure Bugzilla files and
- directories have reasonable permissions, set up the data directory,
- and create all the MySQL tables.
-
- bash# ./checksetup.pl
-
- The first time you run it, it will create a file called localconfig.
-
- This file contains a variety of settings you may need to tweak
- including how Bugzilla should connect to the MySQL database.
-
- The connection settings include:
-
- 1. server's host: just use "localhost" if the MySQL server is local
- 2. database name: "bugs" if you're following these directions
- 3. MySQL username: "bugs" if you're following these directions
- 4. Password for the "bugs" MySQL account; (<bugs_password>) above
-
- Once you are happy with the settings, su to the user your web server
- runs as, and re-run checksetup.pl. (Note: on some security-conscious
- systems, you may need to change the login shell for the webserver
- account before you can do this.) On this second run, it will create
- the database and an administrator account for which you will be
- prompted to provide information.
-
- Note
-
- The checksetup.pl script is designed so that you can run it at any
- time without causing harm. You should run it after any upgrade to
- Bugzilla.
- _________________________________________________________________
-
-4.1.10. Configuring Bugzilla
-
- You should run through the parameters on the Edit Parameters page
- (link in the footer) and set them all to appropriate values. They key
- parameters are documented in Section 5.1.
- _________________________________________________________________
-
-4.2. Optional Additional Configuration
-
-4.2.1. Dependency Charts
-
- As well as the text-based dependency graphs, Bugzilla also supports
- dependency graphing, using a package called 'dot'. Exactly how this
- works is controlled by the 'webdotbase' parameter, which can have one
- of three values:
-
- 1. A complete file path to the command 'dot' (part of GraphViz) will
- generate the graphs locally
- 2. A URL prefix pointing to an installation of the webdot package
- will generate the graphs remotely
- 3. A blank value will disable dependency graphing.
-
- So, to get this working, install GraphViz. If you do that, you need to
- enable server-side image maps in Apache. Alternatively, you could set
- up a webdot server, or use the AT&T public webdot server (the default
- for the webdotbase param). Note that AT&T's server won't work if
- Bugzilla is only accessible using HTTPS.
- _________________________________________________________________
-
-4.2.2. Bug Graphs
-
- As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty Bugzilla bug reporting graphs.
-
- Add a cron entry like this to run collectstats.pl daily at 5 after
- midnight:
-
- bash# crontab -e
- 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
-
- After two days have passed you'll be able to view bug graphs from the
- Bug Reports page.
- _________________________________________________________________
-
-4.2.3. The Whining Cron
-
- By now you have a fully functional Bugzilla, but what good are bugs if
- they're not annoying? To help make those bugs more annoying you can
- set up Bugzilla's automatic whining system to complain at engineers
- which leave their bugs in the NEW state without triaging them.
-
- This can be done by adding the following command as a daily crontab
- entry (for help on that see that crontab man page):
-
- cd <your-bugzilla-directory> ; ./whineatnews.pl
-
- Tip
-
- Depending on your system, crontab may have several manpages. The
- following command should lead you to the most useful page for this
- purpose:
-
- man 5 crontab
- _________________________________________________________________
-
-4.2.4. LDAP Authentication
-
- Warning
-
- This information on using the LDAP authentication options with
- Bugzilla is old, and the authors do not know of anyone who has tested
- it. Approach with caution.
-
- The existing authentication scheme for Bugzilla uses email addresses
- as the primary user ID, and a password to authenticate that user. All
- places within Bugzilla where you need to deal with user ID (e.g
- assigning a bug) use the email address. The LDAP authentication builds
- on top of this scheme, rather than replacing it. The initial log in is
- done with a username and password for the LDAP directory. This then
- fetches the email address from LDAP and authenticates seamlessly in
- the standard Bugzilla authentication scheme using this email address.
- If an account for this address already exists in your Bugzilla system,
- it will log in to that account. If no account for that email address
- exists, one is created at the time of login. (In this case, Bugzilla
- will attempt to use the "displayName" or "cn" attribute to determine
- the user's full name.) After authentication, all other user-related
- tasks are still handled by email address, not LDAP username. You still
- assign bugs by email address, query on users by email address, etc.
-
- Using LDAP for Bugzilla authentication requires the Mozilla::LDAP (aka
- PerLDAP) Perl module. The Mozilla::LDAP module in turn requires
- Netscape's Directory SDK for C. After you have installed the SDK, then
- install the PerLDAP module. Mozilla::LDAP and the Directory SDK for C
- are both available for download from mozilla.org.
-
- Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
- directory for authentication. Be very careful when setting up this
- parameter; if you set LDAP authentication, but do not have a valid
- LDAP directory set up, you will not be able to log back in to Bugzilla
- once you log out. (If this happens, you can get back in by manually
- editing the data/params file, and setting useLDAP back to 0.)
-
- If using LDAP, you must set the three additional parameters: Set
- LDAPserver to the name (and optionally port) of your LDAP server. If
- no port is specified, it defaults to the default port of 389. (e.g
- "ldap.mycompany.com" or "ldap.mycompany.com:1234") Set LDAPBaseDN to
- the base DN for searching for users in your LDAP directory. (e.g.
- "ou=People,o=MyCompany") uids must be unique under the DN specified
- here. Set LDAPmailattribute to the name of the attribute in your LDAP
- directory which contains the primary email address. On most directory
- servers available, this is "mail", but you may need to change this.
- _________________________________________________________________
-
-4.2.5. Preventing untrusted Bugzilla content from executing malicious
-Javascript code
-
- It is possible for a Bugzilla to execute malicious Javascript code.
- Due to internationalization concerns, we are unable to incorporate the
- code changes necessary to fulfill the CERT advisory requirements
- mentioned in
- http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3.
- Executing the following code snippet from a UNIX command shell will
- rectify the problem if your Bugzilla installation is intended for an
- English-speaking audience. As always, be sure your Bugzilla
- installation has a good backup before making changes, and I recommend
- you understand what the script is doing before executing it.
-
-bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; char
-set=ISO-8859-1/i" *.cgi *.pl
-
- All this one-liner command does is search for all instances of
- "Content-type: text/html" and replaces it with "Content-Type:
- text/html; charset=ISO-8859-1" . This specification prevents possible
- Javascript attacks on the browser, and is suggested for all
- English-speaking sites. For non-English-speaking Bugzilla sites, I
- suggest changing "ISO-8859-1", above, to "UTF-8".
-
- Note: using <meta> tags to set the charset is not recommended, as
- there's a bug in Netscape 4.x which causes pages marked up in this way
- to load twice.
- _________________________________________________________________
-
-4.2.6. .htaccess files and security
-
- To enhance the security of your Bugzilla installation, Bugzilla's
- checksetup.pl script will generate .htaccess files which the Apache
- webserver can use to restrict access to the bugzilla data files. These
- .htaccess files will not work with Apache 1.2.x - but this has
- security holes, so you shouldn't be using it anyway.
-
- Note
-
- If you are using an alternate provider of webdot services for graphing
- (as described when viewing editparams.cgi in your web browser), you
- will need to change the ip address in data/webdot/.htaccess to the ip
- address of the webdot server that you are using.
-
- The default .htaccess file may not provide adequate access
- restrictions, depending on your web server configuration. Be sure to
- check the <Directory> entries for your Bugzilla directory so that the
- .htaccess file is allowed to override web server defaults. For
- instance, let's assume your installation of Bugzilla is installed to
- /usr/local/bugzilla . You should have this <Directory> entry in your
- httpd.conf file:
-
- <Directory /usr/local/bugzilla/>
- Options +FollowSymLinks +Indexes +Includes +ExecCGI
- AllowOverride All
- </Directory>
-
- The important part above is "AllowOverride All" . Without that, the
- .htaccess file created by checksetup.pl will not have sufficient
- permissions to protect your Bugzilla installation.
-
- If you are using Internet Information Server (IIS) or another web
- server which does not observe .htaccess conventions, you can disable
- their creation by editing localconfig and setting the $create_htaccess
- variable to 0.
- _________________________________________________________________
-
-4.2.7. mod_throttle and Security
-
- It is possible for a user, by mistake or on purpose, to access the
- database many times in a row which can result in very slow access
- speeds for other users. If your Bugzilla installation is experiencing
- this problem , you may install the Apache module mod_throttle which
- can limit connections by ip-address. You may download this module at
- http://www.snert.com/Software/mod_throttle/ Follow the instructions to
- install into your Apache install. This module only functions with the
- Apache web server! You may use the ThrottleClientIP command provided
- by this module to accomplish this goal. See the Module Instructions
- for more information.
- _________________________________________________________________
-
-4.3. Win32 Installation Notes
-
- This section covers installation on Microsoft Windows. Bugzilla has
- been made to work on Win32 platforms, but the Bugzilla team wish to
- emphasise that The easiest way to install Bugzilla on
- Intel-archiecture machines is to install some variant of GNU/Linux,
- then follow the UNIX installation instructions in this Guide. If you
- have any influence in the platform choice for running this system,
- please choose GNU/Linux instead of Microsoft Windows.
-
- Warning
-
- After that warning, here's the situation for 2.16 and Windows. It
- doesn't work at all out of the box. You are almost certainly better
- off getting the 2.17 version from CVS (after consultation with the
- Bugzilla Team to make sure you are pulling on a stable day) because
- we'll be doing a load of work to make the Win32 experience more
- pleasant than it is now.
-
- If you still want to try this, to have any hope of getting it to work,
- you'll need to apply the mail patch from bug 124174. After that,
- you'll need to read the (outdated) installation instructions below,
- some (probably a lot better) more recent ones kindly provided by Toms
- Baugis and Jean-Sebastien Guay, and also check the Bugzilla 2.16 Win32
- update page . If we get time, we'll write some better installation
- instructions for 2.16 and put them up there. But no promises.
- _________________________________________________________________
-
-4.3.1. Win32 Installation: Step-by-step
-
- Note
-
- You should be familiar with, and cross-reference, the rest of the
- Bugzilla Installation section while performing your Win32
- installation.
-
- Making Bugzilla work on Microsoft Windows is no picnic. Support for
- Win32 has improved dramatically in the last few releases, but, if you
- choose to proceed, you should be a very skilled Windows Systems
- Administrator with strong troubleshooting abilities, a high tolerance
- for pain, and moderate perl skills. Bugzilla on NT requires hacking
- source code and implementing some advanced utilities. What follows is
- the recommended installation procedure for Win32; additional
- suggestions are provided in Appendix A .
- 1. Install Apache Web Server for Windows, and copy the Bugzilla files
- somewhere Apache can serve them. Please follow all the
- instructions referenced in Bugzilla Installation regarding your
- Apache configuration, particularly instructions regarding the
- "AddHandler" parameter and "ExecCGI" .
-
- Note
-
- You may also use Internet Information Server or Personal Web Server
- for this purpose. However, setup is quite different. If ActivePerl
- doesn't seem to handle your file associations correctly (for .cgi and
- .pl files), please consult Appendix A .
- If you are going to use IIS, if on Windows NT you must be updated to
- at least Service Pack 4. Windows 2000 ships with a sufficient version
- of IIS.
- 2. Install ActivePerl for Windows. Check
- http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a
- current compiled binary.
- Please also check the following links to fully understand the
- status of ActivePerl on Win32: Perl Porting , and Perl on Win32
- FAQ
- 3. Use ppm from your perl\bin directory to install the following
- packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
- AppConfig, and Template. You may need to extract them from .zip
- format using Winzip or other unzip program first. Most of these
- additional ppm modules can be downloaded from ActiveState, but
- AppConfig and Template should be obtained from OpenInteract using
- the instructions on the Template Toolkit web site .
-
- Note
-
- You can find a list of modules at
- http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or
- http://www.activestate.com/PPMPackages/5.6plus
- The syntax for ppm is: C:> ppm <modulename>
- Example 4-1. Installing ActivePerl ppd Modules on Microsoft
- Windows
- C:> ppm DBD-Mysql
- Watch your capitalization!
- ActiveState's 5.6Plus directory also contains an AppConfig ppm, so
- you might see the following error when trying to install the
- version at OpenInteract:
- Error installing package 'AppConfig': Read a PPD for 'AppConfig',
- but it is not intended for this build of Perl
- (MSWin32-x86-multi-thread)
- If so, download both the tarball and the ppd directly from
- OpenInteract, then run ppm from within the same directory to which
- you downloaded those files and install the package by referencing
- the ppd file explicitly via in the install command, f.e.:
- Example 4-2. Installing OpenInteract ppd Modules manually on
- Microsoft Windows
- install C:\AppConfig.ppd
- 4. Install MySQL for NT.
-
- Note
-
- You can download MySQL for Windows NT from MySQL.com . Some find it
- helpful to use the WinMySqlAdmin utility, included with the download,
- to set up the database.
- 5. Setup MySQL
- a. C:> C:\mysql\bin\mysql -u root mysql
- b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
- c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
- "new_password" , above, indicates whatever password you wish
- to use for your "root" user.
- d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
- CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';
- "bugs_password" , above, indicates whatever password you wish
- to use for your "bugs" user.
- e. mysql> FLUSH PRIVILEGES;
- f. mysql> create database bugs;
- g. mysql> exit;
- h. C:> C:\mysql\bin\mysqladmin -u root -p reload
- 6. Edit checksetup.pl in your Bugzilla directory. Change this line:
-
- my $webservergid =
- getgrnam($my_webservergroup);
-
- to
-
- my $webservergid =
- $my_webservergroup;
-
- or the name of the group you wish to own the files explicitly:
-
- my $webservergid =
- 'Administrators'
-
- 7. Run checksetup.pl from the Bugzilla directory.
- 8. Edit localconfig to suit your requirements. Set $db_pass to your
- "bugs_password" from step 5.d , and $webservergroup to "8" .
-
- Note
-
- Not sure on the "8" for $webservergroup above. If it's wrong, please
- send corrections.
- 9. Edit defparams.pl to suit your requirements. Particularly, set
- DefParam("maintainer") and DefParam("urlbase") to match your
- install.
-
- Note
-
- This is yet another step I'm not sure of, since the maintainer of this
- documentation does not maintain Bugzilla on NT. If you can confirm or
- deny that this step is required, please let me know.
- 10.
-
- Note
-
- There are several alternatives to Sendmail that will work on Win32.
- The one mentioned here is a suggestion , not a requirement. Some other
- mail packages that can work include BLAT , Windmail , Mercury Sendmail
- , and the CPAN Net::SMTP Perl module (available in .ppm). Every option
- requires some hacking of the Perl scripts for Bugzilla to make it
- work. The option here simply requires the least.
- 1. Download NTsendmail, available from www.ntsendmail.com . You
- must have a "real" mail server which allows you to relay off
- it in your $ENV{"NTsendmail"} (which you should probably
- place in globals.pl)
- 2. Put ntsendmail.pm into your .\perl\lib directory.
- 3. Add to globals.pl:
-
- # these settings configure the NTsendmail
- process use NTsendmail;
- $ENV{"NTsendmail"}="your.smtpserver.box";
- $ENV{"NTsendmail_debug"}=1;
- $ENV{"NTsendmail_max_tries"}=5;
-
- Note
-
- Some mention to also edit $db_pass in globals.pl to be your
- "bugs_password" . Although this may get you around some problem
- authenticating to your database, since globals.pl is not normally
- restricted by .htaccess , your database password is exposed to whoever
- uses your web server.
- 4. Find and comment out all occurences of " open(SENDMAIL " in
- your Bugzilla directory. Then replace them with:
-
- # new sendmail functionality my $mail=new
- NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
- $to=$login; my $subject=$urlbase;
- $mail->send($from,$to,$subject,$msg);
-
-Note
-
- Some have found success using the commercial product, Windmail . You
- could try replacing your sendmail calls with:
-
- open SENDMAIL,
- "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
- mail.log";
-
- or something to that effect.
- 11. Change all references in all files from processmail to
- processmail.pl , and rename processmail to processmail.pl .
-
- Note
-
- Many think this may be a change we want to make for main-tree
- Bugzilla. It's painless for the UNIX folks, and will make the Win32
- people happier.
-
- Note
-
- Some people have suggested using the Net::SMTP Perl module instead of
- NTsendmail or the other options listed here. You can change
- processmail.pl to make this work.
-
-
-my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
-ver
-$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
-$smtp->to($tolist); # recipient's address
-$smtp->data(); # Start the mail
-$smtp->datasend($msg);
-$smtp->dataend(); # Finish sending the mail
-$smtp->quit; # Close the SMTP connection
-$logstr = "$logstr; mail sent to $tolist $cclist";
-}
-
-
-
-
- here is a test mail program for Net::SMTP:
-
- use Net::SMTP;
- my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
- => 1, ); # connect to SMTP server
- $smtp->auth;
- $smtp->mail('you@yourcompany.com');# use the sender's adress
- here
- $smtp->to('someotherAddress@someotherdomain.com'); #
- recipient's address
- $smtp->data(); # Start the mail
- $smtp->datasend('test');
- $smtp->dataend(); # Finish sending the mail
- $smtp->quit; # Close the SMTP connection
- exit;
-
-
-
-
- 12.
-
- Note
-
- This step is optional if you are using IIS or another web server which
- only decides on an interpreter based upon the file extension (.pl),
- rather than the "shebang" line (#/usr/bonsaitools/bin/perl)
- Modify the path to perl on the first line (#!) of all files to
- point to your Perl installation, and add "perl" to the beginning
- of all Perl system calls that use a perl script as an argument.
- This may take you a while. There is a "setperl.csh" utility to
- speed part of this procedure, available in the Useful Patches and
- Utilities for Bugzilla section of The Bugzilla Guide. However, it
- requires the Cygwin GNU-compatible environment for Win32 be set up
- in order to work. See http://www.cygwin.com/ for details on
- obtaining Cygwin.
- 13. Modify the invocation of all system() calls in all perl scripts in
- your Bugzilla directory. You should specify the full path to perl
- for each system() call. For instance, change this line in
- processmail:
-
-
- system ("./processmail",@ARGLIST);
- </programlisting> to
- <programlisting>
- system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
-
-
-
- 14. Add binmode() calls so attachments will work ( bug 62000 ).
- Because Microsoft Windows based systems handle binary files
- different than Unix based systems, you need to add the following
- lines to createattachment.cgi and showattachment.cgi before the
- require 'CGI.pl'; line.
-
- binmode(STDIN);
- binmode(STDOUT);
-
-
-
- Note
-
- According to bug 62000 , the perl documentation says that you should
- always use binmode() when dealing with binary files, but never when
- dealing with text files. That seems to suggest that rather than
- arbitrarily putting binmode() at the beginning of the attachment
- files, there should be logic to determine if binmode() is needed or
- not.
-
- Tip
-
- If you are using IIS or Personal Web Server, you must add cgi
- relationships to Properties -> Home directory (tab) -> Application
- Settings (section) -> Configuration (button), such as:
-
-
- .cgi to: <perl install directory>\perl.exe %s
- %s .pl to: <perl install directory>\perl.exe %s %s
- GET,HEAD,POST
-
- Change the path to Perl to match your install, of course.
- _________________________________________________________________
-
-4.3.2. Additional Windows Tips
-
- Tip
-
- From Andrew Pearson:
-
- You can make Bugzilla work with Personal Web Server for Windows 98
- and higher, as well as for IIS 4.0. Microsoft has information
- available at
- http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP
-
- Basically you need to add two String Keys in the registry at the
- following location:
-
-
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramete
-rs\ScriptMap
-
- The keys should be called ".pl" and ".cgi", and both should have a
- value something like: c:/perl/bin/perl.exe "%s" "%s"
-
- The KB article only talks about .pl, but it goes into more detail
- and provides a perl test script.
-
- Tip
-
- If attempting to run Bugzilla 2.12 or older, you will need to remove
- encrypt() calls from the Perl source. This is not necessary for
- Bugzilla 2.13 and later, which includes the current release, Bugzilla
- 2.16.4.
-
- Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12
- or earlier
-
- Replace this:
-
- SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
- ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
- $enteredcryptpwd = FetchOneColumn();
-
- with this:
- my $enteredcryptpwd = $enteredpwd
-
- in cgi.pl.
- _________________________________________________________________
-
-4.4. Mac OS X Installation Notes
-
- There are a lot of common libraries and utilities out there that Apple
- did not include with Mac OS X, but which run perfectly well on it. The
- GD library, which Bugzilla needs to do bug graphs, is one of these.
-
- The easiest way to get a lot of these is with a program called Fink,
- which is similar in nature to the CPAN installer, but installs common
- GNU utilities. Fink is available from
- <http://sourceforge.net/projects/fink/>.
-
- Follow the instructions for setting up Fink. Once it's installed,
- you'll want to run the following as root: fink install gd
-
- It will prompt you for a number of dependencies, type 'y' and hit
- enter to install all of the dependencies. Then watch it work.
-
- To prevent creating conflicts with the software that Apple installs by
- default, Fink creates its own directory tree at /sw where it installs
- most of the software that it installs. This means your libraries and
- headers for libgd will be at /sw/lib and /sw/include instead of
- /usr/lib and /usr/local/include. Because of these changed locations
- for the libraries, the Perl GD module will not install directly via
- CPAN, because it looks for the specific paths instead of getting them
- from your environment. But there's a way around that :-)
-
- Instead of typing "install GD" at the cpan> prompt, type look GD. This
- should go through the motions of downloading the latest version of the
- GD module, then it will open a shell and drop you into the build
- directory. Apply this patch to the Makefile.PL file (save the patch
- into a file and use the command patch < patchfile.)
-
- Then, run these commands to finish the installation of the GD module:
-
- perl Makefile.PL
- make
- make test
- make install
- And don't forget to run exit to get back to CPAN.
- _________________________________________________________________
-
-4.5. Troubleshooting
-
- This section gives solutions to common Bugzilla installation problems.
- _________________________________________________________________
-
-4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
-
- Try executing perl -MCPAN -e 'install CPAN' and then continuing.
-
- Certain older versions of the CPAN toolset were somewhat naive about
- how to upgrade Perl modules. When a couple of modules got rolled into
- the core Perl distribution for 5.6.1, CPAN thought that the best way
- to get those modules up to date was to haul down the Perl distribution
- itself and build it. Needless to say, this has caused headaches for
- just about everybody. Upgrading to a newer version of CPAN with the
- commandline above should fix things.
- _________________________________________________________________
-
-4.5.2. DBD::Sponge::db prepare failed
-
- The following error message may appear due to a bug in DBD::mysql
- (over which the Bugzilla team have no control):
- DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site
-/lib/DBD/mysql.pm line 248.
- SV = NULL(0x0) at 0x20fc444
- REFCNT = 1
- FLAGS = (PADBUSY,PADMY)
-
- To fix this, go to <path-to-perl>/lib/DBD/sponge.pm in your Perl
- installation and replace
- my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAME'}) {
- $numFields = @{$attribs->{NAME}};
-
- by
- my $numFields;
- if ($attribs->{'NUM_OF_FIELDS'}) {
- $numFields = $attribs->{'NUM_OF_FIELDS'};
- } elsif ($attribs->{'NAMES'}) {
- $numFields = @{$attribs->{NAMES}};
-
- (note the S added to NAME.)
- _________________________________________________________________
-
-4.5.3. cannot chdir(/var/spool/mqueue)
-
- If you are installing Bugzilla on SuSE Linux, or some other
- distributions with "paranoid" security options, it is possible that
- the checksetup.pl script may fail with the error:
- cannot chdir(/var/spool/mqueue): Permission denied
-
- This is because your /var/spool/mqueue directory has a mode of
- "drwx------". Type chmod 755 /var/spool/mqueue as root to fix this
- problem.
- _________________________________________________________________
-
-4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
-
- This is caused by a bug in the version of File::Temp that is
- distributed with perl 5.6.0. Many minor variations of this error have
- been reported. Examples can be found in Figure 4-1.
-
- Figure 4-1. Other File::Temp error messages
- Your vendor has not defined Fcntl macro O_NOINHERIT, used
- at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
-
- Your vendor has not defined Fcntl macro O_EXLOCK, used
- at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
-
- Your vendor has not defined Fcntl macro O_TEMPORARY, used
- at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
-
- Numerous people have reported that upgrading to version 5.6.1 or
- higher solved the problem for them. A less involved fix is to apply
- the patch in Figure 4-2. The patch is also available as a patch file.
-
- Figure 4-2. Patch for File::Temp in Perl 5.6.0
- --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
- +++ File/Temp.pm Thu Feb 6 16:26:23 2003
- @@ -205,6 +205,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
- + local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
- @@ -226,6 +227,7 @@
- # eg CGI::Carp
- local $SIG{__DIE__} = sub {};
- local $SIG{__WARN__} = sub {};
- + local *CORE::GLOBAL::die = sub {};
- $bit = &$func();
- 1;
- };
- _________________________________________________________________
-
-Chapter 5. Administering Bugzilla
-
-5.1. Bugzilla Configuration
-
- Bugzilla is configured by changing various parameters, accessed from
- the "Edit parameters" link in the page footer. Here are some of the
- key parameters on that page. You should run down this list and set
- them appropriately after installing Bugzilla.
- 1. maintainer: The maintainer parameter is the email address of the
- person responsible for maintaining this Bugzilla installation. The
- address need not be that of a valid Bugzilla account.
- 2. urlbase: This parameter defines the fully qualified domain name
- and web server path to your Bugzilla installation.
- For example, if your Bugzilla query page is
- http://www.foo.com/bugzilla/query.cgi, set your "urlbase" to
- http://www.foo.com/bugzilla/.
- 3. usebuggroups: This dictates whether or not to implement
- group-based security for Bugzilla. If set, Bugzilla bugs can have
- an associated 'group', defining which users are allowed to see and
- edit the bug.
- Set "usebuggroups" to "on" only if you may wish to restrict access
- to particular bugs to certain groups of users. I suggest leaving
- this parameter off while initially testing your Bugzilla.
- 4. usebuggroupsentry: Bugzilla Products can have a group associated
- with them, so that certain users can only see bugs in certain
- products. When this parameter is set to "on", this places all
- newly-created bugs in the group for their product immediately.
- 5. shadowdb: You run into an interesting problem when Bugzilla
- reaches a high level of continuous activity. MySQL supports only
- table-level write locking. What this means is that if someone
- needs to make a change to a bug, they will lock the entire table
- until the operation is complete. Locking for write also blocks
- reads until the write is complete. The "shadowdb" parameter was
- designed to get around this limitation. While only a single user
- is allowed to write to a table at a time, reads can continue
- unimpeded on a read-only shadow copy of the database. Although
- your database size will double, a shadow database can cause an
- enormous performance improvement when implemented on extremely
- high-traffic Bugzilla databases.
- As a guide, mozilla.org began needing "shadowdb" when they reached
- around 40,000 Bugzilla users with several hundred Bugzilla bug
- changes and comments per day.
- The value of the parameter defines the name of the shadow bug
- database. Set "shadowdb" to e.g. "bug_shadowdb" if you will be
- running a *very* large installation of Bugzilla.
-
- Note
-
- Enabling "shadowdb" can adversely affect the stability of your
- installation of Bugzilla. You should regularly check that your
- database is in sync. It is often advisable to force a shadow database
- sync nightly via "cron".
- If you use the "shadowdb" option, it is only natural that you
- should turn the "queryagainstshadowdb" option on as well.
- Otherwise you are replicating data into a shadow database for no
- reason!
- 6. shutdownhtml: If you need to shut down Bugzilla to perform
- administration, enter some descriptive HTML here and anyone who
- tries to use Bugzilla will receive a page to that effect.
- Obviously, editparams.cgi will still be accessible so you can
- remove the HTML and re-enable Bugzilla. :-)
- 7. passwordmail: Every time a user creates an account, the text of
- this parameter (with substitutions) is sent to the new user along
- with their password message.
- Add any text you wish to the "passwordmail" parameter box. For
- instance, many people choose to use this box to give a quick
- training blurb about how to use Bugzilla at your site.
- 8. useqacontact: This allows you to define an email address for each
- component, in addition to that of the default owner, who will be
- sent carbon copies of incoming bugs.
- 9. usestatuswhiteboard: This defines whether you wish to have a
- free-form, overwritable field associated with each bug. The
- advantage of the Status Whiteboard is that it can be deleted or
- modified with ease, and provides an easily-searchable field for
- indexing some bugs that have some trait in common.
- 10. whinedays: Set this to the number of days you want to let bugs go
- in the NEW or REOPENED state before notifying people they have
- untouched new bugs. If you do not plan to use this feature, simply
- do not set up the whining cron job described in the installation
- instructions, or set this value to "0" (never whine).
- 11. commenton*: All these fields allow you to dictate what changes can
- pass without comment, and which must have a comment from the
- person who changed them. Often, administrators will allow users to
- add themselves to the CC list, accept bugs, or change the Status
- Whiteboard without adding a comment as to their reasons for the
- change, yet require that most other changes come with an
- explanation.
- Set the "commenton" options according to your site policy. It is a
- wise idea to require comments when users resolve, reassign, or
- reopen bugs at the very least.
-
- Note
-
- It is generally far better to require a developer comment when
- resolving bugs than not. Few things are more annoying to bug database
- users than having a developer mark a bug "fixed" without any comment
- as to what the fix was (or even that it was truly fixed!)
- 12. supportwatchers: Turning on this option allows users to ask to
- receive copies of all a particular other user's bug email. This
- is, of course, subject to the groupset restrictions on the bug; if
- the "watcher" would not normally be allowed to view a bug, the
- watcher cannot get around the system by setting herself up to
- watch the bugs of someone with bugs outside her privileges. They
- would still only receive email updates for those bugs she could
- normally view.
- _________________________________________________________________
-
-5.2. User Administration
-
-5.2.1. Creating the Default User
-
- When you first run checksetup.pl after installing Bugzilla, it will
- prompt you for the administrative username (email address) and
- password for this "super user". If for some reason you delete the
- "super user" account, re-running checksetup.pl will again prompt you
- for this username and password.
-
- Tip
-
- If you wish to add more administrative users, you must use the MySQL
- interface. Run "mysql" from the command line, and use these commands:
-
-
- mysql> use bugs;
- mysql> update profiles set groupset=0x7ffffffffffffff where login_name
- = "(user's login name)";
-
- Yes, that is fourteen "f" 's. A whole lot of f-ing going on if you
- want to create a new administator.
- _________________________________________________________________
-
-5.2.2. Managing Other Users
-
-5.2.2.1. Creating new users
-
- Your users can create their own user accounts by clicking the "New
- Account" link at the bottom of each page (assuming they aren't logged
- in as someone else already.) However, should you desire to create user
- accounts ahead of time, here is how you do it.
-
- 1. After logging in, click the "Users" link at the footer of the
- query page, and then click "Add a new user".
- 2. Fill out the form presented. This page is self-explanatory. When
- done, click "Submit".
-
- Note
-
- Adding a user this way will not send an email informing them of their
- username and password. While useful for creating dummy accounts
- (watchers which shuttle mail to another system, for instance, or email
- addresses which are a mailing list), in general it is preferable to
- log out and use the "New Account" button to create users, as it will
- pre-populate all the required fields and also notify the user of her
- account name and password.
- _________________________________________________________________
-
-5.2.2.2. Modifying Users
-
- To see a specific user, search for their login name in the box
- provided on the "Edit Users" page. To see all users, leave the box
- blank.
-
- You can search in different ways the listbox to the right of the text
- entry box. You can match by case-insensitive substring (the default),
- regular expression, or a reverse regular expression match, which finds
- every user name which does NOT match the regular expression. (Please
- see the man regexp manual page for details on regular expression
- syntax.)
-
- Once you have found your user, you can change the following fields:
-
- * Login Name: This is generally the user's full email address.
- However, if you have are using the emailsuffix Param, this may
- just be the user's login name. Note that users can now change
- their login names themselves (to any valid email address.)
- * Real Name: The user's real name. Note that Bugzilla does not
- require this to create an account.
- * Password: You can change the user's password here. Users can
- automatically request a new password, so you shouldn't need to do
- this often. If you want to disable an account, see Disable Text
- below.
- * Disable Text: If you type anything in this box, including just a
- space, the user is prevented from logging in, or making any
- changes to bugs via the web interface. The HTML you type in this
- box is presented to the user when they attempt to perform these
- actions, and should explain why the account was disabled.
-
- Warning
-
- Don't disable the administrator account!
-
- Note
-
- The user can still submit bugs via the e-mail gateway, if you set it
- up, even if the disabled text field is filled in. The e-mail gateway
- should not be enabled for secure installations of Bugzilla.
- * <groupname>: If you have created some groups, e.g.
- "securitysensitive", then checkboxes will appear here to allow you
- to add users to, or remove them from, these groups.
- * canconfirm: This field is only used if you have enabled the
- "unconfirmed" status. If you enable this for a user, that user can
- then move bugs from "Unconfirmed" to a "Confirmed" status (e.g.:
- "New" status).
- * creategroups: This option will allow a user to create and destroy
- groups in Bugzilla.
- * editbugs: Unless a user has this bit set, they can only edit those
- bugs for which they are the assignee or the reporter. Even if this
- option is unchecked, users can still add comments to bugs.
- * editcomponents: This flag allows a user to create new products and
- components, as well as modify and destroy those that have no bugs
- associated with them. If a product or component has bugs
- associated with it, those bugs must be moved to a different
- product or component before Bugzilla will allow them to be
- destroyed.
- * editkeywords: If you use Bugzilla's keyword functionality,
- enabling this feature allows a user to create and destroy
- keywords. As always, the keywords for existing bugs containing the
- keyword the user wishes to destroy must be changed before Bugzilla
- will allow it to die.
- * editusers: This flag allows a user to do what you're doing right
- now: edit other users. This will allow those with the right to do
- so to remove administrator privileges from other users or grant
- them to themselves. Enable with care.
- * tweakparams: This flag allows a user to change Bugzilla's Params
- (using editparams.cgi.)
- * <productname>: This allows an administrator to specify the
- products in which a user can see bugs. The user must still have
- the "editbugs" privilege to edit bugs in these products.
- _________________________________________________________________
-
-5.3. Product, Component, Milestone, and Version Administration
-
-5.3.1. Products
-
- Products are the broadest category in Bugzilla, and tend to represent
- real-world shipping products. E.g. if your company makes computer
- games, you should have one product per game, perhaps a "Common"
- product for units of technology used in multiple games, and maybe a
- few special products (Website, Administration...)
-
- Many of Bugzilla's settings are configurable on a per-product basis.
- The number of "votes" available to users is set per-product, as is the
- number of votes required to move a bug automatically from the
- UNCONFIRMED status to the NEW status.
-
- To create a new product:
-
- 1. Select "products" from the footer
- 2. Select the "Add" link in the bottom right
- 3. Enter the name of the product and a description. The Description
- field may contain HTML.
-
- Don't worry about the "Closed for bug entry", "Maximum Votes per
- person", "Maximum votes a person can put on a single bug", "Number of
- votes a bug in this Product needs to automatically get out of the
- UNCOMFIRMED state", and "Version" options yet. We'll cover those in a
- few moments.
- _________________________________________________________________
-
-5.3.2. Components
-
- Components are subsections of a Product. E.g. the computer game you
- are designing may have a "UI" component, an "API" component, a "Sound
- System" component, and a "Plugins" component, each overseen by a
- different programmer. It often makes sense to divide Components in
- Bugzilla according to the natural divisions of responsibility within
- your Product or company.
-
- Each component has a owner and (if you turned it on in the
- parameters), a QA Contact. The owner should be the primary person who
- fixes bugs in that component. The QA Contact should be the person who
- will ensure these bugs are completely fixed. The Owner, QA Contact,
- and Reporter will get email when new bugs are created in this
- Component and when these bugs change. Default Owner and Default QA
- Contact fields only dictate the default assignments; these can be
- changed on bug submission, or at any later point in a bug's life.
-
- To create a new Component:
-
- 1. Select the "Edit components" link from the "Edit product" page
- 2. Select the "Add" link in the bottom right.
- 3. Fill out the "Component" field, a short "Description", the
- "Initial Owner" and "Initial QA Contact" (if enabled.) The
- Component and Description fields may contain HTML; the "Initial
- Owner" field must be a login name already existing in the
- database.
- _________________________________________________________________
-
-5.3.3. Versions
-
- Versions are the revisions of the product, such as "Flinders 3.1",
- "Flinders 95", and "Flinders 2000". Version is not a multi-select
- field; the usual practice is to select the most recent version with
- the bug.
-
- To create and edit Versions:
-
- 1. From the "Edit product" screen, select "Edit Versions"
- 2. You will notice that the product already has the default version
- "undefined". Click the "Add" link in the bottom right.
- 3. Enter the name of the Version. This field takes text only. Then
- click the "Add" button.
- _________________________________________________________________
-
-5.3.4. Milestones
-
- Milestones are "targets" that you plan to get a bug fixed by. For
- example, you have a bug that you plan to fix for your 3.0 release, it
- would be assigned the milestone of 3.0.
-
- Note
-
- Milestone options will only appear for a Product if you turned on the
- "usetargetmilestone" Param in the "Edit Parameters" screen.
-
- To create new Milestones, set Default Milestones, and set Milestone
- URL:
-
- 1. Select "Edit milestones" from the "Edit product" page.
- 2. Select "Add" in the bottom right corner. text
- 3. Enter the name of the Milestone in the "Milestone" field. You can
- optionally set the "sortkey", which is a positive or negative
- number (-255 to 255) that defines where in the list this
- particular milestone appears. This is because milestones often do
- not occur in alphanumeric order For example, "Future" might be
- after "Release 1.2". Select "Add".
- 4. From the Edit product screen, you can enter the URL of a page
- which gives information about your milestones and what they mean.
-
- Tip
-
- If you want your milestone document to be restricted so that it can
- only be viewed by people in a particular Bugzilla group, the best way
- is to attach the document to a bug in that group, and make the URL the
- URL of that attachment.
- _________________________________________________________________
-
-5.4. Voting
-
- Voting allows users to be given a pot of votes which they can allocate
- to bugs, to indicate that they'd like them fixed. This allows
- developers to gauge user need for a particular enhancement or bugfix.
- By allowing bugs with a certain number of votes to automatically move
- from "UNCONFIRMED" to "NEW", users of the bug system can help
- high-priority bugs garner attention so they don't sit for a long time
- awaiting triage.
-
- To modify Voting settings:
-
- 1. Navigate to the "Edit product" screen for the Product you wish to
- modify
- 2. Maximum Votes per person: Setting this field to "0" disables
- voting.
- 3. Maximum Votes a person can put on a single bug": It should
- probably be some number lower than the "Maximum votes per person".
- Don't set this field to "0" if "Maximum votes per person" is
- non-zero; that doesn't make any sense.
- 4. Number of votes a bug in this product needs to automatically get
- out of the UNCONFIRMED state: Setting this field to "0" disables
- the automatic move of bugs from UNCONFIRMED to NEW.
- 5. Once you have adjusted the values to your preference, click
- "Update".
- _________________________________________________________________
-
-5.5. Groups and Group Security
-
- Groups allow the administrator to isolate bugs or products that should
- only be seen by certain people. There are two types of group - Generic
- Groups, and Product-Based Groups.
-
- Product-Based Groups are matched with products, and allow you to
- restrict access to bugs on a per-product basis. They are enabled using
- the usebuggroups Param. Turning on the usebuggroupsentry Param will
- mean bugs automatically get added to their product group when filed.
-
- Generic Groups have no special relationship to products; you create
- them, and put bugs in them as required. One example of the use of
- Generic Groups is Mozilla's "Security" group, into which
- security-sensitive bugs are placed until fixed. Only the Mozilla
- Security Team are members of this group.
-
- To create Generic Groups:
-
- 1. Select the "groups" link in the footer.
- 2. Take a moment to understand the instructions on the "Edit Groups"
- screen, then select the "Add Group" link.
- 3. Fill out the "New Name", "New Description", and "New User RegExp"
- fields. "New User RegExp" allows you to automatically place all
- users who fulfill the Regular Expression into the new group. When
- you have finished, click "Add".
-
- To use Product-Based Groups:
-
- 1. Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen.
-
- Warning
-
- XXX is this still true? "usebuggroupsentry" has the capacity to
- prevent the administrative user from directly altering bugs because of
- conflicting group permissions. If you plan on using
- "usebuggroupsentry", you should plan on restricting administrative
- account usage to administrative duties only. In other words, manage
- bugs with an unpriveleged user account, and manage users, groups,
- Products, etc. with the administrative account.
- 2. In future, when you create a Product, a matching group will be
- automatically created. If you need to add a Product Group to a
- Product which was created before you turned on usebuggroups, then
- simply create a new group, as outlined above, with the same name
- as the Product.
-
- Warning
-
- Bugzilla currently has a limit of 64 groups per installation. If you
- have more than about 50 products, you should consider running multiple
- Bugzillas. Ask in the newsgroup for other suggestions for working
- around this restriction.
-
- Note that group permissions are such that you need to be a member of
- all the groups a bug is in, for whatever reason, to see that bug.
- _________________________________________________________________
-
-5.6. Bugzilla Security
-
- Warning
-
- Poorly-configured MySQL and Bugzilla installations have given
- attackers full access to systems in the past. Please take these
- guidelines seriously, even for Bugzilla machines hidden away behind
- your firewall. 80% of all computer trespassers are insiders, not
- anonymous crackers.
-
- Note
-
- These instructions must, of necessity, be somewhat vague since
- Bugzilla runs on so many different platforms. If you have refinements
- of these directions, please submit a bug to Bugzilla.
-
- Warning
-
- This is not meant to be a comprehensive list of every possible
- security issue regarding the tools mentioned in this section. There is
- no subsitute for reading the information written by the authors of any
- software running on your system.
- _________________________________________________________________
-
-5.6.1. TCP/IP Ports
-
- TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only
- needs 1... 2 if you need to use features that require e-mail such as
- bug moving or the e-mail interface from contrib. You should audit your
- server and make sure that you aren't listening on any ports you don't
- need to be. You may also wish to use some kind of firewall software to
- be sure that trafic can only be recieved on ports you specify.
- _________________________________________________________________
-
-5.6.2. MySQL
-
- MySQL ships by default with many settings that should be changed. By
- defaults it allows anybody to connect from localhost without a
- password and have full administrative capabilities. It also defaults
- to not have a root password (this is not the same as the system root).
- Also, many installations default to running mysqld as the system root.
-
- 1. Make sure you are running at least version 3.22.32 of MySQL as
- earlier versions had notable security holes.
- 2. Consult the documentation that came with your system for
- information on making mysqld run as an unprivleged user.
- 3. You should also be sure to disable the anonymous user account and
- set a password for the root user. This is accomplished using the
- following commands:
-
-bash$ mysql mysql
-mysql> DELETE FROM user WHERE user = '';
-mysql> UPDATE user SET password = password('new_password') WHERE user = 'root';
-mysql> FLUSH PRIVILEGES;
-
-
- From this point forward you will need to use mysql -u root -p and
- enter new_password when prompted when using the mysql client.
- 4. If you run MySQL on the same machine as your httpd server, you
- should consider disabling networking from within MySQL by adding
- the following to your /etc/my.conf:
-
- [myslqd]
- # Prevent network access to MySQL.
- skip-networking
-
-
- 5. You may also consider running MySQL, or even all of Bugzilla in a
- chroot jail; however, instructions for doing that are beyond the
- scope of this document.
- _________________________________________________________________
-
-5.6.3. Daemon Accounts
-
- Many daemons, such as Apache's httpd and MySQL's mysqld default to
- running as either "root" or "nobody". Running as "root" introduces
- obvious security problems, but the problems introduced by running
- everything as "nobody" may not be so obvious. Basically, if you're
- running every daemon as "nobody" and one of them gets comprimised,
- they all get comprimised. For this reason it is recommended that you
- create a user account for each daemon.
-
- Note
-
- You will need to set the webservergroup to the group you created for
- your webserver to run as in localconfig. This will allow
- ./checksetup.pl to better adjust the file permissions on your Bugzilla
- install so as to not require making anything world-writable.
- _________________________________________________________________
-
-5.6.4. Web Server Access Controls
-
- There are many files that are placed in the Bugzilla directory area
- that should not be accessable from the web. Because of the way
- Bugzilla is currently layed out, the list of what should and should
- not be accessible is rather complicated. A new installation method is
- currently in the works which should solve this by allowing files that
- shouldn't be accessible from the web to be placed in directory outside
- the webroot. See bug 44659 for more information.
-
- * In the main Bugzilla directory, you should:
- + Block: *.pl, *localconfig*, runtests.sh, processmail,
- syncshadowdb
- + But allow: localconfig.js, localconfig.rdf
- * In data:
- + Block everything
- + But allow: duplicates.rdf
- * In data/webdot:
- + If you use a remote webdot server:
- o Block everything
- o But allow *.dot only for the remote webdot server
- + Otherwise, if you use a local GraphViz:
- o Block everything
- o But allow: *.png, *.gif, *.jpg, *.map
- + And if you don't use any dot:
- o Block everything
- * In Bugzilla:
- + Block everything
- * In template:
- + Block everything
-
- Tip
-
- Bugzilla ships with the ability to generate .htaccess files
- instructing Apache which files should and should not be accessible.
-
- You should test to make sure that the files mentioned above are not
- accessible from the Internet, especially your localconfig file which
- contains your database password. To test, simply point your web
- browser at the file; for example, to test mozilla.org's installation,
- we'd try to access http://bugzilla.mozilla.org/localconfig. You should
- get a 403 Forbidden error.
-
- Caution
-
- Not following the instructions in this section, including testing, may
- result in sensitive information being globally accessible.
- _________________________________________________________________
-
-5.7. Template Customisation
-
- One of the large changes for 2.16 was the templatisation of the entire
- user-facing UI, using the Template Toolkit. Administrators can now
- configure the look and feel of Bugzilla without having to edit Perl
- files or face the nightmare of massive merge conflicts when they
- upgrade to a newer version in the future.
-
- Templatisation also makes localised versions of Bugzilla possible, for
- the first time. In the future, a Bugzilla installation may have
- templates installed for multiple localisations, and select which ones
- to use based on the user's browser language setting.
- _________________________________________________________________
-
-5.7.1. What to Edit
-
- There are two different ways of editing of Bugzilla's templates, and
- which you use depends mainly on how you upgrade Bugzilla. The template
- directory structure is that there's a top level directory, template,
- which contains a directory for each installed localisation. The
- default English templates are therefore in en. Underneath that, there
- is the default directory and optionally the custom directory. The
- default directory contains all the templates shipped with Bugzilla,
- whereas the custom directory does not exist at first and must be
- created if you want to use it.
-
- The first method of making customisations is to directly edit the
- templates in template/en/default. This is probably the best method for
- small changes if you are going to use the CVS method of upgrading,
- because if you then execute a cvs update, any template fixes will get
- automagically merged into your modified versions.
-
- If you use this method, your installation will break if CVS conflicts
- occur.
-
- The other method is to copy the templates into a mirrored directory
- structure under template/en/custom. The templates in this directory
- automatically override those in default. This is the technique you
- need to use if you use the overwriting method of upgrade, because
- otherwise your changes will be lost. This method is also better if you
- are using the CVS method of upgrading and are going to make major
- changes, because it is guaranteed that the contents of this directory
- will not be touched during an upgrade, and you can then decide whether
- to continue using your own templates, or make the effort to merge your
- changes into the new versions by hand.
-
- If you use this method, your installation may break if incompatible
- changes are made to the template interface. If such changes are made
- they will be documented in the release notes, provided you are using a
- stable release of Bugzilla. If you use using unstable code, you will
- need to deal with this one yourself, although if possible the changes
- will be mentioned before they occur in the deprecations section of the
- previous stable release's release notes.
-
- Note
-
- Don't directly edit the compiled templates in data/template/* - your
- changes will be lost when Template Toolkit recompiles them.
-
- Note
-
- It is recommended that you run ./checksetup.pl after any template
- edits, especially if you've created a new file in the custom
- directory.
- _________________________________________________________________
-
-5.7.2. How To Edit Templates
-
- The syntax of the Template Toolkit language is beyond the scope of
- this guide. It's reasonably easy to pick up by looking at the current
- templates; or, you can read the manual, available on the Template
- Toolkit home page. However, you should particularly remember (for
- security reasons) to always HTML filter things which come from the
- database or user input, to prevent cross-site scripting attacks.
-
- However, one thing you should take particular care about is the need
- to properly HTML filter data that has been passed into the template.
- This means that if the data can possibly contain special HTML
- characters such as <, and the data was not intended to be HTML, they
- need to be converted to entity form, ie <. You use the 'html'
- filter in the Template Toolkit to do this. If you fail to do this, you
- may open up your installation to cross-site scripting attacks.
-
- Also note that Bugzilla adds a few filters of its own, that are not in
- standard Template Toolkit. In particular, the 'url_quote' filter can
- convert characters that are illegal or have special meaning in URLs,
- such as &, to the encoded form, ie %26. This actually encodes most
- characters (but not the common ones such as letters and numbers and so
- on), including the HTML-special characters, so there's never a need to
- HTML filter afterwards.
-
- Editing templates is a good way of doing a "poor man's custom fields".
- For example, if you don't use the Status Whiteboard, but want to have
- a free-form text entry box for "Build Identifier", then you can just
- edit the templates to change the field labels. It's still be called
- status_whiteboard internally, but your users don't need to know that.
-
- Note
-
- If you are making template changes that you intend on submitting back
- for inclusion in standard Bugzilla, you should read the relevant
- sections of the Developers' Guide.
- _________________________________________________________________
-
-5.7.3. Template Formats
-
- Some CGIs have the ability to use more than one template. For example,
- buglist.cgi can output bug lists as RDF or two different forms of HTML
- (complex and simple). (Try this out by appending &format=simple to a
- buglist.cgi URL on your Bugzilla installation.) This mechanism, called
- template 'formats', is extensible.
-
- To see if a CGI supports multiple output formats, grep the CGI for
- "ValidateOutputFormat". If it's not present, adding multiple format
- support isn't too hard - see how it's done in other CGIs.
-
- To make a new format template for a CGI which supports this, open a
- current template for that CGI and take note of the INTERFACE comment
- (if present.) This comment defines what variables are passed into this
- template. If there isn't one, I'm afraid you'll have to read the
- template and the code to find out what information you get.
-
- Write your template in whatever markup or text style is appropriate.
-
- You now need to decide what content type you want your template served
- as. Open up the localconfig file and find the $contenttypes variable.
- If your content type is not there, add it. Remember the three- or
- four-letter tag assigned to you content type. This tag will be part of
- the template filename.
-
- Save the template as <stubname>-<formatname>.<contenttypetag>.tmpl.
- Try out the template by calling the CGI as
- <cginame>.cgi?format=<formatname> .
- _________________________________________________________________
-
-5.7.4. Particular Templates
-
- There are a few templates you may be particularly interested in
- customising for your installation.
-
- index.html.tmpl: This is the Bugzilla front page.
-
- global/header.html.tmpl: This defines the header that goes on all
- Bugzilla pages. The header includes the banner, which is what appears
- to users and is probably what you want to edit instead. However the
- header also includes the HTML HEAD section, so you could for example
- add a stylesheet or META tag by editing the header.
-
- global/banner.html.tmpl: This contains the "banner", the part of the
- header that appears at the top of all Bugzilla pages. The default
- banner is reasonably barren, so you'll probably want to customise this
- to give your installation a distinctive look and feel. It is
- recommended you preserve the Bugzilla version number in some form so
- the version you are running can be determined, and users know what
- docs to read.
-
- global/footer.html.tmpl: This defines the footer that goes on all
- Bugzilla pages. Editing this is another way to quickly get a
- distinctive look and feel for your Bugzilla installation.
-
- bug/create/user-message.html.tmpl: This is a message that appears near
- the top of the bug reporting page. By modifying this, you can tell
- your users how they should report bugs.
-
- bug/create/create.html.tmpl and bug/create/comment.txt.tmpl: You may
- wish to get bug submitters to give certain bits of structured
- information, each in a separate input widget, for which there is not a
- field in the database. The bug entry system has been designed in an
- extensible fashion to enable you to define arbitrary fields and
- widgets, and have their values appear formatted in the initial
- Description, rather than in database fields. An example of this is the
- mozilla.org guided bug submission form.
-
- To make this work, create a custom template for enter_bug.cgi (the
- default template, on which you could base it, is create.html.tmpl),
- and either call it create.html.tmpl or use a format and call it
- create-<formatname>.html.tmpl. Put it in the custom/bug/create
- directory. In it, add widgets for each piece of information you'd like
- collected - such as a build number, or set of steps to reproduce.
-
- Then, create a template like custom/bug/create/comment.txt.tmpl, also
- named after your format if you are using one, which references the
- form fields you have created. When a bug report is submitted, the
- initial comment attached to the bug report will be formatted according
- to the layout of this template.
-
- For example, if your enter_bug template had a field
- <input type="text" name="buildid" size="30">
-
- and then your comment.txt.tmpl had
- BuildID: [% form.buildid %]
-
- then
- BuildID: 20020303
-
- would appear in the initial checkin comment.
- _________________________________________________________________
-
-5.8. Upgrading to New Releases
-
- Upgrading Bugzilla is something we all want to do from time to time,
- be it to get new features or pick up the latest security fix. How easy
- it is to update depends on a few factors.
-
- * If the new version is a revision or a new point release
- * How many, if any, local changes have been made
-
- There are also three different methods to upgrade your installation.
-
- 1. Using CVS (Example 5-1)
- 2. Downloading a new tarball (Example 5-2)
- 3. Applying the relevant patches (Example 5-3)
-
- Which options are available to you may depend on how large a jump you
- are making and/or your network configuration.
-
- Revisions are normally released to fix security vulnerabilities and
- are distinguished by an increase in the third number. For example,
- when 2.16.2 was released, it was a revision to 2.16.1.
-
- Point releases are normally released when the Bugzilla team feels that
- there has been a significant amount of progress made between the last
- point release and the current time. These are often proceeded by a
- stabilization period and release candidates, however the use of
- development versions or release candidates is beyond the scope of this
- document. Point releases can be distinguished by an increase in the
- second number, or minor version. For example, 2.16.2 is a newer point
- release than 2.14.5.
-
- The examples in this section are written as if you were updating to
- version 2.16.2. The procedures are the same regardless if you are
- updating to a new point release or a new revision. However, the chance
- of running into trouble increases when upgrading to a new point
- release, escpecially if you've made local changes.
-
- These examples also assume that your Bugzilla installation is at
- /var/www/html/bugzilla. If that is not the case, simply substitute the
- proper paths where appropriate.
-
- Example 5-1. Upgrading using CVS
-
- Every release of Bugzilla, whether it is a revision or a point
- release, is tagged in CVS. Also, every tarball we have distributed
- since version 2.12 has been primed for using CVS. This does, however,
- require that you are able to access cvs-mirror.mozilla.org on port
- 2401.
-
- Tip
-
- If you can do this, updating using CVS is probably the most painless
- method, especially if you have a lot of local changes.
- bash$ cd /var/www/html/bugzilla
- bash$ cvs login
- Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
- CVS password: anonymous
- bash$ cvs -q update -r BUGZILLA-2_16_2 -dP
- P checksetup.pl
- P collectstats.pl
- P globals.pl
- P docs/rel_notes.txt
- P template/en/default/list/quips.html.tmpl
-
- Caution
-
- If a line in the output from cvs update begins with a C that
- represents a file with local changes that CVS was unable to properly
- merge. You need to resolve these conflicts manually before Bugzilla
- (or at least the portion using that file) will be usable.
-
- Note
-
- You also need to run ./checksetup.pl before your Bugzilla upgrade will
- be complete.
-
- Example 5-2. Upgrading using the tarball
-
- If you are unable or unwilling to use CVS, another option that's
- always available is to download the latest tarball. This is the most
- difficult option to use, especially if you have local changes.
- bash$ cd /var/www/html
- bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz
- Output omitted
- bash$ tar xzvf bugzilla-2.16.2.tar.gz
- bugzilla-2.16.2/
- bugzilla-2.16.2/.cvsignore
- bugzilla-2.16.2/1x1.gif
- Output truncated
- bash$ cd bugzilla-2.16.2
- bash$ cp ../bugzilla/localconfig* .
- bash$ cp -r ../bugzilla/data .
- bash$ cd ..
- bash$ mv bugzilla bugzilla.old
- bash$ mv bugzilla-2.16.2 bugzilla
- bash$ cd bugzilla
- bash$ ./checksetup.pl
- Output omitted
-
- Warning
-
- The cp commands both end with periods which is a very important
- detail, it tells the shell that the destination directory is the
- current working directory. Also, the period at the beginning of the
- ./checksetup.pl is important and can not be omitted.
-
- Note
-
- You will now have to reapply any changes you have made to your local
- installation manually.
-
- Example 5-3. Upgrading using patches
-
- The Bugzilla team will normally make a patch file available for
- revisions to go from the most recent revision to the new one. You
- could also read the release notes and grab the patches attached to the
- mentioned bug, but it is safer to use the released patch file as
- sometimes patches get changed before they get checked in (for minor
- spelling fixes and the like). It is also theorectically possible to
- scour the fixed bug list and pick and choose which patches to apply
- from a point release, but this is not recommended either as what
- you'll end up with is a hodge podge Bugzilla that isn't really any
- version. This would also make it more difficult to upgrade in the
- future.
-bash$ cd /var/www/html/bugzilla
-bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz
-Output omitted
-bash$ gunzip bugzilla-2.16.1-to-2.16.2.diff.gz
-bash$ patch -p1 < bugzilla-2.16.1-to-2.16.2.diff
-patching file checksetup.pl
-patching file collectstats.pl
-patching file globals.pl
-
- Caution
-
- If you do this, beware that this doesn't change the entires in your
- CVS directory so it may make updates using CVS (Example 5-1) more
- difficult in the future.
- _________________________________________________________________
-
-5.9. Integrating Bugzilla with Third-Party Tools
-
-5.9.1. Bonsai
-
- Bonsai is a web-based tool for managing CVS, the Concurrent Versioning
- System . Using Bonsai, administrators can control open/closed status
- of trees, query a fast relational database back-end for change,
- branch, and comment information, and view changes made since the last
- time the tree was closed. Bonsai also integrates with Tinderbox, the
- Mozilla automated build management system.
- _________________________________________________________________
-
-5.9.2. CVS
-
- CVS integration is best accomplished, at this point, using the
- Bugzilla Email Gateway.
-
- Follow the instructions in this Guide for enabling Bugzilla e-mail
- integration. Ensure that your check-in script sends an email to your
- Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
- have CVS check-in comments append to your Bugzilla bug. If you want to
- have the bug be closed automatically, you'll have to modify the
- contrib/bugzilla_email_append.pl script.
-
- There is also a CVSZilla project, based upon somewhat dated Bugzilla
- code, to integrate CVS and Bugzilla through CVS' ability to email.
- Check it out at: http://homepages.kcbbs.gen.nz/~tonyg/.
- _________________________________________________________________
-
-5.9.3. Perforce SCM
-
- You can find the project page for Bugzilla and Teamtrack Perforce
- integration (p4dti) at: http://www.ravenbrook.com/project/p4dti .
- "p4dti" is now an officially supported product from Perforce, and you
- can find the "Perforce Public Depot" p4dti page at
- http://public.perforce.com/public/perforce/p4dti/index.html .
-
- Integration of Perforce with Bugzilla, once patches are applied, is
- seamless. Perforce replication information will appear below the
- comments of each bug. Be certain you have a matching set of patches
- for the Bugzilla version you are installing. p4dti is designed to
- support multiple defect trackers, and maintains its own documentation
- for it. Please consult the pages linked above for further information.
- _________________________________________________________________
-
-5.9.4. Tinderbox/Tinderbox2
-
- We need Tinderbox integration information.
- _________________________________________________________________
-
-Appendix A. The Bugzilla FAQ
-
- This FAQ includes questions not covered elsewhere in the Guide.
-
- 1. General Questions
-
- A.1.1. Where can I find information about Bugzilla?
- A.1.2. What license is Bugzilla distributed under?
- A.1.3. How do I get commercial support for Bugzilla?
- A.1.4. What major companies or projects are currently using
- Bugzilla for bug-tracking?
-
- A.1.5. Who maintains Bugzilla?
- A.1.6. How does Bugzilla stack up against other bug-tracking
- databases?
-
- A.1.7. Why doesn't Bugzilla offer this or that feature or
- compatibility with this other tracking software?
-
- A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
-
- A.1.9. Why do the scripts say /usr/bonsaitools/bin/perl instead
- of /usr/bin/perl or something else?
-
- A.1.10. Is there an easy way to change the Bugzilla cookie name?
-
- 2. Managerial Questions
-
- A.2.1. Is Bugzilla web-based, or do you have to have specific
- software or a specific operating system on your machine?
-
- A.2.2. Can Bugzilla integrate with Perforce (SCM software)?
- A.2.3. Does Bugzilla allow the user to track multiple projects?
- A.2.4. If I am on many projects, and search for all bugs assigned
- to me, will Bugzilla list them for me and allow me to
- sort by project, severity etc?
-
- A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs
- etc)? If yes, are there any that are NOT allowed?
-
- A.2.6. Does Bugzilla allow us to define our own priorities and
- levels? Do we have complete freedom to change the labels
- of fields and format of them, and the choice of
- acceptable values?
-
- A.2.7. Does Bugzilla provide any reporting features, metrics,
- graphs, etc? You know, the type of stuff that management
- likes to see. :)
-
- A.2.8. Is there email notification and if so, what do you see
- when you get an email?
-
- A.2.9. Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
-
- A.2.10. Do users have to have any particular type of email
- application?
-
- A.2.11. Does Bugzilla allow data to be imported and exported? If
- I had outsiders write up a bug report using a MS Word bug
- template, could that template be imported into "matching"
- fields? If I wanted to take the results of a query and
- export that data to MS Excel, could I do that?
-
- A.2.12. Has anyone converted Bugzilla to another language to be
- used in other countries? Is it localizable?
-
- A.2.13. Can a user create and save reports? Can they do this in
- Word format? Excel format?
-
- A.2.14. Does Bugzilla have the ability to search by word, phrase,
- compound search?
-
- A.2.15. Does Bugzilla provide record locking when there is
- simultaneous access to the same bug? Does the second
- person get a notice that the bug is in use or how are
- they notified?
-
- A.2.16. Are there any backup features provided?
- A.2.17. Can users be on the system while a backup is in progress?
-
- A.2.18. What type of human resources are needed to be on staff to
- install and maintain Bugzilla? Specifically, what type of
- skills does the person need to have? I need to find out
- if we were to go with Bugzilla, what types of individuals
- would we need to hire and how much would that cost vs
- buying an "Out-of-the-Box" solution.
-
- A.2.19. What time frame are we looking at if we decide to hire
- people to install and maintain the Bugzilla? Is this
- something that takes hours or weeks to install and a
- couple of hours per week to maintain and customize or is
- this a multi-week install process, plus a full time job
- for 1 person, 2 people, etc?
-
- A.2.20. Is there any licensing fee or other fees for using
- Bugzilla? Any out-of-pocket cost other than the bodies
- needed as identified above?
-
- 3. Bugzilla Security
-
- A.3.1. How do I completely disable MySQL security if it's giving
- me problems (I've followed the instructions in the
- installation section of this guide)?
-
- A.3.2. Are there any security problems with Bugzilla?
- A.3.3. I've implemented the security fixes mentioned in Chris
- Yeh's security advisory of 5/10/2000 advising not to run
- MySQL as root, and am running into problems with MySQL no
- longer working correctly.
-
- 4. Bugzilla Email
-
- A.4.1. I have a user who doesn't want to receive any more email
- from Bugzilla. How do I stop it entirely for this user?
-
- A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send
- email to anyone but me. How do I do it?
-
- A.4.3. I want whineatnews.pl to whine at something more, or other
- than, only new bugs. How do I do it?
-
- A.4.4. I don't like/want to use Procmail to hand mail off to
- bug_email.pl. What alternatives do I have?
-
- A.4.5. How do I set up the email interface to submit/change bugs
- via email?
-
- A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's
- extremely slow. What gives?
-
- A.4.7. How come email from Bugzilla changes never reaches me?
-
- 5. Bugzilla Database
-
- A.5.1. I've heard Bugzilla can be used with Oracle?
- A.5.2. I think my database might be corrupted, or contain invalid
- entries. What do I do?
-
- A.5.3. I want to manually edit some entries in my database. How?
- A.5.4. I think I've set up MySQL permissions correctly, but
- Bugzilla still can't connect.
-
- A.5.5. How do I synchronize bug information among multiple
- different Bugzilla databases?
-
- 6. Bugzilla and Win32
-
- A.6.1. What is the easiest way to run Bugzilla on Win32
- (Win98+/NT/2K)?
-
- A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32?
- A.6.3. CGI's are failing with a "something.cgi is not a valid
- Windows NT application" error. Why?
-
- A.6.4. I'm having trouble with the perl modules for NT not being
- able to talk to to the database.
-
- 7. Bugzilla Usage
-
- A.7.1. How do I change my user name (email address) in Bugzilla?
- A.7.2. The query page is very confusing. Isn't there a simpler
- way to query?
-
- A.7.3. I'm confused by the behavior of the "accept" button in the
- Show Bug form. Why doesn't it assign the bug to me when I
- accept it?
-
- A.7.4. I can't upload anything into the database via the "Create
- Attachment" link. What am I doing wrong?
-
- A.7.5. How do I change a keyword in Bugzilla, once some bugs are
- using it?
-
- A.7.6. Why can't I close bugs from the "Change Several Bugs at
- Once" page?
-
- 8. Bugzilla Hacking
-
- A.8.1. What bugs are in Bugzilla right now?
- A.8.2. How can I change the default priority to a null value? For
- instance, have the default priority be "---" instead of
- "P2"?
-
- A.8.3. What's the best way to submit patches? What guidelines
- should I follow?
-
-1. General Questions
-
- A.1.1. Where can I find information about Bugzilla?
-
- You can stay up-to-date with the latest Bugzilla information at
- http://www.bugzilla.org/
-
- A.1.2. What license is Bugzilla distributed under?
-
- Bugzilla is covered by the Mozilla Public License. See details at
- http://www.mozilla.org/MPL/
-
- A.1.3. How do I get commercial support for Bugzilla?
-
- http://bugzilla.org/consulting.html is a list of people and companies
- who have asked us to list them as consultants for Bugzilla.
-
- www.collab.net offers Bugzilla as part of their standard offering to
- large projects. They do have some minimum fees that are pretty hefty,
- and generally aren't interested in small projects.
-
- There are several experienced Bugzilla hackers on the mailing
- list/newsgroup who are willing to make themselves available for
- generous compensation. Try sending a message to the mailing list
- asking for a volunteer.
-
- A.1.4. What major companies or projects are currently using Bugzilla
- for bug-tracking?
-
- There are dozens of major companies with public Bugzilla sites to
- track bugs in their products. A few include:
-
- Netscape/AOL
- Mozilla.org
- NASA
- Red Hat Software
- SuSe Corp
- The Horde Project
- AbiSource
- Real Time Enterprises, Inc
- Eggheads.org
- Strata Software
- RockLinux
- Creative Labs (makers of SoundBlaster)
- The Apache Foundation
- The Gnome Foundation
- Ximian
- Linux-Mandrake
-
- Suffice to say, there are more than enough huge projects using
- Bugzilla that we can safely say it's extremely popular.
-
- A.1.5. Who maintains Bugzilla?
-
- A core team, led by Dave Miller (justdave@bugzilla.org).
-
- A.1.6. How does Bugzilla stack up against other bug-tracking
- databases?
-
- We can't find any head-to-head comparisons of Bugzilla against other
- defect-tracking software. If you know of one, please get in touch.
- However, from the author's personal experience with other
- bug-trackers, Bugzilla offers superior performance on commodity
- hardware, better price (free!), more developer- friendly features
- (such as stored queries, email integration, and platform
- independence), improved scalability, open source code, greater
- flexibility, and superior ease-of-use.
-
- If you happen to be a commercial bug-tracker vendor, please step
- forward with a list of advantages your product has over Bugzilla. We'd
- be happy to include it in the "Competitors" section.
-
- A.1.7. Why doesn't Bugzilla offer this or that feature or
- compatibility with this other tracking software?
-
- It may be that the support has not been built yet, or that you have
- not yet found it. Bugzilla is making tremendous strides in usability,
- customizability, scalability, and user interface. It is widely
- considered the most complete and popular open-source bug-tracking
- software in existence.
-
- That doesn't mean it can't use improvement! You can help the project
- along by either hacking a patch yourself that supports the
- functionality you require, or else submitting a "Request for
- Enhancement" (RFE) using the bug submission interface at
- bugzilla.mozilla.org.
-
- A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
-
- MySQL was originally chosen because it is free, easy to install, and
- was available for the hardware Netscape intended to run it on.
-
- There is currently work in progress to make Bugzilla work on
- PostgreSQL and Sybase in the default distribution. You can track the
- progress of these initiatives in bugs 98304 and 173130 respectively.
-
- Once both of these are done, adding support for additional database
- servers should be trivial.
-
- A.1.9. Why do the scripts say /usr/bonsaitools/bin/perl instead of
- /usr/bin/perl or something else?
-
- Mozilla.org used /usr/bonsaitools/bin/perl, because originally Terry
- wanted a place to put a version of Perl and other tools that was
- strictly under his control.
-
- Note
-
- This convention was abonded during the 2.17 development cycle so it
- will no longer be an issue when 2.18 comes out.
-
- A.1.10. Is there an easy way to change the Bugzilla cookie name?
-
- At present, no.
-
-2. Managerial Questions
-
- Note
-
- Questions likely to be asked by managers. :-)
-
- A.2.1. Is Bugzilla web-based, or do you have to have specific software
- or a specific operating system on your machine?
-
- It is web and e-mail based. You can edit bugs by sending specially
- formatted email to a properly configured Bugzilla, or control via the
- web.
-
- A.2.2. Can Bugzilla integrate with Perforce (SCM software)?
-
- Yes! You can find more information elsewhere in "The Bugzilla Guide"
- in the "Integration with Third-Party Products" section.
-
- A.2.3. Does Bugzilla allow the user to track multiple projects?
-
- Absolutely! You can track any number of Products that can each be
- composed of any number of Components.
-
- Note
-
- There are only 55 groups available in version 2.16 of Bugzilla. If you
- are using product groups, this will also limit the number of products
- you can have. This limit does not exist in the current 2.17
- development releases and will not exist in 2.18.
-
- A.2.4. If I am on many projects, and search for all bugs assigned to
- me, will Bugzilla list them for me and allow me to sort by project,
- severity etc?
-
- Yes.
-
- A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs etc)?
- If yes, are there any that are NOT allowed?
-
- Yes - any sort of attachment is allowed, although administrators can
- configure a maximum size. Bugzilla gives the user the option of either
- using the MIME-type supplied by the browser, choosing from a
- pre-defined list or manually typing any arbitrary MIME-type.
-
- A.2.6. Does Bugzilla allow us to define our own priorities and levels?
- Do we have complete freedom to change the labels of fields and format
- of them, and the choice of acceptable values?
-
- Yes. However, modifying some fields, notably those related to bug
- progression states, also require adjusting the program logic to
- compensate for the change.
-
- There is no GUI for adding fields to Bugzilla at this time. You can
- follow development of this feature at
- http://bugzilla.mozilla.org/show_bug.cgi?id=91037.
-
- A.2.7. Does Bugzilla provide any reporting features, metrics, graphs,
- etc? You know, the type of stuff that management likes to see. :)
-
- Yes. Look at http://bugzilla.mozilla.org/reports.cgi for samples of
- what Bugzilla can do in reporting and graphing.
-
- If you can not get the reports you want from the included reporting
- scripts, it is possible to hook up a professional reporting package
- such as Crystal Reports using ODBC. If you choose to do this, beware
- that giving direct access to the database does contain some security
- implications. Even if you give read-only access to the bugs database
- it will bypass the secure bugs features of Bugzilla.
-
- Note
-
- Bugzilla's current development versions can do a lot more in the way
- of reporting. To see examples, check out
- http://bugzilla.mozilla.org/report.cgi.
-
- A.2.8. Is there email notification and if so, what do you see when you
- get an email?
-
- Email notification is user-configurable. By default, the bug id and
- Summary of the bug report accompany each email notification, along
- with a list of the changes made.
-
- A.2.9. Can email notification be set up to send to multiple people,
- some on the To List, CC List, BCC List etc?
-
- Yes.
-
- A.2.10. Do users have to have any particular type of email
- application?
-
- Bugzilla email is sent in plain text, the most compatible mail format
- on the planet.
-
- Note
-
- If you decide to use the bugzilla_email integration features to allow
- Bugzilla to record responses to mail with the associated bug, you may
- need to caution your users to set their mailer to "respond to messages
- in the format in which they were sent". For security reasons Bugzilla
- ignores HTML tags in comments, and if a user sends HTML-based email
- into Bugzilla the resulting comment looks downright awful.
-
- A.2.11. Does Bugzilla allow data to be imported and exported? If I had
- outsiders write up a bug report using a MS Word bug template, could
- that template be imported into "matching" fields? If I wanted to take
- the results of a query and export that data to MS Excel, could I do
- that?
-
- Bugzilla can only output buglists as HTML in version 2.16. There are
- other formats available (CSV and RDF) in the newer development
- versions.
-
- Bugzilla can export bugs using xml.cgi with either a bug number or
- list of bug numbers.
-
- Currently the only script included with Bugzilla that can import data
- is importxml.pl which is intended to be used for importing the data
- generated by xml.cgi in association with bug moving. Any other use is
- left as an exercise for the user.
-
- There are also scripts included in the contrib/ directory for using
- e-mail to import information into Bugzilla, but these scripts are not
- currently supported and included for educational purposes.
-
- A.2.12. Has anyone converted Bugzilla to another language to be used
- in other countries? Is it localizable?
-
- Yes. For more information including available translated templates,
- see http://www.bugzilla.org/download.html#localizations. The admin
- interfaces are still not included in these translated templates and is
- therefore still English only. Also, there may be issues with the
- charset not being declared. See bug 126226 for more information.
-
- A.2.13. Can a user create and save reports? Can they do this in Word
- format? Excel format?
-
- Yes. No. Not in 2.16.
-
- A.2.14. Does Bugzilla have the ability to search by word, phrase,
- compound search?
-
- You have no idea. Bugzilla's query interface, particularly with the
- advanced Boolean operators, is incredibly versatile.
-
- A.2.15. Does Bugzilla provide record locking when there is
- simultaneous access to the same bug? Does the second person get a
- notice that the bug is in use or how are they notified?
-
- Bugzilla does not lock records. It provides mid-air collision
- detection, and offers the offending user a choice of options to deal
- with the conflict.
-
- A.2.16. Are there any backup features provided?
-
- MySQL, the database back-end for Bugzilla, allows hot-backup of data.
- You can find strategies for dealing with backup considerations at
- http://www.mysql.com/doc/B/a/Backup.html
-
- A.2.17. Can users be on the system while a backup is in progress?
-
- Yes. However, commits to the database must wait until the tables are
- unlocked. Bugzilla databases are typically very small, and backups
- routinely take less than a minute.
-
- A.2.18. What type of human resources are needed to be on staff to
- install and maintain Bugzilla? Specifically, what type of skills does
- the person need to have? I need to find out if we were to go with
- Bugzilla, what types of individuals would we need to hire and how much
- would that cost vs buying an "Out-of-the-Box" solution.
-
- If Bugzilla is set up correctly from the start, continuing maintenance
- needs are minimal and can be done easily using the web interface.
-
- Commercial Bug-tracking software typically costs somewhere upwards of
- $20,000 or more for 5-10 floating licenses. Bugzilla consultation is
- available from skilled members of the newsgroup. Simple questions are
- answered there and then.
-
- A.2.19. What time frame are we looking at if we decide to hire people
- to install and maintain the Bugzilla? Is this something that takes
- hours or weeks to install and a couple of hours per week to maintain
- and customize or is this a multi-week install process, plus a full
- time job for 1 person, 2 people, etc?
-
- It all depends on your level of commitment. Someone with much Bugzilla
- experience can get you up and running in less than a day, and your
- Bugzilla install can run untended for years. If your Bugzilla strategy
- is critical to your business workflow, hire somebody with reasonable
- UNIX or Perl skills to handle your process management and bug-tracking
- maintenance & customization.
-
- A.2.20. Is there any licensing fee or other fees for using Bugzilla?
- Any out-of-pocket cost other than the bodies needed as identified
- above?
-
- No. MySQL asks, if you find their product valuable, that you purchase
- a support contract from them that suits your needs.
-
-3. Bugzilla Security
-
- A.3.1. How do I completely disable MySQL security if it's giving me
- problems (I've followed the instructions in the installation section
- of this guide)?
-
- Run MySQL like this: "mysqld --skip-grant-tables". Please remember
- this makes MySQL as secure as taping a $100 to the floor of a football
- stadium bathroom for safekeeping.
-
- A.3.2. Are there any security problems with Bugzilla?
-
- The Bugzilla code has undergone a reasonably complete security audit,
- and user-facing CGIs run under Perl's taint mode. However, it is
- recommended that you closely examine permissions on your Bugzilla
- installation, and follow the recommended security guidelines found in
- The Bugzilla Guide.
-
- A.3.3. I've implemented the security fixes mentioned in Chris Yeh's
- security advisory of 5/10/2000 advising not to run MySQL as root, and
- am running into problems with MySQL no longer working correctly.
-
- This is a common problem, related to running out of file descriptors.
- Simply add "ulimit -n unlimited" to the script which starts mysqld.
-
-4. Bugzilla Email
-
- A.4.1. I have a user who doesn't want to receive any more email from
- Bugzilla. How do I stop it entirely for this user?
-
- The user should be able to set this in user email preferences (uncheck
- all boxes) or you can add their email address to the data/nomail file.
-
- A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send
- email to anyone but me. How do I do it?
-
- Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
- replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
-
- A.4.3. I want whineatnews.pl to whine at something more, or other
- than, only new bugs. How do I do it?
-
- Try Klaas Freitag's excellent patch for "whineatassigned"
- functionality. You can find it at
- http://bugzilla.mozilla.org/show_bug.cgi?id=6679. This patch is
- against an older version of Bugzilla, so you must apply the diffs
- manually.
-
- A.4.4. I don't like/want to use Procmail to hand mail off to
- bug_email.pl. What alternatives do I have?
-
- You can call bug_email.pl directly from your aliases file, with an
- entry like this:
-
- bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
-
- However, this is fairly nasty and subject to problems; you also need
- to set up your smrsh (sendmail restricted shell) to allow it. In a
- pinch, though, it can work.
-
- A.4.5. How do I set up the email interface to submit/change bugs via
- email?
-
- You can find an updated README.mailif file in the contrib/ directory
- of your Bugzilla distribution that walks you through the setup.
-
- A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's extremely
- slow. What gives?
-
- If you are using an alternate Mail Transport Agent (MTA other than
- sendmail), make sure the options given in the "processmail" and other
- scripts for all instances of "sendmail" are correct for your MTA.
-
- If you are using Sendmail, try enabling "sendmailnow" in
- editparams.cgi. If you are using Postfix, you will also need to enable
- "sendmailnow".
-
- A.4.7. How come email from Bugzilla changes never reaches me?
-
- Double-check that you have not turned off email in your user
- preferences. Confirm that Bugzilla is able to send email by visiting
- the "Log In" link of your Bugzilla installation and clicking the
- "Email me a password" button after entering your email address.
-
- If you never receive mail from Bugzilla, chances you do not have
- sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is
- symlinked to, "/usr/lib/sendmail".
-
-5. Bugzilla Database
-
- A.5.1. I've heard Bugzilla can be used with Oracle?
-
- Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. Red
- Hat's newer version (based on 2.17.1 and soon to be merged into the
- main distribution) runs on PostgreSQL. At this time we know of no
- recent ports of Bugzilla to Oracle but do intend to support it in the
- future (possibly the 2.20 time-frame).
-
- A.5.2. I think my database might be corrupted, or contain invalid
- entries. What do I do?
-
- Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home
- directory) from your web browser to see! If it finishes without
- errors, you're probably OK. If it doesn't come back OK (i.e. any red
- letters), there are certain things Bugzilla can recover from and
- certain things it can't. If it can't auto-recover, I hope you're
- familiar with mysqladmin commands or have installed another way to
- manage your database. Sanity Check, although it is a good basic check
- on your database integrity, by no means is a substitute for competent
- database administration and avoiding deletion of data. It is not
- exhaustive, and was created to do a basic check for the most common
- problems in Bugzilla databases.
-
- A.5.3. I want to manually edit some entries in my database. How?
-
- There is no facility in Bugzilla itself to do this. It's also
- generally not a smart thing to do if you don't know exactly what
- you're doing. However, if you understand SQL you can use the mysql
- command line utility to manually insert, delete and modify table
- information. There are also more intuitive GUI clients available.
- Personal favorites of the Bugzilla team are phpMyAdmin and MySQL
- Control Center.
-
- A.5.4. I think I've set up MySQL permissions correctly, but Bugzilla
- still can't connect.
-
- Try running MySQL from its binary: "mysqld --skip-grant-tables". This
- will allow you to completely rule out grant tables as the cause of
- your frustration. If this Bugzilla is able to connect at this point
- then you need to check that you have granted proper permission to the
- user password combo defined in localconfig.
-
- Warning
-
- Running MySQL with this command line option is very insecure and
- should only be done when not connected to the external network as a
- troubleshooting step.
-
- A.5.5. How do I synchronize bug information among multiple different
- Bugzilla databases?
-
- Well, you can synchronize or you can move bugs. Synchronization will
- only work one way -- you can create a read-only copy of the database
- at one site, and have it regularly updated at intervals from the main
- database.
-
- MySQL has some synchronization features builtin to the latest
- releases. It would be great if someone looked into the possibilities
- there and provided a report to the newsgroup on how to effectively
- synchronize two Bugzilla installations.
-
- If you simply need to transfer bugs from one Bugzilla to another,
- checkout the "move.pl" script in the Bugzilla distribution.
-
-6. Bugzilla and Win32
-
- A.6.1. What is the easiest way to run Bugzilla on Win32
- (Win98+/NT/2K)?
-
- Remove Windows. Install Linux. Install Bugzilla. The boss will never
- know the difference.
-
- A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32?
-
- Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
- installation on UNIX systems. If someone can volunteer to create a
- suitable PPM bundle for Win32, it would be appreciated.
-
- A.6.3. CGI's are failing with a "something.cgi is not a valid Windows
- NT application" error. Why?
-
- Depending on what Web server you are using, you will have to configure
- the Web server to treat *.cgi files as CGI scripts. In IIS, you do
- this by adding *.cgi to the App Mappings with the <path>\perl.exe %s
- %s as the executable.
-
- Microsoft has some advice on this matter, as well:
-
- "Set application mappings. In the ISM, map the extension for the
- script file(s) to the executable for the script interpreter. For
- example, you might map the extension .py to Python.exe, the
- executable for the Python script interpreter. Note For the
- ActiveState Perl script interpreter, the extension .pl is
- associated with PerlIS.dll by default. If you want to change the
- association of .pl to perl.exe, you need to change the application
- mapping. In the mapping, you must add two percent (%) characters to
- the end of the pathname for perl.exe, as shown in this example:
- c:\perl\bin\perl.exe %s %s"
-
- A.6.4. I'm having trouble with the perl modules for NT not being able
- to talk to to the database.
-
- Your modules may be outdated or inaccurate. Try:
-
- 1. Hitting http://www.activestate.com/ActivePerl
- 2. Download ActivePerl
- 3. Go to your prompt
- 4. Type 'ppm'
- 5. PPM> install DBI DBD-mysql GD
-
- I reckon TimeDate and Data::Dumper come with the activeperl. You can
- check the ActiveState site for packages for installation through PPM.
- http://www.activestate.com/Packages/
-
-7. Bugzilla Usage
-
- A.7.1. How do I change my user name (email address) in Bugzilla?
-
- New in 2.16 - go to the Account section of the Preferences. You will
- be emailed at both addresses for confirmation.
-
- A.7.2. The query page is very confusing. Isn't there a simpler way to
- query?
-
- The interface was simplified by a UI designer for 2.16. Further
- suggestions for improvement are welcome, but we won't sacrifice power
- for simplicity.
-
- A.7.3. I'm confused by the behavior of the "accept" button in the Show
- Bug form. Why doesn't it assign the bug to me when I accept it?
-
- The current behavior is acceptable to bugzilla.mozilla.org and most
- users. You have your choice of patches to change this behavior,
- however.
-
- Add a "and accept bug" radio button
- "Accept" button automatically assigns to you
-
- Note that these patches are somewhat dated. You will need to apply
- them manually.
-
- A.7.4. I can't upload anything into the database via the "Create
- Attachment" link. What am I doing wrong?
-
- The most likely cause is a very old browser or a browser that is
- incompatible with file upload via POST. Download the latest Netscape,
- Microsoft, or Mozilla browser to handle uploads correctly.
-
- A.7.5. How do I change a keyword in Bugzilla, once some bugs are using
- it?
-
- In the Bugzilla administrator UI, edit the keyword and it will let you
- replace the old keyword name with a new one. This will cause a problem
- with the keyword cache. Run sanitycheck.cgi to fix it.
-
- A.7.6. Why can't I close bugs from the "Change Several Bugs at Once"
- page?
-
- The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
- You can mass-CLOSE bugs from the change several bugs at once page.
- but, every bug listed on the page has to be in VERIFIED state before
- the control to do it will show up on the form. You can also
- mass-VERIFY, but every bug listed has to be RESOLVED in order for the
- control to show up on the form. The logic behind this is that if you
- pick one of the bugs that's not VERIFIED and try to CLOSE it, the bug
- change will fail miserably (thus killing any changes in the list after
- it while doing the bulk change) so it doesn't even give you the
- choice.
-
-8. Bugzilla Hacking
-
- A.8.1. What bugs are in Bugzilla right now?
-
- Try this link to view current bugs or requests for enhancement for
- Bugzilla.
-
- You can view bugs marked for 2.18 release here. This list includes
- bugs for the 2.18 release that have already been fixed and checked
- into CVS. Please consult the Bugzilla Project Page for details on how
- to check current sources out of CVS so you can have these bug fixes
- early!
-
- A.8.2. How can I change the default priority to a null value? For
- instance, have the default priority be "---" instead of "P2"?
-
- This is well-documented here:
- http://bugzilla.mozilla.org/show_bug.cgi?id=49862. Ultimately, it's as
- easy as adding the "---" priority field to your localconfig file in
- the appropriate area, re-running checksetup.pl, and then changing the
- default priority in your browser using "editparams.cgi".
-
- A.8.3. What's the best way to submit patches? What guidelines should I
- follow?
-
- 1. Enter a bug into bugzilla.mozilla.org for the "Bugzilla" product.
- 2. Upload your patch as a unified diff (having used "diff -u" against
- the current sources checked out of CVS), or new source file by
- clicking "Create a new attachment" link on the bug page you've
- just created, and include any descriptions of database changes you
- may make, into the bug ID you submitted in step #1. Be sure and
- click the "Patch" checkbox to indicate the text you are sending is
- a patch!
- 3. Announce your patch and the associated URL
- (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for
- discussion in the newsgroup (netscape.public.mozilla.webtools).
- You'll get a really good, fairly immediate reaction to the
- implications of your patch, which will also give us an idea how
- well-received the change would be.
- 4. If it passes muster with minimal modification, the person to whom
- the bug is assigned in Bugzilla is responsible for seeing the
- patch is checked into CVS.
- 5. Bask in the glory of the fact that you helped write the most
- successful open-source bug-tracking software on the planet :)
- _________________________________________________________________
-
-Appendix B. The Bugzilla Database
-
- Note
-
- This document really needs to be updated with more fleshed out
- information about primary keys, interrelationships, and maybe some
- nifty tables to document dependencies. Any takers?
- _________________________________________________________________
-
-B.1. Database Schema Chart
-
- [dbschema.jpg]
-
- Bugzilla database relationships chart
- _________________________________________________________________
-
-B.2. MySQL Bugzilla Database Introduction
-
- This information comes straight from my life. I was forced to learn
- how Bugzilla organizes database because of nitpicky requests from
- users for tiny changes in wording, rather than having people
- re-educate themselves or figure out how to work our procedures around
- the tool. It sucks, but it can and will happen to you, so learn how
- the schema works and deal with it when it comes.
-
- So, here you are with your brand-new installation of Bugzilla. You've
- got MySQL set up, Apache working right, Perl DBI and DBD talking to
- the database flawlessly. Maybe you've even entered a few test bugs to
- make sure email's working; people seem to be notified of new bugs and
- changes, and you can enter and edit bugs to your heart's content.
- Perhaps you've gone through the trouble of setting up a gateway for
- people to submit bugs to your database via email, have had a few
- people test it, and received rave reviews from your beta testers.
-
- What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new
- tool you've labored over for hours.
-
- Your first training session starts off very well! You have a captive
- audience which seems enraptured by the efficiency embodied in this
- thing called "Bugzilla". You are caught up describing the nifty
- features, how people can save favorite queries in the database, set
- them up as headers and footers on their pages, customize their
- layouts, generate reports, track status with greater efficiency than
- ever before, leap tall buildings with a single bound and rescue Jane
- from the clutches of Certain Death!
-
- But Certain Death speaks up -- a tiny voice, from the dark corners of
- the conference room. "I have a concern," the voice hisses from the
- darkness, "about the use of the word 'verified'.
-
- The room, previously filled with happy chatter, lapses into
- reverential silence as Certain Death (better known as the Vice
- President of Software Engineering) continues. "You see, for two years
- we've used the word 'verified' to indicate that a developer or quality
- assurance engineer has confirmed that, in fact, a bug is valid. I
- don't want to lose two years of training to a new software product.
- You need to change the bug status of 'verified' to 'approved' as soon
- as possible. To avoid confusion, of course."
-
- Oh no! Terror strikes your heart, as you find yourself mumbling "yes,
- yes, I don't think that would be a problem," You review the changes
- with Certain Death, and continue to jabber on, "no, it's not too big a
- change. I mean, we have the source code, right? You know, 'Use the
- Source, Luke' and all that... no problem," All the while you quiver
- inside like a beached jellyfish bubbling, burbling, and boiling on a
- hot Jamaican sand dune...
-
- Thus begins your adventure into the heart of Bugzilla. You've been
- forced to learn about non-portable enum() fields, varchar columns, and
- tinyint definitions. The Adventure Awaits You!
- _________________________________________________________________
-
-B.2.1. Bugzilla Database Basics
-
- If you were like me, at this point you're totally clueless about the
- internals of MySQL, and if it weren't for this executive order from
- the Vice President you couldn't care less about the difference between
- a "bigint" and a "tinyint" entry in MySQL. I recommend you refer to
- the MySQL documentation, available at MySQL.com . Below are the basics
- you need to know about the Bugzilla database. Check the chart above
- for more details.
-
- 1. To connect to your database:
- bash# mysql -u root
- If this works without asking you for a password, shame on you !
- You should have locked your security down like the installation
- instructions told you to. You can find details on locking down
- your database in the Bugzilla FAQ in this directory (under
- "Security"), or more robust security generalities in the MySQL
- searchable documentation.
- 2. You should now be at a prompt that looks like this:
- mysql>
- At the prompt, if "bugs" is the name you chose in the localconfig
- file for your Bugzilla database, type:
- mysql use bugs;
- _________________________________________________________________
-
-B.2.1.1. Bugzilla Database Tables
-
- Imagine your MySQL database as a series of spreadsheets, and you won't
- be too far off. If you use this command:
-
- mysql> show tables from bugs;
-
- you'll be able to see the names of all the "spreadsheets" (tables) in
- your database.
-
- From the command issued above, ou should have some output that looks
- like this:
- +-------------------+
- | Tables in bugs |
- +-------------------+
- | attachments |
- | bugs |
- | bugs_activity |
- | cc |
- | components |
- | dependencies |
- | fielddefs |
- | groups |
- | keyworddefs |
- | keywords |
- | logincookies |
- | longdescs |
- | milestones |
- | namedqueries |
- | products |
- | profiles |
- | profiles_activity |
- | shadowlog |
- | tokens |
- | versions |
- | votes |
- | watch |
- +-------------------+
-
- Here's an overview of what each table does. Most columns in each ta
- ble have
- descriptive names that make it fairly trivial to figure out their jobs
- .
- attachments: This table stores all attachments to bugs. It tends to b
- e your
- largest table, yet also generally has the fewest entries because file
- attachments are so (relatively) large.
- bugs: This is the core of your system. The bugs table stores most of
- the
- current information about a bug, with the exception of the info stored
- in the
- other tables.
- bugs_activity: This stores information regarding what changes are mad
- e to bugs
- when -- a history file.
- cc: This tiny table simply stores all the CC information for any bug
- which has
- any entries in the CC field of the bug. Note that, like most other ta
- bles in
- Bugzilla, it does not refer to users by their user names, but by their
- unique
- userid, stored as a primary key in the profiles table.
- components: This stores the programs and components (or products and
- components, in newer Bugzilla parlance) for Bugzilla. Curiously, the
- "program"
- (product) field is the full name of the product, rather than some othe
- r unique
- identifier, like bug_id and user_id are elsewhere in the database.
- dependencies: Stores data about those cool dependency trees.
- fielddefs: A nifty table that defines other tables. For instance, wh
- en you
- submit a form that changes the value of "AssignedTo" this table allows
- translation to the actual field name "assigned_to" for entry into MySQ
- L.
- groups: defines bitmasks for groups. A bitmask is a number that can
- uniquely
- identify group memberships. For instance, say the group that is allow
- ed to
- tweak parameters is assigned a value of "1", the group that is allowed
- to edit
- users is assigned a "2", and the group that is allowed to create new g
- roups is
- assigned the bitmask of "4". By uniquely combining the group bitmasks
- (much
- like the chmod command in UNIX,) you can identify a user is allowed to
- tweak
- parameters and create groups, but not edit users, by giving him a bitm
- ask of
- "5", or a user allowed to edit users and create groups, but not tweak
- parameters, by giving him a bitmask of "6" Simple, huh?
- If this makes no sense to you, try this at the mysql prompt:
- mysql> select * from groups;
- You'll see the list, it makes much more sense that way.
- keyworddefs: Definitions of keywords to be used
- keywords: Unlike what you'd think, this table holds which keywords are
- associated with which bug id's.
- logincookies: This stores every login cookie ever assigned to you for
- every
- machine you've ever logged into Bugzilla from. Curiously, it never do
- es any
- housecleaning -- I see cookies in this file I've not used for months.
- However,
- since Bugzilla never expires your cookie (for convenience' sake), it m
- akes
- sense.
- longdescs: The meat of bugzilla -- here is where all user comments ar
- e stored!
- You've only got 2^24 bytes per comment (it's a mediumtext field), so s
- peak
- sparingly -- that's only the amount of space the Old Testament from th
- e Bible
- would take (uncompressed, 16 megabytes). Each comment is keyed to the
- bug_id to which it's attached, so the order is necessarily chronologic
- al, for
- comments are played back in the order in which they are received.
- milestones: Interesting that milestones are associated with a specifi
- c product
- in this table, but Bugzilla does not yet support differing milestones
- by
- product through the standard configuration interfaces.
- namedqueries: This is where everybody stores their "custom queries".
- Very
- cool feature; it beats the tar out of having to bookmark each cool que
- ry you
- construct.
- products: What products you have, whether new bug entries are allowed
- for the
- product, what milestone you're working toward on that product, votes,
- etc. It
- will be nice when the components table supports these same features, s
- o you
- could close a particular component for bug entry without having to clo
- se an
- entire product...
- profiles: Ahh, so you were wondering where your precious user informa
- tion was
- stored? Here it is! With the passwords in plain text for all to see!
- (but
- sshh... don't tell your users!)
- profiles_activity: Need to know who did what when to who's profile?
- This'll
- tell you, it's a pretty complete history.
- shadowlog: I could be mistaken here, but I believe this table tells y
- ou when
- your shadow database is updated and what commands were used to update
- it. We
- don't use a shadow database at our site yet, so it's pretty empty for
- us.
- versions: Version information for every product
- votes: Who voted for what when
- watch: Who (according to userid) is watching who's bugs (according to
- their
- userid).
- ===
- THE DETAILS
- ===
- Ahh, so you're wondering just what to do with the information above?
- At the
- mysql prompt, you can view any information about the columns in a tabl
- e with
- this command (where "table" is the name of the table you wish to view)
- :
- mysql> show columns from table;
- You can also view all the data in a table with this command:
- mysql> select * from table;
- -- note: this is a very bad idea to do on, for instance, the "bugs"
- table if
- you have 50,000 bugs. You'll be sitting there a while until you ctrl-
- c or
- 50,000 bugs play across your screen.
- You can limit the display from above a little with the command, wher
- e
- "column" is the name of the column for which you wish to restrict info
- rmation:
- mysql> select * from table where (column = "some info");
- -- or the reverse of this
- mysql> select * from table where (column != "some info");
- Let's take our example from the introduction, and assume you need to
- change
- the word "verified" to "approved" in the resolution field. We know fr
- om the
- above information that the resolution is likely to be stored in the "b
- ugs"
- table. Note we'll need to change a little perl code as well as this da
- tabase
- change, but I won't plunge into that in this document. Let's verify th
- e
- information is stored in the "bugs" table:
- mysql> show columns from bugs
- (exceedingly long output truncated here)
- | bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED
- ','VERIFIED','CLOSED')||MUL | UNCONFIRMED||
- Sorry about that long line. We see from this that the "bug status"
- column is
- an "enum field", which is a MySQL peculiarity where a string type fiel
- d can
- only have certain types of entries. While I think this is very cool,
- it's not
- standard SQL. Anyway, we need to add the possible enum field entry
- 'APPROVED' by altering the "bugs" table.
- mysql> ALTER table bugs CHANGE bug_status bug_status
- -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
- -> "VERIFIED", "APPROVED", "CLOSED") not null;
- (note we can take three lines or more -- whatever you put in befor
- e the
- semicolon is evaluated as a single expression)
- Now if you do this:
- mysql> show columns from bugs;
- you'll see that the bug_status field has an extra "APPROVED" enum th
- at's
- available! Cool thing, too, is that this is reflected on your query p
- age as
- well -- you can query by the new status. But how's it fit into the ex
- isting
- scheme of things?
- Looks like you need to go back and look for instances of the word "v
- erified"
- in the perl code for Bugzilla -- wherever you find "verified", change
- it to
- "approved" and you're in business (make sure that's a case-insensitive
- search).
- Although you can query by the enum field, you can't give something a s
- tatus
- of "APPROVED" until you make the perl changes. Note that this change
- I
- mentioned can also be done by editing checksetup.pl, which automates a
- lot of
- this. But you need to know this stuff anyway, right?
- _________________________________________________________________
-
-Appendix C. Useful Patches and Utilities for Bugzilla
-
- Are you looking for a way to put your Bugzilla into overdrive? Catch
- some of the niftiest tricks here in this section.
- _________________________________________________________________
-
-C.1. Apache mod_rewrite magic
-
- Apache's mod_rewrite module lets you do some truly amazing things with
- URL rewriting. Here are a couple of examples of what you can do.
-
- 1. Make it so if someone types http://www.foo.com/12345 , Bugzilla
- spits back http://www.foo.com/show_bug.cgi?id=12345. Try setting
- up your VirtualHost section for Bugzilla with a rule like this:
-
- <VirtualHost 12.34.56.78>
- RewriteEngine On
- RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
- </VirtualHost>
-
- 2. There are many, many more things you can do with mod_rewrite.
- Please refer to the mod_rewrite documentation at
- http://www.apache.org.
- _________________________________________________________________
-
-C.2. Command-line Bugzilla Queries
-
- There are a suite of Unix utilities for querying Bugzilla from the
- command line. They live in the contrib/cmdline directory. However,
- they have not yet been updated to work with 2.16
- (post-templatisation.). There are three files - query.conf, buglist
- and bugs.
-
- query.conf contains the mapping from options to field names and
- comparison types. Quoted option names are "grepped" for, so it should
- be easy to edit this file. Comments (#) have no effect; you must make
- sure these lines do not contain any quoted "option".
-
- buglist is a shell script which submits a Bugzilla query and writes
- the resulting HTML page to stdout. It supports both short options,
- (such as "-Afoo" or "-Rbar") and long options (such as
- "--assignedto=foo" or "--reporter=bar"). If the first character of an
- option is not "-", it is treated as if it were prefixed with
- "--default=".
-
- The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the "Change Columns" option when you list bugs
- in buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
- in your cookies file to see your current COLUMNLIST setting.
-
- bugs is a simple shell script which calls buglist and extracts the bug
- numbers from the output. Adding the prefix
- "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list
- into a working link if any bugs are found. Counting bugs is easy. Pipe
- the results through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
-
- Akkana Peck says she has good results piping buglist output through
- w3m -T text/html -dump
- _________________________________________________________________
-
-Appendix D. Bugzilla Variants and Competitors
-
- I created this section to answer questions about Bugzilla competitors
- and variants, then found a wonderful site which covers an awful lot of
- what I wanted to discuss. Rather than quote it in its entirety, I'll
- simply refer you here: http://linas.org/linux/pm.html
- _________________________________________________________________
-
-D.1. Red Hat Bugzilla
-
- Red Hat's old fork of Bugzilla which was based on version 2.8 is now
- obsolete. The newest version in use is based on version 2.17.1 and is
- in the process of being integrated into the main Bugzilla source tree.
- The back-end is modified to work with PostgreSQL instead of MySQL and
- they have custom templates to get their desired look and feel, but
- other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put
- forth a great deal of effort to make sure that the changes he made
- could be integrated back into the main tree. Bug 98304 exists to track
- this integration.
-
- URL: http://bugzilla.redhat.com/bugzilla/
-
- This section last updated 24 Dec 2002
- _________________________________________________________________
-
-D.2. Loki Bugzilla (Fenris)
-
- Fenris was a fork from Bugzilla made by Loki Games; when Loki went
- into receivership, it died. While Loki's other code lives on, its
- custodians recommend Bugzilla for future bug-tracker deployments.
-
- This section last updated 27 Jul 2002
- _________________________________________________________________
-
-D.3. Issuezilla
-
- Issuezilla was another fork from Bugzilla, made by collab.net and
- hosted at tigris.org. It is also dead; the primary focus of
- bug-tracking at tigris.org is their Java-based bug-tracker, Section
- D.4.
-
- This section last updated 27 Jul 2002
- _________________________________________________________________
-
-D.4. Scarab
-
- Scarab is a new open source bug-tracking system built using Java
- Servlet technology. It is currently at version 1.0 beta 13.
-
- URL: http://scarab.tigris.org
-
- This section last updated 18 Jan 2003
- _________________________________________________________________
-
-D.5. Perforce SCM
-
- Although Perforce isn't really a bug tracker, it can be used as such
- through the "jobs" functionality.
-
- URL: http://www.perforce.com/perforce/technotes/note052.html
-
- This section last updated 27 Jul 2002
- _________________________________________________________________
-
-D.6. SourceForge
-
- SourceForge is a way of coordinating geographically distributed free
- software and open source projects over the Internet. It has a built-in
- bug tracker, but it's not highly thought of.
-
- URL: http://www.sourceforge.net
-
- This section last updated 27 Jul 2002
- _________________________________________________________________
-
-Appendix E. GNU Free Documentation License
-
- Version 1.1, March 2000
-
- Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy
- and distribute verbatim copies of this license document, but
- changing it is not allowed.
- _________________________________________________________________
-
-0. PREAMBLE
-
- The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone
- the effective freedom to copy and redistribute it, with or without
- modifying it, either commercially or noncommercially. Secondarily,
- this License preserves for the author and publisher a way to get
- credit for their work, while not being considered responsible for
- modifications made by others.
-
- This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft
- license designed for free software.
-
- We have designed this License in order to use it for manuals for free
- software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or
- whether it is published as a printed book. We recommend this License
- principally for works whose purpose is instruction or reference.
- _________________________________________________________________
-
-1. APPLICABILITY AND DEFINITIONS
-
- This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed
- under the terms of this License. The "Document", below, refers to any
- such manual or work. Any member of the public is a licensee, and is
- addressed as "you".
-
- A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.
-
- A "Secondary Section" is a named appendix or a front-matter section of
- the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall
- subject (or to related matters) and contains nothing that could fall
- directly within that overall subject. (For example, if the Document is
- in part a textbook of mathematics, a Secondary Section may not explain
- any mathematics.) The relationship could be a matter of historical
- connection with the subject or with related matters, or of legal,
- commercial, philosophical, ethical or political position regarding
- them.
-
- The "Invariant Sections" are certain Secondary Sections whose titles
- are designated, as being those of Invariant Sections, in the notice
- that says that the Document is released under this License.
-
- The "Cover Texts" are certain short passages of text that are listed,
- as Front-Cover Texts or Back-Cover Texts, in the notice that says that
- the Document is released under this License.
-
- A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the
- general public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or
- for automatic translation to a variety of formats suitable for input
- to text formatters. A copy made in an otherwise Transparent file
- format whose markup has been designed to thwart or discourage
- subsequent modification by readers is not Transparent. A copy that is
- not "Transparent" is called "Opaque".
-
- Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML
- or XML using a publicly available DTD, and standard-conforming simple
- HTML designed for human modification. Opaque formats include
- PostScript, PDF, proprietary formats that can be read and edited only
- by proprietary word processors, SGML or XML for which the DTD and/or
- processing tools are not generally available, and the
- machine-generated HTML produced by some word processors for output
- purposes only.
-
- The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in
- formats which do not have any title page as such, "Title Page" means
- the text near the most prominent appearance of the work's title,
- preceding the beginning of the body of the text.
- _________________________________________________________________
-
-2. VERBATIM COPYING
-
- You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies
- to the Document are reproduced in all copies, and that you add no
- other conditions whatsoever to those of this License. You may not use
- technical measures to obstruct or control the reading or further
- copying of the copies you make or distribute. However, you may accept
- compensation in exchange for copies. If you distribute a large enough
- number of copies you must also follow the conditions in section 3.
-
- You may also lend copies, under the same conditions stated above, and
- you may publicly display copies.
- _________________________________________________________________
-
-3. COPYING IN QUANTITY
-
- If you publish printed copies of the Document numbering more than 100,
- and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all
- these Cover Texts: Front-Cover Texts on the front cover, and
- Back-Cover Texts on the back cover. Both covers must also clearly and
- legibly identify you as the publisher of these copies. The front cover
- must present the full title with all words of the title equally
- prominent and visible. You may add other material on the covers in
- addition. Copying with changes limited to the covers, as long as they
- preserve the title of the Document and satisfy these conditions, can
- be treated as verbatim copying in other respects.
-
- If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit
- reasonably) on the actual cover, and continue the rest onto adjacent
- pages.
-
- If you publish or distribute Opaque copies of the Document numbering
- more than 100, you must either include a machine-readable Transparent
- copy along with each Opaque copy, or state in or with each Opaque copy
- a publicly-accessible computer-network location containing a complete
- Transparent copy of the Document, free of added material, which the
- general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location
- until at least one year after the last time you distribute an Opaque
- copy (directly or through your agents or retailers) of that edition to
- the public.
-
- It is requested, but not required, that you contact the authors of the
- Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.
- _________________________________________________________________
-
-4. MODIFICATIONS
-
- You may copy and distribute a Modified Version of the Document under
- the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution
- and modification of the Modified Version to whoever possesses a copy
- of it. In addition, you must do these things in the Modified Version:
-
- A. Use in the Title Page (and on the covers, if any) a title distinct
- from that of the Document, and from those of previous versions
- (which should, if there were any, be listed in the History section
- of the Document). You may use the same title as a previous version
- if the original publisher of that version gives permission.
- B. List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has
- less than five).
- C. State on the Title page the name of the publisher of the Modified
- Version, as the publisher.
- D. Preserve all the copyright notices of the Document.
- E. Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.
- F. Include, immediately after the copyright notices, a license notice
- giving the public permission to use the Modified Version under the
- terms of this License, in the form shown in the Addendum below.
- G. Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.
- H. Include an unaltered copy of this License.
- I. Preserve the section entitled "History", and its title, and add to
- it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.
- J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the "History" section. You
- may omit a network location for a work that was published at least
- four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.
- K. In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements
- and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document, unaltered in
- their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.
- M. Delete any section entitled "Endorsements". Such a section may not
- be included in the Modified Version.
- N. Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.
-
- If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all
- of these sections as invariant. To do this, add their titles to the
- list of Invariant Sections in the Modified Version's license notice.
- These titles must be distinct from any other section titles.
-
- You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various
- parties--for example, statements of peer review or that the text has
- been approved by an organization as the authoritative definition of a
- standard.
-
- You may add a passage of up to five words as a Front-Cover Text, and a
- passage of up to 25 words as a Back-Cover Text, to the end of the list
- of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document already
- includes a cover text for the same cover, previously added by you or
- by arrangement made by the same entity you are acting on behalf of,
- you may not add another; but you may replace the old one, on explicit
- permission from the previous publisher that added the old one.
-
- The author(s) and publisher(s) of the Document do not by this License
- give permission to use their names for publicity for or to assert or
- imply endorsement of any Modified Version.
- _________________________________________________________________
-
-5. COMBINING DOCUMENTS
-
- You may combine the Document with other documents released under this
- License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and
- list them all as Invariant Sections of your combined work in its
- license notice.
-
- The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single
- copy. If there are multiple Invariant Sections with the same name but
- different contents, make the title of each such section unique by
- adding at the end of it, in parentheses, the name of the original
- author or publisher of that section if known, or else a unique number.
- Make the same adjustment to the section titles in the list of
- Invariant Sections in the license notice of the combined work.
-
- In the combination, you must combine any sections entitled "History"
- in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements",
- and any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."
- _________________________________________________________________
-
-6. COLLECTIONS OF DOCUMENTS
-
- You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual
- copies of this License in the various documents with a single copy
- that is included in the collection, provided that you follow the rules
- of this License for verbatim copying of each of the documents in all
- other respects.
-
- You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a
- copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
- _________________________________________________________________
-
-7. AGGREGATION WITH INDEPENDENT WORKS
-
- A compilation of the Document or its derivatives with other separate
- and independent documents or works, in or on a volume of a storage or
- distribution medium, does not as a whole count as a Modified Version
- of the Document, provided no compilation copyright is claimed for the
- compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they
- are not themselves derivative works of the Document.
-
- If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter
- of the entire aggregate, the Document's Cover Texts may be placed on
- covers that surround only the Document within the aggregate. Otherwise
- they must appear on covers around the whole aggregate.
- _________________________________________________________________
-
-8. TRANSLATION
-
- Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include
- translations of some or all Invariant Sections in addition to the
- original versions of these Invariant Sections. You may include a
- translation of this License provided that you also include the
- original English version of this License. In case of a disagreement
- between the translation and the original English version of this
- License, the original English version will prevail.
- _________________________________________________________________
-
-9. TERMINATION
-
- You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt
- to copy, modify, sublicense or distribute the Document is void, and
- will automatically terminate your rights under this License. However,
- parties who have received copies, or rights, from you under this
- License will not have their licenses terminated so long as such
- parties remain in full compliance.
- _________________________________________________________________
-
-10. FUTURE REVISIONS OF THIS LICENSE
-
- The Free Software Foundation may publish new, revised versions of the
- GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- http://www.gnu.org/copyleft/ .
-
- Each version of the License is given a distinguishing version number.
- If the Document specifies that a particular numbered version of this
- License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or
- of any later version that has been published (not as a draft) by the
- Free Software Foundation. If the Document does not specify a version
- number of this License, you may choose any version ever published (not
- as a draft) by the Free Software Foundation.
- _________________________________________________________________
-
-How to use this License for your documents
-
- To use this License in a document you have written, include a copy of
- the License in the document and put the following copyright and
- license notices just after the title page:
-
- Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU
- Free Documentation License, Version 1.1 or any later version
- published by the Free Software Foundation; with the Invariant
- Sections being LIST THEIR TITLES, with the Front-Cover Texts being
- LIST, and with the Back-Cover Texts being LIST. A copy of the
- license is included in the section entitled "GNU Free Documentation
- License".
-
- If you have no Invariant Sections, write "with no Invariant Sections"
- instead of saying which ones are invariant. If you have no Front-Cover
- Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts
- being LIST"; likewise for Back-Cover Texts.
-
- If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of
- free software license, such as the GNU General Public License, to
- permit their use in free software.
-
-Glossary
-
-0-9, high ascii
-
- .htaccess
- Apache web server, and other NCSA-compliant web servers,
- observe the convention of using files in directories called
- .htaccess to restrict access to certain files. In Bugzilla,
- they are used to keep secret files which would otherwise
- compromise your installation - e.g. the localconfig file
- contains the password to your database. curious.
-
-A
-
- Apache
- In this context, Apache is the web server most commonly used
- for serving up Bugzilla pages. Contrary to popular belief, the
- apache web server has nothing to do with the ancient and noble
- Native American tribe, but instead derived its name from the
- fact that it was "a patchy" version of the original NCSA
- world-wide-web server.
-
- Useful Directives when configuring Bugzilla
-
- AddHandler
- Tell Apache that it's OK to run CGI scripts.
-
- AllowOverride, Options
- These directives are used to tell Apache many things
- about the directory they apply to. For Bugzilla's
- purposes, we need them to allow script execution and
- .htaccess overrides.
-
- DirectoryIndex
- Used to tell Apache what files are indexes. If you can
- not add index.cgi to the list of valid files, you'll need
- to set $index_html to 1 in localconfig so ./checksetup.pl
- will create an index.html that redirects to index.cgi.
-
- ScriptInterpreterSource
- Used when running Apache on windows so the shebang line
- doesn't have to be changed in every Bugzilla script.
-
-B
-
- Bug
- A "bug" in Bugzilla refers to an issue entered into the
- database which has an associated number, assignments, comments,
- etc. Some also refer to a "tickets" or "issues"; in the context
- of Bugzilla, they are synonymous.
-
- Bug Number
- Each Bugzilla bug is assigned a number that uniquely identifies
- that bug. The bug associated with a bug number can be pulled up
- via a query, or easily from the very front page by typing the
- number in the "Find" box.
-
- Bugzilla
- Bugzilla is the world-leading free software bug tracking
- system.
-
-C
-
- Common Gateway Interface (CGI)
- CGI is an acronym for Common Gateway Interface. This is a
- standard for interfacing an external application with a web
- server. Bugzilla is an example of a CGI application.
-
- Component
- A Component is a subsection of a Product. It should be a narrow
- category, tailored to your organization. All Products must
- contain at least one Component (and, as a matter of fact,
- creating a Product with no Components will create an error in
- Bugzilla).
-
- CPAN
- CPAN stands for the "Comprehensive Perl Archive Network". CPAN
- maintains a large number of extremely useful Perl modules -
- encapsulated chunks of code for performing a particular task.
-
-D
-
- daemon
- A daemon is a computer program which runs in the background. In
- general, most daemons are started at boot time via System V
- init scripts, or through RC scripts on BSD-based systems.
- mysqld, the MySQL server, and apache, a web server, are
- generally run as daemons.
-
-G
-
- Groups
- The word "Groups" has a very special meaning to Bugzilla.
- Bugzilla's main security mechanism comes by placing users in
- groups, and assigning those groups certain privileges to view
- bugs in particular Products in the Bugzilla database.
-
-M
-
- Message Transport Agent (MTA)
- A Message Transport Agent is used to control the flow of email
- on a system. Many unix based systems use sendmail which is what
- Bugzilla expects to find by default at /usr/sbin/sendmail. Many
- other MTA's will work, but they all require that the
- sendmailnow param be set to on.
-
- MySQL
- MySQL is currently the required RDBMS for Bugzilla. MySQL can
- be downloaded from http://www.mysql.com. While you should
- familiarize yourself with all of the documentation, some high
- points are:
-
- + MySQL Privilege System - Much more detailed information about
- the suggestions in Section 5.6.2.
-
-P
-
- Product
- A Product is a broad category of types of bugs, normally
- representing a single piece of software or entity. In general,
- there are several Components to a Product. A Product may define
- a group (used for security) for all bugs entered into its
- Components.
-
- Perl
- First written by Larry Wall, Perl is a remarkable program
- language. It has the benefits of the flexibility of an
- interpreted scripting language (such as shell script), combined
- with the speed and power of a compiled language, such as C.
- Bugzilla is maintained in Perl.
-
-Q
-
- QA
- "QA", "Q/A", and "Q.A." are short for "Quality Assurance". In
- most large software development organizations, there is a team
- devoted to ensuring the product meets minimum standards before
- shipping. This team will also generally want to track the
- progress of bugs over their life cycle, thus the need for the
- "QA Contact" field in a bug.
-
-R
-
- Relational DataBase Managment System (RDBMS)
- A relational database management system is a database system
- that stores information in tables that are related to each
- other.
-
-S
-
- SGML
- SGML stands for "Standard Generalized Markup Language". Created
- in the 1980's to provide an extensible means to maintain
- documentation based upon content instead of presentation, SGML
- has withstood the test of time as a robust, powerful language.
- XML is the "baby brother" of SGML; any valid XML document it,
- by definition, a valid SGML document. The document you are
- reading is written and maintained in SGML, and is also valid
- XML if you modify the Document Type Definition.
-
-T
-
- Target Milestone
- Target Milestones are Product goals. They are configurable on a
- per-Product basis. Most software development houses have a
- concept of "milestones" where the people funding a project
- expect certain functionality on certain dates. Bugzilla
- facilitates meeting these milestones by giving you the ability
- to declare by which milestone a bug will be fixed, or an
- enhancement will be implemented.
-
- Tool Command Language (TCL)
- TCL is an open source scripting language available for Windows,
- Macintosh, and Unix based systems. Bugzilla 1.0 was written in
- TCL but never released. The first release of Bugzilla was 2.0,
- which was when it was ported to perl.
-
-Z
-
- Zarro Boogs Found
- This is just a goofy way of saying that there were no bugs
- found matching your query. When asked to explain this message,
- Terry had the following to say:
-
-
-
- I've been asked to explain this ... way back when, when Netscape
- released version 4.0 of its browser, we had a release party.
- Naturally, there had been a big push to try and fix every known bug
- before the release. Naturally, that hadn't actually happened. (This is
- not unique to Netscape or to 4.0; the same thing has happened with
- every software project I've ever seen.) Anyway, at the release party,
- T-shirts were handed out that said something like "Netscape 4.0: Zarro
- Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh.
- So, when you query for a list of bugs, and it gets no results, you can
- think of this as a friendly reminder. Of *course* there are bugs
- matching your query, they just aren't in the bugsystem yet...
-
- --Terry Weissman
projects / thirdparty / bugzilla.git / commitdiff
