From 2b20c4fb3318781ae9cec65da0062d080488d683 Mon Sep 17 00:00:00 2001 From: "jake%acutex.net" Date: Fri, 18 Jan 2002 23:27:01 +0000 Subject: [PATCH] Latest version of compiled docs (picking up recent SGML changes). --- .../bugzilla/docs/html/Bugzilla-Guide.html | 5520 +++++++++-------- webtools/bugzilla/docs/html/about.html | 6 +- .../bugzilla/docs/html/aboutthisguide.html | 20 +- .../bugzilla/docs/html/administration.html | 34 +- webtools/bugzilla/docs/html/bonsai.html | 8 +- webtools/bugzilla/docs/html/bsdinstall.html | 10 +- webtools/bugzilla/docs/html/bzhacking.html | 194 +- webtools/bugzilla/docs/html/cmdline.html | 64 +- webtools/bugzilla/docs/html/contributors.html | 12 +- webtools/bugzilla/docs/html/conventions.html | 110 +- webtools/bugzilla/docs/html/copyright.html | 14 +- webtools/bugzilla/docs/html/credits.html | 20 +- webtools/bugzilla/docs/html/cvs.html | 14 +- webtools/bugzilla/docs/html/database.html | 12 +- webtools/bugzilla/docs/html/dbdoc.html | 75 +- webtools/bugzilla/docs/html/dbschema.html | 14 +- webtools/bugzilla/docs/html/disclaimer.html | 18 +- .../bugzilla/docs/html/downloadlinks.html | 58 +- webtools/bugzilla/docs/html/errata.html | 38 +- webtools/bugzilla/docs/html/faq.html | 1652 ++--- webtools/bugzilla/docs/html/feedback.html | 14 +- webtools/bugzilla/docs/html/future.html | 19 +- webtools/bugzilla/docs/html/geninstall.html | 165 +- webtools/bugzilla/docs/html/gfdl-0.html | 159 + webtools/bugzilla/docs/html/gfdl-1.html | 200 + webtools/bugzilla/docs/html/gfdl-10.html | 156 + webtools/bugzilla/docs/html/gfdl-2.html | 150 + webtools/bugzilla/docs/html/gfdl-3.html | 174 + webtools/bugzilla/docs/html/gfdl-4.html | 280 + webtools/bugzilla/docs/html/gfdl-5.html | 159 + webtools/bugzilla/docs/html/gfdl-6.html | 149 + webtools/bugzilla/docs/html/gfdl-7.html | 153 + webtools/bugzilla/docs/html/gfdl-8.html | 148 + webtools/bugzilla/docs/html/gfdl-9.html | 145 + webtools/bugzilla/docs/html/gfdl-howto.html | 167 + webtools/bugzilla/docs/html/gfdl.html | 38 +- webtools/bugzilla/docs/html/glossary.html | 168 +- webtools/bugzilla/docs/html/granttables.html | 19 +- webtools/bugzilla/docs/html/how.html | 242 +- webtools/bugzilla/docs/html/index.html | 176 +- webtools/bugzilla/docs/html/init4me.html | 88 +- webtools/bugzilla/docs/html/installation.html | 32 +- webtools/bugzilla/docs/html/integration.html | 6 +- webtools/bugzilla/docs/html/newversions.html | 22 +- webtools/bugzilla/docs/html/osx.html | 49 +- webtools/bugzilla/docs/html/patches.html | 14 +- .../bugzilla/docs/html/postinstall-check.html | 66 +- webtools/bugzilla/docs/html/programadmin.html | 353 +- webtools/bugzilla/docs/html/quicksearch.html | 20 +- webtools/bugzilla/docs/html/rewrite.html | 24 +- webtools/bugzilla/docs/html/rhbugzilla.html | 16 +- webtools/bugzilla/docs/html/scm.html | 12 +- webtools/bugzilla/docs/html/security.html | 66 +- webtools/bugzilla/docs/html/setperl.html | 92 +- webtools/bugzilla/docs/html/stepbystep.html | 669 +- webtools/bugzilla/docs/html/tinderbox.html | 8 +- webtools/bugzilla/docs/html/translations.html | 12 +- webtools/bugzilla/docs/html/useradmin.html | 179 +- webtools/bugzilla/docs/html/using.html | 30 +- webtools/bugzilla/docs/html/usingbz-conc.html | 10 +- .../bugzilla/docs/html/variant-fenris.html | 142 + .../docs/html/variant-issuezilla.html | 153 + .../bugzilla/docs/html/variant-perforce.html | 148 + .../bugzilla/docs/html/variant-scarab.html | 148 + .../docs/html/variant-sourceforge.html | 148 + webtools/bugzilla/docs/html/variants.html | 16 +- webtools/bugzilla/docs/html/whatis.html | 36 +- webtools/bugzilla/docs/html/why.html | 20 +- webtools/bugzilla/docs/html/win32.html | 453 +- webtools/bugzilla/docs/txt/Bugzilla-Guide.txt | 98 +- 70 files changed, 8661 insertions(+), 5243 deletions(-) create mode 100644 webtools/bugzilla/docs/html/gfdl-0.html create mode 100644 webtools/bugzilla/docs/html/gfdl-1.html create mode 100644 webtools/bugzilla/docs/html/gfdl-10.html create mode 100644 webtools/bugzilla/docs/html/gfdl-2.html create mode 100644 webtools/bugzilla/docs/html/gfdl-3.html create mode 100644 webtools/bugzilla/docs/html/gfdl-4.html create mode 100644 webtools/bugzilla/docs/html/gfdl-5.html create mode 100644 webtools/bugzilla/docs/html/gfdl-6.html create mode 100644 webtools/bugzilla/docs/html/gfdl-7.html create mode 100644 webtools/bugzilla/docs/html/gfdl-8.html create mode 100644 webtools/bugzilla/docs/html/gfdl-9.html create mode 100644 webtools/bugzilla/docs/html/gfdl-howto.html create mode 100644 webtools/bugzilla/docs/html/variant-fenris.html create mode 100644 webtools/bugzilla/docs/html/variant-issuezilla.html create mode 100644 webtools/bugzilla/docs/html/variant-perforce.html create mode 100644 webtools/bugzilla/docs/html/variant-scarab.html create mode 100644 webtools/bugzilla/docs/html/variant-sourceforge.html diff --git a/webtools/bugzilla/docs/html/Bugzilla-Guide.html b/webtools/bugzilla/docs/html/Bugzilla-Guide.html index 43f1d3cf10e..60045e438cd 100644 --- a/webtools/bugzilla/docs/html/Bugzilla-Guide.html +++ b/webtools/bugzilla/docs/html/Bugzilla-Guide.html @@ -25,7 +25,7 @@ CONTENT="Mozilla">

The Bugzilla Guide

Matthew P. Barnson

barnboy@trilobyte.net

Zach Lipton

zach AT zachlipton DOT com


This is the documentation for Bugzilla, the Mozilla +> This is the documentation for Bugzilla, the Mozilla bug-tracking system.

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.

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! @@ -223,107 +223,107 @@ CLASS="TOC" >

1. About This Guide
1.1. Purpose and Scope of this Guide
1.2. Copyright Information
1.3. Disclaimer
1.4. New Versions
1.5. Credits
1.6. Contributors
1.7. Feedback
1.8. Translations
1.9. Document Conventions
2. Using Bugzilla
2.1. What is Bugzilla?
2.2. Why Should We Use Bugzilla?
2.3. How do I use Bugzilla?
2.3.1. Create a Bugzilla Account
2.3.2. The Bugzilla Query Page
2.3.3. Creating and Managing Bug Reports
2.3.3.1. Writing a Great Bug Report
2.3.3.2. Managing your Bug Reports
2.4. Where can I find my user preferences?
2.4.1. Account Settings
2.4.2. Email Settings
2.4.2.1. Email Notification
2.4.2.2. New Email Technology
2.4.2.3. "Watching" Users
2.4.3. Page Footer
2.4.4. Permissions
2.5. Using Bugzilla-Conclusion
3. Installation
3.1. ERRATA
3.2. Step-by-step Install
3.2.3. Installing MySQL Database
3.2.4. Perl (5.004 or greater)
3.2.15. Tweaking localconfig
3.3. Mac OS X Installation Notes
3.4. BSD Installation Notes
3.5. Installation General Notes
3.5.3. .htaccess files and security
3.5.4. mod_throttle and Security
3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code
3.5.6. UNIX Installation Instructions History
3.6. Win32 Installation Notes
3.6.1. Win32 Installation: Step-by-step
3.6.2. Additional Windows Tips
3.6.3. Bugzilla LDAP Integration
4. Administering Bugzilla
4.1. Post-Installation Checklist
4.2. User Administration
4.2.1. Creating the Default User
4.2.2. Managing Other Users
4.2.2.1. Logging In
4.2.2.2. Creating new users
4.2.2.3. Disabling Users
4.2.2.4. Modifying Users
4.3. Product, Component, Milestone, and Version Administration
4.3.1. Products
4.3.2. Components
4.3.3. Versions
4.3.4. Milestones
4.3.5. Voting
4.3.6. Groups and Group Security
4.4. Bugzilla Security
5. Integrating Bugzilla with Third-Party Tools
5.1. Bonsai
5.2. CVS
5.3. Perforce SCM
5.4. Tinderbox/Tinderbox2
6. The Future of Bugzilla
7. Bugzilla Variants and Competitors
7.1. Red Hat Bugzilla
7.2. Loki Bugzilla (Fenris)
7.3. Issuezilla
7.4. Scarab
7.5. Perforce SCM
7.6. SourceForge
A. The Bugzilla FAQ
B. Software Download Links
C. The Bugzilla Database
C.1. Database Schema Chart
C.2. MySQL Bugzilla Database Introduction
C.2.1. Bugzilla Database Basics
C.2.1.1. Bugzilla Database Tables
C.3. MySQL Permissions & Grant Tables
D. Useful Patches and Utilities for Bugzilla
D.1. Apache mod_rewrite magic
D.2. The setperl.csh Utility
D.3. Command-line Bugzilla Queries
D.4. The Quicksearch Utility
D.5. Hacking Bugzilla
D.5.1. Things that have caused problems and should be avoided
D.5.2. Coding Style for Bugzilla
E. GNU Free Documentation License
0. PREAMBLE
1. APPLICABILITY AND DEFINITIONS
2. VERBATIM COPYING
3. COPYING IN QUANTITY
4. MODIFICATIONS
5. COMBINING DOCUMENTS
6. COLLECTIONS OF DOCUMENTS
7. AGGREGATION WITH INDEPENDENT WORKS
8. TRANSLATION
9. TERMINATION
10. FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
Glossary
3-3. Installing ActivePerl ppd Modules on Microsoft Windows
3-4. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier
4-1. Creating some Components
4-2. Common Use of Versions
4-3. A Different Use of Versions
4-4. Using SortKey with Target Milestone
4-5. When to Use Group Security
4-6. Creating a New Group
4-7. Bugzilla Groups
D-1. Using Setperl to set your perl path
1. A Sample Product

Chapter 1. About This Guide

1.1. Purpose and Scope of this Guide

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.

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.

This release of the Bugzilla Guide is the +> This release of the Bugzilla Guide is the 2.14 release. It is so named that it @@ -1075,7 +1075,7 @@ NAME="ABOUTTHISGUIDE" developers, and those who enjoy a lot of pain.

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

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 <barnboy@trilobyte.net

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.

1.3. Disclaimer

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 @@ -1183,13 +1183,13 @@ NAME="DISCLAIMER" war. Proceed with caution.

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.

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, @@ -1197,13 +1197,13 @@ NAME="DISCLAIMER" environment for Bugzilla.

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!

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 @@ -1217,29 +1217,29 @@ NAME="DISCLAIMER"

1.4. New Versions

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.

This document can be found in the following places: +> This document can be found in the following places:

1.5. Credits

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:

Terry Weissman

Tara @@ -1310,7 +1310,7 @@ TARGET="_top" strong after Terry left Mozilla.org

Dave Lawrence

Dawn Endico

Last but not least, all the members of the Last but not least, all the members of the netscape.public.mozilla.webtools

1.6. Contributors

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):

Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron +> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron Teitelbaum, Jacob Steenhagen, Joe Robins

1.7. Feedback

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 <barnboy@trilobyte.net>. Please send flames to <devnull@localhost

1.8. Translations

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 <mozilla-webtools@mozilla.org

1.9. Document Conventions

This document uses the following conventions +> This document uses the following conventions

DescriptionsAppearanceWarnings

Hint

Notes

Information requiring special attention

File Namesfile.extension
Directory Namesdirectory
Commands to be typedcommand
Applications Namesapplication
Prompt of users command under bash shellbash$
Prompt of root users command under bash shellbash#
Prompt of user command under tcsh shelltcsh$
Environment VariablesVARIABLE
Emphasized wordword
Code Example
<para>Beginning and end of paragraph</para>

2.1. What is Bugzilla?

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 @@ -1790,48 +1790,48 @@ project, Mozilla). It is now the de-facto standard defect-tracking system against which all others are measured.

Bugzilla has matured immensely, and now boasts many advanced features. These include: +> Bugzilla has matured immensely, and now boasts many advanced features. These include:

  • integrated, product-based granular security schema +> integrated, product-based granular security schema

  • inter-bug dependencies and dependency graphing +> inter-bug dependencies and dependency graphing

  • advanced reporting capabilities +> advanced reporting capabilities

  • a robust, stable RDBMS back-end +> a robust, stable RDBMS back-end

  • extensive configurability +> extensive configurability

  • a very well-understood and well-thought-out natural bug resolution protocol +> a very well-understood and well-thought-out natural bug resolution protocol

  • email, XML, console, and HTTP APIs +> email, XML, console, and HTTP APIs

  • 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) @@ -1839,14 +1839,14 @@ system against which all others are measured. >

  • too many more features to list +> too many more features to list

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 @@ -1857,7 +1857,7 @@ system against which all others are measured. some nonstandard libraries.

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

Despite these small problems, Bugzilla is very hard to beat. It +> Despite these small problems, Bugzilla is very hard to beat. It is under very active development to address @@ -1876,11 +1876,11 @@ CLASS="QUOTE"

2.2. Why Should We Use Bugzilla?

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 @@ -1916,7 +1916,7 @@ VALIGN="TOP" dropped or ignored.

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 @@ -1928,12 +1928,12 @@ VALIGN="TOP" system for accounting for unusual system or software issues.

But why should But why should you use Bugzilla?

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 @@ -1944,7 +1944,7 @@ VALIGN="TOP" replication problems

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 @@ -1958,18 +1958,18 @@ VALIGN="TOP" led to critical decisions.

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.

2.3. How do I use Bugzilla?

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. @@ -2006,19 +2006,19 @@ VALIGN="TOP" software.

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, landfill.tequilarista.org landfill.tequilarista.org.

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

2.3.1. Create a Bugzilla Account

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 @@ -2083,19 +2083,19 @@ TARGET="_top" TYPE="1" >

  • Click the "Open a new Bugzilla account" link. +> Click the "Open a new Bugzilla account" link.

  • 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.

  • 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 @@ -2105,7 +2105,7 @@ TYPE="1" >

  • Click the Click the "Log In" link in the yellow area at @@ -2123,12 +2123,12 @@ CLASS="QUOTE" >"Login".

    • 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 "E-mail address"

    Many modern browsers include an +> Many modern browsers include an "Auto-Complete"

    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 @@ -2218,46 +2218,46 @@ CLASS="QUOTE"

    2.3.2. The Bugzilla Query Page

    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.

    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 quicksearch.html available to use and simplify your searches. There is also a helper for the query interface, called queryhelp.cgi. Landfill 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, +> At this point, let's visit the query page. bugzilla.mozilla.org, to see a more fleshed-out query page. +> landfill.tequilarista.org/bugzilla-tip/query.cgi

    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 @@ -2267,7 +2267,7 @@ CLASS="QUOTE" > underlined. Select it.

    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 @@ -2278,7 +2278,7 @@ CLASS="QUOTE" button in your browser.

    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 @@ -2290,7 +2290,7 @@ CLASS="QUOTE" TYPE="1" >

  • Ensure you are back on the Ensure you are back on the "Bugzilla Query Page"

    Basically, selecting Basically, selecting anything on the query page narrows your search down. Leaving stuff @@ -2315,7 +2315,7 @@ CLASS="QUOTE" >

  • 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 @@ -2323,12 +2323,12 @@ CLASS="QUOTE" put my email address in there, and see what happens.

    Type "barnboy@trilobyte.net" in the top Email text box. +> Type "barnboy@trilobyte.net" in the top Email text box.

  • 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 @@ -2342,13 +2342,13 @@ CLASS="QUOTE" >

  • 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.

    Example 2-1. Some Famous Software Versions

    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. @@ -2374,7 +2374,7 @@ NAME="AEN309" ME(Millenium Edition)(r).

    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, @@ -2391,7 +2391,7 @@ NAME="AEN309" version than 1.1.1.

    In general, a "Version" in Bugzilla should refer to +> In general, a "Version" in Bugzilla should refer to released products, not products @@ -2406,13 +2406,13 @@ NAME="AEN309" >

    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.

    Example 2-2. Mozilla's Bugzilla Components

    Mozilla's "Bugzilla" Product is composed of several pieces (Components): +> Mozilla's "Bugzilla" Product is composed of several pieces (Components):

    • , Administration of a bugzilla installation, including editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi, editproducts.cgi, editusers.cgi, editversions.cgi, and sanitycheck.cgi. , Creating, changing, and viewing bugs. enter_bug.cgi, post_bug.cgi, show_bug.cgi and process_bug.cgi. , The bugzilla documentation, including anything in the docs/ directory and The Bugzilla Guide (This document :) @@ -2527,7 +2527,7 @@ CLASS="FILENAME" >, Anything to do with email sent by Bugzilla. processmail , The installation process of Bugzilla. This includes checksetup.pl and whatever else it evolves into. , Anything to do with searching for bugs and viewing the buglists. query.cgi and buglist.cgi , Getting reports from Bugzilla. reports.cgi and duplicates.cgi , Anything about managing a user account from the user's perspective. userprefs.cgi, saved queries, creating accounts, changing passwords, logging in, etc. @@ -2611,7 +2611,7 @@ CLASS="FILENAME" >

    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 @@ -2626,7 +2626,7 @@ CLASS="FILENAME" of reach by the time the important day arrives.

    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". @@ -2634,19 +2634,19 @@ CLASS="FILENAME" >

  • OK, now let's select the "Bugzilla" component from its scrollbox. +> OK, now let's select the "Bugzilla" component from its scrollbox.

  • 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!

  • 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 @@ -2658,7 +2658,7 @@ CLASS="FILENAME" >

    • 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 @@ -2667,7 +2667,7 @@ CLASS="FILENAME" this is a tremendous timesaver.

    A couple more interesting things about the Bug List page: +> A couple more interesting things about the Bug List page:

    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

    2.3.3.1. Writing a Great Bug Report

    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 @@ -2807,7 +2807,7 @@ TARGET="_top" >. 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.

    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 .

    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!

  • Go back to Go back to http://landfill.tequilarista.org/bugzilla-tip/

  • Select the Select the Enter a new bug report

  • Select a product. +> Select a product.

  • 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, @@ -2858,12 +2858,12 @@ TARGET="_top" >

  • Select a Component in the scrollbox. +> Select a Component in the scrollbox.

  • 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! @@ -2871,7 +2871,7 @@ TARGET="_top" >

  • 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. @@ -2879,33 +2879,33 @@ TARGET="_top" >

  • 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".

  • 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.

    • 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.

    2.3.3.2. Managing your Bug Reports

    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. @@ -2916,7 +2916,7 @@ NAME="BUG_MANAGE" TYPE="1" >

  • 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, @@ -2928,7 +2928,7 @@ TYPE="1" >

  • 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 @@ -2937,40 +2937,40 @@ TYPE="1" >

    • 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.

    But I'll give a few last hints! +> But I'll give a few last hints!

    There is a There is a CLUE on the Query page that will teach you more how to use the form.

    If you click the hyperlink on the If you click the hyperlink on the Component box of the Query page, you will be presented a form that will describe what all the components are.

    Possibly the most powerful feature of the Query page is the +> Possibly the most powerful feature of the Query page is the Boolean Chart 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.

    Finally, you can build some nifty Finally, you can build some nifty Reports 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. @@ -2979,11 +2979,11 @@ TARGET="_top" >

    2.4. Where can I find my user preferences?

    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 .

    2.4.1. Account Settings

    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

    2.4.2. Email Settings

    2.4.2.1. Email Notification

    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 Bonsai, the Mozilla automated CVS management system or Tinderbox, the Mozilla automated build management system, and restrict which types of Bugzilla information are fed to @@ -3101,19 +3101,19 @@ HREF="#TINDERBOX"

    2.4.2.2. New Email Technology

    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, @@ -3142,13 +3142,13 @@ VALIGN="TOP" >

    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.

    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 @@ -3156,19 +3156,19 @@ VALIGN="TOP"

    2.4.2.3. "Watching" Users

    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, @@ -3195,7 +3195,7 @@ VALIGN="TOP" >

    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 @@ -3207,19 +3207,19 @@ VALIGN="TOP" >

    2.4.3. Page Footer

    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 @@ -3247,7 +3247,7 @@ VALIGN="TOP" >

    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 @@ -3255,11 +3255,11 @@ VALIGN="TOP" is an excellent way to impress your boss...

    2.4.4. Permissions

    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. @@ -3311,15 +3311,15 @@ NAME="PERMISSIONSETTINGS" >

    2.5. Using Bugzilla-Conclusion

    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

    Chapter 3. Installation

    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.

    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 "paranoid" security options, it is possible that the checksetup.pl script may fail with the error: cannot chdir(/var/spool/mqueue): Permission denied This is because your /var/spool/mqueue directory has a mode of "drwx------". Type chmod 755 /var/spool/mqueue as root to @@ -3395,7 +3395,7 @@ CLASS="FILENAME" >
    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 @@ -3405,9 +3405,9 @@ CLASS="FILENAME" >
    Release Notes for Bugzilla 2.14 are available at +> Release Notes for Bugzilla 2.14 are available at docs/rel_notes.txt in your Bugzilla source distribution. @@ -3415,7 +3415,7 @@ CLASS="FILENAME" >
    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. @@ -3426,11 +3426,11 @@ CLASS="FILENAME" >

    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 @@ -3460,11 +3460,11 @@ VALIGN="TOP" >

    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. @@ -3491,58 +3491,58 @@ VALIGN="TOP" >

    3.2. Step-by-step Install

    3.2.1. Introduction

    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.

    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 Win32 Installation Notes for further advice on getting Bugzilla to work on Microsoft Windows.

    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).

    Using Bundle::Bugzilla instead of manually installing Perl modules

    The software packages necessary for the proper running of bugzilla are: +> The software packages necessary for the proper running of bugzilla are:

    1. MySQL database server and the mysql client (3.22.5 or greater) +> MySQL database server and the mysql client (3.22.5 or greater)

    2. 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)

    3. DBI Perl module +> DBI Perl module

    4. Data::Dumper Perl module +> Data::Dumper Perl module

    5. Bundle::Mysql Perl module collection +> Bundle::Mysql Perl module collection

    6. TimeDate Perl module collection +> TimeDate Perl module collection

    7. GD perl module (1.8.3) (optional, for bug charting) +> GD perl module (1.8.3) (optional, for bug charting)

    8. Chart::Base Perl module (0.99c) (optional, for bug charting) +> Chart::Base Perl module (0.99c) (optional, for bug charting)

    9. DB_File Perl module (optional, for bug charting) +> DB_File Perl module (optional, for bug charting)

    10. The web server of your choice. Apache is recommended. +> The web server of your choice. Apache is recommended.

    11. MIME::Parser Perl module (optional, for contrib/bug_email.pl interface) +> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)

    It is a good idea, while installing Bugzilla, to ensure it +> It is a good idea, while installing Bugzilla, to ensure it is not accessible by other machines @@ -3674,11 +3674,11 @@ VALIGN="TOP" >

    urpmi utility. If you follow these commands, you should have everything you need for Bugzilla, and checksetup.pl should not complain about any missing libraries. You may already @@ -3716,10 +3716,10 @@ BORDER="0" >

    3.2.3. Installing MySQL Database

    Visit MySQL homepage at Visit MySQL homepage at www.mysql.com and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in /var 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 configure.

    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 mysqld to your init scripts so the server daemon will come back up whenever your machine reboots. Further discussion of UNIX init sequences are beyond the scope of this guide.

    bash# urpmi perl-mysql
    bash# urpmi perl-chart
    bash# urpmi perl-gd
    bash# urpmi perl-MailTools (for Bugzilla email @@ -3761,10 +3761,10 @@ CLASS="COMMAND" >
    bash# urpmi apache-modules

    You should have your init script start mysqld with the ability to accept large packets. By default, mysqld only accepts packets up to 64K long. This limits the size of attachments you may put on bugs. If you add -O max_allowed_packet=1M to the command that starts mysqld (or safe_mysqld), then you will be able to have attachments up to about 1 megabyte.

    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 --skip-networking option in the init script. This enhances security by @@ -3899,15 +3899,15 @@ CLASS="OPTION" >

    3.2.4. Perl (5.004 or greater)

    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 @@ -3915,7 +3915,7 @@ NAME="INSTALL-PERL" this writing, that is perl version 5.6.1.

    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 @@ -3926,11 +3926,11 @@ NAME="INSTALL-PERL" isn't up to snuff.

    You can skip the following Perl module installation steps by +> You can skip the following Perl module installation steps by installing Bundle::Bugzilla from CPAN, which @@ -4009,13 +4009,13 @@ CLASS="GLOSSTERM" version of Perl (at this writing, version 5.6.1)

    bash# perl -MCPAN -e 'install "Bundle::Bugzilla"' @@ -4023,7 +4023,7 @@ CLASS="COMMAND" >

    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. @@ -4034,62 +4034,62 @@ CLASS="COMMAND" >

    3.2.5. DBI Perl Module

    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.

    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 Appendix B.

    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.

    To use the CPAN shell to install DBI: +> To use the CPAN shell to install DBI:

    bash# perl -MCPAN -e 'install "DBI"'

    To do it the hard way:

    Untar the module tarball -- it should create its own directory +> Untar the module tarball -- it should create its own directory

    CD to the directory just created, and enter the following commands: +> CD to the directory just created, and enter the following commands:

    1. bash# perl Makefile.PL

    2. bash# make

    3. bash# make test

    4. bash# make install

    3.2.6. Data::Dumper Perl Module

    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.

    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 Appendix B) and can be @@ -4235,45 +4235,45 @@ HREF="#DOWNLOADLINKS"

    3.2.7. MySQL related Perl Module Collection

    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.

    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: bash# perl Makefile.pl

    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.

    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.

    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 @@ -4281,19 +4281,19 @@ CLASS="COMMAND"

    3.2.8. TimeDate Perl Module Collection

    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: Appendix B). The component module we're most interested in is the Date::Format @@ -4303,15 +4303,15 @@ HREF="#DOWNLOADLINKS"

    3.2.9. GD Perl Module (1.8.3)

    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 @@ -4320,20 +4320,20 @@ NAME="AEN658" install it if you want any of the graphing to work.

    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 Appendix B.

    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 libpng and libgd. The full requirements are listed in the Perl GD library README. Just realize that if @@ -4369,19 +4369,19 @@ CLASS="CLASSNAME" >

    3.2.10. Chart::Base Perl Module (0.99c)

    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 Appendix B. Note that as with the GD perl module, only the version listed above, or @@ -4390,15 +4390,15 @@ HREF="#DOWNLOADLINKS"

    3.2.11. DB_File Perl Module

    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 @@ -4406,15 +4406,15 @@ NAME="AEN671"

    3.2.12. HTTP Server

    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 "bugs" user permissions accordingly.

    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: @@ -4468,8 +4468,8 @@ WIDTH="100%" >

    AddHandler cgi-script .cgi
