diff options
Diffstat (limited to 'docs/html/Bugzilla-Guide.html')
| -rw-r--r-- | docs/html/Bugzilla-Guide.html | 1111 |
1 files changed, 832 insertions, 279 deletions
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html index 216216cc5..3b3283361 100644 --- a/docs/html/Bugzilla-Guide.html +++ b/docs/html/Bugzilla-Guide.html @@ -4,8 +4,7 @@ >The Bugzilla Guide - 2.17.5 Development Release</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><META +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><META NAME="KEYWORD" CONTENT="Bugzilla"><META NAME="KEYWORD" @@ -34,20 +33,28 @@ ALINK="#0000FF" ><DIV CLASS="BOOK" ><A -NAME="index"><DIV +NAME="index" +></A +><DIV CLASS="TITLEPAGE" ><H1 CLASS="title" ><A -NAME="AEN2">The Bugzilla Guide - 2.17.5 Development Release</H1 +NAME="AEN2" +></A +>The Bugzilla Guide - 2.17.5 Development Release</H1 ><H3 CLASS="author" ><A -NAME="AEN5">Matthew P. Barnson</H3 +NAME="AEN5" +></A +>Matthew P. Barnson</H3 ><H3 CLASS="author" ><A -NAME="AEN9">Jacob Steenhagen</H3 +NAME="AEN9" +></A +>Jacob Steenhagen</H3 ><H3 CLASS="corpauthor" >The Bugzilla Team</H3 @@ -58,7 +65,9 @@ CLASS="pubdate" ><DIV CLASS="abstract" ><A -NAME="AEN14"><P +NAME="AEN14" +></A +><P ></P ><P > This is the documentation for Bugzilla, the mozilla.org @@ -503,15 +512,21 @@ HREF="#upgrade-patches" CLASS="chapter" ><HR><H1 ><A -NAME="about">Chapter 1. About This Guide</H1 +NAME="about" +></A +>Chapter 1. About This Guide</H1 ><DIV CLASS="section" ><H1 CLASS="section" ><A -NAME="copyright">1.1. Copyright Information</H1 +NAME="copyright" +></A +>1.1. Copyright Information</H1 ><A -NAME="AEN35"><TABLE +NAME="AEN35" +></A +><TABLE BORDER="0" WIDTH="100%" CELLSPACING="0" @@ -567,7 +582,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="disclaimer">1.2. Disclaimer</H1 +NAME="disclaimer" +></A +>1.2. Disclaimer</H1 ><P > No liability for the contents of this document can be accepted. Use the concepts, examples, and other content at your own risk. @@ -615,7 +632,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="newversions">1.3. New Versions</H1 +NAME="newversions" +></A +>1.3. New Versions</H1 ><P > This is the 2.17.5 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. @@ -674,7 +693,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="credits">1.4. Credits</H1 +NAME="credits" +></A +>1.4. Credits</H1 ><P > The people listed below have made enormous contributions to the creation of this Guide, through their writing, dedicated hacking efforts, @@ -798,13 +819,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="conventions">1.5. Document Conventions</H1 +NAME="conventions" +></A +>1.5. Document Conventions</H1 ><P >This document uses the following conventions:</P ><DIV CLASS="informaltable" ><A -NAME="AEN113"><P +NAME="AEN113" +></A +><P ></P ><TABLE BORDER="0" @@ -1160,13 +1185,17 @@ CLASS="sgmltag" CLASS="chapter" ><HR><H1 ><A -NAME="introduction">Chapter 2. Introduction</H1 +NAME="introduction" +></A +>Chapter 2. Introduction</H1 ><DIV CLASS="section" ><H1 CLASS="section" ><A -NAME="whatis">2.1. What is Bugzilla?</H1 +NAME="whatis" +></A +>2.1. What is Bugzilla?</H1 ><P > Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track @@ -1244,7 +1273,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="why">2.2. Why Should We Use Bugzilla?</H1 +NAME="why" +></A +>2.2. Why Should We Use Bugzilla?</H1 ><P >For many years, defect-tracking software has remained principally the domain of large software development houses. Even then, most shops @@ -1316,13 +1347,17 @@ TARGET="_top" CLASS="chapter" ><HR><H1 ><A -NAME="using">Chapter 3. Using Bugzilla</H1 +NAME="using" +></A +>Chapter 3. Using Bugzilla</H1 ><DIV CLASS="section" ><H1 CLASS="section" ><A -NAME="how">3.1. How do I use Bugzilla?</H1 +NAME="how" +></A +>3.1. How do I use Bugzilla?</H1 ><P >This section contains information for end-users of Bugzilla. There is a Bugzilla test installation, called @@ -1341,7 +1376,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="myaccount">3.1.1. Create a Bugzilla Account</H2 +NAME="myaccount" +></A +>3.1.1. Create a Bugzilla Account</H2 ><P >If you want to use Bugzilla, first you need to create an account. Consult with the administrator responsible for your installation of @@ -1409,7 +1446,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="bug_page">3.1.2. Anatomy of a Bug</H2 +NAME="bug_page" +></A +>3.1.2. Anatomy of a Bug</H2 ><P >The core of Bugzilla is the screen which displays a particular bug. It's a good place to explain some Bugzilla concepts. @@ -1674,7 +1713,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="query">3.1.3. Searching for Bugs</H2 +NAME="query" +></A +>3.1.3. Searching for Bugs</H2 ><P >The Bugzilla Search page is is the interface where you can find any bug report, comment, or patch currently in the Bugzilla system. You @@ -1702,7 +1743,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="list">3.1.4. Bug Lists</H2 +NAME="list" +></A +>3.1.4. Bug Lists</H2 ><P >If you run a search, a list of matching bugs will be returned. The default search is to return all open bugs on the system - don't try @@ -1774,7 +1817,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="bugreports">3.1.5. Filing Bugs</H2 +NAME="bugreports" +></A +>3.1.5. Filing Bugs</H2 ><P >Years of bug writing experience has been distilled for your reading pleasure into the @@ -1832,7 +1877,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="patchviewer">3.1.6. Patch Viewer</H2 +NAME="patchviewer" +></A +>3.1.6. Patch Viewer</H2 ><P >Viewing and reviewing patches in Bugzilla is often difficult due to lack of context, improper format and the inherent readability issues that @@ -1888,7 +1935,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_view">3.1.6.1. Viewing Patches in Patch Viewer</H3 +NAME="patchviewer_view" +></A +>3.1.6.1. Viewing Patches in Patch Viewer</H3 ><P >The main way to view a patch in patch viewer is to click on the "Diff" link next to a patch in the Attachments list on a bug. You may @@ -1900,7 +1949,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_diff">3.1.6.2. Seeing the Difference Between Two Patches</H3 +NAME="patchviewer_diff" +></A +>3.1.6.2. Seeing the Difference Between Two Patches</H3 ><P >To see the difference between two patches, you must first view the newer patch in Patch Viewer. Then select the older patch from the @@ -1913,7 +1964,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_context">3.1.6.3. Getting More Context in a Patch</H3 +NAME="patchviewer_context" +></A +>3.1.6.3. Getting More Context in a Patch</H3 ><P >To get more context in a patch, you put a number in the textbox at the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. @@ -1927,7 +1980,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_collapse">3.1.6.4. Collapsing and Expanding Sections of a Patch</H3 +NAME="patchviewer_collapse" +></A +>3.1.6.4. Collapsing and Expanding Sections of a Patch</H3 ><P >To view only a certain set of files in a patch (for example, if a patch is absolutely huge and you want to only review part of it at a @@ -1941,7 +1996,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_link">3.1.6.5. Linking to a Section of a Patch</H3 +NAME="patchviewer_link" +></A +>3.1.6.5. Linking to a Section of a Patch</H3 ><P >To link to a section of a patch (for example, if you want to be able to give someone a URL to show them which part you are talking @@ -1954,7 +2011,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_bonsai_lxr">3.1.6.6. Going to Bonsai and LXR</H3 +NAME="patchviewer_bonsai_lxr" +></A +>3.1.6.6. Going to Bonsai and LXR</H3 ><P >To go to Bonsai to get blame for the lines you are interested in, you can click the "Lines XX-YY" link on the section header you are @@ -1970,7 +2029,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="patchviewer_unified_diff">3.1.6.7. Creating a Unified Diff</H3 +NAME="patchviewer_unified_diff" +></A +>3.1.6.7. Creating a Unified Diff</H3 ><P >If the patch is not in a format that you like, you can turn it into a unified diff format by clicking the "Raw Unified" link at the top @@ -1983,7 +2044,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="hintsandtips">3.2. Hints and Tips</H1 +NAME="hintsandtips" +></A +>3.2. Hints and Tips</H1 ><P >This section distills some Bugzilla tips and best practices that have been developed.</P @@ -1992,7 +2055,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN407">3.2.1. Autolinkification</H2 +NAME="AEN407" +></A +>3.2.1. Autolinkification</H2 ><P >Bugzilla comments are plain text - so posting HTML will result in literal HTML tags rather than being interpreted by a browser. @@ -2055,7 +2120,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="quicksearch">3.2.2. Quicksearch</H2 +NAME="quicksearch" +></A +>3.2.2. Quicksearch</H2 ><P >Quicksearch is a single-text-box query tool which uses metacharacters to indicate what is to be searched. For example, typing @@ -2086,7 +2153,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="commenting">3.2.3. Comments</H2 +NAME="commenting" +></A +>3.2.3. Comments</H2 ><P >If you are changing the fields on a bug, only comment if either you have something pertinent to say, or Bugzilla requires it. @@ -2108,7 +2177,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="attachments">3.2.4. Attachments</H2 +NAME="attachments" +></A +>3.2.4. Attachments</H2 ><P > Use attachments, rather than comments, for large chunks of ASCII data, such as trace, debugging output files, or log files. That way, it doesn't @@ -2132,7 +2203,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN436">3.2.5. Filing Bugs</H2 +NAME="AEN436" +></A +>3.2.5. Filing Bugs</H2 ><P >Try to make sure that everything said in the summary is also said in the first comment. Summaries are often updated and this will @@ -2156,7 +2229,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="userpreferences">3.3. User Preferences</H1 +NAME="userpreferences" +></A +>3.3. User Preferences</H1 ><P >Once you have logged in, you can customise various aspects of Bugzilla via the "Edit prefs" link in the page footer. @@ -2166,7 +2241,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="accountsettings">3.3.1. Account Settings</H2 +NAME="accountsettings" +></A +>3.3.1. Account Settings</H2 ><P >On this tab, you can change your basic account information, including your password, email address and real name. For security @@ -2189,7 +2266,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="emailsettings">3.3.2. Email Settings</H2 +NAME="emailsettings" +></A +>3.3.2. Email Settings</H2 ><P >On this tab you can reduce or increase the amount of email sent you from Bugzilla, opting in our out depending on your relationship to @@ -2236,7 +2315,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="footersettings">3.3.3. Page Footer</H2 +NAME="footersettings" +></A +>3.3.3. Page Footer</H2 ><P >On the Search page, you can store queries in Bugzilla, so if you regularly run a particular query it is just a drop-down menu away. @@ -2248,7 +2329,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="permissionsettings">3.3.4. Permissions</H2 +NAME="permissionsettings" +></A +>3.3.4. Permissions</H2 ><P >This is a purely informative page which outlines your current permissions on this installation of Bugzilla - what product groups you @@ -2261,13 +2344,17 @@ NAME="permissionsettings">3.3.4. Permissions</H2 CLASS="chapter" ><HR><H1 ><A -NAME="installation">Chapter 4. Installation</H1 +NAME="installation" +></A +>Chapter 4. Installation</H1 ><DIV CLASS="section" ><H1 CLASS="section" ><A -NAME="stepbystep">4.1. Step-by-step Install</H1 +NAME="stepbystep" +></A +>4.1. Step-by-step Install</H1 ><P >Bugzilla has been successfully installed under many different operating systems including almost all Unix clones and @@ -2421,7 +2508,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-mysql">4.1.1. MySQL</H2 +NAME="install-mysql" +></A +>4.1.1. MySQL</H2 ><P >Visit the MySQL homepage at <A @@ -2493,7 +2582,9 @@ CLASS="filename" ><DIV CLASS="figure" ><A -NAME="install-mysql-packets"><P +NAME="install-mysql-packets" +></A +><P ><B >Figure 4-1. Set Max Packet Size in MySQL</B ></P @@ -2533,7 +2624,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-perl">4.1.2. Perl</H2 +NAME="install-perl" +></A +>4.1.2. Perl</H2 ><P >Any machine that doesn't have Perl on it is a sad machine indeed. Perl can be got in source form from <A @@ -2553,7 +2646,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-perlmodules">4.1.3. Perl Modules</H2 +NAME="install-perlmodules" +></A +>4.1.3. Perl Modules</H2 ><P >Perl modules can be found using <A @@ -2587,7 +2682,9 @@ HREF="#win32-perlmodules" ><DIV CLASS="example" ><A -NAME="install-perlmodules-cpan"><P +NAME="install-perlmodules-cpan" +></A +><P ><B >Example 4-1. Installing perl modules with CPAN</B ></P @@ -2954,7 +3051,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-bundle-bugzilla">4.1.3.1. Bundle::Bugzilla</H3 +NAME="install-modules-bundle-bugzilla" +></A +>4.1.3.1. Bundle::Bugzilla</H3 ><P >If you are running at least perl 5.6.1, you can save yourself a lot of time by using Bundle::Bugzilla. This bundle contains every module @@ -3031,7 +3130,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-appconfig">4.1.3.2. AppConfig (1.52)</H3 +NAME="install-modules-appconfig" +></A +>4.1.3.2. AppConfig (1.52)</H3 ><P >Dependency for Template Toolkit. We probably don't need to specifically check for it anymore. @@ -3042,7 +3143,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-cgi">4.1.3.3. CGI (2.88)</H3 +NAME="install-modules-cgi" +></A +>4.1.3.3. CGI (2.88)</H3 ><P >The CGI module parses form elements and cookies and does many other usefule things. It come as a part of recent perl distributions, but @@ -3073,7 +3176,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-data-dumper">4.1.3.4. Data::Dumper (any)</H3 +NAME="install-modules-data-dumper" +></A +>4.1.3.4. Data::Dumper (any)</H3 ><P >The Data::Dumper module provides data structure persistence for Perl (similar to Java's serialization). It comes with later @@ -3105,7 +3210,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-date-format">4.1.3.5. TimeDate modules (2.21)</H3 +NAME="install-modules-date-format" +></A +>4.1.3.5. TimeDate modules (2.21)</H3 ><P >Many of the more common date/time/calendar related Perl modules have been grouped into a bundle similar to the MySQL modules bundle. @@ -3138,7 +3245,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-dbi">4.1.3.6. DBI (1.32)</H3 +NAME="install-modules-dbi" +></A +>4.1.3.6. DBI (1.32)</H3 ><P >The DBI module is a generic Perl module used the MySQL-related modules. As long as your Perl installation was done @@ -3170,7 +3279,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-dbd-mysql">4.1.3.7. MySQL-related modules</H3 +NAME="install-modules-dbd-mysql" +></A +>4.1.3.7. MySQL-related modules</H3 ><P >The Perl/MySQL interface requires a few mutually-dependent Perl modules. These modules are grouped together into the the @@ -3213,7 +3324,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-file-spec">4.1.3.8. File::Spec (0.82)</H3 +NAME="install-file-spec" +></A +>4.1.3.8. File::Spec (0.82)</H3 ><P >File::Spec is a perl module that allows file operations, such as generating full path names, to work cross platform. @@ -3243,7 +3356,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-file-temp">4.1.3.9. File::Temp (any)</H3 +NAME="install-modules-file-temp" +></A +>4.1.3.9. File::Temp (any)</H3 ><P >File::Temp is used to generate a temporary filename that is guaranteed to be unique. It comes as a standard part of perl @@ -3273,7 +3388,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-template">4.1.3.10. Template Toolkit (2.08)</H3 +NAME="install-modules-template" +></A +>4.1.3.10. Template Toolkit (2.08)</H3 ><P >When you install Template Toolkit, you'll get asked various questions about features to enable. The defaults are fine, except @@ -3305,7 +3422,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-text-wrap">4.1.3.11. Text::Wrap (2001.0131)</H3 +NAME="install-modules-text-wrap" +></A +>4.1.3.11. Text::Wrap (2001.0131)</H3 ><P >Text::Wrap is designed to proved intelligent text wrapping. </P @@ -3329,7 +3448,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-gd">4.1.3.12. GD (1.20) [optional]</H3 +NAME="install-modules-gd" +></A +>4.1.3.12. GD (1.20) [optional]</H3 ><P >The GD library was written by Thomas Boutell a long while ago to programmatically generate images in C. Since then it's become the @@ -3437,7 +3558,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-chart-base">4.1.3.13. Chart::Base (0.99c) [optional]</H3 +NAME="install-modules-chart-base" +></A +>4.1.3.13. Chart::Base (0.99c) [optional]</H3 ><P >The Chart module provides Bugzilla with on-the-fly charting abilities. It can be installed in the usual fashion after it has been @@ -3464,7 +3587,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-xml-parser">4.1.3.14. XML::Parser (any) [Optional]</H3 +NAME="install-modules-xml-parser" +></A +>4.1.3.14. XML::Parser (any) [Optional]</H3 ><P >XML::Parser is used by the <TT CLASS="filename" @@ -3497,7 +3622,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-gd-graph">4.1.3.15. GD::Graph (any) [Optional]</H3 +NAME="install-modules-gd-graph" +></A +>4.1.3.15. GD::Graph (any) [Optional]</H3 ><P >In addition to GD listed above, the reporting interface of Bugzilla needs to have the GD::Graph module installed. @@ -3527,7 +3654,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-gd-text-align">4.1.3.16. GD::Text::Align (any) [Optional]</H3 +NAME="install-modules-gd-text-align" +></A +>4.1.3.16. GD::Text::Align (any) [Optional]</H3 ><P >GD::Text::Align, as the name implies, is used to draw aligned strings of text. It is needed by the reporting interface. @@ -3557,7 +3686,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-mime-parser">4.1.3.17. MIME::Parser (any) [Optional]</H3 +NAME="install-modules-mime-parser" +></A +>4.1.3.17. MIME::Parser (any) [Optional]</H3 ><P >MIME::Parser is only needed if you want to use the e-mail interface located in the <TT @@ -3590,7 +3721,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="install-modules-patchreader">4.1.3.18. PatchReader (0.9.1) [Optional]</H3 +NAME="install-modules-patchreader" +></A +>4.1.3.18. PatchReader (0.9.1) [Optional]</H3 ><P >PatchReader is only needed if you want to use Patch Viewer, a Bugzilla feature to format patches in a pretty HTML fashion. There are a @@ -3626,7 +3759,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-webserver">4.1.4. HTTP Server</H2 +NAME="install-webserver" +></A +>4.1.4. HTTP Server</H2 ><P >You have freedom of choice here, pretty much any web server that is capable of running <A @@ -3682,7 +3817,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-bzfiles">4.1.5. Bugzilla</H2 +NAME="install-bzfiles" +></A +>4.1.5. Bugzilla</H2 ><P >You should untar the Bugzilla files into a directory that you're willing to make writable by the default web server user (probably @@ -3794,7 +3931,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-setupdatabase">4.1.6. Setting Up the MySQL Database</H2 +NAME="install-setupdatabase" +></A +>4.1.6. Setting Up the MySQL Database</H2 ><P >After you've gotten all the software installed and working you're ready to start preparing the database for its life as the back end to @@ -3949,7 +4088,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN795">4.1.7. <TT +NAME="AEN795" +></A +>4.1.7. <TT CLASS="filename" >checksetup.pl</TT ></H2 @@ -4097,7 +4238,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN826">4.1.8. Configuring Bugzilla</H2 +NAME="AEN826" +></A +>4.1.8. Configuring Bugzilla</H2 ><P > You should run through the parameters on the Edit Parameters page (link in the footer) and set them all to appropriate values. @@ -4113,13 +4256,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="extraconfig">4.2. Optional Additional Configuration</H1 +NAME="extraconfig" +></A +>4.2. Optional Additional Configuration</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN832">4.2.1. Dependency Charts</H2 +NAME="AEN832" +></A +>4.2.1. Dependency Charts</H2 ><P >As well as the text-based dependency graphs, Bugzilla also supports dependency graphing, using a package called 'dot'. @@ -4181,7 +4328,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN847">4.2.2. Bug Graphs</H2 +NAME="AEN847" +></A +>4.2.2. Bug Graphs</H2 ><P >As long as you installed the GD and Graph::Base Perl modules you might as well turn on the nifty Bugzilla bug reporting graphs.</P @@ -4238,7 +4387,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN860">4.2.3. The Whining Cron</H2 +NAME="AEN860" +></A +>4.2.3. The Whining Cron</H2 ><P >By now you have a fully functional Bugzilla, but what good are bugs if they're not annoying? To help make those bugs more annoying you @@ -4325,7 +4476,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="bzldap">4.2.4. LDAP Authentication</H2 +NAME="bzldap" +></A +>4.2.4. LDAP Authentication</H2 ><DIV CLASS="note" ><P @@ -4444,7 +4597,9 @@ CLASS="variablelist" ><DL ><DT ><A -NAME="param-loginmethod">loginmethod</DT +NAME="param-loginmethod" +></A +>loginmethod</DT ><DD ><P >This parameter should be set to <SPAN @@ -4473,7 +4628,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="param-LDAPserver">LDAPserver</DT +NAME="param-LDAPserver" +></A +>LDAPserver</DT ><DD ><P >This parameter should be set to the name (and optionally the @@ -4493,7 +4650,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="param-LDAPbinddn">LDAPbinddn [Optional]</DT +NAME="param-LDAPbinddn" +></A +>LDAPbinddn [Optional]</DT ><DD ><P >Some LDAP servers will not allow an anonymous bind to search @@ -4509,7 +4668,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="param-LDAPBaseDN">LDAPBaseDN</DT +NAME="param-LDAPBaseDN" +></A +>LDAPBaseDN</DT ><DD ><P >The LDAPBaseDN parameter should be set to the location in @@ -4524,7 +4685,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="param-LDAPuidattribute">LDAPuidattribute</DT +NAME="param-LDAPuidattribute" +></A +>LDAPuidattribute</DT ><DD ><P >The LDAPuidattribute parameter should be set to the attribute @@ -4540,7 +4703,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="param-LDAPmailattribute">LDAPmailattribute</DT +NAME="param-LDAPmailattribute" +></A +>LDAPmailattribute</DT ><DD ><P >The LDAPmailattribute parameter should be the name of the @@ -4561,7 +4726,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious +NAME="content-type" +></A +>4.2.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</H2 ><P >It is possible for a Bugzilla to execute malicious Javascript @@ -4665,7 +4832,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="directoryindex">4.2.6. <TT +NAME="directoryindex" +></A +>4.2.6. <TT CLASS="filename" >directoryindex</TT > for the Bugzilla default page.</H2 @@ -4690,7 +4859,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="mod_perl">4.2.7. Bugzilla and <TT +NAME="mod_perl" +></A +>4.2.7. Bugzilla and <TT CLASS="filename" >mod_perl</TT ></H2 @@ -4705,7 +4876,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="mod-throttle">4.2.8. <TT +NAME="mod-throttle" +></A +>4.2.8. <TT CLASS="filename" >mod_throttle</TT > @@ -4754,7 +4927,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="os-specific">4.3. OS Specific Installation Notes</H1 +NAME="os-specific" +></A +>4.3. OS Specific Installation Notes</H1 ><P >Many aspects of the Bugzilla installation can be affected by the the operating system you choose to install it on. Sometimes it can be made @@ -4775,7 +4950,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="os-win32">4.3.1. Microsoft Windows</H2 +NAME="os-win32" +></A +>4.3.1. Microsoft Windows</H2 ><P >Making Bugzilla work on windows is still a very painful processes. The Bugzilla Team is working to make it easier, but that goal is not @@ -4799,7 +4976,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="win32-perl">4.3.1.1. Win32 Perl</H3 +NAME="win32-perl" +></A +>4.3.1.1. Win32 Perl</H3 ><P >Perl for Windows can be obtained from <A HREF="http://www.activestate.com/" @@ -4818,7 +4997,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="win32-perlmodules">4.3.1.2. Perl Modules on Win32</H3 +NAME="win32-perlmodules" +></A +>4.3.1.2. Perl Modules on Win32</H3 ><P >Bugzilla on Windows requires the same perl modules found in <A @@ -4928,7 +5109,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="win32-code-changes">4.3.1.3. Code changes required to run on win32</H3 +NAME="win32-code-changes" +></A +>4.3.1.3. Code changes required to run on win32</H3 ><P >Unfortunately, Bugzilla still doesn't run "out of the box" on Windows. There is work in progress to make this easier, but until that @@ -4946,7 +5129,9 @@ CLASS="section" ><HR><H4 CLASS="section" ><A -NAME="win32-code-checksetup">4.3.1.3.1. Changes to <TT +NAME="win32-code-checksetup" +></A +>4.3.1.3.1. Changes to <TT CLASS="filename" >checksetup.pl</TT ></H4 @@ -5031,7 +5216,9 @@ CLASS="section" ><HR><H4 CLASS="section" ><A -NAME="win32-code-bugmail">4.3.1.3.2. Changes to <TT +NAME="win32-code-bugmail" +></A +>4.3.1.3.2. Changes to <TT CLASS="filename" >BugMail.pm</TT ></H4 @@ -5110,7 +5297,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="win32-http">4.3.1.4. Serving the web pages</H3 +NAME="win32-http" +></A +>4.3.1.4. Serving the web pages</H3 ><P >As is the case on Unix based systems, any web server should be able to handle Bugzilla; however, the Bugzilla Team still recommends @@ -5169,7 +5358,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="os-macosx">4.3.2. <SPAN +NAME="os-macosx" +></A +>4.3.2. <SPAN CLASS="productname" >Mac OS X</SPAN ></H2 @@ -5361,7 +5552,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="os-mandrake">4.3.3. Linux-Mandrake 8.0</H2 +NAME="os-mandrake" +></A +>4.3.3. Linux-Mandrake 8.0</H2 ><P >Linux-Mandrake 8.0 includes every required and optional library for Bugzilla. The easiest way to install them is by using the @@ -5459,7 +5652,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="http">4.4. HTTP Server Configuration</H1 +NAME="http" +></A +>4.4. HTTP Server Configuration</H1 ><P >The Bugzilla Team recommends Apache when using Bugzilla, however, any web server that can be configured to run <A @@ -5485,7 +5680,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="http-apache">4.4.1. Apache <SPAN +NAME="http-apache" +></A +>4.4.1. Apache <SPAN CLASS="productname" >httpd</SPAN ></H2 @@ -5619,7 +5816,9 @@ CLASS="glossterm" ><DIV CLASS="example" ><A -NAME="http-apache-htaccess"><P +NAME="http-apache-htaccess" +></A +><P ><B >Example 4-2. <TT CLASS="filename" @@ -5779,7 +5978,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="http-iis">4.4.2. Microsoft <SPAN +NAME="http-iis" +></A +>4.4.2. Microsoft <SPAN CLASS="productname" >Internet Information Services</SPAN ></H2 @@ -5834,7 +6035,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="http-aol">4.4.3. AOL Server</H2 +NAME="http-aol" +></A +>4.4.3. AOL Server</H2 ><P >Ben FrantzDale reported success using AOL Server with Bugzilla. He reported his experience and what appears below is based on that. @@ -6012,7 +6215,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="troubleshooting">4.5. Troubleshooting</H1 +NAME="troubleshooting" +></A +>4.5. Troubleshooting</H1 ><P >This section gives solutions to common Bugzilla installation problems. @@ -6022,7 +6227,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1157">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 +NAME="AEN1157" +></A +>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 ><P > Try executing <B CLASS="command" @@ -6045,7 +6252,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1162">4.5.2. DBD::Sponge::db prepare failed</H2 +NAME="AEN1162" +></A +>4.5.2. DBD::Sponge::db prepare failed</H2 ><P > The following error message may appear due to a bug in DBD::mysql (over which the Bugzilla team have no control): @@ -6129,7 +6338,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2 +NAME="paranoid-security" +></A +>4.5.3. cannot chdir(/var/spool/mqueue)</H2 ><P >If you are installing Bugzilla on SuSE Linux, or some other distributions with @@ -6185,7 +6396,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="trouble-filetemp">4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 +NAME="trouble-filetemp" +></A +>4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 ><P >This is caused by a bug in the version of <SPAN @@ -6201,7 +6414,9 @@ HREF="#trouble-filetemp-errors" ><DIV CLASS="figure" ><A -NAME="trouble-filetemp-errors"><P +NAME="trouble-filetemp-errors" +></A +><P ><B >Figure 4-2. Other File::Temp error messages</B ></P @@ -6245,7 +6460,9 @@ TARGET="_top" ><DIV CLASS="figure" ><A -NAME="trouble-filetemp-patch"><P +NAME="trouble-filetemp-patch" +></A +><P ><B >Figure 4-3. Patch for File::Temp in Perl 5.6.0</B ></P @@ -6290,13 +6507,17 @@ CLASS="programlisting" CLASS="chapter" ><HR><H1 ><A -NAME="administration">Chapter 5. Administering Bugzilla</H1 +NAME="administration" +></A +>Chapter 5. Administering Bugzilla</H1 ><DIV CLASS="section" ><H1 CLASS="section" ><A -NAME="parameters">5.1. Bugzilla Configuration</H1 +NAME="parameters" +></A +>5.1. Bugzilla Configuration</H1 ><P >Bugzilla is configured by changing various parameters, accessed from the "Edit parameters" link in the page footer. Here are @@ -6573,13 +6794,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="useradmin">5.2. User Administration</H1 +NAME="useradmin" +></A +>5.2. User Administration</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="defaultuser">5.2.1. Creating the Default User</H2 +NAME="defaultuser" +></A +>5.2.1. Creating the Default User</H2 ><P >When you first run checksetup.pl after installing Bugzilla, it will prompt you for the administrative username (email address) and @@ -6622,13 +6847,17 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="manageusers">5.2.2. Managing Other Users</H2 +NAME="manageusers" +></A +>5.2.2. Managing Other Users</H2 ><DIV CLASS="section" ><H3 CLASS="section" ><A -NAME="createnewusers">5.2.2.1. Creating new users</H3 +NAME="createnewusers" +></A +>5.2.2.1. Creating new users</H3 ><P >Your users can create their own user accounts by clicking the "New Account" link at the bottom of each page (assuming they @@ -6699,7 +6928,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="modifyusers">5.2.2.2. Modifying Users</H3 +NAME="modifyusers" +></A +>5.2.2.2. Modifying Users</H3 ><P >To see a specific user, search for their login name in the box provided on the "Edit Users" page. To see all users, @@ -6928,13 +7159,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1 +NAME="programadmin" +></A +>5.3. Product, Component, Milestone, and Version Administration</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="products">5.3.1. Products</H2 +NAME="products" +></A +>5.3.1. Products</H2 ><P > <A HREF="#gloss-product" @@ -6988,7 +7223,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="components">5.3.2. Components</H2 +NAME="components" +></A +>5.3.2. Components</H2 ><P >Components are subsections of a Product. E.g. the computer game you are designing may have a "UI" @@ -7041,7 +7278,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="versions">5.3.3. Versions</H2 +NAME="versions" +></A +>5.3.3. Versions</H2 ><P >Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select @@ -7075,7 +7314,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="milestones">5.3.4. Milestones</H2 +NAME="milestones" +></A +>5.3.4. Milestones</H2 ><P >Milestones are "targets" that you plan to get a bug fixed by. For example, you have a bug that you plan to fix for your 3.0 release, it @@ -7176,7 +7417,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="voting">5.4. Voting</H1 +NAME="voting" +></A +>5.4. Voting</H1 ><P >Voting allows users to be given a pot of votes which they can allocate to bugs, to indicate that they'd like them fixed. @@ -7236,7 +7479,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="groups">5.5. Groups and Group Security</H1 +NAME="groups" +></A +>5.5. Groups and Group Security</H1 ><P >Groups allow the administrator to isolate bugs or products that should only be seen by certain people. @@ -7416,7 +7661,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="security">5.6. Bugzilla Security</H1 +NAME="security" +></A +>5.6. Bugzilla Security</H1 ><DIV CLASS="warning" ><P @@ -7515,7 +7762,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="security-networking">5.6.1. TCP/IP Ports</H2 +NAME="security-networking" +></A +>5.6.1. TCP/IP Ports</H2 ><P >TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only needs 1... 2 if you need to use features that require e-mail such @@ -7531,7 +7780,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="security-mysql">5.6.2. MySQL</H2 +NAME="security-mysql" +></A +>5.6.2. MySQL</H2 ><P >MySQL ships by default with many settings that should be changed. By defaults it allows anybody to connect from localhost without a @@ -7658,7 +7909,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="security-daemon">5.6.3. Daemon Accounts</H2 +NAME="security-daemon" +></A +>5.6.3. Daemon Accounts</H2 ><P >Many daemons, such as Apache's httpd and MySQL's mysqld default to running as either <SPAN @@ -7731,7 +7984,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="security-access">5.6.4. Web Server Access Controls</H2 +NAME="security-access" +></A +>5.6.4. Web Server Access Controls</H2 ><P >There are many files that are placed in the Bugzilla directory area that should not be accessable from the web. Because of the way @@ -8057,7 +8312,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="cust-templates">5.7. Template Customization</H1 +NAME="cust-templates" +></A +>5.7. Template Customization</H1 ><P > One of the large changes for 2.16 was the templatization of the entire user-facing UI, using the @@ -8085,7 +8342,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1606">5.7.1. What to Edit</H2 +NAME="AEN1606" +></A +>5.7.1. What to Edit</H2 ><P > There are two different ways of editing of Bugzilla's templates, and which you use depends mainly on how you upgrade Bugzilla. The @@ -8233,7 +8492,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1629">5.7.2. How To Edit Templates</H2 +NAME="AEN1629" +></A +>5.7.2. How To Edit Templates</H2 ><P > The syntax of the Template Toolkit language is beyond the scope of this guide. It's reasonably easy to pick up by looking at the current @@ -8313,7 +8574,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1639">5.7.3. Template Formats</H2 +NAME="AEN1639" +></A +>5.7.3. Template Formats</H2 ><P > Some CGIs have the ability to use more than one template. For example, buglist.cgi can output bug lists as RDF or two @@ -8373,7 +8636,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1652">5.7.4. Particular Templates</H2 +NAME="AEN1652" +></A +>5.7.4. Particular Templates</H2 ><P > There are a few templates you may be particularly interested in customizing for your installation. @@ -8560,7 +8825,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="template-http-accept">5.7.5. Configuring Bugzilla to Detect the User's Language</H2 +NAME="template-http-accept" +></A +>5.7.5. Configuring Bugzilla to Detect the User's Language</H2 ><P >Begining in version 2.18 (first introduced in version 2.17.4), it's now possible to have the users web browser tell Bugzilla @@ -8601,7 +8868,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="cust-change-permissions">5.8. Change Permission Customization</H1 +NAME="cust-change-permissions" +></A +>5.8. Change Permission Customization</H1 ><DIV CLASS="warning" ><P @@ -8770,7 +9039,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="upgrading">5.9. Upgrading to New Releases</H1 +NAME="upgrading" +></A +>5.9. Upgrading to New Releases</H1 ><DIV CLASS="warning" ><P @@ -8884,7 +9155,9 @@ CLASS="filename" ><DIV CLASS="example" ><A -NAME="upgrade-cvs"><P +NAME="upgrade-cvs" +></A +><P ><B >Example 5-1. Upgrading using CVS</B ></P @@ -9039,7 +9312,9 @@ CLASS="command" ><DIV CLASS="example" ><A -NAME="upgrade-tarball"><P +NAME="upgrade-tarball" +></A +><P ><B >Example 5-2. Upgrading using the tarball</B ></P @@ -9193,7 +9468,9 @@ VALIGN="TOP" ><DIV CLASS="example" ><A -NAME="upgrade-patches"><P +NAME="upgrade-patches" +></A +><P ><B >Example 5-3. Upgrading using patches</B ></P @@ -9292,13 +9569,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="integration">5.10. Integrating Bugzilla with Third-Party Tools</H1 +NAME="integration" +></A +>5.10. Integrating Bugzilla with Third-Party Tools</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="bonsai">5.10.1. Bonsai</H2 +NAME="bonsai" +></A +>5.10.1. Bonsai</H2 ><P >Bonsai is a web-based tool for managing <A @@ -9322,7 +9603,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="cvs">5.10.2. CVS</H2 +NAME="cvs" +></A +>5.10.2. CVS</H2 ><P >CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P @@ -9356,7 +9639,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="scm">5.10.3. Perforce SCM</H2 +NAME="scm" +></A +>5.10.3. Perforce SCM</H2 ><P >You can find the project page for Bugzilla and Teamtrack Perforce integration (p4dti) at: @@ -9394,7 +9679,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="tinderbox">5.10.4. Tinderbox/Tinderbox2</H2 +NAME="tinderbox" +></A +>5.10.4. Tinderbox/Tinderbox2</H2 ><P >We need Tinderbox integration information.</P ></DIV @@ -9404,7 +9691,9 @@ NAME="tinderbox">5.10.4. Tinderbox/Tinderbox2</H2 CLASS="appendix" ><HR><H1 ><A -NAME="faq">Appendix A. The Bugzilla FAQ</H1 +NAME="faq" +></A +>Appendix A. The Bugzilla FAQ</H1 ><P > This FAQ includes questions not covered elsewhere in the Guide. </P @@ -9900,14 +10189,18 @@ HREF="#faq-hacking-patches" CLASS="qandadiv" ><H3 ><A -NAME="faq-general">1. General Questions</H3 +NAME="faq-general" +></A +>1. General Questions</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-general-information"><B +NAME="faq-general-information" +></A +><B >A.1.1. </B > Where can I find information about Bugzilla?</P @@ -9933,7 +10226,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-license"><B +NAME="faq-general-license" +></A +><B >A.1.2. </B > What license is Bugzilla distributed under? @@ -9960,7 +10255,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-support"><B +NAME="faq-general-support" +></A +><B >A.1.3. </B > How do I get commercial support for Bugzilla? @@ -10004,7 +10301,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-companies"><B +NAME="faq-general-companies" +></A +><B >A.1.4. </B > What major companies or projects are currently using Bugzilla @@ -10049,7 +10348,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-maintainers"><B +NAME="faq-general-maintainers" +></A +><B >A.1.5. </B > Who maintains Bugzilla? @@ -10077,7 +10378,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-compare"><B +NAME="faq-general-compare" +></A +><B >A.1.6. </B > How does Bugzilla stack up against other bug-tracking databases? @@ -10113,7 +10416,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-bzmissing"><B +NAME="faq-general-bzmissing" +></A +><B >A.1.7. </B > Why doesn't Bugzilla offer this or that feature or compatibility @@ -10151,7 +10456,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-mysql"><B +NAME="faq-general-mysql" +></A +><B >A.1.8. </B > Why MySQL? I'm interested in seeing Bugzilla run on @@ -10194,7 +10501,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-bonsaitools"><B +NAME="faq-general-bonsaitools" +></A +><B >A.1.9. </B > What is <TT @@ -10234,7 +10543,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-perlpath"><B +NAME="faq-general-perlpath" +></A +><B >A.1.10. </B > My perl is not located at <TT @@ -10281,7 +10592,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-cookie"><B +NAME="faq-general-cookie" +></A +><B >A.1.11. </B > Is there an easy way to change the Bugzilla cookie name? @@ -10302,7 +10615,9 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-phb">2. Managerial Questions</H3 +NAME="faq-phb" +></A +>2. Managerial Questions</H3 ><P > <DIV CLASS="note" @@ -10339,7 +10654,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-client"><B +NAME="faq-phb-client" +></A +><B >A.2.1. </B > Is Bugzilla web-based, or do you have to have specific software or @@ -10363,7 +10680,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-integration"><B +NAME="faq-phb-integration" +></A +><B >A.2.2. </B > Can Bugzilla integrate with @@ -10387,7 +10706,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-projects"><B +NAME="faq-phb-projects" +></A +><B >A.2.3. </B > Does Bugzilla allow the user to track multiple projects? @@ -10410,7 +10731,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-sorting"><B +NAME="faq-phb-sorting" +></A +><B >A.2.4. </B > If I am on many projects, and search for all bugs assigned to me, will @@ -10433,7 +10756,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-attachments"><B +NAME="faq-phb-attachments" +></A +><B >A.2.5. </B > Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, @@ -10460,7 +10785,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-priorities"><B +NAME="faq-phb-priorities" +></A +><B >A.2.6. </B > Does Bugzilla allow us to define our own priorities and levels? Do we @@ -10495,7 +10822,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-reporting"><B +NAME="faq-phb-reporting" +></A +><B >A.2.7. </B > Does Bugzilla provide any reporting features, metrics, graphs, etc? You @@ -10531,7 +10860,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-email"><B +NAME="faq-phb-email" +></A +><B >A.2.8. </B > Is there email notification and if so, what do you see when you get an @@ -10556,7 +10887,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-cclist"><B +NAME="faq-phb-cclist" +></A +><B >A.2.9. </B > Can email notification be set up to send to multiple @@ -10579,7 +10912,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-emailapp"><B +NAME="faq-phb-emailapp" +></A +><B >A.2.10. </B > Do users have to have any particular @@ -10636,7 +10971,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-data"><B +NAME="faq-phb-data" +></A +><B >A.2.11. </B > Does Bugzilla allow data to be imported and exported? If I had outsiders @@ -10696,7 +11033,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-l10n"><B +NAME="faq-phb-l10n" +></A +><B >A.2.12. </B > Has anyone converted Bugzilla to another language to be used in other @@ -10732,7 +11071,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-reports"><B +NAME="faq-phb-reports" +></A +><B >A.2.13. </B > Can a user create and save reports? Can they do this in Word format? @@ -10755,7 +11096,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-searching"><B +NAME="faq-phb-searching" +></A +><B >A.2.14. </B > Does Bugzilla have the ability to search by word, phrase, compound @@ -10779,7 +11122,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-midair"><B +NAME="faq-phb-midair" +></A +><B >A.2.15. </B > Does Bugzilla provide record locking when there is simultaneous access @@ -10804,7 +11149,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-backup"><B +NAME="faq-phb-backup" +></A +><B >A.2.16. </B > Are there any backup features provided? @@ -10832,7 +11179,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-livebackup"><B +NAME="faq-phb-livebackup" +></A +><B >A.2.17. </B > Can users be on the system while a backup is in progress? @@ -10856,7 +11205,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-maintenance"><B +NAME="faq-phb-maintenance" +></A +><B >A.2.18. </B > What type of human resources are needed to be on staff to install and @@ -10889,7 +11240,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-installtime"><B +NAME="faq-phb-installtime" +></A +><B >A.2.19. </B > What time frame are we looking at if we decide to hire people to install @@ -10920,7 +11273,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-cost"><B +NAME="faq-phb-cost" +></A +><B >A.2.20. </B > Is there any licensing fee or other fees for using Bugzilla? Any @@ -10943,14 +11298,18 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-security">3. Bugzilla Security</H3 +NAME="faq-security" +></A +>3. Bugzilla Security</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-security-mysql"><B +NAME="faq-security-mysql" +></A +><B >A.3.1. </B > How do I completely disable MySQL security if it's giving me problems @@ -10977,7 +11336,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-security-knownproblems"><B +NAME="faq-security-knownproblems" +></A +><B >A.3.2. </B > Are there any security problems with Bugzilla? @@ -11003,7 +11364,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-security-mysqluser"><B +NAME="faq-security-mysqluser" +></A +><B >A.3.3. </B > I've implemented the security fixes mentioned in Chris Yeh's security @@ -11028,14 +11391,18 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-email">4. Bugzilla Email</H3 +NAME="faq-email" +></A +>4. Bugzilla Email</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-email-nomail"><B +NAME="faq-email-nomail" +></A +><B >A.4.1. </B > I have a user who doesn't want to receive any more email from Bugzilla. @@ -11063,7 +11430,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-testing"><B +NAME="faq-email-testing" +></A +><B >A.4.2. </B > I'm evaluating/testing Bugzilla, and don't want it to send email to @@ -11087,7 +11456,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-whine"><B +NAME="faq-email-whine" +></A +><B >A.4.3. </B > I want whineatnews.pl to whine at something more, or other than, only new @@ -11118,7 +11489,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-procmail"><B +NAME="faq-email-procmail" +></A +><B >A.4.4. </B > I don't like/want to use Procmail to hand mail off to bug_email.pl. @@ -11134,7 +11507,9 @@ CLASS="answer" You can call bug_email.pl directly from your aliases file, with an entry like this: <A -NAME="AEN2067"><BLOCKQUOTE +NAME="AEN2067" +></A +><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P > bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" @@ -11153,7 +11528,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-mailif"><B +NAME="faq-email-mailif" +></A +><B >A.4.5. </B > How do I set up the email interface to submit/change bugs via email? @@ -11176,7 +11553,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-sendmailnow"><B +NAME="faq-email-sendmailnow" +></A +><B >A.4.6. </B > Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. @@ -11235,7 +11614,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-nonreceived"><B +NAME="faq-email-nonreceived" +></A +><B >A.4.7. </B > How come email from Bugzilla changes never reaches me? @@ -11264,14 +11645,18 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-db">5. Bugzilla Database</H3 +NAME="faq-db" +></A +>5. Bugzilla Database</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-db-oracle"><B +NAME="faq-db-oracle" +></A +><B >A.5.1. </B > I've heard Bugzilla can be used with Oracle? @@ -11297,7 +11682,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-db-corrupted"><B +NAME="faq-db-corrupted" +></A +><B >A.5.2. </B > I think my database might be corrupted, or contain invalid entries. What @@ -11342,7 +11729,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-db-manualedit"><B +NAME="faq-db-manualedit" +></A +><B >A.5.3. </B > I want to manually edit some entries in my database. How? @@ -11381,7 +11770,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-db-permissions"><B +NAME="faq-db-permissions" +></A +><B >A.5.4. </B > I think I've set up MySQL permissions correctly, but Bugzilla still can't @@ -11440,7 +11831,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-db-synchronize"><B +NAME="faq-db-synchronize" +></A +><B >A.5.5. </B > How do I synchronize bug information among multiple different Bugzilla @@ -11475,14 +11868,18 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-nt">6. Bugzilla and Win32</H3 +NAME="faq-nt" +></A +>6. Bugzilla and Win32</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-nt-easiest"><B +NAME="faq-nt-easiest" +></A +><B >A.6.1. </B > What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? @@ -11505,7 +11902,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-nt-bundle"><B +NAME="faq-nt-bundle" +></A +><B >A.6.2. </B > Is there a "Bundle::Bugzilla" equivalent for Win32? @@ -11529,7 +11928,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-nt-mappings"><B +NAME="faq-nt-mappings" +></A +><B >A.6.3. </B > CGI's are failing with a "something.cgi is not a valid Windows NT @@ -11550,7 +11951,9 @@ CLASS="answer" ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN2150"><BLOCKQUOTE +NAME="AEN2150" +></A +><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P > "Set application mappings. In the ISM, map the extension for the script @@ -11573,7 +11976,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-nt-dbi"><B +NAME="faq-nt-dbi" +></A +><B >A.6.4. </B > I'm having trouble with the perl modules for NT not being able to talk to @@ -11639,14 +12044,18 @@ TARGET="_top" CLASS="qandadiv" ><H3 ><A -NAME="faq-use">7. Bugzilla Usage</H3 +NAME="faq-use" +></A +>7. Bugzilla Usage</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-use-changeaddress"><B +NAME="faq-use-changeaddress" +></A +><B >A.7.1. </B > How do I change my user name (email address) in Bugzilla? @@ -11669,7 +12078,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-use-query"><B +NAME="faq-use-query" +></A +><B >A.7.2. </B > The query page is very confusing. Isn't there a simpler way to query? @@ -11693,7 +12104,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-use-accept"><B +NAME="faq-use-accept" +></A +><B >A.7.3. </B > I'm confused by the behavior of the "accept" button in the Show Bug form. @@ -11745,7 +12158,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-use-attachment"><B +NAME="faq-use-attachment" +></A +><B >A.7.4. </B > I can't upload anything into the database via the "Create Attachment" @@ -11770,7 +12185,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-use-keyword"><B +NAME="faq-use-keyword" +></A +><B >A.7.5. </B > How do I change a keyword in Bugzilla, once some bugs are using it? @@ -11794,7 +12211,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-use-close"><B +NAME="faq-use-close" +></A +><B >A.7.6. </B > Why can't I close bugs from the "Change Several Bugs at Once" page? @@ -11828,14 +12247,18 @@ CLASS="answer" CLASS="qandadiv" ><H3 ><A -NAME="faq-hacking">8. Bugzilla Hacking</H3 +NAME="faq-hacking" +></A +>8. Bugzilla Hacking</H3 ><DIV CLASS="qandaentry" ><DIV CLASS="question" ><P ><A -NAME="faq-hacking-templatestyle"><B +NAME="faq-hacking-templatestyle" +></A +><B >A.8.1. </B > What kind of style should I use for templatization? @@ -11892,7 +12315,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-hacking-bugzillabugs"><B +NAME="faq-hacking-bugzillabugs" +></A +><B >A.8.2. </B > What bugs are in Bugzilla right now? @@ -11936,7 +12361,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-hacking-priority"><B +NAME="faq-hacking-priority" +></A +><B >A.8.3. </B > How can I change the default priority to a null value? For instance, have the default @@ -11965,7 +12392,9 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-hacking-patches"><B +NAME="faq-hacking-patches" +></A +><B >A.8.4. </B > What's the best way to submit patches? What guidelines should I follow? @@ -12040,7 +12469,9 @@ TARGET="_top" CLASS="appendix" ><HR><H1 ><A -NAME="database">Appendix B. The Bugzilla Database</H1 +NAME="database" +></A +>Appendix B. The Bugzilla Database</H1 ><DIV CLASS="note" ><P @@ -12074,7 +12505,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="dbmodify">B.1. Modifying Your Running System</H1 +NAME="dbmodify" +></A +>B.1. Modifying Your Running System</H1 ><P >Bugzilla optimizes database lookups by storing all relatively static information in the @@ -12121,7 +12554,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1 +NAME="dbdoc" +></A +>B.2. MySQL Bugzilla Database Introduction</H1 ><P >This information comes straight from my life. I was forced to learn how Bugzilla organizes database because of nitpicky requests from users @@ -12181,7 +12616,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN2279">B.2.1. Bugzilla Database Basics</H2 +NAME="AEN2279" +></A +>B.2.1. Bugzilla Database Basics</H2 ><P >If you were like me, at this point you're totally clueless about the internals of MySQL, and if it weren't for this executive order from @@ -12293,7 +12730,9 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="AEN2306">B.2.1.1. Bugzilla Database Tables</H3 +NAME="AEN2306" +></A +>B.2.1.1. Bugzilla Database Tables</H3 ><P >Imagine your MySQL database as a series of spreadsheets, and you won't be too far off. If you use this command:</P @@ -12528,7 +12967,9 @@ this. But you need to know this stuff an CLASS="appendix" ><HR><H1 ><A -NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1 +NAME="patches" +></A +>Appendix C. Useful Patches and Utilities for Bugzilla</H1 ><P >Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P @@ -12537,7 +12978,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="rewrite">C.1. Apache +NAME="rewrite" +></A +>C.1. Apache <TT CLASS="filename" >mod_rewrite</TT @@ -12606,7 +13049,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="cmdline">C.2. Command-line Bugzilla Queries</H1 +NAME="cmdline" +></A +>C.2. Command-line Bugzilla Queries</H1 ><P >There are a suite of Unix utilities for querying Bugzilla from the command line. They live in the @@ -12686,7 +13131,9 @@ CLASS="command" CLASS="appendix" ><HR><H1 ><A -NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1 +NAME="variants" +></A +>Appendix D. Bugzilla Variants and Competitors</H1 ><P >I created this section to answer questions about Bugzilla competitors and variants, then found a wonderful site which covers an awful lot of what @@ -12703,7 +13150,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-redhat">D.1. Red Hat Bugzilla</H1 +NAME="variant-redhat" +></A +>D.1. Red Hat Bugzilla</H1 ><P >Red Hat's old fork of Bugzilla which was based on version 2.8 is now obsolete. The newest version in use is based on version 2.17.1 and is in @@ -12735,7 +13184,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1 +NAME="variant-fenris" +></A +>D.2. Loki Bugzilla (Fenris)</H1 ><P >Fenris was a fork from Bugzilla made by Loki Games; when Loki went into receivership, it died. While Loki's other code lives on, @@ -12749,7 +13200,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-issuezilla">D.3. Issuezilla</H1 +NAME="variant-issuezilla" +></A +>D.3. Issuezilla</H1 ><P >Issuezilla was another fork from Bugzilla, made by collab.net and hosted at tigris.org. It is also dead; the primary focus of bug-tracking @@ -12766,7 +13219,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-scarab">D.4. Scarab</H1 +NAME="variant-scarab" +></A +>D.4. Scarab</H1 ><P >Scarab is a new open source bug-tracking system built using Java Servlet technology. It is currently at version 1.0 beta 13.</P @@ -12785,7 +13240,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-perforce">D.5. Perforce SCM</H1 +NAME="variant-perforce" +></A +>D.5. Perforce SCM</H1 ><P >Although Perforce isn't really a bug tracker, it can be used as such through the <SPAN @@ -12808,7 +13265,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="variant-sourceforge">D.6. SourceForge</H1 +NAME="variant-sourceforge" +></A +>D.6. SourceForge</H1 ><P >SourceForge is a way of coordinating geographically distributed free software and open source projects over the Internet. @@ -12828,11 +13287,15 @@ TARGET="_top" CLASS="appendix" ><HR><H1 ><A -NAME="gfdl">Appendix E. GNU Free Documentation License</H1 +NAME="gfdl" +></A +>Appendix E. GNU Free Documentation License</H1 ><P >Version 1.1, March 2000</P ><A -NAME="AEN2394"><BLOCKQUOTE +NAME="AEN2394" +></A +><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P >Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, @@ -12845,7 +13308,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-0">0. PREAMBLE</H1 +NAME="gfdl-0" +></A +>0. PREAMBLE</H1 ><P >The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the @@ -12873,7 +13338,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H1 +NAME="gfdl-1" +></A +>1. APPLICABILITY AND DEFINITIONS</H1 ><P >This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under @@ -12936,7 +13403,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-2">2. VERBATIM COPYING</H1 +NAME="gfdl-2" +></A +>2. VERBATIM COPYING</H1 ><P >You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the @@ -12956,7 +13425,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-3">3. COPYING IN QUANTITY</H1 +NAME="gfdl-3" +></A +>3. COPYING IN QUANTITY</H1 ><P >If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must @@ -12998,7 +13469,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-4">4. MODIFICATIONS</H1 +NAME="gfdl-4" +></A +>4. MODIFICATIONS</H1 ><P >You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release @@ -13134,7 +13607,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-5">5. COMBINING DOCUMENTS</H1 +NAME="gfdl-5" +></A +>5. COMBINING DOCUMENTS</H1 ><P >You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified @@ -13163,7 +13638,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H1 +NAME="gfdl-6" +></A +>6. COLLECTIONS OF DOCUMENTS</H1 ><P >You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies @@ -13182,7 +13659,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H1 +NAME="gfdl-7" +></A +>7. AGGREGATION WITH INDEPENDENT WORKS</H1 ><P >A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a @@ -13204,7 +13683,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-8">8. TRANSLATION</H1 +NAME="gfdl-8" +></A +>8. TRANSLATION</H1 ><P >Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. @@ -13222,7 +13703,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-9">9. TERMINATION</H1 +NAME="gfdl-9" +></A +>9. TERMINATION</H1 ><P >You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to @@ -13237,7 +13720,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H1 +NAME="gfdl-10" +></A +>10. FUTURE REVISIONS OF THIS LICENSE</H1 ><P >The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions @@ -13263,13 +13748,17 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="gfdl-howto">How to use this License for your documents</H1 +NAME="gfdl-howto" +></A +>How to use this License for your documents</H1 ><P >To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:</P ><A -NAME="AEN2484"><BLOCKQUOTE +NAME="AEN2484" +></A +><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P >Copyright (c) YEAR YOUR NAME. Permission is granted to copy, @@ -13296,13 +13785,17 @@ CLASS="BLOCKQUOTE" CLASS="GLOSSARY" ><H1 ><A -NAME="glossary">Glossary</H1 +NAME="glossary" +></A +>Glossary</H1 ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="AEN2489">0-9, high ascii</H1 +NAME="AEN2489" +></A +>0-9, high ascii</H1 ><DL ><DT ><B @@ -13334,11 +13827,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-a">A</H1 +NAME="gloss-a" +></A +>A</H1 ><DL ><DT ><A -NAME="gloss-apache"><B +NAME="gloss-apache" +></A +><B >Apache</B ></DT ><DD @@ -13477,7 +13974,9 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-b">B</H1 +NAME="gloss-b" +></A +>B</H1 ><DL ><DT ><B @@ -13517,7 +14016,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="gloss-bugzilla"><B +NAME="gloss-bugzilla" +></A +><B >Bugzilla</B ></DT ><DD @@ -13532,11 +14033,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-c">C</H1 +NAME="gloss-c" +></A +>C</H1 ><DL ><DT ><A -NAME="gloss-cgi"><B +NAME="gloss-cgi" +></A +><B >Common Gateway Interface</B ></DT > (CGI)<DD @@ -13554,7 +14059,9 @@ CLASS="acronym" ></DD ><DT ><A -NAME="gloss-component"><B +NAME="gloss-component" +></A +><B >Component</B ></DT ><DD @@ -13566,7 +14073,9 @@ NAME="gloss-component"><B ></DD ><DT ><A -NAME="gloss-cpan"><B +NAME="gloss-cpan" +></A +><B >Comprehensive Perl Archive Network</B ></DT > (CPAN)<DD @@ -13591,7 +14100,9 @@ CLASS="glossterm" ></DD ><DT ><A -NAME="gloss-contrib"><B +NAME="gloss-contrib" +></A +><B ><TT CLASS="filename" >contrib</TT @@ -13650,7 +14161,9 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-d">D</H1 +NAME="gloss-d" +></A +>D</H1 ><DL ><DT ><B @@ -13679,11 +14192,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-g">G</H1 +NAME="gloss-g" +></A +>G</H1 ><DL ><DT ><A -NAME="gloss-groups"><B +NAME="gloss-groups" +></A +><B >Groups</B ></DT ><DD @@ -13715,11 +14232,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-j">J</H1 +NAME="gloss-j" +></A +>J</H1 ><DL ><DT ><A -NAME="gloss-javascript"><B +NAME="gloss-javascript" +></A +><B >JavaScript</B ></DT ><DD @@ -13734,11 +14255,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-m">M</H1 +NAME="gloss-m" +></A +>M</H1 ><DL ><DT ><A -NAME="gloss-mta"><B +NAME="gloss-mta" +></A +><B >Message Transport Agent</B ></DT > (MTA)<DD @@ -13766,7 +14291,9 @@ CLASS="literal" ></DD ><DT ><A -NAME="gloss-mysql"><B +NAME="gloss-mysql" +></A +><B >MySQL</B ></DT ><DD @@ -13843,11 +14370,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-p">P</H1 +NAME="gloss-p" +></A +>P</H1 ><DL ><DT ><A -NAME="gloss-ppm"><B +NAME="gloss-ppm" +></A +><B >Perl Package Manager</B ></DT > (PPM)<DD @@ -13895,7 +14426,9 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-q">Q</H1 +NAME="gloss-q" +></A +>Q</H1 ><DL ><DT ><B @@ -13938,11 +14471,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-r">R</H1 +NAME="gloss-r" +></A +>R</H1 ><DL ><DT ><A -NAME="gloss-rdbms"><B +NAME="gloss-rdbms" +></A +><B >Relational DataBase Managment System</B ></DT > (RDBMS)<DD @@ -13953,7 +14490,9 @@ NAME="gloss-rdbms"><B ></DD ><DT ><A -NAME="gloss-regexp"><B +NAME="gloss-regexp" +></A +><B >Regular Expression</B ></DT > (regexp)<DD @@ -13973,7 +14512,9 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-s">S</H1 +NAME="gloss-s" +></A +>S</H1 ><DL ><DT ><B @@ -14050,11 +14591,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-t">T</H1 +NAME="gloss-t" +></A +>T</H1 ><DL ><DT ><A -NAME="gloss-target-milestone"><B +NAME="gloss-target-milestone" +></A +><B >Target Milestone</B ></DT ><DD @@ -14074,7 +14619,9 @@ CLASS="QUOTE" ></DD ><DT ><A -NAME="gloss-tcl"><B +NAME="gloss-tcl" +></A +><B >Tool Command Language</B ></DT > (TCL)<DD @@ -14092,11 +14639,15 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="gloss-z">Z</H1 +NAME="gloss-z" +></A +>Z</H1 ><DL ><DT ><A -NAME="gloss-zarro"><B +NAME="gloss-zarro" +></A +><B >Zarro Boogs Found</B ></DT ><DD @@ -14106,7 +14657,9 @@ NAME="gloss-zarro"><B Terry had the following to say: </P ><A -NAME="AEN2724"><TABLE +NAME="AEN2724" +></A +><TABLE BORDER="0" WIDTH="100%" CELLSPACING="0" |