NAME="KEYWORD"
CONTENT="webtools"></HEAD
><BODY
-CLASS="BOOK"
+CLASS="book"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
><DIV
CLASS="BOOK"
><A
-NAME="INDEX"
+NAME="index"
></A
><DIV
CLASS="TITLEPAGE"
><H1
-CLASS="TITLE"
+CLASS="title"
><A
NAME="AEN2"
>The Bugzilla Guide</A
></H1
><H3
-CLASS="AUTHOR"
+CLASS="author"
><A
NAME="AEN27"
>Matthew P. Barnson</A
></H3
><DIV
-CLASS="AFFILIATION"
+CLASS="affiliation"
><DIV
-CLASS="ADDRESS"
+CLASS="address"
><P
-CLASS="ADDRESS"
+CLASS="address"
>barnboy@trilobyte.net</P
></DIV
></DIV
><SPAN
-CLASS="COLLAB"
+CLASS="collab"
><SPAN
-CLASS="COLLABNAME"
+CLASS="collabname"
>Zach Lipton</SPAN
><DIV
-CLASS="AFFILIATION"
+CLASS="affiliation"
><DIV
-CLASS="ADDRESS"
+CLASS="address"
><P
-CLASS="ADDRESS"
+CLASS="address"
>zach AT zachlipton DOT com</P
></DIV
></DIV
><BR></SPAN
><DIV
-CLASS="REVHISTORY"
+CLASS="revhistory"
><TABLE
WIDTH="100%"
BORDER="0"
></DIV
><DIV
><DIV
-CLASS="ABSTRACT"
+CLASS="abstract"
><A
NAME="AEN39"
></A
><P
></P
><P
-> This is the documentation for Bugzilla, the Mozilla
+> This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</P
><P
-> Bugzilla is an enterprise-class set of software utilities
+> Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
- While it is easy to use and quite flexible, it is very
+ While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
- professional on operating system upon which you install
+ professional for the operating system upon which you install
Bugzilla.
</P
><P
-> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
+> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
></DT
><DT
>1. <A
-HREF="#ABOUT"
+HREF="#about"
>About This Guide</A
></DT
><DD
><DL
><DT
>1.1. <A
-HREF="#ABOUTTHISGUIDE"
+HREF="#aboutthisguide"
>Purpose and Scope of this Guide</A
></DT
><DT
>1.2. <A
-HREF="#COPYRIGHT"
+HREF="#copyright"
>Copyright Information</A
></DT
><DT
>1.3. <A
-HREF="#DISCLAIMER"
+HREF="#disclaimer"
>Disclaimer</A
></DT
><DT
>1.4. <A
-HREF="#NEWVERSIONS"
+HREF="#newversions"
>New Versions</A
></DT
><DT
>1.5. <A
-HREF="#CREDITS"
+HREF="#credits"
>Credits</A
></DT
><DT
>1.6. <A
-HREF="#CONTRIBUTORS"
+HREF="#contributors"
>Contributors</A
></DT
><DT
>1.7. <A
-HREF="#FEEDBACK"
+HREF="#feedback"
>Feedback</A
></DT
><DT
>1.8. <A
-HREF="#TRANSLATIONS"
+HREF="#translations"
>Translations</A
></DT
><DT
>1.9. <A
-HREF="#CONVENTIONS"
+HREF="#conventions"
>Document Conventions</A
></DT
></DL
></DD
><DT
>2. <A
-HREF="#USING"
+HREF="#using"
>Using Bugzilla</A
></DT
><DD
><DL
><DT
>2.1. <A
-HREF="#WHATIS"
+HREF="#whatis"
>What is Bugzilla?</A
></DT
><DT
>2.2. <A
-HREF="#WHY"
+HREF="#why"
>Why Should We Use Bugzilla?</A
></DT
><DT
>2.3. <A
-HREF="#HOW"
+HREF="#how"
>How do I use Bugzilla?</A
></DT
><DD
><DL
><DT
>2.3.1. <A
-HREF="#MYACCOUNT"
+HREF="#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
-HREF="#QUERY"
+HREF="#query"
>The Bugzilla Query Page</A
></DT
><DT
>2.3.3. <A
-HREF="#BUGREPORTS"
+HREF="#bugreports"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>2.3.3.1. <A
-HREF="#BUG_WRITING"
+HREF="#bug-writing"
>Writing a Great Bug Report</A
></DT
><DT
>2.3.3.2. <A
-HREF="#BUG_MANAGE"
+HREF="#bug-manage"
>Managing your Bug Reports</A
></DT
></DL
></DD
><DT
>2.4. <A
-HREF="#INIT4ME"
+HREF="#init4me"
>Where can I find my user preferences?</A
></DT
><DD
><DL
><DT
>2.4.1. <A
-HREF="#ACCOUNTSETTINGS"
+HREF="#accountsettings"
>Account Settings</A
></DT
><DT
>2.4.2. <A
-HREF="#EMAILSETTINGS"
+HREF="#emailsettings"
>Email Settings</A
></DT
><DD
><DL
><DT
>2.4.2.1. <A
-HREF="#NOTIFICATION"
+HREF="#notification"
>Email Notification</A
></DT
><DT
>2.4.2.2. <A
-HREF="#NEWEMAILTECH"
+HREF="#newemailtech"
>New Email Technology</A
></DT
><DT
>2.4.2.3. <A
-HREF="#WATCHSETTINGS"
+HREF="#watchsettings"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>2.4.3. <A
-HREF="#FOOTERSETTINGS"
+HREF="#footersettings"
>Page Footer</A
></DT
><DT
>2.4.4. <A
-HREF="#PERMISSIONSETTINGS"
+HREF="#permissionsettings"
>Permissions</A
></DT
></DL
></DD
><DT
>2.5. <A
-HREF="#USINGBZ-CONC"
+HREF="#usingbz-conc"
>Using Bugzilla-Conclusion</A
></DT
></DL
></DD
><DT
>3. <A
-HREF="#INSTALLATION"
+HREF="#installation"
>Installation</A
></DT
><DD
><DL
><DT
>3.1. <A
-HREF="#ERRATA"
+HREF="#errata"
>ERRATA</A
></DT
><DT
>3.2. <A
-HREF="#STEPBYSTEP"
+HREF="#stepbystep"
>Step-by-step Install</A
></DT
><DD
></DT
><DT
>3.2.3. <A
-HREF="#INSTALL-MYSQL"
+HREF="#install-mysql"
>Installing MySQL Database</A
></DT
><DT
>3.2.4. <A
-HREF="#INSTALL-PERL"
+HREF="#install-perl"
>Perl (5.004 or greater)</A
></DT
><DT
>3.2.15. <A
HREF="#AEN768"
>Tweaking <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
></A
></DT
></DD
><DT
>3.3. <A
-HREF="#OSX"
+HREF="#osx"
>Mac OS X Installation Notes</A
></DT
><DT
>3.4. <A
-HREF="#BSDINSTALL"
+HREF="#bsdinstall"
>BSD Installation Notes</A
></DT
><DT
>3.5. <A
-HREF="#GENINSTALL"
+HREF="#geninstall"
>Installation General Notes</A
></DT
><DD
></DT
><DT
>3.5.3. <A
-HREF="#HTACCESS"
+HREF="#htaccess"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files and security</A
></DT
><DT
>3.5.4. <A
-HREF="#MOD_THROTTLE"
+HREF="#mod-throttle"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
-HREF="#CONTENT_TYPE"
+HREF="#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
-HREF="#UNIXHISTORY"
+HREF="#unixhistory"
>UNIX Installation Instructions History</A
></DT
></DL
></DD
><DT
>3.6. <A
-HREF="#WIN32"
+HREF="#win32"
>Win32 Installation Notes</A
></DT
><DD
><DL
><DT
>3.6.1. <A
-HREF="#WININSTALL"
+HREF="#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
-HREF="#ADDLWINTIPS"
+HREF="#addlwintips"
>Additional Windows Tips</A
></DT
><DT
>3.6.3. <A
-HREF="#BZLDAP"
+HREF="#bzldap"
>Bugzilla LDAP Integration</A
></DT
></DL
></DD
><DT
>4. <A
-HREF="#ADMINISTRATION"
+HREF="#administration"
>Administering Bugzilla</A
></DT
><DD
><DL
><DT
>4.1. <A
-HREF="#POSTINSTALL-CHECK"
+HREF="#postinstall-check"
>Post-Installation Checklist</A
></DT
><DT
>4.2. <A
-HREF="#USERADMIN"
+HREF="#useradmin"
>User Administration</A
></DT
><DD
><DL
><DT
>4.2.1. <A
-HREF="#DEFAULTUSER"
+HREF="#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
-HREF="#MANAGEUSERS"
+HREF="#manageusers"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>4.2.2.1. <A
-HREF="#LOGIN"
+HREF="#login"
>Logging In</A
></DT
><DT
>4.2.2.2. <A
-HREF="#CREATENEWUSERS"
+HREF="#createnewusers"
>Creating new users</A
></DT
><DT
>4.2.2.3. <A
-HREF="#DISABLEUSERS"
+HREF="#disableusers"
>Disabling Users</A
></DT
><DT
>4.2.2.4. <A
-HREF="#MODIFYUSERS"
+HREF="#modifyusers"
>Modifying Users</A
></DT
></DL
></DD
><DT
>4.3. <A
-HREF="#PROGRAMADMIN"
+HREF="#programadmin"
>Product, Component, Milestone, and Version
Administration</A
></DT
><DL
><DT
>4.3.1. <A
-HREF="#PRODUCTS"
+HREF="#products"
>Products</A
></DT
><DT
>4.3.2. <A
-HREF="#COMPONENTS"
+HREF="#components"
>Components</A
></DT
><DT
>4.3.3. <A
-HREF="#VERSIONS"
+HREF="#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
-HREF="#MILESTONES"
+HREF="#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
-HREF="#VOTING"
+HREF="#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
-HREF="#GROUPS"
+HREF="#groups"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
>4.4. <A
-HREF="#SECURITY"
+HREF="#security"
>Bugzilla Security</A
></DT
></DL
></DD
><DT
>5. <A
-HREF="#INTEGRATION"
+HREF="#integration"
>Integrating Bugzilla with Third-Party Tools</A
></DT
><DD
><DL
><DT
>5.1. <A
-HREF="#BONSAI"
+HREF="#bonsai"
>Bonsai</A
></DT
><DT
>5.2. <A
-HREF="#CVS"
+HREF="#cvs"
>CVS</A
></DT
><DT
>5.3. <A
-HREF="#SCM"
+HREF="#scm"
>Perforce SCM</A
></DT
><DT
>5.4. <A
-HREF="#TINDERBOX"
+HREF="#tinderbox"
>Tinderbox/Tinderbox2</A
></DT
></DL
></DD
><DT
>6. <A
-HREF="#FUTURE"
+HREF="#future"
>The Future of Bugzilla</A
></DT
><DT
>7. <A
-HREF="#VARIANTS"
+HREF="#variants"
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
>7.1. <A
-HREF="#RHBUGZILLA"
+HREF="#rhbugzilla"
>Red Hat Bugzilla</A
></DT
><DT
>7.2. <A
-HREF="#VARIANT_FENRIS"
+HREF="#variant-fenris"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
-HREF="#VARIANT_ISSUEZILLA"
+HREF="#variant-issuezilla"
>Issuezilla</A
></DT
><DT
>7.4. <A
-HREF="#VARIANT_SCARAB"
+HREF="#variant-scarab"
>Scarab</A
></DT
><DT
>7.5. <A
-HREF="#VARIANT_PERFORCE"
+HREF="#variant-perforce"
>Perforce SCM</A
></DT
><DT
>7.6. <A
-HREF="#VARIANT_SOURCEFORGE"
+HREF="#variant-sourceforge"
>SourceForge</A
></DT
></DL
></DD
><DT
>A. <A
-HREF="#FAQ"
+HREF="#faq"
>The Bugzilla FAQ</A
></DT
><DT
>B. <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Software Download Links</A
></DT
><DT
>C. <A
-HREF="#DATABASE"
+HREF="#database"
>The Bugzilla Database</A
></DT
><DD
><DL
><DT
>C.1. <A
-HREF="#DBSCHEMA"
+HREF="#dbschema"
>Database Schema Chart</A
></DT
><DT
>C.2. <A
-HREF="#DBDOC"
+HREF="#dbdoc"
>MySQL Bugzilla Database Introduction</A
></DT
><DD
><DL
><DT
>C.2.1. <A
-HREF="#AEN2331"
+HREF="#AEN2340"
>Bugzilla Database Basics</A
></DT
><DD
><DL
><DT
>C.2.1.1. <A
-HREF="#AEN2360"
+HREF="#AEN2369"
>Bugzilla Database Tables</A
></DT
></DL
></DD
><DT
>C.3. <A
-HREF="#GRANTTABLES"
+HREF="#granttables"
>MySQL Permissions & Grant Tables</A
></DT
></DL
></DD
><DT
>D. <A
-HREF="#PATCHES"
+HREF="#patches"
>Useful Patches and Utilities for Bugzilla</A
></DT
><DD
><DL
><DT
>D.1. <A
-HREF="#REWRITE"
+HREF="#rewrite"
>Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</A
></DT
><DT
>D.2. <A
-HREF="#SETPERL"
+HREF="#setperl"
>The setperl.csh Utility</A
></DT
><DT
>D.3. <A
-HREF="#CMDLINE"
+HREF="#cmdline"
>Command-line Bugzilla Queries</A
></DT
><DT
>D.4. <A
-HREF="#QUICKSEARCH"
+HREF="#quicksearch"
>The Quicksearch Utility</A
></DT
><DT
>D.5. <A
-HREF="#BZHACKING"
+HREF="#bzhacking"
>Hacking Bugzilla</A
></DT
><DD
><DL
><DT
>D.5.1. <A
-HREF="#AEN2495"
+HREF="#AEN2504"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
-HREF="#AEN2509"
+HREF="#AEN2518"
>Coding Style for Bugzilla</A
></DT
></DL
></DD
><DT
>E. <A
-HREF="#GFDL"
+HREF="#gfdl"
>GNU Free Documentation License</A
></DT
><DD
><DL
><DT
>0. <A
-HREF="#GFDL_0"
+HREF="#gfdl-0"
>PREAMBLE</A
></DT
><DT
>1. <A
-HREF="#GFDL_1"
+HREF="#gfdl-1"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
-HREF="#GFDL_2"
+HREF="#gfdl-2"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
-HREF="#GFDL_3"
+HREF="#gfdl-3"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
-HREF="#GFDL_4"
+HREF="#gfdl-4"
>MODIFICATIONS</A
></DT
><DT
>5. <A
-HREF="#GFDL_5"
+HREF="#gfdl-5"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
-HREF="#GFDL_6"
+HREF="#gfdl-6"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
-HREF="#GFDL_7"
+HREF="#gfdl-7"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
-HREF="#GFDL_8"
+HREF="#gfdl-8"
>TRANSLATION</A
></DT
><DT
>9. <A
-HREF="#GFDL_9"
+HREF="#gfdl-9"
>TERMINATION</A
></DT
><DT
>10. <A
-HREF="#GFDL_10"
+HREF="#gfdl-10"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
-HREF="#GFDL_HOWTO"
+HREF="#gfdl-howto"
>How to use this License for your documents</A
></DT
></DL
></DD
><DT
><A
-HREF="#GLOSSARY"
+HREF="#glossary"
>Glossary</A
></DT
></DL
></DT
><DT
>3-3. <A
-HREF="#AEN1038"
+HREF="#AEN1048"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
-HREF="#AEN1224"
+HREF="#AEN1233"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
-HREF="#AEN1461"
+HREF="#AEN1470"
>Creating some Components</A
></DT
><DT
>4-2. <A
-HREF="#AEN1490"
+HREF="#AEN1499"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
-HREF="#AEN1494"
+HREF="#AEN1503"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
-HREF="#AEN1522"
+HREF="#AEN1531"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
-HREF="#AEN1558"
+HREF="#AEN1567"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
-HREF="#AEN1575"
+HREF="#AEN1584"
>Creating a New Group</A
></DT
><DT
>4-7. <A
-HREF="#AEN1592"
+HREF="#AEN1601"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
-HREF="#AEN2439"
+HREF="#AEN2448"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
-HREF="#AEN2736"
+HREF="#AEN2769"
>A Sample Product</A
></DT
></DL
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="ABOUT"
+NAME="about"
>Chapter 1. About This Guide</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ABOUTTHISGUIDE"
+NAME="aboutthisguide"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
-> This document was started on September 17, 2000 by Matthew P.
+> This document was started on September 17, 2000 by Matthew P.
Barnson after a great deal of procrastination updating the
Bugzilla FAQ, which I left untouched for nearly half a year.
After numerous complete rewrites and reformatting, it is the
document you see today.
</P
><P
-> Bugzilla is simply the best piece of bug-tracking software the
+> 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
+> This release of the Bugzilla Guide is the
<EM
>2.14</EM
> release. It is so named that it
developers, and those who enjoy a lot of pain.
</P
><P
-> Newer revisions of the Bugzilla Guide follow the numbering
+> Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<A
HREF="http://www.mozilla.org/projects/bugzilla"
Got it? Good.
</P
><P
-> I wrote this in response to the enormous demand for decent
+> I wrote this in response to the enormous demand for decent
Bugzilla documentation. I have incorporated instructions from
the Bugzilla README, Frequently Asked Questions, Database Schema
Document, and various mailing lists to create it. Chances are,
there are glaring errors in this documentation; please contact
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="COPYRIGHT"
+NAME="copyright"
>1.2. Copyright Information</A
></H1
><A
WIDTH="80%"
VALIGN="TOP"
><P
-> Permission is granted to copy, distribute and/or modify this
+> 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
ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
-CLASS="ATTRIBUTION"
+CLASS="attribution"
>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
></TD
><TD
></TR
></TABLE
><P
-> If you have any questions regarding this document, its
+> If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
please contact Matthew P. Barnson.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DISCLAIMER"
+NAME="disclaimer"
>1.3. Disclaimer</A
></H1
><P
-> No liability for the contents of this document can be accepted.
+> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
and inaccuracies that may damage your system. Use of this
war. Proceed with caution.
</P
><P
-> All copyrights are held by their respective owners, unless
+> 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
+> Naming of particular products or brands should not be seen as
endorsements, with the exception of the term "GNU/Linux". I
wholeheartedly endorse the use of GNU/Linux in every situation
where it is appropriate. It is an extremely versatile, stable,
environment for Bugzilla.
</P
><P
-> You are strongly recommended to make a backup of your system
+> You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
Heaven knows it's saved my bacon time after time; if you
implement any suggestion in this Guide, implement this one!
</P
><P
-> Although the Bugzilla development team has taken great care to
+> 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
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NEWVERSIONS"
+NAME="newversions"
>1.4. New Versions</A
></H1
><P
-> This is the 2.14 version of The Bugzilla Guide. If you are
+> This is the 2.14 version of The Bugzilla Guide. 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
-> This document can be found in the following places:
+> This document can be found in the following places:
</P
><P
-> <P
></P
><UL
><LI
><P
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>TriloBYTE</A
></LI
><LI
><P
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
>Mozilla.org</A
></LI
><LI
><P
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>The Linux
>
</P
><P
-> The latest version of this document can be checked out via CVS.
+> The latest version of this document can be checked out via CVS.
Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CREDITS"
+NAME="credits"
>1.5. Credits</A
></H1
><P
-> The people listed below have made enormous contributions to the
+> The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</P
><P
-> <A
HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
README upon which the UNIX installation documentation is largely based.
</P
><P
-> <A
HREF="mailto://tara@tequilarista.org"
TARGET="_top"
>Tara
strong after Terry left Mozilla.org
</P
><P
-> <A
HREF="mailto://dkl@redhat.com"
TARGET="_top"
>Dave Lawrence</A
Hat Bugzilla" appendix
</P
><P
-> <A
HREF="mailto://endico@mozilla.org"
TARGET="_top"
>Dawn Endico</A
questions and arguments on irc.mozilla.org in #mozwebtools
</P
><P
-> Last but not least, all the members of the <A
+>
Last but not least, all the members of the <A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
TARGET="_top"
> netscape.public.mozilla.webtools</A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONTRIBUTORS"
+NAME="contributors"
>1.6. Contributors</A
></H1
><P
-> Thanks go to these people for significant contributions to this
+> Thanks go to these people for significant contributions to this
documentation (in no particular order):
</P
><P
-> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="FEEDBACK"
+NAME="feedback"
>1.7. Feedback</A
></H1
><P
-> I welcome feedback on this document. Without your submissions
+> I welcome feedback on this document. Without your submissions
and input, this Guide cannot continue to exist. Please mail
additions, comments, criticisms, etc. to
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>></TT
>. Please send flames to
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:devnull@localhost"
>devnull@localhost</A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="TRANSLATIONS"
+NAME="translations"
>1.8. Translations</A
></H1
><P
-> The Bugzilla Guide needs translators! Please volunteer your
+> The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will
translate this Guide, please notify the members of the
mozilla-webtools mailing list at
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONVENTIONS"
+NAME="conventions"
>1.9. Document Conventions</A
></H1
><P
-> This document uses the following conventions
+> This document uses the following conventions
</P
><DIV
-CLASS="INFORMALTABLE"
+CLASS="informaltable"
><A
NAME="AEN129"
></A
><TR
><TH
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Descriptions</TH
><TH
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Appearance</TH
></TR
></THEAD
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Warnings</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="CAUTION"
+CLASS="caution"
><P
></P
><TABLE
-CLASS="CAUTION"
+CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Hint</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Notes</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Information requiring special attention</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>File Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>file.extension</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Directory Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>directory</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Commands to be typed</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><B
-CLASS="COMMAND"
+CLASS="command"
>command</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Applications Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><SPAN
-CLASS="APPLICATION"
+CLASS="application"
>application</SPAN
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of users command under bash shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>bash$</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of root users command under bash shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>bash#</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of user command under tcsh shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>tcsh$</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Environment Variables</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="ENVAR"
+CLASS="envar"
>VARIABLE</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Emphasized word</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><EM
>word</EM
></TD
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
><TT
-CLASS="SGMLTAG"
+CLASS="sgmltag"
><para></TT
>Beginning and end of paragraph<TT
-CLASS="SGMLTAG"
+CLASS="sgmltag"
></para></TT
></PRE
></FONT
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="USING"
+NAME="using"
>Chapter 2. Using Bugzilla</A
></H1
><TABLE
></TR
></TABLE
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WHATIS"
+NAME="whatis"
>2.1. What is Bugzilla?</A
></H1
><P
-> Bugzilla is one example of a class of programs called "Defect
+> Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
system against which all others are measured.
</P
><P
-> Bugzilla has matured immensely, and now boasts many advanced features. These include:
+> Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P
></P
><UL
><LI
><P
-> integrated, product-based granular security schema
+> integrated, product-based granular security schema
</P
></LI
><LI
><P
-> inter-bug dependencies and dependency graphing
+> inter-bug dependencies and dependency graphing
</P
></LI
><LI
><P
-> advanced reporting capabilities
+> advanced reporting capabilities
</P
></LI
><LI
><P
-> a robust, stable RDBMS back-end
+> a robust, stable RDBMS back-end
</P
></LI
><LI
><P
-> extensive configurability
+> extensive configurability
</P
></LI
><LI
><P
-> a very well-understood and well-thought-out natural bug resolution protocol
+> a very well-understood and well-thought-out natural bug resolution protocol
</P
></LI
><LI
><P
-> email, XML, console, and HTTP APIs
+> email, XML, console, and HTTP APIs
</P
></LI
><LI
><P
-> available integration with automated software
+> available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
></LI
><LI
><P
-> too many more features to list
+> too many more features to list
</P
></LI
></UL
>
</P
><P
-> Despite its current robustness and popularity, Bugzilla faces
+> Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but
some nonstandard libraries.
</P
><P
-> Some recent headway has been made on the query front, however.
+> Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
available as "queryhelp.cgi".
</P
><P
-> Despite these small problems, Bugzilla is very hard to beat. It
+> Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
> active development to address
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WHY"
+NAME="why"
>2.2. Why Should We Use Bugzilla?</A
></H1
><TABLE
></TR
></TABLE
><P
-> For many years, defect-tracking software has remained
+> 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
dropped or ignored.
</P
><P
-> These days, many companies are finding that integrated
+> 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
system for accounting for unusual system or software issues.
</P
><P
-> But why should <EM
+> But why should <EM
>you</EM
> use Bugzilla?
</P
><P
-> Bugzilla is very adaptable to various situations. Known uses
+> 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
replication problems
</P
><P
-> Bugzilla can dramatically increase the productivity and
+> 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
led to critical decisions.
</P
><P
-> Ultimately, Bugzilla puts the power in your hands to improve
+> 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="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="HOW"
+NAME="how"
>2.3. How do I use Bugzilla?</A
></H1
><TABLE
></TR
></TABLE
><P
-> Bugzilla is a large, complex system. Describing how to use it
+> Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
software.
</P
><P
-> Throughout this portion of the Guide, we will refer to user
+> Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
-> landfill.tequilarista.org</A
+> landfill.tequilarista.org</A
>.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some people have run into difficulties completing this
+> Some people have run into difficulties completing this
tutorial. If you run into problems, please check the
updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/"
mentioned here.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MYACCOUNT"
+NAME="myaccount"
>2.3.1. Create a Bugzilla Account</A
></H2
><P
-> First things first! If you want to use Bugzilla, first you
+> First things first! 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 the end-user
TYPE="1"
><LI
><P
-> Click the "Open a new Bugzilla account" link.
+> Click the "Open a new Bugzilla account" link.
</P
></LI
><LI
><P
-> Enter your "E-mail address" and "Real Name" (or whatever
+> Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
</P
></LI
><LI
><P
-> Within moments, you should receive an email to the address
+> 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
></LI
><LI
><P
-> Click the <SPAN
+> Click the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
> link in the yellow area at
>"Login"</SPAN
>.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you ever forget your password, you can come back to
+> If you ever forget your password, you can come back to
this page, enter your <SPAN
CLASS="QUOTE"
>"E-mail address"</SPAN
></DIV
>
<DIV
-CLASS="CAUTION"
+CLASS="caution"
><P
></P
><TABLE
-CLASS="CAUTION"
-WIDTH="90%"
+CLASS="caution"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Many modern browsers include an
+> Many modern browsers include an
<SPAN
CLASS="QUOTE"
>"Auto-Complete"</SPAN
></LI
></OL
><P
-> Congratulations! If you followed these directions, you now
+> Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="QUERY"
+NAME="query"
>2.3.2. The Bugzilla Query Page</A
></H2
><P
-> The Bugzilla Query Page is the heart and soul of the Bugzilla
+> The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
</P
><P
-> There are efforts underway to simplify query usage. If you
+> There are efforts underway to simplify query usage. If you
have a local installation of Bugzilla 2.12 or higher, you
should have <TT
-CLASS="FILENAME"
+CLASS="filename"
>quicksearch.html</TT
> available to
use and simplify your searches. There is also a helper for
the query interface, called
<TT
-CLASS="FILENAME"
+CLASS="filename"
>queryhelp.cgi</TT
>. Landfill tends to run the
latest code, so these two utilities should be available there
for your perusal.
</P
><P
-> At this point, please visit the main Bugzilla site,
+> At this point, let's visit the query page.
<A
-HREF="http://bugzilla.mozilla.org/query.cgi"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
TARGET="_top"
-> bugzilla.mozilla.org</A
->, to see a more fleshed-out query page.
+> landfill.tequilarista.org/bugzilla-tip/query.cgi</A
+>
</P
><P
-> The first thing you need to notice about the Bugzilla Query
+> The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
> underlined. Select it.
</P
><P
-> Notice the page that popped up? Every underlined word you see
+> Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
button in your browser.
</P
><P
-> I'm sure that after checking out the online help, you are now
+> I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
TYPE="1"
><LI
><P
-> Ensure you are back on the <SPAN
+> Ensure you are back on the <SPAN
CLASS="QUOTE"
>"Bugzilla Query
Page"</SPAN
figured out.
</P
><P
-> Basically, selecting <EM
+> Basically, selecting <EM
>anything</EM
> on the
query page narrows your search down. Leaving stuff
></LI
><LI
><P
-> You see the box immediately below the top six boxes that
+> You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
put my email address in there, and see what happens.
</P
><P
-> Type "barnboy@trilobyte.net" in the top Email text box.
+> Type "barnboy@trilobyte.net" in the top Email text box.
</P
></LI
><LI
><P
-> Let's narrow the search some more. Scroll down until you
+> Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
></LI
><LI
><P
-> Did you notice that some of the boxes to the right changed
+> Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN307"
></A
>Example 2-1. Some Famous Software Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN309"
></A
><P
></P
><P
-> Do you remember the hype in 1995 when Microsoft
+> Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
ME(Millenium Edition)(r).
</P
><P
-> Software "Versions" help a manufacturer
+> Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
version than 1.1.1.
</P
><P
-> In general, a "Version" in Bugzilla should refer to
+> In general, a "Version" in Bugzilla should refer to
<EM
>released</EM
> products, not products
>
</P
><P
-> A "Component" is a piece of a Product.
+> A "Component" is a piece of a Product.
It may be a standalone program, or some other logical
division of a Product or Program.
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN317"
></A
>Example 2-2. Mozilla's Bugzilla Components</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN319"
></A
><P
></P
><P
-> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
+> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<P
></P
><TABLE
>,
Administration of a bugzilla installation, including
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editcomponents.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editgroups.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editkeywords.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editparams.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editproducts.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editusers.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editversions.cgi,</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>sanitycheck.cgi</TT
>.
</TD
>,
Creating, changing, and viewing bugs.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>enter_bug.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>post_bug.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>show_bug.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>process_bug.cgi</TT
>.
</TD
>,
The bugzilla documentation, including anything in the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>docs/</TT
> directory and The Bugzilla Guide
(This document :)
>,
Anything to do with email sent by Bugzilla.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
>
</TD
>,
The installation process of Bugzilla. This includes
<TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
> and whatever else it evolves into.
</TD
>,
Anything to do with searching for bugs and viewing the buglists.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>query.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>buglist.cgi</TT
>
</TD
>,
Getting reports from Bugzilla.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>reports.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>duplicates.cgi</TT
>
</TD
>,
Anything about managing a user account from the user's perspective.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>userprefs.cgi</TT
>, saved queries, creating accounts,
changing passwords, logging in, etc.
>
</P
><P
-> A "Milestone", or "Target Milestone" is a often a planned
+> A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
of reach by the time the important day arrives.
</P
><P
-> The Bugzilla Project has set up Milestones for future
+> The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
></LI
><LI
><P
-> OK, now let's select the "Bugzilla" component from its scrollbox.
+> OK, now let's select the "Bugzilla" component from its scrollbox.
</P
></LI
><LI
><P
-> Skip down the page a bit -- do you see the "submit query" button?
+> Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run
this query!
</P
></LI
><LI
><P
-> Congratulations! You've completed your first Query, and
+> Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
></LI
></OL
><P
-> I encourage you to click the bug numbers in the left-hand
+> I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
this is a tremendous timesaver.
</P
><P
-> A couple more interesting things about the Bug List page:
+> A couple more interesting things about the Bug List page:
<P
></P
><TABLE
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are many more options to the Bugzilla Query Page and
+> There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <A
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUGREPORTS"
+NAME="bugreports"
>2.3.3. Creating and Managing Bug Reports</A
></H2
><TABLE
></TR
></TABLE
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUG_WRITING"
+NAME="bug-writing"
>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
-> Before we plunge into writing your first bug report, I
+> Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
>. 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
-> While you are at it, why not learn how to find previously
+> While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
>.
</P
><P
-> I realize this was a lot to read. However, understanding
+> I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
</P
TYPE="1"
><LI
><P
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
></LI
><LI
><P
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
> Enter a new bug report</A
></LI
><LI
><P
-> Select a product.
+> Select a product.
</P
></LI
><LI
><P
-> Now you should be at the "Enter Bug" form. The
+> Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
></LI
><LI
><P
-> Select a Component in the scrollbox.
+> Select a Component in the scrollbox.
</P
></LI
><LI
><P
-> Bugzilla should have made reasonable guesses, based upon
+> Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
></LI
><LI
><P
-> Fill in the "Assigned To" box with the email address you
+> Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
></LI
><LI
><P
-> Leave the "CC" text box blank. Fill in the "URL" box
+> Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</P
></LI
><LI
><P
-> Enter "The Bugzilla Guide" in the Summary text box, and
+> Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</P
></LI
></OL
><P
-> Voila! Select "Commit" and send in your bug report! Next
+> Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUG_MANAGE"
+NAME="bug-manage"
>2.3.3.2. Managing your Bug Reports</A
></H3
><P
-> OK, you should have a link to the bug you just created near
+> OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
TYPE="1"
><LI
><P
-> Scroll down a bit on the subsequent page, until you see
+> Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
></LI
><LI
><P
-> Hey! It said it couldn't take the change in a big red
+> Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
></LI
></OL
><P
-> You have now learned the basics of Bugzilla navigation,
+> You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</P
><P
-> But I'll give a few last hints!
+> But I'll give a few last hints!
</P
><P
-HREF="http://bugzilla.mozilla.org/help.html"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html"
TARGET="_top"
>CLUE</A
> on the Query page that will teach you more how to use the form.
</P
><P
->
If you click the hyperlink on the <A
-HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
+>
If you click the hyperlink on the <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi"
TARGET="_top"
>Component</A
> box of the Query page, you will be presented a form that will describe what all the components are.
</P
><P
-> Possibly the most powerful feature of the Query page is the
+> Possibly the most powerful feature of the Query page is the
<A
-HREF="http://bugzilla.mozilla.org/booleanchart.html"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
TARGET="_top"
>Boolean Chart</A
> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P
><P
->
Finally, you can build some nifty <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
+>
Finally, you can build some nifty <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi"
TARGET="_top"
>Reports</A
> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INIT4ME"
+NAME="init4me"
>2.4. Where can I find my user preferences?</A
></H1
><TABLE
></TR
></TABLE
><P
-> Customized User Preferences offer tremendous versatility to your
+> Customized User Preferences offer tremendous versatility to your
individual Bugzilla experience. Let's plunge into what you can
do! The first step is to click the "Edit prefs" link at the
footer of each page once you have logged in to <A
>.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ACCOUNTSETTINGS"
+NAME="accountsettings"
>2.4.1. Account Settings</A
></H2
><P
-> On this page, you can change your basic Account Settings,
+> On this page, you can change your basic Account Settings,
including your password and full name. For security reasons,
in order to change anything on this page you must type your
<EM
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="EMAILSETTINGS"
+NAME="emailsettings"
>2.4.2. Email Settings</A
></H2
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NOTIFICATION"
+NAME="notification"
>2.4.2.1. Email Notification</A
></H3
><P
-> Here you can reduce or increase the amount of email sent you
+> Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as
<SPAN
CLASS="QUOTE"
onto a quality assurance platform for inspection. Other
people set up email gateways to
<A
-HREF="#BONSAI"
+HREF="#bonsai"
>Bonsai, the Mozilla automated CVS management system</A
> or <A
-HREF="#TINDERBOX"
+HREF="#tinderbox"
>Tinderbox, the Mozilla automated build management system</A
>, and
restrict which types of Bugzilla information are fed to
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NEWEMAILTECH"
+NAME="newemailtech"
>2.4.2.2. New Email Technology</A
></H3
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This option may not be available in all Bugzilla
+> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
></TABLE
></DIV
><P
-> Disregard the warnings about "experimental and bleeding
+> Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and
well-tested now.
</P
><P
-> I recommend you enable the option, "Click here to sign up
+> I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WATCHSETTINGS"
+NAME="watchsettings"
>2.4.2.3. "Watching" Users</A
></H3
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This option may not be available in all Bugzilla
+> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
></TABLE
></DIV
><P
-> By entering user email names into the "Users to watch" text
+> By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="FOOTERSETTINGS"
+NAME="footersettings"
>2.4.3. Page Footer</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> By default, this page is quite barren. However, go explore
+> By default, this page is quite barren. However, go explore
the Query Page some more; you will find that you can store
numerous queries on the server, so if you regularly run a
particular query it is just a drop-down menu away. On this
></TABLE
></DIV
><P
-> If you have many stored queries on the server, here you will
+> If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful
is an excellent way to impress your boss...
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PERMISSIONSETTINGS"
+NAME="permissionsettings"
>2.4.4. Permissions</A
></H2
><P
-> This is a purely informative page which outlines your current
+> This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer.
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="USINGBZ-CONC"
+NAME="usingbz-conc"
>2.5. Using Bugzilla-Conclusion</A
></H1
><P
-> Thank you for reading through this portion of the Bugzilla
+> Thank you for reading through this portion of the Bugzilla
Guide. I anticipate it may not yet meet the needs of all
readers. If you have additional comments or corrections to
make, please submit your contributions to the <A
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="INSTALLATION"
+NAME="installation"
>Chapter 3. Installation</A
></H1
><P
-> These installation instructions are presented assuming you are
+> These installation instructions are presented assuming you are
installing on a UNIX or completely POSIX-compliant system. If
you are installing on Microsoft Windows or another oddball
operating system, please consult the appropriate sections in
this installation guide for notes on how to be successful.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ERRATA"
+NAME="errata"
>3.1. ERRATA</A
></H1
><P
><TBODY
><TR
><TD
-> If you are installing Bugzilla on S.u.S.e. Linux, or some
+> If you are installing Bugzilla on S.u.S.e. 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: <SPAN
-CLASS="ERRORNAME"
+CLASS="errorname"
>cannot chdir(/var/spool/mqueue):
Permission denied</SPAN
> This is because your
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/var/spool/mqueue</TT
> directory has a mode of
<SPAN
CLASS="QUOTE"
>"drwx------"</SPAN
>. Type <B
-CLASS="COMMAND"
+CLASS="command"
>chmod 755
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/var/spool/mqueue</TT
></B
> as root to
></TR
><TR
><TD
-> Bugzilla may be installed on Macintosh OS X (10), which is a
+> Bugzilla may be installed on Macintosh OS X (10), which is a
unix-based (BSD) operating system. Everything required for
Bugzilla on OS X will install cleanly, but the optional GD
perl module which is used for bug charting requires some
></TR
><TR
><TD
-> Release Notes for Bugzilla 2.14 are available at
+> Release Notes for Bugzilla 2.14 are available at
<TT
-CLASS="FILENAME"
+CLASS="filename"
>docs/rel_notes.txt</TT
> in your Bugzilla
source distribution.
></TR
><TR
><TD
-> The preferred documentation for Bugzilla is available in
+> The preferred documentation for Bugzilla is available in
docs/, with a variety of document types available. Please
refer to these documents when installing, configuring, and
maintaining your Bugzilla installation.
><P
></P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla is not a package where you can just plop it in a directory,
+> Bugzilla is not a package where you can just plop it in a directory,
twiddle a few things, and you're off. Installing Bugzilla assumes you
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
></TABLE
></DIV
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla has not undergone a complete security review. Security holes
+> Bugzilla has not undergone a complete security review. Security holes
may exist in the code. 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.
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="STEPBYSTEP"
+NAME="stepbystep"
>3.2. Step-by-step Install</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN509"
>3.2.1. Introduction</A
></H2
><P
-> Installation of bugzilla is pretty straightforward, particularly if your
+> Installation of bugzilla is pretty straightforward, particularly if your
machine already has MySQL and the MySQL-related perl packages installed.
If those aren't installed yet, then that's the first order of business. The
other necessary ingredient is a web server set up to run cgi scripts.
While using Apache for your webserver is not required, it is recommended.
</P
><P
-> Bugzilla has been successfully installed under Solaris, Linux,
+> Bugzilla has been successfully installed under Solaris, Linux,
and Win32. The peculiarities of installing on Win32 (Microsoft
Windows) are not included in this section of the Guide; please
check out the <A
-HREF="#WIN32"
+HREF="#win32"
>Win32 Installation Notes</A
> for further advice
on getting Bugzilla to work on Microsoft Windows.
</P
><P
-> The Bugzilla Guide is contained in the "docs/" folder in your
+> The Bugzilla Guide is contained in the "docs/" folder in your
Bugzilla distribution. It is available in plain text
(docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN515"
>3.2.2. Installing the Prerequisites</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
most recent version of Perl and MySQL (both the executables
and development libraries) on your system, check out
Bundle::Bugzilla in <A
-HREF="#BUNDLEBUGZILLA"
+HREF="#bundlebugzilla"
>Using Bundle::Bugzilla instead of manually installing Perl modules</A
></P
></TD
></TABLE
></DIV
><P
-> The software packages necessary for the proper running of bugzilla are:
+> The software packages necessary for the proper running of bugzilla are:
<P
></P
><OL
TYPE="1"
><LI
><P
-> MySQL database server and the mysql client (3.22.5 or greater)
+> MySQL database server and the mysql client (3.22.5 or greater)
</P
></LI
><LI
><P
-> Perl (5.004 or greater, 5.6.1 is recommended if you wish
+> Perl (5.004 or greater, 5.6.1 is recommended if you wish
to use Bundle::Bugzilla)
</P
></LI
><LI
><P
-> DBI Perl module
+> DBI Perl module
</P
></LI
><LI
><P
-> Data::Dumper Perl module
+> Data::Dumper Perl module
</P
></LI
><LI
><P
-> Bundle::Mysql Perl module collection
+> Bundle::Mysql Perl module collection
</P
></LI
><LI
><P
-> TimeDate Perl module collection
+> TimeDate Perl module collection
</P
></LI
><LI
><P
-> GD perl module (1.8.3) (optional, for bug charting)
+> GD perl module (1.8.3) (optional, for bug charting)
</P
></LI
><LI
><P
-> Chart::Base Perl module (0.99c) (optional, for bug charting)
+> Chart::Base Perl module (0.99c) (optional, for bug charting)
</P
></LI
><LI
><P
-> DB_File Perl module (optional, for bug charting)
+> DB_File Perl module (optional, for bug charting)
</P
></LI
><LI
><P
-> The web server of your choice. Apache is recommended.
+> The web server of your choice. Apache is recommended.
</P
></LI
><LI
><P
-> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</P
></LI
></OL
>
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It is a good idea, while installing Bugzilla, to ensure it
+> It is a good idea, while installing Bugzilla, to ensure it
is not <EM
>accessible</EM
> by other machines
></DIV
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
every required and optional library for Bugzilla. The
easiest way to install them is by using the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>urpmi</TT
> utility. If you follow these
commands, you should have everything you need for
Bugzilla, and <TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
> should
not complain about any missing libraries. You may already
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-mysql</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-chart</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-gd</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-MailTools</B
> (for Bugzilla email
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
apache-modules</B
></TD
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INSTALL-MYSQL"
+NAME="install-mysql"
>3.2.3. Installing MySQL Database</A
></H2
><P
->
Visit MySQL homepage at <A
+>
Visit MySQL homepage at <A
HREF="http://www.mysql.com"
TARGET="_top"
>www.mysql.com</A
> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT
-CLASS="FILENAME"
+CLASS="filename"
>/var</TT
> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
-CLASS="FILENAME"
+CLASS="filename"
>configure</TT
>.
</P
><P
-> If you install from source or non-package (RPM, deb, etc.)
+> If you install from source or non-package (RPM, deb, etc.)
binaries you need to add
<I
-CLASS="FIRSTTERM"
+CLASS="firstterm"
>mysqld</I
> 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.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><P
>You should have your init script start
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>mysqld</I
> with the ability to accept
large packets. By default, <TT
-CLASS="FILENAME"
+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"
+CLASS="option"
>-O
max_allowed_packet=1M</TT
> to the command that starts
<TT
-CLASS="FILENAME"
+CLASS="filename"
>mysqld</TT
> (or
<TT
-CLASS="FILENAME"
+CLASS="filename"
>safe_mysqld</TT
>), then you will be able
to have attachments up to about 1 megabyte.</P
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you plan on running Bugzilla and MySQL on the same
+> If you plan on running Bugzilla and MySQL on the same
machine, consider using the <TT
-CLASS="OPTION"
+CLASS="option"
>--skip-networking</TT
>
option in the init script. This enhances security by
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INSTALL-PERL"
+NAME="install-perl"
>3.2.4. Perl (5.004 or greater)</A
></H2
><P
-> Any machine that doesn't have perl on it is a sad machine
+> Any machine that doesn't have perl on it is a sad machine
indeed. Perl for *nix systems can be gotten in source form
from http://www.perl.com. Although Bugzilla runs with most
post-5.004 versions of Perl, it's a good idea to be up to the
this writing, that is perl version 5.6.1.
</P
><P
-> Perl is now a far cry from the the single compiler/interpreter
+> Perl is now a far cry from the the single compiler/interpreter
binary it once was. It includes a great many required modules
and quite a few other support files. If you're not up to or
not inclined to build perl from source, you'll want to install
isn't up to snuff.
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
></TABLE
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><A
-NAME="BUNDLEBUGZILLA"
+NAME="bundlebugzilla"
></A
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You can skip the following Perl module installation steps by
+> You can skip the following Perl module installation steps by
installing <SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>Bundle::Bugzilla</SPAN
> from
<A
-HREF="#GLOSS_CPAN"
+HREF="#gloss-cpan"
><I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>CPAN</I
></A
>, which
version of Perl (at this writing, version 5.6.1)
</P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>perl -MCPAN
-e 'install "Bundle::Bugzilla"'</B
>
>
</P
><P
-> Bundle::Bugzilla doesn't include GD, Chart::Base, or
+> 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.
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN602"
>3.2.5. DBI Perl Module</A
></H2
><P
-> The DBI module is a generic Perl module used by other database related
+> The DBI module is a generic Perl module used by other database related
Perl modules. For our purposes it's required by 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
><P
-> Like almost all Perl modules DBI can be found on the Comprehensive Perl
+> Like almost all Perl modules DBI can be found on the Comprehensive Perl
Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
real tendency to bog down, so please use mirrors. The current location
at the time of this writing can be found in <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Appendix B</A
>.
</P
><P
-> Quality, general Perl module installation instructions can be found on
+> 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.
</P
><P
-> To use the CPAN shell to install DBI:
+> To use the CPAN shell to install DBI:
<DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN609"
></A
><P
></P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl -MCPAN -e 'install "DBI"'</B
>
</TT
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>
To do it the hard way:
<DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN616"
></A
><P
></P
><P
-> Untar the module tarball -- it should create its own directory
+> Untar the module tarball -- it should create its own directory
</P
><P
-> CD to the directory just created, and enter the following commands:
+> CD to the directory just created, and enter the following commands:
<P
></P
><OL
TYPE="1"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.PL</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make test</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make install</B
>
</TT
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN640"
>3.2.6. Data::Dumper Perl Module</A
></H2
><P
-> The Data::Dumper module provides data structure persistence for Perl
+> 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
><P
-> Data::Dumper is used by the MySQL-related Perl modules. It
+> Data::Dumper is used by the MySQL-related Perl modules. It
can be found on CPAN (see <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Appendix B</A
>) and
can be
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN645"
>3.2.7. MySQL related Perl Module Collection</A
></H2
><P
-> The Perl/MySQL interface requires a few mutually-dependent perl
+> The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should
be untarred.
</P
><P
-> The MySQL modules are all built using one make file which is generated
+> The MySQL modules are all built using one make file which is generated
by running:
<TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.pl</B
>
</P
><P
-> The MakeMaker process will ask you a few questions about the desired
+> The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
</P
><P
-> When asked if your desired target is the MySQL or mSQL packages,
+> When asked if your desired target is the MySQL or mSQL packages,
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' and
+> A host of 'localhost' should be fine and a testing user of 'test' and
a null password should find itself with sufficient access to run tests
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN654"
>3.2.8. TimeDate Perl Module Collection</A
></H2
><P
-> Many of the more common date/time/calendar related Perl
+> 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 (see link: <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Appendix B</A
>). The
component module we're most interested in is the Date::Format
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN658"
>3.2.9. GD Perl Module (1.8.3)</A
></H2
><P
-> The GD library was written by Thomas Boutell a long while
+> 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
install it if you want any of the graphing to work.
</P
><P
-> Actually bugzilla uses the Graph module which relies on GD
+> Actually bugzilla uses the Graph module which relies on GD
itself. Isn't that always the way with object-oriented
programming? At any rate, you can find the GD library on CPAN
in <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Appendix B</A
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The Perl GD library requires some other libraries that may
+> The Perl GD library requires some other libraries that may
or may not be installed on your system, including
<TT
-CLASS="CLASSNAME"
+CLASS="classname"
>libpng</TT
> and
<TT
-CLASS="CLASSNAME"
+CLASS="classname"
>libgd</TT
>. The full requirements are
listed in the Perl GD library README. Just realize that if
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN667"
>3.2.10. Chart::Base Perl Module (0.99c)</A
></H2
><P
-> The Chart module provides bugzilla with on-the-fly charting
+> 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 where it is found as the
Chart-x.x... tarball, linked in <A
-HREF="#DOWNLOADLINKS"
+HREF="#downloadlinks"
>Appendix B</A
>. Note that
as with the GD perl module, only the version listed above, or
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN671"
>3.2.11. DB_File Perl Module</A
></H2
><P
-> DB_File is a module which allows Perl programs to make use
+> DB_File is a module which allows Perl programs to make use
of the facilities provided by Berkeley DB version 1.x. This
module is required by collectstats.pl which is used for bug
charting. If you plan to make use of bug charting, you must
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN674"
>3.2.12. HTTP Server</A
></H2
><P
-> You have a freedom of choice here - Apache, Netscape or any
+> You have a freedom of choice here - Apache, Netscape or any
other server on UNIX would do. You can easily run the web
server on a different machine than MySQL, but need to adjust
the MySQL <SPAN
>"bugs"</SPAN
> user permissions accordingly.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>
</P
><P
-> You'll want to make sure that your web server will run any
+> 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 srm.conf file:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->AddHandler cgi-script .cgi
+CLASS="programlisting"
+> AddHandler cgi-script .cgi
</PRE
></FONT
></TD
>
</P
><P
-> With apache you'll also want to make sure that within the
+> With apache you'll also want to make sure that within the
access.conf file the line:
<TABLE
BORDER="0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->Options ExecCGI</PRE
+CLASS="programlisting"
+> Options ExecCGI
+</PRE
></FONT
></TD
></TR
you intend to put the bugzilla .html and .cgi files.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Users of newer versions of Apache will generally find both
+> Users of newer versions of Apache will generally find both
of the above lines will be in the httpd.conf file, rather
than srm.conf or access.conf.
</P
></TABLE
></DIV
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are important files and directories that should not
+> There are important files and directories that should not
be a served by the HTTP server. These are most files in the
<SPAN
CLASS="QUOTE"
configure your HTTP server to not serve content from these
files. Failure to do so will expose critical passwords and
other data. Please see <A
-HREF="#HTACCESS"
+HREF="#htaccess"
>.htaccess files and security</A
> for details
on how to do this for Apache. I appreciate notes on how to
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN692"
>3.2.13. Installing the Bugzilla Files</A
></H2
><P
-> You should untar the Bugzilla files into a directory that
+> 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"
>). You may decide to put the
files off of the main web space for your web server or perhaps
off of <TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/local</TT
> with a symbolic link in
the web space that points to the Bugzilla directory. At any
server.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you symlink the bugzilla directory into your Apache's
+> If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive
<SPAN
-CLASS="ERRORNAME"
+CLASS="errorname"
>Forbidden</SPAN
> errors unless you add the
<SPAN
></TABLE
></DIV
><P
-> Once all the files are in a web accessible directory, make
+> 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"
+CLASS="filename"
>checksetup.pl</TT
> script, which locks down your
installation.
</P
><P
-> Lastly, you'll need to set up a symbolic link to
+> Lastly, you'll need to set up a symbolic link to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
> for the correct
location of your perl executable (probably
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/bin/perl</TT
>). Otherwise you must hack
all the .cgi files to change where they look for perl, or use
<A
-HREF="#SETPERL"
+HREF="#setperl"
>The setperl.csh Utility</A
>, found in
<A
-HREF="#PATCHES"
+HREF="#patches"
>Useful Patches and Utilities for Bugzilla</A
>. I suggest using the symlink
approach for future release compatability.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN708"
></A
>Example 3-1. Setting up bonsaitools symlink</B
></P
><P
-> Here's how you set up the Perl symlink on Linux to make
+> Here's how you set up the Perl symlink on Linux to make
Bugzilla work. Your mileage may vary. For some UNIX
operating systems, you probably need to subsitute
<SPAN
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->bash# mkdir /usr/bonsaitools
+CLASS="programlisting"
+> bash# mkdir /usr/bonsaitools
bash# mkdir /usr/bonsaitools/bin
bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl
</PRE
>
</P
><P
-> Alternately, you can simply run this perl one-liner to
+> Alternately, you can simply run this perl one-liner to
change your path to perl in all the files in your Bugzilla
installation:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+CLASS="programlisting"
+> perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
</PRE
></FONT
></TD
></DIV
>
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you don't have root access to set this symlink up,
+> If you don't have root access to set this symlink up,
check out the
<A
-HREF="#SETPERL"
+HREF="#setperl"
>The setperl.csh Utility</A
>, listed in <A
-HREF="#PATCHES"
+HREF="#patches"
>Useful Patches and Utilities for Bugzilla</A
>. It will change the path to perl in all your Bugzilla files for you.
</P
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN721"
>3.2.14. Setting Up the MySQL Database</A
></H2
><P
-> After you've gotten all the software installed and working you're ready
+> After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high
quality bug tracker.
</P
><P
-> First, you'll want to fix MySQL permissions to allow access
+> 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"
have minimal permissions.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla has not undergone a thorough security audit. It
+> Bugzilla has not undergone a thorough security audit. It
may be possible for a system cracker to somehow trick
Bugzilla into executing a command such as <B
-CLASS="COMMAND"
+CLASS="command"
>DROP
DATABASE mysql</B
>.
>
</P
><P
-> Give the MySQL root user a password. MySQL passwords are
+> Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
<P
></P
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>mysql
-u root mysql</B
> </TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
-> UPDATE user SET Password=PASSWORD ('new_password')
+CLASS="command"
+> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root'; </B
> </TT
>
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>FLUSH
PRIVILEGES;</B
> </TT
> From this point on, if you need to access
MySQL as the MySQL root user, you will need to use
<B
-CLASS="COMMAND"
+CLASS="command"
>mysql -u root -p</B
> and enter your
new_password. Remember that MySQL user names have nothing to
do with Unix user names (login names).
</P
><P
-> Next, we create the <SPAN
+> Next, we create the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user, and grant
as a different user.
</P
><P
-> Remember to set bugs_password to some unique password.
+> Remember to set bugs_password to some unique password.
<P
></P
><TABLE
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
-> mysql>
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
+> mysql>
</TT
>
<B
-CLASS="COMMAND"
-> FLUSH PRIVILEGES;
+CLASS="command"
+> FLUSH PRIVILEGES;
</B
>
</TT
>
</P
><P
-> Next, run the magic checksetup.pl script. (Many thanks to
+> Next, run the magic checksetup.pl script. (Many thanks to
Holger Schurig <holgerschurig@nikocity.de> for writing
this script!) It will make sure Bugzilla files and directories
have reasonable permissions, set up the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>data</TT
> directory, and create all the MySQL
tables.
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./checksetup.pl</B
> </TT
>
></P
> The first time you run it, it will create a
file called <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
>.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN768"
>3.2.15. Tweaking <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
></A
></H2
><P
-> This file contains a variety of settings you may need to tweak including
+> 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:
+> The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
-> server's host: just use <SPAN
+> server's host: just use <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
> if the
></LI
><LI
><P
-> database name: <SPAN
+> database name: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
></LI
><LI
><P
-> MySQL username: <SPAN
+> MySQL username: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
></LI
><LI
><P
-> Password for the <SPAN
+> Password for the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> MySQL account above
>
</P
><P
-> You should also install .htaccess files that the Apache
+> You should also install .htaccess files that the Apache
webserver will use to restrict access to Bugzilla data files.
See <A
-HREF="#HTACCESS"
+HREF="#htaccess"
>.htaccess files and security</A
>.
</P
><P
-> Once you are happy with the settings, re-run
+> Once you are happy with the settings, re-run
<TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
>. On this second run, it will
create the database and an administrator account for which
you will be prompted to provide information.
</P
><P
-> When logged into an administrator account once Bugzilla is
+> When logged into an administrator account once Bugzilla is
running, if you go to the query page (off of the Bugzilla main
menu), you'll find an <SPAN
CLASS="QUOTE"
that is filled with editable treats.
</P
><P
-> Should everything work, you will have a nearly empty Bugzilla
+> Should everything work, you will have a nearly empty Bugzilla
database and a newly-created <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
>
file in your Bugzilla root directory.
</P
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The second time you run checksetup.pl, you should become
+> The second time you run checksetup.pl, you should become
the user your web server runs as, and that you ensure that
you set the <SPAN
CLASS="QUOTE"
> parameter in
localconfig as well.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN799"
></A
>Example 3-2. Running checksetup.pl as the web user</B
></P
><P
-> Assuming your web server runs as user "apache", and
+> Assuming your web server runs as user "apache", and
Bugzilla is installed in "/usr/local/bugzilla", here's
one way to run checksetup.pl as the web server user.
As root, for the <EM
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
bash# chown -R apache:apache /usr/local/bugzilla
bash# su - apache
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The checksetup.pl script is designed so that you can run
+> 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
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN806"
>3.2.16. Setting Up Maintainers Manually (Optional)</A
></H2
><P
-> If you want to add someone else to every group by hand, you
+> If you want to add someone else to every group by hand, you
can do it by typing the appropriate MySQL commands. Run
<B
-CLASS="COMMAND"
+CLASS="command"
> mysql -u root -p bugs</B
> You
may need different parameters, depending on your security
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>update
profiles set groupset=0x7fffffffffffffff where
login_name = 'XXX';</B
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN817"
>3.2.17. The Whining Cron (Optional)</A
></H2
><P
-> By now you have a fully functional bugzilla, but what good
+> 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. This can be done by adding the following command as a
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <B
-CLASS="COMMAND"
+CLASS="command"
>cd
<your-bugzilla-directory> ;
./whineatnews.pl</B
>
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Depending on your system, crontab may have several manpages.
+> Depending on your system, crontab may have several manpages.
The following command should lead you to the most useful
page for this purpose:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> man 5 crontab
+CLASS="programlisting"
+> man 5 crontab
</PRE
></FONT
></TD
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN827"
>3.2.18. Bug Graphs (Optional)</A
></H2
><P
-> As long as you installed the GD and Graph::Base Perl modules
+> 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 collectstats daily at 5
+> Add a cron entry like this to run collectstats daily at 5
after midnight:
<P
></P
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>crontab
-e</B
> </TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> 5 0 * * * cd
<your-bugzilla-directory> ; ./collectstats.pl
</TT
>
</P
><P
-> After two days have passed you'll be able to view bug graphs
+> After two days have passed you'll be able to view bug graphs
from the Bug Reports page.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN839"
>3.2.19. Securing MySQL</A
></H2
><P
-> If you followed the installation instructions for setting up
+> If you followed the installation instructions for setting up
your "bugs" and "root" user in MySQL, much of this should not
apply to you. If you are upgrading an existing installation
of Bugzilla, you should pay close attention to this section.
</P
><P
-> Most MySQL installs have "interesting" default security parameters:
+> Most MySQL installs have "interesting" default security parameters:
<P
></P
><TABLE
>
</P
><P
-> This means anyone from anywhere on the internet can not only
+> This means anyone from anywhere on the internet can not only
drop the database with one SQL command, and they can write as
root to the system.
</P
><P
-> To see your permissions do:
+> To see your permissions do:
<P
></P
><TABLE
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>mysql -u root -p</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>use mysql;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>show tables;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>select * from user;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>select * from db;</B
>
</TT
>
</P
><P
-> To fix the gaping holes:
+> To fix the gaping holes:
<P
></P
><TABLE
>
</P
><P
-> If you're not running "mit-pthreads" you can use:
+> If you're not running "mit-pthreads" you can use:
<P
></P
><TABLE
>
</P
><P
-> With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
+> With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
<P
>
</P
><P
-> Use .htaccess files with the Apache webserver to secure your
+> Use .htaccess files with the Apache webserver to secure your
bugzilla install. See <A
-HREF="#HTACCESS"
+HREF="#htaccess"
>.htaccess files and security</A
>
</P
><P
-> Consider also:
+> Consider also:
<P
></P
><OL
TYPE="1"
><LI
><P
-> Turning off external networking with "--skip-networking",
+> Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
</P
></LI
><LI
><P
-> using the --user= option to mysqld to run it as an unprivileged
+> using the --user= option to mysqld to run it as an unprivileged
user.
</P
></LI
><LI
><P
-> starting MySQL in a chroot jail
+> starting MySQL in a chroot jail
</P
></LI
><LI
><P
-> running the httpd in a "chrooted" jail
+> running the httpd in a "chrooted" jail
</P
></LI
><LI
><P
-> making sure the MySQL passwords are different from the OS
+> making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
</P
></LI
><LI
><P
-> running MySQL on a separate untrusted machine
+> running MySQL on a separate untrusted machine
</P
></LI
><LI
><P
-> making backups ;-)
+> making backups ;-)
</P
></LI
></OL
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="OSX"
+NAME="osx"
>3.3. Mac OS X Installation Notes</A
></H1
><P
-> There are a lot of common libraries and utilities out there
+> 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
+> 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
+> Follow the instructions for setting up Fink. Once it's
installed, you'll want to run the following as root:
<B
-CLASS="COMMAND"
+CLASS="command"
>fink install gd</B
>
</P
><P
-> It will prompt you for a number of dependencies, type 'y' and
+> 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
+> 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
:-)
</P
><P
-> Instead of typing <SPAN
+> Instead of typing <SPAN
CLASS="QUOTE"
>"install GD"</SPAN
> at the
<TT
-CLASS="PROMPT"
+CLASS="prompt"
>cpan></TT
> prompt, type <B
-CLASS="COMMAND"
+CLASS="command"
>look
GD</B
>. This should go through the motions of
open a shell and drop you into the build directory. Apply the
following patch to the Makefile.PL file (save the patch into a
file and use the command <B
-CLASS="COMMAND"
+CLASS="command"
>patch <
patchfile</B
>:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->
+CLASS="programlisting"
+>
+
--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
+++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
@@ -3,8 +3,8 @@
>
</P
><P
-> Then, run these commands to finish the installation of the perl module:
+> Then, run these commands to finish the installation of the perl module:
<P
></P
><TABLE
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.PL</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make test</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make install</B
></TD
></TR
><TR
><TD
>And don't forget to run <B
-CLASS="COMMAND"
+CLASS="command"
>exit</B
> to get back to cpan.</TD
></TR
>
</P
><P
-> Happy Hacking!
+> Happy Hacking!
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BSDINSTALL"
+NAME="bsdinstall"
>3.4. BSD Installation Notes</A
></H1
><P
-> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
+> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
consult <A
-HREF="#OSX"
+HREF="#osx"
>Section 3.3</A
>.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GENINSTALL"
+NAME="geninstall"
>3.5. Installation General Notes</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN941"
>3.5.1. Modifying Your Running System</A
></H2
><P
-> Bugzilla optimizes database lookups by storing all relatively static
+> Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory.
</P
><P
-> If you make a change to the structural data in your database
+> If you make a change to the structural data in your database
(the versions table for example), or to the
<SPAN
CLASS="QUOTE"
changes won't show up.
</P
><P
-> That file gets automatically regenerated whenever it's more than an
+> That file gets automatically regenerated whenever it's more than an
hour old, so Bugzilla will eventually notice your changes by itself, but
generally you want it to notice right away, so that you can test things.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN948"
>3.5.2. Upgrading From Previous Versions</A
></H2
><P
-> The developers of Bugzilla are constantly adding new tables, columns and
+> The developers of Bugzilla are constantly adding new tables, columns and
fields. You'll get SQL errors if you just update the code. The strategy
to update is to simply always run the checksetup.pl script whenever
you upgrade your installation of Bugzilla. If you want to see what has
changed, you can read the comments in that file, starting from the end.
</P
><P
-> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
+> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
the latest version, please consult the file, "UPGRADING-pre-2.8" in the
Bugzilla root directory after untarring the archive.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="HTACCESS"
+NAME="htaccess"
>3.5.3. <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files and security</A
></H2
><P
-> To enhance the security of your Bugzilla installation,
+> To enhance the security of your Bugzilla installation,
Bugzilla will generate
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
></I
> files
which the Apache webserver can use to restrict access to
the bugzilla data files. The checksetup script will
generate the <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you are using an alternate provider of
+> If you are using an alternate provider of
<SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>webdot</SPAN
> services for graphing
(as described when viewing
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editparams.cgi</TT
> in your web
browser), you will need to change the ip address in
<TT
-CLASS="FILENAME"
+CLASS="filename"
>data/webdot/.htaccess</TT
> to the ip
address of the webdot server that you are using.
</P
><P
-> If you are using Internet Information Server or other web
+> 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 or other web
server which does not observe <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
>
conventions, you can disable their creation by editing
<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> and setting the
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$create_htaccess</TT
> variable to
<TT
-CLASS="PARAMETER"
+CLASS="parameter"
><I
>0</I
></TT
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MOD_THROTTLE"
+NAME="mod-throttle"
>3.5.4. <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_throttle</TT
> and Security</A
></H2
><P
-> It is possible for a user, by mistake or on purpose, to access
+> 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"
+CLASS="filename"
>mod_throttle</TT
> which can limit
connections by ip-address. You may download this module at
>. 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"
+CLASS="command"
>ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/"
> for more information. </P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONTENT_TYPE"
+NAME="content-type"
>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></H2
><P
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+CLASS="programlisting"
+> bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \
mv $i.tmp $i; done
</PRE
></TABLE
></P
><P
-> All this one-liner command does is search for all instances of
+> All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="UNIXHISTORY"
+NAME="unixhistory"
>3.5.6. UNIX Installation Instructions History</A
></H2
><P
-> This document was originally adapted from the Bonsai
+> This document was originally adapted from the Bonsai
installation instructions by Terry Weissman
<terry@mozilla.org>.
</P
><P
-> The February 25, 1999 re-write of this page was done by Ry4an
+> The February 25, 1999 re-write of this page was done by Ry4an
Brase <ry4an@ry4an.org>, with some edits by Terry
Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But
don't send bug reports to them; report them using bugzilla, at <A
> ).
</P
><P
-> This document was heavily modified again Wednesday, March 07
+> This document was heavily modified again Wednesday, March 07
2001 to reflect changes for Bugzilla 2.12 release by Matthew
P. Barnson. The securing MySQL section should be changed to
become standard procedure for Bugzilla installations.
</P
><P
-> Finally, the README in its entirety was marked up in SGML and
+> Finally, the README in its entirety was marked up in SGML and
included into the Guide on April 24, 2001 by Matt Barnson.
Since that time, it's undergone extensive modification as
Bugzilla grew.
</P
><P
-> Comments from people using this Guide for the first time are
+> Comments from people using this Guide for the first time are
particularly welcome.
</P
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WIN32"
+NAME="win32"
>3.6. Win32 Installation Notes</A
></H1
><P
any influence in the platform choice for running this system,
please choose GNU/Linux instead of Microsoft Windows.</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WININSTALL"
+NAME="wininstall"
>3.6.1. Win32 Installation: Step-by-step</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You should be familiar with, and cross-reference, the rest
+> You should be familiar with, and cross-reference, the rest
of the
<A
-HREF="#INSTALLATION"
+HREF="#installation"
>Bugzilla Installation</A
> section while performing your
Win32 installation.
utilities. What follows is the recommended installation
procedure for Win32; additional suggestions are provided in
<A
-HREF="#FAQ"
+HREF="#faq"
>Appendix A</A
>.
</P
></TABLE
></DIV
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
HREF="http://www.apache.org/"
TARGET="_top"
>Apache Web
> for Windows, and copy the Bugzilla files
somewhere Apache can serve them. Please follow all the
instructions referenced in <A
-HREF="#INSTALLATION"
+HREF="#installation"
>Bugzilla Installation</A
>
regarding your Apache configuration, particularly
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You may also use Internet Information Server or Personal
+> 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"
+HREF="#faq"
>Appendix A</A
>.
</P
><P
-> If you are going to use IIS, if on Windows NT you must
+> 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
></LI
><LI
><P
HREF="http://www.activestate.com/"
TARGET="_top"
>ActivePerl</A
> for a current compiled binary.
</P
><P
-> Please also check the following links to fully understand the status
+> 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
+> 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
+> Perl on Win32 FAQ</A
>
</P
></LI
><LI
><P
-> Use ppm from your perl\bin directory to install the following packs: DBI,
+> Use ppm from your perl\bin directory to install the following packs: DBI,
DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
to extract them from .zip format using Winzip or other unzip program first.
These additional ppm modules can be downloaded from ActiveState.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You can find a list of modules at
+> 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
+> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
>
</P
></TD
></TABLE
></DIV
><P
-> The syntax for ppm is:
+> The syntax for ppm is:
<TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:> </TT
><B
-CLASS="COMMAND"
+CLASS="command"
>ppm <modulename></B
>
</TT
>
</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1038"
+NAME="AEN1048"
></A
><P
><B
></P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>C:></TT
><B
-CLASS="COMMAND"
+CLASS="command"
>ppm
<TT
-CLASS="OPTION"
+CLASS="option"
>DBD-Mysql</TT
></B
></P
>Watch your capitalization!</P
></DIV
><P
-> You can find ActiveState ppm modules at
+> You can find ActiveState ppm modules at
<A
HREF="http://www.activestate.com/PPMPackages/5.6plus/"
TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
+> http://www.activestate.com/PPMPackages/5.6plus</A
>
</P
></LI
><LI
><P
-> Install MySQL for NT.
+> Install MySQL for NT.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
->
You can download MySQL for Windows NT from <A
+>
You can download MySQL for Windows NT from <A
HREF="http://www.mysql.com/"
TARGET="_top"
>MySQL.com</A
></LI
><LI
><P
-> Setup MySQL
+> Setup MySQL
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:> </TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>C:\mysql\bin\mysql -u root mysql</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>DELETE FROM user WHERE Host='localhost' AND User='';</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';</B
>
></LI
><LI
><A
-NAME="NTBUGS-PASSWORD"
+NAME="ntbugs-password"
></A
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>GRANT SELECT, INSERT, UPDATE, DELETE,
INDEX, ALTER, CREATE, DROP, REFERENCES
ON bugs.* to bugs@localhost
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>FLUSH PRIVILEGES;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>create database bugs;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>exit;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>C:\mysql\bin\mysqladmin -u root -p reload</B
>
</TT
></LI
><LI
><P
-> Edit <TT
-CLASS="FILENAME"
+> Edit <TT
+CLASS="filename"
>checksetup.pl</TT
> in your Bugzilla directory. Change
this line:
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = getgrnam($my_webservergroup);
+CLASS="programlisting"
+> my $webservergid = getgrnam($my_webservergroup);
</PRE
></FONT
></TD
>
</P
><P
-> to
+> to
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = $my_webservergroup;
+CLASS="programlisting"
+> my $webservergid = $my_webservergroup;
</PRE
></FONT
></TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = 'Administrators'
+CLASS="programlisting"
+> my $webservergid = 'Administrators'
</PRE
></FONT
></TD
></LI
><LI
><P
-> Run <TT
-CLASS="FILENAME"
+> Run <TT
+CLASS="filename"
>checksetup.pl</TT
> from the Bugzilla directory.
</P
><LI
><P
>Edit <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> to suit your
requirements. Set <TT
-CLASS="VARNAME"
+CLASS="varname"
>$db_pass</TT
> to your
<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> from <A
-HREF="#NTBUGS-PASSWORD"
+HREF="#ntbugs-password"
>step 5.d</A
>, and <TT
-CLASS="VARNAME"
+CLASS="varname"
>$webservergroup</TT
> to <SPAN
CLASS="QUOTE"
>"8"</SPAN
>.</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>"8"</SPAN
> for
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$webservergroup</TT
> above. If it's
wrong, please send corrections.</P
></LI
><LI
><P
-> Edit <TT
-CLASS="FILENAME"
+> Edit <TT
+CLASS="filename"
>defparams.pl</TT
> to suit your
requirements. Particularly, set
<TT
-CLASS="VARNAME"
+CLASS="varname"
>DefParam("maintainer")</TT
> and
<TT
-CLASS="VARNAME"
+CLASS="varname"
>DefParam("urlbase") to match your
install.</TT
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
></LI
><LI
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are several alternatives to Sendmail that will work on Win32.
+> There are several alternatives to Sendmail that will work on Win32.
The one mentioned here is a <EM
>suggestion</EM
>, not
></TABLE
></DIV
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
->
Download NTsendmail, available from<A
+>
Download NTsendmail, available from<A
HREF="http://www.ntsendmail.com/"
TARGET="_top"
> www.ntsendmail.com</A
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-># these settings configure the NTsendmail process
+CLASS="programlisting"
+> # these settings configure the NTsendmail process
use NTsendmail;
$ENV{"NTsendmail"}="your.smtpserver.box";
$ENV{"NTsendmail_debug"}=1;
></TR
></TABLE
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some mention to also edit
+> Some mention to also edit
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$db_pass</TT
> in
<TT
-CLASS="FILENAME"
+CLASS="filename"
>globals.pl</TT
> to be your
<SPAN
you around some problem authenticating to your
database, since globals.pl is not normally
restricted by <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
>, your
database password is exposed to whoever uses your
></LI
><LI
><P
-> Find and comment out all occurences of
+> Find and comment out all occurences of
<SPAN
CLASS="QUOTE"
>"<B
-CLASS="COMMAND"
+CLASS="command"
>open(SENDMAIL</B
>"</SPAN
> in
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-># new sendmail functionality
+CLASS="programlisting"
+> # new sendmail functionality
my $mail=new NTsendmail;
my $from="bugzilla\@your.machine.name.tld";
my $to=$login;
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some have found success using the commercial product,
+> Some have found success using the commercial product,
<SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>Windmail</SPAN
>.
You could try replacing your sendmail calls with:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+CLASS="programlisting"
+> open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
</PRE
></FONT
></TD
></LI
><LI
><P
-> Change all references in all files from
+> Change all references in all files from
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
> to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail.pl</TT
>, and
rename <TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
> to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail.pl</TT
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Many think this may be a change we want to make for
+> 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
></TABLE
></DIV
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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.
+> 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"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
+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->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist";
-} </PRE
+}
+
+
+</PRE
></FONT
></TD
></TR
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> use Net::SMTP;
+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->datasend('test');
$smtp->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
-exit; </PRE
+exit;
+
+
+</PRE
></FONT
></TD
></TR
></LI
><LI
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This step is optional if you are using IIS or another
+> 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
></TABLE
></DIV
><P
-> Modify the path to perl on the first line (#!) of all
+> Modify the path to perl on the first line (#!) of all
files to point to your Perl installation, and add
<SPAN
CLASS="QUOTE"
>
utility to speed part of this procedure, available in the
<A
-HREF="#PATCHES"
+HREF="#patches"
>Useful Patches and Utilities for Bugzilla</A
> section of The Bugzilla Guide.
However, it requires the Cygwin GNU-compatible environment
></LI
><LI
><P
-> Modify the invocation of all system() calls in all perl
- scripts in your Bugzilla directory. For instance, change
+> 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"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->
-system ("./processmail.pl",@ARGLIST);
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-> to
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
-system ("perl processmail.pl",@ARGLIST);
+system ("./processmail",@ARGLIST);
+ </programlisting> to
+ <programlisting>
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
</PRE
></FONT
></TD
></LI
><LI
><P
-> Add <TT
-CLASS="FUNCTION"
+> Add <TT
+CLASS="function"
>binmode()</TT
> calls so attachments
will work (<A
>).
</P
><P
-> Because Microsoft Windows based systems handle binary
+> Because Microsoft Windows based systems handle binary
files different than Unix based systems, you need to add
the following lines to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>createattachment.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>showattachment.cgi</TT
> before the
<TT
-CLASS="FUNCTION"
+CLASS="function"
>require 'CGI.pl';</TT
-> line.</P
+> line.
+</P
><P
-><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->binmode(STDIN);
-binmode(STDOUT);</PRE
+CLASS="programlisting"
+>
+binmode(STDIN);
+binmode(STDOUT);
+
+</PRE
></FONT
></TD
></TR
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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"
+CLASS="function"
>binmode()</TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
-CLASS="FUNCTION"
+CLASS="function"
>binmode()</TT
> at the begining of the attachment files, there should be logic to determine if <TT
-CLASS="FUNCTION"
+CLASS="function"
>binmode()</TT
> is needed or not.
</P
></OL
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you are using IIS or Personal Web Server, you must add cgi
+> 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
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
.cgi to: <perl install directory>\perl.exe %s %s
.pl to: <perl install directory>\perl.exe %s %s
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ADDLWINTIPS"
+NAME="addlwintips"
>3.6.2. Additional Windows Tips</A
></H2
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> From Andrew Pearson:
+> From Andrew Pearson:
<A
-NAME="AEN1212"
+NAME="AEN1221"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> You can make Bugzilla work with Personal Web Server for
+> 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"
>
</P
><P
-> Basically you need to add two String Keys in the
+> Basically you need to add two String Keys in the
registry at the following location:
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+CLASS="programlisting"
+> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
</PRE
></FONT
></TD
>
</P
><P
-> The keys should be called ".pl" and ".cgi", and both
+> The keys should be called ".pl" and ".cgi", and both
should have a value something like:
<B
-CLASS="COMMAND"
+CLASS="command"
>c:/perl/bin/perl.exe "%s" "%s"</B
>
</P
><P
-> The KB article only talks about .pl, but it goes into
+> The KB article only talks about .pl, but it goes into
more detail and provides a perl test script.
</P
></BLOCKQUOTE
></TABLE
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If attempting to run Bugzilla 2.12 or older, you will need
+> 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
later, which includes the current release, Bugzilla
2.14.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1224"
+NAME="AEN1233"
></A
><P
><B
2.12 or earlier</B
></P
><P
-> Replace this:
+> Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
my $enteredcryptpwd = $enteredpwd
</PRE
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BZLDAP"
+NAME="bzldap"
>3.6.3. Bugzilla LDAP Integration</A
></H2
><P
-> What follows is some late-breaking information on using the
+> What follows is some late-breaking information on using the
LDAP authentication options with Bugzilla. The author has not
tested these (nor even formatted this section!) so please
contribute feedback to the newsgroup.
</P
><P
-CLASS="LITERALLAYOUT"
->Mozilla::LDAP module<br>
+CLASS="literallayout"
+><br>
+Mozilla::LDAP module<br>
<br>
The Mozilla::LDAP module allows you to use LDAP for authentication to<br>
the Bugzilla system. This module is not required if you are not using<br>
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="ADMINISTRATION"
+NAME="administration"
>Chapter 4. Administering Bugzilla</A
></H1
><FONT
COLOR="RED"
-> Or, I just got this cool thing installed. Now what the heck do I
+> Or, I just got this cool thing installed. Now what the heck do I
do with it?
</FONT
><P
-> So you followed <SPAN
+> So you followed <SPAN
CLASS="QUOTE"
>"<A
-HREF="#INSTALLATION"
+HREF="#installation"
>Bugzilla Installation</A
>"</SPAN
> to the
getting data into your bug tracker.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="POSTINSTALL-CHECK"
+NAME="postinstall-check"
>4.1. Post-Installation Checklist</A
></H1
><P
-> After installation, follow the checklist below to help ensure
+> After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Bring up <TT
-CLASS="FILENAME"
+> Bring up <TT
+CLASS="filename"
>editparams.cgi</TT
> in your web
browser. This should be available as the <SPAN
will be sent with the maintainer as the return email
address.</P
><P
-> Set <SPAN
+> Set <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> to <EM
qualified domain name and web server path to your Bugzilla
installation.</P
><P
-> For example, if your bugzilla query page is
+> For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<SPAN
CLASS="QUOTE"
which groups of users are allowed to see and edit the
bug.</P
><P
-> Set "usebuggroups" to "on" <EM
+> Set "usebuggroups" to "on" <EM
>only</EM
> if you
may wish to restrict access to products. I suggest leaving
></LI
><LI
><P
-> <SPAN
+> <SPAN
CLASS="QUOTE"
>"usebuggroupsentry"</SPAN
>, when set to
installations where product isolation is a necessity.
</P
><P
-> Set "usebuggroupsentry" to "on" if you absolutely need to
+> Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
></LI
><LI
><P
-> You run into an interesting problem when Bugzilla reaches a
+> 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
extremely high-traffic Bugzilla databases.
</P
><P
-> Set "shadowdb" to "bug_shadowdb" if you will be running a
+> Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
enables many simultaneous users to read and write to the
database without interfering with one another.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Enabling "shadowdb" can adversely affect the stability
+> 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
comments per day.
</P
><P
-> If you use the "shadowdb" option, it is only natural that
+> 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!
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <TT
-CLASS="FILENAME"
+CLASS="filename"
>data/params</TT
> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <TT
-CLASS="FILENAME"
+CLASS="filename"
>data/params</TT
> file.</P
><P
-> If you have custom logos or HTML you must put in place to
+> If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
or "blurbhtml" text boxes.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The "headerhtml" text box is the HTML printed out
+> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page,
is read as the text to send to the new user along with their
password message.</P
><P
-> Add any text you wish to the "passwordmail" parameter box.
+> 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
their status even more than that which can be indicated by
the Resolution fields.</P
><P
-> Do you want to use the QA Contact ("useqacontact") and
+> Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
></LI
><LI
><P
-> Set "whinedays" to the amount of days you want to let bugs
+> Set "whinedays" to the amount 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
require that most other changes come with an
explanation.</P
><P
-> Set the "commenton" options according to your site policy.
+> 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"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It is generally far better to require a developer
+> 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
security to prevent snooping, watchers are not a good
idea.</P
><P
-> However, for most sites you should set
+> However, for most sites you should set
<SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="USERADMIN"
+NAME="useradmin"
>4.2. User Administration</A
></H1
><P
-> User administration is one of the easiest parts of Bugzilla.
+> User administration is one of the easiest parts of Bugzilla.
Keeping it from getting out of hand, however, can become a
challenge.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DEFAULTUSER"
+NAME="defaultuser"
>4.2.1. Creating the Default User</A
></H2
><P
-> When you first run checksetup.pl after installing Bugzilla, it
+> 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 were to delete the "super user" account, re-running
password.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you wish to add more administrative users, you must use the
+> 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>" denotes the mysql prompt, not
something you should type in):
<B
-CLASS="COMMAND"
+CLASS="command"
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> use bugs;</B
>
<B
-CLASS="COMMAND"
+CLASS="command"
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> update profiles set
groupset=0x7ffffffffffffff where login_name = "(user's
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MANAGEUSERS"
+NAME="manageusers"
>4.2.2. Managing Other Users</A
></H2
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="LOGIN"
+NAME="login"
>4.2.2.1. Logging In</A
></H3
><P
TYPE="1"
><LI
><P
-> Open the index.html page for your Bugzilla installation
+> Open the index.html page for your Bugzilla installation
in your browser window.
</P
></LI
><LI
><P
-> Click the "Query Existing Bug Reports" link.
+> Click the "Query Existing Bug Reports" link.
</P
></LI
><LI
><P
-> Click the "Log In" link at the foot of the page.
+> Click the "Log In" link at the foot of the page.
</P
></LI
><LI
><P
-> Type your email address, and the password which was
+> Type your email address, and the password which was
emailed to you when you created your Bugzilla account,
into the spaces provided.
</P
>Congratulations, you are logged in!</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CREATENEWUSERS"
+NAME="createnewusers"
>4.2.2.2. Creating new users</A
></H3
><P
-> Your users can create their own user accounts by clicking
+> Your users can create their own user accounts by clicking
the "New Account" link at the bottom of each page. However,
should you desire to create user accounts ahead of time,
here is how you do it.
TYPE="1"
><LI
><P
-> After logging in, click the "Users" link at the footer
+> After logging in, click the "Users" link at the footer
of the query page.
</P
></LI
><LI
><P
-> To see a specific user, type a portion of their login
+> To see a specific user, type a portion of their login
name in the box provided and click "submit". To see all
users, simply click the "submit" button. You must click
"submit" here to be able to add a new user.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> More functionality is available via the list on the
+> More functionality is available via the list on the
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the <B
-CLASS="COMMAND"
+CLASS="command"
>man
regexp</B
> manual page for details on regular
></LI
><LI
><P
-> Click the "Add New User" link at the bottom of the user
+> Click the "Add New User" link at the bottom of the user
list
</P
></LI
><LI
><P
-> Fill out the form presented. This page is
+> Fill out the form presented. This page is
self-explanatory. When done, click "submit".
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Adding a user this way will <EM
+> Adding a user this way will <EM
>not</EM
>
send an email informing them of their username and
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DISABLEUSERS"
+NAME="disableusers"
>4.2.2.3. Disabling Users</A
></H3
><P
-> I bet you noticed that big "Disabled Text" entry box
+> I bet you noticed that big "Disabled Text" entry box
available from the "Add New User" screen, when you edit an
account? By entering any text in this box and selecting
"submit", you have prevented the user from using Bugzilla
text box, will be presented to the user the next time she
attempts to use the system.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't disable your own administrative account, or you
+> Don't disable your own administrative account, or you
will hate life!
</P
><P
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MODIFYUSERS"
+NAME="modifyusers"
>4.2.2.4. Modifying Users</A
></H3
><P
-> Here I will attempt to describe the function of each option
+> Here I will attempt to describe the function of each option
on the Edit User screen.
</P
><P
><UL
><LI
><P
-> <EM
+> <EM
>Login Name</EM
>: This is generally the
user's email address. However, if you have edited your
system parameters, this may just be the user's login
name or some other identifier.
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> For compatability reasons, you should probably stick
+> For compatability reasons, you should probably stick
with email addresses as user login names. It will
make your life easier.
</P
></LI
><LI
><P
-> <EM
+> <EM
>Real Name</EM
>: Duh!
</P
></LI
><LI
><P
-> <EM
+> <EM
>Password</EM
>: You can change the user
password here. It is normal to only see asterisks.
></LI
><LI
><P
-> <EM
+> <EM
>Email Notification</EM
>: You may choose
from one of three options:
TYPE="1"
><LI
><P
-> All qualifying bugs except those which I change:
+> All qualifying bugs except those which I change:
The user will be notified of any change to any bug
for which she is the reporter, assignee, QA
Contact, CC recipient, or "watcher".
></LI
><LI
><P
-> Only those bugs which I am listed on the CC line:
+> Only those bugs which I am listed on the CC line:
The user will not be notified of changes to bugs
where she is the assignee, reporter, or QA
Contact, but will receive them if she is on the CC
list.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> She will still receive whining cron emails if
+> She will still receive whining cron emails if
you set up the "whinemail" feature.
</P
></TD
></LI
><LI
><P
-> <EM
+> <EM
>All Qualifying Bugs</EM
>: This
user is a glutton for punishment. If her name is
</P
></LI
></OL
-></P
+>
+</P
><P
-> <EM
+> <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
interface, and what you type in this box is presented as
the reason.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
-WIDTH="90%"
+CLASS="warning"
+WIDTH="100%"
BORDER="0"
><TR
><TD
></DIV
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> As of this writing, the user can still submit bugs
+> As of this writing, the user can still submit bugs
via the e-mail gateway, if you set it up, despite
the disabled text field. The e-mail gateway should
<EM
></LI
><LI
><P
-> <EM
+> <EM
>CanConfirm</EM
>: This field is only used
if you have enabled "unconfirmed" status in your
></LI
><LI
><P
-> <EM
+> <EM
>Creategroups</EM
>: This option will
allow a user to create and destroy groups in Bugzilla.
></LI
><LI
><P
-> <EM
+> <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.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Leaving this option unchecked does not prevent users
+> Leaving this option unchecked does not prevent users
from adding comments to a bug! They simply cannot
change a bug priority, severity, etc. unless they
are the assignee or reporter.
></LI
><LI
><P
-> <EM
+> <EM
>Editcomponents</EM
>: This flag allows a
user to create new products and components, as well as
></LI
><LI
><P
-> <EM
+> <EM
>Editkeywords</EM
>: If you use Bugzilla's
keyword functionality, enabling this feature allows a
></LI
><LI
><P
-> <EM
+> <EM
>Editusers</EM
>: This flag allows a user
do what you're doing right now: edit other users. This
></LI
><LI
><P
-> <EM
+> <EM
>PRODUCT</EM
>: PRODUCT bugs access. This
allows an administrator, with product-level granularity,
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PROGRAMADMIN"
+NAME="programadmin"
>4.3. Product, Component, Milestone, and Version
Administration</A
></H1
></TR
></TABLE
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PRODUCTS"
+NAME="products"
>4.3.1. Products</A
></H2
><FONT
>Formerly, and in some spots still, called
"Programs"</FONT
><P
-HREF="#GLOSS_PRODUCT"
+HREF="#gloss-product"
><I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Products</I
></A
> are
products (website, meetings...)
</P
><P
-> A Product (formerly called "Program", and still referred to
+> A Product (formerly called "Program", and still referred to
that way in some portions of the source code) controls some
very important functions. The number of "votes" available for
users to vote for the most important bugs is set per-product,
TYPE="1"
><LI
><P
-> Select "components" from the yellow footer
+> Select "components" from the yellow footer
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It may seem counterintuitive to click "components" when
+> It may seem counterintuitive to click "components" when
you want to edit the properties associated with
Products. This is one of a long list of things we want
in Bugzilla 3.0...
></LI
><LI
><P
-> Select the "Add" link to the right of "Add a new product".
+> Select the "Add" link to the right of "Add a new product".
</P
></LI
><LI
><P
-> Enter the name of the product and a description. The
+> Enter the name of the product and a description. The
Description field is free-form.
</P
></LI
></OL
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't worry about the "Closed for bug entry", "Maximum Votes
+> 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
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="COMPONENTS"
+NAME="components"
>4.3.2. Components</A
></H2
><P
-> Components are subsections of a Product.
+> Components are subsections of a Product.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1461"
+NAME="AEN1470"
></A
><P
><B
>Example 4-1. Creating some Components</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1463"
+NAME="AEN1472"
></A
><P
></P
><P
-> The computer game you are designing may have a "UI"
+> 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
to the Component.
</P
><P
-> To create a new Component:
+> To create a new Component:
</P
><P
></P
TYPE="1"
><LI
><P
-> Select the "Edit components" link from the "Edit product"
+> Select the "Edit components" link from the "Edit product"
page
</P
></LI
><LI
><P
-> Select the "Add" link to the right of the "Add a new
+> Select the "Add" link to the right of the "Add a new
component" text on the "Select Component" page.
</P
></LI
><LI
><P
-> Fill out the "Component" field, a short "Description", and
+> Fill out the "Component" field, a short "Description", and
the "Initial Owner". The Component and Description fields
are free-form; the "Initial Owner" field must be that of a
user ID already existing in the database. If the initial
owner does not exist, Bugzilla will refuse to create the
component.
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Is your "Default Owner" a user who is not yet in the
+> Is your "Default Owner" a user who is not yet in the
database? No problem.
<P
></P
TYPE="a"
><LI
><P
-> Select the "Log out" link on the footer of the
+> Select the "Log out" link on the footer of the
page.
</P
></LI
><LI
><P
-> Select the "New Account" link on the footer of
+> Select the "New Account" link on the footer of
the "Relogin" page
</P
></LI
><LI
><P
-> Type in the email address of the default owner
+> Type in the email address of the default owner
you want to create in the "E-mail address"
field, and her full name in the "Real name"
field, then select the "Submit Query" button.
></LI
><LI
><P
-> Now select "Log in" again, type in your login
+> Now select "Log in" again, type in your login
information, and you can modify the product to
use the Default Owner information you require.
</P
></LI
><LI
><P
-> Either Edit more components or return to the Bugzilla
+> Either Edit more components or return to the Bugzilla
Query Page. To return to the Product you were editing, you
must select the Components link as before.
</P
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VERSIONS"
+NAME="versions"
>4.3.3. Versions</A
></H2
><P
-> Versions are the revisions of the product, such as "Flinders
+> Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Using Versions
helps you isolate code changes and are an aid in reporting.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1490"
+NAME="AEN1499"
></A
><P
><B
>Example 4-2. Common Use of Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1492"
+NAME="AEN1501"
></A
><P
></P
><P
-> A user reports a bug against Version "Beta 2.0" of your
+> A user reports a bug against Version "Beta 2.0" of your
product. The current Version of your software is
"Release Candidate 1", and no longer has the bug. This
will help you triage and classify bugs according to
></DIV
>
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1494"
+NAME="AEN1503"
></A
><P
><B
>Example 4-3. A Different Use of Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1496"
+NAME="AEN1505"
></A
><P
></P
><P
-> This field has been used to good effect by an online
+> This field has been used to good effect by an online
service provider in a slightly different way. They had
three versions of the product: "Production", "QA", and
"Dev". Although it may be the same product, a bug in
>
</P
><P
-> To create and edit Versions:
+> To create and edit Versions:
</P
><P
></P
TYPE="1"
><LI
><P
-> From the "Edit product" screen, select "Edit Versions"
+> From the "Edit product" screen, select "Edit Versions"
</P
></LI
><LI
><P
-> You will notice that the product already has the default
+> You will notice that the product already has the default
version "undefined". If your product doesn't use version
numbers, you may want to leave this as it is or edit it so
that it is "---". You can then go back to the edit
versions page and add new versions to your product.
</P
><P
-> Otherwise, click the "Add" button to the right of the "Add
+> Otherwise, click the "Add" button to the right of the "Add
a new version" text.
</P
></LI
><LI
><P
-> Enter the name of the Version. This can be free-form
+> Enter the name of the Version. This can be free-form
characters up to the limit of the text box. Then select
the "Add" button.
</P
></LI
><LI
><P
-> At this point you can select "Edit" to edit more Versions,
+> At this point you can select "Edit" to edit more Versions,
or return to the "Query" page, from which you can navigate
back to the product through the "components" link at the
foot of the Query page.
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MILESTONES"
+NAME="milestones"
>4.3.4. Milestones</A
></H2
><P
-> Milestones are "targets" that you plan to get a bug fixed by.
+> 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. Or, you
have a bug that you plan to fix for 2.8, this would have a
milestone of 2.8.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Milestone options will only appear for a Product if you
+> Milestone options will only appear for a Product if you
turned the "usetargetmilestone" field in the "Edit
Parameters" screen "On".
</P
></TABLE
></DIV
><P
-> To create new Milestones, set Default Milestones, and set
+> To create new Milestones, set Default Milestones, and set
Milestone URL:
</P
><P
TYPE="1"
><LI
><P
-> Select "edit milestones"
+> Select "edit milestones"
</P
></LI
><LI
><P
-> Select "Add" to the right of the "Add a new milestone"
+> Select "Add" to the right of the "Add a new milestone"
text
</P
></LI
><LI
><P
-> Enter the name of the Milestone in the "Milestone" field.
+> 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. Select "Add".
</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1522"
+NAME="AEN1531"
></A
><P
><B
>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1524"
+NAME="AEN1533"
></A
><P
></P
><P
-> Let's say you create a target milestone called
+> Let's say you create a target milestone called
"Release 1.0", with Sortkey set to "0". Later, you
realize that you will have a public beta, called
"Beta1". You can create a Milestone called "Beta1",
></LI
><LI
><P
-> If you want to add more milestones, select the "Edit"
+> If you want to add more milestones, select the "Edit"
link. If you don't, well shoot, you have to go back to the
"query" page and select "components" again, and make your
way back to the Product you were editing.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This is another in the list of unusual user interface
+> This is another in the list of unusual user interface
decisions that we'd like to get cleaned up. Shouldn't
there be a link to the effect of "edit the Product I
was editing when I ended up here"? In any case,
></LI
><LI
><P
-> From the Edit product screen again (once you've made your
+> From the Edit product screen again (once you've made your
way back), enter the URL for a description of what your
milestones are for this product in the "Milestone URL"
field. It should be of the format
"http://www.foo.com/bugzilla/product_milestones.html"
</P
><P
-> Some common uses of this field include product
+> Some common uses of this field include product
descriptions, product roadmaps, and of course a simple
description of the meaning of each milestone.
</P
></LI
><LI
><P
-> If you're using Target Milestones, the "Default Milestone"
+> If you're using Target Milestones, the "Default Milestone"
field must have some kind of entry. If you really don't
care if people set coherent Target Milestones, simply
leave this at the default, "---". However, controlling
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VOTING"
+NAME="voting"
>4.3.5. Voting</A
></H2
><P
-> The concept of "voting" is a poorly understood, yet powerful
+> The concept of "voting" is a poorly understood, yet powerful
feature for the management of open-source projects. Each user
is assigned so many Votes per product, which they can freely
reassign (or assign multiple votes to a single bug). This
attention so they don't sit for a long time awaiting triage.
</P
><P
-> The daunting challenge of Votes is deciding where you draw the
+> The daunting challenge of Votes is deciding where you draw the
line for a "vocal majority". If you only have a user base of
100 users, setting a low threshold for bugs to move from
UNCONFIRMED to NEW makes sense. As the Bugzilla user base
TYPE="1"
><LI
><P
-> Navigate to the "Edit product" screen for the Product you
+> Navigate to the "Edit product" screen for the Product you
wish to modify
</P
></LI
><LI
><P
-> Set "Maximum Votes per person" to your calculated value.
+> Set "Maximum Votes per person" to your calculated value.
Setting this field to "0" disables voting.
</P
></LI
><LI
><P
-> Set "Maximum Votes a person can put on a single bug" to
+> Set "Maximum Votes a person can put on a single bug" to
your calculated value. It should probably be some number
lower than the "Maximum votes per person". Setting this
field to "0" disables voting, but leaves the voting
></LI
><LI
><P
-> Set "Number of votes a bug in this product needs to
+> Set "Number of votes a bug in this product needs to
automatically get out of the UNCONFIRMED state" to your
calculated number. Setting this field to "0" disables
the automatic move of bugs from UNCONFIRMED to NEW. Some
Votes if your Bugzilla user base is unable to affect which
bugs appear on Development radar?
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You should probably set this number to higher than a
+> You should probably set this number to higher than a
small coalition of Bugzilla users can influence it.
Most sites use this as a "referendum" mechanism -- if
users are able to vote a bug out of UNCONFIRMED, it is
></LI
><LI
><P
-> Once you have adjusted the values to your preference,
+> Once you have adjusted the values to your preference,
select the "Update" button.
</P
></LI
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GROUPS"
+NAME="groups"
>4.3.6. Groups and Group Security</A
></H2
><P
-> Groups can be very useful in bugzilla, because they allow
+> Groups can be very useful in bugzilla, because they allow
users to isolate bugs or products that should only be seen by
certain people. Groups can also be a complicated minefield of
interdependencies and weirdness if mismanaged.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1558"
+NAME="AEN1567"
></A
><P
><B
>Example 4-5. When to Use Group Security</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1560"
+NAME="AEN1569"
></A
><P
></P
><P
-> Many Bugzilla sites isolate "Security-related" bugs from
+> Many Bugzilla sites isolate "Security-related" bugs from
all other bugs. This way, they can have a fix ready
before the security vulnerability is announced to the
world. You can create a "Security" product which, by
into two categories: Generic and Product-Based.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Groups in Bugzilla are a complicated beast that evolved out
+> Groups in Bugzilla are a complicated beast that evolved out
of very simple user permission bitmasks, apparently itself
derived from common concepts in UNIX access controls. A
"bitmask" is a fixed-length number whose value can describe
next 32, etc.
</P
><P
-> Similarly, Bugzilla offers a bitmask to define group
+> Similarly, Bugzilla offers a bitmask to define group
permissions, with an internal limit of 64. Several are
already occupied by built-in permissions. The way around
this limitation is to avoid assigning groups to products if
></TABLE
></DIV
><P
-> To enable Generic Group Security ("usebuggroups"):
+> To enable Generic Group Security ("usebuggroups"):
</P
><P
></P
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
</P
></LI
><LI
><P
-> You will generally have no groups set up. Select the
+> You will generally have no groups set up. Select the
"groups" link in the footer.
</P
></LI
><LI
><P
-> Take a moment to understand the instructions on the "Edit
+> Take a moment to understand the instructions on the "Edit
Groups" screen. Once you feel confident you understand
what is expected of you, select the "Add Group" link.
</P
></LI
><LI
><P
-> Fill out the "New Name" (remember, no spaces!), "New
+> Fill out the "New Name" (remember, no spaces!), "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.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1575"
+NAME="AEN1584"
></A
><P
><B
>Example 4-6. Creating a New Group</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1577"
+NAME="AEN1586"
></A
><P
></P
><P
-> I created a group called DefaultGroup with a
+> I created a group called DefaultGroup with a
description of <SPAN
CLASS="QUOTE"
>"This is simply a group to play
></LI
></OL
><P
-> To enable Product-Based Group Security (usebuggroupsentry):
+> To enable Product-Based Group Security (usebuggroupsentry):
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't forget that you only have 64 groups masks available,
+> Don't forget that you only have 64 groups masks available,
total, for your installation of Bugzilla! If you plan on
having more than 50 products in your individual Bugzilla
installation, and require group security for your products,
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
"Edit Parameters" screen.
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
-WIDTH="90%"
+CLASS="warning"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> "usebuggroupsentry" has the capacity to prevent the
+> "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
></LI
><LI
><P
-> You will generally have no Groups set up, unless you
+> You will generally have no Groups set up, unless you
enabled "usebuggroupsentry" prior to creating any
Products. To create "Generic Group Security" groups,
follow the instructions given above. To create
></LI
></OL
><P
-> You may find this example illustrative for how bug groups work.
+> You may find this example illustrative for how bug groups work.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1592"
+NAME="AEN1601"
></A
><P
><B
>Example 4-7. Bugzilla Groups</B
></P
><P
-CLASS="LITERALLAYOUT"
->Bugzilla Groups example<br>
+CLASS="literallayout"
+><br>
+Bugzilla Groups example<br>
-----------------------<br>
<br>
For this example, let us suppose we have four groups, call them<br>
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SECURITY"
+NAME="security"
>4.4. Bugzilla Security</A
></H1
><TABLE
></TR
></TABLE
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Poorly-configured MySQL, Bugzilla, and FTP installations have
+> Poorly-configured MySQL, Bugzilla, and FTP 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
></TABLE
></DIV
><P
-> Secure your installation.
+> Secure your installation.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> These instructions must, of necessity, be somewhat vague
+> These instructions must, of necessity, be somewhat vague
since Bugzilla runs on so many different platforms. If you
have refinements of these directions for specific platforms,
please submit them to <A
TYPE="1"
><LI
><P
-> Ensure you are running at least MysQL version 3.22.32 or
+> Ensure you are running at least MysQL version 3.22.32 or
newer. Earlier versions had notable security holes and
poorly secured default configuration choices.
</P
> The MySQL Privilege System</A
> until you can recite it from memory!</P
><P
-> At the very least, ensure you password the "mysql -u root"
+> At the very least, ensure you password the "mysql -u root"
account and the "bugs" account, establish grant table
rights (consult the Keystone guide in Appendix C: The
Bugzilla Database for some easy-to-use details) that do
></LI
><LI
><P
-> Lock down /etc/inetd.conf. Heck, disable inet entirely on
+> Lock down /etc/inetd.conf. Heck, disable inet entirely on
this box. It should only listen to port 25 for Sendmail
and port 80 for Apache.
</P
></LI
><LI
><P
-> Do not run Apache as <SPAN
+> Do not run Apache as <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>. This will
Run it, instead, as a user with a name, set via your
httpd.conf file.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <SPAN
+> <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> is a real user on UNIX systems.
></LI
><LI
><P
-> Ensure you have adequate access controls for the
+> Ensure you have adequate access controls for the
$BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
directories, as well as the $BUGZILLA_HOME/localconfig and
$BUGZILLA_HOME/globals.pl files. The localconfig file
bug information to those who may not be allowed to see it.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla provides default .htaccess files to protect the
+> Bugzilla provides default .htaccess files to protect the
most common Apache installations. However, you should
verify these are adequate according to the site-wide
security policy of your web server, and ensure that the
details.
</P
><P
-> If you are using a web server that does not support the
+> If you are using a web server that does not support the
.htaccess control method, <EM
>you are at
risk!</EM
></TABLE
></DIV
><P
-> On Apache, you can use .htaccess files to protect access
+> On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
TARGET="_top"
> for adequate protection in your data/ and shadow/ directories.
</P
><P
-> Note the instructions which follow are Apache-specific.
+> Note the instructions which follow are Apache-specific.
If you use IIS, Netscape, or other non-Apache web servers,
please consult your system documentation for how to secure
these files from being transmitted to curious users.
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> <Files comments> allow<br>
from all </Files> deny from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> <Files localconfig> deny<br>
from all </Files> allow from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/shadow
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> deny from all </P
>
</P
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="INTEGRATION"
+NAME="integration"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BONSAI"
+NAME="bonsai"
>5.1. Bonsai</A
></H1
><P
>Bonsai is a web-based tool for managing <A
-HREF="#CVS"
+HREF="#cvs"
>CVS, the Concurrent Versioning System</A
>
. Using Bonsai, administrators can control open/closed status
> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <A
-HREF="#TINDERBOX"
+HREF="#tinderbox"
>Tinderbox, the Mozilla automated build management system</A
> and Bugzilla </P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CVS"
+NAME="cvs"
>5.2. CVS</A
></H1
><P
certain that Bugzilla is not tied into one particular software
management package.</P
><P
-> Follow the instructions in the FAQ for enabling Bugzilla e-mail
+> Follow the instructions in the FAQ 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"
state.
</P
><P
-> There is also a project, based upon somewhat dated Bugzilla
+> There is also a 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
+> http://homepages.kcbbs.gen.nz/~tonyg/</A
>, under the
<SPAN
CLASS="QUOTE"
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SCM"
+NAME="scm"
>5.3. Perforce SCM</A
></H1
><P
-> You can find the project page for Bugzilla and Teamtrack
+> You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
>.
</P
><P
-> Integration of Perforce with Bugzilla, once patches are applied,
+> 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
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="TINDERBOX"
+NAME="tinderbox"
>5.4. Tinderbox/Tinderbox2</A
></H1
><P
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="FUTURE"
+NAME="future"
>Chapter 6. The Future of Bugzilla</A
></H1
><TABLE
BORDER="0"
-BGCOLOR="#6495ED"
+BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="SYNOPSIS"
+CLASS="synopsis"
>Bugzilla's Future. Much of this is the present, now.</PRE
></FONT
></TD
></TR
></TABLE
><P
-> Bugzilla's future is a constantly-changing thing, as various developers
+> Bugzilla's future is a constantly-changing thing, as various developers
<SPAN
CLASS="QUOTE"
>"scratch an itch"</SPAN
not quite as readable as the rest of the Guide.
</P
><P
-> <P
-CLASS="LITERALLAYOUT"
-> Bugzilla Blue Sky<br>
+> <P
+CLASS="literallayout"
+><br>
+ Bugzilla Blue Sky<br>
<br>
Customisability<br>
<br>
</P
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><HR><H1
><A
-NAME="VARIANTS"
+NAME="variants"
>Chapter 7. Bugzilla Variants and Competitors</A
></H1
><P
>http://linas.org/linux/pm.html</A
></P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="RHBUGZILLA"
+NAME="rhbugzilla"
>7.1. Red Hat Bugzilla</A
></H1
><P
-> Red Hat Bugzilla is probably the most popular Bugzilla variant
+> Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
></P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VARIANT_FENRIS"
+NAME="variant-fenris"
>7.2. Loki Bugzilla (Fenris)</A
></H1
><P
>. It is a fork from Bugzilla.</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VARIANT_ISSUEZILLA"
+NAME="variant-issuezilla"
>7.3. Issuezilla</A
></H1
><P
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <A
-HREF="#VARIANT_SCARAB"
+HREF="#variant-scarab"
>Scarab, a newfangled Java-based issue tracker</A
>, is under heavy development
and looks promising!</P
></P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VARIANT_SCARAB"
+NAME="variant-scarab"
>7.4. Scarab</A
></H1
><P
></P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VARIANT_PERFORCE"
+NAME="variant-perforce"
>7.5. Perforce SCM</A
></H1
><P
>http://www.perforce.com/perforce/technotes/note052.html</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VARIANT_SOURCEFORGE"
+NAME="variant-sourceforge"
>7.6. SourceForge</A
></H1
><P
></DIV
></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><HR><H1
><A
-NAME="FAQ"
+NAME="faq"
>Appendix A. The Bugzilla FAQ</A
></H1
><DIV
-CLASS="QANDASET"
+CLASS="qandaset"
><DL
><DT
>1. <A
-HREF="#FAQ_GENERAL"
+HREF="#faq-general"
>General Questions</A
></DT
><DD
><DL
><DT
>A.1.1. <A
-HREF="#AEN1713"
-> Where can I find information about Bugzilla?</A
+HREF="#AEN1722"
+> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="#AEN1719"
-> What license is Bugzilla distributed under?
+HREF="#AEN1728"
+> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="#AEN1725"
-> How do I get commercial support for Bugzilla?
+HREF="#AEN1734"
+> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="#AEN1732"
-> What major companies or projects are currently using Bugzilla
+HREF="#AEN1741"
+> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="#AEN1757"
-> Who maintains Bugzilla?
+HREF="#AEN1766"
+> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="#AEN1763"
-> How does Bugzilla stack up against other bug-tracking databases?
+HREF="#AEN1772"
+> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="#AEN1770"
-> How do I change my user name in Bugzilla?
+HREF="#AEN1779"
+> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
-HREF="#AEN1775"
-> Why doesn't Bugzilla offer this or that feature or compatability
+HREF="#AEN1784"
+> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
-HREF="#AEN1782"
-> Why MySQL? I'm interested in seeing Bugzilla run on
+HREF="#AEN1791"
+> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
-HREF="#AEN1800"
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
+HREF="#AEN1809"
+> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
></DD
><DT
>2. <A
-HREF="#FAQ_REDHAT"
+HREF="#faq-redhat"
>Red Hat Bugzilla</A
></DT
><DD
><DL
><DT
>A.2.1. <A
-HREF="#AEN1817"
-> What about Red Hat Bugzilla?
+HREF="#AEN1826"
+> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
-HREF="#AEN1825"
-> What are the primary benefits of Red Hat Bugzilla?
+HREF="#AEN1834"
+> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
-HREF="#AEN1853"
-> What's the current status of Red Hat Bugzilla?
+HREF="#AEN1862"
+> What's the current status of Red Hat Bugzilla?
</A
></DT
></DL
></DD
><DT
>3. <A
-HREF="#FAQ_LOKI"
+HREF="#faq-loki"
>Loki Bugzilla (AKA Fenris)</A
></DT
><DD
><DL
><DT
>A.3.1. <A
-HREF="#AEN1866"
-> What is Loki Bugzilla (Fenris)?
+HREF="#AEN1875"
+> What is Loki Bugzilla (Fenris)?
</A
></DT
></DL
></DD
><DT
>4. <A
-HREF="#FAQ_PHB"
+HREF="#faq-phb"
>Pointy-Haired-Boss Questions</A
></DT
><DD
><DL
><DT
>A.4.1. <A
-HREF="#AEN1877"
-> Is Bugzilla web-based or do you have to have specific software or
+HREF="#AEN1886"
+> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
-HREF="#AEN1882"
-> Has anyone you know of already done any Bugzilla integration with
+HREF="#AEN1891"
+> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
-HREF="#AEN1887"
-> Does Bugzilla allow the user to track multiple projects?
+HREF="#AEN1896"
+> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
-HREF="#AEN1892"
-> If I am on many projects, and search for all bugs assigned to me, will
+HREF="#AEN1901"
+> 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.4.5. <A
-HREF="#AEN1897"
-> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
+HREF="#AEN1906"
+> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
-HREF="#AEN1902"
-> Does Bugzilla allow us to define our own priorities and levels? Do we
+HREF="#AEN1911"
+> 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.4.7. <A
-HREF="#AEN1909"
-> The index.html page doesn't show the footer. It's really annoying to have
+HREF="#AEN1918"
+> The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages?
</A
></DT
><DT
>A.4.8. <A
-HREF="#AEN1931"
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+HREF="#AEN1940"
+> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.4.9. <A
-HREF="#AEN1939"
-> Is there email notification and if so, what do you see when you get an
+HREF="#AEN1948"
+> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</A
></DT
><DT
>A.4.10. <A
-HREF="#AEN1944"
-> Can email notification be set up to send to multiple
+HREF="#AEN1953"
+> 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.4.11. <A
-HREF="#AEN1949"
-> If there is email notification, do users have to have any particular
+HREF="#AEN1958"
+> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
>A.4.12. <A
-HREF="#AEN1956"
-> If I just wanted to track certain bugs, as they go through life, can I
+HREF="#AEN1965"
+> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</A
></DT
><DT
>A.4.13. <A
-HREF="#AEN1961"
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
+HREF="#AEN1970"
+> 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?
></DT
><DT
>A.4.14. <A
-HREF="#AEN1969"
-> Has anyone converted Bugzilla to another language to be used in other
+HREF="#AEN1978"
+> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
-HREF="#AEN1974"
-> Can a user create and save reports? Can they do this in Word format?
+HREF="#AEN1983"
+> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
-HREF="#AEN1979"
-> Can a user re-run a report with a new project, same query?
+HREF="#AEN1988"
+> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
-HREF="#AEN1984"
-> Can a user modify an existing report and then save it into another name?
+HREF="#AEN1993"
+> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
-HREF="#AEN1989"
-> Does Bugzilla have the ability to search by word, phrase, compound
+HREF="#AEN1998"
+> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
-HREF="#AEN1994"
-> Can the admin person establish separate group and individual user
+HREF="#AEN2003"
+> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
-HREF="#AEN1999"
-> Does Bugzilla provide record locking when there is simultaneous access
+HREF="#AEN2008"
+> 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.4.21. <A
-HREF="#AEN2004"
-> Are there any backup features provided?
+HREF="#AEN2013"
+> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
-HREF="#AEN2010"
-> Can users be on the system while a backup is in progress?
+HREF="#AEN2019"
+> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
-HREF="#AEN2015"
-> What type of human resources are needed to be on staff to install and
+HREF="#AEN2024"
+> 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
></DT
><DT
>A.4.24. <A
-HREF="#AEN2022"
-> What time frame are we looking at if we decide to hire people to install
+HREF="#AEN2031"
+> 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,
></DT
><DT
>A.4.25. <A
-HREF="#AEN2027"
-> Is there any licensing fee or other fees for using Bugzilla? Any
+HREF="#AEN2036"
+> 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
></DD
><DT
>5. <A
-HREF="#FAQ_INSTALL"
+HREF="#faq-install"
>Bugzilla Installation</A
></DT
><DD
><DL
><DT
>A.5.1. <A
-HREF="#AEN2034"
-> How do I download and install Bugzilla?
+HREF="#AEN2043"
+> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
-HREF="#AEN2040"
-> How do I install Bugzilla on Windows NT?
+HREF="#AEN2049"
+> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
-HREF="#AEN2045"
-> Is there an easy way to change the Bugzilla cookie name?
+HREF="#AEN2054"
+> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
></DL
></DD
><DT
>6. <A
-HREF="#FAQ_SECURITY"
+HREF="#faq-security"
>Bugzilla Security</A
></DT
><DD
><DL
><DT
>A.6.1. <A
-HREF="#AEN2052"
-> How do I completely disable MySQL security if it's giving me problems
+HREF="#AEN2061"
+> 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.6.2. <A
-HREF="#AEN2058"
-> Are there any security problems with Bugzilla?
+HREF="#AEN2067"
+> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
-HREF="#AEN2063"
-> I've implemented the security fixes mentioned in Chris Yeh's security
+HREF="#AEN2072"
+> 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
></DD
><DT
>7. <A
-HREF="#FAQ_EMAIL"
+HREF="#faq-email"
>Bugzilla Email</A
></DT
><DD
><DL
><DT
>A.7.1. <A
-HREF="#AEN2070"
-> I have a user who doesn't want to receive any more email from Bugzilla.
+HREF="#AEN2079"
+> 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.7.2. <A
-HREF="#AEN2075"
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
+HREF="#AEN2084"
+> 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.7.3. <A
-HREF="#AEN2080"
-> I want whineatnews.pl to whine at something more, or other than, only new
+HREF="#AEN2089"
+> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
-HREF="#AEN2086"
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
+HREF="#AEN2095"
+> 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.7.5. <A
-HREF="#AEN2093"
-> How do I set up the email interface to submit/change bugs via email?
+HREF="#AEN2102"
+> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
-HREF="#AEN2098"
-> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
+HREF="#AEN2107"
+> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
-HREF="#AEN2105"
-> How come email never reaches me from bugzilla changes?
+HREF="#AEN2114"
+> How come email never reaches me from bugzilla changes?
</A
></DT
></DL
></DD
><DT
>8. <A
-HREF="#FAQ_DB"
+HREF="#faq-db"
>Bugzilla Database</A
></DT
><DD
><DL
><DT
>A.8.1. <A
-HREF="#AEN2113"
-> I've heard Bugzilla can be used with Oracle?
+HREF="#AEN2122"
+> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
-HREF="#AEN2118"
-> Bugs are missing from queries, but exist in the database (and I can pull
+HREF="#AEN2127"
+> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
-HREF="#AEN2123"
-> I think my database might be corrupted, or contain invalid entries. What
+HREF="#AEN2132"
+> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
-HREF="#AEN2131"
-> I want to manually edit some entries in my database. How?
+HREF="#AEN2140"
+> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
-HREF="#AEN2136"
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
+HREF="#AEN2145"
+> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
-HREF="#AEN2141"
-> I think I've set up MySQL permissions correctly, but bugzilla still can't
+HREF="#AEN2150"
+> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
-HREF="#AEN2146"
-> How do I synchronize bug information among multiple different Bugzilla
+HREF="#AEN2155"
+> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
-HREF="#AEN2153"
-> Why do I get bizarre errors when trying to submit data, particularly problems
+HREF="#AEN2162"
+> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
-HREF="#AEN2158"
-> How come even after I delete bugs, the long descriptions show up?
+HREF="#AEN2167"
+> How come even after I delete bugs, the long descriptions show up?
</A
></DT
></DL
></DD
><DT
>9. <A
-HREF="#FAQ_NT"
+HREF="#faq-nt"
>Bugzilla and Win32</A
></DT
><DD
><DL
><DT
>A.9.1. <A
-HREF="#AEN2168"
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+HREF="#AEN2177"
+> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
-HREF="#AEN2173"
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
+HREF="#AEN2182"
+> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
-HREF="#AEN2178"
-> CGI's are failing with a "something.cgi is not a valid Windows NT
+HREF="#AEN2187"
+> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
-HREF="#AEN2186"
-> Can I have some general instructions on how to make Bugzilla on Win32 work?
+HREF="#AEN2195"
+> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
-HREF="#AEN2192"
-> I'm having trouble with the perl modules for NT not being able to talk to
+HREF="#AEN2201"
+> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
></DT
></DD
><DT
>10. <A
-HREF="#FAQ_USE"
+HREF="#faq-use"
>Bugzilla Usage</A
></DT
><DD
><DL
><DT
>A.10.1. <A
-HREF="#AEN2213"
-> The query page is very confusing. Isn't there a simpler way to query?
+HREF="#AEN2222"
+> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
-HREF="#AEN2219"
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
+HREF="#AEN2228"
+> 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.10.3. <A
-HREF="#AEN2229"
-> I can't upload anything into the database via the "Create Attachment"
+HREF="#AEN2238"
+> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
-HREF="#AEN2234"
-> Email submissions to Bugzilla that have attachments end up asking me to
+HREF="#AEN2243"
+> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
-HREF="#AEN2239"
-> How do I change a keyword in Bugzilla, once some bugs are using it?
+HREF="#AEN2248"
+> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
></DL
></DD
><DT
>11. <A
-HREF="#FAQ_HACKING"
+HREF="#faq-hacking"
>Bugzilla Hacking</A
></DT
><DD
><DL
><DT
>A.11.1. <A
-HREF="#AEN2246"
-> What bugs are in Bugzilla right now?
+HREF="#AEN2255"
+> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
-HREF="#AEN2255"
-> How can I change the default priority to a null value? For instance, have the default
+HREF="#AEN2264"
+> 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.11.3. <A
-HREF="#AEN2261"
-> What's the best way to submit patches? What guidelines should I follow?
+HREF="#AEN2270"
+> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
></DL
></DD
></DL
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_GENERAL"
+NAME="faq-general"
></A
>1. General Questions</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1713"
+NAME="AEN1722"
></A
><B
>A.1.1. </B
-> Where can I find information about Bugzilla?</P
+>
+ Where can I find information about Bugzilla?</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can stay up-to-date with the latest Bugzilla
+>
+ You can stay up-to-date with the latest Bugzilla
information at <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1719"
+NAME="AEN1728"
></A
><B
>A.1.2. </B
-> What license is Bugzilla distributed under?
+>
+ What license is Bugzilla distributed under?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla is covered by the Mozilla Public License.
+>
+ 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
+> http://www.mozilla.org/MPL/</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1725"
+NAME="AEN1734"
></A
><B
>A.1.3. </B
-> How do I get commercial support for Bugzilla?
+>
+ How do I get commercial support for Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <A
+>
+ <A
HREF="http://www.collab.net/"
TARGET="_top"
>www.collab.net</A
aren't interested in small projects.
</P
><P
-> There are several experienced
+> There are several experienced
Bugzilla hackers on the mailing list/newsgroup who are willing
to whore themselves out for generous compensation.
Try sending a message to the mailing list asking for a volunteer.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1732"
+NAME="AEN1741"
></A
><B
>A.1.4. </B
-> What major companies or projects are currently using Bugzilla
+>
+ What major companies or projects are currently using Bugzilla
for bug-tracking?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> There are <EM
+>
+ There are <EM
>dozens</EM
> of major comapanies with public
Bugzilla sites to track bugs in their products. A few include:
>
</P
><P
-> Suffice to say, there are more than enough huge projects using Bugzilla
+> 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1757"
+NAME="AEN1766"
></A
><B
>A.1.5. </B
-> Who maintains Bugzilla?
+>
+ Who maintains Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla maintenance has been in a state of flux recently.
+>
+ Bugzilla maintenance has been in a state of flux recently.
Please check <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1763"
+NAME="AEN1772"
></A
><B
>A.1.6. </B
-> How does Bugzilla stack up against other bug-tracking databases?
+>
+ How does Bugzilla stack up against other bug-tracking databases?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> A year has gone by, and I <EM
+>
+ A year has gone by, and I <EM
>still</EM
> can't
find any head-to-head comparisons of Bugzilla against
flexibility, and superior ease-of-use.
</P
><P
-> If you happen to be a commercial bug-tracker vendor, please
+> If you happen to be a commercial bug-tracker vendor, please
step forward with a rebuttal so I can include it in the
FAQ. We're not in pursuit of Bugzilla ueber alles; we
simply love having a powerful, open-source tool to get our
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1770"
+NAME="AEN1779"
></A
><B
>A.1.7. </B
-> How do I change my user name in Bugzilla?
+>
+ How do I change my user name in Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can't. However, the administrative account can, by simply opening
+>
+ You can't. However, the administrative account can, by simply opening
your user account in editusers.cgi and changing the login name.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1775"
+NAME="AEN1784"
></A
><B
>A.1.8. </B
-> Why doesn't Bugzilla offer this or that feature or compatability
+>
+ Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It may be that the support has not been built yet, or that you
+>
+ 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!
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1782"
+NAME="AEN1791"
></A
><B
>A.1.9. </B
-> Why MySQL? I'm interested in seeing Bugzilla run on
+>
+ Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
>Terry Weissman answers,
<A
-NAME="AEN1786"
+NAME="AEN1795"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> You're not the only one. But <EM
+> You're not the only one. But <EM
>I</EM
> am not very interested. I'm not
a real SQL or database person. I just wanted to make a useful tool,
>
</P
><P
-> Things aren't quite that grim these days, however. Terry pretty much
+> Things aren't quite that grim these days, however. Terry pretty much
sums up much of the thinking many of us have for Bugzilla, but there
is light on the horizon for database-independence! Here are some options:
</P
><TBODY
><TR
><TD
-> <EM
+> <EM
><A
HREF="http://bugzilla.redhat.com/"
TARGET="_top"
></TR
><TR
><TD
-> <EM
+> <EM
><A
HREF="http://sourceforge.net/projects/interzilla"
TARGET="_top"
></TR
><TR
><TD
-> <EM
+> <EM
>Bugzilla 3.0</EM
>: One of the primary stated goals
is multiple database support.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1800"
+NAME="AEN1809"
></A
><B
>A.1.10. </B
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
+>
+ Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
+>
+ Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
submissions is "don't break bugzilla.mozilla.org". If it breaks it, your
patch will be reverted faster than you can do a diff.
</P
><P
-> Here's Terry Weissman's comment, for some historical context:
+> Here's Terry Weissman's comment, for some historical context:
<A
-NAME="AEN1805"
+NAME="AEN1814"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> [This was] purely my own convention. I wanted a place to put a version of
+> [This was] purely my own convention. I wanted a place to put a version of
Perl and other tools that was strictly under my control for the
various webtools, and not subject to anyone else. Edit it to point
to whatever you like.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> We always recommend that, if possible, you keep the path
+> We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
of perl to /usr/bonsaitools/bin/perl. This will make upgrading
your Bugzilla much easier in the future.
</P
><P
-> Obviously, if you do not have root access to your Bugzilla
+> Obviously, if you do not have root access to your Bugzilla
box, our suggestion is irrelevant.
</P
></TD
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_REDHAT"
+NAME="faq-redhat"
></A
>2. Red Hat Bugzilla</H3
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <EM
+> <EM
>This section is no longer up-to-date.</EM
>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
>
</P
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1817"
+NAME="AEN1826"
></A
><B
>A.2.1. </B
-> What about Red Hat Bugzilla?
+>
+ What about Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
+>
+ Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
than stock Bugzilla. Check it out at
http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/.
They've set their Bugzilla up to work with Oracle out of the box.
yourself?
</P
><P
-> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
+> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
-NAME="AEN1822"
+NAME="AEN1831"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> Somebody needs to take the ball and run with it. I'm the only
+> Somebody needs to take the ball and run with it. I'm the only
maintainer and am very pressed for time.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1825"
+NAME="AEN1834"
></A
><B
>A.2.2. </B
-> What are the primary benefits of Red Hat Bugzilla?
+>
+ What are the primary benefits of Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <EM
+>
+ <EM
>Dave Lawrence</EM
>:
<A
-NAME="AEN1830"
+NAME="AEN1839"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> For the record, we are not using any template type implementation for
+> For the record, we are not using any template type implementation for
the cosmetic changes maded to Bugzilla. It is just alot of html changes
in the code itself. I admit I may have gotten a little carried away with it
but the corporate types asked for a more standardized interface to match up
internal tools I am working on also look like Bugzilla.
</P
><P
-> I do want to land the changes that I have made to Bugzilla but I may
+> I do want to land the changes that I have made to Bugzilla but I may
have to back out a good deal and make a different version of Red Hat's
Bugzilla for checking in to CVS. Especially the cosmetic changes because it
seems they may not fit the general public. I will do that as soon as I can.
is difficult sometimes to come by.
</P
><P
-> There are also a good deal of other changes that were requested by
+> There are also a good deal of other changes that were requested by
management for things like support contracts and different permission
groups for making bugs private. Here is a short list of the major
changes that have been made:
TYPE="1"
><LI
><P
-> No enum types. All old enum types are now separate smaller tables.
+> No enum types. All old enum types are now separate smaller tables.
</P
></LI
><LI
><P
-> No bit wise operations. Not all databases support this so they were
+> No bit wise operations. Not all databases support this so they were
changed to a more generic way of doing this task
</P
></LI
><LI
><P
-> Bug reports can only be altered by the reporter, assignee, or a
+> Bug reports can only be altered by the reporter, assignee, or a
privileged bugzilla user. The rest of the world can see the bug but in
a non-changeable format (unless the bug has been marked private). They
can however add comments, add and remove themselves from the CC list
></LI
><LI
><P
-> Different group scheme. Each group has an id number related to it.
+> Different group scheme. Each group has an id number related to it.
There is a user_group table which contains userid to groupid mappings
to determine which groups each user belongs to. Additionally there is
a bug_group table that has bugid to groupid mappings to show which
></LI
><LI
><P
-> Product groups. product_table created to only allow certain products to
+> Product groups. product_table created to only allow certain products to
be visible for certain groups in both bug entry and query. This was
particulary helpful for support contracts.
</P
></LI
><LI
><P
-> Of course many (too many) changes to Bugzilla code itself to allow use
+> Of course many (too many) changes to Bugzilla code itself to allow use
with Oracle and still allow operation with Mysql if so desired.
Currently if you use Mysql it is set to use Mysql's old permission
scheme to keep breakage to a minimum. Hopefully one day this will
></LI
><LI
><P
-> Uses Text::Template perl module for rendering of the dynamic HTML pages
+> Uses Text::Template perl module for rendering of the dynamic HTML pages
such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and
footer parts of the page. This allows the html to be separate from the
perl code for customizing the look and feel of the page to one's
></LI
><LI
><P
-> There are many other smaller changes. There is also a port to Oracle
+> There are many other smaller changes. There is also a port to Oracle
that I have been working on as time permits but is not completely
finished but somewhat usable. I will merge it into our standard code
base when it becomes production quality. Unfortunately there will have
></LI
></OL
><P
-> Both the Mysql and Oracle versions of our current code base are
+> Both the Mysql and Oracle versions of our current code base are
available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit
patch files for all of the changes I have made and he can determine what is
suitable for addition to the main bugzilla cade base. But for me to commit
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1853"
+NAME="AEN1862"
></A
><B
>A.2.3. </B
-> What's the current status of Red Hat Bugzilla?
+>
+ What's the current status of Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <DIV
-CLASS="NOTE"
+>
+ <DIV
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This information is somewhat dated; I last updated it
+> This information is somewhat dated; I last updated it
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</P
>Dave Lawrence</EM
>:
<A
-NAME="AEN1860"
+NAME="AEN1869"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> I suppose the current thread warrants an update on the status of
+> I suppose the current thread warrants an update on the status of
Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on
Oracle for the last two days in our production environment. I
tried to do as much testing as possible with it before going live
thing going to help others that may need it.
</P
><P
-> As Matt has mentioned it is still using out-dated code and with a
+> As Matt has mentioned it is still using out-dated code and with a
little help I would like to bring everything up to date for
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_LOKI"
+NAME="faq-loki"
></A
>3. Loki Bugzilla (AKA Fenris)</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1866"
+NAME="AEN1875"
></A
><B
>A.3.1. </B
-> What is Loki Bugzilla (Fenris)?
+>
+ What is Loki Bugzilla (Fenris)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Loki Games has a customized version of Bugzilla available at
+>
+ Loki Games has a customized version of Bugzilla available at
<A
HREF="http://fenris.lokigames.com/"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_PHB"
+NAME="faq-phb"
></A
>4. Pointy-Haired-Boss Questions</H3
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The title of this section doesn't mean you're a PHB -- it just means
+> The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</P
></TD
>
</P
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1877"
+NAME="AEN1886"
></A
><B
>A.4.1. </B
-> Is Bugzilla web-based or do you have to have specific software or
+>
+ Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It is web and e-mail based. You can edit bugs by sending specially
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1882"
+NAME="AEN1891"
></A
><B
>A.4.2. </B
-> Has anyone you know of already done any Bugzilla integration with
+>
+ Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes! You can find more information elsewhere in "The Bugzilla
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1887"
+NAME="AEN1896"
></A
><B
>A.4.3. </B
-> Does Bugzilla allow the user to track multiple projects?
+>
+ Does Bugzilla allow the user to track multiple projects?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Absolutely! You can track up to a "soft-limit" of around
+>
+ Absolutely! You can track up to a "soft-limit" of around
64 individual "Products", that can each be composed of as
many "Components" as you want. Check the Administration
section of the Bugzilla Guide for more information regarding
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1892"
+NAME="AEN1901"
></A
><B
>A.4.4. </B
-> If I am on many projects, and search for all bugs assigned to me, will
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1897"
+NAME="AEN1906"
></A
><B
>A.4.5. </B
-> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
+>
+ Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. There are many specific MIME-types that are pre-defined by Bugzilla,
+>
+ Yes. There are many specific MIME-types that are pre-defined by Bugzilla,
but you may specify any arbitrary MIME-type you need when you
upload the file. Since all attachments are stored in the database,
however, I recommend storing large binary attachments elsewhere
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1902"
+NAME="AEN1911"
></A
><B
>A.4.6. </B
-> Does Bugzilla allow us to define our own priorities and levels? Do we
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes. However, modifying some fields, notably those related to bug
+>
+ 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
+> 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"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1909"
+NAME="AEN1918"
></A
><B
>A.4.7. </B
-> The index.html page doesn't show the footer. It's really annoying to have
+>
+ The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It's possible to get the footer on the static index page using
+>
+ It's possible to get the footer on the static index page using
Server Side Includes (SSI). The trick to doing this is making
sure that your web server is set up to allow SSI and specifically,
the #exec directive. You should also rename <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.html</TT
>
to <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>.
</P
><P
-> After you've done all that, you can add the following line to
+> After you've done all that, you can add the following line to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" --></PRE
+CLASS="programlisting"
+>
+<!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
+
+</PRE
></FONT
></TD
></TR
</P
><P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This line will be replaced with the actual HTML for the footer
+> This line will be replaced with the actual HTML for the footer
when the page is requested, so you should put this line where you
want the footer to appear.
</P
></DIV
></P
><P
-> Because this method depends on being able to use a #exec directive,
+> Because this method depends on being able to use a #exec directive,
and most ISP's will not allow that, there is an alternative method.
You could have a small script (such as <TT
-CLASS="FILENAME"
+CLASS="filename"
>api.cgi</TT
>)
that basically looks like:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->#!/usr/bonsaitools/bin/perl -w
+CLASS="programlisting"
+>
+#!/usr/bonsaitools/bin/perl -w
require 'globals.pl';
PutFooter();
} else {
die 'api.cgi was incorrectly called';
-}</PRE
+}
+
+</PRE
></FONT
></TD
></TR
></TABLE
>
and then put this line in <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>.
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><!--#include virtual="api.cgi?sub=PutFooter"--></PRE
+CLASS="programlisting"
+>
+<!--#include virtual="api.cgi?sub=PutFooter"-->
+
+</PRE
></FONT
></TD
></TR
</P
><P
> <DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This still requires being able to use Server Side Includes, if
+> This still requires being able to use Server Side Includes, if
this simply will not work for you, see <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1931"
+NAME="AEN1940"
></A
><B
>A.4.8. </B
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes. Look at <A
+>
+ Yes. Look at <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top"
-> http://bugzilla.mozilla.org/reports.cgi</A
+> http://bugzilla.mozilla.org/reports.cgi</A
> for basic reporting
facilities.
</P
><P
-> For more advanced reporting, I recommend hooking up a professional
+> For more advanced reporting, I recommend hooking up a professional
reporting package, such as Crystal Reports, and use ODBC to access
the MySQL database. You can do a lot through the Query page of
Bugzilla as well, but right now Advanced Reporting is much
interface with the database directly.
</P
><P
-> Advanced Reporting is a Bugzilla 3.X proposed feature.
+> Advanced Reporting is a Bugzilla 3.X proposed feature.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1939"
+NAME="AEN1948"
></A
><B
>A.4.9. </B
-> Is there email notification and if so, what do you see when you get an
+>
+ Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Email notification is user-configurable. The bug id and Topic
+>
+ Email notification is user-configurable. The bug id and Topic
of the bug report accompany each email notification, along with
a list of the changes made.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1944"
+NAME="AEN1953"
></A
><B
>A.4.10. </B
-> Can email notification be set up to send to multiple
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1949"
+NAME="AEN1958"
></A
><B
>A.4.11. </B
-> If there is email notification, do users have to have any particular
+>
+ If there is email notification, do users have to have any particular
type of email application?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla email is sent in plain text, the most compatible mail format
+>
+ Bugzilla email is sent in plain text, the most compatible mail format
on the planet.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you decide to use the bugzilla_email integration features
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1956"
+NAME="AEN1965"
></A
><B
>A.4.12. </B
-> If I just wanted to track certain bugs, as they go through life, can I
+>
+ If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. Place yourself in the "cc" field of the bug you wish to monitor.
+>
+ Yes. Place yourself in the "cc" field of the bug you wish to monitor.
Then change your "Notify me of changes to" field in the Email Settings
tab of the User Preferences screen in Bugzilla to the "Only those
bugs which I am listed on the CC line" option.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1961"
+NAME="AEN1970"
></A
><B
>A.4.13. </B
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Mozilla allows data export through a custom DTD in XML format.
+>
+ Mozilla allows data export through a custom DTD in XML format.
It does not, however, export to specific formats other than the
XML Mozilla DTD. Importing the data into Excel or any other application
is left as an exercise for the reader.
</P
><P
-> If you create import filters to other applications from Mozilla's XML,
+> If you create import filters to other applications from Mozilla's XML,
please submit your modifications for inclusion in future Bugzilla
distributions.
</P
><P
-> As for data import, any application can send data to Bugzilla through
+> As for data import, any application can send data to Bugzilla through
the HTTP protocol, or through Mozilla's XML API. However, it seems
kind of silly to put another front-end in front of Bugzilla;
it makes more sense to create a simplified bug submission form in
<A
HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
TARGET="_top"
-> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1969"
+NAME="AEN1978"
></A
><B
>A.4.14. </B
-> Has anyone converted Bugzilla to another language to be used in other
+>
+ Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Currently, no. Internationalization support for Perl did not
+>
+ Currently, no. Internationalization support for Perl did not
exist in a robust fashion until the recent release of version 5.6.0;
Bugzilla is, and likely will remain (until 3.X) completely
non-localized.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1974"
+NAME="AEN1983"
></A
><B
>A.4.15. </B
-> Can a user create and save reports? Can they do this in Word format?
+>
+ Can a user create and save reports? Can they do this in Word format?
Excel format?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. No. No.
+>
+ Yes. No. No.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1979"
+NAME="AEN1988"
></A
><B
>A.4.16. </B
-> Can a user re-run a report with a new project, same query?
+>
+ Can a user re-run a report with a new project, same query?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1984"
+NAME="AEN1993"
></A
><B
>A.4.17. </B
-> Can a user modify an existing report and then save it into another name?
+>
+ Can a user modify an existing report and then save it into another name?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can save an unlimited number of queries in Bugzilla. You are free
+>
+ You can save an unlimited number of queries in Bugzilla. You are free
to modify them and rename them to your heart's desire.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1989"
+NAME="AEN1998"
></A
><B
>A.4.18. </B
-> Does Bugzilla have the ability to search by word, phrase, compound
+>
+ Does Bugzilla have the ability to search by word, phrase, compound
search?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You have no idea. Bugzilla's query interface, particularly with the
+>
+ You have no idea. Bugzilla's query interface, particularly with the
advanced Boolean operators, is incredibly versatile.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1994"
+NAME="AEN2003"
></A
><B
>A.4.19. </B
-> Can the admin person establish separate group and individual user
+>
+ Can the admin person establish separate group and individual user
privileges?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1999"
+NAME="AEN2008"
></A
><B
>A.4.20. </B
-> Does Bugzilla provide record locking when there is simultaneous access
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla does not lock records. It provides mid-air collision detection,
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2004"
+NAME="AEN2013"
></A
><B
>A.4.21. </B
-> Are there any backup features provided?
+>
+ Are there any backup features provided?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> MySQL, the database back-end for Bugzilla, allows hot-backup of data.
+>
+ 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
+> http://www.mysql.com/doc/B/a/Backup.html</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2010"
+NAME="AEN2019"
></A
><B
>A.4.22. </B
-> Can users be on the system while a backup is in progress?
+>
+ Can users be on the system while a backup is in progress?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. However, commits to the database must wait
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2015"
+NAME="AEN2024"
></A
><B
>A.4.23. </B
-> What type of human resources are needed to be on staff to install and
+>
+ 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
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If Bugzilla is set up correctly from the start, continuing maintenance needs
+>
+ If Bugzilla is set up correctly from the start, continuing maintenance needs
are minimal and can be completed by unskilled labor. Things like rotate
backup tapes and check log files for the word "error".
</P
><P
-> Commercial Bug-tracking software typically costs somewhere upwards
+> 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.
</P
><P
-> As an example, as of this writing I typically charge
+> As an example, as of this writing I typically charge
$115 for the first hour, and $89 each hour thereafter
for consulting work. It takes me three to five hours to make Bugzilla
happy on a Development installation of Linux-Mandrake.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2022"
+NAME="AEN2031"
></A
><B
>A.4.24. </B
-> What time frame are we looking at if we decide to hire people to install
+>
+ 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,
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It all depends on your level of commitment. Someone with much Bugzilla
+>
+ 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2027"
+NAME="AEN2036"
></A
><B
>A.4.25. </B
-> Is there any licensing fee or other fees for using Bugzilla? Any
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> No. MySQL asks, if you find their product valuable, that you purchase
+>
+ 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"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_INSTALL"
+NAME="faq-install"
></A
>5. Bugzilla Installation</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2034"
+NAME="AEN2043"
></A
><B
>A.5.1. </B
-> How do I download and install Bugzilla?
+>
+ How do I download and install Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Check <A
+>
+ Check <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
> for details.
Once you download it, untar it, read the Bugzilla Guide.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2040"
+NAME="AEN2049"
></A
><B
>A.5.2. </B
-> How do I install Bugzilla on Windows NT?
+>
+ How do I install Bugzilla on Windows NT?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Installation on Windows NT has its own section in
+>
+ Installation on Windows NT has its own section in
"The Bugzilla Guide".
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2045"
+NAME="AEN2054"
></A
><B
>A.5.3. </B
-> Is there an easy way to change the Bugzilla cookie name?
+>
+ Is there an easy way to change the Bugzilla cookie name?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> At present, no.
+>
+ At present, no.
</P
></DIV
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_SECURITY"
+NAME="faq-security"
></A
>6. Bugzilla Security</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2052"
+NAME="AEN2061"
></A
><B
>A.6.1. </B
-> How do I completely disable MySQL security if it's giving me problems
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM
+>
+ 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2058"
+NAME="AEN2067"
></A
><B
>A.6.2. </B
-> Are there any security problems with Bugzilla?
+>
+ Are there any security problems with Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The Bugzilla code has not undergone a complete security audit.
+>
+ The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found
in The Bugzilla Guide.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2063"
+NAME="AEN2072"
></A
><B
>A.6.3. </B
-> I've implemented the security fixes mentioned in Chris Yeh's security
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> This is a common problem, related to running out of file descriptors.
+>
+ 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
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_EMAIL"
+NAME="faq-email"
></A
>7. Bugzilla Email</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2070"
+NAME="AEN2079"
></A
><B
>A.7.1. </B
-> I have a user who doesn't want to receive any more email from Bugzilla.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> With the email changes to 2.12, the user should be able to set
+>
+ With the email changes to 2.12, the user should be able to set
this in user email preferences.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2075"
+NAME="AEN2084"
></A
><B
>A.7.2. </B
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Edit the param for the mail text. Replace "To:" with "X-Real-To:",
+>
+ Edit the param for the mail text. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2080"
+NAME="AEN2089"
></A
><B
>A.7.3. </B
-> I want whineatnews.pl to whine at something more, or other than, only new
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+>
+ 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
+> 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.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2086"
+NAME="AEN2095"
></A
><B
>A.7.4. </B
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> You can call bug_email.pl directly from your aliases file, with
+>
+ You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN2090"
+NAME="AEN2099"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
+> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
</P
></BLOCKQUOTE
>
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2093"
+NAME="AEN2102"
></A
><B
>A.7.5. </B
-> How do I set up the email interface to submit/change bugs via email?
+>
+ How do I set up the email interface to submit/change bugs via email?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can find an updated README.mailif file in the contrib/ directory
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2098"
+NAME="AEN2107"
></A
><B
>A.7.6. </B
-> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
+>
+ Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If you are using an alternate Mail Transport Agent (MTA other than
+>
+ If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script 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 Sendmail, try enabling "sendmailnow" in editparams.cgi.
If you are using Postfix, you will also need to enable <SPAN
CLASS="QUOTE"
>"sendmailnow"</SPAN
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2105"
+NAME="AEN2114"
></A
><B
>A.7.7. </B
-> How come email never reaches me from bugzilla changes?
+>
+ How come email never reaches me from bugzilla changes?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Double-check that you have not turned off email in your user preferences.
+>
+ 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
+> 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
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_DB"
+NAME="faq-db"
></A
>8. Bugzilla Database</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2113"
+NAME="AEN2122"
></A
><B
>A.8.1. </B
-> I've heard Bugzilla can be used with Oracle?
+>
+ I've heard Bugzilla can be used with Oracle?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Red Hat Bugzilla, mentioned above, works with Oracle. The current version
+>
+ Red Hat Bugzilla, mentioned above, works with Oracle. The current version
from Mozilla.org does not have this capability. Unfortunately, though
you will sacrifice a lot of the really great features available in
Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2118"
+NAME="AEN2127"
></A
><B
>A.8.2. </B
-> Bugs are missing from queries, but exist in the database (and I can pull
+>
+ Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You've almost certainly enabled the "shadow database", but for some
+>
+ You've almost certainly enabled the "shadow database", but for some
reason it hasn't been updated for all your bugs. This is the database
against which queries are run, so that really complex or slow queries won't
lock up portions of the database for other users. You can turn off the
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2123"
+NAME="AEN2132"
></A
><B
>A.8.3. </B
-> I think my database might be corrupted, or contain invalid entries. What
+>
+ I think my database might be corrupted, or contain invalid entries. What
do I do?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Run the <SPAN
+>
+ Run the <SPAN
CLASS="QUOTE"
>"sanity check"</SPAN
> utility
(<TT
-CLASS="FILENAME"
+CLASS="filename"
>./sanitycheck.cgi</TT
> in the
Bugzilla_home directory) from your web browser to see! If
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2131"
+NAME="AEN2140"
></A
><B
>A.8.4. </B
-> I want to manually edit some entries in my database. How?
+>
+ I want to manually edit some entries in my database. How?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> There is no facility in Bugzilla itself to do this. It's also generally
+>
+ 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 mysqladmin utility to
manually insert, delete, and modify table information. Personally, I
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2136"
+NAME="AEN2145"
></A
><B
>A.8.5. </B
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
+>
+ I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
+>
+ Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
the "crypt()" function. This prevented MySQL from storing encrypted passwords.
Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2141"
+NAME="AEN2150"
></A
><B
>A.8.6. </B
-> I think I've set up MySQL permissions correctly, but bugzilla still can't
+>
+ I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Try running MySQL from its binary: "mysqld --skip-grant-tables". This
+>
+ 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. However, I do not recommend you run it this way on a regular
basis, unless you really want your web site defaced and your machine
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2146"
+NAME="AEN2155"
></A
><B
>A.8.7. </B
-> How do I synchronize bug information among multiple different Bugzilla
+>
+ How do I synchronize bug information among multiple different Bugzilla
databases?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Well, you can synchronize or you can move bugs. Synchronization will
+>
+ 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.
+> 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,
+> 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
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2153"
+NAME="AEN2162"
></A
><B
>A.8.8. </B
-> Why do I get bizarre errors when trying to submit data, particularly problems
+>
+ Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If you're sure your MySQL parameters are correct, you might want turn
+>
+ If you're sure your MySQL parameters are correct, you might want turn
"strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set
"On", you also cannot submit a bug as readable by more than one group with
"strictvaluechecks" ON.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2158"
+NAME="AEN2167"
></A
><B
>A.8.9. </B
-> How come even after I delete bugs, the long descriptions show up?
+>
+ How come even after I delete bugs, the long descriptions show up?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> This should only happen with Bugzilla 2.14 if you are
+>
+ This should only happen with Bugzilla 2.14 if you are
using the <SPAN
CLASS="QUOTE"
>"shadow database"</SPAN
> feature, and your
shadow database is out of sync. Try running
<TT
-CLASS="FILENAME"
+CLASS="filename"
>syncshadowdb</TT
>
<TT
-CLASS="OPTION"
+CLASS="option"
>-syncall</TT
> to make sure your shadow
database is in synch with your primary database.
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_NT"
+NAME="faq-nt"
></A
>9. Bugzilla and Win32</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2168"
+NAME="AEN2177"
></A
><B
>A.9.1. </B
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+>
+ What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Remove Windows. Install Linux. Install Bugzilla.
+>
+ Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2173"
+NAME="AEN2182"
></A
><B
>A.9.2. </B
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
+>
+ Is there a "Bundle::Bugzilla" equivalent for Win32?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2178"
+NAME="AEN2187"
></A
><B
>A.9.3. </B
-> CGI's are failing with a "something.cgi is not a valid Windows NT
+>
+ CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Depending on what Web server you are using, you will have to configure
+>
+ 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:
+> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN2183"
+NAME="AEN2192"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> "Set application mappings. In the ISM, map the extension for the script
+> "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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2186"
+NAME="AEN2195"
></A
><B
>A.9.4. </B
-> Can I have some general instructions on how to make Bugzilla on Win32 work?
+>
+ Can I have some general instructions on how to make Bugzilla on Win32 work?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The following couple entries are deprecated in favor of the Windows installation
+>
+ The following couple entries are deprecated in favor of the Windows installation
instructions available in the "Administration" portion of "The Bugzilla Guide".
However, they are provided here for historical interest and insight.
<P
-CLASS="LITERALLAYOUT"
-> 1. #!C:/perl/bin/perl had to be added to every perl file.<br>
+CLASS="literallayout"
+><br>
+ 1. #!C:/perl/bin/perl had to be added to every perl file.<br>
2. Converted to Net::SMTP to handle mail messages instead of<br>
/usr/bin/sendmail.<br>
3. The crypt function isn't available on Windows NT (at least none that I<br>
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2192"
+NAME="AEN2201"
></A
><B
>A.9.5. </B
-> I'm having trouble with the perl modules for NT not being able to talk to
+>
+ I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Your modules may be outdated or inaccurate. Try:
+>
+ Your modules may be outdated or inaccurate. Try:
<P
></P
><OL
TYPE="1"
><LI
><P
-> Hitting http://www.activestate.com/ActivePerl
+> Hitting http://www.activestate.com/ActivePerl
</P
></LI
><LI
><P
-> Download ActivePerl
+> Download ActivePerl
</P
></LI
><LI
><P
-> Go to your prompt
+> Go to your prompt
</P
></LI
><LI
><P
-> Type 'ppm'
+> Type 'ppm'
</P
></LI
><LI
><P
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="prompt"
>PPM></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>install DBI DBD-mysql GD</B
>
</P
<A
HREF=" http://www.activestate.com/Packages/"
TARGET="_top"
-> http://www.activestate.com/Packages/</A
+> http://www.activestate.com/Packages/</A
>
</P
></DIV
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_USE"
+NAME="faq-use"
></A
>10. Bugzilla Usage</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2213"
+NAME="AEN2222"
></A
><B
>A.10.1. </B
-> The query page is very confusing. Isn't there a simpler way to query?
+>
+ The query page is very confusing. Isn't there a simpler way to query?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> We are developing in that direction. You can follow progress on this
+>
+ We are developing in that direction. You can follow progress on this
at <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"
TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
+> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
>. Some functionality
is available in Bugzilla 2.12, and is available as "quicksearch.html"
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2219"
+NAME="AEN2228"
></A
><B
>A.10.2. </B
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> The current behavior is acceptable to bugzilla.mozilla.org and most
+>
+ The current behavior is acceptable to bugzilla.mozilla.org and most
users. I personally don't like it. You have your choice of patches
to change this behavior, however.
<P
><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
TARGET="_top"
-> Add a "and accept bug" radio button</A
+> Add a "and accept bug" radio button</A
></TD
></TR
><TR
><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
TARGET="_top"
-> "Accept" button automatically assigns to you</A
+> "Accept" button automatically assigns to you</A
></TD
></TR
></TBODY
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2229"
+NAME="AEN2238"
></A
><B
>A.10.3. </B
-> I can't upload anything into the database via the "Create Attachment"
+>
+ I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The most likely cause is a very old browser or a browser that is
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2234"
+NAME="AEN2243"
></A
><B
>A.10.4. </B
-> Email submissions to Bugzilla that have attachments end up asking me to
+>
+ Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yup. Just rename it once you download it, or save it under a different
+>
+ Yup. Just rename it once you download it, or save it under a different
filename. This will not be fixed anytime too soon, because it would
cripple some other functionality.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2239"
+NAME="AEN2248"
></A
><B
>A.10.5. </B
-> How do I change a keyword in Bugzilla, once some bugs are using it?
+>
+ How do I change a keyword in Bugzilla, once some bugs are using it?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> In the Bugzilla administrator UI, edit the keyword and it will let you
+>
+ 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="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_HACKING"
+NAME="faq-hacking"
></A
>11. Bugzilla Hacking</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2246"
+NAME="AEN2255"
></A
><B
>A.11.1. </B
-> What bugs are in Bugzilla right now?
+>
+ What bugs are in Bugzilla right now?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Try <A
+>
+ 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
+> this link</A
> to view current bugs or requests for
enhancement for Bugzilla.
</P
><P
-> You can view bugs marked for 2.16 release
+> You can view bugs marked for 2.16 release
<A
HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16"
TARGET="_top"
<A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> Bugzilla Project Page</A
+> Bugzilla Project Page</A
> for details on how to
check current sources out of CVS so you can have these
bug fixes early!
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2255"
+NAME="AEN2264"
></A
><B
>A.11.2. </B
-> How can I change the default priority to a null value? For instance, have the default
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> This is well-documented here: <A
+>
+ 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
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2261"
+NAME="AEN2270"
></A
><B
>A.11.3. </B
-> What's the best way to submit patches? What guidelines should I follow?
+>
+ What's the best way to submit patches? What guidelines should I follow?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
TYPE="1"
><LI
><P
-> Enter a bug into bugzilla.mozilla.org for the <SPAN
+> Enter a bug into bugzilla.mozilla.org for the <SPAN
CLASS="QUOTE"
>"<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
></LI
><LI
><P
-> Upload your patch as a unified DIFF (having used "diff -u" against
+> Upload your patch as a unified DIFF (having used "diff -u" against
the <EM
>current sources</EM
> checked out of CVS),
></LI
><LI
><P
-> Announce your patch and the associated URL
+> Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
good, fairly immediate reaction to the implications of your patch,
></LI
><LI
><P
-> If it passes muster with minimal modification, the person to whom
+> 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
+> Bask in the glory of the fact that you helped write the most successful
open-source bug-tracking software on the planet :)
</P
></LI
></DIV
></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><HR><H1
><A
-NAME="DOWNLOADLINKS"
+NAME="downloadlinks"
>Appendix B. Software Download Links</A
></H1
><P
-> All of these sites are current as of April, 2001. Hopefully
+> All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
-> Apache Web Server: <A
+>
Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
-> Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
-> MySQL: <A
HREF="http://www.mysql.com/"
TARGET="_top"
>http://www.mysql.com/</A
>
</P
><P
-> Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
-> CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
-> DBI Perl module:
+> DBI Perl module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/"
+HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A
+> http://www.cpan.org/modules/by-module/DBI/</A
>
</P
><P
-> Data::Dumper module:
+> Data::Dumper module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/"
+HREF="http://www.cpan.org/modules/by-module/Data/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A
+> http://www.cpan.org/modules/by-module/Data/</A
>
</P
><P
-> MySQL related Perl modules:
+> MySQL related Perl modules:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/"
+HREF="http://www.cpan.org/modules/by-module/Mysql/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A
+> http://www.cpan.org/modules/by-module/Mysql/</A
>
</P
><P
-> TimeDate Perl module collection:
+> TimeDate Perl module collection:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/"
+HREF="http://www.cpan.org/modules/by-module/Date/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A
+> http://www.cpan.org/modules/by-module/Date/</A
>
</P
><P
-> GD Perl module:
+> GD Perl module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/"
+HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A
+> http://www.cpan.org/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
>
</P
><P
-> Chart::Base module:
+> Chart::Base module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/"
+HREF="http://www.cpan.org/modules/by-module/Chart/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A
+> http://www.cpan.org/modules/by-module/Chart/</A
>
</P
><P
-> LinuxDoc Software:
+> LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
</P
></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><HR><H1
><A
-NAME="DATABASE"
+NAME="database"
>Appendix C. The Bugzilla Database</A
></H1
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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?
+> 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"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DBSCHEMA"
+NAME="dbschema"
>C.1. Database Schema Chart</A
></H1
><P
-> <DIV
-CLASS="MEDIAOBJECT"
+CLASS="mediaobject"
><P
><IMG
SRC="../images/dbschema.jpg"
ALT="Database Relationships"
></IMG
><DIV
-CLASS="CAPTION"
+CLASS="caption"
><P
>Bugzilla database relationships chart</P
></DIV
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DBDOC"
+NAME="dbdoc"
>C.2. MySQL Bugzilla Database Introduction</A
></H1
><P
-> This information comes straight from my life. I was forced to learn how
+> 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
comes.
</P
><P
-> So, here you are with your brand-new installation of Bugzilla. You've got
+> 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
testers.
</P
><P
-> What's the next thing you do? Outline a training strategy for your
+> 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
+> 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
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
+> 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
+> 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,
'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
+> 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...
burbling, and boiling on a hot Jamaican sand dune...
</P
><P
-> Thus begins your adventure into the heart of Bugzilla. You've been forced
+> 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"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2331"
+NAME="AEN2340"
>C.2.1. Bugzilla Database Basics</A
></H2
><P
-> If you were like me, at this point you're totally clueless
+> 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
TYPE="1"
><LI
><P
-> To connect to your database:
+> To connect to your database:
</P
><P
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
>mysql</B
><TT
-CLASS="PARAMETER"
+CLASS="parameter"
><I
>-u root</I
></TT
>
</P
><P
-> If this works without asking you for a password,
+> If this works without asking you for a password,
<EM
>shame on you</EM
>! You should have
this:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
></P
><P
>"bugs"</SPAN
> is the name
you chose in the<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> file
for your Bugzilla database, type:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql</TT
><B
-CLASS="COMMAND"
+CLASS="command"
>use bugs;</B
></P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
>
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2360"
+NAME="AEN2369"
>C.2.1.1. Bugzilla Database Tables</A
></H3
><P
command:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
><B
-CLASS="COMMAND"
+CLASS="command"
>show tables from bugs;</B
></P
><P
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->+-------------------+
+CLASS="programlisting"
+> +-------------------+
| Tables in bugs |
+-------------------+
| attachments |
></TABLE
></P
><P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
><br>
+<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>
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GRANTTABLES"
+NAME="granttables"
>C.3. MySQL Permissions & Grant Tables</A
></H1
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
troubles to work on : ) Although it is of limited use, it
still has SOME use, thus it's still included.</P
><P
-> Please note, however, that I was a relatively new user to
+> Please note, however, that I was a relatively new user to
MySQL at the time. Some of my suggestions, particularly in
how to set up security, showed a terrible lack of
security-related database experience.
></TABLE
></DIV
><P
-CLASS="LITERALLAYOUT"
->From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999<br>
+CLASS="literallayout"
+><br>
+From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999<br>
Date: Mon, 1 Mar 1999 21:37:04 -0700 <br>
From: Matthew Barnson matt_barnson@singletrac.com<br>
To: keystone-users@homeport.org<br>
></DIV
></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><HR><H1
><A
-NAME="PATCHES"
+NAME="patches"
>Appendix D. Useful Patches and Utilities for Bugzilla</A
></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"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="REWRITE"
+NAME="rewrite"
>D.1. Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</A
></H1
><P
>Apache's <TT
-CLASS="FILENAME"
+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
TYPE="1"
><LI
><P
-> Make it so if someone types
+> Make it so if someone types
<TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>http://www.foo.com/12345</TT
>,
Bugzilla spits back
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><VirtualHost 12.34.56.78>
+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
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SETPERL"
+NAME="setperl"
>D.2. The setperl.csh Utility</A
></H1
><P
search path on your system, it will not work!
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Download the "setperl.csh" utility to your Bugzilla
+> Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>cd /your/path/to/bugzilla</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>chmod
u+x setperl.csh</B
> </TT
></LI
><LI
><P
-> Prepare (and fix) Bugzilla file permissions.
+> Prepare (and fix) Bugzilla file permissions.
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod u+w *</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>chmod
u+x duplicates.cgi</B
> </TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod a-x bug_status.html</B
>
</TT
></LI
><LI
><P
-> Run the script:
+> Run the script:
</P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN2439"
+NAME="AEN2448"
></A
><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./setperl.csh /usr/bin/perl</B
>
</TT
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CMDLINE"
+NAME="cmdline"
>D.3. Command-line Bugzilla Queries</A
></H1
><P
-> Users can query Bugzilla from the command line using this suite
+> Users can query Bugzilla from the command line using this suite
of utilities.
</P
><P
-> The query.conf file contains the mapping from options to field
+> The query.conf file 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
-> buglist is a shell script which submits a Bugzilla query and
+> 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
prefixed with "--default=".
</P
><P
-> The columlist is taken from the COLUMNLIST environment variable.
+> The columlist 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, use
<B
-CLASS="COMMAND"
+CLASS="command"
>grep COLUMLIST ~/.netscape/cookies</B
> to see
your current COLUMNLIST setting.
</P
><P
-> bugs is a simple shell script which calls buglist and extracts
+> 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 <B
-CLASS="COMMAND"
+CLASS="command"
>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</B
>
</P
><P
-> Akkana says she has good results piping buglist output through
+> Akkana says she has good results piping buglist output through
<B
-CLASS="COMMAND"
+CLASS="command"
>w3m -T text/html -dump</B
>
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Download three files:
+> Download three files:
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash$</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash$</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
></LI
><LI
><P
-> Make your utilities executable:
+> Make your utilities executable:
<TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash$</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod u+x buglist bugs</B
>
</TT
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="QUICKSEARCH"
+NAME="quicksearch"
>D.4. The Quicksearch Utility</A
></H1
><P
-> Quicksearch is a new, experimental feature of the 2.12 release.
+> Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</P
><P
-> The index.html page has been updated to include the QuickSearch
+> The index.html page has been updated to include the QuickSearch
text box.
</P
><P
-> To take full advantage of the query power, the Bugzilla
+> To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</P
><P
-> Currently, keywords must be hard-coded in localconfig.js. If
+> Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
but not those with the keyword "foo".
</P
><P
-> Workarounds for Bugzilla users:
+> Workarounds for Bugzilla users:
<P
></P
><TABLE
>
</P
><P
-> When this tool is ported from client-side JavaScript to
+> When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BZHACKING"
+NAME="bzhacking"
>D.5. Hacking Bugzilla</A
></H1
><P
-> The following is a guide for reviewers when checking code into Bugzilla's
+> The following is a guide for reviewers when checking code into Bugzilla's
CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,
you should follow the rules and style conventions below. Any code that
does not adhere to these basic rules will not be added to Bugzilla's
codebase.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2495"
+NAME="AEN2504"
>D.5.1. Things that have caused problems and should be avoided</A
></H2
><P
TYPE="1"
><LI
><P
-> Usage of variables in Regular Expressions
+> Usage of variables in Regular Expressions
</P
><P
-> It is very important that you don't use a variable in a regular
+> It is very important that you don't use a variable in a regular
expression unless that variable is supposed to contain an expression.
This especially applies when using grep. You should use:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->grep ($_ eq $value, @array);
+CLASS="programlisting"
+> grep ($_ eq $value, @array);
</PRE
></FONT
></TD
>
</P
><P
-> -- NOT THIS --
+> -- NOT THIS --
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->grep (/$value/, @array);
+CLASS="programlisting"
+> grep (/$value/, @array);
</PRE
></FONT
></TD
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you need to use a non-expression variable inside of an expression, be
+> If you need to use a non-expression variable inside of an expression, be
sure to quote it properly (using <TT
-CLASS="FUNCTION"
+CLASS="function"
>\Q..\E</TT
>).
</P
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><HR><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2509"
+NAME="AEN2518"
>D.5.2. Coding Style for Bugzilla</A
></H2
><P
-> While it's true that not all of the code currently in Bugzilla adheres to
+> While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore,
we ask that all new code (submitted patches and new files) follow this guide
as closely as possible (if you're only changing 1 or 2 lines, you don't have
to reformat the entire file :).
</P
><P
-> The Bugzilla development team has decided to adopt the perl style guide as
+> The Bugzilla development team has decided to adopt the perl style guide as
published by Larry Wall. This giude can be found in <SPAN
CLASS="QUOTE"
>"Programming
Perl"</SPAN
> (the camel book) or by typing <B
-CLASS="COMMAND"
+CLASS="command"
>man perlstyle</B
> at
your favorite shell prompt.
</P
><P
-> What appears below if a brief summary, please refer to the perl style
- guide if you don't see your question covered here.
+> What appears below if a brief summary, please refer to the perl style
+ guide if you don't see your question covered here. It is much better to submit
+ a patch which fails these criteria than no patch at all, but please try to meet
+ these minimum standards when submitting code to Bugzilla.
</P
><P
></P
><UL
><LI
><P
-> Whitespace
+> Whitespace
</P
><P
-> Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+> Bugzilla's prefered indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
><P
-> Curly braces.
+> Curly braces.
</P
><P
-> The opening brace of a block should be on the same line as the statement
+> The opening brace of a block should be on the same line as the statement
that is causing the block and the closing brace should be at the same
indentation level as that statement, for example:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->if ($var) {
+CLASS="programlisting"
+> if ($var) {
print "The variable is true";
}
else {
>
</P
><P
-> -- NOT THIS --
+> -- NOT THIS --
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->if ($var)
+CLASS="programlisting"
+> if ($var)
{
print "The variable is true";
}
></LI
><LI
><P
-> File Names
+> Cookies
+ </P
+><P
+> Bugzilla uses cookies to ease the user experience, but no new patches
+ should <EM
+>require</EM
+> user-side cookies.
+ </P
+></LI
+><LI
+><P
+> File Names
</P
><P
-> File names for bugzilla code and support documention should be legal across
+> File names for bugzilla code and support documention should be legal across
multiple platforms. <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>\ / : * ? " < ></TT
>
and <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>|</TT
> are all illegal characters for filenames
on various platforms. Also, file names should not have spaces in them as they
></LI
><LI
><P
-> Variable Names
+> Javascript dependencies
+ </P
+><P
+> While Bugzilla uses Javascript to make the user experience easier, no patch
+ to Bugzilla should <EM
+>require</EM
+> Javascript.
+ </P
+></LI
+><LI
+><P
+> Patch Format
+ </P
+><P
+> All patches submitted for inclusion into Bugzilla should be in the form of a
+ <SPAN
+CLASS="QUOTE"
+>"unified diff"</SPAN
+>. This comes from using <SPAN
+CLASS="QUOTE"
+>"diff -u"</SPAN
+>
+ instead of simply <SPAN
+CLASS="QUOTE"
+>"diff"</SPAN
+> when creating your patch. This will
+ result in quicker acceptance of the patch.
+ </P
+></LI
+><LI
+><P
+> Schema Changes
+ </P
+><P
+> If you make schema changes, you should modify <TT
+CLASS="filename"
+>sanitycheck.cgi</TT
+>
+ to support the new schema. All referential columns should be checked.
+ </P
+></LI
+><LI
+><P
+> Taint Mode
+ </P
+><P
+> All new cgis must run in Taint mode (Perl taint and DBI taint), and existing cgi's
+ which run in taint mode must not have taint mode turned off.
+ </P
+></LI
+><LI
+><P
+> Templatization
+ </P
+><P
+> Patches to Bugzilla need to support templates so they do not force user interface choices
+ on Bugzilla administrators.
+ </P
+></LI
+><LI
+><P
+> Variable Names
</P
><P
-> If a variable is scoped globally (<TT
-CLASS="COMPUTEROUTPUT"
+> If a variable is scoped globally (<TT
+CLASS="computeroutput"
>$::variable</TT
>)
its name should be descriptive of what it contains. Local variables can be named
a bit looser, provided the context makes their content obvious. For example,
<TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>$ret</TT
> could be used as a staging variable for a
routine's return value as the line <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>return $ret;</TT
>
will make it blatantly obvious what the variable holds and most likely be shown
on the same screen as <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>my $ret = "";</TT
>.
</P
></LI
><LI
><P
-> Cross Database Compatability
+> Cross Database Compatability
</P
><P
-> Bugzilla was originally written to work with MySQL and therefore took advantage
+> Bugzilla was originally written to work with MySQL and therefore took advantage
of some of its features that aren't contained in other RDBMS software. These
should be avoided in all new code. Examples of these features are enums and
<TT
-CLASS="FUNCTION"
+CLASS="function"
>encrypt()</TT
>.
</P
></LI
><LI
><P
-> Cross Platform Compatability
+> Cross Platform Compatability
</P
><P
-> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
+> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
still the only officially supported platform) there are many who desire/need to
run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive
not to make the lives of these people any more complicated and avoid doing things
></DIV
></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><HR><H1
><A
-NAME="GFDL"
+NAME="gfdl"
>Appendix E. GNU Free Documentation License</A
></H1
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2550"
+NAME="AEN2583"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
of this license document, but changing it is not allowed.</P
></BLOCKQUOTE
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_0"
+NAME="gfdl-0"
>0. PREAMBLE</A
></H1
><P
whose purpose is instruction or reference.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_1"
+NAME="gfdl-1"
>1. APPLICABILITY AND DEFINITIONS</A
></H1
><P
text.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_2"
+NAME="gfdl-2"
>2. VERBATIM COPYING</A
></H1
><P
above, and you may publicly display copies.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_3"
+NAME="gfdl-3"
>3. COPYING IN QUANTITY</A
></H1
><P
updated version of the Document.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_4"
+NAME="gfdl-4"
>4. MODIFICATIONS</A
></H1
><P
or to assert or imply endorsement of any Modified Version.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_5"
+NAME="gfdl-5"
>5. COMBINING DOCUMENTS</A
></H1
><P
must delete all sections entitled "Endorsements."</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_6"
+NAME="gfdl-6"
>6. COLLECTIONS OF DOCUMENTS</A
></H1
><P
copying of that document.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_7"
+NAME="gfdl-7"
>7. AGGREGATION WITH INDEPENDENT WORKS</A
></H1
><P
aggregate.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_8"
+NAME="gfdl-8"
>8. TRANSLATION</A
></H1
><P
prevail.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_9"
+NAME="gfdl-9"
>9. TERMINATION</A
></H1
><P
compliance.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_10"
+NAME="gfdl-10"
>10. FUTURE REVISIONS OF THIS LICENSE</A
></H1
><P
Free Software Foundation.</P
></DIV
><DIV
-CLASS="SECT1"
+CLASS="sect1"
><HR><H1
-CLASS="SECT1"
+CLASS="sect1"
><A
-NAME="GFDL_HOWTO"
+NAME="gfdl-howto"
>How to use this License for your documents</A
></H1
><P
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
-NAME="AEN2640"
+NAME="AEN2673"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> Copyright (c) YEAR YOUR NAME.
+> 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
+ Free Documentation License".
+</P
></BLOCKQUOTE
><P
>If you have no Invariant Sections, write "with no Invariant
CLASS="GLOSSARY"
><H1
><A
-NAME="GLOSSARY"
+NAME="glossary"
>Glossary</A
></H1
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="AEN2645"
+NAME="AEN2678"
>0-9, high ascii</A
></H1
><DL
></DT
><DD
><P
-> Apache web server, and other NCSA-compliant web servers,
+> Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files. These
restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> file contains the
password to your database. If this information were
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_A"
+NAME="gloss-a"
>A</A
></H1
><DL
>In this context, Apache is the web server most
commonly used for serving up
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Bugzilla</I
> pages. Contrary to
popular belief, the apache web server has nothing to do
>"a patchy"</SPAN
> version of the original
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>NCSA</SPAN
> world-wide-web server.</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_B"
+NAME="gloss-b"
>B</A
></H1
><DL
></DT
><DD
><P
-> A <SPAN
+> A <SPAN
CLASS="QUOTE"
>"Bug"</SPAN
> in Bugzilla refers to an issue
></DT
><DD
><P
-> Each Bugzilla Bug is assigned a number that uniquely
+> 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.
></DT
><DD
><P
-> Bugzilla is the industry-standard bug tracking system. It
+> Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_C"
+NAME="gloss-c"
></A
></H1
><DL
><DT
><A
-NAME="GLOSS_COMPONENT"
+NAME="gloss-component"
><B
>Component</B
></A
></DT
><DD
><P
-> A Component is a subsection of a Product. It should be a
+> 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
></DD
><DT
><A
-NAME="GLOSS_CPAN"
+NAME="gloss-cpan"
><B
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>CPAN</SPAN
></B
></A
><DD
><P
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>CPAN</SPAN
> stands for the
<SPAN
>. CPAN
maintains a large number of extremely useful
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Perl</I
> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_D"
+NAME="gloss-d"
>D</A
></H1
><DL
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"
+CLASS="glossterm"
>mysqld</I
>, the
MySQL server, and <I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>apache</I
>, a web
server, are generally run as daemons.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_G"
+NAME="gloss-g"
></A
></H1
><DL
comes by lumping users into groups, and assigning those
groups certain privileges to
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Products</I
> and
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Components</I
> in the
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_I"
+NAME="gloss-i"
>I</A
></H1
><DL
><DT
><A
-NAME="GLOSS_INFINITELOOP"
+NAME="gloss-infiniteloop"
><B
>Infinite Loop</B
></A
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_M"
+NAME="gloss-m"
>M</A
></H1
><DL
><P
>mysqld is the name of the
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>daemon</I
> for the MySQL database. In
general, it is invoked automatically through the use of
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_P"
+NAME="gloss-p"
>P</A
></H1
><DL
Security) for all bugs entered into components beneath
it.</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN2736"
+NAME="AEN2769"
></A
><P
><B
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"
+CLASS="glossterm"
>Bugzilla</I
> is
maintained in Perl.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_Q"
+NAME="gloss-q"
>Q</A
></H1
><DL
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_R"
+NAME="gloss-r"
>R</A
></H1
><DL
><DT
><A
-NAME="GLOSS_RECURSION"
+NAME="gloss-recursion"
><B
>Recursion</B
></A
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_S"
+NAME="gloss-s"
>S</A
></H1
><DL
><DT
><B
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
></B
></DT
><DD
><P
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> stands for <SPAN
CLASS="QUOTE"
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> has withstood the test of time as
a robust, powerful language.
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
></I
> is the
>"baby brother"</SPAN
> of SGML; any valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
> document it, by definition, a valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> document. The document you are
reading is written and maintained in
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
>, and is also valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
> if you modify the Document Type
Definition.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_T"
+NAME="gloss-t"
>T</A
></H1
><DL
><DT
><A
-NAME="GLOSS_TARGET_MILESTONE"
+NAME="gloss-target-milestone"
><B
>Target Milestone</B
></A
></DT
><DD
><P
-> Target Milestones are Product goals. They are
+> Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<SPAN
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_Z"
+NAME="gloss-z"
>Z</A
></H1
><DL
><DT
><A
-NAME="ZARRO-BOOGS-FOUND"
+NAME="zarro-boogs-found"
><B
>Zarro Boogs Found</B
></A
TITLE="Purpose and Scope of this Guide"
HREF="aboutthisguide.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="ABOUT"
+NAME="about"
>Chapter 1. About This Guide</A
></H1
><DIV
TITLE="Copyright Information"
HREF="copyright.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ABOUTTHISGUIDE"
+NAME="aboutthisguide"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
-> This document was started on September 17, 2000 by Matthew P.
+> This document was started on September 17, 2000 by Matthew P.
Barnson after a great deal of procrastination updating the
Bugzilla FAQ, which I left untouched for nearly half a year.
After numerous complete rewrites and reformatting, it is the
document you see today.
</P
><P
-> Bugzilla is simply the best piece of bug-tracking software the
+> 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
+> This release of the Bugzilla Guide is the
<EM
>2.14</EM
> release. It is so named that it
developers, and those who enjoy a lot of pain.
</P
><P
-> Newer revisions of the Bugzilla Guide follow the numbering
+> Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<A
HREF="http://www.mozilla.org/projects/bugzilla"
Got it? Good.
</P
><P
-> I wrote this in response to the enormous demand for decent
+> I wrote this in response to the enormous demand for decent
Bugzilla documentation. I have incorporated instructions from
the Bugzilla README, Frequently Asked Questions, Database Schema
Document, and various mailing lists to create it. Chances are,
there are glaring errors in this documentation; please contact
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="ADMINISTRATION"
+NAME="administration"
>Chapter 4. Administering Bugzilla</A
></H1
><DIV
><DL
><DT
>4.2.1. <A
-HREF="useradmin.html#DEFAULTUSER"
+HREF="useradmin.html#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
-HREF="useradmin.html#MANAGEUSERS"
+HREF="useradmin.html#manageusers"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>4.2.2.1. <A
-HREF="useradmin.html#LOGIN"
+HREF="useradmin.html#login"
>Logging In</A
></DT
><DT
>4.2.2.2. <A
-HREF="useradmin.html#CREATENEWUSERS"
+HREF="useradmin.html#createnewusers"
>Creating new users</A
></DT
><DT
>4.2.2.3. <A
-HREF="useradmin.html#DISABLEUSERS"
+HREF="useradmin.html#disableusers"
>Disabling Users</A
></DT
><DT
>4.2.2.4. <A
-HREF="useradmin.html#MODIFYUSERS"
+HREF="useradmin.html#modifyusers"
>Modifying Users</A
></DT
></DL
><DL
><DT
>4.3.1. <A
-HREF="programadmin.html#PRODUCTS"
+HREF="programadmin.html#products"
>Products</A
></DT
><DT
>4.3.2. <A
-HREF="programadmin.html#COMPONENTS"
+HREF="programadmin.html#components"
>Components</A
></DT
><DT
>4.3.3. <A
-HREF="programadmin.html#VERSIONS"
+HREF="programadmin.html#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
-HREF="programadmin.html#MILESTONES"
+HREF="programadmin.html#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
-HREF="programadmin.html#VOTING"
+HREF="programadmin.html#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
-HREF="programadmin.html#GROUPS"
+HREF="programadmin.html#groups"
>Groups and Group Security</A
></DT
></DL
></DIV
><FONT
COLOR="RED"
-> Or, I just got this cool thing installed. Now what the heck do I
+> Or, I just got this cool thing installed. Now what the heck do I
do with it?
</FONT
><P
-> So you followed <SPAN
+> So you followed <SPAN
CLASS="QUOTE"
>"<A
HREF="installation.html"
TITLE="CVS"
HREF="cvs.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BONSAI"
+NAME="bonsai"
>5.1. Bonsai</A
></H1
><P
TITLE="Installation General Notes"
HREF="geninstall.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BSDINSTALL"
+NAME="bsdinstall"
>3.4. BSD Installation Notes</A
></H1
><P
-> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
+> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
consult <A
HREF="osx.html"
>Section 3.3</A
TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BZHACKING"
+NAME="bzhacking"
>D.5. Hacking Bugzilla</A
></H1
><P
-> The following is a guide for reviewers when checking code into Bugzilla's
+> The following is a guide for reviewers when checking code into Bugzilla's
CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,
you should follow the rules and style conventions below. Any code that
does not adhere to these basic rules will not be added to Bugzilla's
codebase.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2495"
+NAME="AEN2504"
>D.5.1. Things that have caused problems and should be avoided</A
></H2
><P
TYPE="1"
><LI
><P
-> Usage of variables in Regular Expressions
+> Usage of variables in Regular Expressions
</P
><P
-> It is very important that you don't use a variable in a regular
+> It is very important that you don't use a variable in a regular
expression unless that variable is supposed to contain an expression.
This especially applies when using grep. You should use:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->grep ($_ eq $value, @array);
+CLASS="programlisting"
+> grep ($_ eq $value, @array);
</PRE
></FONT
></TD
>
</P
><P
-> -- NOT THIS --
+> -- NOT THIS --
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->grep (/$value/, @array);
+CLASS="programlisting"
+> grep (/$value/, @array);
</PRE
></FONT
></TD
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you need to use a non-expression variable inside of an expression, be
+> If you need to use a non-expression variable inside of an expression, be
sure to quote it properly (using <TT
-CLASS="FUNCTION"
+CLASS="function"
>\Q..\E</TT
>).
</P
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2509"
+NAME="AEN2518"
>D.5.2. Coding Style for Bugzilla</A
></H2
><P
-> While it's true that not all of the code currently in Bugzilla adheres to
+> While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore,
we ask that all new code (submitted patches and new files) follow this guide
as closely as possible (if you're only changing 1 or 2 lines, you don't have
to reformat the entire file :).
</P
><P
-> The Bugzilla development team has decided to adopt the perl style guide as
+> The Bugzilla development team has decided to adopt the perl style guide as
published by Larry Wall. This giude can be found in <SPAN
CLASS="QUOTE"
>"Programming
Perl"</SPAN
> (the camel book) or by typing <B
-CLASS="COMMAND"
+CLASS="command"
>man perlstyle</B
> at
your favorite shell prompt.
</P
><P
-> What appears below if a brief summary, please refer to the perl style
- guide if you don't see your question covered here.
+> What appears below if a brief summary, please refer to the perl style
+ guide if you don't see your question covered here. It is much better to submit
+ a patch which fails these criteria than no patch at all, but please try to meet
+ these minimum standards when submitting code to Bugzilla.
</P
><P
></P
><UL
><LI
><P
-> Whitespace
+> Whitespace
</P
><P
-> Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+> Bugzilla's prefered indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
><P
-> Curly braces.
+> Curly braces.
</P
><P
-> The opening brace of a block should be on the same line as the statement
+> The opening brace of a block should be on the same line as the statement
that is causing the block and the closing brace should be at the same
indentation level as that statement, for example:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->if ($var) {
+CLASS="programlisting"
+> if ($var) {
print "The variable is true";
}
else {
>
</P
><P
-> -- NOT THIS --
+> -- NOT THIS --
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->if ($var)
+CLASS="programlisting"
+> if ($var)
{
print "The variable is true";
}
></LI
><LI
><P
-> File Names
+> Cookies
+ </P
+><P
+> Bugzilla uses cookies to ease the user experience, but no new patches
+ should <EM
+>require</EM
+> user-side cookies.
+ </P
+></LI
+><LI
+><P
+> File Names
</P
><P
-> File names for bugzilla code and support documention should be legal across
+> File names for bugzilla code and support documention should be legal across
multiple platforms. <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>\ / : * ? " < ></TT
>
and <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>|</TT
> are all illegal characters for filenames
on various platforms. Also, file names should not have spaces in them as they
></LI
><LI
><P
-> Variable Names
+> Javascript dependencies
+ </P
+><P
+> While Bugzilla uses Javascript to make the user experience easier, no patch
+ to Bugzilla should <EM
+>require</EM
+> Javascript.
+ </P
+></LI
+><LI
+><P
+> Patch Format
+ </P
+><P
+> All patches submitted for inclusion into Bugzilla should be in the form of a
+ <SPAN
+CLASS="QUOTE"
+>"unified diff"</SPAN
+>. This comes from using <SPAN
+CLASS="QUOTE"
+>"diff -u"</SPAN
+>
+ instead of simply <SPAN
+CLASS="QUOTE"
+>"diff"</SPAN
+> when creating your patch. This will
+ result in quicker acceptance of the patch.
+ </P
+></LI
+><LI
+><P
+> Schema Changes
+ </P
+><P
+> If you make schema changes, you should modify <TT
+CLASS="filename"
+>sanitycheck.cgi</TT
+>
+ to support the new schema. All referential columns should be checked.
+ </P
+></LI
+><LI
+><P
+> Taint Mode
+ </P
+><P
+> All new cgis must run in Taint mode (Perl taint and DBI taint), and existing cgi's
+ which run in taint mode must not have taint mode turned off.
+ </P
+></LI
+><LI
+><P
+> Templatization
+ </P
+><P
+> Patches to Bugzilla need to support templates so they do not force user interface choices
+ on Bugzilla administrators.
+ </P
+></LI
+><LI
+><P
+> Variable Names
</P
><P
-> If a variable is scoped globally (<TT
-CLASS="COMPUTEROUTPUT"
+> If a variable is scoped globally (<TT
+CLASS="computeroutput"
>$::variable</TT
>)
its name should be descriptive of what it contains. Local variables can be named
a bit looser, provided the context makes their content obvious. For example,
<TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>$ret</TT
> could be used as a staging variable for a
routine's return value as the line <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>return $ret;</TT
>
will make it blatantly obvious what the variable holds and most likely be shown
on the same screen as <TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>my $ret = "";</TT
>.
</P
></LI
><LI
><P
-> Cross Database Compatability
+> Cross Database Compatability
</P
><P
-> Bugzilla was originally written to work with MySQL and therefore took advantage
+> Bugzilla was originally written to work with MySQL and therefore took advantage
of some of its features that aren't contained in other RDBMS software. These
should be avoided in all new code. Examples of these features are enums and
<TT
-CLASS="FUNCTION"
+CLASS="function"
>encrypt()</TT
>.
</P
></LI
><LI
><P
-> Cross Platform Compatability
+> Cross Platform Compatability
</P
><P
-> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
+> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
still the only officially supported platform) there are many who desire/need to
run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive
not to make the lives of these people any more complicated and avoid doing things
TITLE="The Quicksearch Utility"
HREF="quicksearch.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CMDLINE"
+NAME="cmdline"
>D.3. Command-line Bugzilla Queries</A
></H1
><P
-> Users can query Bugzilla from the command line using this suite
+> Users can query Bugzilla from the command line using this suite
of utilities.
</P
><P
-> The query.conf file contains the mapping from options to field
+> The query.conf file 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
-> buglist is a shell script which submits a Bugzilla query and
+> 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
prefixed with "--default=".
</P
><P
-> The columlist is taken from the COLUMNLIST environment variable.
+> The columlist 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, use
<B
-CLASS="COMMAND"
+CLASS="command"
>grep COLUMLIST ~/.netscape/cookies</B
> to see
your current COLUMNLIST setting.
</P
><P
-> bugs is a simple shell script which calls buglist and extracts
+> 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 <B
-CLASS="COMMAND"
+CLASS="command"
>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</B
>
</P
><P
-> Akkana says she has good results piping buglist output through
+> Akkana says she has good results piping buglist output through
<B
-CLASS="COMMAND"
+CLASS="command"
>w3m -T text/html -dump</B
>
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Download three files:
+> Download three files:
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash$</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash$</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
></LI
><LI
><P
-> Make your utilities executable:
+> Make your utilities executable:
<TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash$</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod u+x buglist bugs</B
>
</TT
TITLE="Feedback"
HREF="feedback.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONTRIBUTORS"
+NAME="contributors"
>1.6. Contributors</A
></H1
><P
-> Thanks go to these people for significant contributions to this
+> Thanks go to these people for significant contributions to this
documentation (in no particular order):
</P
><P
-> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONVENTIONS"
+NAME="conventions"
>1.9. Document Conventions</A
></H1
><P
-> This document uses the following conventions
+> This document uses the following conventions
</P
><DIV
-CLASS="INFORMALTABLE"
+CLASS="informaltable"
><A
NAME="AEN129"
></A
><TR
><TH
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Descriptions</TH
><TH
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Appearance</TH
></TR
></THEAD
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Warnings</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="CAUTION"
+CLASS="caution"
><P
></P
><TABLE
-CLASS="CAUTION"
+CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Hint</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Notes</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Information requiring special attention</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>File Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>file.extension</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Directory Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>directory</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Commands to be typed</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><B
-CLASS="COMMAND"
+CLASS="command"
>command</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Applications Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><SPAN
-CLASS="APPLICATION"
+CLASS="application"
>application</SPAN
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of users command under bash shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>bash$</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of root users command under bash shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>bash#</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><I
-CLASS="FOREIGNPHRASE"
+CLASS="foreignphrase"
>Prompt</I
> of user command under tcsh shell</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>tcsh$</TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Environment Variables</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TT
-CLASS="ENVAR"
+CLASS="envar"
>VARIABLE</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Emphasized word</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><EM
>word</EM
></TD
><TR
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
+VALIGN="MIDDLE"
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
><TT
-CLASS="SGMLTAG"
+CLASS="sgmltag"
><para></TT
>Beginning and end of paragraph<TT
-CLASS="SGMLTAG"
+CLASS="sgmltag"
></para></TT
></PRE
></FONT
TITLE="Disclaimer"
HREF="disclaimer.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="COPYRIGHT"
+NAME="copyright"
>1.2. Copyright Information</A
></H1
><A
WIDTH="80%"
VALIGN="TOP"
><P
-> Permission is granted to copy, distribute and/or modify this
+> 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
ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
-CLASS="ATTRIBUTION"
+CLASS="attribution"
>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
></TD
><TD
></TR
></TABLE
><P
-> If you have any questions regarding this document, its
+> If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
please contact Matthew P. Barnson.
</P
TITLE="Contributors"
HREF="contributors.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CREDITS"
+NAME="credits"
>1.5. Credits</A
></H1
><P
-> The people listed below have made enormous contributions to the
+> The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</P
><P
-> <A
HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
README upon which the UNIX installation documentation is largely based.
</P
><P
-> <A
HREF="mailto://tara@tequilarista.org"
TARGET="_top"
>Tara
strong after Terry left Mozilla.org
</P
><P
-> <A
HREF="mailto://dkl@redhat.com"
TARGET="_top"
>Dave Lawrence</A
Hat Bugzilla" appendix
</P
><P
-> <A
HREF="mailto://endico@mozilla.org"
TARGET="_top"
>Dawn Endico</A
questions and arguments on irc.mozilla.org in #mozwebtools
</P
><P
-> Last but not least, all the members of the <A
+>
Last but not least, all the members of the <A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
TARGET="_top"
> netscape.public.mozilla.webtools</A
TITLE="Perforce SCM"
HREF="scm.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CVS"
+NAME="cvs"
>5.2. CVS</A
></H1
><P
certain that Bugzilla is not tied into one particular software
management package.</P
><P
-> Follow the instructions in the FAQ for enabling Bugzilla e-mail
+> Follow the instructions in the FAQ 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"
state.
</P
><P
-> There is also a project, based upon somewhat dated Bugzilla
+> There is also a 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
+> http://homepages.kcbbs.gen.nz/~tonyg/</A
>, under the
<SPAN
CLASS="QUOTE"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
><BODY
-CLASS="APPENDIX"
+CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><H1
><A
-NAME="DATABASE"
+NAME="database"
>Appendix C. The Bugzilla Database</A
></H1
><DIV
></DL
></DIV
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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?
+> 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
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DBDOC"
+NAME="dbdoc"
>C.2. MySQL Bugzilla Database Introduction</A
></H1
><P
-> This information comes straight from my life. I was forced to learn how
+> 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
comes.
</P
><P
-> So, here you are with your brand-new installation of Bugzilla. You've got
+> 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
testers.
</P
><P
-> What's the next thing you do? Outline a training strategy for your
+> 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
+> 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
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
+> 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
+> 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,
'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
+> 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...
burbling, and boiling on a hot Jamaican sand dune...
</P
><P
-> Thus begins your adventure into the heart of Bugzilla. You've been forced
+> 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"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2331"
+NAME="AEN2340"
>C.2.1. Bugzilla Database Basics</A
></H2
><P
-> If you were like me, at this point you're totally clueless
+> 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
TYPE="1"
><LI
><P
-> To connect to your database:
+> To connect to your database:
</P
><P
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
>mysql</B
><TT
-CLASS="PARAMETER"
+CLASS="parameter"
><I
>-u root</I
></TT
>
</P
><P
-> If this works without asking you for a password,
+> If this works without asking you for a password,
<EM
>shame on you</EM
>! You should have
this:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
></P
><P
>"bugs"</SPAN
> is the name
you chose in the<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> file
for your Bugzilla database, type:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql</TT
><B
-CLASS="COMMAND"
+CLASS="command"
>use bugs;</B
></P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
>
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="AEN2360"
+NAME="AEN2369"
>C.2.1.1. Bugzilla Database Tables</A
></H3
><P
command:</P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
><B
-CLASS="COMMAND"
+CLASS="command"
>show tables from bugs;</B
></P
><P
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->+-------------------+
+CLASS="programlisting"
+> +-------------------+
| Tables in bugs |
+-------------------+
| attachments |
></TABLE
></P
><P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
><br>
+<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>
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DBSCHEMA"
+NAME="dbschema"
>C.1. Database Schema Chart</A
></H1
><P
-> <DIV
-CLASS="MEDIAOBJECT"
+CLASS="mediaobject"
><P
><IMG
SRC="../images/dbschema.jpg"
ALT="Database Relationships"
></IMG
><DIV
-CLASS="CAPTION"
+CLASS="caption"
><P
>Bugzilla database relationships chart</P
></DIV
TITLE="New Versions"
HREF="newversions.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DISCLAIMER"
+NAME="disclaimer"
>1.3. Disclaimer</A
></H1
><P
-> No liability for the contents of this document can be accepted.
+> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
and inaccuracies that may damage your system. Use of this
war. Proceed with caution.
</P
><P
-> All copyrights are held by their respective owners, unless
+> 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
+> Naming of particular products or brands should not be seen as
endorsements, with the exception of the term "GNU/Linux". I
wholeheartedly endorse the use of GNU/Linux in every situation
where it is appropriate. It is an extremely versatile, stable,
environment for Bugzilla.
</P
><P
-> You are strongly recommended to make a backup of your system
+> You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
Heaven knows it's saved my bacon time after time; if you
implement any suggestion in this Guide, implement this one!
</P
><P
-> Although the Bugzilla development team has taken great care to
+> 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
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
><BODY
-CLASS="APPENDIX"
+CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><H1
><A
-NAME="DOWNLOADLINKS"
+NAME="downloadlinks"
>Appendix B. Software Download Links</A
></H1
><P
-> All of these sites are current as of April, 2001. Hopefully
+> All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
-> Apache Web Server: <A
+>
Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
-> Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
-> MySQL: <A
HREF="http://www.mysql.com/"
TARGET="_top"
>http://www.mysql.com/</A
>
</P
><P
-> Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
-> CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
-> DBI Perl module:
+> DBI Perl module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/"
+HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A
+> http://www.cpan.org/modules/by-module/DBI/</A
>
</P
><P
-> Data::Dumper module:
+> Data::Dumper module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/"
+HREF="http://www.cpan.org/modules/by-module/Data/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A
+> http://www.cpan.org/modules/by-module/Data/</A
>
</P
><P
-> MySQL related Perl modules:
+> MySQL related Perl modules:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/"
+HREF="http://www.cpan.org/modules/by-module/Mysql/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A
+> http://www.cpan.org/modules/by-module/Mysql/</A
>
</P
><P
-> TimeDate Perl module collection:
+> TimeDate Perl module collection:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/"
+HREF="http://www.cpan.org/modules/by-module/Date/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A
+> http://www.cpan.org/modules/by-module/Date/</A
>
</P
><P
-> GD Perl module:
+> GD Perl module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/"
+HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A
+> http://www.cpan.org/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
>
</P
><P
-> Chart::Base module:
+> Chart::Base module:
<A
-HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/"
+HREF="http://www.cpan.org/modules/by-module/Chart/"
TARGET="_top"
-> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A
+> http://www.cpan.org/modules/by-module/Chart/</A
>
</P
><P
-> LinuxDoc Software:
+> LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
TITLE="Step-by-step Install"
HREF="stepbystep.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ERRATA"
+NAME="errata"
>3.1. ERRATA</A
></H1
><P
><TBODY
><TR
><TD
-> If you are installing Bugzilla on S.u.S.e. Linux, or some
+> If you are installing Bugzilla on S.u.S.e. 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: <SPAN
-CLASS="ERRORNAME"
+CLASS="errorname"
>cannot chdir(/var/spool/mqueue):
Permission denied</SPAN
> This is because your
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/var/spool/mqueue</TT
> directory has a mode of
<SPAN
CLASS="QUOTE"
>"drwx------"</SPAN
>. Type <B
-CLASS="COMMAND"
+CLASS="command"
>chmod 755
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/var/spool/mqueue</TT
></B
> as root to
></TR
><TR
><TD
-> Bugzilla may be installed on Macintosh OS X (10), which is a
+> Bugzilla may be installed on Macintosh OS X (10), which is a
unix-based (BSD) operating system. Everything required for
Bugzilla on OS X will install cleanly, but the optional GD
perl module which is used for bug charting requires some
></TR
><TR
><TD
-> Release Notes for Bugzilla 2.14 are available at
+> Release Notes for Bugzilla 2.14 are available at
<TT
-CLASS="FILENAME"
+CLASS="filename"
>docs/rel_notes.txt</TT
> in your Bugzilla
source distribution.
></TR
><TR
><TD
-> The preferred documentation for Bugzilla is available in
+> The preferred documentation for Bugzilla is available in
docs/, with a variety of document types available. Please
refer to these documents when installing, configuring, and
maintaining your Bugzilla installation.
><P
></P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla is not a package where you can just plop it in a directory,
+> Bugzilla is not a package where you can just plop it in a directory,
twiddle a few things, and you're off. Installing Bugzilla assumes you
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
></TABLE
></DIV
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla has not undergone a complete security review. Security holes
+> Bugzilla has not undergone a complete security review. Security holes
may exist in the code. 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.
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="SourceForge"
-HREF="variant_sourceforge.html"><LINK
+HREF="variant-sourceforge.html"><LINK
REL="NEXT"
TITLE="Software Download Links"
HREF="downloadlinks.html"></HEAD
><BODY
-CLASS="APPENDIX"
+CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="variant_sourceforge.html"
+HREF="variant-sourceforge.html"
>Prev</A
></TD
><TD
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><H1
><A
-NAME="FAQ"
+NAME="faq"
>Appendix A. The Bugzilla FAQ</A
></H1
><DIV
-CLASS="QANDASET"
+CLASS="qandaset"
><DL
><DT
>1. <A
-HREF="faq.html#FAQ_GENERAL"
+HREF="faq.html#faq-general"
>General Questions</A
></DT
><DD
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1713"
-> Where can I find information about Bugzilla?</A
+HREF="faq.html#AEN1722"
+> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1719"
-> What license is Bugzilla distributed under?
+HREF="faq.html#AEN1728"
+> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1725"
-> How do I get commercial support for Bugzilla?
+HREF="faq.html#AEN1734"
+> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1732"
-> What major companies or projects are currently using Bugzilla
+HREF="faq.html#AEN1741"
+> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1757"
-> Who maintains Bugzilla?
+HREF="faq.html#AEN1766"
+> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1763"
-> How does Bugzilla stack up against other bug-tracking databases?
+HREF="faq.html#AEN1772"
+> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1770"
-> How do I change my user name in Bugzilla?
+HREF="faq.html#AEN1779"
+> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1775"
-> Why doesn't Bugzilla offer this or that feature or compatability
+HREF="faq.html#AEN1784"
+> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1782"
-> Why MySQL? I'm interested in seeing Bugzilla run on
+HREF="faq.html#AEN1791"
+> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1800"
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
+HREF="faq.html#AEN1809"
+> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
></DD
><DT
>2. <A
-HREF="faq.html#FAQ_REDHAT"
+HREF="faq.html#faq-redhat"
>Red Hat Bugzilla</A
></DT
><DD
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1817"
-> What about Red Hat Bugzilla?
+HREF="faq.html#AEN1826"
+> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
-HREF="faq.html#AEN1825"
-> What are the primary benefits of Red Hat Bugzilla?
+HREF="faq.html#AEN1834"
+> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1853"
-> What's the current status of Red Hat Bugzilla?
+HREF="faq.html#AEN1862"
+> What's the current status of Red Hat Bugzilla?
</A
></DT
></DL
></DD
><DT
>3. <A
-HREF="faq.html#FAQ_LOKI"
+HREF="faq.html#faq-loki"
>Loki Bugzilla (AKA Fenris)</A
></DT
><DD
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1866"
-> What is Loki Bugzilla (Fenris)?
+HREF="faq.html#AEN1875"
+> What is Loki Bugzilla (Fenris)?
</A
></DT
></DL
></DD
><DT
>4. <A
-HREF="faq.html#FAQ_PHB"
+HREF="faq.html#faq-phb"
>Pointy-Haired-Boss Questions</A
></DT
><DD
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1877"
-> Is Bugzilla web-based or do you have to have specific software or
+HREF="faq.html#AEN1886"
+> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
-HREF="faq.html#AEN1882"
-> Has anyone you know of already done any Bugzilla integration with
+HREF="faq.html#AEN1891"
+> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
-HREF="faq.html#AEN1887"
-> Does Bugzilla allow the user to track multiple projects?
+HREF="faq.html#AEN1896"
+> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1892"
-> If I am on many projects, and search for all bugs assigned to me, will
+HREF="faq.html#AEN1901"
+> 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.4.5. <A
-HREF="faq.html#AEN1897"
-> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
+HREF="faq.html#AEN1906"
+> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1902"
-> Does Bugzilla allow us to define our own priorities and levels? Do we
+HREF="faq.html#AEN1911"
+> 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.4.7. <A
-HREF="faq.html#AEN1909"
-> The index.html page doesn't show the footer. It's really annoying to have
+HREF="faq.html#AEN1918"
+> The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages?
</A
></DT
><DT
>A.4.8. <A
-HREF="faq.html#AEN1931"
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+HREF="faq.html#AEN1940"
+> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.4.9. <A
-HREF="faq.html#AEN1939"
-> Is there email notification and if so, what do you see when you get an
+HREF="faq.html#AEN1948"
+> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</A
></DT
><DT
>A.4.10. <A
-HREF="faq.html#AEN1944"
-> Can email notification be set up to send to multiple
+HREF="faq.html#AEN1953"
+> 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.4.11. <A
-HREF="faq.html#AEN1949"
-> If there is email notification, do users have to have any particular
+HREF="faq.html#AEN1958"
+> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
>A.4.12. <A
-HREF="faq.html#AEN1956"
-> If I just wanted to track certain bugs, as they go through life, can I
+HREF="faq.html#AEN1965"
+> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</A
></DT
><DT
>A.4.13. <A
-HREF="faq.html#AEN1961"
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
+HREF="faq.html#AEN1970"
+> 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?
></DT
><DT
>A.4.14. <A
-HREF="faq.html#AEN1969"
-> Has anyone converted Bugzilla to another language to be used in other
+HREF="faq.html#AEN1978"
+> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
-HREF="faq.html#AEN1974"
-> Can a user create and save reports? Can they do this in Word format?
+HREF="faq.html#AEN1983"
+> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
-HREF="faq.html#AEN1979"
-> Can a user re-run a report with a new project, same query?
+HREF="faq.html#AEN1988"
+> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
-HREF="faq.html#AEN1984"
-> Can a user modify an existing report and then save it into another name?
+HREF="faq.html#AEN1993"
+> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
-HREF="faq.html#AEN1989"
-> Does Bugzilla have the ability to search by word, phrase, compound
+HREF="faq.html#AEN1998"
+> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
-HREF="faq.html#AEN1994"
-> Can the admin person establish separate group and individual user
+HREF="faq.html#AEN2003"
+> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
-HREF="faq.html#AEN1999"
-> Does Bugzilla provide record locking when there is simultaneous access
+HREF="faq.html#AEN2008"
+> 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.4.21. <A
-HREF="faq.html#AEN2004"
-> Are there any backup features provided?
+HREF="faq.html#AEN2013"
+> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
-HREF="faq.html#AEN2010"
-> Can users be on the system while a backup is in progress?
+HREF="faq.html#AEN2019"
+> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
-HREF="faq.html#AEN2015"
-> What type of human resources are needed to be on staff to install and
+HREF="faq.html#AEN2024"
+> 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
></DT
><DT
>A.4.24. <A
-HREF="faq.html#AEN2022"
-> What time frame are we looking at if we decide to hire people to install
+HREF="faq.html#AEN2031"
+> 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,
></DT
><DT
>A.4.25. <A
-HREF="faq.html#AEN2027"
-> Is there any licensing fee or other fees for using Bugzilla? Any
+HREF="faq.html#AEN2036"
+> 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
></DD
><DT
>5. <A
-HREF="faq.html#FAQ_INSTALL"
+HREF="faq.html#faq-install"
>Bugzilla Installation</A
></DT
><DD
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN2034"
-> How do I download and install Bugzilla?
+HREF="faq.html#AEN2043"
+> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN2040"
-> How do I install Bugzilla on Windows NT?
+HREF="faq.html#AEN2049"
+> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN2045"
-> Is there an easy way to change the Bugzilla cookie name?
+HREF="faq.html#AEN2054"
+> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
></DL
></DD
><DT
>6. <A
-HREF="faq.html#FAQ_SECURITY"
+HREF="faq.html#faq-security"
>Bugzilla Security</A
></DT
><DD
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN2052"
-> How do I completely disable MySQL security if it's giving me problems
+HREF="faq.html#AEN2061"
+> 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.6.2. <A
-HREF="faq.html#AEN2058"
-> Are there any security problems with Bugzilla?
+HREF="faq.html#AEN2067"
+> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN2063"
-> I've implemented the security fixes mentioned in Chris Yeh's security
+HREF="faq.html#AEN2072"
+> 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
></DD
><DT
>7. <A
-HREF="faq.html#FAQ_EMAIL"
+HREF="faq.html#faq-email"
>Bugzilla Email</A
></DT
><DD
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN2070"
-> I have a user who doesn't want to receive any more email from Bugzilla.
+HREF="faq.html#AEN2079"
+> 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.7.2. <A
-HREF="faq.html#AEN2075"
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
+HREF="faq.html#AEN2084"
+> 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.7.3. <A
-HREF="faq.html#AEN2080"
-> I want whineatnews.pl to whine at something more, or other than, only new
+HREF="faq.html#AEN2089"
+> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
-HREF="faq.html#AEN2086"
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
+HREF="faq.html#AEN2095"
+> 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.7.5. <A
-HREF="faq.html#AEN2093"
-> How do I set up the email interface to submit/change bugs via email?
+HREF="faq.html#AEN2102"
+> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
-HREF="faq.html#AEN2098"
-> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
+HREF="faq.html#AEN2107"
+> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
-HREF="faq.html#AEN2105"
-> How come email never reaches me from bugzilla changes?
+HREF="faq.html#AEN2114"
+> How come email never reaches me from bugzilla changes?
</A
></DT
></DL
></DD
><DT
>8. <A
-HREF="faq.html#FAQ_DB"
+HREF="faq.html#faq-db"
>Bugzilla Database</A
></DT
><DD
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN2113"
-> I've heard Bugzilla can be used with Oracle?
+HREF="faq.html#AEN2122"
+> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN2118"
-> Bugs are missing from queries, but exist in the database (and I can pull
+HREF="faq.html#AEN2127"
+> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN2123"
-> I think my database might be corrupted, or contain invalid entries. What
+HREF="faq.html#AEN2132"
+> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
-HREF="faq.html#AEN2131"
-> I want to manually edit some entries in my database. How?
+HREF="faq.html#AEN2140"
+> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
-HREF="faq.html#AEN2136"
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
+HREF="faq.html#AEN2145"
+> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
-HREF="faq.html#AEN2141"
-> I think I've set up MySQL permissions correctly, but bugzilla still can't
+HREF="faq.html#AEN2150"
+> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
-HREF="faq.html#AEN2146"
-> How do I synchronize bug information among multiple different Bugzilla
+HREF="faq.html#AEN2155"
+> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
-HREF="faq.html#AEN2153"
-> Why do I get bizarre errors when trying to submit data, particularly problems
+HREF="faq.html#AEN2162"
+> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
-HREF="faq.html#AEN2158"
-> How come even after I delete bugs, the long descriptions show up?
+HREF="faq.html#AEN2167"
+> How come even after I delete bugs, the long descriptions show up?
</A
></DT
></DL
></DD
><DT
>9. <A
-HREF="faq.html#FAQ_NT"
+HREF="faq.html#faq-nt"
>Bugzilla and Win32</A
></DT
><DD
><DL
><DT
>A.9.1. <A
-HREF="faq.html#AEN2168"
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+HREF="faq.html#AEN2177"
+> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
-HREF="faq.html#AEN2173"
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
+HREF="faq.html#AEN2182"
+> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
-HREF="faq.html#AEN2178"
-> CGI's are failing with a "something.cgi is not a valid Windows NT
+HREF="faq.html#AEN2187"
+> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
-HREF="faq.html#AEN2186"
-> Can I have some general instructions on how to make Bugzilla on Win32 work?
+HREF="faq.html#AEN2195"
+> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
-HREF="faq.html#AEN2192"
-> I'm having trouble with the perl modules for NT not being able to talk to
+HREF="faq.html#AEN2201"
+> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
></DT
></DD
><DT
>10. <A
-HREF="faq.html#FAQ_USE"
+HREF="faq.html#faq-use"
>Bugzilla Usage</A
></DT
><DD
><DL
><DT
>A.10.1. <A
-HREF="faq.html#AEN2213"
-> The query page is very confusing. Isn't there a simpler way to query?
+HREF="faq.html#AEN2222"
+> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
-HREF="faq.html#AEN2219"
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
+HREF="faq.html#AEN2228"
+> 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.10.3. <A
-HREF="faq.html#AEN2229"
-> I can't upload anything into the database via the "Create Attachment"
+HREF="faq.html#AEN2238"
+> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
-HREF="faq.html#AEN2234"
-> Email submissions to Bugzilla that have attachments end up asking me to
+HREF="faq.html#AEN2243"
+> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
-HREF="faq.html#AEN2239"
-> How do I change a keyword in Bugzilla, once some bugs are using it?
+HREF="faq.html#AEN2248"
+> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
></DL
></DD
><DT
>11. <A
-HREF="faq.html#FAQ_HACKING"
+HREF="faq.html#faq-hacking"
>Bugzilla Hacking</A
></DT
><DD
><DL
><DT
>A.11.1. <A
-HREF="faq.html#AEN2246"
-> What bugs are in Bugzilla right now?
+HREF="faq.html#AEN2255"
+> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
-HREF="faq.html#AEN2255"
-> How can I change the default priority to a null value? For instance, have the default
+HREF="faq.html#AEN2264"
+> 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.11.3. <A
-HREF="faq.html#AEN2261"
-> What's the best way to submit patches? What guidelines should I follow?
+HREF="faq.html#AEN2270"
+> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
></DL
></DD
></DL
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_GENERAL"
+NAME="faq-general"
></A
>1. General Questions</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1713"
+NAME="AEN1722"
></A
><B
>A.1.1. </B
-> Where can I find information about Bugzilla?</P
+>
+ Where can I find information about Bugzilla?</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can stay up-to-date with the latest Bugzilla
+>
+ You can stay up-to-date with the latest Bugzilla
information at <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1719"
+NAME="AEN1728"
></A
><B
>A.1.2. </B
-> What license is Bugzilla distributed under?
+>
+ What license is Bugzilla distributed under?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla is covered by the Mozilla Public License.
+>
+ 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
+> http://www.mozilla.org/MPL/</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1725"
+NAME="AEN1734"
></A
><B
>A.1.3. </B
-> How do I get commercial support for Bugzilla?
+>
+ How do I get commercial support for Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <A
+>
+ <A
HREF="http://www.collab.net/"
TARGET="_top"
>www.collab.net</A
aren't interested in small projects.
</P
><P
-> There are several experienced
+> There are several experienced
Bugzilla hackers on the mailing list/newsgroup who are willing
to whore themselves out for generous compensation.
Try sending a message to the mailing list asking for a volunteer.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1732"
+NAME="AEN1741"
></A
><B
>A.1.4. </B
-> What major companies or projects are currently using Bugzilla
+>
+ What major companies or projects are currently using Bugzilla
for bug-tracking?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> There are <EM
+>
+ There are <EM
>dozens</EM
> of major comapanies with public
Bugzilla sites to track bugs in their products. A few include:
>
</P
><P
-> Suffice to say, there are more than enough huge projects using Bugzilla
+> 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1757"
+NAME="AEN1766"
></A
><B
>A.1.5. </B
-> Who maintains Bugzilla?
+>
+ Who maintains Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla maintenance has been in a state of flux recently.
+>
+ Bugzilla maintenance has been in a state of flux recently.
Please check <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1763"
+NAME="AEN1772"
></A
><B
>A.1.6. </B
-> How does Bugzilla stack up against other bug-tracking databases?
+>
+ How does Bugzilla stack up against other bug-tracking databases?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> A year has gone by, and I <EM
+>
+ A year has gone by, and I <EM
>still</EM
> can't
find any head-to-head comparisons of Bugzilla against
flexibility, and superior ease-of-use.
</P
><P
-> If you happen to be a commercial bug-tracker vendor, please
+> If you happen to be a commercial bug-tracker vendor, please
step forward with a rebuttal so I can include it in the
FAQ. We're not in pursuit of Bugzilla ueber alles; we
simply love having a powerful, open-source tool to get our
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1770"
+NAME="AEN1779"
></A
><B
>A.1.7. </B
-> How do I change my user name in Bugzilla?
+>
+ How do I change my user name in Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can't. However, the administrative account can, by simply opening
+>
+ You can't. However, the administrative account can, by simply opening
your user account in editusers.cgi and changing the login name.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1775"
+NAME="AEN1784"
></A
><B
>A.1.8. </B
-> Why doesn't Bugzilla offer this or that feature or compatability
+>
+ Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It may be that the support has not been built yet, or that you
+>
+ 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!
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1782"
+NAME="AEN1791"
></A
><B
>A.1.9. </B
-> Why MySQL? I'm interested in seeing Bugzilla run on
+>
+ Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
>Terry Weissman answers,
<A
-NAME="AEN1786"
+NAME="AEN1795"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> You're not the only one. But <EM
+> You're not the only one. But <EM
>I</EM
> am not very interested. I'm not
a real SQL or database person. I just wanted to make a useful tool,
>
</P
><P
-> Things aren't quite that grim these days, however. Terry pretty much
+> Things aren't quite that grim these days, however. Terry pretty much
sums up much of the thinking many of us have for Bugzilla, but there
is light on the horizon for database-independence! Here are some options:
</P
><TBODY
><TR
><TD
-> <EM
+> <EM
><A
HREF="http://bugzilla.redhat.com/"
TARGET="_top"
></TR
><TR
><TD
-> <EM
+> <EM
><A
HREF="http://sourceforge.net/projects/interzilla"
TARGET="_top"
></TR
><TR
><TD
-> <EM
+> <EM
>Bugzilla 3.0</EM
>: One of the primary stated goals
is multiple database support.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1800"
+NAME="AEN1809"
></A
><B
>A.1.10. </B
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
+>
+ Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
+>
+ Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
submissions is "don't break bugzilla.mozilla.org". If it breaks it, your
patch will be reverted faster than you can do a diff.
</P
><P
-> Here's Terry Weissman's comment, for some historical context:
+> Here's Terry Weissman's comment, for some historical context:
<A
-NAME="AEN1805"
+NAME="AEN1814"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> [This was] purely my own convention. I wanted a place to put a version of
+> [This was] purely my own convention. I wanted a place to put a version of
Perl and other tools that was strictly under my control for the
various webtools, and not subject to anyone else. Edit it to point
to whatever you like.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> We always recommend that, if possible, you keep the path
+> We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
of perl to /usr/bonsaitools/bin/perl. This will make upgrading
your Bugzilla much easier in the future.
</P
><P
-> Obviously, if you do not have root access to your Bugzilla
+> Obviously, if you do not have root access to your Bugzilla
box, our suggestion is irrelevant.
</P
></TD
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_REDHAT"
+NAME="faq-redhat"
></A
>2. Red Hat Bugzilla</H3
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <EM
+> <EM
>This section is no longer up-to-date.</EM
>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
>
</P
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1817"
+NAME="AEN1826"
></A
><B
>A.2.1. </B
-> What about Red Hat Bugzilla?
+>
+ What about Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
+>
+ Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
than stock Bugzilla. Check it out at
http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/.
They've set their Bugzilla up to work with Oracle out of the box.
yourself?
</P
><P
-> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
+> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
-NAME="AEN1822"
+NAME="AEN1831"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> Somebody needs to take the ball and run with it. I'm the only
+> Somebody needs to take the ball and run with it. I'm the only
maintainer and am very pressed for time.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1825"
+NAME="AEN1834"
></A
><B
>A.2.2. </B
-> What are the primary benefits of Red Hat Bugzilla?
+>
+ What are the primary benefits of Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <EM
+>
+ <EM
>Dave Lawrence</EM
>:
<A
-NAME="AEN1830"
+NAME="AEN1839"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> For the record, we are not using any template type implementation for
+> For the record, we are not using any template type implementation for
the cosmetic changes maded to Bugzilla. It is just alot of html changes
in the code itself. I admit I may have gotten a little carried away with it
but the corporate types asked for a more standardized interface to match up
internal tools I am working on also look like Bugzilla.
</P
><P
-> I do want to land the changes that I have made to Bugzilla but I may
+> I do want to land the changes that I have made to Bugzilla but I may
have to back out a good deal and make a different version of Red Hat's
Bugzilla for checking in to CVS. Especially the cosmetic changes because it
seems they may not fit the general public. I will do that as soon as I can.
is difficult sometimes to come by.
</P
><P
-> There are also a good deal of other changes that were requested by
+> There are also a good deal of other changes that were requested by
management for things like support contracts and different permission
groups for making bugs private. Here is a short list of the major
changes that have been made:
TYPE="1"
><LI
><P
-> No enum types. All old enum types are now separate smaller tables.
+> No enum types. All old enum types are now separate smaller tables.
</P
></LI
><LI
><P
-> No bit wise operations. Not all databases support this so they were
+> No bit wise operations. Not all databases support this so they were
changed to a more generic way of doing this task
</P
></LI
><LI
><P
-> Bug reports can only be altered by the reporter, assignee, or a
+> Bug reports can only be altered by the reporter, assignee, or a
privileged bugzilla user. The rest of the world can see the bug but in
a non-changeable format (unless the bug has been marked private). They
can however add comments, add and remove themselves from the CC list
></LI
><LI
><P
-> Different group scheme. Each group has an id number related to it.
+> Different group scheme. Each group has an id number related to it.
There is a user_group table which contains userid to groupid mappings
to determine which groups each user belongs to. Additionally there is
a bug_group table that has bugid to groupid mappings to show which
></LI
><LI
><P
-> Product groups. product_table created to only allow certain products to
+> Product groups. product_table created to only allow certain products to
be visible for certain groups in both bug entry and query. This was
particulary helpful for support contracts.
</P
></LI
><LI
><P
-> Of course many (too many) changes to Bugzilla code itself to allow use
+> Of course many (too many) changes to Bugzilla code itself to allow use
with Oracle and still allow operation with Mysql if so desired.
Currently if you use Mysql it is set to use Mysql's old permission
scheme to keep breakage to a minimum. Hopefully one day this will
></LI
><LI
><P
-> Uses Text::Template perl module for rendering of the dynamic HTML pages
+> Uses Text::Template perl module for rendering of the dynamic HTML pages
such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and
footer parts of the page. This allows the html to be separate from the
perl code for customizing the look and feel of the page to one's
></LI
><LI
><P
-> There are many other smaller changes. There is also a port to Oracle
+> There are many other smaller changes. There is also a port to Oracle
that I have been working on as time permits but is not completely
finished but somewhat usable. I will merge it into our standard code
base when it becomes production quality. Unfortunately there will have
></LI
></OL
><P
-> Both the Mysql and Oracle versions of our current code base are
+> Both the Mysql and Oracle versions of our current code base are
available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit
patch files for all of the changes I have made and he can determine what is
suitable for addition to the main bugzilla cade base. But for me to commit
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1853"
+NAME="AEN1862"
></A
><B
>A.2.3. </B
-> What's the current status of Red Hat Bugzilla?
+>
+ What's the current status of Red Hat Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> <DIV
-CLASS="NOTE"
+>
+ <DIV
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This information is somewhat dated; I last updated it
+> This information is somewhat dated; I last updated it
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</P
>Dave Lawrence</EM
>:
<A
-NAME="AEN1860"
+NAME="AEN1869"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> I suppose the current thread warrants an update on the status of
+> I suppose the current thread warrants an update on the status of
Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on
Oracle for the last two days in our production environment. I
tried to do as much testing as possible with it before going live
thing going to help others that may need it.
</P
><P
-> As Matt has mentioned it is still using out-dated code and with a
+> As Matt has mentioned it is still using out-dated code and with a
little help I would like to bring everything up to date for
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_LOKI"
+NAME="faq-loki"
></A
>3. Loki Bugzilla (AKA Fenris)</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1866"
+NAME="AEN1875"
></A
><B
>A.3.1. </B
-> What is Loki Bugzilla (Fenris)?
+>
+ What is Loki Bugzilla (Fenris)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Loki Games has a customized version of Bugzilla available at
+>
+ Loki Games has a customized version of Bugzilla available at
<A
HREF="http://fenris.lokigames.com/"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_PHB"
+NAME="faq-phb"
></A
>4. Pointy-Haired-Boss Questions</H3
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The title of this section doesn't mean you're a PHB -- it just means
+> The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</P
></TD
>
</P
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1877"
+NAME="AEN1886"
></A
><B
>A.4.1. </B
-> Is Bugzilla web-based or do you have to have specific software or
+>
+ Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It is web and e-mail based. You can edit bugs by sending specially
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1882"
+NAME="AEN1891"
></A
><B
>A.4.2. </B
-> Has anyone you know of already done any Bugzilla integration with
+>
+ Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes! You can find more information elsewhere in "The Bugzilla
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1887"
+NAME="AEN1896"
></A
><B
>A.4.3. </B
-> Does Bugzilla allow the user to track multiple projects?
+>
+ Does Bugzilla allow the user to track multiple projects?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Absolutely! You can track up to a "soft-limit" of around
+>
+ Absolutely! You can track up to a "soft-limit" of around
64 individual "Products", that can each be composed of as
many "Components" as you want. Check the Administration
section of the Bugzilla Guide for more information regarding
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1892"
+NAME="AEN1901"
></A
><B
>A.4.4. </B
-> If I am on many projects, and search for all bugs assigned to me, will
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1897"
+NAME="AEN1906"
></A
><B
>A.4.5. </B
-> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
+>
+ Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. There are many specific MIME-types that are pre-defined by Bugzilla,
+>
+ Yes. There are many specific MIME-types that are pre-defined by Bugzilla,
but you may specify any arbitrary MIME-type you need when you
upload the file. Since all attachments are stored in the database,
however, I recommend storing large binary attachments elsewhere
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1902"
+NAME="AEN1911"
></A
><B
>A.4.6. </B
-> Does Bugzilla allow us to define our own priorities and levels? Do we
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes. However, modifying some fields, notably those related to bug
+>
+ 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
+> 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"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1909"
+NAME="AEN1918"
></A
><B
>A.4.7. </B
-> The index.html page doesn't show the footer. It's really annoying to have
+>
+ The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It's possible to get the footer on the static index page using
+>
+ It's possible to get the footer on the static index page using
Server Side Includes (SSI). The trick to doing this is making
sure that your web server is set up to allow SSI and specifically,
the #exec directive. You should also rename <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.html</TT
>
to <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>.
</P
><P
-> After you've done all that, you can add the following line to
+> After you've done all that, you can add the following line to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" --></PRE
+CLASS="programlisting"
+>
+<!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
+
+</PRE
></FONT
></TD
></TR
</P
><P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This line will be replaced with the actual HTML for the footer
+> This line will be replaced with the actual HTML for the footer
when the page is requested, so you should put this line where you
want the footer to appear.
</P
></DIV
></P
><P
-> Because this method depends on being able to use a #exec directive,
+> Because this method depends on being able to use a #exec directive,
and most ISP's will not allow that, there is an alternative method.
You could have a small script (such as <TT
-CLASS="FILENAME"
+CLASS="filename"
>api.cgi</TT
>)
that basically looks like:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->#!/usr/bonsaitools/bin/perl -w
+CLASS="programlisting"
+>
+#!/usr/bonsaitools/bin/perl -w
require 'globals.pl';
PutFooter();
} else {
die 'api.cgi was incorrectly called';
-}</PRE
+}
+
+</PRE
></FONT
></TD
></TR
></TABLE
>
and then put this line in <TT
-CLASS="FILENAME"
+CLASS="filename"
>index.shtml</TT
>.
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><!--#include virtual="api.cgi?sub=PutFooter"--></PRE
+CLASS="programlisting"
+>
+<!--#include virtual="api.cgi?sub=PutFooter"-->
+
+</PRE
></FONT
></TD
></TR
</P
><P
> <DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This still requires being able to use Server Side Includes, if
+> This still requires being able to use Server Side Includes, if
this simply will not work for you, see <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183"
TARGET="_top"
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1931"
+NAME="AEN1940"
></A
><B
>A.4.8. </B
-> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes. Look at <A
+>
+ Yes. Look at <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top"
-> http://bugzilla.mozilla.org/reports.cgi</A
+> http://bugzilla.mozilla.org/reports.cgi</A
> for basic reporting
facilities.
</P
><P
-> For more advanced reporting, I recommend hooking up a professional
+> For more advanced reporting, I recommend hooking up a professional
reporting package, such as Crystal Reports, and use ODBC to access
the MySQL database. You can do a lot through the Query page of
Bugzilla as well, but right now Advanced Reporting is much
interface with the database directly.
</P
><P
-> Advanced Reporting is a Bugzilla 3.X proposed feature.
+> Advanced Reporting is a Bugzilla 3.X proposed feature.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1939"
+NAME="AEN1948"
></A
><B
>A.4.9. </B
-> Is there email notification and if so, what do you see when you get an
+>
+ Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Email notification is user-configurable. The bug id and Topic
+>
+ Email notification is user-configurable. The bug id and Topic
of the bug report accompany each email notification, along with
a list of the changes made.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1944"
+NAME="AEN1953"
></A
><B
>A.4.10. </B
-> Can email notification be set up to send to multiple
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1949"
+NAME="AEN1958"
></A
><B
>A.4.11. </B
-> If there is email notification, do users have to have any particular
+>
+ If there is email notification, do users have to have any particular
type of email application?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla email is sent in plain text, the most compatible mail format
+>
+ Bugzilla email is sent in plain text, the most compatible mail format
on the planet.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you decide to use the bugzilla_email integration features
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1956"
+NAME="AEN1965"
></A
><B
>A.4.12. </B
-> If I just wanted to track certain bugs, as they go through life, can I
+>
+ If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. Place yourself in the "cc" field of the bug you wish to monitor.
+>
+ Yes. Place yourself in the "cc" field of the bug you wish to monitor.
Then change your "Notify me of changes to" field in the Email Settings
tab of the User Preferences screen in Bugzilla to the "Only those
bugs which I am listed on the CC line" option.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1961"
+NAME="AEN1970"
></A
><B
>A.4.13. </B
-> Does Bugzilla allow data to be imported and exported? If I had outsiders
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Mozilla allows data export through a custom DTD in XML format.
+>
+ Mozilla allows data export through a custom DTD in XML format.
It does not, however, export to specific formats other than the
XML Mozilla DTD. Importing the data into Excel or any other application
is left as an exercise for the reader.
</P
><P
-> If you create import filters to other applications from Mozilla's XML,
+> If you create import filters to other applications from Mozilla's XML,
please submit your modifications for inclusion in future Bugzilla
distributions.
</P
><P
-> As for data import, any application can send data to Bugzilla through
+> As for data import, any application can send data to Bugzilla through
the HTTP protocol, or through Mozilla's XML API. However, it seems
kind of silly to put another front-end in front of Bugzilla;
it makes more sense to create a simplified bug submission form in
<A
HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
TARGET="_top"
-> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1969"
+NAME="AEN1978"
></A
><B
>A.4.14. </B
-> Has anyone converted Bugzilla to another language to be used in other
+>
+ Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Currently, no. Internationalization support for Perl did not
+>
+ Currently, no. Internationalization support for Perl did not
exist in a robust fashion until the recent release of version 5.6.0;
Bugzilla is, and likely will remain (until 3.X) completely
non-localized.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1974"
+NAME="AEN1983"
></A
><B
>A.4.15. </B
-> Can a user create and save reports? Can they do this in Word format?
+>
+ Can a user create and save reports? Can they do this in Word format?
Excel format?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. No. No.
+>
+ Yes. No. No.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1979"
+NAME="AEN1988"
></A
><B
>A.4.16. </B
-> Can a user re-run a report with a new project, same query?
+>
+ Can a user re-run a report with a new project, same query?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1984"
+NAME="AEN1993"
></A
><B
>A.4.17. </B
-> Can a user modify an existing report and then save it into another name?
+>
+ Can a user modify an existing report and then save it into another name?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can save an unlimited number of queries in Bugzilla. You are free
+>
+ You can save an unlimited number of queries in Bugzilla. You are free
to modify them and rename them to your heart's desire.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1989"
+NAME="AEN1998"
></A
><B
>A.4.18. </B
-> Does Bugzilla have the ability to search by word, phrase, compound
+>
+ Does Bugzilla have the ability to search by word, phrase, compound
search?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You have no idea. Bugzilla's query interface, particularly with the
+>
+ You have no idea. Bugzilla's query interface, particularly with the
advanced Boolean operators, is incredibly versatile.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1994"
+NAME="AEN2003"
></A
><B
>A.4.19. </B
-> Can the admin person establish separate group and individual user
+>
+ Can the admin person establish separate group and individual user
privileges?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes.
+>
+ Yes.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN1999"
+NAME="AEN2008"
></A
><B
>A.4.20. </B
-> Does Bugzilla provide record locking when there is simultaneous access
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Bugzilla does not lock records. It provides mid-air collision detection,
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2004"
+NAME="AEN2013"
></A
><B
>A.4.21. </B
-> Are there any backup features provided?
+>
+ Are there any backup features provided?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> MySQL, the database back-end for Bugzilla, allows hot-backup of data.
+>
+ 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
+> http://www.mysql.com/doc/B/a/Backup.html</A
>
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2010"
+NAME="AEN2019"
></A
><B
>A.4.22. </B
-> Can users be on the system while a backup is in progress?
+>
+ Can users be on the system while a backup is in progress?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yes. However, commits to the database must wait
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2015"
+NAME="AEN2024"
></A
><B
>A.4.23. </B
-> What type of human resources are needed to be on staff to install and
+>
+ 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
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If Bugzilla is set up correctly from the start, continuing maintenance needs
+>
+ If Bugzilla is set up correctly from the start, continuing maintenance needs
are minimal and can be completed by unskilled labor. Things like rotate
backup tapes and check log files for the word "error".
</P
><P
-> Commercial Bug-tracking software typically costs somewhere upwards
+> 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.
</P
><P
-> As an example, as of this writing I typically charge
+> As an example, as of this writing I typically charge
$115 for the first hour, and $89 each hour thereafter
for consulting work. It takes me three to five hours to make Bugzilla
happy on a Development installation of Linux-Mandrake.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2022"
+NAME="AEN2031"
></A
><B
>A.4.24. </B
-> What time frame are we looking at if we decide to hire people to install
+>
+ 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,
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> It all depends on your level of commitment. Someone with much Bugzilla
+>
+ 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2027"
+NAME="AEN2036"
></A
><B
>A.4.25. </B
-> Is there any licensing fee or other fees for using Bugzilla? Any
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> No. MySQL asks, if you find their product valuable, that you purchase
+>
+ 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"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_INSTALL"
+NAME="faq-install"
></A
>5. Bugzilla Installation</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2034"
+NAME="AEN2043"
></A
><B
>A.5.1. </B
-> How do I download and install Bugzilla?
+>
+ How do I download and install Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Check <A
+>
+ Check <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> http://www.mozilla.org/projects/bugzilla/</A
+> http://www.mozilla.org/projects/bugzilla/</A
> for details.
Once you download it, untar it, read the Bugzilla Guide.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2040"
+NAME="AEN2049"
></A
><B
>A.5.2. </B
-> How do I install Bugzilla on Windows NT?
+>
+ How do I install Bugzilla on Windows NT?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Installation on Windows NT has its own section in
+>
+ Installation on Windows NT has its own section in
"The Bugzilla Guide".
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2045"
+NAME="AEN2054"
></A
><B
>A.5.3. </B
-> Is there an easy way to change the Bugzilla cookie name?
+>
+ Is there an easy way to change the Bugzilla cookie name?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> At present, no.
+>
+ At present, no.
</P
></DIV
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_SECURITY"
+NAME="faq-security"
></A
>6. Bugzilla Security</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2052"
+NAME="AEN2061"
></A
><B
>A.6.1. </B
-> How do I completely disable MySQL security if it's giving me problems
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM
+>
+ 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2058"
+NAME="AEN2067"
></A
><B
>A.6.2. </B
-> Are there any security problems with Bugzilla?
+>
+ Are there any security problems with Bugzilla?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The Bugzilla code has not undergone a complete security audit.
+>
+ The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found
in The Bugzilla Guide.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2063"
+NAME="AEN2072"
></A
><B
>A.6.3. </B
-> I've implemented the security fixes mentioned in Chris Yeh's security
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> This is a common problem, related to running out of file descriptors.
+>
+ 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
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_EMAIL"
+NAME="faq-email"
></A
>7. Bugzilla Email</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2070"
+NAME="AEN2079"
></A
><B
>A.7.1. </B
-> I have a user who doesn't want to receive any more email from Bugzilla.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> With the email changes to 2.12, the user should be able to set
+>
+ With the email changes to 2.12, the user should be able to set
this in user email preferences.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2075"
+NAME="AEN2084"
></A
><B
>A.7.2. </B
-> I'm evaluating/testing Bugzilla, and don't want it to send email to
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Edit the param for the mail text. Replace "To:" with "X-Real-To:",
+>
+ Edit the param for the mail text. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2080"
+NAME="AEN2089"
></A
><B
>A.7.3. </B
-> I want whineatnews.pl to whine at something more, or other than, only new
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+>
+ 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
+> 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.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2086"
+NAME="AEN2095"
></A
><B
>A.7.4. </B
-> I don't like/want to use Procmail to hand mail off to bug_email.pl.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> You can call bug_email.pl directly from your aliases file, with
+>
+ You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN2090"
+NAME="AEN2099"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
+> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
</P
></BLOCKQUOTE
>
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2093"
+NAME="AEN2102"
></A
><B
>A.7.5. </B
-> How do I set up the email interface to submit/change bugs via email?
+>
+ How do I set up the email interface to submit/change bugs via email?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You can find an updated README.mailif file in the contrib/ directory
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2098"
+NAME="AEN2107"
></A
><B
>A.7.6. </B
-> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
+>
+ Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If you are using an alternate Mail Transport Agent (MTA other than
+>
+ If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script 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 Sendmail, try enabling "sendmailnow" in editparams.cgi.
If you are using Postfix, you will also need to enable <SPAN
CLASS="QUOTE"
>"sendmailnow"</SPAN
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2105"
+NAME="AEN2114"
></A
><B
>A.7.7. </B
-> How come email never reaches me from bugzilla changes?
+>
+ How come email never reaches me from bugzilla changes?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Double-check that you have not turned off email in your user preferences.
+>
+ 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
+> 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
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_DB"
+NAME="faq-db"
></A
>8. Bugzilla Database</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2113"
+NAME="AEN2122"
></A
><B
>A.8.1. </B
-> I've heard Bugzilla can be used with Oracle?
+>
+ I've heard Bugzilla can be used with Oracle?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Red Hat Bugzilla, mentioned above, works with Oracle. The current version
+>
+ Red Hat Bugzilla, mentioned above, works with Oracle. The current version
from Mozilla.org does not have this capability. Unfortunately, though
you will sacrifice a lot of the really great features available in
Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2118"
+NAME="AEN2127"
></A
><B
>A.8.2. </B
-> Bugs are missing from queries, but exist in the database (and I can pull
+>
+ Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> You've almost certainly enabled the "shadow database", but for some
+>
+ You've almost certainly enabled the "shadow database", but for some
reason it hasn't been updated for all your bugs. This is the database
against which queries are run, so that really complex or slow queries won't
lock up portions of the database for other users. You can turn off the
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2123"
+NAME="AEN2132"
></A
><B
>A.8.3. </B
-> I think my database might be corrupted, or contain invalid entries. What
+>
+ I think my database might be corrupted, or contain invalid entries. What
do I do?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Run the <SPAN
+>
+ Run the <SPAN
CLASS="QUOTE"
>"sanity check"</SPAN
> utility
(<TT
-CLASS="FILENAME"
+CLASS="filename"
>./sanitycheck.cgi</TT
> in the
Bugzilla_home directory) from your web browser to see! If
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2131"
+NAME="AEN2140"
></A
><B
>A.8.4. </B
-> I want to manually edit some entries in my database. How?
+>
+ I want to manually edit some entries in my database. How?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> There is no facility in Bugzilla itself to do this. It's also generally
+>
+ 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 mysqladmin utility to
manually insert, delete, and modify table information. Personally, I
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2136"
+NAME="AEN2145"
></A
><B
>A.8.5. </B
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
+>
+ I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
+>
+ Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
the "crypt()" function. This prevented MySQL from storing encrypted passwords.
Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2141"
+NAME="AEN2150"
></A
><B
>A.8.6. </B
-> I think I've set up MySQL permissions correctly, but bugzilla still can't
+>
+ I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Try running MySQL from its binary: "mysqld --skip-grant-tables". This
+>
+ 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. However, I do not recommend you run it this way on a regular
basis, unless you really want your web site defaced and your machine
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2146"
+NAME="AEN2155"
></A
><B
>A.8.7. </B
-> How do I synchronize bug information among multiple different Bugzilla
+>
+ How do I synchronize bug information among multiple different Bugzilla
databases?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Well, you can synchronize or you can move bugs. Synchronization will
+>
+ 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.
+> 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,
+> 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
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2153"
+NAME="AEN2162"
></A
><B
>A.8.8. </B
-> Why do I get bizarre errors when trying to submit data, particularly problems
+>
+ Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> If you're sure your MySQL parameters are correct, you might want turn
+>
+ If you're sure your MySQL parameters are correct, you might want turn
"strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set
"On", you also cannot submit a bug as readable by more than one group with
"strictvaluechecks" ON.
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2158"
+NAME="AEN2167"
></A
><B
>A.8.9. </B
-> How come even after I delete bugs, the long descriptions show up?
+>
+ How come even after I delete bugs, the long descriptions show up?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> This should only happen with Bugzilla 2.14 if you are
+>
+ This should only happen with Bugzilla 2.14 if you are
using the <SPAN
CLASS="QUOTE"
>"shadow database"</SPAN
> feature, and your
shadow database is out of sync. Try running
<TT
-CLASS="FILENAME"
+CLASS="filename"
>syncshadowdb</TT
>
<TT
-CLASS="OPTION"
+CLASS="option"
>-syncall</TT
> to make sure your shadow
database is in synch with your primary database.
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_NT"
+NAME="faq-nt"
></A
>9. Bugzilla and Win32</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2168"
+NAME="AEN2177"
></A
><B
>A.9.1. </B
-> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+>
+ What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Remove Windows. Install Linux. Install Bugzilla.
+>
+ Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2173"
+NAME="AEN2182"
></A
><B
>A.9.2. </B
-> Is there a "Bundle::Bugzilla" equivalent for Win32?
+>
+ Is there a "Bundle::Bugzilla" equivalent for Win32?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2178"
+NAME="AEN2187"
></A
><B
>A.9.3. </B
-> CGI's are failing with a "something.cgi is not a valid Windows NT
+>
+ CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Depending on what Web server you are using, you will have to configure
+>
+ 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:
+> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN2183"
+NAME="AEN2192"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> "Set application mappings. In the ISM, map the extension for the script
+> "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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2186"
+NAME="AEN2195"
></A
><B
>A.9.4. </B
-> Can I have some general instructions on how to make Bugzilla on Win32 work?
+>
+ Can I have some general instructions on how to make Bugzilla on Win32 work?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The following couple entries are deprecated in favor of the Windows installation
+>
+ The following couple entries are deprecated in favor of the Windows installation
instructions available in the "Administration" portion of "The Bugzilla Guide".
However, they are provided here for historical interest and insight.
<P
-CLASS="LITERALLAYOUT"
-> 1. #!C:/perl/bin/perl had to be added to every perl file.<br>
+CLASS="literallayout"
+><br>
+ 1. #!C:/perl/bin/perl had to be added to every perl file.<br>
2. Converted to Net::SMTP to handle mail messages instead of<br>
/usr/bin/sendmail.<br>
3. The crypt function isn't available on Windows NT (at least none that I<br>
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2192"
+NAME="AEN2201"
></A
><B
>A.9.5. </B
-> I'm having trouble with the perl modules for NT not being able to talk to
+>
+ I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Your modules may be outdated or inaccurate. Try:
+>
+ Your modules may be outdated or inaccurate. Try:
<P
></P
><OL
TYPE="1"
><LI
><P
-> Hitting http://www.activestate.com/ActivePerl
+> Hitting http://www.activestate.com/ActivePerl
</P
></LI
><LI
><P
-> Download ActivePerl
+> Download ActivePerl
</P
></LI
><LI
><P
-> Go to your prompt
+> Go to your prompt
</P
></LI
><LI
><P
-> Type 'ppm'
+> Type 'ppm'
</P
></LI
><LI
><P
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="prompt"
>PPM></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>install DBI DBD-mysql GD</B
>
</P
<A
HREF=" http://www.activestate.com/Packages/"
TARGET="_top"
-> http://www.activestate.com/Packages/</A
+> http://www.activestate.com/Packages/</A
>
</P
></DIV
></DIV
></DIV
><DIV
-CLASS="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_USE"
+NAME="faq-use"
></A
>10. Bugzilla Usage</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2213"
+NAME="AEN2222"
></A
><B
>A.10.1. </B
-> The query page is very confusing. Isn't there a simpler way to query?
+>
+ The query page is very confusing. Isn't there a simpler way to query?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> We are developing in that direction. You can follow progress on this
+>
+ We are developing in that direction. You can follow progress on this
at <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"
TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
+> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
>. Some functionality
is available in Bugzilla 2.12, and is available as "quicksearch.html"
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2219"
+NAME="AEN2228"
></A
><B
>A.10.2. </B
-> I'm confused by the behavior of the "accept" button in the Show Bug form.
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> The current behavior is acceptable to bugzilla.mozilla.org and most
+>
+ The current behavior is acceptable to bugzilla.mozilla.org and most
users. I personally don't like it. You have your choice of patches
to change this behavior, however.
<P
><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
TARGET="_top"
-> Add a "and accept bug" radio button</A
+> Add a "and accept bug" radio button</A
></TD
></TR
><TR
><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
TARGET="_top"
-> "Accept" button automatically assigns to you</A
+> "Accept" button automatically assigns to you</A
></TD
></TR
></TBODY
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2229"
+NAME="AEN2238"
></A
><B
>A.10.3. </B
-> I can't upload anything into the database via the "Create Attachment"
+>
+ I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> The most likely cause is a very old browser or a browser that is
+>
+ 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"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2234"
+NAME="AEN2243"
></A
><B
>A.10.4. </B
-> Email submissions to Bugzilla that have attachments end up asking me to
+>
+ Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Yup. Just rename it once you download it, or save it under a different
+>
+ Yup. Just rename it once you download it, or save it under a different
filename. This will not be fixed anytime too soon, because it would
cripple some other functionality.
</P
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2239"
+NAME="AEN2248"
></A
><B
>A.10.5. </B
-> How do I change a keyword in Bugzilla, once some bugs are using it?
+>
+ How do I change a keyword in Bugzilla, once some bugs are using it?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> In the Bugzilla administrator UI, edit the keyword and it will let you
+>
+ 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="QANDADIV"
+CLASS="qandadiv"
><H3
><A
-NAME="FAQ_HACKING"
+NAME="faq-hacking"
></A
>11. Bugzilla Hacking</H3
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2246"
+NAME="AEN2255"
></A
><B
>A.11.1. </B
-> What bugs are in Bugzilla right now?
+>
+ What bugs are in Bugzilla right now?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
-> Try <A
+>
+ 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
+> this link</A
> to view current bugs or requests for
enhancement for Bugzilla.
</P
><P
-> You can view bugs marked for 2.16 release
+> You can view bugs marked for 2.16 release
<A
HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16"
TARGET="_top"
<A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
-> Bugzilla Project Page</A
+> Bugzilla Project Page</A
> for details on how to
check current sources out of CVS so you can have these
bug fixes early!
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2255"
+NAME="AEN2264"
></A
><B
>A.11.2. </B
-> How can I change the default priority to a null value? For instance, have the default
+>
+ 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"
+CLASS="answer"
><P
><B
> </B
-> This is well-documented here: <A
+>
+ 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
+> 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
></DIV
></DIV
><DIV
-CLASS="QANDAENTRY"
+CLASS="qandaentry"
><DIV
-CLASS="QUESTION"
+CLASS="question"
><P
><A
-NAME="AEN2261"
+NAME="AEN2270"
></A
><B
>A.11.3. </B
-> What's the best way to submit patches? What guidelines should I follow?
+>
+ What's the best way to submit patches? What guidelines should I follow?
</P
></DIV
><DIV
-CLASS="ANSWER"
+CLASS="answer"
><P
><B
> </B
TYPE="1"
><LI
><P
-> Enter a bug into bugzilla.mozilla.org for the <SPAN
+> Enter a bug into bugzilla.mozilla.org for the <SPAN
CLASS="QUOTE"
>"<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
></LI
><LI
><P
-> Upload your patch as a unified DIFF (having used "diff -u" against
+> Upload your patch as a unified DIFF (having used "diff -u" against
the <EM
>current sources</EM
> checked out of CVS),
></LI
><LI
><P
-> Announce your patch and the associated URL
+> Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
good, fairly immediate reaction to the implications of your patch,
></LI
><LI
><P
-> If it passes muster with minimal modification, the person to whom
+> 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
+> Bask in the glory of the fact that you helped write the most successful
open-source bug-tracking software on the planet :)
</P
></LI
ALIGN="left"
VALIGN="top"
><A
-HREF="variant_sourceforge.html"
+HREF="variant-sourceforge.html"
>Prev</A
></TD
><TD
TITLE="Translations"
HREF="translations.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="FEEDBACK"
+NAME="feedback"
>1.7. Feedback</A
></H1
><P
-> I welcome feedback on this document. Without your submissions
+> I welcome feedback on this document. Without your submissions
and input, this Guide cannot continue to exist. Please mail
additions, comments, criticisms, etc. to
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>></TT
>. Please send flames to
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:devnull@localhost"
>devnull@localhost</A
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="FUTURE"
+NAME="future"
>Chapter 6. The Future of Bugzilla</A
></H1
><TABLE
BORDER="0"
-BGCOLOR="#6495ED"
+BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="SYNOPSIS"
+CLASS="synopsis"
>Bugzilla's Future. Much of this is the present, now.</PRE
></FONT
></TD
></TR
></TABLE
><P
-> Bugzilla's future is a constantly-changing thing, as various developers
+> Bugzilla's future is a constantly-changing thing, as various developers
<SPAN
CLASS="QUOTE"
>"scratch an itch"</SPAN
not quite as readable as the rest of the Guide.
</P
><P
-> <P
-CLASS="LITERALLAYOUT"
-> Bugzilla Blue Sky<br>
+> <P
+CLASS="literallayout"
+><br>
+ Bugzilla Blue Sky<br>
<br>
Customisability<br>
<br>
TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GENINSTALL"
+NAME="geninstall"
>3.5. Installation General Notes</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN941"
>3.5.1. Modifying Your Running System</A
></H2
><P
-> Bugzilla optimizes database lookups by storing all relatively static
+> Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory.
</P
><P
-> If you make a change to the structural data in your database
+> If you make a change to the structural data in your database
(the versions table for example), or to the
<SPAN
CLASS="QUOTE"
changes won't show up.
</P
><P
-> That file gets automatically regenerated whenever it's more than an
+> That file gets automatically regenerated whenever it's more than an
hour old, so Bugzilla will eventually notice your changes by itself, but
generally you want it to notice right away, so that you can test things.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN948"
>3.5.2. Upgrading From Previous Versions</A
></H2
><P
-> The developers of Bugzilla are constantly adding new tables, columns and
+> The developers of Bugzilla are constantly adding new tables, columns and
fields. You'll get SQL errors if you just update the code. The strategy
to update is to simply always run the checksetup.pl script whenever
you upgrade your installation of Bugzilla. If you want to see what has
changed, you can read the comments in that file, starting from the end.
</P
><P
-> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
+> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
the latest version, please consult the file, "UPGRADING-pre-2.8" in the
Bugzilla root directory after untarring the archive.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="HTACCESS"
+NAME="htaccess"
>3.5.3. <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files and security</A
></H2
><P
-> To enhance the security of your Bugzilla installation,
+> To enhance the security of your Bugzilla installation,
Bugzilla will generate
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
></I
> files
which the Apache webserver can use to restrict access to
the bugzilla data files. The checksetup script will
generate the <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you are using an alternate provider of
+> If you are using an alternate provider of
<SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>webdot</SPAN
> services for graphing
(as described when viewing
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editparams.cgi</TT
> in your web
browser), you will need to change the ip address in
<TT
-CLASS="FILENAME"
+CLASS="filename"
>data/webdot/.htaccess</TT
> to the ip
address of the webdot server that you are using.
</P
><P
-> If you are using Internet Information Server or other web
+> 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 or other web
server which does not observe <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
>
conventions, you can disable their creation by editing
<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> and setting the
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$create_htaccess</TT
> variable to
<TT
-CLASS="PARAMETER"
+CLASS="parameter"
><I
>0</I
></TT
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MOD_THROTTLE"
+NAME="mod-throttle"
>3.5.4. <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_throttle</TT
> and Security</A
></H2
><P
-> It is possible for a user, by mistake or on purpose, to access
+> 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"
+CLASS="filename"
>mod_throttle</TT
> which can limit
connections by ip-address. You may download this module at
>. 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"
+CLASS="command"
>ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/"
> for more information. </P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CONTENT_TYPE"
+NAME="content-type"
>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></H2
><P
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+CLASS="programlisting"
+> bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \
mv $i.tmp $i; done
</PRE
></TABLE
></P
><P
-> All this one-liner command does is search for all instances of
+> All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="UNIXHISTORY"
+NAME="unixhistory"
>3.5.6. UNIX Installation Instructions History</A
></H2
><P
-> This document was originally adapted from the Bonsai
+> This document was originally adapted from the Bonsai
installation instructions by Terry Weissman
<terry@mozilla.org>.
</P
><P
-> The February 25, 1999 re-write of this page was done by Ry4an
+> The February 25, 1999 re-write of this page was done by Ry4an
Brase <ry4an@ry4an.org>, with some edits by Terry
Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But
don't send bug reports to them; report them using bugzilla, at <A
> ).
</P
><P
-> This document was heavily modified again Wednesday, March 07
+> This document was heavily modified again Wednesday, March 07
2001 to reflect changes for Bugzilla 2.12 release by Matthew
P. Barnson. The securing MySQL section should be changed to
become standard procedure for Bugzilla installations.
</P
><P
-> Finally, the README in its entirety was marked up in SGML and
+> Finally, the README in its entirety was marked up in SGML and
included into the Guide on April 24, 2001 by Matt Barnson.
Since that time, it's undergone extensive modification as
Bugzilla grew.
</P
><P
-> Comments from people using this Guide for the first time are
+> Comments from people using this Guide for the first time are
particularly welcome.
</P
></DIV
--- /dev/null
+<HTML
+><HEAD
+><TITLE
+>PREAMBLE</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-0"
+>0. PREAMBLE</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-1.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-0.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-1"
+>1. APPLICABILITY AND DEFINITIONS</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-0.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-2.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-9.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-10"
+>10. FUTURE REVISIONS OF THIS LICENSE</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-9.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-howto.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-1.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-2"
+>2. VERBATIM COPYING</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-1.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-3.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-2.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-3"
+>3. COPYING IN QUANTITY</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-2.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-4.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-3.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-4"
+>4. MODIFICATIONS</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-3.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-5.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-4.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-5"
+>5. COMBINING DOCUMENTS</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-4.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-6.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-5.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-6"
+>6. COLLECTIONS OF DOCUMENTS</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-5.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-7.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-6.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-7"
+>7. AGGREGATION WITH INDEPENDENT WORKS</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-6.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-8.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-7.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-8"
+>8. TRANSLATION</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-7.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-9.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-8.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-9"
+>9. TERMINATION</A
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-8.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-10.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="gfdl-10.html"
+>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"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="gfdl-howto"
+>How to use this License for your documents</A
+></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="AEN2673"
+></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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-10.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="glossary.html"
+>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"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Glossary</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
HREF="bzhacking.html"><LINK
REL="NEXT"
TITLE="PREAMBLE"
-HREF="gfdl_0.html"></HEAD
+HREF="gfdl-0.html"></HEAD
><BODY
-CLASS="APPENDIX"
+CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="gfdl_0.html"
+HREF="gfdl-0.html"
>Next</A
></TD
></TR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><H1
><A
-NAME="GFDL"
+NAME="gfdl"
>Appendix E. GNU Free Documentation License</A
></H1
><DIV
></DT
><DT
>0. <A
-HREF="gfdl_0.html"
+HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
-HREF="gfdl_1.html"
+HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
-HREF="gfdl_2.html"
+HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
-HREF="gfdl_3.html"
+HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
-HREF="gfdl_4.html"
+HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
-HREF="gfdl_5.html"
+HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
-HREF="gfdl_6.html"
+HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
-HREF="gfdl_7.html"
+HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
-HREF="gfdl_8.html"
+HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
-HREF="gfdl_9.html"
+HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
-HREF="gfdl_10.html"
+HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
-HREF="gfdl_howto.html"
+HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2550"
+NAME="AEN2583"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
ALIGN="right"
VALIGN="top"
><A
-HREF="gfdl_0.html"
+HREF="gfdl-0.html"
>Next</A
></TD
></TR
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="How to use this License for your documents"
-HREF="gfdl_howto.html"></HEAD
+HREF="gfdl-howto.html"></HEAD
><BODY
-CLASS="GLOSSARY"
+CLASS="glossary"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="gfdl_howto.html"
+HREF="gfdl-howto.html"
>Prev</A
></TD
><TD
CLASS="GLOSSARY"
><H1
><A
-NAME="GLOSSARY"
+NAME="glossary"
>Glossary</A
></H1
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="AEN2645"
+NAME="AEN2678"
>0-9, high ascii</A
></H1
><DL
></DT
><DD
><P
-> Apache web server, and other NCSA-compliant web servers,
+> Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files. These
restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> file contains the
password to your database. If this information were
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_A"
+NAME="gloss-a"
>A</A
></H1
><DL
>In this context, Apache is the web server most
commonly used for serving up
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Bugzilla</I
> pages. Contrary to
popular belief, the apache web server has nothing to do
>"a patchy"</SPAN
> version of the original
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>NCSA</SPAN
> world-wide-web server.</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_B"
+NAME="gloss-b"
>B</A
></H1
><DL
></DT
><DD
><P
-> A <SPAN
+> A <SPAN
CLASS="QUOTE"
>"Bug"</SPAN
> in Bugzilla refers to an issue
></DT
><DD
><P
-> Each Bugzilla Bug is assigned a number that uniquely
+> 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.
></DT
><DD
><P
-> Bugzilla is the industry-standard bug tracking system. It
+> Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_C"
+NAME="gloss-c"
></A
></H1
><DL
><DT
><A
-NAME="GLOSS_COMPONENT"
+NAME="gloss-component"
><B
>Component</B
></A
></DT
><DD
><P
-> A Component is a subsection of a Product. It should be a
+> 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
></DD
><DT
><A
-NAME="GLOSS_CPAN"
+NAME="gloss-cpan"
><B
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>CPAN</SPAN
></B
></A
><DD
><P
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>CPAN</SPAN
> stands for the
<SPAN
>. CPAN
maintains a large number of extremely useful
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Perl</I
> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_D"
+NAME="gloss-d"
>D</A
></H1
><DL
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"
+CLASS="glossterm"
>mysqld</I
>, the
MySQL server, and <I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>apache</I
>, a web
server, are generally run as daemons.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_G"
+NAME="gloss-g"
></A
></H1
><DL
comes by lumping users into groups, and assigning those
groups certain privileges to
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Products</I
> and
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Components</I
> in the
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_I"
+NAME="gloss-i"
>I</A
></H1
><DL
><DT
><A
-NAME="GLOSS_INFINITELOOP"
+NAME="gloss-infiniteloop"
><B
>Infinite Loop</B
></A
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_M"
+NAME="gloss-m"
>M</A
></H1
><DL
><P
>mysqld is the name of the
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>daemon</I
> for the MySQL database. In
general, it is invoked automatically through the use of
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_P"
+NAME="gloss-p"
>P</A
></H1
><DL
Security) for all bugs entered into components beneath
it.</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN2736"
+NAME="AEN2769"
></A
><P
><B
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"
+CLASS="glossterm"
>Bugzilla</I
> is
maintained in Perl.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_Q"
+NAME="gloss-q"
>Q</A
></H1
><DL
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_R"
+NAME="gloss-r"
>R</A
></H1
><DL
><DT
><A
-NAME="GLOSS_RECURSION"
+NAME="gloss-recursion"
><B
>Recursion</B
></A
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_S"
+NAME="gloss-s"
>S</A
></H1
><DL
><DT
><B
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
></B
></DT
><DD
><P
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> stands for <SPAN
CLASS="QUOTE"
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> has withstood the test of time as
a robust, powerful language.
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
><SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
></I
> is the
>"baby brother"</SPAN
> of SGML; any valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
> document it, by definition, a valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
> document. The document you are
reading is written and maintained in
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>SGML</SPAN
>, and is also valid
<SPAN
-CLASS="ACRONYM"
+CLASS="acronym"
>XML</SPAN
> if you modify the Document Type
Definition.</P
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_T"
+NAME="gloss-t"
>T</A
></H1
><DL
><DT
><A
-NAME="GLOSS_TARGET_MILESTONE"
+NAME="gloss-target-milestone"
><B
>Target Milestone</B
></A
></DT
><DD
><P
-> Target Milestones are Product goals. They are
+> Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<SPAN
></DL
></DIV
><DIV
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><H1
-CLASS="GLOSSDIV"
+CLASS="glossdiv"
><A
-NAME="GLOSS_Z"
+NAME="gloss-z"
>Z</A
></H1
><DL
><DT
><A
-NAME="ZARRO-BOOGS-FOUND"
+NAME="zarro-boogs-found"
><B
>Zarro Boogs Found</B
></A
ALIGN="left"
VALIGN="top"
><A
-HREF="gfdl_howto.html"
+HREF="gfdl-howto.html"
>Prev</A
></TD
><TD
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GRANTTABLES"
+NAME="granttables"
>C.3. MySQL Permissions & Grant Tables</A
></H1
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
troubles to work on : ) Although it is of limited use, it
still has SOME use, thus it's still included.</P
><P
-> Please note, however, that I was a relatively new user to
+> Please note, however, that I was a relatively new user to
MySQL at the time. Some of my suggestions, particularly in
how to set up security, showed a terrible lack of
security-related database experience.
></TABLE
></DIV
><P
-CLASS="LITERALLAYOUT"
->From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999<br>
+CLASS="literallayout"
+><br>
+From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999<br>
Date: Mon, 1 Mar 1999 21:37:04 -0700 <br>
From: Matthew Barnson matt_barnson@singletrac.com<br>
To: keystone-users@homeport.org<br>
TITLE="Where can I find my user preferences?"
HREF="init4me.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="HOW"
+NAME="how"
>2.3. How do I use Bugzilla?</A
></H1
><TABLE
></TR
></TABLE
><P
-> Bugzilla is a large, complex system. Describing how to use it
+> Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
software.
</P
><P
-> Throughout this portion of the Guide, we will refer to user
+> Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
-> landfill.tequilarista.org</A
+> landfill.tequilarista.org</A
>.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some people have run into difficulties completing this
+> Some people have run into difficulties completing this
tutorial. If you run into problems, please check the
updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/"
mentioned here.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MYACCOUNT"
+NAME="myaccount"
>2.3.1. Create a Bugzilla Account</A
></H2
><P
-> First things first! If you want to use Bugzilla, first you
+> First things first! 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 the end-user
TYPE="1"
><LI
><P
-> Click the "Open a new Bugzilla account" link.
+> Click the "Open a new Bugzilla account" link.
</P
></LI
><LI
><P
-> Enter your "E-mail address" and "Real Name" (or whatever
+> Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
</P
></LI
><LI
><P
-> Within moments, you should receive an email to the address
+> 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
></LI
><LI
><P
-> Click the <SPAN
+> Click the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
> link in the yellow area at
>"Login"</SPAN
>.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you ever forget your password, you can come back to
+> If you ever forget your password, you can come back to
this page, enter your <SPAN
CLASS="QUOTE"
>"E-mail address"</SPAN
></DIV
>
<DIV
-CLASS="CAUTION"
+CLASS="caution"
><P
></P
><TABLE
-CLASS="CAUTION"
-WIDTH="90%"
+CLASS="caution"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Many modern browsers include an
+> Many modern browsers include an
<SPAN
CLASS="QUOTE"
>"Auto-Complete"</SPAN
></LI
></OL
><P
-> Congratulations! If you followed these directions, you now
+> Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="QUERY"
+NAME="query"
>2.3.2. The Bugzilla Query Page</A
></H2
><P
-> The Bugzilla Query Page is the heart and soul of the Bugzilla
+> The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
</P
><P
-> There are efforts underway to simplify query usage. If you
+> There are efforts underway to simplify query usage. If you
have a local installation of Bugzilla 2.12 or higher, you
should have <TT
-CLASS="FILENAME"
+CLASS="filename"
>quicksearch.html</TT
> available to
use and simplify your searches. There is also a helper for
the query interface, called
<TT
-CLASS="FILENAME"
+CLASS="filename"
>queryhelp.cgi</TT
>. Landfill tends to run the
latest code, so these two utilities should be available there
for your perusal.
</P
><P
-> At this point, please visit the main Bugzilla site,
+> At this point, let's visit the query page.
<A
-HREF="http://bugzilla.mozilla.org/query.cgi"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
TARGET="_top"
-> bugzilla.mozilla.org</A
->, to see a more fleshed-out query page.
+> landfill.tequilarista.org/bugzilla-tip/query.cgi</A
+>
</P
><P
-> The first thing you need to notice about the Bugzilla Query
+> The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
> underlined. Select it.
</P
><P
-> Notice the page that popped up? Every underlined word you see
+> Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
button in your browser.
</P
><P
-> I'm sure that after checking out the online help, you are now
+> I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
TYPE="1"
><LI
><P
-> Ensure you are back on the <SPAN
+> Ensure you are back on the <SPAN
CLASS="QUOTE"
>"Bugzilla Query
Page"</SPAN
figured out.
</P
><P
-> Basically, selecting <EM
+> Basically, selecting <EM
>anything</EM
> on the
query page narrows your search down. Leaving stuff
></LI
><LI
><P
-> You see the box immediately below the top six boxes that
+> You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
put my email address in there, and see what happens.
</P
><P
-> Type "barnboy@trilobyte.net" in the top Email text box.
+> Type "barnboy@trilobyte.net" in the top Email text box.
</P
></LI
><LI
><P
-> Let's narrow the search some more. Scroll down until you
+> Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
></LI
><LI
><P
-> Did you notice that some of the boxes to the right changed
+> Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN307"
></A
>Example 2-1. Some Famous Software Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN309"
></A
><P
></P
><P
-> Do you remember the hype in 1995 when Microsoft
+> Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
ME(Millenium Edition)(r).
</P
><P
-> Software "Versions" help a manufacturer
+> Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
version than 1.1.1.
</P
><P
-> In general, a "Version" in Bugzilla should refer to
+> In general, a "Version" in Bugzilla should refer to
<EM
>released</EM
> products, not products
>
</P
><P
-> A "Component" is a piece of a Product.
+> A "Component" is a piece of a Product.
It may be a standalone program, or some other logical
division of a Product or Program.
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN317"
></A
>Example 2-2. Mozilla's Bugzilla Components</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN319"
></A
><P
></P
><P
-> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
+> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<P
></P
><TABLE
>,
Administration of a bugzilla installation, including
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editcomponents.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editgroups.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editkeywords.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editparams.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editproducts.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editusers.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>editversions.cgi,</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>sanitycheck.cgi</TT
>.
</TD
>,
Creating, changing, and viewing bugs.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>enter_bug.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>post_bug.cgi</TT
>,
<TT
-CLASS="FILENAME"
+CLASS="filename"
>show_bug.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>process_bug.cgi</TT
>.
</TD
>,
The bugzilla documentation, including anything in the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>docs/</TT
> directory and The Bugzilla Guide
(This document :)
>,
Anything to do with email sent by Bugzilla.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
>
</TD
>,
The installation process of Bugzilla. This includes
<TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
> and whatever else it evolves into.
</TD
>,
Anything to do with searching for bugs and viewing the buglists.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>query.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>buglist.cgi</TT
>
</TD
>,
Getting reports from Bugzilla.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>reports.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>duplicates.cgi</TT
>
</TD
>,
Anything about managing a user account from the user's perspective.
<TT
-CLASS="FILENAME"
+CLASS="filename"
>userprefs.cgi</TT
>, saved queries, creating accounts,
changing passwords, logging in, etc.
>
</P
><P
-> A "Milestone", or "Target Milestone" is a often a planned
+> A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
of reach by the time the important day arrives.
</P
><P
-> The Bugzilla Project has set up Milestones for future
+> The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
></LI
><LI
><P
-> OK, now let's select the "Bugzilla" component from its scrollbox.
+> OK, now let's select the "Bugzilla" component from its scrollbox.
</P
></LI
><LI
><P
-> Skip down the page a bit -- do you see the "submit query" button?
+> Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run
this query!
</P
></LI
><LI
><P
-> Congratulations! You've completed your first Query, and
+> Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
></LI
></OL
><P
-> I encourage you to click the bug numbers in the left-hand
+> I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
this is a tremendous timesaver.
</P
><P
-> A couple more interesting things about the Bug List page:
+> A couple more interesting things about the Bug List page:
<P
></P
><TABLE
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are many more options to the Bugzilla Query Page and
+> There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <A
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUGREPORTS"
+NAME="bugreports"
>2.3.3. Creating and Managing Bug Reports</A
></H2
><TABLE
></TR
></TABLE
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUG_WRITING"
+NAME="bug-writing"
>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
-> Before we plunge into writing your first bug report, I
+> Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
>. 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
-> While you are at it, why not learn how to find previously
+> While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
>.
</P
><P
-> I realize this was a lot to read. However, understanding
+> I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
</P
TYPE="1"
><LI
><P
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
></LI
><LI
><P
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
> Enter a new bug report</A
></LI
><LI
><P
-> Select a product.
+> Select a product.
</P
></LI
><LI
><P
-> Now you should be at the "Enter Bug" form. The
+> Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
></LI
><LI
><P
-> Select a Component in the scrollbox.
+> Select a Component in the scrollbox.
</P
></LI
><LI
><P
-> Bugzilla should have made reasonable guesses, based upon
+> Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
></LI
><LI
><P
-> Fill in the "Assigned To" box with the email address you
+> Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
></LI
><LI
><P
-> Leave the "CC" text box blank. Fill in the "URL" box
+> Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</P
></LI
><LI
><P
-> Enter "The Bugzilla Guide" in the Summary text box, and
+> Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</P
></LI
></OL
><P
-> Voila! Select "Commit" and send in your bug report! Next
+> Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BUG_MANAGE"
+NAME="bug-manage"
>2.3.3.2. Managing your Bug Reports</A
></H3
><P
-> OK, you should have a link to the bug you just created near
+> OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
TYPE="1"
><LI
><P
-> Scroll down a bit on the subsequent page, until you see
+> Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
></LI
><LI
><P
-> Hey! It said it couldn't take the change in a big red
+> Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
></LI
></OL
><P
-> You have now learned the basics of Bugzilla navigation,
+> You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</P
><P
-> But I'll give a few last hints!
+> But I'll give a few last hints!
</P
><P
-HREF="http://bugzilla.mozilla.org/help.html"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html"
TARGET="_top"
>CLUE</A
> on the Query page that will teach you more how to use the form.
</P
><P
->
If you click the hyperlink on the <A
-HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
+>
If you click the hyperlink on the <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi"
TARGET="_top"
>Component</A
> box of the Query page, you will be presented a form that will describe what all the components are.
</P
><P
-> Possibly the most powerful feature of the Query page is the
+> Possibly the most powerful feature of the Query page is the
<A
-HREF="http://bugzilla.mozilla.org/booleanchart.html"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
TARGET="_top"
>Boolean Chart</A
> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P
><P
->
Finally, you can build some nifty <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
+>
Finally, you can build some nifty <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi"
TARGET="_top"
>Reports</A
> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
NAME="KEYWORD"
CONTENT="webtools"></HEAD
><BODY
-CLASS="BOOK"
+CLASS="book"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
><DIV
CLASS="BOOK"
><A
-NAME="INDEX"
+NAME="index"
></A
><DIV
CLASS="TITLEPAGE"
><H1
-CLASS="TITLE"
+CLASS="title"
><A
NAME="AEN2"
>The Bugzilla Guide</A
></H1
><H3
-CLASS="AUTHOR"
+CLASS="author"
><A
NAME="AEN27"
>Matthew P. Barnson</A
></H3
><DIV
-CLASS="AFFILIATION"
+CLASS="affiliation"
><DIV
-CLASS="ADDRESS"
+CLASS="address"
><P
-CLASS="ADDRESS"
+CLASS="address"
>barnboy@trilobyte.net</P
></DIV
></DIV
><SPAN
-CLASS="COLLAB"
+CLASS="collab"
><SPAN
-CLASS="COLLABNAME"
+CLASS="collabname"
>Zach Lipton</SPAN
><DIV
-CLASS="AFFILIATION"
+CLASS="affiliation"
><DIV
-CLASS="ADDRESS"
+CLASS="address"
><P
-CLASS="ADDRESS"
+CLASS="address"
>zach AT zachlipton DOT com</P
></DIV
></DIV
><BR></SPAN
><DIV
-CLASS="REVHISTORY"
+CLASS="revhistory"
><TABLE
WIDTH="100%"
BORDER="0"
></DIV
><DIV
><DIV
-CLASS="ABSTRACT"
+CLASS="abstract"
><A
NAME="AEN39"
></A
><P
></P
><P
-> This is the documentation for Bugzilla, the Mozilla
+> This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</P
><P
-> Bugzilla is an enterprise-class set of software utilities
+> Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
- While it is easy to use and quite flexible, it is very
+ While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
- professional on operating system upon which you install
+ professional for the operating system upon which you install
Bugzilla.
</P
><P
-> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
+> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
><DL
><DT
>2.3.1. <A
-HREF="how.html#MYACCOUNT"
+HREF="how.html#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
-HREF="how.html#QUERY"
+HREF="how.html#query"
>The Bugzilla Query Page</A
></DT
><DT
>2.3.3. <A
-HREF="how.html#BUGREPORTS"
+HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>2.3.3.1. <A
-HREF="how.html#BUG_WRITING"
+HREF="how.html#bug-writing"
>Writing a Great Bug Report</A
></DT
><DT
>2.3.3.2. <A
-HREF="how.html#BUG_MANAGE"
+HREF="how.html#bug-manage"
>Managing your Bug Reports</A
></DT
></DL
><DL
><DT
>2.4.1. <A
-HREF="init4me.html#ACCOUNTSETTINGS"
+HREF="init4me.html#accountsettings"
>Account Settings</A
></DT
><DT
>2.4.2. <A
-HREF="init4me.html#EMAILSETTINGS"
+HREF="init4me.html#emailsettings"
>Email Settings</A
></DT
><DD
><DL
><DT
>2.4.2.1. <A
-HREF="init4me.html#NOTIFICATION"
+HREF="init4me.html#notification"
>Email Notification</A
></DT
><DT
>2.4.2.2. <A
-HREF="init4me.html#NEWEMAILTECH"
+HREF="init4me.html#newemailtech"
>New Email Technology</A
></DT
><DT
>2.4.2.3. <A
-HREF="init4me.html#WATCHSETTINGS"
+HREF="init4me.html#watchsettings"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>2.4.3. <A
-HREF="init4me.html#FOOTERSETTINGS"
+HREF="init4me.html#footersettings"
>Page Footer</A
></DT
><DT
>2.4.4. <A
-HREF="init4me.html#PERMISSIONSETTINGS"
+HREF="init4me.html#permissionsettings"
>Permissions</A
></DT
></DL
></DT
><DT
>3.2.3. <A
-HREF="stepbystep.html#INSTALL-MYSQL"
+HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A
></DT
><DT
>3.2.4. <A
-HREF="stepbystep.html#INSTALL-PERL"
+HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN768"
>Tweaking <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
></A
></DT
></DT
><DT
>3.5.3. <A
-HREF="geninstall.html#HTACCESS"
+HREF="geninstall.html#htaccess"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files and security</A
></DT
><DT
>3.5.4. <A
-HREF="geninstall.html#MOD_THROTTLE"
+HREF="geninstall.html#mod-throttle"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
-HREF="geninstall.html#CONTENT_TYPE"
+HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
-HREF="geninstall.html#UNIXHISTORY"
+HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A
></DT
></DL
><DL
><DT
>3.6.1. <A
-HREF="win32.html#WININSTALL"
+HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
-HREF="win32.html#ADDLWINTIPS"
+HREF="win32.html#addlwintips"
>Additional Windows Tips</A
></DT
><DT
>3.6.3. <A
-HREF="win32.html#BZLDAP"
+HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A
></DT
></DL
><DL
><DT
>4.2.1. <A
-HREF="useradmin.html#DEFAULTUSER"
+HREF="useradmin.html#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
-HREF="useradmin.html#MANAGEUSERS"
+HREF="useradmin.html#manageusers"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>4.2.2.1. <A
-HREF="useradmin.html#LOGIN"
+HREF="useradmin.html#login"
>Logging In</A
></DT
><DT
>4.2.2.2. <A
-HREF="useradmin.html#CREATENEWUSERS"
+HREF="useradmin.html#createnewusers"
>Creating new users</A
></DT
><DT
>4.2.2.3. <A
-HREF="useradmin.html#DISABLEUSERS"
+HREF="useradmin.html#disableusers"
>Disabling Users</A
></DT
><DT
>4.2.2.4. <A
-HREF="useradmin.html#MODIFYUSERS"
+HREF="useradmin.html#modifyusers"
>Modifying Users</A
></DT
></DL
><DL
><DT
>4.3.1. <A
-HREF="programadmin.html#PRODUCTS"
+HREF="programadmin.html#products"
>Products</A
></DT
><DT
>4.3.2. <A
-HREF="programadmin.html#COMPONENTS"
+HREF="programadmin.html#components"
>Components</A
></DT
><DT
>4.3.3. <A
-HREF="programadmin.html#VERSIONS"
+HREF="programadmin.html#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
-HREF="programadmin.html#MILESTONES"
+HREF="programadmin.html#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
-HREF="programadmin.html#VOTING"
+HREF="programadmin.html#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
-HREF="programadmin.html#GROUPS"
+HREF="programadmin.html#groups"
>Groups and Group Security</A
></DT
></DL
></DT
><DT
>7.2. <A
-HREF="variant_fenris.html"
+HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
-HREF="variant_issuezilla.html"
+HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
-HREF="variant_scarab.html"
+HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
-HREF="variant_perforce.html"
+HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
-HREF="variant_sourceforge.html"
+HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL
><DL
><DT
>C.2.1. <A
-HREF="dbdoc.html#AEN2331"
+HREF="dbdoc.html#AEN2340"
>Bugzilla Database Basics</A
></DT
><DD
><DL
><DT
>C.2.1.1. <A
-HREF="dbdoc.html#AEN2360"
+HREF="dbdoc.html#AEN2369"
>Bugzilla Database Tables</A
></DT
></DL
>D.1. <A
HREF="rewrite.html"
>Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</A
></DT
><DL
><DT
>D.5.1. <A
-HREF="bzhacking.html#AEN2495"
+HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
-HREF="bzhacking.html#AEN2509"
+HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A
></DT
></DL
><DL
><DT
>0. <A
-HREF="gfdl_0.html"
+HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
-HREF="gfdl_1.html"
+HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
-HREF="gfdl_2.html"
+HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
-HREF="gfdl_3.html"
+HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
-HREF="gfdl_4.html"
+HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
-HREF="gfdl_5.html"
+HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
-HREF="gfdl_6.html"
+HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
-HREF="gfdl_7.html"
+HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
-HREF="gfdl_8.html"
+HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
-HREF="gfdl_9.html"
+HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
-HREF="gfdl_10.html"
+HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
-HREF="gfdl_howto.html"
+HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
></DT
><DT
>3-3. <A
-HREF="win32.html#AEN1038"
+HREF="win32.html#AEN1048"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
-HREF="win32.html#AEN1224"
+HREF="win32.html#AEN1233"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
-HREF="programadmin.html#AEN1461"
+HREF="programadmin.html#AEN1470"
>Creating some Components</A
></DT
><DT
>4-2. <A
-HREF="programadmin.html#AEN1490"
+HREF="programadmin.html#AEN1499"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
-HREF="programadmin.html#AEN1494"
+HREF="programadmin.html#AEN1503"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
-HREF="programadmin.html#AEN1522"
+HREF="programadmin.html#AEN1531"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
-HREF="programadmin.html#AEN1558"
+HREF="programadmin.html#AEN1567"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
-HREF="programadmin.html#AEN1575"
+HREF="programadmin.html#AEN1584"
>Creating a New Group</A
></DT
><DT
>4-7. <A
-HREF="programadmin.html#AEN1592"
+HREF="programadmin.html#AEN1601"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
-HREF="setperl.html#AEN2439"
+HREF="setperl.html#AEN2448"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
-HREF="glossary.html#AEN2736"
+HREF="glossary.html#AEN2769"
>A Sample Product</A
></DT
></DL
TITLE="Using Bugzilla-Conclusion"
HREF="usingbz-conc.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INIT4ME"
+NAME="init4me"
>2.4. Where can I find my user preferences?</A
></H1
><TABLE
></TR
></TABLE
><P
-> Customized User Preferences offer tremendous versatility to your
+> Customized User Preferences offer tremendous versatility to your
individual Bugzilla experience. Let's plunge into what you can
do! The first step is to click the "Edit prefs" link at the
footer of each page once you have logged in to <A
>.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ACCOUNTSETTINGS"
+NAME="accountsettings"
>2.4.1. Account Settings</A
></H2
><P
-> On this page, you can change your basic Account Settings,
+> On this page, you can change your basic Account Settings,
including your password and full name. For security reasons,
in order to change anything on this page you must type your
<EM
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="EMAILSETTINGS"
+NAME="emailsettings"
>2.4.2. Email Settings</A
></H2
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NOTIFICATION"
+NAME="notification"
>2.4.2.1. Email Notification</A
></H3
><P
-> Here you can reduce or increase the amount of email sent you
+> Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as
<SPAN
CLASS="QUOTE"
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NEWEMAILTECH"
+NAME="newemailtech"
>2.4.2.2. New Email Technology</A
></H3
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This option may not be available in all Bugzilla
+> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
></TABLE
></DIV
><P
-> Disregard the warnings about "experimental and bleeding
+> Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and
well-tested now.
</P
><P
-> I recommend you enable the option, "Click here to sign up
+> I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WATCHSETTINGS"
+NAME="watchsettings"
>2.4.2.3. "Watching" Users</A
></H3
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This option may not be available in all Bugzilla
+> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
></TABLE
></DIV
><P
-> By entering user email names into the "Users to watch" text
+> By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="FOOTERSETTINGS"
+NAME="footersettings"
>2.4.3. Page Footer</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> By default, this page is quite barren. However, go explore
+> By default, this page is quite barren. However, go explore
the Query Page some more; you will find that you can store
numerous queries on the server, so if you regularly run a
particular query it is just a drop-down menu away. On this
></TABLE
></DIV
><P
-> If you have many stored queries on the server, here you will
+> If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful
is an excellent way to impress your boss...
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PERMISSIONSETTINGS"
+NAME="permissionsettings"
>2.4.4. Permissions</A
></H2
><P
-> This is a purely informative page which outlines your current
+> This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer.
TITLE="ERRATA"
HREF="errata.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="INSTALLATION"
+NAME="installation"
>Chapter 3. Installation</A
></H1
><DIV
></DT
><DT
>3.2.3. <A
-HREF="stepbystep.html#INSTALL-MYSQL"
+HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A
></DT
><DT
>3.2.4. <A
-HREF="stepbystep.html#INSTALL-PERL"
+HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN768"
>Tweaking <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
></A
></DT
></DT
><DT
>3.5.3. <A
-HREF="geninstall.html#HTACCESS"
+HREF="geninstall.html#htaccess"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
> files and security</A
></DT
><DT
>3.5.4. <A
-HREF="geninstall.html#MOD_THROTTLE"
+HREF="geninstall.html#mod-throttle"
><TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
-HREF="geninstall.html#CONTENT_TYPE"
+HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
-HREF="geninstall.html#UNIXHISTORY"
+HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A
></DT
></DL
><DL
><DT
>3.6.1. <A
-HREF="win32.html#WININSTALL"
+HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
-HREF="win32.html#ADDLWINTIPS"
+HREF="win32.html#addlwintips"
>Additional Windows Tips</A
></DT
><DT
>3.6.3. <A
-HREF="win32.html#BZLDAP"
+HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A
></DT
></DL
></DL
></DIV
><P
-> These installation instructions are presented assuming you are
+> These installation instructions are presented assuming you are
installing on a UNIX or completely POSIX-compliant system. If
you are installing on Microsoft Windows or another oddball
operating system, please consult the appropriate sections in
TITLE="Bonsai"
HREF="bonsai.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="INTEGRATION"
+NAME="integration"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</A
></H1
><DIV
TITLE="Credits"
HREF="credits.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="NEWVERSIONS"
+NAME="newversions"
>1.4. New Versions</A
></H1
><P
-> This is the 2.14 version of The Bugzilla Guide. If you are
+> This is the 2.14 version of The Bugzilla Guide. 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
-> This document can be found in the following places:
+> This document can be found in the following places:
</P
><P
-> <P
></P
><UL
><LI
><P
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>TriloBYTE</A
></LI
><LI
><P
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
>Mozilla.org</A
></LI
><LI
><P
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>The Linux
>
</P
><P
-> The latest version of this document can be checked out via CVS.
+> The latest version of this document can be checked out via CVS.
Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
TITLE="BSD Installation Notes"
HREF="bsdinstall.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="OSX"
+NAME="osx"
>3.3. Mac OS X Installation Notes</A
></H1
><P
-> There are a lot of common libraries and utilities out there
+> 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
+> 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
+> Follow the instructions for setting up Fink. Once it's
installed, you'll want to run the following as root:
<B
-CLASS="COMMAND"
+CLASS="command"
>fink install gd</B
>
</P
><P
-> It will prompt you for a number of dependencies, type 'y' and
+> 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
+> 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
:-)
</P
><P
-> Instead of typing <SPAN
+> Instead of typing <SPAN
CLASS="QUOTE"
>"install GD"</SPAN
> at the
<TT
-CLASS="PROMPT"
+CLASS="prompt"
>cpan></TT
> prompt, type <B
-CLASS="COMMAND"
+CLASS="command"
>look
GD</B
>. This should go through the motions of
open a shell and drop you into the build directory. Apply the
following patch to the Makefile.PL file (save the patch into a
file and use the command <B
-CLASS="COMMAND"
+CLASS="command"
>patch <
patchfile</B
>:
</P
><P
-> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->
+CLASS="programlisting"
+>
+
--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
+++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
@@ -3,8 +3,8 @@
>
</P
><P
-> Then, run these commands to finish the installation of the perl module:
+> Then, run these commands to finish the installation of the perl module:
<P
></P
><TABLE
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.PL</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make test</B
></TD
></TR
><TR
><TD
><B
-CLASS="COMMAND"
+CLASS="command"
>make install</B
></TD
></TR
><TR
><TD
>And don't forget to run <B
-CLASS="COMMAND"
+CLASS="command"
>exit</B
> to get back to cpan.</TD
></TR
>
</P
><P
-> Happy Hacking!
+> Happy Hacking!
</P
></DIV
><DIV
TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"></HEAD
><BODY
-CLASS="APPENDIX"
+CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="APPENDIX"
+CLASS="appendix"
><H1
><A
-NAME="PATCHES"
+NAME="patches"
>Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1
><DIV
>D.1. <A
HREF="rewrite.html"
>Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</A
></DT
><DL
><DT
>D.5.1. <A
-HREF="bzhacking.html#AEN2495"
+HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
-HREF="bzhacking.html#AEN2509"
+HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A
></DT
></DL
ALIGN="right"
VALIGN="top"
>Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</TD
></TR
TITLE="User Administration"
HREF="useradmin.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="POSTINSTALL-CHECK"
+NAME="postinstall-check"
>4.1. Post-Installation Checklist</A
></H1
><P
-> After installation, follow the checklist below to help ensure
+> After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Bring up <TT
-CLASS="FILENAME"
+> Bring up <TT
+CLASS="filename"
>editparams.cgi</TT
> in your web
browser. This should be available as the <SPAN
will be sent with the maintainer as the return email
address.</P
><P
-> Set <SPAN
+> Set <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> to <EM
qualified domain name and web server path to your Bugzilla
installation.</P
><P
-> For example, if your bugzilla query page is
+> For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<SPAN
CLASS="QUOTE"
which groups of users are allowed to see and edit the
bug.</P
><P
-> Set "usebuggroups" to "on" <EM
+> Set "usebuggroups" to "on" <EM
>only</EM
> if you
may wish to restrict access to products. I suggest leaving
></LI
><LI
><P
-> <SPAN
+> <SPAN
CLASS="QUOTE"
>"usebuggroupsentry"</SPAN
>, when set to
installations where product isolation is a necessity.
</P
><P
-> Set "usebuggroupsentry" to "on" if you absolutely need to
+> Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
></LI
><LI
><P
-> You run into an interesting problem when Bugzilla reaches a
+> 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
extremely high-traffic Bugzilla databases.
</P
><P
-> Set "shadowdb" to "bug_shadowdb" if you will be running a
+> Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
enables many simultaneous users to read and write to the
database without interfering with one another.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Enabling "shadowdb" can adversely affect the stability
+> 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
comments per day.
</P
><P
-> If you use the "shadowdb" option, it is only natural that
+> 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!
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <TT
-CLASS="FILENAME"
+CLASS="filename"
>data/params</TT
> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <TT
-CLASS="FILENAME"
+CLASS="filename"
>data/params</TT
> file.</P
><P
-> If you have custom logos or HTML you must put in place to
+> If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
or "blurbhtml" text boxes.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The "headerhtml" text box is the HTML printed out
+> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page,
is read as the text to send to the new user along with their
password message.</P
><P
-> Add any text you wish to the "passwordmail" parameter box.
+> 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
their status even more than that which can be indicated by
the Resolution fields.</P
><P
-> Do you want to use the QA Contact ("useqacontact") and
+> Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
></LI
><LI
><P
-> Set "whinedays" to the amount of days you want to let bugs
+> Set "whinedays" to the amount 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
require that most other changes come with an
explanation.</P
><P
-> Set the "commenton" options according to your site policy.
+> 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"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It is generally far better to require a developer
+> 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
security to prevent snooping, watchers are not a good
idea.</P
><P
-> However, for most sites you should set
+> However, for most sites you should set
<SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
TITLE="Bugzilla Security"
HREF="security.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PROGRAMADMIN"
+NAME="programadmin"
>4.3. Product, Component, Milestone, and Version
Administration</A
></H1
></TR
></TABLE
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="PRODUCTS"
+NAME="products"
>4.3.1. Products</A
></H2
><FONT
>Formerly, and in some spots still, called
"Programs"</FONT
><P
-HREF="glossary.html#GLOSS_PRODUCT"
+HREF="glossary.html#gloss-product"
><I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>Products</I
></A
> are
products (website, meetings...)
</P
><P
-> A Product (formerly called "Program", and still referred to
+> A Product (formerly called "Program", and still referred to
that way in some portions of the source code) controls some
very important functions. The number of "votes" available for
users to vote for the most important bugs is set per-product,
TYPE="1"
><LI
><P
-> Select "components" from the yellow footer
+> Select "components" from the yellow footer
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It may seem counterintuitive to click "components" when
+> It may seem counterintuitive to click "components" when
you want to edit the properties associated with
Products. This is one of a long list of things we want
in Bugzilla 3.0...
></LI
><LI
><P
-> Select the "Add" link to the right of "Add a new product".
+> Select the "Add" link to the right of "Add a new product".
</P
></LI
><LI
><P
-> Enter the name of the product and a description. The
+> Enter the name of the product and a description. The
Description field is free-form.
</P
></LI
></OL
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't worry about the "Closed for bug entry", "Maximum Votes
+> 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
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="COMPONENTS"
+NAME="components"
>4.3.2. Components</A
></H2
><P
-> Components are subsections of a Product.
+> Components are subsections of a Product.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1461"
+NAME="AEN1470"
></A
><P
><B
>Example 4-1. Creating some Components</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1463"
+NAME="AEN1472"
></A
><P
></P
><P
-> The computer game you are designing may have a "UI"
+> 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
to the Component.
</P
><P
-> To create a new Component:
+> To create a new Component:
</P
><P
></P
TYPE="1"
><LI
><P
-> Select the "Edit components" link from the "Edit product"
+> Select the "Edit components" link from the "Edit product"
page
</P
></LI
><LI
><P
-> Select the "Add" link to the right of the "Add a new
+> Select the "Add" link to the right of the "Add a new
component" text on the "Select Component" page.
</P
></LI
><LI
><P
-> Fill out the "Component" field, a short "Description", and
+> Fill out the "Component" field, a short "Description", and
the "Initial Owner". The Component and Description fields
are free-form; the "Initial Owner" field must be that of a
user ID already existing in the database. If the initial
owner does not exist, Bugzilla will refuse to create the
component.
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Is your "Default Owner" a user who is not yet in the
+> Is your "Default Owner" a user who is not yet in the
database? No problem.
<P
></P
TYPE="a"
><LI
><P
-> Select the "Log out" link on the footer of the
+> Select the "Log out" link on the footer of the
page.
</P
></LI
><LI
><P
-> Select the "New Account" link on the footer of
+> Select the "New Account" link on the footer of
the "Relogin" page
</P
></LI
><LI
><P
-> Type in the email address of the default owner
+> Type in the email address of the default owner
you want to create in the "E-mail address"
field, and her full name in the "Real name"
field, then select the "Submit Query" button.
></LI
><LI
><P
-> Now select "Log in" again, type in your login
+> Now select "Log in" again, type in your login
information, and you can modify the product to
use the Default Owner information you require.
</P
></LI
><LI
><P
-> Either Edit more components or return to the Bugzilla
+> Either Edit more components or return to the Bugzilla
Query Page. To return to the Product you were editing, you
must select the Components link as before.
</P
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VERSIONS"
+NAME="versions"
>4.3.3. Versions</A
></H2
><P
-> Versions are the revisions of the product, such as "Flinders
+> Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Using Versions
helps you isolate code changes and are an aid in reporting.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1490"
+NAME="AEN1499"
></A
><P
><B
>Example 4-2. Common Use of Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1492"
+NAME="AEN1501"
></A
><P
></P
><P
-> A user reports a bug against Version "Beta 2.0" of your
+> A user reports a bug against Version "Beta 2.0" of your
product. The current Version of your software is
"Release Candidate 1", and no longer has the bug. This
will help you triage and classify bugs according to
></DIV
>
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1494"
+NAME="AEN1503"
></A
><P
><B
>Example 4-3. A Different Use of Versions</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1496"
+NAME="AEN1505"
></A
><P
></P
><P
-> This field has been used to good effect by an online
+> This field has been used to good effect by an online
service provider in a slightly different way. They had
three versions of the product: "Production", "QA", and
"Dev". Although it may be the same product, a bug in
>
</P
><P
-> To create and edit Versions:
+> To create and edit Versions:
</P
><P
></P
TYPE="1"
><LI
><P
-> From the "Edit product" screen, select "Edit Versions"
+> From the "Edit product" screen, select "Edit Versions"
</P
></LI
><LI
><P
-> You will notice that the product already has the default
+> You will notice that the product already has the default
version "undefined". If your product doesn't use version
numbers, you may want to leave this as it is or edit it so
that it is "---". You can then go back to the edit
versions page and add new versions to your product.
</P
><P
-> Otherwise, click the "Add" button to the right of the "Add
+> Otherwise, click the "Add" button to the right of the "Add
a new version" text.
</P
></LI
><LI
><P
-> Enter the name of the Version. This can be free-form
+> Enter the name of the Version. This can be free-form
characters up to the limit of the text box. Then select
the "Add" button.
</P
></LI
><LI
><P
-> At this point you can select "Edit" to edit more Versions,
+> At this point you can select "Edit" to edit more Versions,
or return to the "Query" page, from which you can navigate
back to the product through the "components" link at the
foot of the Query page.
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MILESTONES"
+NAME="milestones"
>4.3.4. Milestones</A
></H2
><P
-> Milestones are "targets" that you plan to get a bug fixed by.
+> 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. Or, you
have a bug that you plan to fix for 2.8, this would have a
milestone of 2.8.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Milestone options will only appear for a Product if you
+> Milestone options will only appear for a Product if you
turned the "usetargetmilestone" field in the "Edit
Parameters" screen "On".
</P
></TABLE
></DIV
><P
-> To create new Milestones, set Default Milestones, and set
+> To create new Milestones, set Default Milestones, and set
Milestone URL:
</P
><P
TYPE="1"
><LI
><P
-> Select "edit milestones"
+> Select "edit milestones"
</P
></LI
><LI
><P
-> Select "Add" to the right of the "Add a new milestone"
+> Select "Add" to the right of the "Add a new milestone"
text
</P
></LI
><LI
><P
-> Enter the name of the Milestone in the "Milestone" field.
+> 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. Select "Add".
</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1522"
+NAME="AEN1531"
></A
><P
><B
>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1524"
+NAME="AEN1533"
></A
><P
></P
><P
-> Let's say you create a target milestone called
+> Let's say you create a target milestone called
"Release 1.0", with Sortkey set to "0". Later, you
realize that you will have a public beta, called
"Beta1". You can create a Milestone called "Beta1",
></LI
><LI
><P
-> If you want to add more milestones, select the "Edit"
+> If you want to add more milestones, select the "Edit"
link. If you don't, well shoot, you have to go back to the
"query" page and select "components" again, and make your
way back to the Product you were editing.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This is another in the list of unusual user interface
+> This is another in the list of unusual user interface
decisions that we'd like to get cleaned up. Shouldn't
there be a link to the effect of "edit the Product I
was editing when I ended up here"? In any case,
></LI
><LI
><P
-> From the Edit product screen again (once you've made your
+> From the Edit product screen again (once you've made your
way back), enter the URL for a description of what your
milestones are for this product in the "Milestone URL"
field. It should be of the format
"http://www.foo.com/bugzilla/product_milestones.html"
</P
><P
-> Some common uses of this field include product
+> Some common uses of this field include product
descriptions, product roadmaps, and of course a simple
description of the meaning of each milestone.
</P
></LI
><LI
><P
-> If you're using Target Milestones, the "Default Milestone"
+> If you're using Target Milestones, the "Default Milestone"
field must have some kind of entry. If you really don't
care if people set coherent Target Milestones, simply
leave this at the default, "---". However, controlling
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="VOTING"
+NAME="voting"
>4.3.5. Voting</A
></H2
><P
-> The concept of "voting" is a poorly understood, yet powerful
+> The concept of "voting" is a poorly understood, yet powerful
feature for the management of open-source projects. Each user
is assigned so many Votes per product, which they can freely
reassign (or assign multiple votes to a single bug). This
attention so they don't sit for a long time awaiting triage.
</P
><P
-> The daunting challenge of Votes is deciding where you draw the
+> The daunting challenge of Votes is deciding where you draw the
line for a "vocal majority". If you only have a user base of
100 users, setting a low threshold for bugs to move from
UNCONFIRMED to NEW makes sense. As the Bugzilla user base
TYPE="1"
><LI
><P
-> Navigate to the "Edit product" screen for the Product you
+> Navigate to the "Edit product" screen for the Product you
wish to modify
</P
></LI
><LI
><P
-> Set "Maximum Votes per person" to your calculated value.
+> Set "Maximum Votes per person" to your calculated value.
Setting this field to "0" disables voting.
</P
></LI
><LI
><P
-> Set "Maximum Votes a person can put on a single bug" to
+> Set "Maximum Votes a person can put on a single bug" to
your calculated value. It should probably be some number
lower than the "Maximum votes per person". Setting this
field to "0" disables voting, but leaves the voting
></LI
><LI
><P
-> Set "Number of votes a bug in this product needs to
+> Set "Number of votes a bug in this product needs to
automatically get out of the UNCONFIRMED state" to your
calculated number. Setting this field to "0" disables
the automatic move of bugs from UNCONFIRMED to NEW. Some
Votes if your Bugzilla user base is unable to affect which
bugs appear on Development radar?
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You should probably set this number to higher than a
+> You should probably set this number to higher than a
small coalition of Bugzilla users can influence it.
Most sites use this as a "referendum" mechanism -- if
users are able to vote a bug out of UNCONFIRMED, it is
></LI
><LI
><P
-> Once you have adjusted the values to your preference,
+> Once you have adjusted the values to your preference,
select the "Update" button.
</P
></LI
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="GROUPS"
+NAME="groups"
>4.3.6. Groups and Group Security</A
></H2
><P
-> Groups can be very useful in bugzilla, because they allow
+> Groups can be very useful in bugzilla, because they allow
users to isolate bugs or products that should only be seen by
certain people. Groups can also be a complicated minefield of
interdependencies and weirdness if mismanaged.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1558"
+NAME="AEN1567"
></A
><P
><B
>Example 4-5. When to Use Group Security</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1560"
+NAME="AEN1569"
></A
><P
></P
><P
-> Many Bugzilla sites isolate "Security-related" bugs from
+> Many Bugzilla sites isolate "Security-related" bugs from
all other bugs. This way, they can have a fix ready
before the security vulnerability is announced to the
world. You can create a "Security" product which, by
into two categories: Generic and Product-Based.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Groups in Bugzilla are a complicated beast that evolved out
+> Groups in Bugzilla are a complicated beast that evolved out
of very simple user permission bitmasks, apparently itself
derived from common concepts in UNIX access controls. A
"bitmask" is a fixed-length number whose value can describe
next 32, etc.
</P
><P
-> Similarly, Bugzilla offers a bitmask to define group
+> Similarly, Bugzilla offers a bitmask to define group
permissions, with an internal limit of 64. Several are
already occupied by built-in permissions. The way around
this limitation is to avoid assigning groups to products if
></TABLE
></DIV
><P
-> To enable Generic Group Security ("usebuggroups"):
+> To enable Generic Group Security ("usebuggroups"):
</P
><P
></P
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
</P
></LI
><LI
><P
-> You will generally have no groups set up. Select the
+> You will generally have no groups set up. Select the
"groups" link in the footer.
</P
></LI
><LI
><P
-> Take a moment to understand the instructions on the "Edit
+> Take a moment to understand the instructions on the "Edit
Groups" screen. Once you feel confident you understand
what is expected of you, select the "Add Group" link.
</P
></LI
><LI
><P
-> Fill out the "New Name" (remember, no spaces!), "New
+> Fill out the "New Name" (remember, no spaces!), "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.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1575"
+NAME="AEN1584"
></A
><P
><B
>Example 4-6. Creating a New Group</B
></P
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
-NAME="AEN1577"
+NAME="AEN1586"
></A
><P
></P
><P
-> I created a group called DefaultGroup with a
+> I created a group called DefaultGroup with a
description of <SPAN
CLASS="QUOTE"
>"This is simply a group to play
></LI
></OL
><P
-> To enable Product-Based Group Security (usebuggroupsentry):
+> To enable Product-Based Group Security (usebuggroupsentry):
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't forget that you only have 64 groups masks available,
+> Don't forget that you only have 64 groups masks available,
total, for your installation of Bugzilla! If you plan on
having more than 50 products in your individual Bugzilla
installation, and require group security for your products,
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
"Edit Parameters" screen.
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
-WIDTH="90%"
+CLASS="warning"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> "usebuggroupsentry" has the capacity to prevent the
+> "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
></LI
><LI
><P
-> You will generally have no Groups set up, unless you
+> You will generally have no Groups set up, unless you
enabled "usebuggroupsentry" prior to creating any
Products. To create "Generic Group Security" groups,
follow the instructions given above. To create
></LI
></OL
><P
-> You may find this example illustrative for how bug groups work.
+> You may find this example illustrative for how bug groups work.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1592"
+NAME="AEN1601"
></A
><P
><B
>Example 4-7. Bugzilla Groups</B
></P
><P
-CLASS="LITERALLAYOUT"
->Bugzilla Groups example<br>
+CLASS="literallayout"
+><br>
+Bugzilla Groups example<br>
-----------------------<br>
<br>
For this example, let us suppose we have four groups, call them<br>
TITLE="Hacking Bugzilla"
HREF="bzhacking.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="QUICKSEARCH"
+NAME="quicksearch"
>D.4. The Quicksearch Utility</A
></H1
><P
-> Quicksearch is a new, experimental feature of the 2.12 release.
+> Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</P
><P
-> The index.html page has been updated to include the QuickSearch
+> The index.html page has been updated to include the QuickSearch
text box.
</P
><P
-> To take full advantage of the query power, the Bugzilla
+> To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</P
><P
-> Currently, keywords must be hard-coded in localconfig.js. If
+> Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
but not those with the keyword "foo".
</P
><P
-> Workarounds for Bugzilla users:
+> Workarounds for Bugzilla users:
<P
></P
><TABLE
>
</P
><P
-> When this tool is ported from client-side JavaScript to
+> When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="REWRITE"
+NAME="rewrite"
>D.1. Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</A
></H1
><P
>Apache's <TT
-CLASS="FILENAME"
+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
TYPE="1"
><LI
><P
-> Make it so if someone types
+> Make it so if someone types
<TT
-CLASS="COMPUTEROUTPUT"
+CLASS="computeroutput"
>http://www.foo.com/12345</TT
>,
Bugzilla spits back
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
-WIDTH="90%"
+WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-><VirtualHost 12.34.56.78>
+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
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Loki Bugzilla (Fenris)"
-HREF="variant_fenris.html"></HEAD
+HREF="variant-fenris.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="variant_fenris.html"
+HREF="variant-fenris.html"
>Next</A
></TD
></TR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="RHBUGZILLA"
+NAME="rhbugzilla"
>7.1. Red Hat Bugzilla</A
></H1
><P
-> Red Hat Bugzilla is probably the most popular Bugzilla variant
+> Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
ALIGN="right"
VALIGN="top"
><A
-HREF="variant_fenris.html"
+HREF="variant-fenris.html"
>Next</A
></TD
></TR
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SCM"
+NAME="scm"
>5.3. Perforce SCM</A
></H1
><P
-> You can find the project page for Bugzilla and Teamtrack
+> You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
>.
</P
><P
-> Integration of Perforce with Bugzilla, once patches are applied,
+> 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
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SECURITY"
+NAME="security"
>4.4. Bugzilla Security</A
></H1
><TABLE
></TR
></TABLE
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Poorly-configured MySQL, Bugzilla, and FTP installations have
+> Poorly-configured MySQL, Bugzilla, and FTP 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
></TABLE
></DIV
><P
-> Secure your installation.
+> Secure your installation.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> These instructions must, of necessity, be somewhat vague
+> These instructions must, of necessity, be somewhat vague
since Bugzilla runs on so many different platforms. If you
have refinements of these directions for specific platforms,
please submit them to <A
TYPE="1"
><LI
><P
-> Ensure you are running at least MysQL version 3.22.32 or
+> Ensure you are running at least MysQL version 3.22.32 or
newer. Earlier versions had notable security holes and
poorly secured default configuration choices.
</P
> The MySQL Privilege System</A
> until you can recite it from memory!</P
><P
-> At the very least, ensure you password the "mysql -u root"
+> At the very least, ensure you password the "mysql -u root"
account and the "bugs" account, establish grant table
rights (consult the Keystone guide in Appendix C: The
Bugzilla Database for some easy-to-use details) that do
></LI
><LI
><P
-> Lock down /etc/inetd.conf. Heck, disable inet entirely on
+> Lock down /etc/inetd.conf. Heck, disable inet entirely on
this box. It should only listen to port 25 for Sendmail
and port 80 for Apache.
</P
></LI
><LI
><P
-> Do not run Apache as <SPAN
+> Do not run Apache as <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>. This will
Run it, instead, as a user with a name, set via your
httpd.conf file.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <SPAN
+> <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> is a real user on UNIX systems.
></LI
><LI
><P
-> Ensure you have adequate access controls for the
+> Ensure you have adequate access controls for the
$BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
directories, as well as the $BUGZILLA_HOME/localconfig and
$BUGZILLA_HOME/globals.pl files. The localconfig file
bug information to those who may not be allowed to see it.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla provides default .htaccess files to protect the
+> Bugzilla provides default .htaccess files to protect the
most common Apache installations. However, you should
verify these are adequate according to the site-wide
security policy of your web server, and ensure that the
details.
</P
><P
-> If you are using a web server that does not support the
+> If you are using a web server that does not support the
.htaccess control method, <EM
>you are at
risk!</EM
></TABLE
></DIV
><P
-> On Apache, you can use .htaccess files to protect access
+> On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
TARGET="_top"
> for adequate protection in your data/ and shadow/ directories.
</P
><P
-> Note the instructions which follow are Apache-specific.
+> Note the instructions which follow are Apache-specific.
If you use IIS, Netscape, or other non-Apache web servers,
please consult your system documentation for how to secure
these files from being transmitted to curious users.
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> <Files comments> allow<br>
from all </Files> deny from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> <Files localconfig> deny<br>
from all </Files> allow from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess",
+> Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/shadow
directory. <P
-CLASS="LITERALLAYOUT"
+CLASS="literallayout"
> deny from all </P
>
</P
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="SETPERL"
+NAME="setperl"
>D.2. The setperl.csh Utility</A
></H1
><P
search path on your system, it will not work!
</P
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
-> Download the "setperl.csh" utility to your Bugzilla
+> Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>cd /your/path/to/bugzilla</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>chmod
u+x setperl.csh</B
> </TT
></LI
><LI
><P
-> Prepare (and fix) Bugzilla file permissions.
+> Prepare (and fix) Bugzilla file permissions.
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod u+w *</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>chmod
u+x duplicates.cgi</B
> </TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>chmod a-x bug_status.html</B
>
</TT
></LI
><LI
><P
-> Run the script:
+> Run the script:
</P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN2439"
+NAME="AEN2448"
></A
><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./setperl.csh /usr/bin/perl</B
>
</TT
ALIGN="left"
VALIGN="top"
>Apache <TT
-CLASS="FILENAME"
+CLASS="filename"
>mod_rewrite</TT
> magic</TD
><TD
TITLE="Mac OS X Installation Notes"
HREF="osx.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="STEPBYSTEP"
+NAME="stepbystep"
>3.2. Step-by-step Install</A
></H1
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN509"
>3.2.1. Introduction</A
></H2
><P
-> Installation of bugzilla is pretty straightforward, particularly if your
+> Installation of bugzilla is pretty straightforward, particularly if your
machine already has MySQL and the MySQL-related perl packages installed.
If those aren't installed yet, then that's the first order of business. The
other necessary ingredient is a web server set up to run cgi scripts.
While using Apache for your webserver is not required, it is recommended.
</P
><P
-> Bugzilla has been successfully installed under Solaris, Linux,
+> Bugzilla has been successfully installed under Solaris, Linux,
and Win32. The peculiarities of installing on Win32 (Microsoft
Windows) are not included in this section of the Guide; please
check out the <A
on getting Bugzilla to work on Microsoft Windows.
</P
><P
-> The Bugzilla Guide is contained in the "docs/" folder in your
+> The Bugzilla Guide is contained in the "docs/" folder in your
Bugzilla distribution. It is available in plain text
(docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN515"
>3.2.2. Installing the Prerequisites</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
most recent version of Perl and MySQL (both the executables
and development libraries) on your system, check out
Bundle::Bugzilla in <A
-HREF="stepbystep.html#BUNDLEBUGZILLA"
+HREF="stepbystep.html#bundlebugzilla"
>Using Bundle::Bugzilla instead of manually installing Perl modules</A
></P
></TD
></TABLE
></DIV
><P
-> The software packages necessary for the proper running of bugzilla are:
+> The software packages necessary for the proper running of bugzilla are:
<P
></P
><OL
TYPE="1"
><LI
><P
-> MySQL database server and the mysql client (3.22.5 or greater)
+> MySQL database server and the mysql client (3.22.5 or greater)
</P
></LI
><LI
><P
-> Perl (5.004 or greater, 5.6.1 is recommended if you wish
+> Perl (5.004 or greater, 5.6.1 is recommended if you wish
to use Bundle::Bugzilla)
</P
></LI
><LI
><P
-> DBI Perl module
+> DBI Perl module
</P
></LI
><LI
><P
-> Data::Dumper Perl module
+> Data::Dumper Perl module
</P
></LI
><LI
><P
-> Bundle::Mysql Perl module collection
+> Bundle::Mysql Perl module collection
</P
></LI
><LI
><P
-> TimeDate Perl module collection
+> TimeDate Perl module collection
</P
></LI
><LI
><P
-> GD perl module (1.8.3) (optional, for bug charting)
+> GD perl module (1.8.3) (optional, for bug charting)
</P
></LI
><LI
><P
-> Chart::Base Perl module (0.99c) (optional, for bug charting)
+> Chart::Base Perl module (0.99c) (optional, for bug charting)
</P
></LI
><LI
><P
-> DB_File Perl module (optional, for bug charting)
+> DB_File Perl module (optional, for bug charting)
</P
></LI
><LI
><P
-> The web server of your choice. Apache is recommended.
+> The web server of your choice. Apache is recommended.
</P
></LI
><LI
><P
-> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</P
></LI
></OL
>
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> It is a good idea, while installing Bugzilla, to ensure it
+> It is a good idea, while installing Bugzilla, to ensure it
is not <EM
>accessible</EM
> by other machines
></DIV
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
every required and optional library for Bugzilla. The
easiest way to install them is by using the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>urpmi</TT
> utility. If you follow these
commands, you should have everything you need for
Bugzilla, and <TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
> should
not complain about any missing libraries. You may already
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-mysql</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-chart</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-gd</B
></TD
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
perl-MailTools</B
> (for Bugzilla email
><TR
><TD
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
><B
-CLASS="COMMAND"
+CLASS="command"
> urpmi
apache-modules</B
></TD
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INSTALL-MYSQL"
+NAME="install-mysql"
>3.2.3. Installing MySQL Database</A
></H2
><P
->
Visit MySQL homepage at <A
+>
Visit MySQL homepage at <A
HREF="http://www.mysql.com"
TARGET="_top"
>www.mysql.com</A
> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT
-CLASS="FILENAME"
+CLASS="filename"
>/var</TT
> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
-CLASS="FILENAME"
+CLASS="filename"
>configure</TT
>.
</P
><P
-> If you install from source or non-package (RPM, deb, etc.)
+> If you install from source or non-package (RPM, deb, etc.)
binaries you need to add
<I
-CLASS="FIRSTTERM"
+CLASS="firstterm"
>mysqld</I
> 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.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><P
>You should have your init script start
<I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>mysqld</I
> with the ability to accept
large packets. By default, <TT
-CLASS="FILENAME"
+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"
+CLASS="option"
>-O
max_allowed_packet=1M</TT
> to the command that starts
<TT
-CLASS="FILENAME"
+CLASS="filename"
>mysqld</TT
> (or
<TT
-CLASS="FILENAME"
+CLASS="filename"
>safe_mysqld</TT
>), then you will be able
to have attachments up to about 1 megabyte.</P
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you plan on running Bugzilla and MySQL on the same
+> If you plan on running Bugzilla and MySQL on the same
machine, consider using the <TT
-CLASS="OPTION"
+CLASS="option"
>--skip-networking</TT
>
option in the init script. This enhances security by
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="INSTALL-PERL"
+NAME="install-perl"
>3.2.4. Perl (5.004 or greater)</A
></H2
><P
-> Any machine that doesn't have perl on it is a sad machine
+> Any machine that doesn't have perl on it is a sad machine
indeed. Perl for *nix systems can be gotten in source form
from http://www.perl.com. Although Bugzilla runs with most
post-5.004 versions of Perl, it's a good idea to be up to the
this writing, that is perl version 5.6.1.
</P
><P
-> Perl is now a far cry from the the single compiler/interpreter
+> Perl is now a far cry from the the single compiler/interpreter
binary it once was. It includes a great many required modules
and quite a few other support files. If you're not up to or
not inclined to build perl from source, you'll want to install
isn't up to snuff.
</P
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
></TABLE
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><A
-NAME="BUNDLEBUGZILLA"
+NAME="bundlebugzilla"
></A
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You can skip the following Perl module installation steps by
+> You can skip the following Perl module installation steps by
installing <SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>Bundle::Bugzilla</SPAN
> from
<A
-HREF="glossary.html#GLOSS_CPAN"
+HREF="glossary.html#gloss-cpan"
><I
-CLASS="GLOSSTERM"
+CLASS="glossterm"
>CPAN</I
></A
>, which
version of Perl (at this writing, version 5.6.1)
</P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>perl -MCPAN
-e 'install "Bundle::Bugzilla"'</B
>
>
</P
><P
-> Bundle::Bugzilla doesn't include GD, Chart::Base, or
+> 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.
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN602"
>3.2.5. DBI Perl Module</A
></H2
><P
-> The DBI module is a generic Perl module used by other database related
+> The DBI module is a generic Perl module used by other database related
Perl modules. For our purposes it's required by 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
><P
-> Like almost all Perl modules DBI can be found on the Comprehensive Perl
+> Like almost all Perl modules DBI can be found on the Comprehensive Perl
Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
real tendency to bog down, so please use mirrors. The current location
at the time of this writing can be found in <A
>.
</P
><P
-> Quality, general Perl module installation instructions can be found on
+> 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.
</P
><P
-> To use the CPAN shell to install DBI:
+> To use the CPAN shell to install DBI:
<DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN609"
></A
><P
></P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl -MCPAN -e 'install "DBI"'</B
>
</TT
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>
To do it the hard way:
<DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="informalexample"
><A
NAME="AEN616"
></A
><P
></P
><P
-> Untar the module tarball -- it should create its own directory
+> Untar the module tarball -- it should create its own directory
</P
><P
-> CD to the directory just created, and enter the following commands:
+> CD to the directory just created, and enter the following commands:
<P
></P
><OL
TYPE="1"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.PL</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make test</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>make install</B
>
</TT
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN640"
>3.2.6. Data::Dumper Perl Module</A
></H2
><P
-> The Data::Dumper module provides data structure persistence for Perl
+> 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
><P
-> Data::Dumper is used by the MySQL-related Perl modules. It
+> Data::Dumper is used by the MySQL-related Perl modules. It
can be found on CPAN (see <A
HREF="downloadlinks.html"
>Appendix B</A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN645"
>3.2.7. MySQL related Perl Module Collection</A
></H2
><P
-> The Perl/MySQL interface requires a few mutually-dependent perl
+> The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should
be untarred.
</P
><P
-> The MySQL modules are all built using one make file which is generated
+> The MySQL modules are all built using one make file which is generated
by running:
<TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>perl Makefile.pl</B
>
</P
><P
-> The MakeMaker process will ask you a few questions about the desired
+> The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
</P
><P
-> When asked if your desired target is the MySQL or mSQL packages,
+> When asked if your desired target is the MySQL or mSQL packages,
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' and
+> A host of 'localhost' should be fine and a testing user of 'test' and
a null password should find itself with sufficient access to run tests
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN654"
>3.2.8. TimeDate Perl Module Collection</A
></H2
><P
-> Many of the more common date/time/calendar related Perl
+> 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 (see link: <A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN658"
>3.2.9. GD Perl Module (1.8.3)</A
></H2
><P
-> The GD library was written by Thomas Boutell a long while
+> 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
install it if you want any of the graphing to work.
</P
><P
-> Actually bugzilla uses the Graph module which relies on GD
+> Actually bugzilla uses the Graph module which relies on GD
itself. Isn't that always the way with object-oriented
programming? At any rate, you can find the GD library on CPAN
in <A
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The Perl GD library requires some other libraries that may
+> The Perl GD library requires some other libraries that may
or may not be installed on your system, including
<TT
-CLASS="CLASSNAME"
+CLASS="classname"
>libpng</TT
> and
<TT
-CLASS="CLASSNAME"
+CLASS="classname"
>libgd</TT
>. The full requirements are
listed in the Perl GD library README. Just realize that if
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN667"
>3.2.10. Chart::Base Perl Module (0.99c)</A
></H2
><P
-> The Chart module provides bugzilla with on-the-fly charting
+> 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 where it is found as the
Chart-x.x... tarball, linked in <A
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN671"
>3.2.11. DB_File Perl Module</A
></H2
><P
-> DB_File is a module which allows Perl programs to make use
+> DB_File is a module which allows Perl programs to make use
of the facilities provided by Berkeley DB version 1.x. This
module is required by collectstats.pl which is used for bug
charting. If you plan to make use of bug charting, you must
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN674"
>3.2.12. HTTP Server</A
></H2
><P
-> You have a freedom of choice here - Apache, Netscape or any
+> You have a freedom of choice here - Apache, Netscape or any
other server on UNIX would do. You can easily run the web
server on a different machine than MySQL, but need to adjust
the MySQL <SPAN
>"bugs"</SPAN
> user permissions accordingly.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>
</P
><P
-> You'll want to make sure that your web server will run any
+> 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 srm.conf file:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->AddHandler cgi-script .cgi
+CLASS="programlisting"
+> AddHandler cgi-script .cgi
</PRE
></FONT
></TD
>
</P
><P
-> With apache you'll also want to make sure that within the
+> With apache you'll also want to make sure that within the
access.conf file the line:
<TABLE
BORDER="0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->Options ExecCGI</PRE
+CLASS="programlisting"
+> Options ExecCGI
+</PRE
></FONT
></TD
></TR
you intend to put the bugzilla .html and .cgi files.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Users of newer versions of Apache will generally find both
+> Users of newer versions of Apache will generally find both
of the above lines will be in the httpd.conf file, rather
than srm.conf or access.conf.
</P
></TABLE
></DIV
><DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are important files and directories that should not
+> There are important files and directories that should not
be a served by the HTTP server. These are most files in the
<SPAN
CLASS="QUOTE"
configure your HTTP server to not serve content from these
files. Failure to do so will expose critical passwords and
other data. Please see <A
-HREF="geninstall.html#HTACCESS"
+HREF="geninstall.html#htaccess"
>.htaccess files and security</A
> for details
on how to do this for Apache. I appreciate notes on how to
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN692"
>3.2.13. Installing the Bugzilla Files</A
></H2
><P
-> You should untar the Bugzilla files into a directory that
+> 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"
>). You may decide to put the
files off of the main web space for your web server or perhaps
off of <TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/local</TT
> with a symbolic link in
the web space that points to the Bugzilla directory. At any
server.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you symlink the bugzilla directory into your Apache's
+> If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive
<SPAN
-CLASS="ERRORNAME"
+CLASS="errorname"
>Forbidden</SPAN
> errors unless you add the
<SPAN
></TABLE
></DIV
><P
-> Once all the files are in a web accessible directory, make
+> 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"
+CLASS="filename"
>checksetup.pl</TT
> script, which locks down your
installation.
</P
><P
-> Lastly, you'll need to set up a symbolic link to
+> Lastly, you'll need to set up a symbolic link to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
> for the correct
location of your perl executable (probably
<TT
-CLASS="FILENAME"
+CLASS="filename"
>/usr/bin/perl</TT
>). Otherwise you must hack
all the .cgi files to change where they look for perl, or use
>. I suggest using the symlink
approach for future release compatability.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN708"
></A
>Example 3-1. Setting up bonsaitools symlink</B
></P
><P
-> Here's how you set up the Perl symlink on Linux to make
+> Here's how you set up the Perl symlink on Linux to make
Bugzilla work. Your mileage may vary. For some UNIX
operating systems, you probably need to subsitute
<SPAN
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->bash# mkdir /usr/bonsaitools
+CLASS="programlisting"
+> bash# mkdir /usr/bonsaitools
bash# mkdir /usr/bonsaitools/bin
bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl
</PRE
>
</P
><P
-> Alternately, you can simply run this perl one-liner to
+> Alternately, you can simply run this perl one-liner to
change your path to perl in all the files in your Bugzilla
installation:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+CLASS="programlisting"
+> perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
</PRE
></FONT
></TD
></DIV
>
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you don't have root access to set this symlink up,
+> If you don't have root access to set this symlink up,
check out the
<A
HREF="setperl.html"
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN721"
>3.2.14. Setting Up the MySQL Database</A
></H2
><P
-> After you've gotten all the software installed and working you're ready
+> After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high
quality bug tracker.
</P
><P
-> First, you'll want to fix MySQL permissions to allow access
+> 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"
have minimal permissions.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Bugzilla has not undergone a thorough security audit. It
+> Bugzilla has not undergone a thorough security audit. It
may be possible for a system cracker to somehow trick
Bugzilla into executing a command such as <B
-CLASS="COMMAND"
+CLASS="command"
>DROP
DATABASE mysql</B
>.
>
</P
><P
-> Give the MySQL root user a password. MySQL passwords are
+> Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
<P
></P
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>mysql
-u root mysql</B
> </TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
-> UPDATE user SET Password=PASSWORD ('new_password')
+CLASS="command"
+> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root'; </B
> </TT
>
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>FLUSH
PRIVILEGES;</B
> </TT
> From this point on, if you need to access
MySQL as the MySQL root user, you will need to use
<B
-CLASS="COMMAND"
+CLASS="command"
>mysql -u root -p</B
> and enter your
new_password. Remember that MySQL user names have nothing to
do with Unix user names (login names).
</P
><P
-> Next, we create the <SPAN
+> Next, we create the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user, and grant
as a different user.
</P
><P
-> Remember to set bugs_password to some unique password.
+> Remember to set bugs_password to some unique password.
<P
></P
><TABLE
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
-> mysql>
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
+> mysql>
</TT
>
<B
-CLASS="COMMAND"
-> FLUSH PRIVILEGES;
+CLASS="command"
+> FLUSH PRIVILEGES;
</B
>
</TT
>
</P
><P
-> Next, run the magic checksetup.pl script. (Many thanks to
+> Next, run the magic checksetup.pl script. (Many thanks to
Holger Schurig <holgerschurig@nikocity.de> for writing
this script!) It will make sure Bugzilla files and directories
have reasonable permissions, set up the
<TT
-CLASS="FILENAME"
+CLASS="filename"
>data</TT
> directory, and create all the MySQL
tables.
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>./checksetup.pl</B
> </TT
>
></P
> The first time you run it, it will create a
file called <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
>.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN768"
>3.2.15. Tweaking <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
></A
></H2
><P
-> This file contains a variety of settings you may need to tweak including
+> 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:
+> The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
-> server's host: just use <SPAN
+> server's host: just use <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
> if the
></LI
><LI
><P
-> database name: <SPAN
+> database name: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
></LI
><LI
><P
-> MySQL username: <SPAN
+> MySQL username: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
></LI
><LI
><P
-> Password for the <SPAN
+> Password for the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> MySQL account above
>
</P
><P
-> You should also install .htaccess files that the Apache
+> You should also install .htaccess files that the Apache
webserver will use to restrict access to Bugzilla data files.
See <A
-HREF="geninstall.html#HTACCESS"
+HREF="geninstall.html#htaccess"
>.htaccess files and security</A
>.
</P
><P
-> Once you are happy with the settings, re-run
+> Once you are happy with the settings, re-run
<TT
-CLASS="FILENAME"
+CLASS="filename"
>checksetup.pl</TT
>. On this second run, it will
create the database and an administrator account for which
you will be prompted to provide information.
</P
><P
-> When logged into an administrator account once Bugzilla is
+> When logged into an administrator account once Bugzilla is
running, if you go to the query page (off of the Bugzilla main
menu), you'll find an <SPAN
CLASS="QUOTE"
that is filled with editable treats.
</P
><P
-> Should everything work, you will have a nearly empty Bugzilla
+> Should everything work, you will have a nearly empty Bugzilla
database and a newly-created <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
>
file in your Bugzilla root directory.
</P
><P
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The second time you run checksetup.pl, you should become
+> The second time you run checksetup.pl, you should become
the user your web server runs as, and that you ensure that
you set the <SPAN
CLASS="QUOTE"
> parameter in
localconfig as well.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
NAME="AEN799"
></A
>Example 3-2. Running checksetup.pl as the web user</B
></P
><P
-> Assuming your web server runs as user "apache", and
+> Assuming your web server runs as user "apache", and
Bugzilla is installed in "/usr/local/bugzilla", here's
one way to run checksetup.pl as the web server user.
As root, for the <EM
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
bash# chown -R apache:apache /usr/local/bugzilla
bash# su - apache
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> The checksetup.pl script is designed so that you can run
+> 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
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN806"
>3.2.16. Setting Up Maintainers Manually (Optional)</A
></H2
><P
-> If you want to add someone else to every group by hand, you
+> If you want to add someone else to every group by hand, you
can do it by typing the appropriate MySQL commands. Run
<B
-CLASS="COMMAND"
+CLASS="command"
> mysql -u root -p bugs</B
> You
may need different parameters, depending on your security
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>update
profiles set groupset=0x7fffffffffffffff where
login_name = 'XXX';</B
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN817"
>3.2.17. The Whining Cron (Optional)</A
></H2
><P
-> By now you have a fully functional bugzilla, but what good
+> 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. This can be done by adding the following command as a
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <B
-CLASS="COMMAND"
+CLASS="command"
>cd
<your-bugzilla-directory> ;
./whineatnews.pl</B
>
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Depending on your system, crontab may have several manpages.
+> Depending on your system, crontab may have several manpages.
The following command should lead you to the most useful
page for this purpose:
<TABLE
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> man 5 crontab
+CLASS="programlisting"
+> man 5 crontab
</PRE
></FONT
></TD
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN827"
>3.2.18. Bug Graphs (Optional)</A
></H2
><P
-> As long as you installed the GD and Graph::Base Perl modules
+> 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 collectstats daily at 5
+> Add a cron entry like this to run collectstats daily at 5
after midnight:
<P
></P
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> <TT
-CLASS="PROMPT"
+CLASS="prompt"
>bash#</TT
> <B
-CLASS="COMMAND"
+CLASS="command"
>crontab
-e</B
> </TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="computeroutput"
> 5 0 * * * cd
<your-bugzilla-directory> ; ./collectstats.pl
</TT
>
</P
><P
-> After two days have passed you'll be able to view bug graphs
+> After two days have passed you'll be able to view bug graphs
from the Bug Reports page.
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
NAME="AEN839"
>3.2.19. Securing MySQL</A
></H2
><P
-> If you followed the installation instructions for setting up
+> If you followed the installation instructions for setting up
your "bugs" and "root" user in MySQL, much of this should not
apply to you. If you are upgrading an existing installation
of Bugzilla, you should pay close attention to this section.
</P
><P
-> Most MySQL installs have "interesting" default security parameters:
+> Most MySQL installs have "interesting" default security parameters:
<P
></P
><TABLE
>
</P
><P
-> This means anyone from anywhere on the internet can not only
+> This means anyone from anywhere on the internet can not only
drop the database with one SQL command, and they can write as
root to the system.
</P
><P
-> To see your permissions do:
+> To see your permissions do:
<P
></P
><TABLE
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>bash#</TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>mysql -u root -p</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>use mysql;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>show tables;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>select * from user;</B
>
</TT
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>select * from db;</B
>
</TT
>
</P
><P
-> To fix the gaping holes:
+> To fix the gaping holes:
<P
></P
><TABLE
>
</P
><P
-> If you're not running "mit-pthreads" you can use:
+> If you're not running "mit-pthreads" you can use:
<P
></P
><TABLE
>
</P
><P
-> With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
+> With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
<P
>
</P
><P
-> Use .htaccess files with the Apache webserver to secure your
+> Use .htaccess files with the Apache webserver to secure your
bugzilla install. See <A
-HREF="geninstall.html#HTACCESS"
+HREF="geninstall.html#htaccess"
>.htaccess files and security</A
>
</P
><P
-> Consider also:
+> Consider also:
<P
></P
><OL
TYPE="1"
><LI
><P
-> Turning off external networking with "--skip-networking",
+> Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
</P
></LI
><LI
><P
-> using the --user= option to mysqld to run it as an unprivileged
+> using the --user= option to mysqld to run it as an unprivileged
user.
</P
></LI
><LI
><P
-> starting MySQL in a chroot jail
+> starting MySQL in a chroot jail
</P
></LI
><LI
><P
-> running the httpd in a "chrooted" jail
+> running the httpd in a "chrooted" jail
</P
></LI
><LI
><P
-> making sure the MySQL passwords are different from the OS
+> making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
</P
></LI
><LI
><P
-> running MySQL on a separate untrusted machine
+> running MySQL on a separate untrusted machine
</P
></LI
><LI
><P
-> making backups ;-)
+> making backups ;-)
</P
></LI
></OL
TITLE="The Future of Bugzilla"
HREF="future.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="TINDERBOX"
+NAME="tinderbox"
>5.4. Tinderbox/Tinderbox2</A
></H1
><P
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="TRANSLATIONS"
+NAME="translations"
>1.8. Translations</A
></H1
><P
-> The Bugzilla Guide needs translators! Please volunteer your
+> The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will
translate this Guide, please notify the members of the
mozilla-webtools mailing list at
<TT
-CLASS="EMAIL"
+CLASS="email"
><<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
Administration"
HREF="programadmin.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="USERADMIN"
+NAME="useradmin"
>4.2. User Administration</A
></H1
><P
-> User administration is one of the easiest parts of Bugzilla.
+> User administration is one of the easiest parts of Bugzilla.
Keeping it from getting out of hand, however, can become a
challenge.
</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DEFAULTUSER"
+NAME="defaultuser"
>4.2.1. Creating the Default User</A
></H2
><P
-> When you first run checksetup.pl after installing Bugzilla, it
+> 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 were to delete the "super user" account, re-running
password.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you wish to add more administrative users, you must use the
+> 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>" denotes the mysql prompt, not
something you should type in):
<B
-CLASS="COMMAND"
+CLASS="command"
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> use bugs;</B
>
<B
-CLASS="COMMAND"
+CLASS="command"
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>mysql></TT
> update profiles set
groupset=0x7ffffffffffffff where login_name = "(user's
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MANAGEUSERS"
+NAME="manageusers"
>4.2.2. Managing Other Users</A
></H2
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="LOGIN"
+NAME="login"
>4.2.2.1. Logging In</A
></H3
><P
TYPE="1"
><LI
><P
-> Open the index.html page for your Bugzilla installation
+> Open the index.html page for your Bugzilla installation
in your browser window.
</P
></LI
><LI
><P
-> Click the "Query Existing Bug Reports" link.
+> Click the "Query Existing Bug Reports" link.
</P
></LI
><LI
><P
-> Click the "Log In" link at the foot of the page.
+> Click the "Log In" link at the foot of the page.
</P
></LI
><LI
><P
-> Type your email address, and the password which was
+> Type your email address, and the password which was
emailed to you when you created your Bugzilla account,
into the spaces provided.
</P
>Congratulations, you are logged in!</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="CREATENEWUSERS"
+NAME="createnewusers"
>4.2.2.2. Creating new users</A
></H3
><P
-> Your users can create their own user accounts by clicking
+> Your users can create their own user accounts by clicking
the "New Account" link at the bottom of each page. However,
should you desire to create user accounts ahead of time,
here is how you do it.
TYPE="1"
><LI
><P
-> After logging in, click the "Users" link at the footer
+> After logging in, click the "Users" link at the footer
of the query page.
</P
></LI
><LI
><P
-> To see a specific user, type a portion of their login
+> To see a specific user, type a portion of their login
name in the box provided and click "submit". To see all
users, simply click the "submit" button. You must click
"submit" here to be able to add a new user.
</P
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> More functionality is available via the list on the
+> More functionality is available via the list on the
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the <B
-CLASS="COMMAND"
+CLASS="command"
>man
regexp</B
> manual page for details on regular
></LI
><LI
><P
-> Click the "Add New User" link at the bottom of the user
+> Click the "Add New User" link at the bottom of the user
list
</P
></LI
><LI
><P
-> Fill out the form presented. This page is
+> Fill out the form presented. This page is
self-explanatory. When done, click "submit".
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Adding a user this way will <EM
+> Adding a user this way will <EM
>not</EM
>
send an email informing them of their username and
></OL
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="DISABLEUSERS"
+NAME="disableusers"
>4.2.2.3. Disabling Users</A
></H3
><P
-> I bet you noticed that big "Disabled Text" entry box
+> I bet you noticed that big "Disabled Text" entry box
available from the "Add New User" screen, when you edit an
account? By entering any text in this box and selecting
"submit", you have prevented the user from using Bugzilla
text box, will be presented to the user the next time she
attempts to use the system.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
+CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Don't disable your own administrative account, or you
+> Don't disable your own administrative account, or you
will hate life!
</P
><P
</P
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H3
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="MODIFYUSERS"
+NAME="modifyusers"
>4.2.2.4. Modifying Users</A
></H3
><P
-> Here I will attempt to describe the function of each option
+> Here I will attempt to describe the function of each option
on the Edit User screen.
</P
><P
><UL
><LI
><P
-> <EM
+> <EM
>Login Name</EM
>: This is generally the
user's email address. However, if you have edited your
system parameters, this may just be the user's login
name or some other identifier.
<DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
-WIDTH="90%"
+CLASS="tip"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> For compatability reasons, you should probably stick
+> For compatability reasons, you should probably stick
with email addresses as user login names. It will
make your life easier.
</P
></LI
><LI
><P
-> <EM
+> <EM
>Real Name</EM
>: Duh!
</P
></LI
><LI
><P
-> <EM
+> <EM
>Password</EM
>: You can change the user
password here. It is normal to only see asterisks.
></LI
><LI
><P
-> <EM
+> <EM
>Email Notification</EM
>: You may choose
from one of three options:
TYPE="1"
><LI
><P
-> All qualifying bugs except those which I change:
+> All qualifying bugs except those which I change:
The user will be notified of any change to any bug
for which she is the reporter, assignee, QA
Contact, CC recipient, or "watcher".
></LI
><LI
><P
-> Only those bugs which I am listed on the CC line:
+> Only those bugs which I am listed on the CC line:
The user will not be notified of changes to bugs
where she is the assignee, reporter, or QA
Contact, but will receive them if she is on the CC
list.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> She will still receive whining cron emails if
+> She will still receive whining cron emails if
you set up the "whinemail" feature.
</P
></TD
></LI
><LI
><P
-> <EM
+> <EM
>All Qualifying Bugs</EM
>: This
user is a glutton for punishment. If her name is
</P
></LI
></OL
-></P
+>
+</P
><P
-> <EM
+> <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
interface, and what you type in this box is presented as
the reason.
<DIV
-CLASS="WARNING"
+CLASS="warning"
><P
></P
><TABLE
-CLASS="WARNING"
-WIDTH="90%"
+CLASS="warning"
+WIDTH="100%"
BORDER="0"
><TR
><TD
></DIV
>
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> As of this writing, the user can still submit bugs
+> As of this writing, the user can still submit bugs
via the e-mail gateway, if you set it up, despite
the disabled text field. The e-mail gateway should
<EM
></LI
><LI
><P
-> <EM
+> <EM
>CanConfirm</EM
>: This field is only used
if you have enabled "unconfirmed" status in your
></LI
><LI
><P
-> <EM
+> <EM
>Creategroups</EM
>: This option will
allow a user to create and destroy groups in Bugzilla.
></LI
><LI
><P
-> <EM
+> <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.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
-WIDTH="90%"
+CLASS="note"
+WIDTH="100%"
BORDER="0"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Leaving this option unchecked does not prevent users
+> Leaving this option unchecked does not prevent users
from adding comments to a bug! They simply cannot
change a bug priority, severity, etc. unless they
are the assignee or reporter.
></LI
><LI
><P
-> <EM
+> <EM
>Editcomponents</EM
>: This flag allows a
user to create new products and components, as well as
></LI
><LI
><P
-> <EM
+> <EM
>Editkeywords</EM
>: If you use Bugzilla's
keyword functionality, enabling this feature allows a
></LI
><LI
><P
-> <EM
+> <EM
>Editusers</EM
>: This flag allows a user
do what you're doing right now: edit other users. This
></LI
><LI
><P
-> <EM
+> <EM
>PRODUCT</EM
>: PRODUCT bugs access. This
allows an administrator, with product-level granularity,
TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="USING"
+NAME="using"
>Chapter 2. Using Bugzilla</A
></H1
><TABLE
><DL
><DT
>2.3.1. <A
-HREF="how.html#MYACCOUNT"
+HREF="how.html#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
-HREF="how.html#QUERY"
+HREF="how.html#query"
>The Bugzilla Query Page</A
></DT
><DT
>2.3.3. <A
-HREF="how.html#BUGREPORTS"
+HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>2.3.3.1. <A
-HREF="how.html#BUG_WRITING"
+HREF="how.html#bug-writing"
>Writing a Great Bug Report</A
></DT
><DT
>2.3.3.2. <A
-HREF="how.html#BUG_MANAGE"
+HREF="how.html#bug-manage"
>Managing your Bug Reports</A
></DT
></DL
><DL
><DT
>2.4.1. <A
-HREF="init4me.html#ACCOUNTSETTINGS"
+HREF="init4me.html#accountsettings"
>Account Settings</A
></DT
><DT
>2.4.2. <A
-HREF="init4me.html#EMAILSETTINGS"
+HREF="init4me.html#emailsettings"
>Email Settings</A
></DT
><DD
><DL
><DT
>2.4.2.1. <A
-HREF="init4me.html#NOTIFICATION"
+HREF="init4me.html#notification"
>Email Notification</A
></DT
><DT
>2.4.2.2. <A
-HREF="init4me.html#NEWEMAILTECH"
+HREF="init4me.html#newemailtech"
>New Email Technology</A
></DT
><DT
>2.4.2.3. <A
-HREF="init4me.html#WATCHSETTINGS"
+HREF="init4me.html#watchsettings"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>2.4.3. <A
-HREF="init4me.html#FOOTERSETTINGS"
+HREF="init4me.html#footersettings"
>Page Footer</A
></DT
><DT
>2.4.4. <A
-HREF="init4me.html#PERMISSIONSETTINGS"
+HREF="init4me.html#permissionsettings"
>Permissions</A
></DT
></DL
TITLE="Installation"
HREF="installation.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="USINGBZ-CONC"
+NAME="usingbz-conc"
>2.5. Using Bugzilla-Conclusion</A
></H1
><P
-> Thank you for reading through this portion of the Bugzilla
+> Thank you for reading through this portion of the Bugzilla
Guide. I anticipate it may not yet meet the needs of all
readers. If you have additional comments or corrections to
make, please submit your contributions to the <A
--- /dev/null
+<HTML
+><HEAD
+><TITLE
+>Loki Bugzilla (Fenris)</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Red Hat Bugzilla"
+HREF="rhbugzilla.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
+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="rhbugzilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant-issuezilla.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="variant-fenris"
+>7.2. Loki Bugzilla (Fenris)</A
+></H1
+><P
+>Fenris can be found at <A
+HREF="http://fenris.lokigames.com/"
+TARGET="_top"
+>http://fenris.lokigames.com</A
+>. It is a fork from Bugzilla.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="rhbugzilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant-issuezilla.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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
+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="variant-fenris.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant-scarab.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="variant-issuezilla"
+>7.3. Issuezilla</A
+></H1
+><P
+>Issuezilla is another fork from Bugzilla, and seems nearly
+ as popular as the Red Hat Bugzilla fork. Some Issuezilla team
+ members are regular contributors to the Bugzilla mailing
+ list/newsgroup. Issuezilla is not the primary focus of
+ bug-tracking at tigris.org, however. Their Java-based
+ bug-tracker, <A
+HREF="variant-scarab.html"
+>Scarab, a newfangled Java-based issue tracker</A
+>, is under heavy development
+ and looks promising!</P
+><P
+>URL: <A
+HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
+TARGET="_top"
+>http://issuezilla.tigris.org/servlets/ProjectHome</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant-fenris.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant-scarab.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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
+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="variant-scarab.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant-sourceforge.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="variant-perforce"
+>7.5. Perforce SCM</A
+></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
+><A
+HREF="http://www.perforce.com/perforce/technotes/note052.html"
+TARGET="_top"
+>http://www.perforce.com/perforce/technotes/note052.html</A
+>http://www.perforce.com/perforce/technotes/note052.html</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant-scarab.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant-sourceforge.html"
+>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"
+>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
+>Scarab</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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
+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="variant-issuezilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant-perforce.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="variant-scarab"
+>7.4. Scarab</A
+></H1
+><P
+>Scarab is a promising new bug-tracking system built using
+ Java Serlet technology. As of this writing, no source code has
+ been released as a package, but you can obtain the code from
+ CVS.
+ </P
+><P
+>URL: <A
+HREF="http://scarab.tigris.org/"
+TARGET="_top"
+>http://scarab.tigris.org</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant-issuezilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant-perforce.html"
+>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"
+>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.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+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="The Bugzilla FAQ"
+HREF="faq.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><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="variant-perforce.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="faq.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="variant-sourceforge"
+>7.6. SourceForge</A
+></H1
+><P
+>SourceForge is more of a way of coordinating geographically
+ distributed free software and open source projects over the
+ Internet than strictly a bug tracker, but if you're hunting for
+ bug-tracking for your open project, it may be just what the
+ software engineer ordered!</P
+><P
+>URL: <A
+HREF="http://www.sourceforge.net"
+TARGET="_top"
+>http://www.sourceforge.net</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant-perforce.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="faq.html"
+>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"
+>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
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
><BODY
-CLASS="CHAPTER"
+CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="chapter"
><H1
><A
-NAME="VARIANTS"
+NAME="variants"
>Chapter 7. Bugzilla Variants and Competitors</A
></H1
><DIV
></DT
><DT
>7.2. <A
-HREF="variant_fenris.html"
+HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
-HREF="variant_issuezilla.html"
+HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
-HREF="variant_scarab.html"
+HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
-HREF="variant_perforce.html"
+HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
-HREF="variant_sourceforge.html"
+HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WHATIS"
+NAME="whatis"
>2.1. What is Bugzilla?</A
></H1
><P
-> Bugzilla is one example of a class of programs called "Defect
+> Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
system against which all others are measured.
</P
><P
-> Bugzilla has matured immensely, and now boasts many advanced features. These include:
+> Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P
></P
><UL
><LI
><P
-> integrated, product-based granular security schema
+> integrated, product-based granular security schema
</P
></LI
><LI
><P
-> inter-bug dependencies and dependency graphing
+> inter-bug dependencies and dependency graphing
</P
></LI
><LI
><P
-> advanced reporting capabilities
+> advanced reporting capabilities
</P
></LI
><LI
><P
-> a robust, stable RDBMS back-end
+> a robust, stable RDBMS back-end
</P
></LI
><LI
><P
-> extensive configurability
+> extensive configurability
</P
></LI
><LI
><P
-> a very well-understood and well-thought-out natural bug resolution protocol
+> a very well-understood and well-thought-out natural bug resolution protocol
</P
></LI
><LI
><P
-> email, XML, console, and HTTP APIs
+> email, XML, console, and HTTP APIs
</P
></LI
><LI
><P
-> available integration with automated software
+> available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
></LI
><LI
><P
-> too many more features to list
+> too many more features to list
</P
></LI
></UL
>
</P
><P
-> Despite its current robustness and popularity, Bugzilla faces
+> Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but
some nonstandard libraries.
</P
><P
-> Some recent headway has been made on the query front, however.
+> Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
available as "queryhelp.cgi".
</P
><P
-> Despite these small problems, Bugzilla is very hard to beat. It
+> Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
> active development to address
TITLE="How do I use Bugzilla?"
HREF="how.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WHY"
+NAME="why"
>2.2. Why Should We Use Bugzilla?</A
></H1
><TABLE
></TR
></TABLE
><P
-> For many years, defect-tracking software has remained
+> 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
dropped or ignored.
</P
><P
-> These days, many companies are finding that integrated
+> 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
system for accounting for unusual system or software issues.
</P
><P
-> But why should <EM
+> But why should <EM
>you</EM
> use Bugzilla?
</P
><P
-> Bugzilla is very adaptable to various situations. Known uses
+> 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
replication problems
</P
><P
-> Bugzilla can dramatically increase the productivity and
+> 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
led to critical decisions.
</P
><P
-> Ultimately, Bugzilla puts the power in your hands to improve
+> 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.
TITLE="Administering Bugzilla"
HREF="administration.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WIN32"
+NAME="win32"
>3.6. Win32 Installation Notes</A
></H1
><P
any influence in the platform choice for running this system,
please choose GNU/Linux instead of Microsoft Windows.</P
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WININSTALL"
+NAME="wininstall"
>3.6.1. Win32 Installation: Step-by-step</A
></H2
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You should be familiar with, and cross-reference, the rest
+> You should be familiar with, and cross-reference, the rest
of the
<A
HREF="installation.html"
></TABLE
></DIV
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
HREF="http://www.apache.org/"
TARGET="_top"
>Apache Web
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You may also use Internet Information Server or Personal
+> 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),
>.
</P
><P
-> If you are going to use IIS, if on Windows NT you must
+> 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
></LI
><LI
><P
HREF="http://www.activestate.com/"
TARGET="_top"
>ActivePerl</A
> for a current compiled binary.
</P
><P
-> Please also check the following links to fully understand the status
+> 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
+> 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
+> Perl on Win32 FAQ</A
>
</P
></LI
><LI
><P
-> Use ppm from your perl\bin directory to install the following packs: DBI,
+> Use ppm from your perl\bin directory to install the following packs: DBI,
DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
to extract them from .zip format using Winzip or other unzip program first.
These additional ppm modules can be downloaded from ActiveState.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> You can find a list of modules at
+> 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
+> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
>
</P
></TD
></TABLE
></DIV
><P
-> The syntax for ppm is:
+> The syntax for ppm is:
<TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:> </TT
><B
-CLASS="COMMAND"
+CLASS="command"
>ppm <modulename></B
>
</TT
>
</P
><DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1038"
+NAME="AEN1048"
></A
><P
><B
></P
><P
><TT
-CLASS="PROMPT"
+CLASS="prompt"
>C:></TT
><B
-CLASS="COMMAND"
+CLASS="command"
>ppm
<TT
-CLASS="OPTION"
+CLASS="option"
>DBD-Mysql</TT
></B
></P
>Watch your capitalization!</P
></DIV
><P
-> You can find ActiveState ppm modules at
+> You can find ActiveState ppm modules at
<A
HREF="http://www.activestate.com/PPMPackages/5.6plus/"
TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
+> http://www.activestate.com/PPMPackages/5.6plus</A
>
</P
></LI
><LI
><P
-> Install MySQL for NT.
+> Install MySQL for NT.
<DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
->
You can download MySQL for Windows NT from <A
+>
You can download MySQL for Windows NT from <A
HREF="http://www.mysql.com/"
TARGET="_top"
>MySQL.com</A
></LI
><LI
><P
-> Setup MySQL
+> Setup MySQL
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:> </TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>C:\mysql\bin\mysql -u root mysql</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>DELETE FROM user WHERE Host='localhost' AND User='';</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';</B
>
></LI
><LI
><A
-NAME="NTBUGS-PASSWORD"
+NAME="ntbugs-password"
></A
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>GRANT SELECT, INSERT, UPDATE, DELETE,
INDEX, ALTER, CREATE, DROP, REFERENCES
ON bugs.* to bugs@localhost
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>FLUSH PRIVILEGES;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>create database bugs;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>mysql></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>exit;</B
>
</TT
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
+> <TT
+CLASS="computeroutput"
+> <TT
+CLASS="prompt"
>C:></TT
>
<B
-CLASS="COMMAND"
+CLASS="command"
>C:\mysql\bin\mysqladmin -u root -p reload</B
>
</TT
></LI
><LI
><P
-> Edit <TT
-CLASS="FILENAME"
+> Edit <TT
+CLASS="filename"
>checksetup.pl</TT
> in your Bugzilla directory. Change
this line:
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = getgrnam($my_webservergroup);
+CLASS="programlisting"
+> my $webservergid = getgrnam($my_webservergroup);
</PRE
></FONT
></TD
>
</P
><P
-> to
+> to
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = $my_webservergroup;
+CLASS="programlisting"
+> my $webservergid = $my_webservergroup;
</PRE
></FONT
></TD
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = 'Administrators'
+CLASS="programlisting"
+> my $webservergid = 'Administrators'
</PRE
></FONT
></TD
></LI
><LI
><P
-> Run <TT
-CLASS="FILENAME"
+> Run <TT
+CLASS="filename"
>checksetup.pl</TT
> from the Bugzilla directory.
</P
><LI
><P
>Edit <TT
-CLASS="FILENAME"
+CLASS="filename"
>localconfig</TT
> to suit your
requirements. Set <TT
-CLASS="VARNAME"
+CLASS="varname"
>$db_pass</TT
> to your
<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> from <A
-HREF="win32.html#NTBUGS-PASSWORD"
+HREF="win32.html#ntbugs-password"
>step 5.d</A
>, and <TT
-CLASS="VARNAME"
+CLASS="varname"
>$webservergroup</TT
> to <SPAN
CLASS="QUOTE"
>"8"</SPAN
>.</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
>"8"</SPAN
> for
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$webservergroup</TT
> above. If it's
wrong, please send corrections.</P
></LI
><LI
><P
-> Edit <TT
-CLASS="FILENAME"
+> Edit <TT
+CLASS="filename"
>defparams.pl</TT
> to suit your
requirements. Particularly, set
<TT
-CLASS="VARNAME"
+CLASS="varname"
>DefParam("maintainer")</TT
> and
<TT
-CLASS="VARNAME"
+CLASS="varname"
>DefParam("urlbase") to match your
install.</TT
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
></LI
><LI
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> There are several alternatives to Sendmail that will work on Win32.
+> There are several alternatives to Sendmail that will work on Win32.
The one mentioned here is a <EM
>suggestion</EM
>, not
></TABLE
></DIV
><DIV
-CLASS="PROCEDURE"
+CLASS="procedure"
><OL
TYPE="1"
><LI
><P
->
Download NTsendmail, available from<A
+>
Download NTsendmail, available from<A
HREF="http://www.ntsendmail.com/"
TARGET="_top"
> www.ntsendmail.com</A
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-># these settings configure the NTsendmail process
+CLASS="programlisting"
+> # these settings configure the NTsendmail process
use NTsendmail;
$ENV{"NTsendmail"}="your.smtpserver.box";
$ENV{"NTsendmail_debug"}=1;
></TR
></TABLE
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some mention to also edit
+> Some mention to also edit
<TT
-CLASS="VARNAME"
+CLASS="varname"
>$db_pass</TT
> in
<TT
-CLASS="FILENAME"
+CLASS="filename"
>globals.pl</TT
> to be your
<SPAN
you around some problem authenticating to your
database, since globals.pl is not normally
restricted by <TT
-CLASS="FILENAME"
+CLASS="filename"
>.htaccess</TT
>, your
database password is exposed to whoever uses your
></LI
><LI
><P
-> Find and comment out all occurences of
+> Find and comment out all occurences of
<SPAN
CLASS="QUOTE"
>"<B
-CLASS="COMMAND"
+CLASS="command"
>open(SENDMAIL</B
>"</SPAN
> in
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-># new sendmail functionality
+CLASS="programlisting"
+> # new sendmail functionality
my $mail=new NTsendmail;
my $from="bugzilla\@your.machine.name.tld";
my $to=$login;
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Some have found success using the commercial product,
+> Some have found success using the commercial product,
<SPAN
-CLASS="PRODUCTNAME"
+CLASS="productname"
>Windmail</SPAN
>.
You could try replacing your sendmail calls with:
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+CLASS="programlisting"
+> open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
</PRE
></FONT
></TD
></LI
><LI
><P
-> Change all references in all files from
+> Change all references in all files from
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
> to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail.pl</TT
>, and
rename <TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail</TT
> to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>processmail.pl</TT
>.
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> Many think this may be a change we want to make for
+> 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
></TABLE
></DIV
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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.
+> 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"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
+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->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist";
-} </PRE
+}
+
+
+</PRE
></FONT
></TD
></TR
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
-> use Net::SMTP;
+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->datasend('test');
$smtp->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
-exit; </PRE
+exit;
+
+
+</PRE
></FONT
></TD
></TR
></LI
><LI
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> This step is optional if you are using IIS or another
+> 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
></TABLE
></DIV
><P
-> Modify the path to perl on the first line (#!) of all
+> Modify the path to perl on the first line (#!) of all
files to point to your Perl installation, and add
<SPAN
CLASS="QUOTE"
></LI
><LI
><P
-> Modify the invocation of all system() calls in all perl
- scripts in your Bugzilla directory. For instance, change
+> 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"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
-system ("./processmail.pl",@ARGLIST);
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-> to
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="PROGRAMLISTING"
->
-system ("perl processmail.pl",@ARGLIST);
+system ("./processmail",@ARGLIST);
+ </programlisting> to
+ <programlisting>
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
</PRE
></FONT
></TD
></LI
><LI
><P
-> Add <TT
-CLASS="FUNCTION"
+> Add <TT
+CLASS="function"
>binmode()</TT
> calls so attachments
will work (<A
>).
</P
><P
-> Because Microsoft Windows based systems handle binary
+> Because Microsoft Windows based systems handle binary
files different than Unix based systems, you need to add
the following lines to
<TT
-CLASS="FILENAME"
+CLASS="filename"
>createattachment.cgi</TT
> and
<TT
-CLASS="FILENAME"
+CLASS="filename"
>showattachment.cgi</TT
> before the
<TT
-CLASS="FUNCTION"
+CLASS="function"
>require 'CGI.pl';</TT
-> line.</P
+> line.
+</P
><P
-><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->binmode(STDIN);
-binmode(STDOUT);</PRE
+CLASS="programlisting"
+>
+binmode(STDIN);
+binmode(STDOUT);
+
+</PRE
></FONT
></TD
></TR
>
</P
><DIV
-CLASS="NOTE"
+CLASS="note"
><P
></P
><TABLE
-CLASS="NOTE"
+CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
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"
+CLASS="function"
>binmode()</TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
-CLASS="FUNCTION"
+CLASS="function"
>binmode()</TT
> at the begining of the attachment files, there should be logic to determine if <TT
-CLASS="FUNCTION"
+CLASS="function"
>binmode()</TT
> is needed or not.
</P
></OL
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If you are using IIS or Personal Web Server, you must add cgi
+> 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
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
.cgi to: <perl install directory>\perl.exe %s %s
.pl to: <perl install directory>\perl.exe %s %s
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="ADDLWINTIPS"
+NAME="addlwintips"
>3.6.2. Additional Windows Tips</A
></H2
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> From Andrew Pearson:
+> From Andrew Pearson:
<A
-NAME="AEN1212"
+NAME="AEN1221"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
-> You can make Bugzilla work with Personal Web Server for
+> 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"
>
</P
><P
-> Basically you need to add two String Keys in the
+> Basically you need to add two String Keys in the
registry at the following location:
</P
><P
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+CLASS="programlisting"
+> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
</PRE
></FONT
></TD
>
</P
><P
-> The keys should be called ".pl" and ".cgi", and both
+> The keys should be called ".pl" and ".cgi", and both
should have a value something like:
<B
-CLASS="COMMAND"
+CLASS="command"
>c:/perl/bin/perl.exe "%s" "%s"</B
>
</P
><P
-> The KB article only talks about .pl, but it goes into
+> The KB article only talks about .pl, but it goes into
more detail and provides a perl test script.
</P
></BLOCKQUOTE
></TABLE
></DIV
><DIV
-CLASS="TIP"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="TIP"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
ALIGN="LEFT"
VALIGN="TOP"
><P
-> If attempting to run Bugzilla 2.12 or older, you will need
+> 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
later, which includes the current release, Bugzilla
2.14.
<DIV
-CLASS="EXAMPLE"
+CLASS="example"
><A
-NAME="AEN1224"
+NAME="AEN1233"
></A
><P
><B
2.12 or earlier</B
></P
><P
-> Replace this:
+> Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
><FONT
COLOR="#000000"
><PRE
-CLASS="PROGRAMLISTING"
+CLASS="programlisting"
>
my $enteredcryptpwd = $enteredpwd
</PRE
></DIV
></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H2
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="BZLDAP"
+NAME="bzldap"
>3.6.3. Bugzilla LDAP Integration</A
></H2
><P
-> What follows is some late-breaking information on using the
+> What follows is some late-breaking information on using the
LDAP authentication options with Bugzilla. The author has not
tested these (nor even formatted this section!) so please
contribute feedback to the newsgroup.
</P
><P
-CLASS="LITERALLAYOUT"
->Mozilla::LDAP module<br>
+CLASS="literallayout"
+><br>
+Mozilla::LDAP module<br>
<br>
The Mozilla::LDAP module allows you to use LDAP for authentication to<br>
the Bugzilla system. This module is not required if you are not using<br>
Bugzilla is an enterprise-class set of software utilities that, when
used together, power issue-tracking for hundreds of organizations
around the world, tracking millions of bugs. While it is easy to use
- and quite flexible, it is very difficult for a novice to install and
+ and quite flexible, it is difficult for a novice to install and
maintain. Although we have provided step-by-step directions, Bugzilla
is not always easy to get working. Please be sure the person
responsible for installing and maintaining this software is a
- qualified professional on operating system upon which you install
+ qualified professional for the operating system upon which you install
Bugzilla.
- THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. IF YOU
+ THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT. IF YOU
WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS
AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN
HTML!
tends to run the latest code, so these two utilities should be
available there for your perusal.
- At this point, please visit the main Bugzilla site,
- bugzilla.mozilla.org, to see a more fleshed-out query page.
+ At this point, let's visit the query page.
+ landfill.tequilarista.org/bugzilla-tip/query.cgi
The first thing you need to notice about the Bugzilla Query Page is
that nearly every box you see on your screen has a hyperlink nearby,
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 or other web server which
does not observe .htaccess conventions, you can disable their creation
by editing localconfig and setting the $create_htaccess variable to 0.
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
$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->quit; # Close the SMTP connection
exit;
+
12.
Note
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. For instance, change this line 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.pl",@ARGLIST);
-
-
- to
-
-
-system ("perl processmail.pl",@ARGLIST);
+system ("./processmail",@ARGLIST);
+ </programlisting> to
+ <programlisting>
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
14. Add binmode() calls so attachments will work (bug 62000).
}
and then put this line in index.shtml.
- <!--#include virtual="api.cgi?sub=PutFooter"-->
+<!--#include virtual="api.cgi?sub=PutFooter"-->
Note
CPAN: http://www.cpan.org/
- DBI Perl module:
- ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
+ DBI Perl module: http://www.cpan.org/modules/by-module/DBI/
- Data::Dumper module:
- ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
+ Data::Dumper module: http://www.cpan.org/modules/by-module/Data/
MySQL related Perl modules:
- ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
+ http://www.cpan.org/modules/by-module/Mysql/
TimeDate Perl module collection:
- ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
+ http://www.cpan.org/modules/by-module/Date/
- GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
- Alternately, you should be able to find the latest version of GD at
+ GD Perl module: http://www.cpan.org/modules/by-module/GD/ Alternately,
+ you should be able to find the latest version of GD at
http://www.boutell.com/gd/
- Chart::Base module:
- ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
+ Chart::Base module: http://www.cpan.org/modules/by-module/Chart/
LinuxDoc Software: http://www.linuxdoc.org/ (for documentation
maintenance)
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. As
- time goes on, I will include many more in the Guide. For now,
- though, please refer to the mod_rewrite documentation at
- http://www.apache.org
+ 2. There are many, many more things you can do with
+ mod_rewrite. As time goes on, I will include many more in the
+ Guide. For now, though, please refer to the mod_rewrite
+ documentation at http://www.apache.org
_________________________________________________________________
D.2. The setperl.csh Utility
favorite shell prompt.
What appears below if a brief summary, please refer to the perl style
- guide if you don't see your question covered here.
+ guide if you don't see your question covered here. It is much better
+ to submit a patch which fails these criteria than no patch at all, but
+ please try to meet these minimum standards when submitting code to
+ Bugzilla.
* Whitespace
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
}
+ * Cookies
+ Bugzilla uses cookies to ease the user experience, but no new
+ patches should require user-side cookies.
* File Names
File names for bugzilla code and support documention should be
legal across multiple platforms. \ / : * ? " < > and | are all
illegal characters for filenames on various platforms. Also, file
names should not have spaces in them as they can cause confusion
in CVS and other mozilla.org utilities.
+ * Javascript dependencies
+ While Bugzilla uses Javascript to make the user experience easier,
+ no patch to Bugzilla should require Javascript.
+ * Patch Format
+ All patches submitted for inclusion into Bugzilla should be in the
+ form of a "unified diff". This comes from using "diff -u" instead
+ of simply "diff" when creating your patch. This will result in
+ quicker acceptance of the patch.
+ * Schema Changes
+ If you make schema changes, you should modify sanitycheck.cgi to
+ support the new schema. All referential columns should be checked.
+ * Taint Mode
+ All new cgis must run in Taint mode (Perl taint and DBI taint),
+ and existing cgi's which run in taint mode must not have taint
+ mode turned off.
+ * Templatization
+ Patches to Bugzilla need to support templates so they do not force
+ user interface choices on Bugzilla administrators.
* Variable Names
If a variable is scoped globally ($::variable) its name should be
descriptive of what it contains. Local variables can be named a
projects / thirdparty / bugzilla.git / commitdiff