+CLASS="programlisting"
+>
AddHandler cgi-script .cgi

    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: 

    Options ExecCGI
    Options ExecCGI +

    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.

    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 .htaccess files and security for details on how to do this for Apache. I appreciate notes on how to @@ -4577,15 +4578,15 @@ HREF="#HTACCESS" >

    3.2.13. Installing the Bugzilla Files

    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 ). You may decide to put the files off of the main web space for your web server or perhaps off of /usr/local with a symbolic link in the web space that points to the Bugzilla directory. At any @@ -4602,11 +4603,11 @@ CLASS="FILENAME" server.

    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 Forbidden errors unless you add the

    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 checksetup.pl script, which locks down your installation.

    Lastly, you'll need to set up a symbolic link to +> Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl for the correct location of your perl executable (probably /usr/bin/perl). Otherwise you must hack all the .cgi files to change where they look for perl, or use The setperl.csh Utility, found in Useful Patches and Utilities for Bugzilla. I suggest using the symlink approach for future release compatability.

    Example 3-1. Setting up bonsaitools symlink

    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 

    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

    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: 
    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

    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 The setperl.csh Utility, listed in Useful Patches and Utilities for Bugzilla. It will change the path to perl in all your Bugzilla files for you.

    3.2.14. Setting Up the MySQL Database

    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.

    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

    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 DROP DATABASE mysql. @@ -4838,7 +4839,7 @@ CLASS="COMMAND" >

    Give the MySQL root user a password. MySQL passwords are +> Give the MySQL root user a password. MySQL passwords are limited to 16 characters.

    bash# mysql -u root mysql
    mysql> UPDATE user SET Password=PASSWORD ('new_password') +CLASS="command" +> UPDATE user SET Password=PASSWORD ('new_password') WHERE user='root'; @@ -4877,13 +4878,13 @@ CLASS="COMMAND" >
    mysql> FLUSH PRIVILEGES; From this point on, if you need to access MySQL as the MySQL root user, you will need to use mysql -u root -p and enter your new_password. Remember that MySQL user names have nothing to do with Unix user names (login names).

    Next, we create the Next, we create the "bugs" user, and grant @@ -4926,7 +4927,7 @@ CLASS="QUOTE" as a different user.

    Remember to set bugs_password to some unique password. +> Remember to set bugs_password to some unique password.

    mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost @@ -4953,16 +4954,16 @@ CLASS="COMMAND" >
    mysql> +> mysql> FLUSH PRIVILEGES; +CLASS="command" +> FLUSH PRIVILEGES;

    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 data directory, and create all the MySQL tables. @@ -4992,14 +4993,14 @@ BORDER="0" >

    bash# ./checksetup.pl @@ -5011,35 +5012,35 @@ CLASS="COMMAND" >

    The first time you run it, it will create a file called localconfig.

    3.2.15. Tweaking localconfig

    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.

    The connection settings include: +> The connection settings include:

    1. server's host: just use server's host: just use "localhost" if the @@ -5048,7 +5049,7 @@ CLASS="QUOTE" >

    2. database name: database name: "bugs" if you're following @@ -5057,7 +5058,7 @@ CLASS="QUOTE" >

    3. MySQL username: MySQL username: "bugs" if you're following @@ -5066,7 +5067,7 @@ CLASS="QUOTE" >

    4. Password for the Password for the "bugs" MySQL account above @@ -5076,24 +5077,24 @@ CLASS="QUOTE" >

      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 .htaccess files and security.

      Once you are happy with the settings, re-run +> Once you are happy with the settings, re-run checksetup.pl. On this second run, it will create the database and an administrator account for which you will be prompted to provide information.

      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

      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 localconfig file in your Bugzilla root directory.

      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 parameter in localconfig as well.

      Example 3-2. Running checksetup.pl as the web user

      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 

       
 bash# chown -R apache:apache /usr/local/bugzilla 
 bash# su - apache 
@@ -5193,11 +5194,11 @@ bash# ./checksetup.pl
 >

      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.

      3.2.16. Setting Up Maintainers Manually (Optional)

      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 mysql -u root -p bugs You may need different parameters, depending on your security @@ -5246,13 +5247,13 @@ BORDER="0" >

      mysql> update profiles set groupset=0x7fffffffffffffff where login_name = 'XXX';

      3.2.17. The Whining Cron (Optional)

      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 @@ -5294,10 +5295,10 @@ BORDER="0" >

      cd <your-bugzilla-directory> ; ./whineatnews.pl

      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: 

       man 5 crontab
+CLASS="programlisting"
+>
 man 5 crontab

      3.2.18. Bug Graphs (Optional)

      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.

      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:

      bash# crontab -e
      5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl

      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.

      3.2.19. Securing MySQL

      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.

      Most MySQL installs have "interesting" default security parameters: +> Most MySQL installs have "interesting" default security parameters:

      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.

      To see your permissions do: +> To see your permissions do:

      bash# mysql -u root -p
      mysql> use mysql;
      mysql> show tables;
      mysql> select * from user;
      mysql> select * from db;

      To fix the gaping holes: +> To fix the gaping holes:

      If you're not running "mit-pthreads" you can use: +> If you're not running "mit-pthreads" you can use:

      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:

      Use .htaccess files with the Apache webserver to secure your +> Use .htaccess files with the Apache webserver to secure your bugzilla install. See .htaccess files and security

      Consider also: +> Consider also:

      1. 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.

      2. 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.

      3. starting MySQL in a chroot jail +> starting MySQL in a chroot jail

      4. running the httpd in a "chrooted" jail +> running the httpd in a "chrooted" jail

      5. 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").

      6. running MySQL on a separate untrusted machine +> running MySQL on a separate untrusted machine

      7. making backups ;-) +> making backups ;-)

      3.3. Mac OS X Installation Notes

      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.

      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/>.

      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: fink install gd

      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.

      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 @@ -5748,15 +5749,15 @@ CLASS="COMMAND" :-)

      Instead of typing Instead of typing "install GD" at the cpan> prompt, type look GD. This should go through the motions of @@ -5764,13 +5765,13 @@ CLASS="COMMAND" 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 patch < patchfile: 

      	
+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 @@
@@ -5813,7 +5815,7 @@ CLASS="PROGRAMLISTING"
 >
     
            Then, run these commands to finish the installation of the perl module:
+>
      Then, run these commands to finish the installation of the perl module:

      Happy Hacking! +> Happy Hacking!

      3.4. BSD Installation Notes

      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 Section 3.3.

      3.5. Installation General Notes

      3.5.1. Modifying Your Running System

      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.

      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

      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.

      3.5.2. Upgrading From Previous Versions

      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.

      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.

      3.5.3. .htaccess files and security

      To enhance the security of your Bugzilla installation, +> To enhance the security of your Bugzilla installation, Bugzilla will generate .htaccess files which the Apache webserver can use to restrict access to the bugzilla data files. The checksetup script will generate the .htaccess files.

      perl Makefile.PL
      make
      make test
      make install
      And don't forget to run exit to get back to cpan.

      If you are using an alternate provider of +> If you are using an alternate provider of webdot services for graphing (as described when viewing editparams.cgi in your web browser), you will need to change the ip address in data/webdot/.htaccess to the ip address of the webdot server that you are using. @@ -6016,22 +6018,81 @@ CLASS="FILENAME"

      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 .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

      3.5.4. mod_throttle and Security

      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 mod_throttle which can limit connections by ip-address. You may download this module at @@ -6066,7 +6127,7 @@ TARGET="_top" >. Follow the instructions to install into your Apache install. This module only functions with the Apache web server!. You may use the ThrottleClientIP command provided by this module to accomplish this goal. See the for more information.

      3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code

      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

      All this one-liner command does is search for all instances of +> All this one-liner command does is search for all instances of "Content-type: text/html"

      3.5.6. UNIX Installation Instructions History

      This document was originally adapted from the Bonsai +> This document was originally adapted from the Bonsai installation instructions by Terry Weissman <terry@mozilla.org>.

      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 ).

      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.

      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.

      Comments from people using this Guide for the first time are +> Comments from people using this Guide for the first time are particularly welcome.

      3.6. Win32 Installation Notes

      3.6.1. Win32 Installation: Step-by-step

      You should be familiar with, and cross-reference, the rest +> You should be familiar with, and cross-reference, the rest of the Bugzilla Installation section while performing your Win32 installation. @@ -6252,7 +6313,7 @@ HREF="#INSTALLATION" utilities. What follows is the recommended installation procedure for Win32; additional suggestions are provided in Appendix A.

      1. Install Install Apache Web @@ -6274,7 +6335,7 @@ TARGET="_top" > for Windows, and copy the Bugzilla files somewhere Apache can serve them. Please follow all the instructions referenced in Bugzilla Installation regarding your Apache configuration, particularly @@ -6288,11 +6349,11 @@ CLASS="QUOTE" >.

        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 Appendix A.

        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.

      2. Install Install ActivePerl for a current compiled binary.

        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: Perl Porting Perl Porting, and Perl on Win32 FAQ Perl on Win32 FAQ

      3. 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.

        4. You can find a list of modules at +> You can find a list of modules at http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ http://www.activestate.com/PPMPackages/zips/5xx-builds-only/

        The syntax for ppm is: +> The syntax for ppm is: C:> ppm <modulename>

        C:>ppm DBD-Mysql

        Watch your capitalization!

        You can find ActiveState ppm modules at +> You can find ActiveState ppm modules at http://www.activestate.com/PPMPackages/5.6plus http://www.activestate.com/PPMPackages/5.6plus

      4. Install MySQL for NT. +> Install MySQL for NT.

        You can download MySQL for Windows NT from You can download MySQL for Windows NT from MySQL.com

      5. Setup MySQL +> Setup MySQL

        1. C:> C:\mysql\bin\mysql -u root mysql

        2. mysql> DELETE FROM user WHERE Host='localhost' AND User='';

        3. mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE user='root'; @@ -6545,17 +6606,17 @@ CLASS="QUOTE" >

        4. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost @@ -6577,14 +6638,14 @@ CLASS="QUOTE" >

        5. mysql> FLUSH PRIVILEGES;

        6. mysql> create database bugs;

        7. mysql> exit;

        8. C:> C:\mysql\bin\mysqladmin -u root -p reload

        9. Edit Edit checksetup.pl in your Bugzilla directory. Change this line: 

        6. my $webservergid = getgrnam($my_webservergroup);
+CLASS="programlisting"
+>
my $webservergid = getgrnam($my_webservergroup);

        to +> to 

        my $webservergid = $my_webservergroup;
+CLASS="programlisting"
+>
my $webservergid = $my_webservergroup;
 	    
        my $webservergid = 'Administrators'
+CLASS="programlisting"
+>
my $webservergid = 'Administrators'

      6. Run Run checksetup.pl from the Bugzilla directory.

      7. Edit localconfig to suit your requirements. Set $db_pass to your "bugs_password" from step 5.d, and $webservergroup to "8".

        8. "8" for $webservergroup above. If it's wrong, please send corrections.

      8. Edit Edit defparams.pl to suit your requirements. Particularly, set DefParam("maintainer") and DefParam("urlbase") to match your install.

        10. 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 suggestion, not @@ -6873,12 +6934,12 @@ TARGET="_top" >

        1. Download NTsendmail, available from Download NTsendmail, available from www.ntsendmail.com

          # 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;
@@ -6913,11 +6974,11 @@ $ENV{"NTsendmail_max_tries"}=5;
 >

      Some mention to also edit +> Some mention to also edit $db_pass in globals.pl to be your .htaccess, your database password is exposed to whoever uses your @@ -6962,11 +7023,11 @@ CLASS="FILENAME" >

    5. Find and comment out all occurences of +> Find and comment out all occurences of "open(SENDMAIL" in @@ -6980,8 +7041,8 @@ WIDTH="100%" >

      # new sendmail functionality
+CLASS="programlisting"
+>
# new sendmail functionality
 my $mail=new NTsendmail;
 my $from="bugzilla\@your.machine.name.tld";
 my $to=$login;
@@ -6995,11 +7056,11 @@ $mail->send($from,$to,$subject,$msg);
 >

      6. Some have found success using the commercial product, +> Some have found success using the commercial product, Windmail. You could try replacing your sendmail calls with: @@ -7030,8 +7091,8 @@ WIDTH="100%" >

      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";

    6. Change all references in all files from +> Change all references in all files from processmail to processmail.pl, and rename processmail to processmail.pl.

      7. 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.

      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. 

      
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
@@ -7137,7 +7200,10 @@ $smtp->datasend($msg);
 $smtp->dataend();   # Finish sending the mail
 $smtp->quit;    # Close the SMTP connection
 $logstr = "$logstr; mail sent to $tolist $cclist";
-}
      
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;
@@ -7166,7 +7234,10 @@ recipient's address
                 $smtp->datasend('test');
                 $smtp->dataend();   # Finish sending the mail
                 $smtp->quit;    # Close the SMTP connection
-exit;

      8. 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

      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 utility to speed part of this procedure, available in the Useful Patches and Utilities for Bugzilla section of The Bugzilla Guide. However, it requires the Cygwin GNU-compatible environment @@ -7239,8 +7310,9 @@ TARGET="_top" >

    8. 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: 
       
-system ("./processmail.pl",@ARGLIST); 
-
      to -

    9. Add Add binmode() calls so attachments will work ().

      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 createattachment.cgi and showattachment.cgi before the require 'CGI.pl'; line.

      line. +

      10.  
-system ("perl processmail.pl",@ARGLIST);
+system ("./processmail",@ARGLIST); 
+	    </programlisting> to
+	    <programlisting> 
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
 	    
      binmode(STDIN);
-binmode(STDOUT);
      +binmode(STDIN); +binmode(STDOUT); + +

      According to According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not.

      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: 

       
 .cgi to: <perl install directory>\perl.exe %s %s
 .pl to: <perl install directory>\perl.exe %s %s
@@ -7426,19 +7487,19 @@ GET,HEAD,POST
 >

      From Andrew Pearson: +> From Andrew Pearson:

      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

      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: 

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+CLASS="programlisting"
+>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap

      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: c:/perl/bin/perl.exe "%s" "%s"

      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.

      10. 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 not necessary

      Replace this: +> Replace this: 

        
 SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
 my $enteredcryptpwd = FetchOneColumn();
@@ -7580,7 +7641,7 @@ WIDTH="100%"
 >
        
 my $enteredcryptpwd = $enteredpwd   
 	      
      3.6.3. Bugzilla LDAP Integration
      	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.
       
      Mozilla::LDAP module
      
+CLASS="literallayout"
+>
      
+Mozilla::LDAP module
      
 
      
 The Mozilla::LDAP module allows you to use LDAP for authentication to
      
 the Bugzilla system.  This module is not required if you are not using
      
@@ -7683,22 +7745,22 @@ address, query on users by email address, etc
 >
      Chapter 4. Administering Bugzilla
          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?
   
          So you followed 
    So you followed "Bugzilla Installation" to the
@@ -7711,28 +7773,28 @@ HREF="#INSTALLATION"
     getting data into your bug tracker.
   
      4.1. Post-Installation Checklist
            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.
     
      1. 	  Bring up 
	  Bring up editparams.cgi in your web
 	  browser.  This should be available as the 
        	  Set 
	  Set "maintainer" to 
        	  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
 	  
        	  Set "usebuggroups" to "on" 
	  Set "usebuggroups" to "on" only if you
 	  may wish to restrict access to products. I suggest leaving
@@ -7805,7 +7867,7 @@ CLASS="QUOTE"
 >
      2. 	  
	  "usebuggroupsentry", when set to
@@ -7817,7 +7879,7 @@ CLASS="QUOTE"
 	  installations where product isolation is a necessity.
 	
        	  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
@@ -7827,7 +7889,7 @@ CLASS="QUOTE"
 >
      3. 	  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
@@ -7845,16 +7907,16 @@ CLASS="QUOTE"
 	  extremely high-traffic Bugzilla databases.
 	
        	  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.

      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 @@ -7898,7 +7960,7 @@ CLASS="QUOTE" comments per day.

      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! @@ -7929,27 +7991,27 @@ CLASS="QUOTE" 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 data/params 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 data/params file.

      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.

      The "headerhtml" text box is the HTML printed out +> The "headerhtml" text box is the HTML printed out before any other code on the page, @@ -7991,7 +8053,7 @@ CLASS="QUOTE" is read as the text to send to the new user along with their password message.

      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.

      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 @@ -8044,7 +8106,7 @@ CLASS="QUOTE" >

    10. 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 @@ -8066,15 +8128,15 @@ CLASS="QUOTE" require that most other changes come with an explanation.

      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.

      11. 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 @@ -8127,7 +8189,7 @@ CLASS="QUOTE" security to prevent snooping, watchers are not a good idea.

      However, for most sites you should set +> However, for most sites you should set "supportwatchers"

      4.2. User Administration

      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.

      4.2.1. Creating the Default User

      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 @@ -8172,11 +8234,11 @@ NAME="DEFAULTUSER" password.

      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): mysql> use bugs; mysql> update profiles set groupset=0x7ffffffffffffff where login_name = "(user's @@ -8228,19 +8290,19 @@ CLASS="QUOTE" >

      4.2.2. Managing Other Users

      4.2.2.1. Logging In

    11. Open the index.html page for your Bugzilla installation +> Open the index.html page for your Bugzilla installation in your browser window.

    12. Click the "Query Existing Bug Reports" link. +> Click the "Query Existing Bug Reports" link.

    13. Click the "Log In" link at the foot of the page. +> Click the "Log In" link at the foot of the page.

    14. 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.

      Congratulations, you are logged in!

      15. 4.2.2.2. Creating new users

      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. @@ -8294,24 +8356,24 @@ NAME="CREATENEWUSERS" TYPE="1" >

    15. After logging in, click the "Users" link at the footer +> After logging in, click the "Users" link at the footer of the query page.

    16. 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.

      17. 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 man regexp manual page for details on regular @@ -8348,22 +8410,22 @@ CLASS="COMMAND" >

    17. 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

    18. Fill out the form presented. This page is +> Fill out the form presented. This page is self-explanatory. When done, click "submit".

      19. Adding a user this way will Adding a user this way will not send an email informing them of their username and @@ -8402,15 +8464,15 @@ CLASS="QUOTE" >

      4.2.2.3. Disabling Users

      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 @@ -8418,11 +8480,11 @@ NAME="DISABLEUSERS" text box, will be presented to the user the next time she attempts to use the system.

      Don't disable your own administrative account, or you +> Don't disable your own administrative account, or you will hate life!

      4.2.2.4. Modifying Users

      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.

      • Login Name: 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.

      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.

    19. Real Name: Duh!

    20. Password: You can change the user password here. It is normal to only see asterisks. @@ -8529,7 +8591,7 @@ VALIGN="TOP" >

    21. Email Notification: You may choose from one of three options: @@ -8539,7 +8601,7 @@ VALIGN="TOP" TYPE="1" >

    22. 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". @@ -8547,18 +8609,18 @@ TYPE="1" >

    23. 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.

      24. She will still receive whining cron emails if +> She will still receive whining cron emails if you set up the "whinemail" feature.

    24. All Qualifying Bugs: This user is a glutton for punishment. If her name is @@ -8595,9 +8657,10 @@ VALIGN="TOP"

      25. +

      Disable Text: If you type anything in this box, including just a space, the user account is @@ -8605,12 +8668,12 @@ VALIGN="TOP" interface, and what you type in this box is presented as the reason.

      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

    25. CanConfirm: This field is only used if you have enabled "unconfirmed" status in your @@ -8682,7 +8745,7 @@ VALIGN="TOP" >

    26. Creategroups: This option will allow a user to create and destroy groups in Bugzilla. @@ -8693,18 +8756,18 @@ VALIGN="TOP" >

    27. Editbugs: Unless a user has this bit set, they can only edit those bugs for which they are the assignee or the reporter.

      28. 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. @@ -8733,7 +8796,7 @@ VALIGN="TOP" >

    28. Editcomponents: This flag allows a user to create new products and components, as well as @@ -8749,7 +8812,7 @@ VALIGN="TOP" >

    29. Editkeywords: If you use Bugzilla's keyword functionality, enabling this feature allows a @@ -8766,7 +8829,7 @@ VALIGN="TOP" >

    30. Editusers: This flag allows a user do what you're doing right now: edit other users. This @@ -8777,7 +8840,7 @@ VALIGN="TOP" >

    31. PRODUCT: PRODUCT bugs access. This allows an administrator, with product-level granularity, @@ -8795,11 +8858,11 @@ VALIGN="TOP" >

      32. 4.3.1. Products

      Formerly, and in some spots still, called "Programs"

      Products are @@ -8852,7 +8915,7 @@ CLASS="GLOSSTERM" products (website, meetings...)

      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, @@ -8869,57 +8932,14 @@ CLASS="GLOSSTERM" TYPE="1" >

    32. Select "components" from the yellow footer +> Select "components" from the yellow footer

      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... -

    33. Select the "Add" link to the right of "Add a new product". -

    34. Enter the name of the product and a description. The - Description field is free-form. -

      35. Don't worry about the "Closed for bug entry", "Maximum Votes +> 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... +

    35. Select the "Add" link to the right of "Add a new product". +

    36. Enter the name of the product and a description. The + Description field is free-form. +

      37. 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 @@ -8947,34 +9010,34 @@ VALIGN="TOP" >

      4.3.2. Components

      Components are subsections of a Product. +> Components are subsections of a Product.

      Example 4-1. Creating some Components

      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 @@ -9000,7 +9063,7 @@ NAME="AEN1463" to the Component.

      To create a new Component: +> To create a new Component:

    37. Select the "Edit components" link from the "Edit product" +> Select the "Edit components" link from the "Edit product" page

    38. 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.

    39. 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.

      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.

    40. Select the "Log out" link on the footer of the +> Select the "Log out" link on the footer of the page.

    41. Select the "New Account" link on the footer of +> Select the "New Account" link on the footer of the "Relogin" page

    42. 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. @@ -9075,7 +9138,7 @@ TYPE="a" >

    43. 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.

    44. 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.

      4.3.3. Versions

      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.

      Example 4-2. Common Use of Versions

      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 @@ -9144,23 +9207,23 @@ NAME="AEN1492" >

      Example 4-3. A Different Use of Versions

      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 @@ -9178,7 +9241,7 @@ NAME="AEN1496" >

      To create and edit Versions: +> To create and edit Versions:

    45. From the "Edit product" screen, select "Edit Versions" +> From the "Edit product" screen, select "Edit Versions"

    46. 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.

      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.

    47. 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.

    48. 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. @@ -9220,26 +9283,26 @@ TYPE="1" >

      4.3.4. Milestones

      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.

      49. 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".

      To create new Milestones, set Default Milestones, and set +> To create new Milestones, set Default Milestones, and set Milestone URL:

    49. Select "edit milestones" +> Select "edit milestones"

    50. Select "Add" to the right of the "Add a new milestone" +> Select "Add" to the right of the "Add a new milestone" text

    51. 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".

      Example 4-4. Using SortKey with Target Milestone

      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", @@ -9321,17 +9384,17 @@ NAME="AEN1524" >

    52. 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.

      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, @@ -9363,21 +9426,21 @@ VALIGN="TOP" >

    53. 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"

      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.

    54. 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 @@ -9390,15 +9453,15 @@ VALIGN="TOP" >

      4.3.5. Voting

      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 @@ -9409,7 +9472,7 @@ NAME="VOTING" attention so they don't sit for a long time awaiting triage.

      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 @@ -9426,19 +9489,19 @@ NAME="VOTING" TYPE="1" >

    55. Navigate to the "Edit product" screen for the Product you +> Navigate to the "Edit product" screen for the Product you wish to modify

    56. 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.

    57. 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 @@ -9447,7 +9510,7 @@ TYPE="1" >

    58. 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 @@ -9455,12 +9518,12 @@ TYPE="1" Votes if your Bugzilla user base is unable to affect which bugs appear on Development radar?

      59. 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 @@ -9492,44 +9555,44 @@ VALIGN="TOP" >

    59. Once you have adjusted the values to your preference, +> Once you have adjusted the values to your preference, select the "Update" button.

      60. 4.3.6. Groups and Group Security

      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.

      Example 4-5. When to Use Group Security

      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 @@ -9553,11 +9616,11 @@ NAME="AEN1560" into two categories: Generic and Product-Based.

      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 @@ -9591,7 +9654,7 @@ VALIGN="TOP" next 32, etc.

      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 @@ -9607,7 +9670,7 @@ VALIGN="TOP" >

      To enable Generic Group Security ("usebuggroups"): +> To enable Generic Group Security ("usebuggroups"):

    60. Turn "On" "usebuggroups" in the "Edit Parameters" screen. +> Turn "On" "usebuggroups" in the "Edit Parameters" screen.

    61. 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.

    62. 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.

    63. 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.

      Example 4-6. Creating a New Group

      I created a group called DefaultGroup with a +> I created a group called DefaultGroup with a description of "This is simply a group to play @@ -9678,14 +9741,14 @@ CLASS="QUOTE" >

      64. To enable Product-Based Group Security (usebuggroupsentry): +> To enable Product-Based Group Security (usebuggroupsentry):

      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, @@ -9719,16 +9782,16 @@ VALIGN="TOP" TYPE="1" >

    64. Turn "On" "usebuggroups" and "usebuggroupsentry" in the +> Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.

      65. "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 @@ -9759,7 +9822,7 @@ VALIGN="TOP" >

    65. 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 @@ -9772,19 +9835,20 @@ VALIGN="TOP" >

      66. You may find this example illustrative for how bug groups work. +> You may find this example illustrative for how bug groups work.

      Example 4-7. Bugzilla Groups

      Bugzilla Groups example
      +CLASS="literallayout" +>
      +Bugzilla Groups example
      -----------------------

      For this example, let us suppose we have four groups, call them
      @@ -9880,11 +9944,11 @@ Group3, since he isn't in Group4.
      >

      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 @@ -9944,13 +10008,13 @@ VALIGN="TOP" >

      Secure your installation. +> Secure your installation.

      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

    66. 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.

      The MySQL Privilege System until you can recite it from memory!

      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 @@ -10013,14 +10077,14 @@ TARGET="_top" >

    67. 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.

    68. Do not run Apache as Do not run Apache as "nobody". This will @@ -10028,12 +10092,12 @@ CLASS="QUOTE" Run it, instead, as a user with a name, set via your httpd.conf file.

      69. "nobody" is a real user on UNIX systems. @@ -10072,7 +10136,7 @@ CLASS="QUOTE" >

    69. 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 @@ -10087,12 +10151,12 @@ CLASS="QUOTE" bug information to those who may not be allowed to see it.

      70. 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 @@ -10118,7 +10182,7 @@ VALIGN="TOP" details.

      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, you are at risk!

      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 for adequate protection in your data/ and shadow/ directories.

      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.

      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.

       <Files comments> allow
            from all </Files> deny from all 

      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.

       <Files localconfig> deny
            from all </Files> allow from all 

      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.

       deny from all 

      Chapter 5. Integrating Bugzilla with Third-Party Tools

      5.1. Bonsai

      Bonsai is a web-based tool for managing CVS, the Concurrent Versioning System . Using Bonsai, administrators can control open/closed status @@ -10214,16 +10278,16 @@ CLASS="QUOTE" > (include cool URL link here for Hook policies at mozilla.org). Bonsai also includes gateways to Tinderbox, the Mozilla automated build management system and Bugzilla

      5.2. CVS

      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

      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: http://homepages.kcbbs.gen.nz/~tonyg/ http://homepages.kcbbs.gen.nz/~tonyg/, under the

      Chapter 6. The Future of Bugzilla

      Bugzilla's Future.  Much of this is the present, now.

      Bugzilla's future is a constantly-changing thing, as various developers +> Bugzilla's future is a constantly-changing thing, as various developers "scratch an itch"

                                     Bugzilla Blue Sky
      +>


      +                               Bugzilla Blue Sky

      Customisability

      @@ -10924,10 +10989,10 @@ Whiny Reports

      Chapter 7. Bugzilla Variants and Competitors

      http://linas.org/linux/pm.html

      7.1. Red Hat Bugzilla

      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 @@ -10964,11 +11029,11 @@ TARGET="_top" >

      7.2. Loki Bugzilla (Fenris)

      . It is a fork from Bugzilla.

      7.3. Issuezilla

      Scarab, a newfangled Java-based issue tracker, is under heavy development and looks promising!

      7.5. Perforce SCM

      http://www.perforce.com/perforce/technotes/note052.html

      Appendix A. The Bugzilla FAQ

      1. General Questions
      A.1.1. Where can I find information about Bugzilla? Where can I find information about Bugzilla?
      A.1.2. What license is Bugzilla distributed under? +HREF="#AEN1728" +> What license is Bugzilla distributed under?
      A.1.3. How do I get commercial support for Bugzilla? +HREF="#AEN1734" +> How do I get commercial support for Bugzilla?
      A.1.4. What major companies or projects are currently using Bugzilla +HREF="#AEN1741" +> What major companies or projects are currently using Bugzilla for bug-tracking?
      A.1.5. Who maintains Bugzilla? +HREF="#AEN1766" +> Who maintains Bugzilla?
      A.1.6. How does Bugzilla stack up against other bug-tracking databases? +HREF="#AEN1772" +> How does Bugzilla stack up against other bug-tracking databases?
      A.1.7. How do I change my user name in Bugzilla? +HREF="#AEN1779" +> How do I change my user name in Bugzilla?
      A.1.8. 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.1.9. 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.1.10. 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?
      2. Red Hat Bugzilla
      A.2.1. What about Red Hat Bugzilla? +HREF="#AEN1826" +> What about Red Hat Bugzilla?
      A.2.2. What are the primary benefits of Red Hat Bugzilla? +HREF="#AEN1834" +> What are the primary benefits of Red Hat Bugzilla?
      A.2.3. What's the current status of Red Hat Bugzilla? +HREF="#AEN1862" +> What's the current status of Red Hat Bugzilla?
      3. Loki Bugzilla (AKA Fenris)
      A.3.1. What is Loki Bugzilla (Fenris)? +HREF="#AEN1875" +> What is Loki Bugzilla (Fenris)?
      4. Pointy-Haired-Boss Questions
      A.4.1. 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.4.2. 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.4.3. Does Bugzilla allow the user to track multiple projects? +HREF="#AEN1896" +> Does Bugzilla allow the user to track multiple projects?
      A.4.4. 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.4.5. 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.4.6. 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.4.7. 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.4.8. 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.4.9. 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.4.10. 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.4.11. 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.4.12. 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.4.13. 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? @@ -11296,68 +11361,68 @@ HREF="#AEN1961" >
      A.4.14. 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.4.15. 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.4.16. 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.4.17. 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.4.18. 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.4.19. Can the admin person establish separate group and individual user +HREF="#AEN2003" +> Can the admin person establish separate group and individual user privileges?
      A.4.20. 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.4.21. Are there any backup features provided? +HREF="#AEN2013" +> Are there any backup features provided?
      A.4.22. 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.4.23. 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 @@ -11366,8 +11431,8 @@ HREF="#AEN2015" >
      A.4.24. 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, @@ -11376,8 +11441,8 @@ HREF="#AEN2022" >
      A.4.25. 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?
      5. Bugzilla Installation
      A.5.1. How do I download and install Bugzilla? +HREF="#AEN2043" +> How do I download and install Bugzilla?
      A.5.2. How do I install Bugzilla on Windows NT? +HREF="#AEN2049" +> How do I install Bugzilla on Windows NT?
      A.5.3. Is there an easy way to change the Bugzilla cookie name? +HREF="#AEN2054" +> Is there an easy way to change the Bugzilla cookie name?
      6. Bugzilla Security
      A.6.1. 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.6.2. Are there any security problems with Bugzilla? +HREF="#AEN2067" +> Are there any security problems with Bugzilla?
      A.6.3. 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.
      7. Bugzilla Email
      A.7.1. 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.7.2. 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.7.3. 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.7.4. 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.7.5. 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.7.6. 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.7.7. How come email never reaches me from bugzilla changes? +HREF="#AEN2114" +> How come email never reaches me from bugzilla changes?
      8. Bugzilla Database
      A.8.1. I've heard Bugzilla can be used with Oracle? +HREF="#AEN2122" +> I've heard Bugzilla can be used with Oracle?
      A.8.2. 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.8.3. 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.8.4. 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.8.5. 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.8.6. 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.8.7. How do I synchronize bug information among multiple different Bugzilla +HREF="#AEN2155" +> How do I synchronize bug information among multiple different Bugzilla databases?
      A.8.8. 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.8.9. 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?
      9. Bugzilla and Win32
      A.9.1. 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.9.2. Is there a "Bundle::Bugzilla" equivalent for Win32? +HREF="#AEN2182" +> Is there a "Bundle::Bugzilla" equivalent for Win32?
      A.9.3. 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.9.4. 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.9.5. 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.
      10. Bugzilla Usage
      A.10.1. 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.10.2. 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.10.3. 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.10.4. 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.10.5. 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?
      11. Bugzilla Hacking
      A.11.1. What bugs are in Bugzilla right now? +HREF="#AEN2255" +> What bugs are in Bugzilla right now?
      A.11.2. 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.11.3. 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?

      1. General Questions

      A.1.1. Where can I find information about Bugzilla?

      + Where can I find information about Bugzilla?

      You can stay up-to-date with the latest Bugzilla +> + You can stay up-to-date with the latest Bugzilla information at http://www.mozilla.org/projects/bugzilla/ http://www.mozilla.org/projects/bugzilla/

      A.1.2. What license is Bugzilla distributed under? +> + What license is Bugzilla distributed under?

      Bugzilla is covered by the Mozilla Public License. +> + Bugzilla is covered by the Mozilla Public License. See details at http://www.mozilla.org/MPL/ http://www.mozilla.org/MPL/

      A.1.3. How do I get commercial support for Bugzilla? +> + How do I get commercial support for Bugzilla?

      + www.collab.net

      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. @@ -11772,25 +11843,27 @@ TARGET="_top" >

      A.1.4. What major companies or projects are currently using Bugzilla +> + What major companies or projects are currently using Bugzilla for bug-tracking?

      There are + There are dozens of major comapanies with public Bugzilla sites to track bugs in their products. A few include: @@ -11874,30 +11947,32 @@ BORDER="0" >

      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.

      A.1.5. Who maintains Bugzilla? +> + Who maintains Bugzilla?

      Bugzilla maintenance has been in a state of flux recently. +> + Bugzilla maintenance has been in a state of flux recently. Please check

      A.1.6. How does Bugzilla stack up against other bug-tracking databases? +> + How does Bugzilla stack up against other bug-tracking databases?

      A year has gone by, and I + A year has gone by, and I still can't find any head-to-head comparisons of Bugzilla against @@ -11937,7 +12014,7 @@ CLASS="ANSWER" flexibility, and superior ease-of-use.

      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 @@ -11946,55 +12023,59 @@ CLASS="ANSWER" >

      A.1.7. How do I change my user name in Bugzilla? +> + How do I change my user name in Bugzilla?

      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.

      A.1.8. 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?

      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.

      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 @@ -12007,32 +12088,33 @@ TARGET="_top" >

      A.1.9. 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?

      Terry Weissman answers,

      You're not the only one. But You're not the only one. But I am not very interested. I'm not a real SQL or database person. I just wanted to make a useful tool, @@ -12050,7 +12132,7 @@ CLASS="BLOCKQUOTE" >

      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:

      Bugzilla 3.0: One of the primary stated goals is multiple database support. @@ -12098,47 +12180,49 @@ TARGET="_top" >

      A.1.10. 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?

      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.

      Here's Terry Weissman's comment, for some historical context: +> Here's Terry Weissman's comment, for some historical context:

      [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.

      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.

      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.

      2. Red Hat Bugzilla

      This section is no longer up-to-date. Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. @@ -12215,24 +12299,26 @@ VALIGN="TOP" >

      A.2.1. What about Red Hat Bugzilla? +> + What about Red Hat Bugzilla?

      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. @@ -12242,14 +12328,14 @@ CLASS="ANSWER" yourself?

      Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: +> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:

      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.

      A.2.2. What are the primary benefits of Red Hat Bugzilla? +> + What are the primary benefits of Red Hat Bugzilla?

      + Dave Lawrence:

      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 @@ -12296,7 +12384,7 @@ CLASS="BLOCKQUOTE" internal tools I am working on also look like Bugzilla.

      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. @@ -12304,7 +12392,7 @@ CLASS="BLOCKQUOTE" is difficult sometimes to come by.

      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: @@ -12315,18 +12403,18 @@ CLASS="BLOCKQUOTE" TYPE="1" >

    70. No enum types. All old enum types are now separate smaller tables. +> No enum types. All old enum types are now separate smaller tables.

    71. 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

    72. 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 @@ -12334,7 +12422,7 @@ TYPE="1" >

    73. 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 @@ -12344,14 +12432,14 @@ TYPE="1" >

    74. 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.

    75. 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 @@ -12361,7 +12449,7 @@ TYPE="1" >

    76. 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 @@ -12370,7 +12458,7 @@ TYPE="1" >

    77. 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 @@ -12380,7 +12468,7 @@ TYPE="1" >

      78. 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 @@ -12394,29 +12482,31 @@ TYPE="1" >

      A.2.3. What's the current status of Red Hat Bugzilla? +> + What's the current status of Red Hat Bugzilla?

      +

      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.

      Dave Lawrence:

      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 @@ -12479,7 +12569,7 @@ CLASS="BLOCKQUOTE" thing going to help others that may need it.

      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 @@ -12502,31 +12592,33 @@ CLASS="BLOCKQUOTE" >

      3. Loki Bugzilla (AKA Fenris)

      A.3.1. What is Loki Bugzilla (Fenris)? +> + What is Loki Bugzilla (Fenris)?

      Loki Games has a customized version of Bugzilla available at +> + Loki Games has a customized version of Bugzilla available at

      4. Pointy-Haired-Boss Questions

      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 :)

      A.4.1. 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?

      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.

      A.4.2. 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)?

      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.

      A.4.3. Does Bugzilla allow the user to track multiple projects? +> + Does Bugzilla allow the user to track multiple projects?

      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 @@ -12649,48 +12747,52 @@ CLASS="ANSWER" >

      A.4.4. 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?

      Yes. +> + Yes.

      A.4.5. 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?

      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 @@ -12700,31 +12802,33 @@ CLASS="ANSWER" >

      A.4.6. 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?

      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.

      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.4.7. 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?

      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 index.html to index.shtml.

      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 index.shtml: 

      <!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
      +<!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" --> + +

      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.

      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 api.cgi) that basically looks like: @@ -12837,8 +12946,9 @@ WIDTH="100%" >

      #!/usr/bonsaitools/bin/perl -w
+CLASS="programlisting"
+>
+#!/usr/bonsaitools/bin/perl -w
 
 require 'globals.pl';
 
@@ -12846,14 +12956,16 @@ if ($::FORM{sub} eq 'PutFooter') {
     PutFooter();
 } else {
     die 'api.cgi was incorrectly called';
-}
      and then put this line in index.shtml. 
      <!--#include virtual="api.cgi?sub=PutFooter"-->
      +<!--#include virtual="api.cgi?sub=PutFooter"--> + +

      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.4.8. 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. :)

      Yes. Look at + Yes. Look at http://bugzilla.mozilla.org/reports.cgi http://bugzilla.mozilla.org/reports.cgi for basic reporting facilities.

      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 @@ -12945,85 +13062,91 @@ TARGET="_top" interface with the database directly.

      Advanced Reporting is a Bugzilla 3.X proposed feature. +> Advanced Reporting is a Bugzilla 3.X proposed feature.

      A.4.9. 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?

      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.

      A.4.10. 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?

      Yes. +> + Yes.

      A.4.11. 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?

      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.

      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 @@ -13055,26 +13178,28 @@ VALIGN="TOP" >

      A.4.12. 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.?

      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. @@ -13082,38 +13207,40 @@ CLASS="ANSWER" >

      A.4.13. 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?

      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.

      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.

      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 @@ -13121,31 +13248,33 @@ CLASS="ANSWER" http://www.mozilla.org/quality/help/bugzilla-helper.html http://www.mozilla.org/quality/help/bugzilla-helper.html

      A.4.14. 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?

      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. @@ -13153,208 +13282,225 @@ CLASS="ANSWER" >

      A.4.15. 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?

      Yes. No. No. +> + Yes. No. No.

      A.4.16. 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?

      Yes. +> + Yes.

      A.4.17. 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?

      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.

      A.4.18. Does Bugzilla have the ability to search by word, phrase, compound +> + Does Bugzilla have the ability to search by word, phrase, compound search?

      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.

      A.4.19. Can the admin person establish separate group and individual user +> + Can the admin person establish separate group and individual user privileges?

      Yes. +> + Yes.

      A.4.20. 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?

      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.

      A.4.21. Are there any backup features provided? +> + Are there any backup features provided?

      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 http://www.mysql.com/doc/B/a/Backup.html http://www.mysql.com/doc/B/a/Backup.html

      A.4.22. Can users be on the system while a backup is in progress? +> + Can users be on the system while a backup is in progress?

      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.

      A.4.23. 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 @@ -13362,21 +13508,22 @@ NAME="AEN2015"

      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".

      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.

      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. @@ -13384,16 +13531,17 @@ CLASS="ANSWER" >

      A.4.24. 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, @@ -13401,11 +13549,12 @@ NAME="AEN2022"

      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 @@ -13415,137 +13564,147 @@ CLASS="ANSWER" >

      A.4.25. 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?

      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.

      5. Bugzilla Installation

      A.5.1. How do I download and install Bugzilla? +> + How do I download and install Bugzilla?

      Check + Check http://www.mozilla.org/projects/bugzilla/ http://www.mozilla.org/projects/bugzilla/ for details. Once you download it, untar it, read the Bugzilla Guide.

      A.5.2. How do I install Bugzilla on Windows NT? +> + How do I install Bugzilla on Windows NT?

      Installation on Windows NT has its own section in +> + Installation on Windows NT has its own section in "The Bugzilla Guide".

      A.5.3. Is there an easy way to change the Bugzilla cookie name? +> + Is there an easy way to change the Bugzilla cookie name?

      At present, no. +> + At present, no.

      6. Bugzilla Security

      A.6.1. 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!)?

      Run mysql like this: "mysqld --skip-grant-tables". Please remember + Run mysql like this: "mysqld --skip-grant-tables". Please remember this makes mysql as secure as taping a $100 to the floor of a football stadium bathroom for safekeeping.

      A.6.2. Are there any security problems with Bugzilla? +> + Are there any security problems with Bugzilla?

      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. @@ -13580,26 +13741,28 @@ CLASS="ANSWER" >

      A.6.3. 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.

      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.

      7. Bugzilla Email

      A.7.1. 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?

      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.

      A.7.2. 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?

      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)".

      A.7.3. 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?

      Try Klaas Freitag's excellent patch for "whineatassigned" functionality. +> + Try Klaas Freitag's excellent patch for "whineatassigned" functionality. You can find it at http://bugzilla.mozilla.org/show_bug.cgi?id=6679 http://bugzilla.mozilla.org/show_bug.cgi?id=6679. This patch is against an older version of Bugzilla, so you must apply the diffs manually. @@ -13692,33 +13861,35 @@ TARGET="_top" >

      A.7.4. 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?

      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:

      bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" +> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"

      @@ -13729,53 +13900,57 @@ CLASS="BLOCKQUOTE" >

      A.7.5. 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?

      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.

      A.7.6. 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?

      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.

      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 "sendmailnow"

      A.7.7. How come email never reaches me from bugzilla changes? +> + How come email never reaches me from bugzilla changes?

      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.

      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".

      8. Bugzilla Database

      A.8.1. I've heard Bugzilla can be used with Oracle? +> + I've heard Bugzilla can be used with Oracle?

      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. @@ -13847,25 +14026,27 @@ CLASS="ANSWER" >

      A.8.2. 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?

      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 @@ -13882,30 +14063,32 @@ CLASS="ANSWER" >

      A.8.3. 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?

      Run the + Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home directory) from your web browser to see! If @@ -13927,24 +14110,26 @@ CLASS="FILENAME" >

      A.8.4. I want to manually edit some entries in my database. How? +> + I want to manually edit some entries in my database. How?

      There is no facility in Bugzilla itself to do this. It's also generally +> + 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 @@ -13954,49 +14139,53 @@ CLASS="ANSWER" >

      A.8.5. 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.

      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.

      A.8.6. 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.

      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 @@ -14005,61 +14194,65 @@ CLASS="ANSWER" >

      A.8.7. How do I synchronize bug information among multiple different Bugzilla +> + How do I synchronize bug information among multiple different Bugzilla databases?

      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.

      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.

      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.

      A.8.8. 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"?

      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. @@ -14067,35 +14260,37 @@ CLASS="ANSWER" >

      A.8.9. How come even after I delete bugs, the long descriptions show up? +> + How come even after I delete bugs, the long descriptions show up?

      This should only happen with Bugzilla 2.14 if you are +> + This should only happen with Bugzilla 2.14 if you are using the "shadow database" feature, and your shadow database is out of sync. Try running syncshadowdb -syncall to make sure your shadow database is in synch with your primary database. @@ -14104,92 +14299,98 @@ CLASS="OPTION" >

      9. Bugzilla and Win32

      A.9.1. 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)?

      Remove Windows. Install Linux. Install Bugzilla. +> + Remove Windows. Install Linux. Install Bugzilla. The boss will never know the difference.

      A.9.2. Is there a "Bundle::Bugzilla" equivalent for Win32? +> + Is there a "Bundle::Bugzilla" equivalent for Win32?

      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.

      A.9.3. 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?

      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.

      Microsoft has some advice on this matter, as well: +> Microsoft has some advice on this matter, as well:

      "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 @@ -14204,29 +14405,32 @@ CLASS="BLOCKQUOTE" >

      A.9.4. 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?

      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.

        1. #!C:/perl/bin/perl had to be added to every perl file.
      +CLASS="literallayout" +>
      +  1. #!C:/perl/bin/perl had to be added to every perl file.
        2. Converted to Net::SMTP to handle mail messages instead of
           /usr/bin/sendmail.
        3. The crypt function isn't available on Windows NT (at least none that I
      @@ -14315,56 +14519,58 @@ A: Sure! Here ya go!
      >

      A.9.5. 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.

      Your modules may be outdated or inaccurate. Try: +> + Your modules may be outdated or inaccurate. Try:

      1. Hitting http://www.activestate.com/ActivePerl +> Hitting http://www.activestate.com/ActivePerl

      2. Download ActivePerl +> Download ActivePerl

      3. Go to your prompt +> Go to your prompt

      4. Type 'ppm' +> Type 'ppm'

      5. PPM> install DBI DBD-mysql GD

        http://www.activestate.com/Packages/ http://www.activestate.com/Packages/

      10. Bugzilla Usage

      A.10.1. 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?

      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 http://bugzilla.mozilla.org/show_bug.cgi?id=16775 http://bugzilla.mozilla.org/show_bug.cgi?id=16775. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html"

      A.10.2. 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?

      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.

      Add a "and accept bug" radio button Add a "and accept bug" radio button

      "Accept" button automatically assigns to you "Accept" button automatically assigns to you

      A.10.3. 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?

      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.

      A.10.4. 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.

      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.

      A.10.5. 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?

      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.

      11. Bugzilla Hacking

      A.11.1. What bugs are in Bugzilla right now? +> + What bugs are in Bugzilla right now?

      Try + Try this link this link to view current bugs or requests for enhancement for Bugzilla.

      You can view bugs marked for 2.16 release +> You can view bugs marked for 2.16 release Bugzilla Project Page Bugzilla Project Page for details on how to check current sources out of CVS so you can have these bug fixes early! @@ -14597,28 +14815,30 @@ TARGET="_top" >

      A.11.2. 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"?

      This is well-documented here: + This is well-documented here: http://bugzilla.mozilla.org/show_bug.cgi?id=49862 http://bugzilla.mozilla.org/show_bug.cgi?id=49862. Ultimately, it's as easy as adding the "---" priority field to your localconfig file in the appropriate area, re-running checksetup.pl, and then changing the default priority in your browser using @@ -14629,20 +14849,21 @@ TARGET="_top" >

      A.11.3. 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?

    78. Enter a bug into bugzilla.mozilla.org for the Enter a bug into bugzilla.mozilla.org for the "

    79. 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 current sources checked out of CVS), @@ -14678,7 +14899,7 @@ TARGET="_top" >

    80. 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, @@ -14688,14 +14909,14 @@ TARGET="_top" >

    81. 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.

    82. 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 :)

      83. Appendix B. Software Download Links

      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.

      Apache Web Server: Apache Web Server: http://www.apache.org

      Bugzilla: Bugzilla: http://www.mozilla.org/projects/bugzilla/ http://www.mozilla.org/projects/bugzilla/

      MySQL: MySQL: http://www.mysql.com/

      Perl: Perl: http://www.perl.org/

      CPAN: CPAN: http://www.cpan.org/

      DBI Perl module: +> DBI Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/ http://www.cpan.org/modules/by-module/DBI/

      Data::Dumper module: +> Data::Dumper module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/ http://www.cpan.org/modules/by-module/Data/

      MySQL related Perl modules: +> 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: +> 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: +> GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/ http://www.cpan.org/modules/by-module/GD/ Alternately, you should be able to find the latest version of GD at

      Chart::Base module: +> Chart::Base module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/ http://www.cpan.org/modules/by-module/Chart/

      LinuxDoc Software: +> LinuxDoc Software:

      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?

      C.1. Database Schema Chart

      Database Relationships

      Bugzilla database relationships chart

      C.2. MySQL Bugzilla Database Introduction

      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 @@ -14894,7 +15115,7 @@ NAME="DBDOC" comes.

      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 @@ -14904,12 +15125,12 @@ NAME="DBDOC" testers.

      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.

      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 @@ -14918,12 +15139,12 @@ NAME="DBDOC" and rescue Jane from the clutches of Certain Death!

      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'.

      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, @@ -14932,7 +15153,7 @@ NAME="DBDOC" 'approved' as soon as possible. To avoid confusion, of course."

      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... @@ -14940,20 +15161,20 @@ NAME="DBDOC" burbling, and boiling on a hot Jamaican sand dune...

      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!

      C.2.1. Bugzilla Database Basics

      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

    83. To connect to your database: +> To connect to your database:

      bash#mysql-u root

      If this works without asking you for a password, +> If this works without asking you for a password, shame on you! You should have @@ -15012,7 +15233,7 @@ CLASS="PARAMETER" this:

      mysql>

      "bugs" is the name you chose in thelocalconfig file for your Bugzilla database, type:

      mysqluse bugs;

      C.2.1.1. Bugzilla Database Tables

      mysql>show tables from bugs;

      +-------------------+
+CLASS="programlisting"
+>
+-------------------+
 | Tables in bugs    |
 +-------------------+
 | attachments       |
@@ -15141,8 +15362,9 @@ CLASS="PROGRAMLISTING"
 >


      +
        Here's an overview of what each table does.  Most columns in each table have
      descriptive names that make it fairly trivial to figure out their jobs.

      @@ -15324,19 +15546,19 @@ http://www.devshed.com/Server_Side/MySQL/
      >

      84. C.3. MySQL Permissions & Grant Tables

      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. @@ -15375,8 +15597,9 @@ VALIGN="TOP" >

      From matt_barnson@singletrac.com Wed Jul  7 09:00:07 1999
      +CLASS="literallayout" +>
      +From matt_barnson@singletrac.com Wed Jul  7 09:00:07 1999
      Date: Mon, 1 Mar 1999 21:37:04 -0700 
      From: Matthew Barnson matt_barnson@singletrac.com
      To: keystone-users@homeport.org
      @@ -15542,28 +15765,28 @@ http://www.mysql.com/Manual/manual.html.
      >

      Appendix D. Useful Patches and Utilities for Bugzilla

      Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.

      D.1. Apache mod_rewrite magic

      Apache's mod_rewrite module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.

    84. Make it so if someone types +> Make it so if someone types http://www.foo.com/12345, Bugzilla spits back @@ -15584,17 +15807,19 @@ CLASS="COMPUTEROUTPUT" >

      D.2. The setperl.csh Utility

      1. Download the "setperl.csh" utility to your Bugzilla +> Download the "setperl.csh" utility to your Bugzilla directory and make it executable.

        1. bash# cd /your/path/to/bugzilla

        2. bash# wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'

        3. bash# chmod u+x setperl.csh

        4. Prepare (and fix) Bugzilla file permissions. +> Prepare (and fix) Bugzilla file permissions.

          1. bash# chmod u+w *

          2. bash# chmod u+x duplicates.cgi

          3. bash# chmod a-x bug_status.html

          4. Run the script: +> Run the script:

            bash# ./setperl.csh /your/path/to/perl

            Example D-1. Using Setperl to set your perl path

            bash# ./setperl.csh /usr/bin/perl

      D.3. Command-line Bugzilla Queries

      Users can query Bugzilla from the command line using this suite +> Users can query Bugzilla from the command line using this suite of utilities.

      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"

      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 @@ -15820,53 +16045,53 @@ NAME="CMDLINE" prefixed with "--default=".

      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 grep COLUMLIST ~/.netscape/cookies to see your current COLUMNLIST setting.

      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 sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'

      Akkana says she has good results piping buglist output through +> Akkana says she has good results piping buglist output through w3m -T text/html -dump

      1. Download three files: +> Download three files:

        1. bash$ wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'

        2. bash$ wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'

        3. bash# wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'

        4. Make your utilities executable: +> Make your utilities executable: bash$ chmod u+x buglist bugs

      D.4. The Quicksearch Utility

      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"

      The index.html page has been updated to include the QuickSearch +> The index.html page has been updated to include the QuickSearch text box.

      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.

      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" @@ -15960,7 +16185,7 @@ NAME="QUICKSEARCH" but not those with the keyword "foo".

      Workarounds for Bugzilla users: +> Workarounds for Bugzilla users: 

      <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>
+

      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.

      D.5. Hacking Bugzilla

      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.

      D.5.1. Things that have caused problems and should be avoided

    85. Usage of variables in Regular Expressions +> Usage of variables in Regular Expressions

      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:

      86. -- NOT THIS -- +> -- NOT THIS -- 

      grep ($_ eq $value, @array);
+CLASS="programlisting"
+>
grep ($_ eq $value, @array);
             

      grep (/$value/, @array);
+CLASS="programlisting"
+>
grep (/$value/, @array);

      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 \Q..\E).

      D.5.2. Coding Style for Bugzilla

      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 :).

      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 "Programming Perl" (the camel book) or by typing man perlstyle at your 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. +> 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.

      • Whitespace +> Whitespace

        Bugzilla's prefered indentation is 4 spaces (no tabs, please). +> Bugzilla's prefered indentation is 4 spaces (no tabs, please).

      • Curly braces. +> Curly braces.

        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: 

      if ($var) {
+CLASS="programlisting"
+>
if ($var) {
     print "The variable is true";
 }
 else {
@@ -16179,20 +16406,20 @@ else {
 >
           
                  -- NOT THIS --
+>
            -- NOT THIS --
           
                  
      
            
      if ($var)
+CLASS="programlisting"
+>
if ($var)
 {
     print "The variable is true";
 }
@@ -16210,16 +16437,27 @@ else
 >
    86.             File Names
+>
	    Cookies
+	  
      
	    Bugzilla uses cookies to ease the user experience, but no new patches
+	    should require user-side cookies.
+	  
    87. 
            File Names
           
                  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. \ / : * ? " < >
             and | are all illegal characters for filenames
             on various platforms.  Also, file names should not have spaces in them as they
@@ -16228,50 +16466,111 @@ CLASS="COMPUTEROUTPUT"
 >
    88.             Variable Names
+>
	    Javascript dependencies
+	  
      
	    While Bugzilla uses Javascript to make the user experience easier, no patch
+	    to Bugzilla should require Javascript.
+	  
    89. 
	    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.
+	  
    90. 
	    Schema Changes
+	  
      
	    If you make schema changes, you should modify sanitycheck.cgi
+	    to support the new schema.  All referential columns should be checked.
+	  
    91. 
	    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.
+	  
    92. 
	    Templatization
+	  
      
	    Patches to Bugzilla need to support templates so they do not force user interface choices
+	    on Bugzilla administrators.
+	  
    93. 
            Variable Names
           
                  If a variable is scoped globally (
            If a variable is scoped globally ($::variable)
             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,
             $ret could be used as a staging variable for a
              routine's return value as the line return $ret;
              will make it blatantly obvious what the variable holds and most likely be shown
              on the same screen as my $ret = "";.
           
    94.             Cross Database Compatability
+>
            Cross Database Compatability
           
                  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
             encrypt().
           
    95.             Cross Platform Compatability
+>
            Cross Platform Compatability
           
                  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
@@ -16283,16 +16582,16 @@ CLASS="FUNCTION"
 >
      Appendix E. GNU Free Documentation License
      Version 1.1, March 2000
      How to use this License for your documents
            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".
      If you have no Invariant Sections, write "with no Invariant
@@ -16822,15 +17122,15 @@ CLASS="BLOCKQUOTE"
 CLASS="GLOSSARY"
 >
      Glossary
      0-9, high ascii
      	    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 .htaccess 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
 	    localconfig file contains the
 	    password to your database.  If this information were
@@ -16862,11 +17162,11 @@ CLASS="FILENAME"
 >
      A
      In this context, Apache is the web server most
 	    commonly used for serving up
 	    Bugzilla pages.  Contrary to
 	    popular belief, the apache web server has nothing to do
@@ -16890,18 +17190,18 @@ CLASS="QUOTE"
 >"a patchy" version of the original
 	    NCSA world-wide-web server.
      B
      	    A 
	    A "Bug" in Bugzilla refers to an issue
@@ -16933,7 +17233,7 @@ CLASS="QUOTE"
 >
      	    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.
@@ -16963,31 +17263,31 @@ CLASS="QUOTE"
 >
      	    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.
 	  
      Component
      	    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
@@ -16996,10 +17296,10 @@ NAME="GLOSS_COMPONENT"
 >
      CPAN
      CPAN stands for the
 	    .  CPAN
 	    maintains a large number of extremely useful
 	    Perl modules.  By themselves, Perl
 	    modules generally do nothing, but when used as part of a
@@ -17026,11 +17326,11 @@ CLASS="GLOSSTERM"
 >
      D
      mysqld, the
 	    MySQL server, and apache, a web
 	    server, are generally run as daemons.
      Products and
 	    Components in the
 	    Bugzilla database.
      M
      mysqld is the name of the
 	    daemon for the MySQL database.  In
 	    general, it is invoked automatically through the use of
@@ -17142,11 +17442,11 @@ CLASS="GLOSSTERM"
 >
      P
      Bugzilla is
 	    maintained in Perl.
      S
      SGML
      SGML stands for SGML has withstood the test of time as
 	    a robust, powerful language.
 	    XML is the
@@ -17344,20 +17644,20 @@ CLASS="QUOTE"
 >"baby brother" of SGML; any valid
 	    XML document it, by definition, a valid
 	    SGML document.  The document you are
 	    reading is written and maintained in
 	    SGML, and is also valid
 	    XML if you modify the Document Type
 	    Definition.
      T
      Target Milestone
      	    Target Milestones are Product goals.  They are
+>
	    Target Milestones are Product goals.  They are
 	    configurable on a per-Product basis.  Most software
 	    development houses have a concept of
 	    
      Chapter 1. About This Guide
      1.1. Purpose and Scope of this Guide
            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.
     
            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.
     
            This release of the Bugzilla Guide is the
+>
      This release of the Bugzilla Guide is the
       2.14 release. It is so named that it
@@ -108,7 +108,7 @@ NAME="ABOUTTHISGUIDE"
       developers, and those who enjoy a lot of pain. 
     
            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
       
            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
       <barnboy@trilobyte.net
      Chapter 4. Administering Bugzilla
          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?
   
          So you followed 
    So you followed "
      3.4. BSD Installation Notes
            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 Section 3.3
      D.5. Hacking Bugzilla
            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.
     
    96.             Usage of variables in Regular Expressions
+>
            Usage of variables in Regular Expressions
           
                  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:
           
                  
      
            
                  -- NOT THIS --
+>
            -- NOT THIS --
           
                  
      grep ($_ eq $value, @array);
+CLASS="programlisting"
+>
grep ($_ eq $value, @array);
             
      		
           
      
            
      grep (/$value/, @array);
+CLASS="programlisting"
+>
grep (/$value/, @array);
             
      		
           
                    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 \Q..\E).
             
      D.5.2. Coding Style for Bugzilla
              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 :).
       
              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 "Programming
         Perl" (the camel book) or by typing man perlstyle at
         your 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.
+>
        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.
       
      •             Whitespace
+>
            Whitespace
           
                    Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+>
            Bugzilla's prefered indentation is 4 spaces (no tabs, please).
           
      •             Curly braces.
+>
            Curly braces.
           
                    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:
           
                    
      
            
      if ($var) {
+CLASS="programlisting"
+>
if ($var) {
     print "The variable is true";
 }
 else {
@@ -252,20 +254,20 @@ else {
 >
           
                  -- NOT THIS --
+>
            -- NOT THIS --
           
                  
      
            
      if ($var)
+CLASS="programlisting"
+>
if ($var)
 {
     print "The variable is true";
 }
@@ -283,16 +285,27 @@ else
 >
    97.             File Names
+>
	    Cookies
+	  
      
	    Bugzilla uses cookies to ease the user experience, but no new patches
+	    should require user-side cookies.
+	  
    98. 
            File Names
           
                  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. \ / : * ? " < >
             and | are all illegal characters for filenames
             on various platforms.  Also, file names should not have spaces in them as they
@@ -301,50 +314,111 @@ CLASS="COMPUTEROUTPUT"
 >
    99.             Variable Names
+>
	    Javascript dependencies
+	  
      
	    While Bugzilla uses Javascript to make the user experience easier, no patch
+	    to Bugzilla should require Javascript.
+	  
    100. 
	    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.
+	  
    101. 
	    Schema Changes
+	  
      
	    If you make schema changes, you should modify sanitycheck.cgi
+	    to support the new schema.  All referential columns should be checked.
+	  
    102. 
	    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.
+	  
    103. 
	    Templatization
+	  
      
	    Patches to Bugzilla need to support templates so they do not force user interface choices
+	    on Bugzilla administrators.
+	  
    104. 
            Variable Names
           
                  If a variable is scoped globally (
            If a variable is scoped globally ($::variable)
             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,
             $ret could be used as a staging variable for a
              routine's return value as the line return $ret;
              will make it blatantly obvious what the variable holds and most likely be shown
              on the same screen as my $ret = "";.
           
    105.             Cross Database Compatability
+>
            Cross Database Compatability
           
                  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
             encrypt().
           
    106.             Cross Platform Compatability
+>
            Cross Platform Compatability
           
                  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
diff --git a/webtools/bugzilla/docs/html/cmdline.html b/webtools/bugzilla/docs/html/cmdline.html
index 7a1e1ba4487..09a645d6a11 100644
--- a/webtools/bugzilla/docs/html/cmdline.html
+++ b/webtools/bugzilla/docs/html/cmdline.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="The Quicksearch Utility"
 HREF="quicksearch.html">
      D.3. Command-line Bugzilla Queries
            Users can query Bugzilla from the command line using this suite
+>
      Users can query Bugzilla from the command line using this suite
       of utilities.
     
            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"
     
            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
@@ -93,53 +93,53 @@ NAME="CMDLINE"
       prefixed with "--default=".
     
            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
       grep COLUMLIST ~/.netscape/cookies to see
       your current COLUMNLIST setting.
     
            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 sed -e 's/,/ /g' | wc |
 	awk '{printf $2 "\n"}'
     
            Akkana says she has good results piping buglist output through
+>
      Akkana says she has good results piping buglist output through
       w3m -T text/html -dump
     
      1. 	  Download three files:
+>
	  Download three files:
 	
        1. 	      
	       bash$ wget -O
 		  query.conf
 		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'
        2. 	      
	       bash$ wget -O
 		  buglist
 		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'
        3. 	      
	       bash# wget -O
 		  bugs
 		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'
        4. 	  Make your utilities executable:
+>
	  Make your utilities executable:
 	  	    
	    bash$
 	    chmod u+x buglist bugs
 	  
      1.6. Contributors
            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):
     
            Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+>
      Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
       Teitelbaum, Jacob Steenhagen, Joe Robins
     
      1.9. Document Conventions
          This document uses the following conventions
+>
    This document uses the following conventions
   
      107. DescriptionsAppearance
      Warnings
      Hint
      Notes
      Information requiring special attention
      File Namesfile.extension
      Directory Namesdirectory
      Commands to be typedcommand
      Applications Namesapplication
      Prompt of users command under bash shellbash$
      Prompt of root users command under bash shellbash#
      Prompt of user command under tcsh shelltcsh$
      Environment VariablesVARIABLE
      Emphasized wordword
      Code Example
      <para>Beginning and end of paragraph</para>
            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. 
     
      1.5. Credits
            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:
     
            
      Terry Weissman
            
      Tara
@@ -98,7 +98,7 @@ TARGET="_top"
       strong after Terry left Mozilla.org
     
            
      Dave Lawrence
            
      Dawn Endico
            Last but not least, all the members of the 
      Last but not least, all the members of the  netscape.public.mozilla.webtools
      5.2. CVS
            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 
            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:
             http://homepages.kcbbs.gen.nz/~tonyg/
      http://homepages.kcbbs.gen.nz/~tonyg/, under the
       
      Appendix C. The Bugzilla Database
            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?
     
      C.2. MySQL Bugzilla Database Introduction
            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
@@ -82,7 +82,7 @@ NAME="DBDOC"
       comes.
     
            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
@@ -92,12 +92,12 @@ NAME="DBDOC"
       testers.
     
            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.
     
            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
@@ -106,12 +106,12 @@ NAME="DBDOC"
       and rescue Jane from the clutches of Certain Death!
     
            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'.
     
            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,
@@ -120,7 +120,7 @@ NAME="DBDOC"
       'approved' as soon as possible. To avoid confusion, of course."
     
            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...
@@ -128,20 +128,20 @@ NAME="DBDOC"
       burbling, and boiling on a hot Jamaican sand dune...
     
            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!
     
      C.2.1. Bugzilla Database Basics
      	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 
    107. 	      To connect to your database:
+>
	      To connect to your database:
 	    
      	      
	      bash#mysql-u root
 	    
      	      If this works without asking you for a password,
+>
	      If this works without asking you for a password,
 	      shame on you!  You should have
@@ -200,7 +200,7 @@ CLASS="PARAMETER"
 	      this:
      mysql>
      "bugs" is the name
 	      you chose in thelocalconfig file
 	      for your Bugzilla database, type:
      mysqluse bugs;
      108. 
       
      C.2.1.1. Bugzilla Database Tables
      mysql>show tables from bugs;
      +-------------------+
+CLASS="programlisting"
+>
+-------------------+
 | Tables in bugs    |
 +-------------------+
 | attachments       |
@@ -329,8 +329,9 @@ CLASS="PROGRAMLISTING"
 >

      
+
      
   Here's an overview of what each table does.  Most columns in each table have
      
 descriptive names that make it fairly trivial to figure out their jobs.
      
 
      
diff --git a/webtools/bugzilla/docs/html/dbschema.html b/webtools/bugzilla/docs/html/dbschema.html
index 36f51014dcb..66871536f1a 100644
--- a/webtools/bugzilla/docs/html/dbschema.html
+++ b/webtools/bugzilla/docs/html/dbschema.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="MySQL Bugzilla Database Introduction"
 HREF="dbdoc.html">
      C.1. Database Schema Chart
            
      
      
      Database Relationships
      Bugzilla database relationships chart
      1.3. Disclaimer
            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
@@ -84,13 +84,13 @@ NAME="DISCLAIMER"
       war.  Proceed with caution.
     
            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.
     
            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,
@@ -98,13 +98,13 @@ NAME="DISCLAIMER"
       environment for Bugzilla.
     
            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!
     
            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
diff --git a/webtools/bugzilla/docs/html/downloadlinks.html b/webtools/bugzilla/docs/html/downloadlinks.html
index a6f289a75a8..37f40f6abe5 100644
--- a/webtools/bugzilla/docs/html/downloadlinks.html
+++ b/webtools/bugzilla/docs/html/downloadlinks.html
@@ -16,7 +16,7 @@ REL="NEXT"
 TITLE="The Bugzilla Database"
 HREF="database.html">
      Appendix B. Software Download Links
          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.
   
          Apache Web Server: 
    Apache Web Server: http://www.apache.org
          Bugzilla: 
    Bugzilla:       http://www.mozilla.org/projects/bugzilla/
      http://www.mozilla.org/projects/bugzilla/
   
          MySQL: 
    MySQL: http://www.mysql.com/
   
          Perl: 
    Perl: http://www.perl.org/
   
          CPAN: 
    CPAN: http://www.cpan.org/
   
          DBI Perl module: 
+>
    DBI Perl module: 
           ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
      http://www.cpan.org/modules/by-module/DBI/
   
          Data::Dumper module: 
+>
    Data::Dumper module: 
           ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
      http://www.cpan.org/modules/by-module/Data/
   
          MySQL related Perl modules:
+>
    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:
+>
    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:
+>
    GD Perl module:
           ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
      http://www.cpan.org/modules/by-module/GD/
     Alternately, you should be able to find the latest version of
     GD at 
   
          Chart::Base module:
+>
    Chart::Base module:
         ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
    http://www.cpan.org/modules/by-module/Chart/
   
          LinuxDoc Software: 
+>
    LinuxDoc Software: 
     
      	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 "paranoid" security
 	options, it is possible that the checksetup.pl script may fail
 	with the error: cannot chdir(/var/spool/mqueue):
 	  Permission denied This is because your
 	/var/spool/mqueue directory has a mode of
 	"drwx------".  Type chmod 755
 	  /var/spool/mqueue as root to
@@ -116,7 +116,7 @@ CLASS="FILENAME"
 >
      	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
@@ -126,9 +126,9 @@ CLASS="FILENAME"
 >
      	Release Notes for Bugzilla 2.14 are available at
+>
	Release Notes for Bugzilla 2.14 are available at
 	docs/rel_notes.txt in your Bugzilla
 	source distribution.
@@ -136,7 +136,7 @@ CLASS="FILENAME"
 >
      	  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.
@@ -147,11 +147,11 @@ CLASS="FILENAME"
 >
      	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
@@ -181,11 +181,11 @@ VALIGN="TOP"
 >
      	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.
diff --git a/webtools/bugzilla/docs/html/faq.html b/webtools/bugzilla/docs/html/faq.html
index eea2d6b3d92..960647f853c 100644
--- a/webtools/bugzilla/docs/html/faq.html
+++ b/webtools/bugzilla/docs/html/faq.html
@@ -11,12 +11,12 @@ TITLE="The Bugzilla Guide"
 HREF="index.html">Prev
      Appendix A. The Bugzilla FAQ
      1. General Questions
      A.1.1. 	    Where can I find information about Bugzilla?
	    Where can I find information about Bugzilla?
      A.1.2. 	    What license is Bugzilla distributed under?
+HREF="faq.html#AEN1728"
+>
	    What license is Bugzilla distributed under?
 	  
      A.1.3. 	    How do I get commercial support for Bugzilla?
+HREF="faq.html#AEN1734"
+>
	    How do I get commercial support for Bugzilla?
 	  
      A.1.4. 	    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.1.5. 	    Who maintains Bugzilla?
+HREF="faq.html#AEN1766"
+>
	    Who maintains Bugzilla?
 	  
      A.1.6. 	    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.1.7. 	    How do I change my user name in Bugzilla?
+HREF="faq.html#AEN1779"
+>
	    How do I change my user name in Bugzilla?
 	  
      A.1.8. 	    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.1.9. 	    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.1.10. 	    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?
 	  
      2. Red Hat Bugzilla
      A.2.1. 	    What about Red Hat Bugzilla?
+HREF="faq.html#AEN1826"
+>
	    What about Red Hat Bugzilla?
 	  
      A.2.2. 	    What are the primary benefits of Red Hat Bugzilla?
+HREF="faq.html#AEN1834"
+>
	    What are the primary benefits of Red Hat Bugzilla?
 	  
      A.2.3. 	    What's the current status of Red Hat Bugzilla?
+HREF="faq.html#AEN1862"
+>
	    What's the current status of Red Hat Bugzilla?
 	  
      3. Loki Bugzilla (AKA Fenris)
      A.3.1. 	    What is Loki Bugzilla (Fenris)?
+HREF="faq.html#AEN1875"
+>
	    What is Loki Bugzilla (Fenris)?
 	  
      4. Pointy-Haired-Boss Questions
      A.4.1. 	    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.4.2. 	    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.4.3. 	    Does Bugzilla allow the user to track multiple projects?
+HREF="faq.html#AEN1896"
+>
	    Does Bugzilla allow the user to track multiple projects?
 	  
      A.4.4. 	    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.4.5. 	    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.4.6. 	    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.4.7. 	    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.4.8. 	    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.4.9. 	    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.4.10. 	    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.4.11. 	    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.4.12. 	     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.4.13. 	    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?
@@ -290,68 +290,68 @@ HREF="faq.html#AEN1961"
 >
      A.4.14. 	    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.4.15. 	    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.4.16. 	    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.4.17. 	    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.4.18. 	    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.4.19. 	    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.4.20. 	     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.4.21. 	    Are there any backup features provided?
+HREF="faq.html#AEN2013"
+>
	    Are there any backup features provided?
 	  
      A.4.22. 	    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.4.23. 	    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
@@ -360,8 +360,8 @@ HREF="faq.html#AEN2015"
 >
      A.4.24. 	    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,
@@ -370,8 +370,8 @@ HREF="faq.html#AEN2022"
 >
      A.4.25. 	    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?
 	  
      5. Bugzilla Installation
      A.5.1. 	    How do I download and install Bugzilla?
+HREF="faq.html#AEN2043"
+>
	    How do I download and install Bugzilla?
 	  
      A.5.2. 	    How do I install Bugzilla on Windows NT?
+HREF="faq.html#AEN2049"
+>
	    How do I install Bugzilla on Windows NT?
 	  
      A.5.3. 	    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?
 	  
      6. Bugzilla Security
      A.6.1. 	    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.6.2. 	    Are there any security problems with Bugzilla?
+HREF="faq.html#AEN2067"
+>
	    Are there any security problems with Bugzilla?
 	  
      A.6.3. 	    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.
 	  
      7. Bugzilla Email
      A.7.1. 	    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.7.2. 	    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.7.3. 	    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.7.4. 	    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.7.5. 	    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.7.6. 	    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.7.7. 	     How come email never reaches me from bugzilla changes?
+HREF="faq.html#AEN2114"
+>
	     How come email never reaches me from bugzilla changes?
 	  
      8. Bugzilla Database
      A.8.1. 	    I've heard Bugzilla can be used with Oracle?
+HREF="faq.html#AEN2122"
+>
	    I've heard Bugzilla can be used with Oracle?
 	  
      A.8.2. 	    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.8.3. 	    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.8.4. 	    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.8.5. 	    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.8.6. 	    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.8.7. 	    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.8.8. 	    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.8.9. 	    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?
 	  
      9. Bugzilla and Win32
      A.9.1. 	    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.9.2. 	    Is there a "Bundle::Bugzilla" equivalent for Win32?
+HREF="faq.html#AEN2182"
+>
	    Is there a "Bundle::Bugzilla" equivalent for Win32?
 	  
      A.9.3. 	    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.9.4. 	    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.9.5. 	    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.
 	  
      10. Bugzilla Usage
      A.10.1. 	    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.10.2. 	    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.10.3. 	    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.10.4. 	    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.10.5. 	    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?
 	  
      11. Bugzilla Hacking
      A.11.1. 	    What bugs are in Bugzilla right now?
+HREF="faq.html#AEN2255"
+>
	    What bugs are in Bugzilla right now?
 	  
      A.11.2. 	    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.11.3. 	    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?
 	  
      1. General Questions
      A.1.1. 	    Where can I find information about Bugzilla?
      
+	    Where can I find information about Bugzilla?
       	    You can stay up-to-date with the latest Bugzilla
+>
+	    You can stay up-to-date with the latest Bugzilla
 	    information at 	    http://www.mozilla.org/projects/bugzilla/
	    http://www.mozilla.org/projects/bugzilla/
 	  
      A.1.2. 	    What license is Bugzilla distributed under?
+>
+	    What license is Bugzilla distributed under?
 	  
       	    Bugzilla is covered by the Mozilla Public License.
+>
+	    Bugzilla is covered by the Mozilla Public License.
 	    See details at 	    http://www.mozilla.org/MPL/
	    http://www.mozilla.org/MPL/
 	  
      A.1.3. 	    How do I get commercial support for Bugzilla?
+>
+	    How do I get commercial support for Bugzilla?
 	  
       	    
+	    www.collab.net
      	    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.
@@ -766,25 +772,27 @@ TARGET="_top"
 >
      A.1.4. 	    What major companies or projects are currently using Bugzilla
+>
+	    What major companies or projects are currently using Bugzilla
 	    for bug-tracking?
 	  
       	    There are 
+	    There are dozens of major comapanies with public
 	    Bugzilla sites to track bugs in their products.  A few include:
@@ -868,30 +876,32 @@ BORDER="0"
 >
 	  
      	    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.
 	  
      A.1.5. 	    Who maintains Bugzilla?
+>
+	    Who maintains Bugzilla?
 	  
       	    Bugzilla maintenance has been in a state of flux recently.
+>
+	    Bugzilla maintenance has been in a state of flux recently.
 	    Please check 
      A.1.6. 	    How does Bugzilla stack up against other bug-tracking databases?
+>
+	    How does Bugzilla stack up against other bug-tracking databases?
 	  
       	    A year has gone by, and I 
+	    A year has gone by, and I still can't
 	    find any head-to-head comparisons of Bugzilla against
@@ -931,7 +943,7 @@ CLASS="ANSWER"
 	    flexibility, and superior ease-of-use.
 	  
      	    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
@@ -940,55 +952,59 @@ CLASS="ANSWER"
 >
      A.1.7. 	    How do I change my user name in Bugzilla?
+>
+	    How do I change my user name in Bugzilla?
 	  
       	    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.
 	  
      A.1.8. 	    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?
 	  
       	    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.
 	  
      	    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
@@ -1001,32 +1017,33 @@ TARGET="_top"
 >
      A.1.9. 	    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?
 	  
       Terry Weissman answers,
 	  
      	      You're not the only one. But 
	      You're not the only one. But I am not very interested. I'm not
 	      a real SQL or database person. I just wanted to make a useful tool,
@@ -1044,7 +1061,7 @@ CLASS="BLOCKQUOTE"
 >
 	  
      	    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:
 	  
      	      
	      
      	      
	      
      	      
	      Bugzilla 3.0: One of the primary stated goals
 	      is multiple database support.
@@ -1092,47 +1109,49 @@ TARGET="_top"
 >
      A.1.10. 	    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?
 	  
       	     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.
 	  
      	    Here's Terry Weissman's comment, for some historical context:
+>
	    Here's Terry Weissman's comment, for some historical context:
 	    
      		[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.
 	      
      		  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.
 		
      		  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.
 		
      2. Red Hat Bugzilla
      	
      
	
      	    
	    This section is no longer up-to-date.
 	    Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
@@ -1209,24 +1228,26 @@ VALIGN="TOP"
 >
       
      A.2.1. 	    What about Red Hat Bugzilla?
+>
+	    What about Red Hat Bugzilla?
 	  
       	    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.
@@ -1236,14 +1257,14 @@ CLASS="ANSWER"
 	    yourself?
 	  
      	    Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
+>
	    Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
 	    
      		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.
 	      
      A.2.2. 	    What are the primary benefits of Red Hat Bugzilla?
+>
+	    What are the primary benefits of Red Hat Bugzilla?
 	  
       	    
+	    Dave Lawrence:
 	    
      		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
@@ -1290,7 +1313,7 @@ CLASS="BLOCKQUOTE"
 		internal tools I am working on also look like Bugzilla.
 	      
      		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.
@@ -1298,7 +1321,7 @@ CLASS="BLOCKQUOTE"
 		is difficult sometimes to come by.
 	      
      		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:
@@ -1309,18 +1332,18 @@ CLASS="BLOCKQUOTE"
 TYPE="1"
 >
    108. 		    No enum types. All old enum types are now separate smaller tables.
+>
		    No enum types. All old enum types are now separate smaller tables.
 		  
    109. 		    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
 		  
    110. 		    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
@@ -1328,7 +1351,7 @@ TYPE="1"
 >
    111. 		    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
@@ -1338,14 +1361,14 @@ TYPE="1"
 >
    112. 		    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.
 		  
    113. 		    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
@@ -1355,7 +1378,7 @@ TYPE="1"
 >
    114. 		    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
@@ -1364,7 +1387,7 @@ TYPE="1"
 >
    115. 		    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
@@ -1374,7 +1397,7 @@ TYPE="1"
 >
      116. 		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
@@ -1388,29 +1411,31 @@ TYPE="1"
 >
      A.2.3. 	    What's the current status of Red Hat Bugzilla?
+>
+	    What's the current status of Red Hat Bugzilla?
 	  
       	    
      
+	    
      		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.
 	      
      Dave Lawrence:
 	    
      		     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
@@ -1473,7 +1498,7 @@ CLASS="BLOCKQUOTE"
 		thing going to help others that may need it.
 	      
      		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
@@ -1496,31 +1521,33 @@ CLASS="BLOCKQUOTE"
 >
      3. Loki Bugzilla (AKA Fenris)
      A.3.1. 	    What is Loki Bugzilla (Fenris)?
+>
+	    What is Loki Bugzilla (Fenris)?
 	  
       	    Loki Games has a customized version of Bugzilla available at
+>
+	    Loki Games has a customized version of Bugzilla available at
 	    
      4. Pointy-Haired-Boss Questions
      	
      
	
      	    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 :)
 	  
      A.4.1. 	    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?
 	  
       	    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.
 	  
      A.4.2. 	    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)?
 	  
       	    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.
 	  
      A.4.3. 	    Does Bugzilla allow the user to track multiple projects?
+>
+	    Does Bugzilla allow the user to track multiple projects?
 	  
       	    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
@@ -1643,48 +1676,52 @@ CLASS="ANSWER"
 >
      A.4.4. 	    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?
 	  
       	    Yes.
+>
+	    Yes.
 	  
      A.4.5. 	    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?
 	  
       	    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
@@ -1694,31 +1731,33 @@ CLASS="ANSWER"
 >
      A.4.6. 	    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?
 	  
       	    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.
 	  
      	    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.4.7. 	    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?
 	  
                   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 index.html
             to index.shtml.
           
                  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
             index.shtml:
 
      
       
      <!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
      
+<!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" -->
+
+
                    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.
             
                  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 api.cgi)
             that basically looks like:
@@ -1831,8 +1875,9 @@ WIDTH="100%"
 >
      #!/usr/bonsaitools/bin/perl -w
+CLASS="programlisting"
+>
+#!/usr/bonsaitools/bin/perl -w
 
 require 'globals.pl';
 
@@ -1840,14 +1885,16 @@ if ($::FORM{sub} eq 'PutFooter') {
     PutFooter();
 } else {
     die 'api.cgi was incorrectly called';
-}
      
             and then put this line in index.shtml.
 
      <!--#include virtual="api.cgi?sub=PutFooter"-->
      
+<!--#include virtual="api.cgi?sub=PutFooter"-->
+
+
       
                    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.4.8. 	    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. :)
 	  
       	    Yes.  Look at 
+	    Yes.  Look at 	    http://bugzilla.mozilla.org/reports.cgi
	    http://bugzilla.mozilla.org/reports.cgi for basic reporting
 	    facilities.
 	  
      	    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
@@ -1939,85 +1991,91 @@ TARGET="_top"
 	    interface with the database directly.
 	  
      	    Advanced Reporting is a Bugzilla 3.X proposed feature.
+>
	    Advanced Reporting is a Bugzilla 3.X proposed feature.
 	  
      A.4.9. 	    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?
 	  
       	    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.
 	  
      A.4.10. 	    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?
 	  
       	    Yes.
+>
+	    Yes.
 	  
      A.4.11. 	    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?
 	  
       	    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.
 	    
      		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
@@ -2049,26 +2107,28 @@ VALIGN="TOP"
 >
      A.4.12. 	     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.?
 	  
       	    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.
@@ -2076,38 +2136,40 @@ CLASS="ANSWER"
 >
      A.4.13. 	    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?
 	  
       	    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.
 	  
      	    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.
 	  
      	    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
@@ -2115,31 +2177,33 @@ CLASS="ANSWER"
 	    	    http://www.mozilla.org/quality/help/bugzilla-helper.html
	    http://www.mozilla.org/quality/help/bugzilla-helper.html
 	  
      A.4.14. 	    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?
 	  
       	    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.
@@ -2147,208 +2211,225 @@ CLASS="ANSWER"
 >
      A.4.15. 	    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?
 	  
       	    Yes.  No.  No.
+>
+	    Yes.  No.  No.
 	  
      A.4.16. 	    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?
 	  
       	    Yes.
+>
+	    Yes.
 	  
      A.4.17. 	    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?
 	  
       	    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.
 	  
      A.4.18. 	    Does Bugzilla have the ability to search by word, phrase, compound
+>
+	    Does Bugzilla have the ability to search by word, phrase, compound
 	    search?
 	  
       	    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.
 	  
      A.4.19. 	    Can the admin person establish separate group and individual user
+>
+	    Can the admin person establish separate group and individual user
 	    privileges?
 	  
       	    Yes.
+>
+	    Yes.
 	  
      A.4.20. 	     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?
 	  
       	    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.
 	  
      A.4.21. 	    Are there any backup features provided?
+>
+	    Are there any backup features provided?
 	  
       	    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 	    http://www.mysql.com/doc/B/a/Backup.html
	    http://www.mysql.com/doc/B/a/Backup.html
 	  
      A.4.22. 	    Can users be on the system while a backup is in progress?
+>
+	    Can users be on the system while a backup is in progress?
 	  
       	    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.
 	  
      A.4.23. 	    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
@@ -2356,21 +2437,22 @@ NAME="AEN2015"
 	  
       	    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".
 	  
      	    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.
 	  
      	    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.
@@ -2378,16 +2460,17 @@ CLASS="ANSWER"
 >
      A.4.24. 	    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,
@@ -2395,11 +2478,12 @@ NAME="AEN2022"
 	  
       	    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
@@ -2409,137 +2493,147 @@ CLASS="ANSWER"
 >
      A.4.25. 	    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?
 	  
       	    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.
 	  
      5. Bugzilla Installation
      A.5.1. 	    How do I download and install Bugzilla?
+>
+	    How do I download and install Bugzilla?
 	  
       	    Check 
+	    Check 	    http://www.mozilla.org/projects/bugzilla/
	    http://www.mozilla.org/projects/bugzilla/ for details.
 	    Once you download it, untar it, read the Bugzilla Guide.
 	  
      A.5.2. 	    How do I install Bugzilla on Windows NT?
+>
+	    How do I install Bugzilla on Windows NT?
 	  
       	    Installation on Windows NT has its own section in
+>
+	    Installation on Windows NT has its own section in
 	    "The Bugzilla Guide".
 	  
      A.5.3. 	    Is there an easy way to change the Bugzilla cookie name?
+>
+	    Is there an easy way to change the Bugzilla cookie name?
 	  
       	    At present, no.
+>
+	    At present, no.
 	  
      6. Bugzilla Security
      A.6.1. 	    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!)?
 	  
       	    Run mysql like this: "mysqld --skip-grant-tables".  Please remember 
+	    Run mysql like this: "mysqld --skip-grant-tables".  Please remember this
 	    makes mysql as secure as taping a $100 to the floor of a football stadium
 	    bathroom for safekeeping.
      A.6.2. 	    Are there any security problems with Bugzilla?
+>
+	    Are there any security problems with Bugzilla?
 	  
       	    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.
@@ -2574,26 +2670,28 @@ CLASS="ANSWER"
 >
      A.6.3. 	    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.
 	  
       	    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.
 	  
      7. Bugzilla Email
      A.7.1. 	    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?
 	  
       	    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.
 	  
      A.7.2. 	    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?
 	  
       	    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)".
 	  
      A.7.3. 	    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?
 	  
       	    Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+>
+	    Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
 	    You can find it at	      http://bugzilla.mozilla.org/show_bug.cgi?id=6679
	      http://bugzilla.mozilla.org/show_bug.cgi?id=6679. This
 	    patch is against an older version of Bugzilla, so you must apply
 	    the diffs manually.
@@ -2686,33 +2790,35 @@ TARGET="_top"
 >
      A.7.4. 	    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?
 	  
       	    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:
 	    
      		bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
+>
		bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
 	      
      
@@ -2723,53 +2829,57 @@ CLASS="BLOCKQUOTE"
 >
      A.7.5. 	    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?
 	  
       	    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.
 	  
      A.7.6. 	    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?
 	  
       	    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.
 	  
      	    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 "sendmailnow"
      A.7.7. 	     How come email never reaches me from bugzilla changes?
+>
+	     How come email never reaches me from bugzilla changes?
 	  
       	    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.
 	  
      	    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".
 	  
      8. Bugzilla Database
      A.8.1. 	    I've heard Bugzilla can be used with Oracle?
+>
+	    I've heard Bugzilla can be used with Oracle?
 	  
       	    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.
@@ -2841,25 +2955,27 @@ CLASS="ANSWER"
 >
      A.8.2. 	    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?
 	  
       	     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
@@ -2876,30 +2992,32 @@ CLASS="ANSWER"
 >
      A.8.3. 	    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?
 	  
       	    Run the 
+	    Run the "sanity check" utility
 	    (./sanitycheck.cgi in the
 	    Bugzilla_home directory) from your web browser to see! If
@@ -2921,24 +3039,26 @@ CLASS="FILENAME"
 >
      A.8.4. 	    I want to manually edit some entries in my database. How?
+>
+	    I want to manually edit some entries in my database. How?
 	  
       	     There is no facility in Bugzilla itself to do this. It's also generally
+>
+	     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
@@ -2948,49 +3068,53 @@ CLASS="ANSWER"
 >
      A.8.5. 	    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.
 	  
       	    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.
 	  
      A.8.6. 	    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.
 	  
       	    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
@@ -2999,61 +3123,65 @@ CLASS="ANSWER"
 >
      A.8.7. 	    How do I synchronize bug information among multiple different Bugzilla
+>
+	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
 	  
       	    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.
 	  
      	    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.
 	  
      	    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.
 	  
      A.8.8. 	    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"?
 	  
       	    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.
@@ -3061,35 +3189,37 @@ CLASS="ANSWER"
 >
      A.8.9. 	    How come even after I delete bugs, the long descriptions show up?
+>
+	    How come even after I delete bugs, the long descriptions show up?
 	  
       	    This should only happen with Bugzilla 2.14 if you are
+>
+	    This should only happen with Bugzilla 2.14 if you are
 	    using the "shadow database" feature, and your
 	    shadow database is out of sync.  Try running
 	    syncshadowdb
 	    -syncall to make sure your shadow
 	    database is in synch with your primary database.
@@ -3098,92 +3228,98 @@ CLASS="OPTION"
 >
      9. Bugzilla and Win32
      A.9.1. 	    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)?
 	  
       	    Remove Windows. Install Linux. Install Bugzilla.
+>
+	    Remove Windows. Install Linux. Install Bugzilla.
 	    The boss will never know the difference.
 	  
      A.9.2. 	    Is there a "Bundle::Bugzilla" equivalent for Win32?
+>
+	    Is there a "Bundle::Bugzilla" equivalent for Win32?
 	  
       	    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.
 	  
      A.9.3. 	    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?
 	  
       	    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.
 	  
      	    Microsoft has some advice on this matter, as well:
+>
	    Microsoft has some advice on this matter, as well:
 	    
      		"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
@@ -3198,29 +3334,32 @@ CLASS="BLOCKQUOTE"
 >
      A.9.4. 	    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?
 	  
       	    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.
 	    
        1. #!C:/perl/bin/perl had to be added to every perl file.
      
+CLASS="literallayout"
+>
      
+  1. #!C:/perl/bin/perl had to be added to every perl file.
      
   2. Converted to Net::SMTP to handle mail messages instead of
      
      /usr/bin/sendmail.
      
   3. The crypt function isn't available on Windows NT (at least none that I
      
@@ -3309,56 +3448,58 @@ A: Sure! Here ya go!
      
 >
      A.9.5. 	    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.
 	  
       	    Your modules may be outdated or inaccurate. Try:
+>
+	    Your modules may be outdated or inaccurate. Try:
 	    
      1. 		  Hitting http://www.activestate.com/ActivePerl
+>
		  Hitting http://www.activestate.com/ActivePerl
 		
      2. 		  Download ActivePerl
+>
		  Download ActivePerl
 		
      3. 		  Go to your prompt
+>
		  Go to your prompt
 		
      4. 		  Type 'ppm'
+>
		  Type 'ppm'
 		
      5. 		  
		  PPM> install DBI DBD-mysql GD
 		
        	      http://www.activestate.com/Packages/
	      http://www.activestate.com/Packages/
 	  
      10. Bugzilla Usage
      A.10.1. 	    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?
 	  
       	    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 	      http://bugzilla.mozilla.org/show_bug.cgi?id=16775
	      http://bugzilla.mozilla.org/show_bug.cgi?id=16775.  Some functionality
 	    is available in Bugzilla 2.12, and is available as "quicksearch.html"
 	  
      A.10.2. 	    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?
 	  
       	    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.
 	    
      		Add a "and accept bug" radio button
		Add a "and accept bug" radio button
      		"Accept" button automatically assigns to you
		"Accept" button automatically assigns to you
      A.10.3. 	    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?
 	  
       	    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.
 	  
      A.10.4. 	    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.
 	  
       	    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.
 	  
      A.10.5. 	    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?
 	  
       	    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.
 	  
      11. Bugzilla Hacking
      A.11.1. 	    What bugs are in Bugzilla right now?
+>
+	    What bugs are in Bugzilla right now?
 	  
       	    Try 
+	    Try 	    this link
	    this link to view current bugs or requests for
 	    enhancement for Bugzilla.
 	  
      	    You can view bugs marked for 2.16 release
+>
	    You can view bugs marked for 2.16 release
 	    	      Bugzilla Project Page
	      Bugzilla Project Page for details on how to
 	    check current sources out of CVS so you can have these
 	    bug fixes early!
@@ -3591,28 +3744,30 @@ TARGET="_top"
 >
      A.11.2. 	    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"?
 	  
       	    This is well-documented here: 
+	    This is well-documented here: 	    http://bugzilla.mozilla.org/show_bug.cgi?id=49862
	    http://bugzilla.mozilla.org/show_bug.cgi?id=49862.  Ultimately, it's as easy
 	    as adding the "---" priority field to your localconfig file in the appropriate area,
 	    re-running checksetup.pl, and then changing the default priority in your browser using
@@ -3623,20 +3778,21 @@ TARGET="_top"
 >
      A.11.3. 	    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?
 	  
       
    116. 		  Enter a bug into bugzilla.mozilla.org for the 
		  Enter a bug into bugzilla.mozilla.org for the "
    117. 		  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 current sources checked out of CVS),
@@ -3672,7 +3828,7 @@ TARGET="_top"
 >
    118. 		  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,
@@ -3682,14 +3838,14 @@ TARGET="_top"
 >
    119. 		  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.
 		
    120. 		  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 :)
 		
      121. Prev
      1.7. Feedback
            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
       <barnboy@trilobyte.net>.  Please send flames to
       <devnull@localhost
      Chapter 6. The Future of Bugzilla
      Bugzilla's Future.  Much of this is the present, now.
        Bugzilla's future is a constantly-changing thing, as various developers
+>
  Bugzilla's future is a constantly-changing thing, as various developers
   "scratch an itch"
          
                                     Bugzilla Blue Sky
      
+>
    

      
+                               Bugzilla Blue Sky
      
 
      
 Customisability
      
 
      
diff --git a/webtools/bugzilla/docs/html/geninstall.html b/webtools/bugzilla/docs/html/geninstall.html
index 18217ef486f..6bda5b1e870 100644
--- a/webtools/bugzilla/docs/html/geninstall.html
+++ b/webtools/bugzilla/docs/html/geninstall.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="Win32 Installation Notes"
 HREF="win32.html">
      3.5. Installation General Notes
      3.5.1. Modifying Your Running System
      	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.
       
      	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
 	
      	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.
       
      3.5.2. Upgrading From Previous Versions
      	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.
       
      	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.
       
      3.5.3. .htaccess files and security
      	To enhance the security of your Bugzilla installation,
+>
	To enhance the security of your Bugzilla installation,
 	Bugzilla  will generate
 	.htaccess files
 	which the Apache webserver can use to restrict  access to
 	the bugzilla data files. The checksetup script  will
 	generate the .htaccess files.
 	
 	
      	    If you are using an alternate provider of
+>
	    If you are using an alternate provider of
 	    webdot services for graphing
 	    (as described when viewing
 	    editparams.cgi in your web
 	    browser), you will need to change  the ip address in
 	    data/webdot/.htaccess to the ip
 	    address of the webdot server that  you are using. 
@@ -201,22 +201,81 @@ CLASS="FILENAME"
 	
       
      	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 .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
      3.5.4. mod_throttle and Security
      	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 mod_throttle which can limit
 	connections by ip-address. You may download this module at
@@ -251,7 +310,7 @@ TARGET="_top"
 >. Follow the instructions to install into your Apache install.  This module only functions with the Apache web server!. You may use the ThrottleClientIP command provided by this module  to accomplish this goal. See the  for more  information. 
      3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code
      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
 	
      	All this one-liner command does is search for all instances of
+>
	All this one-liner command does is search for all instances of
 	"Content-type: text/html"
      3.5.6. UNIX Installation Instructions History
      	This document was originally adapted from the Bonsai
+>
	This document was originally adapted from the Bonsai
 	installation instructions by Terry Weissman
 	<terry@mozilla.org>.
       
      	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  ).
       
      	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.
       
      	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.
       
      	Comments from people using this Guide for the first time are
+>
	Comments from people using this Guide for the first time are
 	particularly welcome.
       
      PREAMBLE
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      0. PREAMBLE
      The purpose of this License is to make a manual, textbook,
+    or other written document "free" in the sense of freedom: to
+    assure everyone the effective freedom to copy and redistribute it,
+    with or without modifying it, either commercially or
+    noncommercially.  Secondarily, this License preserves for the
+    author and publisher a way to get credit for their work, while not
+    being considered responsible for modifications made by
+    others.
      This License is a kind of "copyleft", which means that
+    derivative works of the document must themselves be free in the
+    same sense.  It complements the GNU General Public License, which
+    is a copyleft license designed for free software.
      We have designed this License in order to use it for manuals
+    for free software, because free software needs free documentation:
+    a free program should come with manuals providing the same
+    freedoms that the software does.  But this License is not limited
+    to software manuals; it can be used for any textual work,
+    regardless of subject matter or whether it is published as a
+    printed book.  We recommend this License principally for works
+    whose purpose is instruction or reference.
      PrevHomeNext
      GNU Free Documentation LicenseUpAPPLICABILITY AND DEFINITIONS
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-1.html b/webtools/bugzilla/docs/html/gfdl-1.html
new file mode 100644
index 00000000000..0635a14b9c9
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-1.html
@@ -0,0 +1,200 @@
+APPLICABILITY AND DEFINITIONS
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      1. APPLICABILITY AND DEFINITIONS
      This License applies to any manual or other work that
+    contains a notice placed by the copyright holder saying it can be
+    distributed under the terms of this License.  The "Document",
+    below, refers to any such manual or work.  Any member of the
+    public is a licensee, and is addressed as "you".
      A "Modified Version" of the Document means any work
+    containing the Document or a portion of it, either copied
+    verbatim, or with modifications and/or translated into another
+    language.
      A "Secondary Section" is a named appendix or a front-matter
+    section of the Document that deals exclusively with the
+    relationship of the publishers or authors of the Document to the
+    Document's overall subject (or to related matters) and contains
+    nothing that could fall directly within that overall subject.
+    (For example, if the Document is in part a textbook of
+    mathematics, a Secondary Section may not explain any mathematics.)
+    The relationship could be a matter of historical connection with
+    the subject or with related matters, or of legal, commercial,
+    philosophical, ethical or political position regarding
+    them.
      The "Invariant Sections" are certain Secondary Sections
+    whose titles are designated, as being those of Invariant Sections,
+    in the notice that says that the Document is released under this
+    License.
      The "Cover Texts" are certain short passages of text that
+    are listed, as Front-Cover Texts or Back-Cover Texts, in the
+    notice that says that the Document is released under this
+    License.
      A "Transparent" copy of the Document means a
+    machine-readable copy, represented in a format whose specification
+    is available to the general public, whose contents can be viewed
+    and edited directly and straightforwardly with generic text
+    editors or (for images composed of pixels) generic paint programs
+    or (for drawings) some widely available drawing editor, and that
+    is suitable for input to text formatters or for automatic
+    translation to a variety of formats suitable for input to text
+    formatters.  A copy made in an otherwise Transparent file format
+    whose markup has been designed to thwart or discourage subsequent
+    modification by readers is not Transparent.  A copy that is not
+    "Transparent" is called "Opaque".
      Examples of suitable formats for Transparent copies include
+    plain ASCII without markup, Texinfo input format, LaTeX input
+    format, SGML or XML using a publicly available DTD, and
+    standard-conforming simple HTML designed for human modification.
+    Opaque formats include PostScript, PDF, proprietary formats that
+    can be read and edited only by proprietary word processors, SGML
+    or XML for which the DTD and/or processing tools are not generally
+    available, and the machine-generated HTML produced by some word
+    processors for output purposes only.
      The "Title Page" means, for a printed book, the title page
+    itself, plus such following pages as are needed to hold, legibly,
+    the material this License requires to appear in the title page.
+    For works in formats which do not have any title page as such,
+    "Title Page" means the text near the most prominent appearance of
+    the work's title, preceding the beginning of the body of the
+    text.
      PrevHomeNext
      PREAMBLEUpVERBATIM COPYING
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-10.html b/webtools/bugzilla/docs/html/gfdl-10.html
new file mode 100644
index 00000000000..8d13637bd6b
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-10.html
@@ -0,0 +1,156 @@
+FUTURE REVISIONS OF THIS LICENSE
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      10. FUTURE REVISIONS OF THIS LICENSE
      The Free Software Foundation may publish new, revised
+    versions of the GNU Free Documentation License from time to time.
+    Such new versions will be similar in spirit to the present
+    version, but may differ in detail to address new problems or
+    concerns.  See http://www.gnu.org/copyleft/.
      Each version of the License is given a distinguishing
+    version number.  If the Document specifies that a particular
+    numbered version of this License "or any later version" applies to
+    it, you have the option of following the terms and conditions
+    either of that specified version or of any later version that has
+    been published (not as a draft) by the Free Software Foundation.
+    If the Document does not specify a version number of this License,
+    you may choose any version ever published (not as a draft) by the
+    Free Software Foundation.
      PrevHomeNext
      TERMINATIONUpHow to use this License for your documents
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-2.html b/webtools/bugzilla/docs/html/gfdl-2.html
new file mode 100644
index 00000000000..1b94bbdd3b9
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-2.html
@@ -0,0 +1,150 @@
+VERBATIM COPYING
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      2. VERBATIM COPYING
      You may copy and distribute the Document in any medium,
+    either commercially or noncommercially, provided that this
+    License, the copyright notices, and the license notice saying this
+    License applies to the Document are reproduced in all copies, and
+    that you add no other conditions whatsoever to those of this
+    License.  You may not use technical measures to obstruct or
+    control the reading or further copying of the copies you make or
+    distribute.  However, you may accept compensation in exchange for
+    copies.  If you distribute a large enough number of copies you
+    must also follow the conditions in section 3.
      You may also lend copies, under the same conditions stated
+    above, and you may publicly display copies.
      PrevHomeNext
      APPLICABILITY AND DEFINITIONSUpCOPYING IN QUANTITY
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-3.html b/webtools/bugzilla/docs/html/gfdl-3.html
new file mode 100644
index 00000000000..4342ac917e3
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-3.html
@@ -0,0 +1,174 @@
+COPYING IN QUANTITY
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      3. COPYING IN QUANTITY
      If you publish printed copies of the Document numbering more
+    than 100, and the Document's license notice requires Cover Texts,
+    you must enclose the copies in covers that carry, clearly and
+    legibly, all these Cover Texts: Front-Cover Texts on the front
+    cover, and Back-Cover Texts on the back cover.  Both covers must
+    also clearly and legibly identify you as the publisher of these
+    copies.  The front cover must present the full title with all
+    words of the title equally prominent and visible.  You may add
+    other material on the covers in addition.  Copying with changes
+    limited to the covers, as long as they preserve the title of the
+    Document and satisfy these conditions, can be treated as verbatim
+    copying in other respects.
      If the required texts for either cover are too voluminous to
+    fit legibly, you should put the first ones listed (as many as fit
+    reasonably) on the actual cover, and continue the rest onto
+    adjacent pages.
      If you publish or distribute Opaque copies of the Document
+    numbering more than 100, you must either include a
+    machine-readable Transparent copy along with each Opaque copy, or
+    state in or with each Opaque copy a publicly-accessible
+    computer-network location containing a complete Transparent copy
+    of the Document, free of added material, which the general
+    network-using public has access to download anonymously at no
+    charge using public-standard network protocols.  If you use the
+    latter option, you must take reasonably prudent steps, when you
+    begin distribution of Opaque copies in quantity, to ensure that
+    this Transparent copy will remain thus accessible at the stated
+    location until at least one year after the last time you
+    distribute an Opaque copy (directly or through your agents or
+    retailers) of that edition to the public.
      It is requested, but not required, that you contact the
+    authors of the Document well before redistributing any large
+    number of copies, to give them a chance to provide you with an
+    updated version of the Document.
      PrevHomeNext
      VERBATIM COPYINGUpMODIFICATIONS
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-4.html b/webtools/bugzilla/docs/html/gfdl-4.html
new file mode 100644
index 00000000000..ae8ef9b977d
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-4.html
@@ -0,0 +1,280 @@
+MODIFICATIONS
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      4. MODIFICATIONS
      You may copy and distribute a Modified Version of the
+    Document under the conditions of sections 2 and 3 above, provided
+    that you release the Modified Version under precisely this
+    License, with the Modified Version filling the role of the
+    Document, thus licensing distribution and modification of the
+    Modified Version to whoever possesses a copy of it.  In addition,
+    you must do these things in the Modified Version:
      1. 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.
      2. 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).
      3. State on the Title page
+      the name of the publisher of the Modified Version, as the
+      publisher.
      4. Preserve all the
+      copyright notices of the Document.
      5. Add an appropriate
+      copyright notice for your modifications adjacent to the other
+      copyright notices.
      6. 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.
      7. Preserve in that license
+      notice the full lists of Invariant Sections and required Cover
+      Texts given in the Document's license notice.
      8. Include an unaltered
+      copy of this License.
      9. 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.
      10. 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.
      11. 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.
      12. 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.
      13. Delete any section
+      entitled "Endorsements".  Such a section may not be included in
+      the Modified Version.
      14. Do not retitle any
+      existing section as "Endorsements" or to conflict in title with
+      any Invariant Section.
      If the Modified Version includes new front-matter sections
+    or appendices that qualify as Secondary Sections and contain no
+    material copied from the Document, you may at your option
+    designate some or all of these sections as invariant.  To do this,
+    add their titles to the list of Invariant Sections in the Modified
+    Version's license notice.  These titles must be distinct from any
+    other section titles.
      You may add a section entitled "Endorsements", provided it
+    contains nothing but endorsements of your Modified Version by
+    various parties--for example, statements of peer review or that
+    the text has been approved by an organization as the authoritative
+    definition of a standard.
      You may add a passage of up to five words as a Front-Cover
+    Text, and a passage of up to 25 words as a Back-Cover Text, to the
+    end of the list of Cover Texts in the Modified Version.  Only one
+    passage of Front-Cover Text and one of Back-Cover Text may be
+    added by (or through arrangements made by) any one entity.  If the
+    Document already includes a cover text for the same cover,
+    previously added by you or by arrangement made by the same entity
+    you are acting on behalf of, you may not add another; but you may
+    replace the old one, on explicit permission from the previous
+    publisher that added the old one.
      The author(s) and publisher(s) of the Document do not by
+    this License give permission to use their names for publicity for
+    or to assert or imply endorsement of any Modified Version.
      PrevHomeNext
      COPYING IN QUANTITYUpCOMBINING DOCUMENTS
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-5.html b/webtools/bugzilla/docs/html/gfdl-5.html
new file mode 100644
index 00000000000..b28398c8cd7
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-5.html
@@ -0,0 +1,159 @@
+COMBINING DOCUMENTS
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      5. COMBINING DOCUMENTS
      You may combine the Document with other documents released
+    under this License, under the terms defined in section 4 above for
+    modified versions, provided that you include in the combination
+    all of the Invariant Sections of all of the original documents,
+    unmodified, and list them all as Invariant Sections of your
+    combined work in its license notice.
      The combined work need only contain one copy of this
+    License, and multiple identical Invariant Sections may be replaced
+    with a single copy.  If there are multiple Invariant Sections with
+    the same name but different contents, make the title of each such
+    section unique by adding at the end of it, in parentheses, the
+    name of the original author or publisher of that section if known,
+    or else a unique number.  Make the same adjustment to the section
+    titles in the list of Invariant Sections in the license notice of
+    the combined work.
      In the combination, you must combine any sections entitled
+    "History" in the various original documents, forming one section
+    entitled "History"; likewise combine any sections entitled
+    "Acknowledgements", and any sections entitled "Dedications".  You
+    must delete all sections entitled "Endorsements."
      PrevHomeNext
      MODIFICATIONSUpCOLLECTIONS OF DOCUMENTS
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-6.html b/webtools/bugzilla/docs/html/gfdl-6.html
new file mode 100644
index 00000000000..31762e3859e
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-6.html
@@ -0,0 +1,149 @@
+COLLECTIONS OF DOCUMENTS
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      6. COLLECTIONS OF DOCUMENTS
      You may make a collection consisting of the Document and
+    other documents released under this License, and replace the
+    individual copies of this License in the various documents with a
+    single copy that is included in the collection, provided that you
+    follow the rules of this License for verbatim copying of each of
+    the documents in all other respects.
      You may extract a single document from such a collection,
+    and distribute it individually under this License, provided you
+    insert a copy of this License into the extracted document, and
+    follow this License in all other respects regarding verbatim
+    copying of that document.
      PrevHomeNext
      COMBINING DOCUMENTSUpAGGREGATION WITH INDEPENDENT WORKS
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-7.html b/webtools/bugzilla/docs/html/gfdl-7.html
new file mode 100644
index 00000000000..e04b3c01b24
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-7.html
@@ -0,0 +1,153 @@
+AGGREGATION WITH INDEPENDENT WORKS
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      7. AGGREGATION WITH INDEPENDENT WORKS
      A compilation of the Document or its derivatives with other
+    separate and independent documents or works, in or on a volume of
+    a storage or distribution medium, does not as a whole count as a
+    Modified Version of the Document, provided no compilation
+    copyright is claimed for the compilation.  Such a compilation is
+    called an "aggregate", and this License does not apply to the
+    other self-contained works thus compiled with the Document, on
+    account of their being thus compiled, if they are not themselves
+    derivative works of the Document.
      If the Cover Text requirement of section 3 is applicable to
+    these copies of the Document, then if the Document is less than
+    one quarter of the entire aggregate, the Document's Cover Texts
+    may be placed on covers that surround only the Document within the
+    aggregate.  Otherwise they must appear on covers around the whole
+    aggregate.
      PrevHomeNext
      COLLECTIONS OF DOCUMENTSUpTRANSLATION
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-8.html b/webtools/bugzilla/docs/html/gfdl-8.html
new file mode 100644
index 00000000000..d49ec3a1dc6
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-8.html
@@ -0,0 +1,148 @@
+TRANSLATION
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      8. TRANSLATION
      Translation is considered a kind of modification, so you may
+    distribute translations of the Document under the terms of section
+    4.  Replacing Invariant Sections with translations requires
+    special permission from their copyright holders, but you may
+    include translations of some or all Invariant Sections in addition
+    to the original versions of these Invariant Sections.  You may
+    include a translation of this License provided that you also
+    include the original English version of this License.  In case of
+    a disagreement between the translation and the original English
+    version of this License, the original English version will
+    prevail.
      PrevHomeNext
      AGGREGATION WITH INDEPENDENT WORKSUpTERMINATION
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-9.html b/webtools/bugzilla/docs/html/gfdl-9.html
new file mode 100644
index 00000000000..22719a21714
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-9.html
@@ -0,0 +1,145 @@
+TERMINATION
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      9. TERMINATION
      You may not copy, modify, sublicense, or distribute the
+    Document except as expressly provided for under this License.  Any
+    other attempt to copy, modify, sublicense or distribute the
+    Document is void, and will automatically terminate your rights
+    under this License.  However, parties who have received copies, or
+    rights, from you under this License will not have their licenses
+    terminated so long as such parties remain in full
+    compliance.
      PrevHomeNext
      TRANSLATIONUpFUTURE REVISIONS OF THIS LICENSE
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl-howto.html b/webtools/bugzilla/docs/html/gfdl-howto.html
new file mode 100644
index 00000000000..0eb0aa3f4ff
--- /dev/null
+++ b/webtools/bugzilla/docs/html/gfdl-howto.html
@@ -0,0 +1,167 @@
+How to use this License for your documents
      The Bugzilla Guide
      PrevAppendix E. GNU Free Documentation LicenseNext
      How to use this License for your documents
      To use this License in a document you have written, include
+    a copy of the License in the document and put the following
+    copyright and license notices just after the title page:
      
      Copyright (c)  YEAR  YOUR NAME.
+      Permission is granted to copy, distribute and/or modify this document
+      under the terms of the GNU Free Documentation License, Version 1.1
+      or any later version published by the Free Software Foundation;
+      with the Invariant Sections being LIST THEIR TITLES, with the
+      Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+      A copy of the license is included in the section entitled "GNU
+      Free Documentation License".
+
      If you have no Invariant Sections, write "with no Invariant
+    Sections" instead of saying which ones are invariant.  If you have
+    no Front-Cover Texts, write "no Front-Cover Texts" instead of
+    "Front-Cover Texts being LIST"; likewise for Back-Cover
+    Texts.
      If your document contains nontrivial examples of program
+    code, we recommend releasing these examples in parallel under your
+    choice of free software license, such as the GNU General Public
+    License, to permit their use in free software.
      PrevHomeNext
      FUTURE REVISIONS OF THIS LICENSEUpGlossary
      
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/gfdl.html b/webtools/bugzilla/docs/html/gfdl.html
index 376123e1f12..38f7af8856a 100644
--- a/webtools/bugzilla/docs/html/gfdl.html
+++ b/webtools/bugzilla/docs/html/gfdl.html
@@ -14,9 +14,9 @@ TITLE="Hacking Bugzilla"
 HREF="bzhacking.html">Next
      Glossary
      0-9, high ascii
      	    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 .htaccess 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
 	    localconfig file contains the
 	    password to your database.  If this information were
@@ -100,11 +100,11 @@ CLASS="FILENAME"
 >
      A
      In this context, Apache is the web server most
 	    commonly used for serving up
 	    Bugzilla pages.  Contrary to
 	    popular belief, the apache web server has nothing to do
@@ -128,18 +128,18 @@ CLASS="QUOTE"
 >"a patchy" version of the original
 	    NCSA world-wide-web server.
      B
      	    A 
	    A "Bug" in Bugzilla refers to an issue
@@ -171,7 +171,7 @@ CLASS="QUOTE"
 >
      	    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.
@@ -201,31 +201,31 @@ CLASS="QUOTE"
 >
      	    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.
 	  
      Component
      	    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
@@ -234,10 +234,10 @@ NAME="GLOSS_COMPONENT"
 >
      CPAN
      CPAN stands for the
 	    .  CPAN
 	    maintains a large number of extremely useful
 	    Perl modules.  By themselves, Perl
 	    modules generally do nothing, but when used as part of a
@@ -264,11 +264,11 @@ CLASS="GLOSSTERM"
 >
      D
      mysqld, the
 	    MySQL server, and apache, a web
 	    server, are generally run as daemons.
      Products and
 	    Components in the
 	    Bugzilla database.
      M
      mysqld is the name of the
 	    daemon for the MySQL database.  In
 	    general, it is invoked automatically through the use of
@@ -380,11 +380,11 @@ CLASS="GLOSSTERM"
 >
      P
      Bugzilla is
 	    maintained in Perl.
      S
      SGML
      SGML stands for SGML has withstood the test of time as
 	    a robust, powerful language.
 	    XML is the
@@ -582,20 +582,20 @@ CLASS="QUOTE"
 >"baby brother" of SGML; any valid
 	    XML document it, by definition, a valid
 	    SGML document.  The document you are
 	    reading is written and maintained in
 	    SGML, and is also valid
 	    XML if you modify the Document Type
 	    Definition.
      T
      Target Milestone
      	    Target Milestones are Product goals.  They are
+>
	    Target Milestones are Product goals.  They are
 	    configurable on a per-Product basis.  Most software
 	    development houses have a concept of
 	    
      C.3. MySQL Permissions & Grant Tables
      	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.
@@ -117,8 +117,9 @@ VALIGN="TOP"
 >
      From matt_barnson@singletrac.com Wed Jul  7 09:00:07 1999
      
+CLASS="literallayout"
+>
      
+From matt_barnson@singletrac.com Wed Jul  7 09:00:07 1999
      
 Date: Mon, 1 Mar 1999 21:37:04 -0700 
      
 From: Matthew Barnson matt_barnson@singletrac.com
      
 To: keystone-users@homeport.org
      
diff --git a/webtools/bugzilla/docs/html/how.html b/webtools/bugzilla/docs/html/how.html
index cad7486432c..130674d1f21 100644
--- a/webtools/bugzilla/docs/html/how.html
+++ b/webtools/bugzilla/docs/html/how.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="Where can I find my user preferences?"
 HREF="init4me.html">
      2.3. How do I use Bugzilla?
            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.
@@ -107,19 +107,19 @@ VALIGN="TOP"
       software.
     
            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,
       	landfill.tequilarista.org
	landfill.tequilarista.org.
       
      	  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 
      2.3.1. Create a Bugzilla Account
      	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
@@ -184,19 +184,19 @@ TARGET="_top"
 TYPE="1"
 >
    121. 	    Click the "Open a new Bugzilla account" link.
+>
	    Click the "Open a new Bugzilla account" link.
 	  
    122. 	    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.
 	  
    123. 	    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
@@ -206,7 +206,7 @@ TYPE="1"
 >
    124. 	    Click the 
	    Click the "Log In" link in the yellow area at
@@ -224,12 +224,12 @@ CLASS="QUOTE"
 >"Login".
 	    
      125. 		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 "E-mail address"
 	    
      		Many modern browsers include an
+>
		Many modern browsers include an
 		"Auto-Complete"
      	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
@@ -319,46 +319,46 @@ CLASS="QUOTE"
       
      2.3.2. The Bugzilla Query Page
      	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.
       
      	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 quicksearch.html available to
 	use and simplify your searches.  There is also a helper for
 	the query interface, called
 	queryhelp.cgi.  Landfill 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,
+>
	At this point, let's visit the query page.
 		bugzilla.mozilla.org, to see a more fleshed-out query page.
+>
	landfill.tequilarista.org/bugzilla-tip/query.cgi
       
      	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
@@ -368,7 +368,7 @@ CLASS="QUOTE"
 > underlined.  Select it.
       
      	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
@@ -379,7 +379,7 @@ CLASS="QUOTE"
 	button in your browser.
       
      	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
@@ -391,7 +391,7 @@ CLASS="QUOTE"
 TYPE="1"
 >
    125. 	    Ensure you are back on the 
	    Ensure you are back on the "Bugzilla Query
 	      Page"
      	    Basically, selecting 
	    Basically, selecting anything on the
 	    query page narrows your search down.  Leaving stuff
@@ -416,7 +416,7 @@ CLASS="QUOTE"
 >
    126. 	    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
@@ -424,12 +424,12 @@ CLASS="QUOTE"
 	    put my email address in there, and see what happens.
 	  
      	    Type "barnboy@trilobyte.net" in the top Email text box.
+>
	    Type "barnboy@trilobyte.net" in the top Email text box.
 	  
    127. 	    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
@@ -443,13 +443,13 @@ CLASS="QUOTE"
 >
    128. 	    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.
 	    
      Example 2-1. Some Famous Software Versions
      		  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.
@@ -475,7 +475,7 @@ NAME="AEN309"
 		  ME(Millenium Edition)(r). 
 		
      		  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,
@@ -492,7 +492,7 @@ NAME="AEN309"
 		  version than 1.1.1.
 		
      		  In general, a "Version" in Bugzilla should refer to
+>
		  In general, a "Version" in Bugzilla should refer to
 		  released products, not products
@@ -507,13 +507,13 @@ NAME="AEN309"
 >
 	  
      	    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.
 	    
      Example 2-2. Mozilla's Bugzilla Components
      		  Mozilla's "Bugzilla" Product is composed of several pieces (Components):
+>
		  Mozilla's "Bugzilla" Product is composed of several pieces (Components):
 		  
      129. ,
                       Administration of a bugzilla installation, including 
                       editcomponents.cgi,
                       editgroups.cgi, 
                       editkeywords.cgi, 
                       editparams.cgi,
                       editproducts.cgi,
                       editusers.cgi,
                       editversions.cgi, and
                       sanitycheck.cgi.
                     ,
                       Creating, changing, and viewing bugs.
                       enter_bug.cgi,
                       post_bug.cgi,
                       show_bug.cgi and
                       process_bug.cgi.
                     ,
                       The bugzilla documentation, including anything in the
                       docs/ directory and The Bugzilla Guide
                       (This document :)
@@ -628,7 +628,7 @@ CLASS="FILENAME"
 >,
                       Anything to do with email sent by Bugzilla.
                       processmail
                     ,
                       The installation process of Bugzilla. This includes
                       checksetup.pl and whatever else it evolves into.
                     ,
                       Anything to do with searching for bugs and viewing the buglists.
                       query.cgi and
                       buglist.cgi
                     ,
                       Getting reports from Bugzilla.
                       reports.cgi and
                       duplicates.cgi
                     ,
                       Anything about managing a user account from the user's perspective.
                       userprefs.cgi, saved queries, creating accounts,
                       changing passwords, logging in, etc. 
@@ -712,7 +712,7 @@ CLASS="FILENAME"
 >
 	  
      	    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
@@ -727,7 +727,7 @@ CLASS="FILENAME"
 	    of reach by the time the important day arrives.
 	  
      	    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".
@@ -735,19 +735,19 @@ CLASS="FILENAME"
 >
    129. 	    OK, now let's select the "Bugzilla" component from its scrollbox.
+>
	    OK, now let's select the "Bugzilla" component from its scrollbox.
 	  
    130. 	    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!
 	  
    131. 	    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
@@ -759,7 +759,7 @@ CLASS="FILENAME"
 >
      132. 	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
@@ -768,7 +768,7 @@ CLASS="FILENAME"
 	this is a tremendous timesaver.
       
      	A couple more interesting things about the Bug List page:
+>
	A couple more interesting things about the Bug List page:
 	
      
       
      	  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 
      2.3.3.1. Writing a Great Bug Report
      	  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
@@ -908,7 +908,7 @@ TARGET="_top"
 >.  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.
 	
      	  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 .
 	
      	  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!
 	
    132. 	      Go back to 
	      Go back to  http://landfill.tequilarista.org/bugzilla-tip/
    133. 	      Select the  
	      Select the   Enter a new bug report
    134. 	      Select a product.
+>
	      Select a product.
 	    
    135. 	      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,
@@ -959,12 +959,12 @@ TARGET="_top"
 >
    136. 	      Select a Component in the scrollbox.
+>
	      Select a Component in the scrollbox.
 	    
    137. 	      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!
@@ -972,7 +972,7 @@ TARGET="_top"
 >
    138. 	      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.
@@ -980,33 +980,33 @@ TARGET="_top"
 >
    139. 	      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".
 	    
    140. 	      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.
 	    
      141. 	  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.
 	
      2.3.3.2. Managing your Bug Reports
      	  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.
@@ -1017,7 +1017,7 @@ NAME="BUG_MANAGE"
 TYPE="1"
 >
    141. 	      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,
@@ -1029,7 +1029,7 @@ TYPE="1"
 >
    142. 	      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
@@ -1038,40 +1038,40 @@ TYPE="1"
 >
      143. 	  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.
 	
      	  But I'll give a few last hints!
+>
	  But I'll give a few last hints!
 	
      	  There is a 
	  There is a CLUE on the Query page that will teach you more how to use the form.
 	
      	  If you click the hyperlink on the 
	  If you click the hyperlink on the Component box of the Query page, you will be presented a form that will describe what all the components are.
 	
      	  Possibly the most powerful feature of the Query page is the
+>
	  Possibly the most powerful feature of the Query page is the
 	  Boolean Chart 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.
 	
      	  Finally, you can build some nifty  
	  Finally, you can build some nifty  Reports 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.
diff --git a/webtools/bugzilla/docs/html/index.html b/webtools/bugzilla/docs/html/index.html
index 36e2e849a12..5d2cc364547 100644
--- a/webtools/bugzilla/docs/html/index.html
+++ b/webtools/bugzilla/docs/html/index.html
@@ -28,7 +28,7 @@ CONTENT="Mozilla">
      The Bugzilla Guide
      Matthew P. Barnson
      barnboy@trilobyte.net
      Zach Lipton
      zach AT zachlipton DOT com

      	This is the documentation for Bugzilla, the Mozilla
+>
	This is the documentation for Bugzilla, the Mozilla
 	bug-tracking system.
       
      	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.
       
      	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!
@@ -304,29 +304,29 @@ HREF="how.html"
 >
      2.3.1. Create a Bugzilla Account
      2.3.2. The Bugzilla Query Page
      2.3.3. Creating and Managing Bug Reports
      2.3.3.1. Writing a Great Bug Report
      2.3.3.2. Managing your Bug Reports
      2.4.1. Account Settings
      2.4.2. Email Settings
      2.4.2.1. Email Notification
      2.4.2.2. New Email Technology
      2.4.2.3. "Watching" Users
      2.4.3. Page Footer
      2.4.4. Permissions
      3.2.3. Installing MySQL Database
      3.2.4. Perl (5.004 or greater)
      3.2.15. Tweaking localconfig
      3.5.3. .htaccess files and security
      3.5.4. mod_throttle and Security
      3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code
      3.5.6. UNIX Installation Instructions History
      3.6.1. Win32 Installation: Step-by-step
      3.6.2. Additional Windows Tips
      3.6.3. Bugzilla LDAP Integration
      4.2.1. Creating the Default User
      4.2.2. Managing Other Users
      4.2.2.1. Logging In
      4.2.2.2. Creating new users
      4.2.2.3. Disabling Users
      4.2.2.4. Modifying Users
      4.3.1. Products
      4.3.2. Components
      4.3.3. Versions
      4.3.4. Milestones
      4.3.5. Voting
      4.3.6. Groups and Group Security
      7.2. Loki Bugzilla (Fenris)
      7.3. Issuezilla
      7.4. Scarab
      7.5. Perforce SCM
      7.6. SourceForge
      C.2.1. Bugzilla Database Basics
      C.2.1.1. Bugzilla Database Tables
      D.1. Apache mod_rewrite magic
      D.5.1. Things that have caused problems and should be avoided
      D.5.2. Coding Style for Bugzilla
      0. PREAMBLE
      1. APPLICABILITY AND DEFINITIONS
      2. VERBATIM COPYING
      3. COPYING IN QUANTITY
      4. MODIFICATIONS
      5. COMBINING DOCUMENTS
      6. COLLECTIONS OF DOCUMENTS
      7. AGGREGATION WITH INDEPENDENT WORKS
      8. TRANSLATION
      9. TERMINATION
      10. FUTURE REVISIONS OF THIS LICENSE
      How to use this License for your documents
      3-3. Installing ActivePerl ppd Modules on Microsoft Windows
      3-4. Removing encrypt() for Windows NT Bugzilla version
 	      2.12 or earlier
      4-1. Creating some Components
      4-2. Common Use of Versions
      4-3. A Different Use of Versions
      4-4. Using SortKey with Target Milestone
      4-5. When to Use Group Security
      4-6. Creating a New Group
      4-7. Bugzilla Groups
      D-1. Using Setperl to set your perl path
      1. A Sample Product
            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 .
     
      2.4.1. Account Settings
      	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
 	
      2.4.2. Email Settings
      2.4.2.1. Email Notification
      	  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
 	  
      2.4.2.2. New Email Technology
      	    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,
@@ -229,13 +229,13 @@ VALIGN="TOP"
 >
      	  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.
 	
      	  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
@@ -243,19 +243,19 @@ VALIGN="TOP"
 	
      2.4.2.3. "Watching" Users
      	    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,
@@ -282,7 +282,7 @@ VALIGN="TOP"
 >
      	  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
@@ -294,19 +294,19 @@ VALIGN="TOP"
 >
      2.4.3. Page Footer
      	  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
@@ -334,7 +334,7 @@ VALIGN="TOP"
 >
      	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
@@ -342,11 +342,11 @@ VALIGN="TOP"
 	is an excellent way to impress your boss...
       
      2.4.4. Permissions
      	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.
diff --git a/webtools/bugzilla/docs/html/installation.html b/webtools/bugzilla/docs/html/installation.html
index 5725bb8b836..9e2aff79249 100644
--- a/webtools/bugzilla/docs/html/installation.html
+++ b/webtools/bugzilla/docs/html/installation.html
@@ -16,7 +16,7 @@ REL="NEXT"
 TITLE="ERRATA"
 HREF="errata.html">
      Chapter 3. Installation
            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
diff --git a/webtools/bugzilla/docs/html/integration.html b/webtools/bugzilla/docs/html/integration.html
index 69648fdf2eb..76d3f39af04 100644
--- a/webtools/bugzilla/docs/html/integration.html
+++ b/webtools/bugzilla/docs/html/integration.html
@@ -16,7 +16,7 @@ REL="NEXT"
 TITLE="Bonsai"
 HREF="bonsai.html">
      Chapter 5. Integrating Bugzilla with Third-Party Tools
      1.4. New Versions
            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.
     
            This document can be found in the following places:
+>
      This document can be found in the following places:
     
            
      
      
      3.3. Mac OS X Installation Notes
            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.
     
            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/>.
     
            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:
       fink install gd
     
            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.
     
            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
@@ -111,15 +111,15 @@ CLASS="COMMAND"
       :-)
     
            Instead of typing 
      Instead of typing "install GD" at the
       cpan> prompt, type look
 	GD.  This should go through the motions of
@@ -127,13 +127,13 @@ CLASS="COMMAND"
       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 patch <
 	patchfile:
     
            
      
      
      	
+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 @@
@@ -176,7 +177,7 @@ CLASS="PROGRAMLISTING"
 >
     
            Then, run these commands to finish the installation of the perl module:
+>
      Then, run these commands to finish the installation of the perl module:
       
            Happy Hacking!
+>
      Happy Hacking!
     
      Appendix D. Useful Patches and Utilities for Bugzilla
      D.1. Apache mod_rewrite magic
      D.5.1. Things that have caused problems and should be avoided
      D.5.2. Coding Style for Bugzilla
      Apache mod_rewrite magic
      4.1. Post-Installation Checklist
            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.
     
      1. 	  Bring up 
	  Bring up editparams.cgi in your web
 	  browser.  This should be available as the 
        	  Set 
	  Set "maintainer" to 
        	  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
 	  
        	  Set "usebuggroups" to "on" 
	  Set "usebuggroups" to "on" only if you
 	  may wish to restrict access to products. I suggest leaving
@@ -160,7 +160,7 @@ CLASS="QUOTE"
 >
      2. 	  
	  "usebuggroupsentry", when set to
@@ -172,7 +172,7 @@ CLASS="QUOTE"
 	  installations where product isolation is a necessity.
 	
        	  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
@@ -182,7 +182,7 @@ CLASS="QUOTE"
 >
      3. 	  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
@@ -200,16 +200,16 @@ CLASS="QUOTE"
 	  extremely high-traffic Bugzilla databases.
 	
        	  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.  
 	  
      perl Makefile.PL
      make
      make test
      make install
      And don't forget to run exit to get back to cpan.
      
     
      	      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
@@ -253,7 +253,7 @@ CLASS="QUOTE"
 	  comments per day.
         
      	  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!
@@ -284,27 +284,27 @@ CLASS="QUOTE"
 	  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 data/params 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 data/params file.
      	  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.
 	  
      	      The "headerhtml" text box is the HTML printed out
+>
	      The "headerhtml" text box is the HTML printed out
 	      before any other code on the page,
@@ -346,7 +346,7 @@ CLASS="QUOTE"
 	  is read as the text to send to the new user along with their
 	  password message.
      	  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.
         
      	  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
@@ -399,7 +399,7 @@ CLASS="QUOTE"
 >
    143. 	  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
@@ -421,15 +421,15 @@ CLASS="QUOTE"
 	  require that most other changes come with an
 	  explanation.
      	  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.
 	  
      144. 	      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
@@ -482,7 +482,7 @@ CLASS="QUOTE"
 	  security to prevent snooping, watchers are not a good
 	  idea.
      	  However, for most sites you should set
+>
	  However, for most sites you should set
 	  "supportwatchers"
      4.3.1. Products
      Formerly, and in some spots still, called
 	"Programs"
      	
	Products are
@@ -124,7 +124,7 @@ CLASS="GLOSSTERM"
 	products (website, meetings...)
       
      	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,
@@ -141,57 +141,14 @@ CLASS="GLOSSTERM"
 TYPE="1"
 >
    144. 	    Select "components" from the yellow footer
+>
	    Select "components" from the yellow footer
 	  
      	      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...
-	    
    145. 	    Select the "Add" link to the right of "Add a new product".
-	  
    146. 	    Enter the name of the product and a description. The
-	    Description field is free-form.
-	  
      147. 	  Don't worry about the "Closed for bug entry", "Maximum Votes
+>
	      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...
+	    
    147. 
	    Select the "Add" link to the right of "Add a new product".
+	  
    148. 
	    Enter the name of the product and a description. The
+	    Description field is free-form.
+	  
      149. 
	  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
@@ -219,34 +219,34 @@ VALIGN="TOP"
 >
      4.3.2. Components
      	Components are subsections of a Product. 
+>
	Components are subsections of a Product. 
 
 	
      Example 4-1. Creating some Components
      	      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
@@ -272,7 +272,7 @@ NAME="AEN1463"
 	to the Component.
       
      	To create a new Component:
+>
	To create a new Component:
       
    149. 	    Select the "Edit components" link from the "Edit product"
+>
	    Select the "Edit components" link from the "Edit product"
 	    page
 	  
    150. 	    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.
 	  
    151. 	    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.
 	    
      		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.
 		
    152. 		      Select the "Log out" link on the footer of the
+>
		      Select the "Log out" link on the footer of the
 		      page.
 		    
    153. 		      Select the "New Account" link on the footer of
+>
		      Select the "New Account" link on the footer of
 		      the "Relogin" page
 		    
    154. 		      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.
@@ -347,7 +347,7 @@ TYPE="a"
 >
    155. 		      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.
 		    
    156. 	    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.
 	  
      4.3.3. Versions
      	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.
 
 	
      Example 4-2. Common Use of Versions
      	      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
@@ -416,23 +416,23 @@ NAME="AEN1492"
 >
      
 	
      Example 4-3. A Different Use of Versions
      	      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
@@ -450,7 +450,7 @@ NAME="AEN1496"
 >
        
      	To create and edit Versions:
+>
	To create and edit Versions:
       
    157. 	    From the "Edit product" screen, select "Edit Versions"
+>
	    From the "Edit product" screen, select "Edit Versions"
 	  
    158. 	    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.
 	  
      	    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.
 	  
    159. 	    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.
 	  
    160. 	    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.
@@ -492,26 +492,26 @@ TYPE="1"
 >
      4.3.4. Milestones
      	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.
       
      161. 	  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".
 	
      	To create new Milestones, set Default Milestones, and set
+>
	To create new Milestones, set Default Milestones, and set
 	Milestone URL: 
       
    161. 	    Select "edit milestones"
+>
	    Select "edit milestones"
 	  
    162. 	    Select "Add" to the right of the "Add a new milestone"
+>
	    Select "Add" to the right of the "Add a new milestone"
 	    text
 	  
    163. 	    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".
 	  
      Example 4-4. Using SortKey with Target Milestone
      		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",
@@ -593,17 +593,17 @@ NAME="AEN1524"
 >
    164. 	    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.
 	    
      		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,
@@ -635,21 +635,21 @@ VALIGN="TOP"
 >
    165. 	    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"
 	  
      	    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.
 	  
    166. 	    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
@@ -662,15 +662,15 @@ VALIGN="TOP"
 >
      4.3.5. Voting
      	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
@@ -681,7 +681,7 @@ NAME="VOTING"
 	attention so they don't sit for a long time awaiting triage.
       
      	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
@@ -698,19 +698,19 @@ NAME="VOTING"
 TYPE="1"
 >
    167. 	    Navigate to the "Edit product" screen for the Product you
+>
	    Navigate to the "Edit product" screen for the Product you
 	    wish to modify
 	  
    168. 	    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.
 	  
    169. 	    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
@@ -719,7 +719,7 @@ TYPE="1"
 >
    170. 	    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
@@ -727,12 +727,12 @@ TYPE="1"
 	    Votes if your Bugzilla user base is unable to affect which
 	    bugs appear on Development radar?
 	    
      171. 		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
@@ -764,44 +764,44 @@ VALIGN="TOP"
 >
    171. 	    Once you have adjusted the values to your preference,
+>
	    Once you have adjusted the values to your preference,
 	    select the "Update" button.
 	  
      172. 4.3.6. Groups and Group Security
      	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.
 
 	
      Example 4-5. When to Use Group Security
      	      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
@@ -825,11 +825,11 @@ NAME="AEN1560"
 	into two categories: Generic and Product-Based.
       
      	  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
@@ -863,7 +863,7 @@ VALIGN="TOP"
 	  next 32, etc.
 	
      	  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
@@ -879,7 +879,7 @@ VALIGN="TOP"
 >
      	To enable Generic Group Security ("usebuggroups"):
+>
	To enable Generic Group Security ("usebuggroups"):
       
    172. 	    Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+>
	    Turn "On" "usebuggroups" in the "Edit Parameters" screen.
 	  
    173. 	    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.
 	  
    174. 	    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.
 	  
    175. 	    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.
 
 	    
      Example 4-6. Creating a New Group
      		  I created a group called DefaultGroup with a
+>
		  I created a group called DefaultGroup with a
 		  description of "This is simply a group to play
@@ -950,14 +950,14 @@ CLASS="QUOTE"
 >
      176. 	To enable Product-Based Group Security (usebuggroupsentry):
+>
	To enable Product-Based Group Security (usebuggroupsentry):
       
      	  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,
@@ -991,16 +991,16 @@ VALIGN="TOP"
 TYPE="1"
 >
    176. 	    Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+>
	    Turn "On" "usebuggroups" and "usebuggroupsentry" in the
 	    "Edit Parameters" screen.
 	  
      177. 	      "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
@@ -1031,7 +1031,7 @@ VALIGN="TOP"
 >
    177. 	    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
@@ -1044,19 +1044,20 @@ VALIGN="TOP"
 >
      178. 	You may find this example illustrative for how bug groups work.
+>
	You may find this example illustrative for how bug groups work.
 	
      Example 4-7. Bugzilla Groups
      Bugzilla Groups example
      
+CLASS="literallayout"
+>
      
+Bugzilla Groups example
      
 -----------------------
      
 
      
 For this example, let us suppose we have four groups, call them
      
diff --git a/webtools/bugzilla/docs/html/quicksearch.html b/webtools/bugzilla/docs/html/quicksearch.html
index 43ae5c20b48..4908e55d496 100644
--- a/webtools/bugzilla/docs/html/quicksearch.html
+++ b/webtools/bugzilla/docs/html/quicksearch.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="Hacking Bugzilla"
 HREF="bzhacking.html">
      D.4. The Quicksearch Utility
            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"
     
            The index.html page has been updated to include the QuickSearch
+>
      The index.html page has been updated to include the QuickSearch
       text box.
     
            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.
     
            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"
@@ -97,7 +97,7 @@ NAME="QUICKSEARCH"
       but not those with the keyword "foo".
     
            Workarounds for Bugzilla users:
+>
      Workarounds for Bugzilla users:
       
            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. 
      D.1. Apache mod_rewrite magic
      Apache's mod_rewrite module lets you do some truly amazing things with URL rewriting.  Here are a couple of examples of what you can do.
    178. 	  Make it so if someone types
+>
	  Make it so if someone types
 	  http://www.foo.com/12345,
 	  Bugzilla spits back
@@ -99,17 +99,19 @@ CLASS="COMPUTEROUTPUT"
 >
      179. 
     
      Next
      7.1. Red Hat Bugzilla
            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
@@ -120,7 +120,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 >Next
      5.3. Perforce SCM
            You can find the project page for Bugzilla and Teamtrack
+>
      You can find the project page for Bugzilla and Teamtrack
       Perforce integration (p4dti) at: .
     
            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
diff --git a/webtools/bugzilla/docs/html/security.html b/webtools/bugzilla/docs/html/security.html
index 45140609ddd..3f277a6fd14 100644
--- a/webtools/bugzilla/docs/html/security.html
+++ b/webtools/bugzilla/docs/html/security.html
@@ -20,7 +20,7 @@ REL="NEXT"
 TITLE="Integrating Bugzilla with Third-Party Tools"
 HREF="integration.html">
      <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>
+
 	
      	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
@@ -131,13 +131,13 @@ VALIGN="TOP"
 >
            Secure your installation.
+>
      Secure your installation.
       
      	  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 
    179. 	    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.
 	  
       The MySQL Privilege System until you can recite it from memory!
      	    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
@@ -200,14 +200,14 @@ TARGET="_top"
 >
    180. 	    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.
 	  
    181. 	    Do not run Apache as 
	    Do not run Apache as "nobody".  This will
@@ -215,12 +215,12 @@ CLASS="QUOTE"
 	    Run it, instead, as a user with a name, set via your
 	    httpd.conf file.
 	    
      182. 		
		"nobody" is a real user on UNIX systems.
@@ -259,7 +259,7 @@ CLASS="QUOTE"
 >
    182. 	    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
@@ -274,12 +274,12 @@ CLASS="QUOTE"
 	    bug information to those who may not be allowed to see it.
 	  
      183. 	      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
@@ -305,7 +305,7 @@ VALIGN="TOP"
 	      details.
 	    
      	      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, you are at
 		risk!
      	    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  for adequate protection in your data/ and shadow/ directories.
 	  
      	    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.
 	  
      	    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. 
       <Files comments> allow
      
 	      from all </Files> deny from all 
      
 	  
      	    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. 
       <Files localconfig> deny
      
 	      from all </Files> allow from all 
      
 	  
      	    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. 
       deny from all 
      
 	  
      D.2. The setperl.csh Utility
      1. 	  Download the "setperl.csh" utility to your Bugzilla
+>
	  Download the "setperl.csh" utility to your Bugzilla
 	  directory and make it executable.
 	
        1. 	      		
	      
		bash#
 		cd /your/path/to/bugzilla
 	      
        2. 	      
	       bash# wget -O
 		  setperl.csh
 		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'
        3. 	      
	       bash# chmod
 		  u+x setperl.csh 
        4. 	  Prepare (and fix) Bugzilla file permissions.
+>
	  Prepare (and fix) Bugzilla file permissions.
 	
          1. 	      		
	      
		bash#
 		chmod u+w *
 	      
          2. 	      
	       bash# chmod
 		  u+x duplicates.cgi 
          3. 	      		
	      
		bash#
 		chmod a-x bug_status.html
 	      
          4. 	  Run the script:
+>
	  Run the script:
 	
            	  
	   bash#
 	    ./setperl.csh /your/path/to/perl
 	  
 
            Example D-1. Using Setperl to set your perl path
            	      
	       bash#
 		./setperl.csh /usr/bin/perl
 	      Apache mod_rewrite magic
      3.2. Step-by-step Install
      3.2.1. Introduction
      	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.
       
      	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 
      	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).
       
      3.2.2. Installing the Prerequisites
      Using Bundle::Bugzilla instead of manually installing Perl modules
      	The software packages necessary for the proper running of bugzilla are:
+>
	The software packages necessary for the proper running of bugzilla are:
 	
      1. 	      MySQL database server and the mysql client (3.22.5 or greater)
+>
	      MySQL database server and the mysql client (3.22.5 or greater)
 	    
      2. 	      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)
 	    
      3. 	      DBI Perl module
+>
	      DBI Perl module
 	    
      4. 	      Data::Dumper Perl module
+>
	      Data::Dumper Perl module
 	    
      5. 	      Bundle::Mysql Perl module collection
+>
	      Bundle::Mysql Perl module collection
 	    
      6. 	      TimeDate Perl module collection
+>
	      TimeDate Perl module collection
 	    
      7. 	      GD perl module (1.8.3) (optional, for bug charting)
+>
	      GD perl module (1.8.3) (optional, for bug charting)
 	    
      8. 	      Chart::Base Perl module (0.99c) (optional, for bug charting)
+>
	      Chart::Base Perl module (0.99c) (optional, for bug charting)
 	    
      9. 	      DB_File Perl module (optional, for bug charting)
+>
	      DB_File Perl module (optional, for bug charting)
 	    
      10. 	      The web server of your choice.  Apache is recommended.
+>
	      The web server of your choice.  Apache is recommended.
 	    
      11. 	      MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+>
	      MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
 	    
      
 
 	
      	    It is a good idea, while installing Bugzilla, to ensure it
+>
	    It is a good idea, while installing Bugzilla, to ensure it
 	    is not accessible by other machines
@@ -249,11 +249,11 @@ VALIGN="TOP"
 >
 	
      urpmi utility.  If you follow these
 	    commands, you should have everything you need for
 	    Bugzilla, and checksetup.pl should
 	    not complain about any missing libraries.  You may already
@@ -291,10 +291,10 @@ BORDER="0"
 >
      3.2.3. Installing MySQL Database
      	Visit MySQL homepage at 
	Visit MySQL homepage at www.mysql.com and grab the latest stable release of the server.  Many of the binary versions of MySQL store their data files in /var 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 configure.
       
      	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
 	mysqld to your
 	init scripts so the server daemon will come back up whenever
 	your machine reboots. Further discussion of UNIX init
 	sequences are beyond the scope of this guide.
 	
      bash# urpmi
 		perl-mysql
      bash# urpmi
 		perl-chart
      bash# urpmi
 		perl-gd
      bash# urpmi
 		perl-MailTools (for Bugzilla email
@@ -336,10 +336,10 @@ CLASS="COMMAND"
 >
      bash# urpmi
 		apache-modules
      You should have your init script start
 	    mysqld with the ability to accept
 	    large packets. By default, mysqld
 	    only accepts packets up to 64K long. This limits the size
 	    of attachments you may put on bugs. If you add -O
 	    max_allowed_packet=1M to the command that starts
 	    mysqld (or
 	    safe_mysqld), then you will be able
 	    to have attachments up to about 1 megabyte.
      	  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 --skip-networking
 	  option in the init script. This enhances security by
@@ -474,15 +474,15 @@ CLASS="OPTION"
 >
      3.2.4. Perl (5.004 or greater)
      	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
@@ -490,7 +490,7 @@ NAME="INSTALL-PERL"
 	this writing, that is perl version 5.6.1.
       
      	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
@@ -501,11 +501,11 @@ NAME="INSTALL-PERL"
 	isn't up to snuff.
       
      	  You can skip the following Perl module installation steps by
+>
	  You can skip the following Perl module installation steps by
 	  installing Bundle::Bugzilla from
 	  CPAN, which
@@ -584,13 +584,13 @@ CLASS="GLOSSTERM"
 	  version of Perl (at this writing, version 5.6.1)
 	
      	  
	   bash# perl -MCPAN
 	      -e 'install "Bundle::Bugzilla"'
@@ -598,7 +598,7 @@ CLASS="COMMAND"
 >
 	
      	  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.
@@ -609,22 +609,22 @@ CLASS="COMMAND"
 >
      3.2.5. DBI Perl Module
      	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.
       
      	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 .
       
      	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.
       
      	To use the CPAN shell to install DBI:
+>
	To use the CPAN shell to install DBI:
 	
      	    	      
	    
	      bash#
 	      perl -MCPAN -e 'install "DBI"'
 	    
 	    
      
 	To do it the hard way:
 	
      	    Untar the module tarball -- it should create its own directory
+>
	    Untar the module tarball -- it should create its own directory
 	  
      	    CD to the directory just created, and enter the following commands:
+>
	    CD to the directory just created, and enter the following commands:
 	    
      1. 		  		    
		  
		    bash#
 		    perl Makefile.PL
 		  
      2. 		  		    
		  
		    bash#
 		    make
 		  
      3. 		  		    
		  
		    bash#
 		    make test
 		  
      4. 		  		    
		  
		    bash#
 		    make install
 		  
      3.2.6. Data::Dumper Perl Module
      	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.
       
      	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 Appendix B
      3.2.7. MySQL related Perl Module Collection
      	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.
       
      	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:
 	bash#
 	perl Makefile.pl
       
      	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.
       
      	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.
 	
      	  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
@@ -856,15 +856,15 @@ CLASS="COMMAND"
 	
      3.2.8. TimeDate Perl Module Collection
      	  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: 
      3.2.9. GD Perl Module (1.8.3)
      	  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
@@ -895,7 +895,7 @@ NAME="AEN658"
 	install it if you want any of the graphing to work.
 	
      	  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 .  
 	
      	    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
 	  libpng and
 	  libgd.  The full requirements are
 	  listed in the Perl GD library README.  Just realize that if
@@ -944,15 +944,15 @@ CLASS="CLASSNAME"
 >
      3.2.10. Chart::Base Perl Module (0.99c)
      	  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 
      3.2.11. DB_File Perl Module
      	  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
@@ -981,15 +981,15 @@ NAME="AEN671"
 	
      3.2.12. HTTP Server
      	  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 "bugs" user permissions accordingly.
 	
      	  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:
@@ -1043,8 +1043,8 @@ WIDTH="100%"
 >
      AddHandler cgi-script .cgi
+CLASS="programlisting"
+>
AddHandler cgi-script .cgi
 	
      	  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:
  
      
 	
 	
      Options ExecCGI
      
Options ExecCGI
+
      	  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.
 	
      	    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
 	  .htaccess files and security for details
 	  on how to do this for Apache.  I appreciate notes on how to
@@ -1152,15 +1153,15 @@ HREF="geninstall.html#HTACCESS"
 >
      3.2.13. Installing the Bugzilla Files
      	  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 ).  You may decide to put the
 	files off of the main web space for your web server or perhaps
 	off of /usr/local with a symbolic link in
 	the web space that points to the Bugzilla directory.  At any
@@ -1177,11 +1178,11 @@ CLASS="FILENAME"
 	server.
 	
      	    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
 	  Forbidden errors unless you add the
 	  
      	  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
 	checksetup.pl script, which locks down your
 	installation.
       
      	Lastly, you'll need to set up a symbolic link to
+>
	Lastly, you'll need to set up a symbolic link to
 	/usr/bonsaitools/bin/perl for the correct
 	location of your perl executable (probably
 	/usr/bin/perl). Otherwise you must hack
 	all the .cgi files to change where they look for perl, or use
@@ -1245,7 +1246,7 @@ HREF="patches.html"
 >.  I suggest using the symlink
 	approach for future release compatability.
 	
      Example 3-1. Setting up bonsaitools symlink
      	      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
 	    
      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
 	    
      
 	  
      	    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:
 	    
      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
 	    
      
 	
      	    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
 	    
      3.2.14. Setting Up the MySQL Database
      	  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.
 	
      	  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 
      	    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 DROP
 	      DATABASE mysql.
@@ -1413,7 +1414,7 @@ CLASS="COMMAND"
 >
       
      	Give the MySQL root user a password.  MySQL passwords are
+>
	Give the MySQL root user a password.  MySQL passwords are
 	limited to 16 characters.
 	
      	    
	     bash# mysql
 		-u root mysql 
      	    
	     mysql> 		UPDATE user SET Password=PASSWORD ('new_password')
+CLASS="command"
+>
		UPDATE user SET Password=PASSWORD ('new_password')
 		WHERE user='root';  
@@ -1452,13 +1453,13 @@ CLASS="COMMAND"
 >
      	    
	     mysql> FLUSH
 		PRIVILEGES;  From this point on, if you need to access
 	MySQL as the MySQL root user, you will need to use
 	mysql -u root -p and enter your
 	new_password.  Remember that MySQL user names have nothing to
 	do with Unix user names (login names).	  
       
      	Next, we create the 
	Next, we create the "bugs" user, and grant
@@ -1501,7 +1502,7 @@ CLASS="QUOTE"
 	as a different user.
       
      	Remember to set bugs_password to some unique password.
+>
	Remember to set bugs_password to some unique password.
 	
      	    	      
	    
	      mysql>
 	      GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
 		ALTER,CREATE,DROP,REFERENCES 
 		ON bugs.* TO bugs@localhost
@@ -1528,16 +1529,16 @@ CLASS="COMMAND"
 >
      	    	      		mysql>
+>
	    
	      
		mysql>
 	      
 	      		FLUSH PRIVILEGES;
+CLASS="command"
+>
		FLUSH PRIVILEGES;
 	      
 	    
       
      	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
 	data directory, and create all the MySQL
 	tables.
@@ -1567,14 +1568,14 @@ BORDER="0"
 >
      	    
	     bash#
 	      ./checksetup.pl 
@@ -1586,35 +1587,35 @@ CLASS="COMMAND"
 >
       The first time you run it, it will create a
 	file called localconfig.
       
      3.2.15. Tweaking localconfig
      	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.
       
      	The connection settings include:
+>
	The connection settings include:
 	
      1. 	      server's host: just use 
	      server's host: just use "localhost" if the
@@ -1623,7 +1624,7 @@ CLASS="QUOTE"
 >
      2. 	      database name: 
	      database name: "bugs" if you're following
@@ -1632,7 +1633,7 @@ CLASS="QUOTE"
 >
      3. 	      MySQL username: 
	      MySQL username: "bugs" if you're following
@@ -1641,7 +1642,7 @@ CLASS="QUOTE"
 >
      4. 	      Password for the 
	      Password for the "bugs" MySQL account above
@@ -1651,24 +1652,24 @@ CLASS="QUOTE"
 >
       
        	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 .htaccess files and security.
       
        	Once you are happy with the settings, re-run
+>
	Once you are happy with the settings, re-run
 	checksetup.pl. On this second run, it will
 	  create the database and an administrator account for which
 	  you will be prompted to provide information.
       
        	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 
        	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 localconfig
 	file in your Bugzilla root directory.
       
        	
        
	
        	    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  parameter in
 	    localconfig as well.
 	    
        Example 3-2. Running checksetup.pl as the web user
        		  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 
         
 bash# chown -R apache:apache /usr/local/bugzilla 
 bash# su - apache 
@@ -1768,11 +1769,11 @@ bash# ./checksetup.pl
 >
       
        	  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.
 	
        3.2.16. Setting Up Maintainers Manually (Optional)
        	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
 	 mysql -u root -p bugs You
 	may need different parameters, depending on your security
@@ -1821,13 +1822,13 @@ BORDER="0"
 >
        	      
	       mysql> update
 		profiles set groupset=0x7fffffffffffffff where
 		login_name = 'XXX';
        3.2.17. The Whining Cron (Optional)
        	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
@@ -1869,10 +1870,10 @@ BORDER="0"
 >
        	    
	     cd
 		<your-bugzilla-directory> ;
 		./whineatnews.pl
       
        	  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: 
 	  
         man 5 crontab
+CLASS="programlisting"
+>
 man 5 crontab
 	  
        3.2.18. Bug Graphs (Optional)
        	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.
       
        	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:
 	
        	    
	     bash# crontab
 		-e 
        	    
	     5 0 * * * cd
 	      <your-bugzilla-directory> ; ./collectstats.pl
 	    
       
        	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. 
       
        3.2.19. Securing MySQL
        	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.
       
        	Most MySQL installs have "interesting" default security parameters:
+>
	Most MySQL installs have "interesting" default security parameters:
 	
        	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.
       
        	To see your permissions do:
+>
	To see your permissions do:
 	
        
       
        	    	      
	    
	      bash#
 	      mysql -u root -p
 	    
        	    	      
	    
	      mysql>
 	      use mysql;
 	    
        	    	      
	    
	      mysql>
 	      show tables;
 	    
        	    	      
	    
	      mysql>
 	      select * from user;
 	    
        	    	      
	    
	      mysql>
 	      select * from db;
 	    
       
        	To fix the gaping holes:
+>
	To fix the gaping holes:
 	
        	If you're not running "mit-pthreads" you can use:
+>
	If you're not running "mit-pthreads" you can use:
 	
        
       
        	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:
 	
        
       
        	Use .htaccess files with the Apache webserver to secure your
+>
	Use .htaccess files with the Apache webserver to secure your
 	bugzilla install. See .htaccess files and security
       
        	Consider also:
+>
	Consider also:
 	
        1. 	      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.
 	    
        2. 	      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.
 	    
        3. 	      starting MySQL in a chroot jail
+>
	      starting MySQL in a chroot jail
 	    
        4. 	      running the httpd in a "chrooted" jail
+>
	      running the httpd in a "chrooted" jail
 	    
        5. 	      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").
 	    
        6. 	      running MySQL on a separate untrusted machine
+>
	      running MySQL on a separate untrusted machine
 	    
        7. 	      making backups ;-)
+>
	      making backups ;-)
 	    
        1.8. Translations
              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
       <mozilla-webtools@mozilla.org
        4.2. User Administration
              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.
     
        4.2.1. Creating the Default User
        	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
@@ -96,11 +96,11 @@ NAME="DEFAULTUSER"
 	password.
       
        
       
               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):
 	  mysql> use bugs;
 	  mysql> update profiles set
 	    groupset=0x7ffffffffffffff where login_name = "(user's
@@ -152,19 +152,19 @@ CLASS="QUOTE"
 >
        4.2.2. Managing Other Users
        4.2.2.1. Logging In
      5. 	      Open the index.html page for your Bugzilla installation
+>
	      Open the index.html page for your Bugzilla installation
 	      in your browser window.
 	    
      6. 	      Click the "Query Existing Bug Reports" link.
+>
	      Click the "Query Existing Bug Reports" link.
 	    
      7. 	      Click the "Log In" link at the foot of the page.
+>
	      Click the "Log In" link at the foot of the page.
 	    
      8. 	      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.
 	    
        Congratulations, you are logged in!
        9. 4.2.2.2. Creating new users
        	  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.
@@ -218,24 +218,24 @@ NAME="CREATENEWUSERS"
 TYPE="1"
 >
      9. 	      After logging in, click the "Users" link at the footer
+>
	      After logging in, click the "Users" link at the footer
 	      of the query page.
 	    
      10. 	      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.
 	    
        11. 		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 man
 		  regexp manual page for details on regular
@@ -272,22 +272,22 @@ CLASS="COMMAND"
 >
      11. 	      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
 	    
      12. 	      Fill out the form presented.  This page is
+>
	      Fill out the form presented.  This page is
 	      self-explanatory.  When done, click "submit".
 	    
        13. 		Adding a user this way will 
		Adding a user this way will not
 		send an email informing them of their username and
@@ -326,15 +326,15 @@ CLASS="QUOTE"
 >
        4.2.2.3. Disabling Users
        	  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
@@ -342,11 +342,11 @@ NAME="DISABLEUSERS"
 	  text box, will be presented to the user the next time she
 	  attempts to use the system.
 	  
        	      Don't disable your own administrative account, or you
+>
	      Don't disable your own administrative account, or you
 	      will hate life!
 	    
        4.2.2.4. Modifying Users
        	  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.
 	
        • 	      
	      Login Name: 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.
 	      
        		  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.
 		
      13. 	      
	      Real Name: Duh!
 	    
      14. 	      
	      Password:  You can change the user
 	      password here.  It is normal to only see asterisks.
@@ -453,7 +453,7 @@ VALIGN="TOP"
 >
      15. 	      
	      Email Notification: You may choose
 	      from one of three options:
@@ -463,7 +463,7 @@ VALIGN="TOP"
 TYPE="1"
 >
      16. 		    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".
@@ -471,18 +471,18 @@ TYPE="1"
 >
      17. 		    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.
 		    
        18. 			She will still receive whining cron emails if
+>
			She will still receive whining cron emails if
 			you set up the "whinemail" feature.
 		      
      18. 		    
		    All Qualifying Bugs: This
 		    user is a glutton for punishment. If her name is
@@ -519,9 +519,10 @@ VALIGN="TOP"
 		  
        19. 
+
        	      
	      Disable Text: If you type anything
 	      in this box, including just a space, the user account is
@@ -529,12 +530,12 @@ VALIGN="TOP"
 	      interface, and what you type in this box is presented as
 	      the reason.
 	      
        
 	      
        		  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
 		  
      19. 	      
	      CanConfirm: This field is only used
 	      if you have enabled "unconfirmed" status in your
@@ -606,7 +607,7 @@ VALIGN="TOP"
 >
      20. 	      
	      Creategroups: This option will
 	      allow a user to create and destroy groups in Bugzilla.
@@ -617,18 +618,18 @@ VALIGN="TOP"
 >
      21. 	      
	      Editbugs: Unless a user has this
 	      bit set, they can only edit those bugs for which they
 	      are the assignee or the reporter.  
 	      
        22. 		  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.
@@ -657,7 +658,7 @@ VALIGN="TOP"
 >
      22. 	      
	      Editcomponents: This flag allows a
 	      user to create new  products and components, as well as
@@ -673,7 +674,7 @@ VALIGN="TOP"
 >
      23. 	      
	      Editkeywords: If you use Bugzilla's
 	      keyword functionality, enabling this feature allows a
@@ -690,7 +691,7 @@ VALIGN="TOP"
 >
      24. 	      
	      Editusers: This flag allows a user
 	      do what you're doing right now: edit other users. This
@@ -701,7 +702,7 @@ VALIGN="TOP"
 >
      25. 	      
	      PRODUCT: PRODUCT bugs access.  This
 	      allows an administrator, with product-level granularity,
diff --git a/webtools/bugzilla/docs/html/using.html b/webtools/bugzilla/docs/html/using.html
index 51e3334515e..71fc423895e 100644
--- a/webtools/bugzilla/docs/html/using.html
+++ b/webtools/bugzilla/docs/html/using.html
@@ -16,7 +16,7 @@ REL="NEXT"
 TITLE="What is Bugzilla?"
 HREF="whatis.html">
        26. 2.3.1. Create a Bugzilla Account
        2.3.2. The Bugzilla Query Page
        2.3.3. Creating and Managing Bug Reports
        2.3.3.1. Writing a Great Bug Report
        2.3.3.2. Managing your Bug Reports
        2.4.1. Account Settings
        2.4.2. Email Settings
        2.4.2.1. Email Notification
        2.4.2.2. New Email Technology
        2.4.2.3. "Watching" Users
        2.4.3. Page Footer
        2.4.4. Permissions
        2.5. Using Bugzilla-Conclusion
              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 Loki Bugzilla (Fenris)
        The Bugzilla Guide
        PrevChapter 7. Bugzilla Variants and CompetitorsNext
        7.2. Loki Bugzilla (Fenris)
        Fenris can be found at http://fenris.lokigames.com.  It is a fork from Bugzilla.
        PrevHomeNext
        Red Hat BugzillaUpIssuezilla
        
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/variant-issuezilla.html b/webtools/bugzilla/docs/html/variant-issuezilla.html
new file mode 100644
index 00000000000..26f04ae847e
--- /dev/null
+++ b/webtools/bugzilla/docs/html/variant-issuezilla.html
@@ -0,0 +1,153 @@
+Issuezilla
        The Bugzilla Guide
        PrevChapter 7. Bugzilla Variants and CompetitorsNext
        7.3. Issuezilla
        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, Scarab, a newfangled Java-based issue tracker, is under heavy development
+      and looks promising!
        URL:  http://issuezilla.tigris.org/servlets/ProjectHome
        PrevHomeNext
        Loki Bugzilla (Fenris)UpScarab
        
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/variant-perforce.html b/webtools/bugzilla/docs/html/variant-perforce.html
new file mode 100644
index 00000000000..6b97d8429be
--- /dev/null
+++ b/webtools/bugzilla/docs/html/variant-perforce.html
@@ -0,0 +1,148 @@
+Perforce SCM
        The Bugzilla Guide
        PrevChapter 7. Bugzilla Variants and CompetitorsNext
        7.5. Perforce SCM
        Although Perforce isn't really a bug tracker, it can be used
+      as such through the "jobs" functionality.
        http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perforce.com/perforce/technotes/note052.html
        PrevHomeNext
        ScarabUpSourceForge
        
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/variant-scarab.html b/webtools/bugzilla/docs/html/variant-scarab.html
new file mode 100644
index 00000000000..5a2c66d1259
--- /dev/null
+++ b/webtools/bugzilla/docs/html/variant-scarab.html
@@ -0,0 +1,148 @@
+Scarab
        The Bugzilla Guide
        PrevChapter 7. Bugzilla Variants and CompetitorsNext
        7.4. Scarab
        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.
+    
        URL: http://scarab.tigris.org
        PrevHomeNext
        IssuezillaUpPerforce SCM
        
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/variant-sourceforge.html b/webtools/bugzilla/docs/html/variant-sourceforge.html
new file mode 100644
index 00000000000..2aeb6481e75
--- /dev/null
+++ b/webtools/bugzilla/docs/html/variant-sourceforge.html
@@ -0,0 +1,148 @@
+SourceForge
        The Bugzilla Guide
        PrevChapter 7. Bugzilla Variants and CompetitorsNext
        7.6. SourceForge
        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!
        URL: http://www.sourceforge.net
        PrevHomeNext
        Perforce SCMUpThe Bugzilla FAQ
        
\ No newline at end of file
diff --git a/webtools/bugzilla/docs/html/variants.html b/webtools/bugzilla/docs/html/variants.html
index a2405d770c6..1bca97b3806 100644
--- a/webtools/bugzilla/docs/html/variants.html
+++ b/webtools/bugzilla/docs/html/variants.html
@@ -16,7 +16,7 @@ REL="NEXT"
 TITLE="Red Hat Bugzilla"
 HREF="rhbugzilla.html">
        Chapter 7. Bugzilla Variants and Competitors
        2.1. What is Bugzilla?
              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
@@ -89,48 +89,48 @@ project, Mozilla).  It is now the de-facto standard defect-tracking
 system against which all others are measured.
     
              Bugzilla has matured immensely, and now boasts many advanced features.  These include:
+>
      Bugzilla has matured immensely, and now boasts many advanced features.  These include:
       
        • 	    integrated, product-based granular security schema
+>
	    integrated, product-based granular security schema
 	  
        • 	    inter-bug dependencies and dependency graphing
+>
	    inter-bug dependencies and dependency graphing
 	  
        • 	    advanced reporting capabilities
+>
	    advanced reporting capabilities
 	  
        • 	    a robust, stable RDBMS back-end
+>
	    a robust, stable RDBMS back-end
 	  
        • 	    extensive configurability
+>
	    extensive configurability
 	  
        • 	    a very well-understood and well-thought-out natural bug resolution protocol
+>
	    a very well-understood and well-thought-out natural bug resolution protocol
 	  
        • 	    email, XML, console, and HTTP APIs
+>
	    email, XML, console, and HTTP APIs
 	  
        • 	    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)
@@ -138,14 +138,14 @@ system against which all others are measured.
 >
        • 	    too many more features to list
+>
	    too many more features to list
 	  
        
     
              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
@@ -156,7 +156,7 @@ system against which all others are measured.
       some nonstandard libraries.
     
              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 
              Despite these small problems, Bugzilla is very hard to beat.  It
+>
      Despite these small problems, Bugzilla is very hard to beat.  It
       is under very active development to address
diff --git a/webtools/bugzilla/docs/html/why.html b/webtools/bugzilla/docs/html/why.html
index dbbb4668b4e..1a5aa2fa56f 100644
--- a/webtools/bugzilla/docs/html/why.html
+++ b/webtools/bugzilla/docs/html/why.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="How do I use Bugzilla?"
 HREF="how.html">
        2.2. Why Should We Use Bugzilla?
              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
@@ -106,7 +106,7 @@ VALIGN="TOP"
       dropped or ignored.
     
              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
@@ -118,12 +118,12 @@ VALIGN="TOP"
       system for accounting for unusual system or software issues.
     
              But why should 
      But why should you use Bugzilla?
     
              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
@@ -134,7 +134,7 @@ VALIGN="TOP"
       replication problems
     
              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
@@ -148,7 +148,7 @@ VALIGN="TOP"
       led to critical decisions.
     
              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.
diff --git a/webtools/bugzilla/docs/html/win32.html b/webtools/bugzilla/docs/html/win32.html
index 6b639622dcf..350b6b88174 100644
--- a/webtools/bugzilla/docs/html/win32.html
+++ b/webtools/bugzilla/docs/html/win32.html
@@ -19,7 +19,7 @@ REL="NEXT"
 TITLE="Administering Bugzilla"
 HREF="administration.html">
        3.6. Win32 Installation Notes
        3.6.1. Win32 Installation: Step-by-step
        	  You should be familiar with, and cross-reference, the rest
+>
	  You should be familiar with, and cross-reference, the rest
 	  of the  
 	  
        1. 	    Install 
	    Install Apache Web
@@ -179,11 +179,11 @@ CLASS="QUOTE"
 >.
 	  
          	      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),
@@ -209,7 +209,7 @@ HREF="faq.html"
 >.
 	    
          	      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.
 	    
        2. 	    Install 
	    Install ActivePerl for a current compiled binary.
 	  
          	    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:
 	    	      Perl Porting
	      Perl Porting, and
 	    	      Perl on Win32 FAQ
	      Perl on Win32 FAQ
 	  
        3. 	    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.
 	  
          4. 	      You can find a list of modules at
+>
	      You can find a list of modules at
 	      		http://www.activestate.com/PPMPackages/zips/5xx-builds-only/
		http://www.activestate.com/PPMPackages/zips/5xx-builds-only/
 	    
          	    The syntax for ppm is:
+>
	    The syntax for ppm is:
 	    	      
	      C:> ppm <modulename>
 	    
 	  
          C:>ppm
 		DBD-Mysql
          Watch your capitalization!
          	    You can find ActiveState ppm modules at
+>
	    You can find ActiveState ppm modules at
 	    	      http://www.activestate.com/PPMPackages/5.6plus
	      http://www.activestate.com/PPMPackages/5.6plus
 	  
        4. 	    Install MySQL for NT.
+>
	    Install MySQL for NT.
 	    
          		You can download MySQL for Windows NT from 
		You can download MySQL for Windows NT from MySQL.com
        5. 	    Setup MySQL
+>
	    Setup MySQL
 	  
          1. 				  
		
		  C:> 
 		  C:\mysql\bin\mysql -u root mysql
 		
          2. 				  
		
		  mysql>
 		  DELETE FROM user WHERE Host='localhost' AND User='';
 		
          3. 				  
		
		  mysql>
 		  UPDATE user SET Password=PASSWORD ('new_password')
 		    WHERE user='root';
@@ -436,17 +436,17 @@ CLASS="QUOTE"
 >
          4. 				  
		
		  mysql>
 		  GRANT SELECT, INSERT, UPDATE, DELETE,
 		    INDEX, ALTER, CREATE, DROP, REFERENCES
 		    ON bugs.* to bugs@localhost
@@ -468,14 +468,14 @@ CLASS="QUOTE"
 >
          5. 				  
		
		  mysql>
 		  FLUSH PRIVILEGES;
 		
          6. 				  
		
		  mysql>
 		  create database bugs;
 		
          7. 				  
		
		  mysql>
 		  exit;
 		
          8. 				  
		
		  C:>
 		  C:\mysql\bin\mysqladmin -u root -p reload
 		
          9. 	    Edit 
	    Edit checksetup.pl in your Bugzilla directory.  Change
 	    this line:
 	  
            	    
          6. 
	    
          my $webservergid = getgrnam($my_webservergroup);
+CLASS="programlisting"
+>
my $webservergid = getgrnam($my_webservergroup);
 	    
          
 	  
          	    to
+>
	    to
 	  
          	    
          
	    
          my $webservergid = $my_webservergroup;
+CLASS="programlisting"
+>
my $webservergid = $my_webservergroup;
 	    
          my $webservergid = 'Administrators'
+CLASS="programlisting"
+>
my $webservergid = 'Administrators'
 	    
        6. 	    Run 
	    Run checksetup.pl from the Bugzilla directory.
 	  
        7. Edit localconfig to suit your
 	    requirements.  Set $db_pass to your
 	    "bugs_password" from step 5.d, and $webservergroup to "8".
          8. "8" for
 	      $webservergroup above.  If it's
 	      wrong, please send corrections.
        8. 	    Edit 
	    Edit defparams.pl to suit your
 	    requirements.  Particularly, set
 	    DefParam("maintainer") and
 	    DefParam("urlbase") to match your
 	      install.
 	  
          10. 	      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 suggestion, not
@@ -764,12 +764,12 @@ TARGET="_top"
 >
          1. 		Download NTsendmail, available from
		Download NTsendmail, available from www.ntsendmail.com
            # 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;
@@ -804,11 +804,11 @@ $ENV{"NTsendmail_max_tries"}=5;
 >
        		  Some mention to also edit
+>
		  Some mention to also edit
 		  $db_pass in
 		  globals.pl to be your
 		  .htaccess, your
 		  database password is exposed to whoever uses your
@@ -853,11 +853,11 @@ CLASS="FILENAME"
 >
      26. 		Find and comment out all occurences of
+>
		Find and comment out all occurences of
 		"open(SENDMAIL" in
@@ -871,8 +871,8 @@ WIDTH="100%"
 >
        # new sendmail functionality
+CLASS="programlisting"
+>
# new sendmail functionality
 my $mail=new NTsendmail;
 my $from="bugzilla\@your.machine.name.tld";
 my $to=$login;
@@ -886,11 +886,11 @@ $mail->send($from,$to,$subject,$msg);
 >
 	      
        27. 		  Some have found success using the commercial product, 
+>
		  Some have found success using the commercial product, 
 		  Windmail.
 		  You could try replacing your sendmail calls with:
@@ -921,8 +921,8 @@ WIDTH="100%"
 >
        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";
 		  
      27. 	    Change all references in all files from
+>
	    Change all references in all files from
 	    processmail to
 	    processmail.pl, and
 	    rename processmail to
 	    processmail.pl.
 	  
        28. 	      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.
 	    
        	      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.
 	    
        
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
@@ -1028,7 +1030,10 @@ $smtp->datasend($msg);
 $smtp->dataend();   # Finish sending the mail
 $smtp->quit;    # Close the SMTP connection
 $logstr = "$logstr; mail sent to $tolist $cclist";
-}
        
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;
@@ -1057,7 +1064,10 @@ recipient's address
                 $smtp->datasend('test');
                 $smtp->dataend();   # Finish sending the mail
                 $smtp->quit;    # Close the SMTP connection
-exit;
        29. 	      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
 	      
        	    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
 	    
      29. 	    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: 
 	    
         
-system ("./processmail.pl",@ARGLIST); 
-	    
         to
-	    
      30.             Add 
            Add binmode() calls so attachments
 	    will work ().
           
                    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
 	    createattachment.cgi  and
 	    showattachment.cgi before the
 	    require 'CGI.pl'; line.
         line.
+
        31.  
-system ("perl processmail.pl",@ARGLIST);
+system ("./processmail",@ARGLIST); 
+	    </programlisting> to
+	    <programlisting> 
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
 	    
        
        binmode(STDIN);
-binmode(STDOUT);
        
+binmode(STDIN);
+binmode(STDOUT);
+
+        
           
                      According to 
              According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files.  That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not.
             
        	  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: 
 	
        	  
        
	  
         
 .cgi to: <perl install directory>\perl.exe %s %s
 .pl to: <perl install directory>\perl.exe %s %s
@@ -1317,19 +1317,19 @@ GET,HEAD,POST
 >
        	  From Andrew Pearson:
+>
	  From Andrew Pearson:
 	  
        	      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 
 	    
        	      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:
 	    
        	      
        
	      
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+CLASS="programlisting"
+>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
 	      
        
 	    
        	      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:
 	      c:/perl/bin/perl.exe "%s" "%s"
 	    
        	      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.
 	    
        	  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
 	  not necessary
        	      Replace this:   
+>
	      Replace this:   
 	      
          
 SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
 my $enteredcryptpwd = FetchOneColumn();
@@ -1471,7 +1471,7 @@ WIDTH="100%"
 >
          
 my $enteredcryptpwd = $enteredpwd   
 	      
        3.6.3. Bugzilla LDAP Integration
        	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.
       
        Mozilla::LDAP module
        
+CLASS="literallayout"
+>
        
+Mozilla::LDAP module
        
 
        
 The Mozilla::LDAP module allows you to use LDAP for authentication to
        
 the Bugzilla system.  This module is not required if you are not using
        
diff --git a/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt b/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
index 07e41226cec..10732dd61b5 100644
--- a/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
+++ b/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
@@ -41,14 +41,14 @@ Matthew P. Barnson
    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!
@@ -649,8 +649,8 @@ Chapter 2. Using Bugzilla
    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,
@@ -1823,6 +1823,23 @@ sr/local/lib);
    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  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  entry in your
+   httpd.conf file:
+
+
+  Options +FollowSymLinks +Indexes +Includes +ExecCGI
+  AllowOverride All
+
+
+           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.
@@ -2082,6 +2099,7 @@ log";
    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('');   #connect to SMTP ser
 ver
 $smtp->mail('@');# use the sender's adress here
@@ -2093,7 +2111,9 @@ $smtp->quit;    # Close the SMTP connection
 $logstr = "$logstr; mail sent to $tolist $cclist";
 }
 
+
    here is a test mail program for Net::SMTP:
+
 use Net::SMTP;
  my $smtp = Net::SMTP->new(' 30, Debug
 => 1, ); # connect to SMTP server
@@ -2108,6 +2128,7 @@ recipient's address
                 $smtp->quit;    # Close the SMTP connection
 exit;
 
+
    12.
 
    Note
@@ -2125,17 +2146,15 @@ exit;
        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);
+             to
+            
+system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
 
 
    14. Add binmode() calls so attachments will work (bug 62000).
@@ -4520,7 +4539,7 @@ if ($::FORM{sub} eq 'PutFooter') {
 }
 
    and then put this line in index.shtml.
-   
+
 
    Note
 
@@ -5165,24 +5184,21 @@ Appendix B. Software Download Links
 
    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)
@@ -5751,10 +5767,10 @@ RewriteEngine On
 RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
 
 
-    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
@@ -5899,7 +5915,10 @@ D.5.2. Coding Style for Bugzilla
    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).
@@ -5928,12 +5947,33 @@ else
 }
 
 
+     * 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