This documentation is maintained in DocBook 4.1.2 XML format. Changes are best submitted as plain text or SGML diffs, attached - to a bug filed in - mozilla.org's Bugzilla. +>Bugzilla Documentation compontent.

This is a development version of this guide. Information in it @@ -198,13 +200,13 @@ HREF="#extraconfig" >

4.3. Win32 Installation NotesOS Specific Installation Notes

4.4. Mac OS X Installation NotesHTTP Server Configuration

4.5.

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

4-1. Installing ActivePerl ppd Modules on Microsoft - Windows

4-2. Installing OpenInteract ppd Modules manually on Microsoft - Windows

4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or - earlier.htaccess files for Apache

5-1. 1.1. Copyright InformationAppendix E.

1.1.1. GNU Free Documentation License

1.2. Disclaimer

Version 1.1, March 2000

No liability for the contents of this document can be accepted. + Use the concepts, examples, and other content at your own risk. + This document may contain errors + and inaccuracies that may damage your system, cause your partner + to leave you, your boss to fire you, your cats to + pee on your furniture and clothing, and global thermonuclear + war. Proceed with caution. +
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, - Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and - distribute verbatim copies of this license document, but changing it is - not allowed.

0. PREAMBLE

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

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.

Naming of particular products or brands should not be seen as + endorsements, with the exception of the term "GNU/Linux". We + wholeheartedly endorse the use of GNU/Linux in every situation + where it is appropriate. It is an extremely versatile, stable, + and robust operating system that offers an ideal operating + environment for Bugzilla. +

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.

You are strongly recommended to make a backup of your system + before installing Bugzilla and at regular intervals thereafter. + If you implement any suggestion in this Guide, implement this one! +

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.

Although the Bugzilla development team has taken great care to + ensure that all easily-exploitable bugs or options are + documented or fixed in the code, security holes surely exist. + Great care should be taken both in the installation and usage of + this software. Carefully consider the implications of installing + other network services with Bugzilla. The Bugzilla development + team members, Netscape Communications, America Online Inc., and + any affiliated developers or sponsors assume no liability for + your use of this product. You have the source code to this + product, and are responsible for auditing it yourself to ensure + your security needs are met. +

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

1.3. New Versions

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.

This is the 2.17.3 version of The Bugzilla Guide. It is so named + to match the current version of Bugzilla. + + This version of the guide, like its associated Bugzilla version is a + development version. Information is subject to change between now and + when 2.18 is released. + + If you are + reading this from any source other than those below, please + check one of these mirrors to make sure you are reading an + up-to-date version of the Guide. +

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

The newest version of this guide can always be found at bugzilla.org; including + documentation for past releases and the current development version. +

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

The documentation for the most recent stable release of Bugzilla can also + be found at + The Linux Documentation Project. +

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 latest version of this document can always be checked out via CVS. + Please follow the instructions available at + the Mozilla CVS page, + and check out the mozilla/webtools/bugzilla/docs/ + subtree. +

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

The Bugzilla Guide is currently only available in English. + If you would like to volunteer to translate it, please contact + Dave Miller. +

2. VERBATIM COPYING

1.4. Credits

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.

The people listed below have made enormous contributions to the + creation of this Guide, through their writing, dedicated hacking efforts, + numerous e-mail and IRC support sessions, and overall excellent + contribution to the Bugzilla community: +

You may also lend copies, under the same conditions stated above, - and you may publicly display copies.

3. COPYING IN QUANTITY

Matthew P. Barnson + for the Herculaean task of pulling together the Bugzilla Guide and + shepherding it to 2.14. +

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.

Terry Weissman + for initially writing Bugzilla and creating the + README upon which the UNIX installation documentation is largely based. +

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.

Tara Hernandez + for keeping Bugzilla development going + strong after Terry left mozilla.org +

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.

Dave Lawrence + for providing insight into the key differences between Red Hat's + customized Bugzilla, and being largely responsible for the "Red + Hat Bugzilla" appendix +

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.

Dawn Endico for + being a hacker extraordinaire and putting up with my incessant + questions and arguments on irc.mozilla.org in #mozwebtools +

Last but not least, all the members of the + netscape.public.mozilla.webtools newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened. +

Thanks also go to the following people for significant contributions + to this documentation (in no particular order): +

Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, + Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham. +

4. MODIFICATIONS

1.5. Document Conventions

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:

This document uses the following conventions:

Many of the binary - versions of MySQL store their data files in - /var. - On some Unix systems, this is part of a smaller root partition, - and may not have room for your bug database. You can set the data - directory as an option to configure - if you build MySQL from source yourself.

The ability to watch other users may not be available in all + Bugzilla installations. If you can't see it, ask your + administrator.

Descriptions Appearance

Warnings

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.

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

Don't run with scissors!

Hint

State on the Title page the name of the publisher of the - Modified Version, as the publisher.

Preserve all the copyright notices of the Document.

Would you like a breath mint?

Notes

Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices.

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.

Preserve in that license notice the full lists of Invariant - Sections and required Cover Texts given in the Document's license - notice.

Include an unaltered copy of this License.

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.

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.

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.

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.

Delete any section entitled "Endorsements". Such a section may - not be included in the Modified Version.

Do not retitle any existing section as "Endorsements" or to - conflict in title with any Invariant Section.

If the Modified Version includes new front-matter sections or - appendices that qualify as Secondary Sections and contain no material - copied from the Document, you may at your option designate some or all of - these sections as invariant. To do this, add their titles to the list of - Invariant Sections in the Modified Version's license notice. These titles - must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains - nothing but endorsements of your Modified Version by various parties--for - example, statements of peer review or that the text has been approved by - an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, - and a passage of up to 25 words as a Back-Cover Text, to the end of the - list of Cover Texts in the Modified Version. Only one passage of - Front-Cover Text and one of Back-Cover Text may be added by (or through - arrangements made by) any one entity. If the Document already includes a - cover text for the same cover, previously added by you or by arrangement - made by the same entity you are acting on behalf of, you may not add - another; but you may replace the old one, on explicit permission from the - previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this - License give permission to use their names for publicity for or to assert - or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under - this License, under the terms defined in section 4 above for modified - versions, provided that you include in the combination all of the - Invariant Sections of all of the original documents, unmodified, and list - them all as Invariant Sections of your combined work in its license - notice.

The combined work need only contain one copy of this License, and - multiple identical Invariant Sections may be replaced with a single copy. - If there are multiple Invariant Sections with the same name but different - contents, make the title of each such section unique by adding at the end - of it, in parentheses, the name of the original author or publisher of - that section if known, or else a unique number. Make the same adjustment - to the section titles in the list of Invariant Sections in the license - notice of the combined work.

In the combination, you must combine any sections entitled - "History" in the various original documents, forming one section entitled - "History"; likewise combine any sections entitled "Acknowledgements", and - any sections entitled "Dedications". You must delete all sections - entitled "Endorsements."

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other - documents released under this License, and replace the individual copies - of this License in the various documents with a single copy that is - included in the collection, provided that you follow the rules of this - License for verbatim copying of each of the documents in all other - respects.

You may extract a single document from such a collection, and - distribute it individually under this License, provided you insert a copy - of this License into the extracted document, and follow this License in - all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other - separate and independent documents or works, in or on a volume of a - storage or distribution medium, does not as a whole count as a Modified - Version of the Document, provided no compilation copyright is claimed for - the compilation. Such a compilation is called an "aggregate", and this - License does not apply to the other self-contained works thus compiled - with the Document, on account of their being thus compiled, if they are - not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these - copies of the Document, then if the Document is less than one quarter of - the entire aggregate, the Document's Cover Texts may be placed on covers - that surround only the Document within the aggregate. Otherwise they must - appear on covers around the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may - distribute translations of the Document under the terms of section 4. - Replacing Invariant Sections with translations requires special - permission from their copyright holders, but you may include translations - of some or all Invariant Sections in addition to the original versions of - these Invariant Sections. You may include a translation of this License - provided that you also include the original English version of this - License. In case of a disagreement between the translation and the - original English version of this License, the original English version - will prevail.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document - except as expressly provided for under this License. Any other attempt to - copy, modify, sublicense or distribute the Document is void, and will - automatically terminate your rights under this License. However, parties - who have received copies, or rights, from you under this License will not - have their licenses terminated so long as such parties remain in full - compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of - the GNU Free Documentation License from time to time. Such new versions - will be similar in spirit to the present version, but may differ in - detail to address new problems or concerns. See - http://www.gnu.org/copyleft/ - - .

Each version of the License is given a distinguishing version - number. If the Document specifies that a particular numbered version of - this License "or any later version" applies to it, you have the option of - following the terms and conditions either of that specified version or of - any later version that has been published (not as a draft) by the Free - Software Foundation. If the Document does not specify a version number of - this License, you may choose any version ever published (not as a draft) - by the Free Software Foundation.

How to use this License for your documents

To use this License in a document you have written, include a copy - of the License in the document and put the following copyright and - license notices just after the title page:

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, - distribute and/or modify this document under the terms of the GNU Free - Documentation License, Version 1.1 or any later version published by - the Free Software Foundation; with the Invariant Sections being LIST - THEIR TITLES, with the Front-Cover Texts being LIST, and with the - Back-Cover Texts being LIST. A copy of the license is included in the - section entitled "GNU Free Documentation License".

If you have no Invariant Sections, write "with no Invariant - Sections" instead of saying which ones are invariant. If you have no - Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover - Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we - recommend releasing these examples in parallel under your choice of free - software license, such as the GNU General Public License, to permit their - use in free software.

1.2. Disclaimer

No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content at your own risk. - This document may contain errors - and inaccuracies that may damage your system, cause your partner - to leave you, your boss to fire you, your cats to - pee on your furniture and clothing, and global thermonuclear - war. Proceed with caution. -

All copyrights are held by their respective owners, unless - specifically noted otherwise. Use of a term in this document - should not be regarded as affecting the validity of any - trademark or service mark. -

Naming of particular products or brands should not be seen as - endorsements, with the exception of the term "GNU/Linux". We - wholeheartedly endorse the use of GNU/Linux in every situation - where it is appropriate. It is an extremely versatile, stable, - and robust operating system that offers an ideal operating - environment for Bugzilla. -

You are strongly recommended to make a backup of your system - before installing Bugzilla and at regular intervals thereafter. - If you implement any suggestion in this Guide, implement this one! -

Although the Bugzilla development team has taken great care to - ensure that all easily-exploitable bugs or options are - documented or fixed in the code, security holes surely exist. - Great care should be taken both in the installation and usage of - this software. Carefully consider the implications of installing - other network services with Bugzilla. The Bugzilla development - team members, Netscape Communications, America Online Inc., and - any affiliated developers or sponsors assume no liability for - your use of this product. You have the source code to this - product, and are responsible for auditing it yourself to ensure - your security needs are met. -

1.3. New Versions

This is the 2.17.3 version of The Bugzilla Guide. It is so named - to match the current version of Bugzilla. - - This version of the guide, like its associated Bugzilla version is a - development version. Information is subject to change between now and - when 2.18 is released. - - If you are - reading this from any source other than those below, please - check one of these mirrors to make sure you are reading an - up-to-date version of the Guide. -

The newest version of this guide can always be found at bugzilla.org; including - documentation for past releases and the current development version. -

The documentation for the most recent stable release of Bugzilla can also - be found at - The Linux Documentation Project. -

The latest version of this document can always be checked out via CVS. - Please follow the instructions available at - the Mozilla CVS page, - and check out the mozilla/webtools/bugzilla/docs/ - subtree. -

The Bugzilla Guide is currently only available in English. - If you would like to volunteer to translate it, please contact - Dave Miller. -

1.4. Credits

The people listed below have made enormous contributions to the - creation of this Guide, through their writing, dedicated hacking efforts, - numerous e-mail and IRC support sessions, and overall excellent - contribution to the Bugzilla community: -

Matthew P. Barnson - for the Herculaean task of pulling together the Bugzilla Guide and - shepherding it to 2.14. -

Terry Weissman - for initially writing Bugzilla and creating the - README upon which the UNIX installation documentation is largely based. -

Tara Hernandez - for keeping Bugzilla development going - strong after Terry left mozilla.org -

Dave Lawrence - for providing insight into the key differences between Red Hat's - customized Bugzilla, and being largely responsible for the "Red - Hat Bugzilla" appendix -

Dawn Endico for - being a hacker extraordinaire and putting up with my incessant - questions and arguments on irc.mozilla.org in #mozwebtools -

Last but not least, all the members of the - netscape.public.mozilla.webtools newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened. -

Thanks also go to the following people for significant contributions - to this documentation (in no particular order): -

Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, - Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham. -

1.5. Document Conventions

This document uses the following conventions:

Descriptions Appearance

Warnings

Don't run with scissors!

Hint

Would you like a breath mint?

Notes

Dear John...

Information requiring special attention

Read this or the cat gets it.

File Names filename -

Directory Names directory -

Commands to be typed command -

Applications Names application -

Prompt - - of users command under bash shell bash$

Prompt - - of root users command under bash shell bash#

Prompt - - of user command under tcsh shell tcsh$

Environment Variables VARIABLE -

Emphasized word word -

Code Example

<para>
-Beginning and end of paragraph
-</para>

Chapter 2. Introduction

2.1. What is Bugzilla?

Bugzilla is a bug- or issue-tracking system. Bug-tracking - systems allow individual or groups of developers effectively to keep track - of outstanding problems with their product. - Bugzilla was originally - written by Terry Weissman in a programming language called TCL, to - replace a rudimentary bug-tracking database used internally by Netscape - Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl - it remains to this day. Most commercial defect-tracking software vendors - at the time charged enormous licensing fees, and Bugzilla quickly became - a favorite of the open-source crowd (with its genesis in the open-source - browser project, Mozilla). It is now the de-facto standard - defect-tracking system against which all others are measured. -

Bugzilla boasts many advanced features. These include: -

Powerful searching
User-configurable email notifications of bug changes
Full change history
Inter-bug dependency tracking and graphing
Excellent attachment management
Integrated, product-based, granular security schema
Fully security-audited, and runs under Perl's taint mode
A robust, stable RDBMS back-end
Web, XML, email and console interfaces
Completely customisable and/or localisable web user - interface
Extensive configurability
Smooth upgrade pathway between versions

2.2. Why Should We Use Bugzilla?

For many years, defect-tracking software has remained principally - the domain of large software development houses. Even then, most shops - never bothered with bug-tracking software, and instead simply relied on - shared lists and email to monitor the status of defects. This procedure - is error-prone and tends to cause those bugs judged least significant by - developers to be dropped or ignored.

These days, many companies are finding that integrated - defect-tracking systems reduce downtime, increase productivity, and raise - customer satisfaction with their systems. Along with full disclosure, an - open bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout the - data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support - accountability, telephone support knowledge bases, and a common, - well-understood system for accounting for unusual system or software - issues.

But why should - you - - use Bugzilla?

Bugzilla is very adaptable to various situations. Known uses - currently include IT support queues, Systems Administration deployment - management, chip design and development problem tracking (both - pre-and-post fabrication), and software and hardware bug tracking for - luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems. - Combined with systems such as - CVS, - Bonsai, or - Perforce SCM, Bugzilla - provides a powerful, easy-to-use solution to configuration management and - replication problems.

Bugzilla can dramatically increase the productivity and - accountability of individual employees by providing a documented workflow - and positive feedback for good performance. How many times do you wake up - in the morning, remembering that you were supposed to do - something - today, but you just can't quite remember? Put it in Bugzilla, and you - have a record of it from which you can extrapolate milestones, predict - product versions for integration, and follow the discussion trail - that led to critical decisions.

Ultimately, Bugzilla puts the power in your hands to improve your - value to your employer or business while providing a usable framework for - your natural attention to detail and knowledge store to flourish.

Chapter 3. Using Bugzilla

3.1. How do I use Bugzilla?

This section contains information for end-users of Bugzilla. - There is a Bugzilla test installation, called - Landfill, - which you are welcome to play with (if it's up.) - However, it does not necessarily - have all Bugzilla features enabled, and often runs cutting-edge versions - of Bugzilla for testing, so some things may work slightly differently - than mentioned here.

3.1.1. Create a Bugzilla Account

If you want to use Bugzilla, first you need to create an account. - Consult with the administrator responsible for your installation of - Bugzilla for the URL you should use to access it. If you're - test-driving Bugzilla, use this URL: - http://landfill.bugzilla.org/bugzilla-tip/ -

Click the - "Open a new Bugzilla account" - - link, enter your email address and, optionally, your name in the - spaces provided, then click - "Create Account" - - .
Within moments, you should receive an email to the address - you provided above, which contains your login name (generally the - same as the email address), and a password you can use to access - your account. This password is randomly generated, and can be - changed to something more memorable.
Click the - "Log In" - link in the yellow area at the bottom of the page in your browser, - enter your email address and password into the spaces provided, and - click - "Login". -

You are now logged in. Bugzilla uses cookies for authentication - so, unless your IP address changes, you should not have to log in - again.

3.1.2. Anatomy of a Bug

The core of Bugzilla is the screen which displays a particular - bug. It's a good place to explain some Bugzilla concepts. - Bug 1 on Landfill - - is a good example. Note that the labels for most fields are hyperlinks; - clicking them will take you to context-sensitive help on that - particular field. Fields marked * may not be present on every - installation of Bugzilla.

Product and Component: - Bugs are divided up by Product and Component, with a Product - having one or more Components in it. For example, - bugzilla.mozilla.org's "Bugzilla" Product is composed of several - Components: -

Dear John...

Administration: - Administration of a Bugzilla installation.

Bugzilla-General: - Anything that doesn't fit in the other components, or spans - multiple components.

Creating/Changing Bugs: - Creating, changing, and viewing bugs.

Documentation: - The Bugzilla documentation, including The Bugzilla Guide.

Email: - Anything to do with email sent by Bugzilla.

Installation: - The installation process of Bugzilla.

Query/Buglist: - Anything to do with searching for bugs and viewing the - buglists.

Reporting/Charting: - Getting reports from Bugzilla.

User Accounts: - Anything about managing a user account from the user's perspective. - Saved queries, creating accounts, changing passwords, logging in, - etc.

User Interface: - General issues having to do with the user interface cosmetics (not - functionality) including cosmetic issues, HTML templates, - etc.

Status and Resolution: - - These define exactly what state the bug is in - from not even - being confirmed as a bug, through to being fixed and the fix - confirmed by Quality Assurance. The different possible values for - Status and Resolution on your installation should be documented in the - context-sensitive help for those items.
Assigned To: - The person responsible for fixing the bug.
*URL: - A URL associated with the bug, if any.
Summary: - A one-sentence summary of the problem.
*Status Whiteboard: - (a.k.a. Whiteboard) A free-form text area for adding short notes - and tags to a bug.
*Keywords: - The administrator can define keywords which you can use to tag and - categorise bugs - e.g. The Mozilla Project has keywords like crash - and regression.
Platform and OS: - These indicate the computing environment where the bug was - found.
Version: - The "Version" field is usually used for versions of a product which - have been released, and is set to indicate which versions of a - Component have the particular problem the bug report is - about.
Priority: - The bug assignee uses this field to prioritise his or her bugs. - It's a good idea not to change this on other people's bugs.
Severity: - This indicates how severe the problem is - from blocker - ("application unusable") to trivial ("minor cosmetic issue"). You - can also use this field to indicate whether a bug is an enhancement - request.
*Target: - (a.k.a. Target Milestone) A future version by which the bug is to - be fixed. e.g. The Bugzilla Project's milestones for future - Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not - restricted to numbers, thought - you can use any text strings, such - as dates.
Reporter: - The person who filed the bug.
CC list: - A list of people who get mail when the bug changes.
Attachments: - You can attach files (e.g. testcases or patches) to bugs. If there - are any attachments, they are listed in this section.
*Dependencies: - If this bug cannot be fixed unless other bugs are fixed (depends - on), or this bug stops other bugs being fixed (blocks), their - numbers are recorded here.
*Votes: - Whether this bug has any votes.
Additional Comments: - You can add your two cents to the bug discussion here, if you have - something worthwhile to say.

3.1.3. Searching for Bugs

The Bugzilla Search page is is the interface where you can find - any bug report, comment, or patch currently in the Bugzilla system. You - can play with it here: - landfill.bugzilla.org/bugzilla-tip/query.cgi - - .

The Search page has controls for selecting different possible - values for all of the fields in a bug, as described above. Once you've - defined a search, you can either run it, or save it as a Remembered - Query, which can optionally appear in the footer of your pages.

Highly advanced querying is done using Boolean Charts, which have - their own - context-sensitive help - - .

3.1.4. Bug Lists

If you run a search, a list of matching bugs will be returned. - The default search is to return all open bugs on the system - don't try - running this search on a Bugzilla installation with a lot of - bugs!

Information requiring special attention

The format of the list is configurable. For example, it can be - sorted by clicking the column headings. Other useful features can be - accessed using the links at the bottom of the list: -

Long Format:

Read this or the cat gets it.

- - this gives you a large page with a non-editable summary of the fields - of each bug.

Change Columns:File Names filename - - change the bug attributes which appear in the list.

Change several bugs at once:Directory Names directory - - If your account is sufficiently empowered, you can make the same - change to all the bugs in the list - for example, changing their - owner.

Send mail to bug owners:Commands to be typed command - - Sends mail to the owners of all bugs on the list.

Edit this query:Applications Names application - - If you didn't get exactly the results you were looking for, you can - return to the Query page through this link and make small revisions - to the query you just made so you get more accurate results.

3.1.5. Filing Bugs

Years of bug writing experience has been distilled for your - reading pleasure into the - Bug Writing Guidelines. - While some of the advice is Mozilla-specific, the basic principles of - reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the - Hardware Platform, and Operating System you were using at the time of - the failure go a long way toward ensuring accurate, responsible fixes - for the bug that bit you.

The procedure for filing a test bug is as follows:

Go to - Landfill - in your browser and click - Enter a new bug report. -
Select a product - any one will do.
Fill in the fields. Bugzilla should have made reasonable - guesses, based upon your browser, for the "Platform" and "OS" - drop-down boxes. If they are wrong, change them.
Select "Commit" and send in your bug report.

3.2. Hints and Tips

This section distills some Bugzilla tips and best practices - that have been developed.

3.2.1. Autolinkification

Bugzilla comments are plain text - so posting HTML will result - in literal HTML tags rather than being interpreted by a browser. - However, Bugzilla will automatically make hyperlinks out of certain - sorts of text in comments. For example, the text - http://www.bugzilla.org will be turned into - http://www.bugzilla.org. - Other strings which get linkified in the obvious manner are: -

Prompt + + of users command under bash shellPrompt + + of root users command under bash shellPrompt + + of user command under tcsh shellEnvironment VariablesEmphasized wordCode Example

bug 12345 bash$

bug 23456, comment 53 bash#

attachment 4321 tcsh$

mailto:george@example.com VARIABLE +

george@example.com word +

ftp://ftp.mozilla.org

<para>
+Beginning and end of paragraph
+</para>

Most other sorts of URL

A corollary here is that if you type a bug number in a comment, - you should put the word "bug" before it, so it gets autolinkified - for the convenience of others. -

3.2.2. Quicksearch

Quicksearch is a single-text-box query tool which uses - metacharacters to indicate what is to be searched. For example, typing - "foo|bar" - into Quicksearch would search for "foo" or "bar" in the - summary and status whiteboard of a bug; adding - ":BazProduct" would - search only in that product. -

You'll find the Quicksearch box on Bugzilla's - front page, along with a - Help - link which details how to use it.

Chapter 2. Introduction

3.2.3. Comments

2.1. What is Bugzilla?

If you are changing the fields on a bug, only comment if - either you have something pertinent to say, or Bugzilla requires it. - Otherwise, you may spam people unnecessarily with bug mail. - To take an example: a user can set up their account to filter out messages - where someone just adds themselves to the CC field of a bug - (which happens a lot.) If you come along, add yourself to the CC field, - and add a comment saying "Adding self to CC", then that person - gets a pointless piece of mail they would otherwise have avoided. -

Bugzilla is a bug- or issue-tracking system. Bug-tracking + systems allow individual or groups of developers effectively to keep track + of outstanding problems with their product. + Bugzilla was originally + written by Terry Weissman in a programming language called TCL, to + replace a rudimentary bug-tracking database used internally by Netscape + Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl + it remains to this day. Most commercial defect-tracking software vendors + at the time charged enormous licensing fees, and Bugzilla quickly became + a favorite of the open-source crowd (with its genesis in the open-source + browser project, Mozilla). It is now the de-facto standard + defect-tracking system against which all others are measured. +

Don't use sigs in comments. Signing your name ("Bill") is acceptable, - particularly if you do it out of habit, but full mail/news-style - four line ASCII art creations are not. -

Bugzilla boasts many advanced features. These include: +

Powerful searching
User-configurable email notifications of bug changes
Full change history
Inter-bug dependency tracking and graphing
Excellent attachment management
Integrated, product-based, granular security schema
Fully security-audited, and runs under Perl's taint mode
A robust, stable RDBMS back-end
Web, XML, email and console interfaces
Completely customisable and/or localisable web user + interface
Extensive configurability
Smooth upgrade pathway between versions

3.2.4. Attachments

2.2. Why Should We Use Bugzilla?

Use attachments, rather than comments, for large chunks of ASCII data, - such as trace, debugging output files, or log files. That way, it doesn't - bloat the bug for everyone who wants to read it, and cause people to - receive fat, useless mails. -

For many years, defect-tracking software has remained principally + the domain of large software development houses. Even then, most shops + never bothered with bug-tracking software, and instead simply relied on + shared lists and email to monitor the status of defects. This procedure + is error-prone and tends to cause those bugs judged least significant by + developers to be dropped or ignored.

Trim screenshots. There's no need to show the whole screen if - you are pointing out a single-pixel problem. -

These days, many companies are finding that integrated + defect-tracking systems reduce downtime, increase productivity, and raise + customer satisfaction with their systems. Along with full disclosure, an + open bug-tracker allows manufacturers to keep in touch with their clients + and resellers, to communicate about problems effectively throughout the + data management chain. Many corporations have also discovered that + defect-tracking helps reduce costs by providing IT support + accountability, telephone support knowledge bases, and a common, + well-understood system for accounting for unusual system or software + issues.

Don't attach simple test cases (e.g. one HTML file, one - CSS file and an image) as a ZIP file. Instead, upload them in - reverse order and edit the referring file so that they point to the - attached files. This way, the test case works immediately - out of the bug. -

But why should + you + + use Bugzilla?

Bugzilla is very adaptable to various situations. Known uses + currently include IT support queues, Systems Administration deployment + management, chip design and development problem tracking (both + pre-and-post fabrication), and software and hardware bug tracking for + luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems. + Combined with systems such as + CVS, + Bonsai, or + Perforce SCM, Bugzilla + provides a powerful, easy-to-use solution to configuration management and + replication problems.

Bugzilla can dramatically increase the productivity and + accountability of individual employees by providing a documented workflow + and positive feedback for good performance. How many times do you wake up + in the morning, remembering that you were supposed to do + something + today, but you just can't quite remember? Put it in Bugzilla, and you + have a record of it from which you can extrapolate milestones, predict + product versions for integration, and follow the discussion trail + that led to critical decisions.

Ultimately, Bugzilla puts the power in your hands to improve your + value to your employer or business while providing a usable framework for + your natural attention to detail and knowledge store to flourish.

3.2.5. Filing Bugs

Try to make sure that everything said in the summary is also - said in the first comment. Summaries are often updated and this will - ensure your original information is easily accessible. -

You do not need to put "any" or similar strings in the URL field. - If there is no specific URL associated with the bug, leave this - field blank. -

If you feel a bug you filed was incorrectly marked as a - DUPLICATE of another, please question it in your bug, not - the bug it was duped to. Feel free to CC the person who duped it - if they are not already CCed. -

Chapter 3. Using Bugzilla

3.3. User Preferences

3.1. How do I use Bugzilla?

Once you have logged in, you can customise various aspects of - Bugzilla via the "Edit prefs" link in the page footer. - The preferences are split into four tabs:

This section contains information for end-users of Bugzilla. + There is a Bugzilla test installation, called + Landfill, + which you are welcome to play with (if it's up.) + However, it does not necessarily + have all Bugzilla features enabled, and often runs cutting-edge versions + of Bugzilla for testing, so some things may work slightly differently + than mentioned here.

3.3.1. Account Settings

3.1.1. Create a Bugzilla Account

On this tab, you can change your basic account information, - including your password, email address and real name. For security - reasons, in order to change anything on this page you must type your - currentIf you want to use Bugzilla, first you need to create an account. + Consult with the administrator responsible for your installation of + Bugzilla for the URL you should use to access it. If you're + test-driving Bugzilla, use this URL: + http://landfill.bugzilla.org/bugzilla-tip/ - password into the -

Click the + "Password""Open a new Bugzilla account" - field at the top of the page. - If you attempt to change your email address, a confirmation - email is sent to both the old and new addresses, with a link to use to - confirm the change. This helps to prevent account hijacking.
"Create Account" + + .
Within moments, you should receive an email to the address + you provided above, which contains your login name (generally the + same as the email address), and a password you can use to access + your account. This password is randomly generated, and can be + changed to something more memorable.
Click the + "Log In" + link in the yellow area at the bottom of the page in your browser, + enter your email address and password into the spaces provided, and + click + "Login". +

You are now logged in. Bugzilla uses cookies for authentication + so, unless your IP address changes, you should not have to log in + again.

3.3.2. Email Settings

3.1.2. Anatomy of a Bug

On this tab you can reduce or increase the amount of email sent - you from Bugzilla, opting in our out depending on your relationship to - the bug and the change that was made to it. (Note that you can also do - client-side filtering using the X-Bugzilla-Reason header which Bugzilla - adds to all bugmail.)

The core of Bugzilla is the screen which displays a particular + bug. It's a good place to explain some Bugzilla concepts. + Bug 1 on Landfill + + is a good example. Note that the labels for most fields are hyperlinks; + clicking them will take you to context-sensitive help on that + particular field. Fields marked * may not be present on every + installation of Bugzilla.

By entering user email names, delineated by commas, into the - "Users to watch" text entry box you can receive a copy of all the - bugmail of other users (security settings permitting.) This powerful - functionality enables seamless transitions as developers change - projects or users go on holiday.

Product and Component: + Bugs are divided up by Product and Component, with a Product + having one or more Components in it. For example, + bugzilla.mozilla.org's "Bugzilla" Product is composed of several + Components: +
Administration: + Administration of a Bugzilla installation.Bugzilla-General: + Anything that doesn't fit in the other components, or spans + multiple components.

The ability to watch other users may not be available in all - Bugzilla installations. If you can't see it, ask your - administrator.

3.3.3. Page Footer

On the Search page, you can store queries in Bugzilla, so if you - regularly run a particular query it is just a drop-down menu away. - Once you have a stored query, you can come - here to request that it also be displayed in your page footer.

3.3.4. Permissions

This is a purely informative page which outlines your current - permissions on this installation of Bugzilla - what product groups you - are in, and whether you can edit bugs or perform various administration - functions.

Chapter 4. Installation

4.1. Step-by-step Install

4.1.1. Introduction

Bugzilla has been successfully installed under Solaris, Linux, - and Win32. Win32 is not yet officially supported, but many people - have got it working fine. - Please see the - Win32 Installation Notes

Creating/Changing Bugs: + Creating, changing, and viewing bugs.

Documentation: - for further advice on getting Bugzilla to work on Microsoft - Windows.

4.1.2. Package List

Email: + Anything to do with email sent by Bugzilla.Installation: + The installation process of Bugzilla.

If you are running the very most recent - version of Perl and MySQL (both the executables and development - libraries) on your system, you can skip these manual installation - steps for the Perl modules by using Bundle::Bugzilla; see - Using Bundle::Bugzilla instead of manually installing Perl modules. -

Query/Buglist: + Anything to do with searching for bugs and viewing the + buglists.

Reporting/Charting: + Getting reports from Bugzilla.

User Accounts: + Anything about managing a user account from the user's perspective. + Saved queries, creating accounts, changing passwords, logging in, + etc.

User Interface: + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, + etc.

The software packages necessary for the proper running of - Bugzilla (with download links) are: -

MySQL database server Status and Resolution: - (3.23.41 or greater) -
Perl Assigned To: - (5.6, 5.6.1 is recommended if you wish to - use Bundle::Bugzilla) -
Perl Modules (minimum version): -
1. Template Summary: - (v2.08) -
2. File::Temp *Status Whiteboard: - (1.804) (Prerequisite for Template) -
3. AppConfig - *Keywords: - (1.52) -
4. Text::Wrap - (2001.0131) -
  Platform and OS: + These indicate the computing environment where the bug was + found.
5. File::Spec - Version: - (0.82) -
6. Data::Dumper - - (any) -
  Priority: + The bug assignee uses this field to prioritise his or her bugs. + It's a good idea not to change this on other people's bugs.
7. DBD::mysql - - (1.2209) -
  Severity: + This indicates how severe the problem is - from blocker + ("application unusable") to trivial ("minor cosmetic issue"). You + can also use this field to indicate whether a bug is an enhancement + request.
8. DBI - (1.13) -
  *Target: + (a.k.a. Target Milestone) A future version by which the bug is to + be fixed. e.g. The Bugzilla Project's milestones for future + Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not + restricted to numbers, thought - you can use any text strings, such + as dates.
9. Reporter: + The person who filed the bug.
10. CC list: + A list of people who get mail when the bug changes.
11. Attachments: + You can attach files (e.g. testcases or patches) to bugs. If there + are any attachments, they are listed in this section.
12. *Dependencies: + If this bug cannot be fixed unless other bugs are fixed (depends + on), or this bug stops other bugs being fixed (blocks), their + numbers are recorded here.
13. Date::Parse - - (any) -
  *Votes: + Whether this bug has any votes.
14. CGI - - (2.88) -
  Additional Comments: + You can add your two cents to the bug discussion here, if you have + something worthwhile to say.

3.1.3. Searching for Bugs

The Bugzilla Search page is is the interface where you can find + any bug report, comment, or patch currently in the Bugzilla system. You + can play with it here: + landfill.bugzilla.org/bugzilla-tip/query.cgi - and, optionally: -

The Search page has controls for selecting different possible + values for all of the fields in a bug, as described above. Once you've + defined a search, you can either run it, or save it as a Remembered + Query, which can optionally appear in the footer of your pages.
Highly advanced querying is done using Boolean Charts, which have + their own + GD context-sensitive help - (1.20) for bug charting -

3.1.4. Bug Lists

GD::Graph - (any) for bug charting -

If you run a search, a list of matching bugs will be returned. + The default search is to return all open bugs on the system - don't try + running this search on a Bugzilla installation with a lot of + bugs!

GD::Text::Align - (any) for bug charting +>The format of the list is configurable. For example, it can be + sorted by clicking the column headings. Other useful features can be + accessed using the links at the bottom of the list: +

Long Format: + + this gives you a large page with a non-editable summary of the fields + of each bug.

Change Columns: + + change the bug attributes which appear in the list.

Change several bugs at once: + + If your account is sufficiently empowered, you can make the same + change to all the bugs in the list - for example, changing their + owner.

Send mail to bug owners: + + Sends mail to the owners of all bugs on the list.

Edit this query: + + If you didn't get exactly the results you were looking for, you can + return to the Query page through this link and make small revisions + to the query you just made so you get more accurate results.

3.1.5. Filing Bugs

Years of bug writing experience has been distilled for your + reading pleasure into the + Bug Writing Guidelines. + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you.

The procedure for filing a test bug is as follows:

Go to + Chart::Base - Landfill - (0.99c) for bug charting -
Enter a new bug report. +
XML::Parser - (any) for the XML interface -
Select a product - any one will do.
MIME::Parser - (any) for the email interface -

Fill in the fields. Bugzilla should have made reasonable + guesses, based upon your browser, for the "Platform" and "OS" + drop-down boxes. If they are wrong, change them.

The web server of your choice. - Apache - is highly recommended. -

Select "Commit" and send in your bug report.

- -

3.2. Hints and Tips

This section distills some Bugzilla tips and best practices + that have been developed.

3.2.1. Autolinkification

Bugzilla comments are plain text - so posting HTML will result + in literal HTML tags rather than being interpreted by a browser. + However, Bugzilla will automatically make hyperlinks out of certain + sorts of text in comments. For example, the text + http://www.bugzilla.org will be turned into + http://www.bugzilla.org. + Other strings which get linkified in the obvious manner are: +

bug 12345

It is a good idea, while installing Bugzilla, to ensure that there - is some kind of firewall between you and the rest of the Internet, - because your machine may be insecure for periods during the install. - Many - installation steps require an active Internet connection to complete, - but you must take care to ensure that at no point is your machine - vulnerable to an attack.

- -

Linux-Mandrake 8.0 includes every - required and optional library for Bugzilla. The easiest way to - install them is by using the - urpmi - - utility. If you follow these commands, you should have everything you - need for Bugzilla, and - checksetup.pl - - should not complain about any missing libraries. You may already have - some of these installed.

bug 23456, comment 53attachment 4321mailto:george@example.comgeorge@example.comftp://ftp.mozilla.orgMost other sorts of URL

bash# - - urpmi perl-mysql -

bash# - - urpmi perl-chart -

bash# - - urpmi perl-gd -

bash# - - urpmi perl-MailTools - - (for Bugzilla email integration)

bash# - - urpmi apache-modules -

A corollary here is that if you type a bug number in a comment, + you should put the word "bug" before it, so it gets autolinkified + for the convenience of others. +

3.2.2. Quicksearch

Quicksearch is a single-text-box query tool which uses + metacharacters to indicate what is to be searched. For example, typing + "foo|bar" + into Quicksearch would search for "foo" or "bar" in the + summary and status whiteboard of a bug; adding + ":BazProduct" would + search only in that product. +

You'll find the Quicksearch box on Bugzilla's + front page, along with a + Help + link which details how to use it.

3.2.3. Comments

If you are changing the fields on a bug, only comment if + either you have something pertinent to say, or Bugzilla requires it. + Otherwise, you may spam people unnecessarily with bug mail. + To take an example: a user can set up their account to filter out messages + where someone just adds themselves to the CC field of a bug + (which happens a lot.) If you come along, add yourself to the CC field, + and add a comment saying "Adding self to CC", then that person + gets a pointless piece of mail they would otherwise have avoided. +

Don't use sigs in comments. Signing your name ("Bill") is acceptable, + particularly if you do it out of habit, but full mail/news-style + four line ASCII art creations are not. +

3.2.4. Attachments

Use attachments, rather than comments, for large chunks of ASCII data, + such as trace, debugging output files, or log files. That way, it doesn't + bloat the bug for everyone who wants to read it, and cause people to + receive fat, useless mails. +

Trim screenshots. There's no need to show the whole screen if + you are pointing out a single-pixel problem. +

Don't attach simple test cases (e.g. one HTML file, one + CSS file and an image) as a ZIP file. Instead, upload them in + reverse order and edit the referring file so that they point to the + attached files. This way, the test case works immediately + out of the bug. +

3.2.5. Filing Bugs

Try to make sure that everything said in the summary is also + said in the first comment. Summaries are often updated and this will + ensure your original information is easily accessible. +

You do not need to put "any" or similar strings in the URL field. + If there is no specific URL associated with the bug, leave this + field blank. +

If you feel a bug you filed was incorrectly marked as a + DUPLICATE of another, please question it in your bug, not + the bug it was duped to. Feel free to CC the person who duped it + if they are not already CCed. +

3.3. User Preferences

Once you have logged in, you can customise various aspects of + Bugzilla via the "Edit prefs" link in the page footer. + The preferences are split into four tabs:

3.3.1. Account Settings

On this tab, you can change your basic account information, + including your password, email address and real name. For security + reasons, in order to change anything on this page you must type your + current -

"Password" + field at the top of the page. + If you attempt to change your email address, a confirmation + email is sent to both the old and new addresses, with a link to use to + confirm the change. This helps to prevent account hijacking.

4.1.3. MySQL

3.3.2. Email Settings

Visit the MySQL homepage at - www.mysql.com - to grab and install the latest stable release of the server. -

On this tab you can reduce or increase the amount of email sent + you from Bugzilla, opting in our out depending on your relationship to + the bug and the change that was made to it. (Note that you can also do + client-side filtering using the X-Bugzilla-Reason header which Bugzilla + adds to all bugmail.)

By entering user email names, delineated by commas, into the + "Users to watch" text entry box you can receive a copy of all the + bugmail of other users (security settings permitting.) This powerful + functionality enables seamless transitions as developers change + projects or users go on holiday.

3.3.3. Page Footer

If you install from something other than an RPM or Debian - package, you will need to add mysqld - to your init scripts so the server daemon will come back up whenever - your machine reboots. Further discussion of UNIX init sequences are - beyond the scope of this guide. -

Change your init script to start - mysqld - with the ability to accept large packets. By default, - mysqld - only accepts packets up to 64K long. This limits the size of - attachments you may put on bugs. If you add - -O max_allowed_packet=1M - to the command that starts - mysqld - (or safe_mysqld), - then you will be able to have attachments up to about 1 megabyte. - There is a Bugzilla parameter for maximum attachment size; - you should configure it to match the value you choose here.

If you plan on running Bugzilla and MySQL on the same machine, - consider using the - --skip-networking - option in the init script. This enhances security by preventing - network access to MySQL.

On the Search page, you can store queries in Bugzilla, so if you + regularly run a particular query it is just a drop-down menu away. + Once you have a stored query, you can come + here to request that it also be displayed in your page footer.

4.1.4. Perl

3.3.4. Permissions

Any machine that doesn't have Perl on it is a sad machine indeed. - Perl can be got in source form from +>This is a purely informative page which outlines your current + permissions on this installation of Bugzilla - what product groups you + are in, and whether you can edit bugs or perform various administration + functions.

Chapter 4. Installation

4.1. Step-by-step Install

4.1.1. Introduction

Bugzilla has been successfully installed under Solaris, Linux, + and Win32. Win32 is not yet officially supported, but many people + have got it working fine. + Please see perl.com for the rare - *nix systems which don't have it. - Although Bugzilla runs with perl 5.6, - it's a good idea to be up to the very latest version - if you can when running Bugzilla. As of this writing, that is Perl - version 5.8.

Section 4.3.1 + for further advice on getting Bugzilla to work on Microsoft + Windows.

4.1.2. Package List

You can skip the following Perl module installation steps by - installing - Bundle::Bugzilla - - from +> If you are running the very most recent + version of Perl and MySQL (both the executables and development + libraries) on your system, you can skip these manual installation + steps for the Perl modules by using Bundle::Bugzilla; see CPAN, - which installs all required modules for you.

Using Bundle::Bugzilla instead of manually installing Perl modules. +

The software packages necessary for the proper running of + Bugzilla (with download links) are: +

MySQL database server + (3.23.41 or greater) +
Perl + (5.6, 5.6.1 is recommended if you wish to + use Bundle::Bugzilla) +
Perl Modules (minimum version): +
1. bash# - - perl -MCPAN -e 'install "Bundle::Bugzilla"' Template -
2. File::Temp -
3. Bundle::Bugzilla doesn't include GD, Chart::Base, or - MIME::Parser, which are not essential to a basic Bugzilla install. If - installing this bundle fails, you should install each module - individually to isolate the problem.

4.1.5. Perl Modules

AppConfig + + (1.52) +

Text::Wrap - All Perl modules can be found on the -

Comprehensive Perl - Archive Network (CPAN). The - CPAN servers have a real tendency to bog down, so please use mirrors. -

File::Spec + + (0.82) +

Quality, general Perl module installation instructions can be - found on the CPAN website, but the easy thing to do is to just use the - CPAN shell which does all the hard work for you. - To use the CPAN shell to install a module: +> Data::Dumper + + (any)

bash# - perl -MCPAN -e 'install "<modulename>"' - +> DBD::mysql + + (2.1010)

To do it the hard way: +> DBI + (1.32)

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

Date::Parse + + (any) +

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

CGI + + (2.88) +

+ and, optionally: +

bash# - - perl Makefile.PL - GD -
bash# - - make - -
GD::Graph + (any) for bug charting +
bash# - - make test - -
GD::Text::Align + (any) for bug charting +
bash# - - make install - Chart::Base + -

XML::Parser + (any) for the XML interface

MIME::Parser + (any) for the email interface +

The web server of your choice. + Apache + is highly recommended. +

+ +

Many people complain that Perl modules will not install for - them. Most times, the error messages complain that they are missing a - file in - "@INC". - Virtually every time, this error is due to permissions being set too - restrictively for you to compile Perl modules or not having the - necessary Perl development libraries installed on your system. - Consult your local UNIX systems administrator for help solving these - permissions issues; if you - are - the local UNIX sysadmin, please consult the newsgroup/mailing list - for further assistance or hire someone to help you out.

It is a good idea, while installing Bugzilla, to ensure that there + is some kind of firewall between you and the rest of the Internet, + because your machine may be insecure for periods during the install. + Many + installation steps require an active Internet connection to complete, + but you must take care to ensure that at no point is your machine + vulnerable to an attack.

4.1.5.1. DBI

The DBI module is a generic Perl module used the - MySQL-related modules. As long as your Perl installation was done - correctly the DBI module should be a breeze. It's a mixed Perl/C - module, but Perl's MakeMaker system simplifies the C compilation - greatly.

4.1.5.2. Data::Dumper

The Data::Dumper module provides data structure persistence for - Perl (similar to Java's serialization). It comes with later - sub-releases of Perl 5.004, but a re-installation just to be sure it's - available won't hurt anything.

4.1.5.3. MySQL-related modules

The Perl/MySQL interface requires a few mutually-dependent Perl - modules. These modules are grouped together into the the - Msql-Mysql-modules package.

The MakeMaker process will ask you a few questions about the - desired compilation target and your MySQL installation. For most of the - questions the provided default will be adequate, but when asked if your - desired target is the MySQL or mSQL packages, you should - select the MySQL related ones. Later you will be asked if you wish to - provide backwards compatibility with the older MySQL packages; you - should answer YES to this question. The default is NO.

A host of 'localhost' should be fine and a testing user of 'test' - with a null password should find itself with sufficient access to run - tests on the 'test' database which MySQL created upon installation. -

4.1.5.4. TimeDate modules

Many of the more common date/time/calendar related Perl modules - have been grouped into a bundle similar to the MySQL modules bundle. - This bundle is stored on the CPAN under the name TimeDate. - The component module we're most interested in is the Date::Format - module, but installing all of them is probably a good idea anyway. -

4.1.5.5. GD (optional)

The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become the - defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on millions of web pages to - generate graphs on the fly. That's what Bugzilla will be using it for - so you must install it if you want any of the graphing to work.

+ +

The Perl GD library requires some other libraries that may or - may not be installed on your system, including +>Linux-Mandrake 8.0 includes every + required and optional library for Bugzilla. The easiest way to + install them is by using the libpngurpmi - and + + utility. If you follow these commands, you should have everything you + need for Bugzilla, and libgd. - The full requirements are listed in the Perl GD library README. - If compiling GD fails, it's probably because you're - missing a required library.

4.1.5.6. Chart::Base (optional)

The Chart module provides Bugzilla with on-the-fly charting - abilities. It can be installed in the usual fashion after it has been - fetched from CPAN. - Note that earlier versions that 0.99c used GIFs, which are no longer - supported by the latest versions of GD.

4.1.5.7. Template Toolkit

When you install Template Toolkit, you'll get asked various - questions about features to enable. The defaults are fine, except - that it is recommended you use the high speed XS Stash of the Template - Toolkit, in order to achieve best performance. -

4.1.6. HTTP Server

You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can run the web server on a - different machine than MySQL, but need to adjust the MySQL - "bugs"checksetup.pl - user permissions accordingly. -

We strongly recommend Apache as the web server to use. The - Bugzilla Guide installation instructions, in general, assume you are - using Apache. If you have got Bugzilla working using another webserver, - please share your experiences with us.

bash# -

You'll want to make sure that your web server will runurpmi perl-mysql - any file - with the .cgi extension as a CGI program and not simply display the source - code. If you're - using Apache that means uncommenting the following line in the httpd.conf - file: - bash# + + urpmi perl-chart +
AddHandler cgi-script .cgi -

bash# -

With Apache you'll also want to make sure that within the - httpd.conf file these lines: - urpmi perl-gd +
Options +ExecCGI -AllowOverride Limit -
bash# - are in the stanza that covers the directories into which you intend to - put the bugzilla .html and .cgi files. + urpmi perl-MailTools -

bash# + + urpmi apache-modules +

AllowOverride Limit allows the use of a Deny statement in the - .htaccess file generated by checksetup.pl

Users of older versions of Apache may find the above lines - in the srm.conf and access.conf files, respectively.

There are important files and directories that should not be a - served by the HTTP server - most files in the - "data" - directory and the - "localconfig" - file. You should configure your HTTP server to not serve - these files. Failure to do so will expose critical passwords and - other data. Please see - .htaccess files and security - for details on how to do this for Apache; the checksetup.pl - script should create appropriate .htaccess files for you.

4.1.7. Bugzilla

4.1.3. MySQL

You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - "nobody"). - You may decide to put the files in the main web space for your - web server or perhaps in - /usr/localVisit the MySQL homepage at + www.mysql.com - with a symbolic link in the web space that points to the Bugzilla - directory.

If you symlink the bugzilla directory into your Apache's HTML - heirarchy, you may receive - Forbidden - errors unless you add the - "FollowSymLinks" Many of the binary + versions of MySQL store their data files in + /var. + On some Unix systems, this is part of a smaller root partition, + and may not have room for your bug database. You can set the data + directory as an option to configure - directive to the <Directory> entry for the HTML root - in httpd.conf.

Once all the files are in a web accessible directory, make that - directory writable by your webserver's user. This is a temporary step - until you run the post-install - If you install from something other than an RPM or Debian + package, you will need to add checksetup.plmysqld - script, which locks down your installation.

Lastly, you'll need to set up a symbolic link to +>Change your init script to start /usr/bonsaitools/bin/perlmysqld - for the correct location of your Perl executable (probably + with the ability to accept large packets. By default, /usr/bin/perl). - Otherwise you must hack all the .cgi files to change where they look - for Perl. This can be done using the following Perl one-liner, but - I suggest using the symlink approach to avoid upgrade hassles. -

"Bonsaitools" is the name Terry Weissman, the - original author of Bugzilla, created - for his suite of webtools at the time he created Bugzilla and several - other tools in use at mozilla.org. He created a directory, - /usr/bonsaitools to house his specific versions - of perl and other utilities. This usage is still current at - bugzilla.mozilla.org, - but in general most other places do not use it. You can either edit - the paths at the start of each perl file to the correct location of - perl on your system, or simply bow to history and create a - /usr/bonsaitools and /usr/bonsaitools/bin - directory, placing a symlink to perl on your system - inside 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 + /usr/bonsaitools/binmysqld -

safe_mysqld), + then you will be able to have attachments up to about 1 megabyte. + There is a Bugzilla parameter for maximum attachment size; + you should configure it to match the value you choose here.

-
perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb -
If you plan on running Bugzilla and MySQL on the same machine, + consider using the + --skip-networking - - Change /usr/bin/perl to match the location - of Perl on your machine. -

4.1.8. Setting Up the MySQL Database

After you've gotten all the software installed and working you're - ready to start preparing the database for its life as the back end to - a high quality bug tracker.

4.1.4. Perl

First, you'll want to fix MySQL permissions to allow access from - Bugzilla. For the purpose of this Installation section, the Bugzilla - username will be - "bugs", and will have minimal permissions. -

Any machine that doesn't have Perl on it is a sad machine indeed. + Perl can be got in source form from + perl.com for the rare + *nix systems which don't have it. + Although Bugzilla runs with perl 5.6, + it's a good idea to be up to the very latest version + if you can when running Bugzilla. As of this writing, that is Perl + version 5.8.

Begin by giving the MySQL root user a password. MySQL passwords are limited - to 16 characters. -

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.

You can skip the following Perl module installation steps by + installing + Bundle::Bugzilla + + from + CPAN, + which installs all required modules for you.

mysql -u root mysqlperl -MCPAN -e 'install "Bundle::Bugzilla"' -

4.1.5. Perl Modules

+ All Perl modules can be found on the + Comprehensive Perl + Archive Network (CPAN). The + CPAN servers have a real tendency to bog down, so please use mirrors. +

Quality, general Perl module installation instructions can be + found on the CPAN website, but the easy thing to do is to just use the + CPAN shell which does all the hard work for you. + To use the CPAN shell to install a module: +

mysql>bash# - - UPDATE user SET Password=PASSWORD('<new_password'>) - WHERE user='root';perl -MCPAN -e 'install "<modulename>"' - -

To do it the hard way: +

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

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

mysql>bash# - FLUSH PRIVILEGES;perl Makefile.PL - -
- - From this point on, if you need to access MySQL as the MySQL root user, - you will need to use - mysql -u root -p bash# - and enter <new_password>. Remember that MySQL user names have - nothing to do with Unix user names (login names). Next, we use an SQL GRANT command to create a - "bugs"make - - user, and grant sufficient permissions for checksetup.pl, which we'll - use later, to work its magic. This also restricts the - "bugs" - user to operations within a database called - "bugs", and only allows the account to connect from - "localhost". - Modify it to reflect your setup if you will be connecting from - another machine or as a different user.

Remember to set <bugs_password> to some unique password. -

mysql>bash# - GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, - ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost - IDENTIFIED BY '<bugs_password>';make test - -

mysql>bash# - FLUSH PRIVILEGES;make install - -

+ Many people complain that Perl modules will not install for + them. Most times, the error messages complain that they are missing a + file in + "@INC". + Virtually every time, this error is due to permissions being set too + restrictively for you to compile Perl modules or not having the + necessary Perl development libraries installed on your system. + Consult your local UNIX systems administrator for help solving these + permissions issues; if you + are + the local UNIX sysadmin, please consult the newsgroup/mailing list + for further assistance or hire someone to help you out. 4.1.5.1. DBI The DBI module is a generic Perl module used the + MySQL-related modules. As long as your Perl installation was done + correctly the DBI module should be a breeze. It's a mixed Perl/C + module, but Perl's MakeMaker system simplifies the C compilation + greatly. 4.1.5.2. Data::Dumper The Data::Dumper module provides data structure persistence for + Perl (similar to Java's serialization). It comes with later + sub-releases of Perl 5.004, but a re-installation just to be sure it's + available won't hurt anything. 4.1.5.3. MySQL-related modules The Perl/MySQL interface requires a few mutually-dependent Perl + modules. These modules are grouped together into the the + Msql-Mysql-modules package. The MakeMaker process will ask you a few questions about the + desired compilation target and your MySQL installation. For most of the + questions the provided default will be adequate, but when asked if your + desired target is the MySQL or mSQL packages, you should + select the MySQL related ones. Later you will be asked if you wish to + provide backwards compatibility with the older MySQL packages; you + should answer YES to this question. The default is NO. A host of 'localhost' should be fine and a testing user of 'test' + with a null password should find itself with sufficient access to run + tests on the 'test' database which MySQL created upon installation. 4.1.9. checksetup.pl 4.1.5.4. TimeDate modulesMany of the more common date/time/calendar related Perl modules + have been grouped into a bundle similar to the MySQL modules bundle. + This bundle is stored on the CPAN under the name TimeDate. + The component module we're most interested in is the Date::Format + module, but installing all of them is probably a good idea anyway. + 4.1.5.5. GD (optional) The GD library was written by Thomas Boutell a long while ago to + programatically generate images in C. Since then it's become the + defacto standard for programmatic image construction. The Perl bindings + to it found in the GD library are used on millions of web pages to + generate graphs on the fly. That's what Bugzilla will be using it for + so you must install it if you want any of the graphing to work. Next, run the magic checksetup.pl script. (Many thanks to - Holger Schurig - for writing this script!) - This script is designed to make sure your MySQL database and other - configuration options are consistent with the Bugzilla CGI files. - It will make sure Bugzilla files and directories have reasonable - permissions, set up the - data - directory, and create all the MySQL tables. - libgd. + The full requirements are listed in the Perl GD library README. + If compiling GD fails, it's probably because you're + missing a required library. bash# - - ./checksetup.pl - The Perl GD library requires some other libraries that may or + may not be installed on your system, including + libpng - 4.1.5.6. Chart::Base (optional) - - The first time you run it, it will create a file called - localconfig. This file contains a variety of settings you may need to tweak - including how Bugzilla should connect to the MySQL database. The connection settings include: - server's host: just use - "localhost" - if the MySQL server is local database name: - "bugs" - if you're following these directions MySQL username: - "bugs" - if you're following these directions The Chart module provides Bugzilla with on-the-fly charting + abilities. It can be installed in the usual fashion after it has been + fetched from CPAN. + Note that earlier versions that 0.99c used GIFs, which are no longer + supported by the latest versions of GD. 4.1.5.7. Template Toolkit Password for the - "bugs" - MySQL account; (<bugs_password>) above +>When you install Template Toolkit, you'll get asked various + questions about features to enable. The defaults are fine, except + that it is recommended you use the high speed XS Stash of the Template + Toolkit, in order to achieve best performance.

`4.1.6. HTTP Server`

Once you are happy with the settings, - su to the user - your web server runs as, and re-run - checksetup.pl. (Note: on some security-conscious - systems, you may need to change the login shell for the webserver - account before you can do this.) - On this second run, it will create the database and an administrator - account for which you will be prompted to provide information.

You have freedom of choice here, pretty much any web server that + is capable of running CGI + scripts will work. Section 4.4 has more information about + configuring web servers to work with Bugzilla. +

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.We strongly recommend Apache as the web server to use. The + Bugzilla Guide installation instructions, in general, assume you are + using Apache. If you have got Bugzilla working using another webserver, + please share your experiences with us. 4.1.10. Securing MySQL 4.1.7. BugzillaIf 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.You should untar the Bugzilla files into a directory that you're + willing to make writable by the default web server user (probably + "nobody"). + You may decide to put the files in the main web space for your + web server or perhaps in + /usr/local + with a symbolic link in the web space that points to the Bugzilla + directory. Most MySQL installs have "interesting" default security - parameters: - If you symlink the bugzilla directory into your Apache's HTML + hierarchy, you may receive + Forbidden + errors unless you add the + "FollowSymLinks" + directive to the <Directory> entry for the HTML root + in httpd.conf. mysqld defaults to running as root it defaults to allowing external network connections it has a known port number, and is easy to detect it defaults to no passwords whatsoever it defaults to allowing "File_Priv" 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 - 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.Lastly, you'll need to set up a symbolic link to + /usr/bonsaitools/bin/perl + for the correct location of your Perl executable (probably + /usr/bin/perl). + Otherwise you must hack all the .cgi files to change where they look + for Perl. This can be done using the following Perl one-liner, but + I suggest using the symlink approach to avoid upgrade hassles. + To see your permissions do: - bash# - - mysql -u root -p - "Bonsaitools" is the name Terry Weissman, the + original author of Bugzilla, created + for his suite of webtools at the time he created Bugzilla and several + other tools in use at mozilla.org. He created a directory, + /usr/bonsaitools to house his specific versions + of perl and other utilities. This usage is still current at + bugzilla.mozilla.org, + but in general most other places do not use it. You can either edit + the paths at the start of each perl file to the correct location of + perl on your system, or simply bow to history and create a + /usr/bonsaitools and /usr/bonsaitools/bin + directory, placing a symlink to perl on your system + inside /usr/bonsaitools/bin -

+ mysql> perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb + - use mysql; - - /usr/bin/perl to match the location + of Perl on your machine. +

4.1.8. Setting Up the MySQL Database

After you've gotten all the software installed and working you're + ready to start preparing the database for its life as the back end to + a high quality bug tracker.

First, you'll want to fix MySQL permissions to allow access from + Bugzilla. For the purpose of this Installation section, the Bugzilla + username will be + "bugs", and will have minimal permissions. +

Begin by giving the MySQL root user a password. MySQL passwords are limited + to 16 characters. +

You can download MySQL for Windows NT from - MySQL.com - - . Some find it helpful to use the WinMySqlAdmin utility, included - with the download, to set up the database.

mysql>bash# show tables;mysql -u root mysql @@ -4262,7 +3311,8 @@ CLASS="prompt" select * from user;UPDATE user SET Password=PASSWORD('<new_password'>) + WHERE user='root'; @@ -4279,7 +3329,7 @@ CLASS="prompt" select * from db;FLUSH PRIVILEGES; @@ -4290,244 +3340,45 @@ CLASS="command" >

To fix the gaping holes: -

DELETE FROM user WHERE User='';

UPDATE user SET Password=PASSWORD('new_password') WHERE - user='root';

FLUSH PRIVILEGES;

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

GRANT USAGE ON *.* TO bugs@localhost;

GRANT ALL ON bugs.* TO bugs@localhost;

REVOKE DROP ON bugs.* FROM bugs@localhost;

FLUSH PRIVILEGES;

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

GRANT USAGE ON *.* TO bugs@bounce.hop.com;

GRANT ALL ON bugs.* TO bugs@bounce.hop.com;

REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;

FLUSH PRIVILEGES;

Consider also: -

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.
using the --user= option to mysqld to run it as an - unprivileged user.
running MySQL in a chroot jail
running the httpd in a chroot jail
making sure the MySQL passwords are different from the OS - passwords (MySQL "root" has nothing to do with system - "root").
running MySQL on a separate untrusted machine
making backups ;-)

4.1.11. Configuring Bugzilla

You should run through the parameters on the Edit Parameters page - (link in the footer) and set them all to appropriate values. - They key parameters are documented in Section 5.1. -

4.2. Optional Additional Configuration

4.2.1. Dependency Charts

As well as the text-based dependency graphs, Bugzilla also - supports dependency graphing, using a package called 'dot'. - Exactly how this works is controlled by the 'webdotbase' parameter, - which can have one of three values: -

A complete file path to the command 'dot' (part of - GraphViz) - will generate the graphs locally -
A URL prefix pointing to an installation of the webdot package will - generate the graphs remotely -
A blank value will disable dependency graphing. -

So, to get this working, install - GraphViz. If you - do that, you need to - enable - server-side image maps in Apache. - Alternatively, you could set up a webdot server, or use the AT&T - public webdot server (the - default for the webdotbase param). Note that AT&T's server won't work - if Bugzilla is only accessible using HTTPS. -

4.2.2. Bug Graphs

mysql -u root -p + + and enter <new_password>. Remember that MySQL user names have + nothing to do with Unix user names (login names).

As long as you installed the GD and Graph::Base Perl modules you - might as well turn on the nifty Bugzilla bug reporting graphs.

Next, we use an SQL GRANT command to create a + "bugs" + + user, and grant sufficient permissions for checksetup.pl, which we'll + use later, to work its magic. This also restricts the + "bugs" + user to operations within a database called + "bugs", and only allows the account to connect from + "localhost". + Modify it to reflect your setup if you will be connecting from + another machine or as a different user.

Add a cron entry like this to run - collectstats.pl - daily at 5 after midnight: +>Remember to set <bugs_password> to some unique password.

bash#mysql>crontab -eGRANT SELECT,INSERT,UPDATE,DELETE,INDEX, + ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost + IDENTIFIED BY '<bugs_password>'; @@ -4554,8 +3407,16 @@ CLASS="command" >

After two days have passed you'll be able to view bug graphs from - the Bug Reports page.

4.2.3. The Whining Cron

By now you have a fully functional Bugzilla, but what good are - bugs if they're not annoying? To help make those bugs more annoying you - can set up Bugzilla's automatic whining system to complain at engineers - which leave their bugs in the NEW state without triaging them. -

4.1.9. checksetup.pl

This can be done by - adding the following command as a daily crontab entry (for help on that - see that crontab man page): +>Next, run the magic checksetup.pl script. (Many thanks to + Holger Schurig + for writing this script!) + This script is designed to make sure your MySQL database and other + configuration options are consistent with the Bugzilla CGI files. + It will make sure Bugzilla files and directories have reasonable + permissions, set up the + data + directory, and create all the MySQL tables.

5 0 * * * cd <your-bugzilla-directory> ; - ./collectstats.pl mysql> + + FLUSH PRIVILEGES; +

You can find a list of modules at - http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ - - or - Using <meta> tags to set the charset is not + recommended, as there's a bug in Netscape 4.x which causes pages + marked up in this way to load twice. See + http://www.activestate.com/PPMPackages/5.6plus -

bug + 126266 for more information including progress toward making + bugzilla charset aware by default. +

bash# + + cd <your-bugzilla-directory> ; - ./whineatnews.pl./checksetup.pl @@ -4610,473 +3482,380 @@ CLASS="command" >

Depending on your system, crontab may have several manpages. - The following command should lead you to the most useful page for - this purpose: -
man 5 crontab -
-

4.2.4. LDAP Authentication

This information on using the LDAP - authentication options with Bugzilla is old, and the authors do - not know of anyone who has tested it. Approach with caution. -

The existing authentication - scheme for Bugzilla uses email addresses as the primary user ID, and a - password to authenticate that user. All places within Bugzilla where - you need to deal with user ID (e.g assigning a bug) use the email - address. The LDAP authentication builds on top of this scheme, rather - than replacing it. The initial log in is done with a username and - password for the LDAP directory. This then fetches the email address - from LDAP and authenticates seamlessly in the standard Bugzilla - authentication scheme using this email address. If an account for this - address already exists in your Bugzilla system, it will log in to that - account. If no account for that email address exists, one is created at - the time of login. (In this case, Bugzilla will attempt to use the - "displayName" or "cn" attribute to determine the user's full name.) - After authentication, all other user-related tasks are still handled by - email address, not LDAP username. You still assign bugs by email - address, query on users by email address, etc. -

Using LDAP for Bugzilla authentication requires the - Mozilla::LDAP (aka PerLDAP) Perl module. The - Mozilla::LDAP module in turn requires Netscape's Directory SDK for C. - After you have installed the SDK, then install the PerLDAP module. - Mozilla::LDAP and the Directory SDK for C are both - available for - download from mozilla.org. -

Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP - directory for - authentication. Be very careful when setting up this parameter; if you - set LDAP authentication, but do not have a valid LDAP directory set up, - you will not be able to log back in to Bugzilla once you log out. (If - this happens, you can get back in by manually editing the data/params - file, and setting useLDAP back to 0.) -

If using LDAP, you must set the - three additional parameters: Set LDAPserver to the name (and optionally - port) of your LDAP server. If no port is specified, it defaults to the - default port of 389. (e.g "ldap.mycompany.com" or - "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching - for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids - must be unique under the DN specified here. Set LDAPmailattribute to - the name of the attribute in your LDAP directory which contains the - primary email address. On most directory servers available, this is - "mail", but you may need to change this. -

You can also try using OpenLDAP with Bugzilla, using any of a number of administration - tools. You should apply the patch attached this bug: - http://bugzilla.mozilla.org/show_bug.cgi?id=158630, then set - the following object classes for your users: + The first time you run it, it will create a file called + localconfig.

This file contains a variety of settings you may need to tweak + including how Bugzilla should connect to the MySQL database.

The connection settings include:

objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
server's host: just use + "localhost" + if the MySQL server is local
objectClass: top
database name: + "bugs" + if you're following these directions
objectClass: posixAccount
MySQL username: + "bugs" + if you're following these directions
objectClass: shadowAccount
Password for the + "bugs" + MySQL account; (<bugs_password>) above

- - Please note that this patch has not yet been - accepted by the Bugzilla team, and so you may need to do some - manual tweaking. That said, it looks like Net::LDAP is probably - the way to go in the future.

Once you are happy with the settings, + su to the user + your web server runs as, and re-run + checksetup.pl. (Note: on some security-conscious + systems, you may need to change the login shell for the webserver + account before you can do this.) + On this second run, it will create the database and an administrator + account for which you will be prompted to provide information.

The checksetup.pl script is designed so that you can run it at + any time without causing harm. You should run it after any upgrade to + Bugzilla.

4.2.5. Preventing untrusted Bugzilla content from executing malicious - Javascript code

4.1.10. Securing MySQL

It is possible for a Bugzilla to execute malicious Javascript - code. Due to internationalization concerns, we are unable to - incorporate the code changes necessary to fulfill the CERT advisory - requirements mentioned in - http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. - Executing the following code snippet from a UNIX command shell will - rectify the problem if your Bugzilla installation is intended for an - English-speaking audience. As always, be sure your Bugzilla - installation has a good backup before making changes, and I recommend - you understand what the script is doing before executing it.

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: +
mysqld defaults to running as root
bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl -
it defaults to allowing external network connections
it has a known port number, and is easy to detect
it defaults to no passwords whatsoever
it defaults to allowing "File_Priv"

All this one-liner command does is search for all instances of - "Content-type: text/html"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: +

bash# - and replaces it with - "Content-Type: text/html; charset=ISO-8859-1"mysql -u root -p + +

mysql> + + use mysql; + +

mysql> + + show tables; + +

mysql> + + select * from user; + +

mysql> + + select * from db; + +

- - . This specification prevents possible Javascript attacks on the - browser, and is suggested for all English-speaking sites. For - non-English-speaking Bugzilla sites, I suggest changing - "ISO-8859-1", above, to - "UTF-8".

To fix the gaping holes: +

DELETE FROM user WHERE User='';UPDATE user SET Password=PASSWORD('new_password') WHERE + user='root';

Using <meta> tags to set the charset is not - recommended, as there's a bug in Netscape 4.x which causes pages - marked up in this way to load twice. See - bug - 126266 for more information including progress toward making - bugzilla charset aware by default. -

FLUSH PRIVILEGES;

4.2.6. `.htaccess` - files and security

To enhance the security of your Bugzilla installation, Bugzilla's - checksetup.pl script will generate - .htaccess -

- - files which the Apache webserver can use to restrict access to the - bugzilla data files. - These .htaccess files will not work with Apache 1.2.x - but this - has security holes, so you shouldn't be using it anyway. -

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

GRANT USAGE ON *.* TO bugs@localhost;GRANT ALL ON bugs.* TO bugs@localhost;

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.

REVOKE DROP ON bugs.* FROM bugs@localhost;

FLUSH PRIVILEGES;

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:

-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: +
GRANT USAGE ON *.* TO bugs@bounce.hop.com;
<Directory /usr/local/bugzilla/> - Options +FollowSymLinks +Indexes +Includes +ExecCGI - AllowOverride All -</Directory> -
GRANT ALL ON bugs.* TO bugs@bounce.hop.com;
REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;
FLUSH PRIVILEGES;

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.

Consider also: +

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.
using the --user= option to mysqld to run it as an + unprivileged user.
running MySQL in a chroot jail
running the httpd in a chroot jail
making sure the MySQL passwords are different from the OS + passwords (MySQL "root" has nothing to do with system + "root").
running MySQL on a separate untrusted machine
If you are using Internet Information Server (IIS) or another - web server which does not observe - .htaccess - conventions, you can disable their creation by editing - localconfig - and setting the - $create_htaccessmaking backups ;-)

- variable to - 0.

4.2.7. `directoryindex` for the Bugzilla default page.

4.1.11. Configuring Bugzilla

You should modify the <DirectoryIndex> parameter for - the Apache virtual host running your Bugzilla installation to - allow index.cgi as the index page for a - directory, as well as the usual index.html, - index.htm, and so forth.

You should run through the parameters on the Edit Parameters page + (link in the footer) and set them all to appropriate values. + They key parameters are documented in Section 5.1. +

4.2.8. Bugzilla and `mod_perl`

Bugzilla is unsupported under mod_perl. Effort is underway - to make it work cleanly in a mod_perl environment, but it is - slow going. -

4.2. Optional Additional Configuration

4.2.9. `mod_throttle` - - and Security

4.2.1. Dependency Charts

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_throttleAs well as the text-based dependency graphs, Bugzilla also + supports dependency graphing, using a package called 'dot'. + Exactly how this works is controlled by the 'webdotbase' parameter, + which can have one of three values: +

A complete file path to the command 'dot' (part of + GraphViz) + will generate the graphs locally +
A URL prefix pointing to an installation of the webdot package will + generate the graphs remotely +
A blank value will disable dependency graphing. +

- - which can limit connections by ip-address. You may download this module - at +

So, to get this working, install http://www.snert.com/Software/Throttle/. - Follow the instructions to install into your Apache install. - This module only functions with the Apache web - server! - You may use the - ThrottleClientIP - - command provided by this module to accomplish this goal. See the +>GraphViz. If you + do that, you need to Module - Instructions - for more information.

enable + server-side image maps in Apache. + Alternatively, you could set up a webdot server, or use the AT&T + public webdot server (the + default for the webdotbase param). Note that AT&T's server won't work + if Bugzilla is only accessible using HARTS. +

4.3. Win32 Installation Notes

4.2.2. Bug Graphs

This section covers installation on Microsoft Windows. - Bugzilla has been made to work on Win32 platforms, but the Bugzilla team - wish to emphasise that The easiest way to install Bugzilla on - Intel-archiecture machines - is to install some variant of GNU/Linux, then follow the UNIX - installation instructions in this Guide. If you have any influence in the - platform choice for running this system, please choose GNU/Linux instead - of Microsoft Windows.

As long as you installed the GD and Graph::Base Perl modules you + might as well turn on the nifty Bugzilla bug reporting graphs.

Add a cron entry like this to run + collectstats.pl + daily at 5 after midnight: +

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

After that warning, here's the situation for 2.16 - and Windows. It doesn't work at all out of the box. - You are almost certainly better off getting - the 2.17 version from CVS (after consultation with the Bugzilla Team to - make sure you are pulling on a stable day) because we'll be doing a load - of work to make the Win32 experience more pleasant than it is now. -

If you still want to try this, to have any hope of getting it to work, - you'll need to apply the - mail patch from - bug 124174. - After that, you'll need to read the (outdated) installation - instructions below, some (probably a lot better) more - recent ones kindly provided by Toms Baugis and Jean-Sebastien - Guay, and also check the - Bugzilla 2.16 Win32 update page - . If we get time, - we'll write some better installation instructions for 2.16 and put - them up there. But no promises. -

After two days have passed you'll be able to view bug graphs from + the Bug Reports page.

4.3.1. Win32 Installation: Step-by-step

4.2.3. The Whining Cron

By now you have a fully functional Bugzilla, but what good are + bugs if they're not annoying? To help make those bugs more annoying you + can set up Bugzilla's automatic whining system to complain at engineers + which leave their bugs in the NEW state without triaging them. +

This can be done by + adding the following command as a daily crontab entry (for help on that + see that crontab man page): +

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

You should be familiar with, and cross-reference, the rest of - the - Bugzilla Installation - - section while performing your Win32 installation.

Making Bugzilla work on Microsoft Windows is no picnic. Support - for Win32 has improved dramatically in the last few releases, but, if - you choose to proceed, you should be a - very - - skilled Windows Systems Administrator with strong troubleshooting - abilities, a high tolerance for pain, and moderate perl skills. - Bugzilla on NT requires hacking source code and implementing some - advanced utilities. What follows is the recommended installation - procedure for Win32; additional suggestions are provided in - Appendix ADepending on your system, crontab may have several manpages. + The following command should lead you to the most useful page for + this purpose: +
man 5 crontab +
- - .

4.2.4. LDAP Authentication

Install - Apache Web Server - - for Windows, and copy the Bugzilla files somewhere Apache can serve - them. Please follow all the instructions referenced in - Bugzilla Installation - - regarding your Apache configuration, particularly instructions - regarding the - "AddHandler" - - parameter and - "ExecCGI" - - .

You may also use Internet Information Server or Personal - Web Server for this purpose. However, setup is quite different. - If ActivePerl doesn't seem to handle your file associations - correctly (for .cgi and .pl files), please consult - Appendix A - - .

If you are going to use IIS, if on Windows NT you must be - updated to at least Service Pack 4. Windows 2000 ships with a - sufficient version of IIS.

This information on using the LDAP + authentication options with Bugzilla is old, and the authors do + not know of anyone who has tested it. Approach with caution. +

+
Install - The existing authentication + scheme for Bugzilla uses email addresses as the primary user ID, and a + password to authenticate that user. All places within Bugzilla where + you need to deal with user ID (e.g assigning a bug) use the email + address. The LDAP authentication builds on top of this scheme, rather + than replacing it. The initial log in is done with a username and + password for the LDAP directory. This then fetches the email address + from LDAP and authenticates seamlessly in the standard Bugzilla + authentication scheme using this email address. If an account for this + address already exists in your Bugzilla system, it will log in to that + account. If no account for that email address exists, one is created at + the time of login. (In this case, Bugzilla will attempt to use the + "displayName" or "cn" attribute to determine the user's full name.) + After authentication, all other user-related tasks are still handled by + email address, not LDAP username. You still assign bugs by email + address, query on users by email address, etc. +
Using LDAP for Bugzilla authentication requires the + Mozilla::LDAP (aka PerLDAP) Perl module. The + Mozilla::LDAP module in turn requires Netscape's Directory SDK for C. + After you have installed the SDK, then install the PerLDAP module. + Mozilla::LDAP and the Directory SDK for C are both + ActivePerl - - for Windows. Check - available for + download from mozilla.org. +
Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP + directory for + authentication. Be very careful when setting up this parameter; if you + set LDAP authentication, but do not have a valid LDAP directory set up, + you will not be able to log back in to Bugzilla once you log out. (If + this happens, you can get back in by manually editing the data/params + file, and setting useLDAP back to 0.) +
If using LDAP, you must set the + three additional parameters: Set LDAPserver to the name (and optionally + port) of your LDAP server. If no port is specified, it defaults to the + default port of 389. (e.g "ldap.mycompany.com" or + "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching + for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids + must be unique under the DN specified here. Set LDAPmailattribute to + the name of the attribute in your LDAP directory which contains the + primary email address. On most directory servers available, this is + "mail", but you may need to change this. +
You can also try using http://aspn.activestate.com/ASPN/Downloads/ActivePerl +> OpenLDAP with Bugzilla, using any of a number of administration + tools. You should apply the patch attached this bug: + http://bugzilla.mozilla.org/show_bug.cgi?id=158630, then set + the following object classes for your users: - for a current compiled binary.
1. Please also check the following links to fully understand the - status of ActivePerl on Win32: - Perl PortingobjectClass: person
2. objectClass: organizationalPerson
3. objectClass: inetOrgPerson
4. objectClass: top
5. objectClass: posixAccount
6. objectClass: shadowAccount
- , and - has not yet been + accepted by the Bugzilla team, and so you may need to do some + manual tweaking. That said, it looks like Net::LDAP is probably + the way to go in the future. +

4.2.5. Preventing untrusted Bugzilla content from executing malicious + Javascript code

It is possible for a Bugzilla to execute malicious Javascript + code. Due to internationalization concerns, we are unable to + incorporate the code changes necessary to fulfill the CERT advisory + requirements mentioned in + Perl on Win32 FAQ http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. + Executing the following code snippet from a UNIX command shell will + rectify the problem if your Bugzilla installation is intended for an + English-speaking audience. As always, be sure your Bugzilla + installation has a good backup before making changes, and I recommend + you understand what the script is doing before executing it.

bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl +
-

Use ppm from your perl\bin directory to install the following - packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD, - AppConfig, and Template. You may need to extract them from .zip - format using Winzip or other unzip program first. Most of these - additional ppm modules can be downloaded from ActiveState, but - AppConfig and Template should be obtained from OpenInteract using - the - instructions on the Template Toolkit web siteAll this one-liner command does is search for all instances of + "Content-type: text/html" - .

"Content-Type: text/html; charset=ISO-8859-1" + + . This specification prevents possible Javascript attacks on the + browser, and is suggested for all English-speaking sites. For + non-English-speaking Bugzilla sites, I suggest changing + "ISO-8859-1", above, to + "UTF-8".

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

Example 4-1. Installing ActivePerl ppd Modules on Microsoft - Windows
`C:>` - - ppm - `DBD-Mysql` - -
Watch your capitalization!

ActiveState's 5.6Plus directory also contains an AppConfig - ppm, so you might see the following error when trying to install - the version at OpenInteract:

Error installing package 'AppConfig': Read a PPD - for 'AppConfig', but it is not intended for this build of Perl - (MSWin32-x86-multi-thread) -

If so, download both - the tarball - - and - the ppd4.2.6. .htaccess - - directly from OpenInteract, then run ppm from within the same - directory to which you downloaded those files and install the - package by referencing the ppd file explicitly via in the install - command, f.e.: -

Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft - Windows

install - To enhance the security of your Bugzilla installation, Bugzilla's + C:\AppConfig.ppd - - checksetup.pl script will generate + .htaccess -

-
Install MySQL for NT. -

Setup MySQL

C:> - - C:\mysql\bin\mysql -u root mysql - -
mysql> - - DELETE FROM user WHERE Host='localhost' AND - User=''; - -
mysql> - - UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root'; - -
"new_password" - - , above, indicates whatever password you wish to use for your - "root" - - user.
mysql> - - GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, - ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost - IDENTIFIED BY 'bugs_password'; - -
"bugs_password" - - , above, indicates whatever password you wish to use for your - "bugs" - - user.
mysql>If you are using an alternate provider of + webdot - FLUSH PRIVILEGES; - -
mysql>editparams.cgi - create database bugs; - -
mysql>data/webdot/.htaccess - exit; - -

C:>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 - C:\mysql\bin\mysqladmin -u root -p - reload -/usr/local/bugzilla -

Edit - checksetup.plhttpd.conf - in your Bugzilla directory. Change this line:

+
my $webservergid = - getgrnam($my_webservergroup);
<Directory /usr/local/bugzilla/> + Options +FollowSymLinks +Indexes +Includes +ExecCGI + AllowOverride All +</Directory> +
-

my $webservergid = - $my_webservergroup;
The important part above is + "AllowOverride All" - or the name of the group you wish to own the files explicitly: -
my $webservergid = - 'Administrators'
.htaccess -

Run - checksetup.pl - from the Bugzilla directory.

Edit - If you are using Internet Information Server (IIS) or another + web server which does not observe + .htaccess + conventions, you can disable their creation by editing + localconfig - - to suit your requirements. Set - $db_pass$create_htaccess - - to your - "bugs_password"0. +

A.4.7. A.6.3. - How come email from Bugzilla changes never reaches me? + CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why?

A.5.4. A.7.3. - I think I've set up MySQL permissions correctly, but Bugzilla still can't - connect. + 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.6.4. A.8.4. - I'm having trouble with the perl modules for NT not being able to talk to - to the database. + What's the best way to submit patches? What guidelines should I follow?

7. Bugzilla Usage

Appendix B. The Bugzilla Database

A.7.1. - How do I change my user name (email address) in Bugzilla? -

- New in 2.16 - go to the Account section of the Preferences. You will - be emailed at both addresses for confirmation. -

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?

A.7.2. B.1. Modifying Your Running System

Bugzilla optimizes database lookups by storing all relatively + static information in the + versioncache file, located in the + data/ - The query page is very confusing. Isn't there a simpler way to query? -

If you make a change to the structural data in your database (the + versions table for example), or to the + "constants" - The interface was simplified by a UI designer for 2.16. Further - suggestions for improvement are welcome, but we won't sacrifice power for - simplicity. -

defparams.pl, you will need to remove + the cached content from the data directory (by doing a + "rm data/versioncache" + + ), or your changes won't show up.

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

B.2. MySQL Bugzilla Database Introduction

This information comes straight from my life. I was forced to learn + how Bugzilla organizes database because of nitpicky requests from users + for tiny changes in wording, rather than having people re-educate + themselves or figure out how to work our procedures around the tool. It + sucks, but it can and will happen to you, so learn how the schema works + and deal with it when it comes.

So, here you are with your brand-new installation of Bugzilla. + You've got MySQL set up, Apache working right, Perl DBI and DBD talking + to the database flawlessly. Maybe you've even entered a few test bugs to + make sure email's working; people seem to be notified of new bugs and + changes, and you can enter and edit bugs to your heart's content. Perhaps + you've gone through the trouble of setting up a gateway for people to + submit bugs to your database via email, have had a few people test it, + and received rave reviews from your beta testers.

What's the next thing you do? Outline a training strategy for your + development team, of course, and bring them up to speed on the new tool + you've labored over for hours.

Your first training session starts off very well! You have a + captive audience which seems enraptured by the efficiency embodied in + this thing called "Bugzilla". You are caught up describing the nifty + features, how people can save favorite queries in the database, set them + up as headers and footers on their pages, customize their layouts, + generate reports, track status with greater efficiency than ever before, + leap tall buildings with a single bound and rescue Jane from the clutches + of Certain Death!

But Certain Death speaks up -- a tiny voice, from the dark corners + of the conference room. "I have a concern," the voice hisses from the + darkness, "about the use of the word 'verified'.

The room, previously filled with happy chatter, lapses into + reverential silence as Certain Death (better known as the Vice President + of Software Engineering) continues. "You see, for two years we've used + the word 'verified' to indicate that a developer or quality assurance + engineer has confirmed that, in fact, a bug is valid. I don't want to + lose two years of training to a new software product. You need to change + the bug status of 'verified' to 'approved' as soon as possible. To avoid + confusion, of course."

Oh no! Terror strikes your heart, as you find yourself mumbling + "yes, yes, I don't think that would be a problem," You review the changes + with Certain Death, and continue to jabber on, "no, it's not too big a + change. I mean, we have the source code, right? You know, 'Use the + Source, Luke' and all that... no problem," All the while you quiver + inside like a beached jellyfish bubbling, burbling, and boiling on a hot + Jamaican sand dune...

Thus begins your adventure into the heart of Bugzilla. You've been + forced to learn about non-portable enum() fields, varchar columns, and + tinyint definitions. The Adventure Awaits You!

A.7.3. - I'm confused by the behavior of the "accept" button in the Show Bug form. - Why doesn't it assign the bug to me when I accept it? -

B.2.1. Bugzilla Database Basics

If you were like me, at this point you're totally clueless about + the internals of MySQL, and if it weren't for this executive order from + the Vice President you couldn't care less about the difference between + a + "bigint" - The current behavior is acceptable to bugzilla.mozilla.org and most - users. You have your choice of patches - to change this behavior, however. -

Add a "and accept bug" radio button

"tinyint" + + entry in MySQL. I recommend you refer to the MySQL documentation, + available at + "Accept" button automatically assigns to you

MySQL.com + + . Below are the basics you need to know about the Bugzilla database. + Check the chart above for more details.

To connect to your database:
bash# - Note that these patches are somewhat dated. You will need to apply - them manually. -

mysql + + -u root +

A.7.4. If this works without asking you for a password, + shame on you - I can't upload anything into the database via the "Create Attachment" - link. What am I doing wrong? -

MySQL + searchable documentation. +

You should now be at a prompt that looks like this:

mysql> - The most likely cause is a very old browser or a browser that is - incompatible with file upload via POST. Download the latest Netscape, - Microsoft, or Mozilla browser to handle uploads correctly. -

A.7.5. At the prompt, if + "bugs" - How do I change a keyword in Bugzilla, once some bugs are using it? -

localconfig + + file for your Bugzilla database, type:

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

use bugs; +

8. Bugzilla Hacking

B.2.1.1. Bugzilla Database Tables

A.8.1. Imagine your MySQL database as a series of spreadsheets, and + you won't be too far off. If you use this command:

mysql> - What kind of style should I use for templatization? -

show tables from bugs; +

you'll be able to see the names of all the + "spreadsheets" - Gerv and Myk suggest a 2-space indent, with embedded code sections on - their own line, in line with outer tags. Like this:

0-9, high ascii

Apache

In this context, Apache is the web server most commonly used - for serving up - Bugzilla - + for serving up Bugzilla pages. Contrary to popular belief, the apache web server has nothing to do with the ancient and noble Native American tribe, but instead derived its name from the fact that it was @@ -128,14 +126,123 @@ CLASS="glossterm" CLASS="QUOTE" >"a patchy" - version of the original NCSA - world-wide-web server.

Useful Directives when configuring Bugzilla

AddHandler: Tell Apache that it's OK to run CGI scripts.
AllowOverride, Options: These directives are used to tell Apache many things about + the directory they apply to. For Bugzilla's purposes, we need + them to allow script execution and .htaccess + overrides. +
DirectoryIndex: Used to tell Apache what files are indexes. If you can + not add index.cgi to the list of valid files, + you'll need to set $index_html to + 1 in localconfig so + ./checksetup.pl will create an + index.html that redirects to + index.cgi. +
ScriptInterpreterSource: Used when running Apache on windows so the shebang line + doesn't have to be changed in every Bugzilla script. +

For more information about how to configure Apache for Bugzilla, + see Section 4.4.1. +

Common Gateway Interface: CGI is an acronym for Common Gateway Interface. This is + a standard for interfacing an external application with a web server. Bugzilla + is an example of a CGI application. +
G
Groups
J
JavaScript
JavaScript is cool, we should talk about it. +
M
Tool Command Language
(TCL)
TCL is an open source scripting language available for Windows, + Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but + never released. The first release of Bugzilla was 2.0, which was when + it was ported to perl. +
PrevSourceForgeHow to use this License for your documents

<fred>
-[% IF foo %]
-  <bar>
-  [% FOREACH x = barney %]
-    <tr>
-      <td>
-        [% x %]
-      </td>
-    <tr>
-  [% END %]
-[% END %]
-</fred>
+        (tables) in your database.
From the command issued above, ou should have some
+	  output that looks like this:
++-------------------+
+| Tables in bugs    |
++-------------------+
+| attachments       |
+| bugs              |
+| bugs_activity     |
+| cc                |
+| components        |
+| dependencies      |
+| fielddefs         |
+| groups            |
+| keyworddefs       |
+| keywords          |
+| logincookies      |
+| longdescs         |
+| milestones        |
+| namedqueries      |
+| products          |
+| profiles          |
+| profiles_activity |
+| tokens            |
+| versions          |
+| votes             |
+| watch             |
++-------------------+
 
 Myk also recommends you turn on PRE_CHOMP in the template
-	initialization to prevent bloating of HTML with unnecessary whitespace.
-	
Please note that many have differing opinions on this subject,
-	and the existing templates in Bugzilla espouse both this and a 4-space
-	style.  Either is acceptable; the above is preferred.
A.8.2. 
-	    What bugs are in Bugzilla right now?
-	  
 
-	    Try 	    this link to view current bugs or requests for
-	    enhancement for Bugzilla.
-	  
	    You can view bugs marked for 2.18 release
-	    here.
-	    This list includes bugs for the 2.18 release that have already
-	    been fixed and checked into CVS.  Please consult the
-	    	      Bugzilla Project Page for details on how to
-	    check current sources out of CVS so you can have these
-	    bug fixes early!
-	  
A.8.3. 
-	    How can I change the default priority to a null value?  For instance, have the default
-	    priority be "---" instead of "P2"?
-	  


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

+

+attachments: This table stores all attachments to bugs.  It tends to be your

+largest table, yet also generally has the fewest entries because file

+attachments are so (relatively) large.

+

+bugs:  This is the core of your system.  The bugs table stores most of the

+current information about a bug, with the exception of the info stored in the

+other tables.

+

+bugs_activity:  This stores information regarding what changes are made to bugs

+when -- a history file.

+

+cc:  This tiny table simply stores all the CC information for any bug which has

+any entries in the CC field of the bug.  Note that, like most other tables in

+Bugzilla, it does not refer to users by their user names, but by their unique

+userid, stored as a primary key in the profiles table.

+

+components: This stores the programs and components (or products and

+components, in newer Bugzilla parlance) for Bugzilla.  Curiously, the "program"

+(product) field is the full name of the product, rather than some other unique

+identifier, like bug_id and user_id are elsewhere in the database.

+

+dependencies: Stores data about those cool dependency trees.

+

+fielddefs:  A nifty table that defines other tables.  For instance, when you

+submit a form that changes the value of "AssignedTo" this table allows

+translation to the actual field name "assigned_to" for entry into MySQL.

+

+groups:  defines bitmasks for groups.  A bitmask is a number that can uniquely

+identify group memberships.  For instance, say the group that is allowed to

+tweak parameters is assigned a value of "1", the group that is allowed to edit

+users is assigned a "2", and the group that is allowed to create new groups is

+assigned the bitmask of "4".  By uniquely combining the group bitmasks (much

+like the chmod command in UNIX,) you can identify a user is allowed to tweak

+parameters and create groups, but not edit users, by giving him a bitmask of

+"5", or a user allowed to edit users and create groups, but not tweak

+parameters, by giving him a bitmask of "6" Simple, huh?

+  If this makes no sense to you, try this at the mysql prompt:

+mysql> select * from groups;

+  You'll see the list, it makes much more sense that way.

+

+keyworddefs:  Definitions of keywords to be used

+

+keywords: Unlike what you'd think, this table holds which keywords are

+associated with which bug id's.

+

+logincookies: This stores every login cookie ever assigned to you for every

+machine you've ever logged into Bugzilla from.  Curiously, it never does any

+housecleaning -- I see cookies in this file I've not used for months.  However,

+since Bugzilla never expires your cookie (for convenience' sake), it makes

+sense.

+

+longdescs:  The meat of bugzilla -- here is where all user comments are stored!

+You've only got 2^24 bytes per comment (it's a mediumtext field), so speak

+sparingly -- that's only the amount of space the Old Testament from the Bible

+would take (uncompressed, 16 megabytes).  Each comment is keyed to the

+bug_id to which it's attached, so the order is necessarily chronological, for

+comments are played back in the order in which they are received.

+

+milestones:  Interesting that milestones are associated with a specific product

+in this table, but Bugzilla does not yet support differing milestones by

+product through the standard configuration interfaces.

+

+namedqueries:  This is where everybody stores their "custom queries".  Very

+cool feature; it beats the tar out of having to bookmark each cool query you

+construct.

+

+products:  What products you have, whether new bug entries are allowed for the

+product, what milestone you're working toward on that product, votes, etc.  It

+will be nice when the components table supports these same features, so you

+could close a particular component for bug entry without having to close an

+entire product...

+

+profiles:  Ahh, so you were wondering where your precious user information was

+stored?  Here it is!  With the passwords in plain text for all to see! (but

+sshh... don't tell your users!)

+

+profiles_activity:  Need to know who did what when to who's profile?  This'll

+tell you, it's a pretty complete history.

+

+versions:  Version information for every product

+

+votes:  Who voted for what when

+

+watch:  Who (according to userid) is watching who's bugs (according to their

+userid).

+

+

+===

+THE DETAILS

+===

+

+  Ahh, so you're wondering just what to do with the information above?  At the

+mysql prompt, you can view any information about the columns in a table with

+this command (where "table" is the name of the table you wish to view):

+

+mysql> show columns from table;

+

+  You can also view all the data in a table with this command:

+

+mysql> select * from table;

+

+  -- note: this is a very bad idea to do on, for instance, the "bugs" table if

+you have 50,000 bugs.  You'll be sitting there a while until you ctrl-c or

+50,000 bugs play across your screen.

+

+  You can limit the display from above a little with the command, where

+"column" is the name of the column for which you wish to restrict information:

+

+mysql> select * from table where (column = "some info");

+

+  -- or the reverse of this

+

+mysql> select * from table where (column != "some info");

+

+  Let's take our example from the introduction, and assume you need to change

+the word "verified" to "approved" in the resolution field.  We know from the

+above information that the resolution is likely to be stored in the "bugs"

+table. Note we'll need to change a little perl code as well as this database

+change, but I won't plunge into that in this document. Let's verify the

+information is stored in the "bugs" table:

+

+mysql> show columns from bugs

+

+  (exceedingly long output truncated here)

+| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||

+

+  Sorry about that long line.  We see from this that the "bug status" column is

+an "enum field", which is a MySQL peculiarity where a string type field can

+only have certain types of entries.  While I think this is very cool, it's not

+standard SQL.  Anyway, we need to add the possible enum field entry

+'APPROVED' by altering the "bugs" table.

+

+mysql> ALTER table bugs CHANGE bug_status bug_status

+    -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",

+    -> "VERIFIED", "APPROVED", "CLOSED") not null;

+

+    (note we can take three lines or more -- whatever you put in before the

+semicolon is evaluated as a single expression)

+

+Now if you do this:

+

+mysql> show columns from bugs;

+

+  you'll see that the bug_status field has an extra "APPROVED" enum that's

+available!  Cool thing, too, is that this is reflected on your query page as

+well -- you can query by the new status.  But how's it fit into the existing

+scheme of things?

+  Looks like you need to go back and look for instances of the word "verified"

+in the perl code for Bugzilla -- wherever you find "verified", change it to

+"approved" and you're in business (make sure that's a case-insensitive search).

+Although you can query by the enum field, you can't give something a status

+of "APPROVED" until you make the perl changes.   Note that this change I

+mentioned can also be done by editing checksetup.pl, which automates a lot of

+this.  But you need to know this stuff anyway, right?

+	
 
-	    This is well-documented here: 	    http://bugzilla.mozilla.org/show_bug.cgi?id=49862.  Ultimately, it's as easy
-	    as adding the "---" priority field to your localconfig file in the appropriate area,
-	    re-running checksetup.pl, and then changing the default priority in your browser using
-	    "editparams.cgi". 
-	  
Appendix C. Useful Patches and Utilities for Bugzilla
Are you looking for a way to put your Bugzilla into overdrive? Catch
+  some of the niftiest tricks here in this section.
A.8.4. C.1. Apache 
+    mod_rewrite
-	    What's the best way to submit patches?  What guidelines should I follow?
-	  
 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.
		  Enter a bug into bugzilla.mozilla.org for the "Bugzilla"Make it so if someone types 
+        http://www.foo.com/12345
-                  product.
-		
<VirtualHost 12.34.56.78>
+RewriteEngine On
+RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+</VirtualHost>
+
		  Upload your patch as a unified diff (having used "diff -u" against
-		  the current sources checked out of CVS),
-		  or new source file by clicking
-		  "Create a new attachment" link on the bug page you've just created, and
-		  include any descriptions of database changes you may make, into the bug
-		  ID you submitted in step #1.  Be sure and click the "Patch" checkbox
-		  to indicate the text you are sending is a patch!
-		There are many, many more things you can do with mod_rewrite.
+        Please refer to the mod_rewrite documentation at 
+        http://www.apache.org.
+        
C.2. Command-line Bugzilla Queries
		  Announce your patch and the associated URL
-		  (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
-		  the newsgroup (netscape.public.mozilla.webtools).  You'll get a really
-		  good, fairly immediate reaction to the implications of your patch,
-		  which will also give us an idea how well-received the change would
-		  be.
-		
There are a suite of Unix utilities for querying Bugzilla from the 
+    command line. They live in the 
+    contrib/cmdline 
+    directory. However, they
+    have not yet been updated to work with 2.16 (post-templatisation.).
+    There are three files - query.conf, 
+    buglist and bugs.
		  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.
-		
query.conf 
+    contains the mapping from options to field
+    names and comparison types. Quoted option names are "grepped" for, so it
+    should be easy to edit this file. Comments (#) have no effect; you must
+    make sure these lines do not contain any quoted "option".
		  Bask in the glory of the fact that you helped write the most successful
-		  open-source bug-tracking software on the planet :)
-		
buglist
+    is a shell script which submits a Bugzilla query and writes
+    the resulting HTML page to stdout. It supports both short options, (such
+    as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
+    "--reporter=bar"). If the first character of an option is not "-", it is
+    treated as if it were prefixed with "--default=".
The column list is taken from the COLUMNLIST environment variable.
+    This is equivalent to the "Change Columns" option when you list bugs in
+    buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
+    in your cookies file to see your current COLUMNLIST setting.
bugs is a simple shell script which calls
+    buglist and extracts the
+    bug numbers from the output. Adding the prefix
+    "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
+    a working link if any bugs are found. Counting bugs is easy. Pipe the
+    results through 
+    sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
+    
Akkana Peck says she has good results piping 
+    buglist output through 
+    w3m -T text/html -dump
+    
Appendix B. The Bugzilla Database
Appendix D. Bugzilla Variants and CompetitorsThis 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?I created this section to answer questions about Bugzilla competitors
+  and variants, then found a wonderful site which covers an awful lot of what
+  I wanted to discuss. Rather than quote it in its entirety, I'll simply
+  refer you here: 
+    http://linas.org/linux/pm.html
+  
B.1. Modifying Your Running System
D.1. Red Hat BugzillaBugzilla optimizes database lookups by storing all relatively
-      static information in the 
-      versioncache file, located in the 
-      data/
-      subdirectory under your installation directory.Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+    obsolete.  The newest version in use is based on version 2.17.1 and is in
+    the process of being integrated into the main Bugzilla source tree.  The
+    back-end is modified to work with PostgreSQL instead of MySQL and they have
+    custom templates to get their desired look and feel, but other than that it
+    is Bugzilla 2.17.1.  Dave Lawrence of Red Hat put forth a great deal of
+    effort to make sure that the changes he made could be integrated back into
+    the main tree. 
+    Bug
+    98304 exists to track this integration.
+    
If you make a change to the structural data in your database (the
-      versions table for example), or to the 
-      "constants"
-
-      encoded in defparams.pl, you will need to remove 
-      the cached content from the data directory (by doing a 
-      "rm data/versioncache"URL: 
+        http://bugzilla.redhat.com/bugzilla/
-
-      ), or your changes won't show up.
 versioncache 
-      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.
This section last updated 24 Dec 2002
B.2. MySQL Bugzilla Database Introduction
This information comes straight from my life. I was forced to learn
-    how Bugzilla organizes database because of nitpicky requests from users
-    for tiny changes in wording, rather than having people re-educate
-    themselves or figure out how to work our procedures around the tool. It
-    sucks, but it can and will happen to you, so learn how the schema works
-    and deal with it when it comes.
So, here you are with your brand-new installation of Bugzilla.
-    You've got MySQL set up, Apache working right, Perl DBI and DBD talking
-    to the database flawlessly. Maybe you've even entered a few test bugs to
-    make sure email's working; people seem to be notified of new bugs and
-    changes, and you can enter and edit bugs to your heart's content. Perhaps
-    you've gone through the trouble of setting up a gateway for people to
-    submit bugs to your database via email, have had a few people test it,
-    and received rave reviews from your beta testers.
What's the next thing you do? Outline a training strategy for your
-    development team, of course, and bring them up to speed on the new tool
-    you've labored over for hours.
Your first training session starts off very well! You have a
-    captive audience which seems enraptured by the efficiency embodied in
-    this thing called "Bugzilla". You are caught up describing the nifty
-    features, how people can save favorite queries in the database, set them
-    up as headers and footers on their pages, customize their layouts,
-    generate reports, track status with greater efficiency than ever before,
-    leap tall buildings with a single bound and rescue Jane from the clutches
-    of Certain Death!
But Certain Death speaks up -- a tiny voice, from the dark corners
-    of the conference room. "I have a concern," the voice hisses from the
-    darkness, "about the use of the word 'verified'.
The room, previously filled with happy chatter, lapses into
-    reverential silence as Certain Death (better known as the Vice President
-    of Software Engineering) continues. "You see, for two years we've used
-    the word 'verified' to indicate that a developer or quality assurance
-    engineer has confirmed that, in fact, a bug is valid. I don't want to
-    lose two years of training to a new software product. You need to change
-    the bug status of 'verified' to 'approved' as soon as possible. To avoid
-    confusion, of course."
D.2. Loki Bugzilla (Fenris)Oh no! Terror strikes your heart, as you find yourself mumbling
-    "yes, yes, I don't think that would be a problem," You review the changes
-    with Certain Death, and continue to jabber on, "no, it's not too big a
-    change. I mean, we have the source code, right? You know, 'Use the
-    Source, Luke' and all that... no problem," All the while you quiver
-    inside like a beached jellyfish bubbling, burbling, and boiling on a hot
-    Jamaican sand dune...Fenris was a fork from Bugzilla made by Loki Games; when
+    Loki went into receivership, it died. While Loki's other code lives on,
+    its custodians recommend Bugzilla for future bug-tracker deployments.
+    
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!
This section last updated 27 Jul 2002
B.2.1. Bugzilla Database Basics
If you were like me, at this point you're totally clueless about
-      the internals of MySQL, and if it weren't for this executive order from
-      the Vice President you couldn't care less about the difference between
-      a 
-      "bigint"
-
-      and a 
-      "tinyint"
-
-      entry in MySQL. I recommend you refer to the MySQL documentation,
-      available at 
-      MySQL.com
-
-      . Below are the basics you need to know about the Bugzilla database.
-      Check the chart above for more details.
D.3. Issuezilla        
Issuezilla was another fork from Bugzilla, made by collab.net and
+    hosted at tigris.org. It is also dead; the primary focus of bug-tracking 
+    at tigris.org is their Java-based bug-tracker, 
+    Scarab.
To connect to your database:
This section last updated 27 Jul 2002
D.4. Scarab
              bash#
-
-              mysql
-
-              -u root
-            Scarab is a new open source bug-tracking system built using Java
+    Servlet technology. It is currently at version 1.0 beta 13.
If this works without asking you for a password, 
-            shame on you
-
-            ! You should have locked your security down like the installation
-            instructions told you to. You can find details on locking down
-            your database in the Bugzilla FAQ in this directory (under
-            "Security"), or more robust security generalities in the 
-            URL: 
+    MySQL
-            searchable documentation.            
-            
You should now be at a prompt that looks like this:
              mysql>
-            
At the prompt, if 
-            "bugs"
-
-            is the name you chose in the
-            localconfig
-
-            file for your Bugzilla database, type:
              mysql
-
-              use bugs;
-            http://scarab.tigris.org
-      
This section last updated 18 Jan 2003
B.2.1.1. Bugzilla Database Tables
Imagine your MySQL database as a series of spreadsheets, and
-        you won't be too far off. If you use this command:
          mysql>
-          show tables from bugs;
-        
D.5. Perforce SCMyou'll be able to see the names of all the 
-        Although Perforce isn't really a bug tracker, it can be used as
+    such through the "spreadsheets""jobs"
-        (tables) in your database.
From the command issued above, ou should have some
-	  output that looks like this:
-+-------------------+
-| Tables in bugs    |
-+-------------------+
-| attachments       |
-| bugs              |
-| bugs_activity     |
-| cc                |
-| components        |
-| dependencies      |
-| fielddefs         |
-| groups            |
-| keyworddefs       |
-| keywords          |
-| logincookies      |
-| longdescs         |
-| milestones        |
-| namedqueries      |
-| products          |
-| profiles          |
-| profiles_activity |
-| tokens            |
-| versions          |
-| votes             |
-| watch             |
-+-------------------+
-URL: 
+        http://www.perforce.com/perforce/technotes/note052.html
+    
-


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

-

-attachments: This table stores all attachments to bugs.  It tends to be your

-largest table, yet also generally has the fewest entries because file

-attachments are so (relatively) large.

-

-bugs:  This is the core of your system.  The bugs table stores most of the

-current information about a bug, with the exception of the info stored in the

-other tables.

-

-bugs_activity:  This stores information regarding what changes are made to bugs

-when -- a history file.

-

-cc:  This tiny table simply stores all the CC information for any bug which has

-any entries in the CC field of the bug.  Note that, like most other tables in

-Bugzilla, it does not refer to users by their user names, but by their unique

-userid, stored as a primary key in the profiles table.

-

-components: This stores the programs and components (or products and

-components, in newer Bugzilla parlance) for Bugzilla.  Curiously, the "program"

-(product) field is the full name of the product, rather than some other unique

-identifier, like bug_id and user_id are elsewhere in the database.

-

-dependencies: Stores data about those cool dependency trees.

-

-fielddefs:  A nifty table that defines other tables.  For instance, when you

-submit a form that changes the value of "AssignedTo" this table allows

-translation to the actual field name "assigned_to" for entry into MySQL.

-

-groups:  defines bitmasks for groups.  A bitmask is a number that can uniquely

-identify group memberships.  For instance, say the group that is allowed to

-tweak parameters is assigned a value of "1", the group that is allowed to edit

-users is assigned a "2", and the group that is allowed to create new groups is

-assigned the bitmask of "4".  By uniquely combining the group bitmasks (much

-like the chmod command in UNIX,) you can identify a user is allowed to tweak

-parameters and create groups, but not edit users, by giving him a bitmask of

-"5", or a user allowed to edit users and create groups, but not tweak

-parameters, by giving him a bitmask of "6" Simple, huh?

-  If this makes no sense to you, try this at the mysql prompt:

-mysql> select * from groups;

-  You'll see the list, it makes much more sense that way.

-

-keyworddefs:  Definitions of keywords to be used

-

-keywords: Unlike what you'd think, this table holds which keywords are

-associated with which bug id's.

-

-logincookies: This stores every login cookie ever assigned to you for every

-machine you've ever logged into Bugzilla from.  Curiously, it never does any

-housecleaning -- I see cookies in this file I've not used for months.  However,

-since Bugzilla never expires your cookie (for convenience' sake), it makes

-sense.

-

-longdescs:  The meat of bugzilla -- here is where all user comments are stored!

-You've only got 2^24 bytes per comment (it's a mediumtext field), so speak

-sparingly -- that's only the amount of space the Old Testament from the Bible

-would take (uncompressed, 16 megabytes).  Each comment is keyed to the

-bug_id to which it's attached, so the order is necessarily chronological, for

-comments are played back in the order in which they are received.

-

-milestones:  Interesting that milestones are associated with a specific product

-in this table, but Bugzilla does not yet support differing milestones by

-product through the standard configuration interfaces.

-

-namedqueries:  This is where everybody stores their "custom queries".  Very

-cool feature; it beats the tar out of having to bookmark each cool query you

-construct.

-

-products:  What products you have, whether new bug entries are allowed for the

-product, what milestone you're working toward on that product, votes, etc.  It

-will be nice when the components table supports these same features, so you

-could close a particular component for bug entry without having to close an

-entire product...

-

-profiles:  Ahh, so you were wondering where your precious user information was

-stored?  Here it is!  With the passwords in plain text for all to see! (but

-sshh... don't tell your users!)

-

-profiles_activity:  Need to know who did what when to who's profile?  This'll

-tell you, it's a pretty complete history.

-

-versions:  Version information for every product

-

-votes:  Who voted for what when

-

-watch:  Who (according to userid) is watching who's bugs (according to their

-userid).

-

-

-===

-THE DETAILS

-===

-

-  Ahh, so you're wondering just what to do with the information above?  At the

-mysql prompt, you can view any information about the columns in a table with

-this command (where "table" is the name of the table you wish to view):

-

-mysql> show columns from table;

-

-  You can also view all the data in a table with this command:

-

-mysql> select * from table;

-

-  -- note: this is a very bad idea to do on, for instance, the "bugs" table if

-you have 50,000 bugs.  You'll be sitting there a while until you ctrl-c or

-50,000 bugs play across your screen.

-

-  You can limit the display from above a little with the command, where

-"column" is the name of the column for which you wish to restrict information:

-

-mysql> select * from table where (column = "some info");

-

-  -- or the reverse of this

-

-mysql> select * from table where (column != "some info");

-

-  Let's take our example from the introduction, and assume you need to change

-the word "verified" to "approved" in the resolution field.  We know from the

-above information that the resolution is likely to be stored in the "bugs"

-table. Note we'll need to change a little perl code as well as this database

-change, but I won't plunge into that in this document. Let's verify the

-information is stored in the "bugs" table:

-

-mysql> show columns from bugs

-

-  (exceedingly long output truncated here)

-| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||

-

-  Sorry about that long line.  We see from this that the "bug status" column is

-an "enum field", which is a MySQL peculiarity where a string type field can

-only have certain types of entries.  While I think this is very cool, it's not

-standard SQL.  Anyway, we need to add the possible enum field entry

-'APPROVED' by altering the "bugs" table.

-

-mysql> ALTER table bugs CHANGE bug_status bug_status

-    -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",

-    -> "VERIFIED", "APPROVED", "CLOSED") not null;

-

-    (note we can take three lines or more -- whatever you put in before the

-semicolon is evaluated as a single expression)

-

-Now if you do this:

-

-mysql> show columns from bugs;

-

-  you'll see that the bug_status field has an extra "APPROVED" enum that's

-available!  Cool thing, too, is that this is reflected on your query page as

-well -- you can query by the new status.  But how's it fit into the existing

-scheme of things?

-  Looks like you need to go back and look for instances of the word "verified"

-in the perl code for Bugzilla -- wherever you find "verified", change it to

-"approved" and you're in business (make sure that's a case-insensitive search).

-Although you can query by the enum field, you can't give something a status

-of "APPROVED" until you make the perl changes.   Note that this change I

-mentioned can also be done by editing checksetup.pl, which automates a lot of

-this.  But you need to know this stuff anyway, right?

-	
This section last updated 27 Jul 2002
D.6. SourceForge
SourceForge is a way of coordinating geographically
+    distributed free software and open source projects over the Internet.
+    It has a built-in bug tracker, but it's not highly thought of.
URL: 
+        http://www.sourceforge.net
+    
This section last updated 27 Jul 2002
Appendix E. GNU Free Documentation License
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
+    Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
+    distribute verbatim copies of this license document, but changing it is
+    not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
+    written document "free" in the sense of freedom: to assure everyone the
+    effective freedom to copy and redistribute it, with or without modifying
+    it, either commercially or noncommercially. Secondarily, this License
+    preserves for the author and publisher a way to get credit for their
+    work, while not being considered responsible for modifications made by
+    others.
This License is a kind of "copyleft", which means that derivative
+    works of the document must themselves be free in the same sense. It
+    complements the GNU General Public License, which is a copyleft license
+    designed for free software.
We have designed this License in order to use it for manuals for
+    free software, because free software needs free documentation: a free
+    program should come with manuals providing the same freedoms that the
+    software does. But this License is not limited to software manuals; it
+    can be used for any textual work, regardless of subject matter or whether
+    it is published as a printed book. We recommend this License principally
+    for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work that contains a
+    notice placed by the copyright holder saying it can be distributed under
+    the terms of this License. The "Document", below, refers to any such
+    manual or work. Any member of the public is a licensee, and is addressed
+    as "you".
A "Modified Version" of the Document means any work containing the
+    Document or a portion of it, either copied verbatim, or with
+    modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section
+    of the Document that deals exclusively with the relationship of the
+    publishers or authors of the Document to the Document's overall subject
+    (or to related matters) and contains nothing that could fall directly
+    within that overall subject. (For example, if the Document is in part a
+    textbook of mathematics, a Secondary Section may not explain any
+    mathematics.) The relationship could be a matter of historical connection
+    with the subject or with related matters, or of legal, commercial,
+    philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose
+    titles are designated, as being those of Invariant Sections, in the
+    notice that says that the Document is released under this License.
The "Cover Texts" are certain short passages of text that are
+    listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
+    that the Document is released under this License.
A "Transparent" copy of the Document means a machine-readable copy,
+    represented in a format whose specification is available to the general
+    public, whose contents can be viewed and edited directly and
+    straightforwardly with generic text editors or (for images composed of
+    pixels) generic paint programs or (for drawings) some widely available
+    drawing editor, and that is suitable for input to text formatters or for
+    automatic translation to a variety of formats suitable for input to text
+    formatters. A copy made in an otherwise Transparent file format whose
+    markup has been designed to thwart or discourage subsequent modification
+    by readers is not Transparent. A copy that is not "Transparent" is called
+    "Opaque".
Examples of suitable formats for Transparent copies include plain
+    ASCII without markup, Texinfo input format, LaTeX input format, SGML or
+    XML using a publicly available DTD, and standard-conforming simple HTML
+    designed for human modification. Opaque formats include PostScript, PDF,
+    proprietary formats that can be read and edited only by proprietary word
+    processors, SGML or XML for which the DTD and/or processing tools are not
+    generally available, and the machine-generated HTML produced by some word
+    processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
+    plus such following pages as are needed to hold, legibly, the material
+    this License requires to appear in the title page. For works in formats
+    which do not have any title page as such, "Title Page" means the text
+    near the most prominent appearance of the work's title, preceding the
+    beginning of the body of the text.
Appendix C. Useful Patches and Utilities for Bugzilla
2. VERBATIM COPYINGAre you looking for a way to put your Bugzilla into overdrive? Catch
-  some of the niftiest tricks here in this section.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.
C.1. Apache 
-    mod_rewrite
-
-    magic
3. COPYING IN QUANTITYIf you publish printed copies of the Document numbering more than
+    100, and the Document's license notice requires Cover Texts, you must
+    enclose the copies in covers that carry, clearly and legibly, all these
+    Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
+    on the back cover. Both covers must also clearly and legibly identify you
+    as the publisher of these copies. The front cover must present the full
+    title with all words of the title equally prominent and visible. You may
+    add other material on the covers in addition. Copying with changes
+    limited to the covers, as long as they preserve the title of the Document
+    and satisfy these conditions, can be treated as verbatim copying in other
+    respects.
If the required texts for either cover are too voluminous to fit
+    legibly, you should put the first ones listed (as many as fit reasonably)
+    on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document
+    numbering more than 100, you must either include a machine-readable
+    Transparent copy along with each Opaque copy, or state in or with each
+    Opaque copy a publicly-accessible computer-network location containing a
+    complete Transparent copy of the Document, free of added material, which
+    the general network-using public has access to download anonymously at no
+    charge using public-standard network protocols. If you use the latter
+    option, you must take reasonably prudent steps, when you begin
+    distribution of Opaque copies in quantity, to ensure that this
+    Transparent copy will remain thus accessible at the stated location until
+    at least one year after the last time you distribute an Opaque copy
+    (directly or through your agents or retailers) of that edition to the
+    public.
It is requested, but not required, that you contact the authors of
+    the Document well before redistributing any large number of copies, to
+    give them a chance to provide you with an updated version of the
+    Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
+    under the conditions of sections 2 and 3 above, provided that you release
+    the Modified Version under precisely this License, with the Modified
+    Version filling the role of the Document, thus licensing distribution and
+    modification of the Modified Version to whoever possesses a copy of it.
+    In addition, you must do these things in the Modified Version:
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.
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).
State on the Title page the name of the publisher of the
+        Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications
+        adjacent to the other copyright notices.
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.
Preserve in that license notice the full lists of Invariant
+        Sections and required Cover Texts given in the Document's license
+        notice.
Include an unaltered copy of this License.
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.
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.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.
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.
Make it so if someone types 
-        http://www.foo.com/12345
-
-        , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
-        setting up your VirtualHost section for Bugzilla with a rule like
-        this:
<VirtualHost 12.34.56.78>
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-</VirtualHost>
-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.
There are many, many more things you can do with mod_rewrite.
-        Please refer to the mod_rewrite documentation at 
-        http://www.apache.org.
-        Delete any section entitled "Endorsements". Such a section may
+        not be included in the Modified Version.
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.
C.2. Command-line Bugzilla Queries
There are a suite of Unix utilities for querying Bugzilla from the 
-    command line. They live in the 
-    contrib/cmdline 
-    directory. However, they
-    have not yet been updated to work with 2.16 (post-templatisation.).
-    There are three files - query.conf, 
-    buglist and bugs.
query.conf 
-    contains the mapping from options to field
-    names and comparison types. Quoted option names are "grepped" for, so it
-    should be easy to edit this file. Comments (#) have no effect; you must
-    make sure these lines do not contain any quoted "option".
buglist
-    is a shell script which submits a Bugzilla query and writes
-    the resulting HTML page to stdout. It supports both short options, (such
-    as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
-    "--reporter=bar"). If the first character of an option is not "-", it is
-    treated as if it were prefixed with "--default=".
5. COMBINING DOCUMENTSThe column list is taken from the COLUMNLIST environment variable.
-    This is equivalent to the "Change Columns" option when you list bugs in
-    buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
-    in your cookies file to see your current COLUMNLIST setting.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.
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"}'
-    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.
Akkana Peck says she has good results piping 
-    buglist output through 
-    w3m -T text/html -dump
-    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."
Appendix D. Bugzilla Variants and Competitors
6. COLLECTIONS OF DOCUMENTSI created this section to answer questions about Bugzilla competitors
-  and variants, then found a wonderful site which covers an awful lot of what
-  I wanted to discuss. Rather than quote it in its entirety, I'll simply
-  refer you here: 
-    http://linas.org/linux/pm.html
-  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.
D.1. Red Hat Bugzilla
Red Hat's old fork of Bugzilla which was based on version 2.8 is now
-    obsolete.  The newest version in use is based on version 2.17.1 and is in
-    the process of being integrated into the main Bugzilla source tree.  The
-    back-end is modified to work with PostgreSQL instead of MySQL and they have
-    custom templates to get their desired look and feel, but other than that it
-    is Bugzilla 2.17.1.  Dave Lawrence of Red Hat put forth a great deal of
-    effort to make sure that the changes he made could be integrated back into
-    the main tree. 
-    Bug
-    98304 exists to track this integration.
-    
7. AGGREGATION WITH INDEPENDENT WORKSURL: 
-        http://bugzilla.redhat.com/bugzilla/
-    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.
This section last updated 24 Dec 2002If 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.
D.2. Loki Bugzilla (Fenris)
Fenris was a fork from Bugzilla made by Loki Games; when
-    Loki went into receivership, it died. While Loki's other code lives on,
-    its custodians recommend Bugzilla for future bug-tracker deployments.
-    
8. TRANSLATIONThis section last updated 27 Jul 2002Translation 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.
D.3. Issuezilla
Issuezilla was another fork from Bugzilla, made by collab.net and
-    hosted at tigris.org. It is also dead; the primary focus of bug-tracking 
-    at tigris.org is their Java-based bug-tracker, 
-    Scarab.
9. TERMINATIONThis section last updated 27 Jul 2002You 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.
D.4. Scarab
10. FUTURE REVISIONS OF THIS LICENSEScarab is a new open source bug-tracking system built using Java
-    Serlet technology. It is currently at version 1.0 beta 8.
URL: 
+>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://scarab.tigris.org    http://www.gnu.org/copyleft/
-    
This section last updated 27 Jul 2002Each 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.
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as
-    such through the "jobs"
-    functionality.
URL: 
-        http://www.perforce.com/perforce/technotes/note052.html
-    
-    
How to use this License for your documentsThis section last updated 27 Jul 2002
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:
D.6. SourceForge
SourceForge is a way of coordinating geographically
-    distributed free software and open source projects over the Internet.
-    It has a built-in bug tracker, but it's not highly thought of.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".
URL: 
-        http://www.sourceforge.net
-    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.
This section last updated 27 Jul 2002If 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.
0-9, high ascii
AApache
In this context, Apache is the web server most commonly used
-        for serving up 
-        Bugzilla
-
+        for serving up Bugzilla 
         pages. Contrary to popular belief, the apache web server has nothing
         to do with the ancient and noble Native American tribe, but instead
         derived its name from the fact that it was 
@@ -13576,14 +12810,123 @@ CLASS="glossterm"
 CLASS="QUOTE"
 >"a patchy"
-
         version of the original 
         NCSA
-
         world-wide-web server.
Useful Directives when configuring Bugzilla
AddHandler
Tell Apache that it's OK to run CGI scripts.
AllowOverride, Options
These directives are used to tell Apache many things about
+              the directory they apply to. For Bugzilla's purposes, we need
+              them to allow script execution and .htaccess
+              overrides.
+              
DirectoryIndex
Used to tell Apache what files are indexes. If you can
+              not add index.cgi to the list of valid files,
+              you'll need to set $index_html to
+              1 in localconfig so
+              ./checksetup.pl will create an
+              index.html that redirects to
+              index.cgi.
+              
ScriptInterpreterSource
Used when running Apache on windows so the shebang line
+              doesn't have to be changed in every Bugzilla script.
+              
For more information about how to configure Apache for Bugzilla,
+        see Section 4.4.1.
+        
Common Gateway Interface
 (CGI)CGI is an acronym for Common Gateway Interface. This is
+        a standard for interfacing an external application with a web server. Bugzilla
+        is an example of a CGI application.
+        
GGroups
J
JavaScript
JavaScript is cool, we should talk about it.
+        
M
Tool Command Language
 (TCL)TCL is an open source scripting language available for Windows,
+        Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
+        never released. The first release of Bugzilla was 2.0, which was when
+        it was ported to perl.
+        
5.7.1. What to Edit
5.7.2. How To Edit Templates
5.7.3. Template Formats
5.7.4. Particular Templates
1.1. Copyright InformationAppendix E.
       
4.2.1. Dependency Charts
4.2.2. Bug Graphs
4.2.3. The Whining Cron
NextWin32 Installation NotesOS Specific Installation Notes
--Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla TeamCopyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team 1.1.1. GNU Free Documentation License
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
-    Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
-    distribute verbatim copies of this license document, but changing it is
-    not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
-    written document "free" in the sense of freedom: to assure everyone the
-    effective freedom to copy and redistribute it, with or without modifying
-    it, either commercially or noncommercially. Secondarily, this License
-    preserves for the author and publisher a way to get credit for their
-    work, while not being considered responsible for modifications made by
-    others.
This License is a kind of "copyleft", which means that derivative
-    works of the document must themselves be free in the same sense. It
-    complements the GNU General Public License, which is a copyleft license
-    designed for free software.
We have designed this License in order to use it for manuals for
-    free software, because free software needs free documentation: a free
-    program should come with manuals providing the same freedoms that the
-    software does. But this License is not limited to software manuals; it
-    can be used for any textual work, regardless of subject matter or whether
-    it is published as a printed book. We recommend this License principally
-    for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work that contains a
-    notice placed by the copyright holder saying it can be distributed under
-    the terms of this License. The "Document", below, refers to any such
-    manual or work. Any member of the public is a licensee, and is addressed
-    as "you".
A "Modified Version" of the Document means any work containing the
-    Document or a portion of it, either copied verbatim, or with
-    modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section
-    of the Document that deals exclusively with the relationship of the
-    publishers or authors of the Document to the Document's overall subject
-    (or to related matters) and contains nothing that could fall directly
-    within that overall subject. (For example, if the Document is in part a
-    textbook of mathematics, a Secondary Section may not explain any
-    mathematics.) The relationship could be a matter of historical connection
-    with the subject or with related matters, or of legal, commercial,
-    philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose
-    titles are designated, as being those of Invariant Sections, in the
-    notice that says that the Document is released under this License.
The "Cover Texts" are certain short passages of text that are
-    listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
-    that the Document is released under this License.
A "Transparent" copy of the Document means a machine-readable copy,
-    represented in a format whose specification is available to the general
-    public, whose contents can be viewed and edited directly and
-    straightforwardly with generic text editors or (for images composed of
-    pixels) generic paint programs or (for drawings) some widely available
-    drawing editor, and that is suitable for input to text formatters or for
-    automatic translation to a variety of formats suitable for input to text
-    formatters. A copy made in an otherwise Transparent file format whose
-    markup has been designed to thwart or discourage subsequent modification
-    by readers is not Transparent. A copy that is not "Transparent" is called
-    "Opaque".
Examples of suitable formats for Transparent copies include plain
-    ASCII without markup, Texinfo input format, LaTeX input format, SGML or
-    XML using a publicly available DTD, and standard-conforming simple HTML
-    designed for human modification. Opaque formats include PostScript, PDF,
-    proprietary formats that can be read and edited only by proprietary word
-    processors, SGML or XML for which the DTD and/or processing tools are not
-    generally available, and the machine-generated HTML produced by some word
-    processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
-    plus such following pages as are needed to hold, legibly, the material
-    this License requires to appear in the title page. For works in formats
-    which do not have any title page as such, "Title Page" means the text
-    near the most prominent appearance of the work's title, preceding the
-    beginning of the body of the text.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
-    commercially or noncommercially, provided that this License, the
-    copyright notices, and the license notice saying this License applies to
-    the Document are reproduced in all copies, and that you add no other
-    conditions whatsoever to those of this License. You may not use technical
-    measures to obstruct or control the reading or further copying of the
-    copies you make or distribute. However, you may accept compensation in
-    exchange for copies. If you distribute a large enough number of copies
-    you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above,
-    and you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies of the Document numbering more than
-    100, and the Document's license notice requires Cover Texts, you must
-    enclose the copies in covers that carry, clearly and legibly, all these
-    Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
-    on the back cover. Both covers must also clearly and legibly identify you
-    as the publisher of these copies. The front cover must present the full
-    title with all words of the title equally prominent and visible. You may
-    add other material on the covers in addition. Copying with changes
-    limited to the covers, as long as they preserve the title of the Document
-    and satisfy these conditions, can be treated as verbatim copying in other
-    respects.
If the required texts for either cover are too voluminous to fit
-    legibly, you should put the first ones listed (as many as fit reasonably)
-    on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document
-    numbering more than 100, you must either include a machine-readable
-    Transparent copy along with each Opaque copy, or state in or with each
-    Opaque copy a publicly-accessible computer-network location containing a
-    complete Transparent copy of the Document, free of added material, which
-    the general network-using public has access to download anonymously at no
-    charge using public-standard network protocols. If you use the latter
-    option, you must take reasonably prudent steps, when you begin
-    distribution of Opaque copies in quantity, to ensure that this
-    Transparent copy will remain thus accessible at the stated location until
-    at least one year after the last time you distribute an Opaque copy
-    (directly or through your agents or retailers) of that edition to the
-    public.
It is requested, but not required, that you contact the authors of
-    the Document well before redistributing any large number of copies, to
-    give them a chance to provide you with an updated version of the
-    Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
-    under the conditions of sections 2 and 3 above, provided that you release
-    the Modified Version under precisely this License, with the Modified
-    Version filling the role of the Document, thus licensing distribution and
-    modification of the Modified Version to whoever possesses a copy of it.
-    In addition, you must do these things in the Modified Version:
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.
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).
State on the Title page the name of the publisher of the
-        Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications
-        adjacent to the other copyright notices.
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.
Preserve in that license notice the full lists of Invariant
-        Sections and required Cover Texts given in the Document's license
-        notice.
Include an unaltered copy of this License.
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.
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.
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.
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.
Delete any section entitled "Endorsements". Such a section may
-        not be included in the Modified Version.
Do not retitle any existing section as "Endorsements" or to
-        conflict in title with any Invariant Section.
If the Modified Version includes new front-matter sections or
-    appendices that qualify as Secondary Sections and contain no material
-    copied from the Document, you may at your option designate some or all of
-    these sections as invariant. To do this, add their titles to the list of
-    Invariant Sections in the Modified Version's license notice. These titles
-    must be distinct from any other section titles.
You may add a section entitled "Endorsements", provided it contains
-    nothing but endorsements of your Modified Version by various parties--for
-    example, statements of peer review or that the text has been approved by
-    an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
-    and a passage of up to 25 words as a Back-Cover Text, to the end of the
-    list of Cover Texts in the Modified Version. Only one passage of
-    Front-Cover Text and one of Back-Cover Text may be added by (or through
-    arrangements made by) any one entity. If the Document already includes a
-    cover text for the same cover, previously added by you or by arrangement
-    made by the same entity you are acting on behalf of, you may not add
-    another; but you may replace the old one, on explicit permission from the
-    previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
-    License give permission to use their names for publicity for or to assert
-    or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under
-    this License, under the terms defined in section 4 above for modified
-    versions, provided that you include in the combination all of the
-    Invariant Sections of all of the original documents, unmodified, and list
-    them all as Invariant Sections of your combined work in its license
-    notice.
The combined work need only contain one copy of this License, and
-    multiple identical Invariant Sections may be replaced with a single copy.
-    If there are multiple Invariant Sections with the same name but different
-    contents, make the title of each such section unique by adding at the end
-    of it, in parentheses, the name of the original author or publisher of
-    that section if known, or else a unique number. Make the same adjustment
-    to the section titles in the list of Invariant Sections in the license
-    notice of the combined work.
In the combination, you must combine any sections entitled
-    "History" in the various original documents, forming one section entitled
-    "History"; likewise combine any sections entitled "Acknowledgements", and
-    any sections entitled "Dedications". You must delete all sections
-    entitled "Endorsements."
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other
-    documents released under this License, and replace the individual copies
-    of this License in the various documents with a single copy that is
-    included in the collection, provided that you follow the rules of this
-    License for verbatim copying of each of the documents in all other
-    respects.
You may extract a single document from such a collection, and
-    distribute it individually under this License, provided you insert a copy
-    of this License into the extracted document, and follow this License in
-    all other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
-    separate and independent documents or works, in or on a volume of a
-    storage or distribution medium, does not as a whole count as a Modified
-    Version of the Document, provided no compilation copyright is claimed for
-    the compilation. Such a compilation is called an "aggregate", and this
-    License does not apply to the other self-contained works thus compiled
-    with the Document, on account of their being thus compiled, if they are
-    not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
-    copies of the Document, then if the Document is less than one quarter of
-    the entire aggregate, the Document's Cover Texts may be placed on covers
-    that surround only the Document within the aggregate. Otherwise they must
-    appear on covers around the whole aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may
-    distribute translations of the Document under the terms of section 4.
-    Replacing Invariant Sections with translations requires special
-    permission from their copyright holders, but you may include translations
-    of some or all Invariant Sections in addition to the original versions of
-    these Invariant Sections. You may include a translation of this License
-    provided that you also include the original English version of this
-    License. In case of a disagreement between the translation and the
-    original English version of this License, the original English version
-    will prevail.
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document
-    except as expressly provided for under this License. Any other attempt to
-    copy, modify, sublicense or distribute the Document is void, and will
-    automatically terminate your rights under this License. However, parties
-    who have received copies, or rights, from you under this License will not
-    have their licenses terminated so long as such parties remain in full
-    compliance.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
-    the GNU Free Documentation License from time to time. Such new versions
-    will be similar in spirit to the present version, but may differ in
-    detail to address new problems or concerns. See 
-        http://www.gnu.org/copyleft/
-
-    .
Each version of the License is given a distinguishing version
-    number. If the Document specifies that a particular numbered version of
-    this License "or any later version" applies to it, you have the option of
-    following the terms and conditions either of that specified version or of
-    any later version that has been published (not as a draft) by the Free
-    Software Foundation. If the Document does not specify a version number of
-    this License, you may choose any version ever published (not as a draft)
-    by the Free Software Foundation.
How to use this License for your documents
To use this License in a document you have written, include a copy
-    of the License in the document and put the following copyright and
-    license notices just after the title page:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
-      distribute and/or modify this document under the terms of the GNU Free
-      Documentation License, Version 1.1 or any later version published by
-      the Free Software Foundation; with the Invariant Sections being LIST
-      THEIR TITLES, with the Front-Cover Texts being LIST, and with the
-      Back-Cover Texts being LIST. A copy of the license is included in the
-      section entitled "GNU Free Documentation License".
If you have no Invariant Sections, write "with no Invariant
-    Sections" instead of saying which ones are invariant. If you have no
-    Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
-    Texts being LIST"; likewise for Back-Cover Texts.
If your document contains nontrivial examples of program code, we
-    recommend releasing these examples in parallel under your choice of free
-    software license, such as the GNU General Public License, to permit their
-    use in free software.
5.7.1. What to Edit
5.7.2. How To Edit Templates
5.7.3. Template Formats
5.7.4. Particular Templates
B.2.1. Bugzilla Database Basics
B.2.1.1. Bugzilla Database Tables
Next
A.1.1. 	    Where can I find information about Bugzilla?
A.1.2. 	    What license is Bugzilla distributed under?
 	  
A.1.3. 	    How do I get commercial support for Bugzilla?
 	  
A.1.4. 	    What major companies or projects are currently using Bugzilla
 	    for bug-tracking?
 	  
A.1.5. 	    Who maintains Bugzilla?
 	  
A.1.6. 	    How does Bugzilla stack up against other bug-tracking databases?
 	  
A.1.7. 	    Why doesn't Bugzilla offer this or that feature or compatibility
 	    with this other tracking software?
 	  
A.1.8. 	    Why MySQL?  I'm interested in seeing Bugzilla run on
 	    Oracle/Sybase/Msql/PostgreSQL/MSSQL.
 	  
A.1.9. 	    Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
 	    "/usr/bin/perl" or something else?
 	  
A.1.10. 	    Is there an easy way to change the Bugzilla cookie name?
 	  
A.2.1. 	    Is Bugzilla web-based, or do you have to have specific software or
 	    a specific operating system on your machine?
 	  
A.2.2. 	    Can Bugzilla integrate with
 	    Perforce (SCM software)?
 	  
A.2.3. 	    Does Bugzilla allow the user to track multiple projects?
 	  
A.2.4. 	    If I am on many projects, and search for all bugs assigned to me, will
 	    Bugzilla list them for me and allow me to sort by project, severity etc?
 	  
A.2.5. 	    Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
 	    are there any that are NOT allowed?
 	  
A.2.6. 	    Does Bugzilla allow us to define our own priorities and levels? Do we
 	    have complete freedom to change the labels of fields and format of them, and
 	    the choice of acceptable values?
@@ -201,35 +201,35 @@ HREF="faq.html#AEN1927"
 >
A.2.7. 	    Does Bugzilla provide any reporting features, metrics, graphs, etc? You
 	    know, the type of stuff that management likes to see. :)
 	  
A.2.8. 	    Is there email notification and if so, what do you see when you get an
 	    email?
 	  
A.2.9. 	    Can email notification be set up to send to multiple
 	    people, some on the To List, CC List, BCC List etc?
 	  
A.2.10. 	    Do users have to have any particular
 	    type of email application?
 	  
A.2.11. 	    Does Bugzilla allow data to be imported and exported? If I had outsiders
 	    write up a bug report using a MS Word bug template, could that template be
 	    imported into "matching" fields? If I wanted to take the results of a query
@@ -238,28 +238,28 @@ HREF="faq.html#AEN1958"
 >
A.2.12. 	    Has anyone converted Bugzilla to another language to be used in other
 	    countries? Is it localizable?
 	  
A.2.13. 	    Can a user create and save reports? Can they do this in Word format?
 	    Excel format?
 	  
A.2.14. 	    Does Bugzilla have the ability to search by word, phrase, compound
 	    search?
 	  
A.2.15. 	     Does Bugzilla provide record locking when there is simultaneous access
 	    to the same bug? Does the second person get a notice that the bug is in use
 	    or how are they notified?
@@ -267,19 +267,19 @@ HREF="faq.html#AEN1987"
 >
A.2.16. 	    Are there any backup features provided?
 	  
A.2.17. 	    Can users be on the system while a backup is in progress?
 	  
A.2.18. 	    What type of human resources are needed to be on staff to install and
 	    maintain Bugzilla? Specifically, what type of skills does the person need to
 	    have? I need to find out if we were to go with Bugzilla, what types of
@@ -289,7 +289,7 @@ HREF="faq.html#AEN2003"
 >
A.2.19. 	    What time frame are we looking at if we decide to hire people to install
 	    and maintain the Bugzilla? Is this something that takes hours or weeks to
 	    install and a couple of hours per week to maintain and customize or is this
@@ -299,7 +299,7 @@ HREF="faq.html#AEN2009"
 >
A.2.20. 	    Is there any licensing fee or other fees for using Bugzilla? Any
 	    out-of-pocket cost other than the bodies needed as identified above?
 	  A.3.1. 	    How do I completely disable MySQL security if it's giving me problems
 	    (I've followed the instructions in the installation section of this guide)?
 	  
A.3.2. 	    Are there any security problems with Bugzilla?
 	  
A.3.3. 	    I've implemented the security fixes mentioned in Chris Yeh's security
 	    advisory of 5/10/2000 advising not to run MySQL as root, and am running into
 	    problems with MySQL no longer working correctly.
@@ -345,48 +345,48 @@ HREF="faq.html#faq-email"
 >A.4.1. 	    I have a user who doesn't want to receive any more email from Bugzilla.
 	    How do I stop it entirely for this user?
 	  
A.4.2. 	    I'm evaluating/testing Bugzilla, and don't want it to send email to
 	    anyone but me. How do I do it?
 	  
A.4.3. 	    I want whineatnews.pl to whine at something more, or other than, only new
 	    bugs. How do I do it?
 	  
A.4.4. 	    I don't like/want to use Procmail to hand mail off to bug_email.pl.
 	    What alternatives do I have?
 	  
A.4.5. 	    How do I set up the email interface to submit/change bugs via email?
 	  
A.4.6. 	    Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
 	    What gives?
 	  
A.4.7. 	     How come email from Bugzilla changes never reaches me?
 	  
A.5.1. 	    I've heard Bugzilla can be used with Oracle?
 	  
A.5.2. 	    I think my database might be corrupted, or contain invalid entries. What
 	    do I do?
 	  
A.5.3. 	    I want to manually edit some entries in my database. How?
 	  
A.5.4. 	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
 	    connect.
 	  
A.5.5. 	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
 	  A.6.1. 	    What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
 	  
A.6.2. 	    Is there a "Bundle::Bugzilla" equivalent for Win32?
 	  
A.6.3. 	    CGI's are failing with a "something.cgi is not a valid Windows NT
 	    application" error. Why?
 	  
A.6.4. 	    I'm having trouble with the perl modules for NT not being able to talk to
 	    to the database.
 	  A.7.1. 	    How do I change my user name (email address) in Bugzilla?
 	  
A.7.2. 	    The query page is very confusing.  Isn't there a simpler way to query?
 	  
A.7.3. 	    I'm confused by the behavior of the "accept" button in the Show Bug form.
 	    Why doesn't it assign the bug to me when I accept it?
 	  
A.7.4. 	    I can't upload anything into the database via the "Create Attachment"
 	    link.  What am I doing wrong?
 	  
A.7.5. 	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  
A.8.1. 	    What kind of style should I use for templatization?
 	  
A.8.2. 	    What bugs are in Bugzilla right now?
 	  
A.8.3. 	    How can I change the default priority to a null value?  For instance, have the default
 	    priority be "---" instead of "P2"?
 	  
A.8.4. 	    What's the best way to submit patches?  What guidelines should I follow?
 	  
A.1.1. 
A.1.2. 
A.1.3. 
A.1.4. 
A.1.5. 
A.1.6. 
A.1.7. 
A.1.8. 
A.1.9. 
A.1.10. 
A.2.1. 
A.2.2. 
A.2.3. 
A.2.4. 
A.2.5. 
A.2.6. 
A.2.7. 
A.2.8. 
A.2.9. 
A.2.10. 
A.2.11. 
A.2.12. 
A.2.13. 
A.2.14. 
A.2.15. 
A.2.16. 
A.2.17. 
A.2.18. 
A.2.19. 
A.2.20. 
A.3.1. 
A.3.2. 
A.3.3. 
A.4.1. 
A.4.2. 
A.4.3. 
A.4.4. 
A.4.5. 
A.4.6. 
A.4.7. 
A.5.1. 
A.5.2. 
A.5.3. 
A.5.4. 
A.5.5. 
A.6.1. 
A.6.2. 
A.6.3. 
	    Microsoft has some advice on this matter, as well:
 	    
A.6.4. 
A.7.1. 
A.7.2. 
A.7.3. 
A.7.4. 
A.7.5. 
A.8.1. 
A.8.2. 
A.8.3. 
A.8.4. PREAMBLE
The Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
GNU Free Documentation License Up APPLICABILITY AND DEFINITIONS
\ No newline at end of file
diff --git a/docs/html/gfdl-1.html b/docs/html/gfdl-1.html
new file mode 100644
index 000000000..d91dc313e
--- /dev/null
+++ b/docs/html/gfdl-1.html
@@ -0,0 +1,200 @@
+APPLICABILITY AND DEFINITIONSThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
PREAMBLE Up VERBATIM COPYING
\ No newline at end of file
diff --git a/docs/html/gfdl-10.html b/docs/html/gfdl-10.html
new file mode 100644
index 000000000..e3c1677e1
--- /dev/null
+++ b/docs/html/gfdl-10.html
@@ -0,0 +1,165 @@
+FUTURE REVISIONS OF THIS LICENSEThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
TERMINATION Up How to use this License for your documents
\ No newline at end of file
diff --git a/docs/html/gfdl-2.html b/docs/html/gfdl-2.html
new file mode 100644
index 000000000..f3903c670
--- /dev/null
+++ b/docs/html/gfdl-2.html
@@ -0,0 +1,157 @@
+VERBATIM COPYINGThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
APPLICABILITY AND DEFINITIONS Up COPYING IN QUANTITY
\ No newline at end of file
diff --git a/docs/html/gfdl-3.html b/docs/html/gfdl-3.html
new file mode 100644
index 000000000..08bbedb9b
--- /dev/null
+++ b/docs/html/gfdl-3.html
@@ -0,0 +1,179 @@
+COPYING IN QUANTITYThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
VERBATIM COPYING Up MODIFICATIONS
\ No newline at end of file
diff --git a/docs/html/gfdl-4.html b/docs/html/gfdl-4.html
new file mode 100644
index 000000000..a67a24604
--- /dev/null
+++ b/docs/html/gfdl-4.html
@@ -0,0 +1,273 @@
+MODIFICATIONSThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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:
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.
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).
State on the Title page the name of the publisher of the
+        Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications
+        adjacent to the other copyright notices.
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.
Preserve in that license notice the full lists of Invariant
+        Sections and required Cover Texts given in the Document's license
+        notice.
Include an unaltered copy of this License.
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.
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.
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.
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.
Delete any section entitled "Endorsements". Such a section may
+        not be included in the Modified Version.
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.
Prev Home Next
COPYING IN QUANTITY Up COMBINING DOCUMENTS
\ No newline at end of file
diff --git a/docs/html/gfdl-5.html b/docs/html/gfdl-5.html
new file mode 100644
index 000000000..1702c2b91
--- /dev/null
+++ b/docs/html/gfdl-5.html
@@ -0,0 +1,166 @@
+COMBINING DOCUMENTSThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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."
Prev Home Next
MODIFICATIONS Up COLLECTIONS OF DOCUMENTS
\ No newline at end of file
diff --git a/docs/html/gfdl-6.html b/docs/html/gfdl-6.html
new file mode 100644
index 000000000..3e2583c2b
--- /dev/null
+++ b/docs/html/gfdl-6.html
@@ -0,0 +1,156 @@
+COLLECTIONS OF DOCUMENTSThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
COMBINING DOCUMENTS Up AGGREGATION WITH INDEPENDENT WORKS
\ No newline at end of file
diff --git a/docs/html/gfdl-7.html b/docs/html/gfdl-7.html
new file mode 100644
index 000000000..c08a7e018
--- /dev/null
+++ b/docs/html/gfdl-7.html
@@ -0,0 +1,159 @@
+AGGREGATION WITH INDEPENDENT WORKSThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
COLLECTIONS OF DOCUMENTS Up TRANSLATION
\ No newline at end of file
diff --git a/docs/html/gfdl-8.html b/docs/html/gfdl-8.html
new file mode 100644
index 000000000..dc721637f
--- /dev/null
+++ b/docs/html/gfdl-8.html
@@ -0,0 +1,155 @@
+TRANSLATIONThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
AGGREGATION WITH INDEPENDENT WORKS Up TERMINATION
\ No newline at end of file
diff --git a/docs/html/gfdl-9.html b/docs/html/gfdl-9.html
new file mode 100644
index 000000000..81e8904d2
--- /dev/null
+++ b/docs/html/gfdl-9.html
@@ -0,0 +1,152 @@
+TERMINATIONThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
TRANSLATION Up FUTURE REVISIONS OF THIS LICENSE
\ No newline at end of file
diff --git a/docs/html/gfdl-howto.html b/docs/html/gfdl-howto.html
new file mode 100644
index 000000000..cf7bdb131
--- /dev/null
+++ b/docs/html/gfdl-howto.html
@@ -0,0 +1,172 @@
+How to use this License for your documentsThe Bugzilla Guide
Prev Appendix E. GNU Free Documentation License Next
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.
Prev Home Next
FUTURE REVISIONS OF THIS LICENSE Up Glossary
\ No newline at end of file
diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html
new file mode 100644
index 000000000..76aa7ca32
--- /dev/null
+++ b/docs/html/gfdl.html
@@ -0,0 +1,218 @@
+GNU Free Documentation LicenseThe Bugzilla Guide
Prev Next
Appendix E. GNU Free Documentation License
Table of Contents
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
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
+    Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
+    distribute verbatim copies of this license document, but changing it is
+    not allowed.
Prev Home Next
SourceForge   PREAMBLE
\ No newline at end of file
diff --git a/docs/html/glossary.html b/docs/html/glossary.html
index ccf315815..d795b1fc8 100644
--- a/docs/html/glossary.html
+++ b/docs/html/glossary.html
@@ -10,8 +10,8 @@ REL="HOME"
 TITLE="The Bugzilla Guide"
 HREF="index.html">Prev

3.2.1. Autolinkification

3.2.5. Filing Bugs

HTTP Server Configuration

The Bugzilla Guide
Prev	Chapter 4. Installation	Next

4.4. HTTP Server Configuration

The Bugzilla Team recommends Apache when using Bugzilla, however, any web server + that can be configured to run CGI scripts + should be able to handle Bugzilla. No matter what web server you choose, but + especially if you choose something other than Apache, you should be sure to read + Section 5.6. +

The plan for this section is to eventually document the specifics of how to lock + down permissions on individual web servers. +

4.4.1. Apache httpd

As mentioned above, the Bugzilla Team recommends Apache for use + with Bugzilla. You will have to make sure that Apache is properly + configured to run the Bugzilla CGI scripts. You also need to make sure + that the .htaccess files created by + ./checksetup.pl (shown in Example 4-1 + for the curious) are allowed to override Apache's normal access + permissions or else important password information may be exposed to the + Internet. +

Many Apache installations are not configured to run scripts + anywhere but in the cgi-bin + directory; however, we recommend that Bugzilla not be installed in the + cgi-bin, otherwise the static + files such as images and JavaScript + will not work correctly. To allow scripts to run in the normal + web space, the following changes should be made to your + httpd.conf file. +

To allow files with a .cgi extension to be run, make sure the + following line exists and is uncommented:

AddHandler cgi-script .cgi
+

To allow .htaccess files to override + permissions and .cgi files to run in the Bugzilla directory, make sure + the following two lines are in a Directory + directive that applies to the Bugzilla directory on your system + (either the Bugzilla directory or one of its parents). +

Options +ExecCGI 
+AllowOverride Limit
+

For more information on Apache and its directives, see the + glossary entry on Apache. +

Example 4-1. .htaccess files for Apache

$BUGZILLA_HOME/.htaccess +
# don't allow people to retrieve non-cgi executable files or our private data +<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$> + deny from all +</FilesMatch> +<FilesMatch ^(localconfig.js|localconfig.rdf)$> + allow from all +</FilesMatch> +
+

$BUGZILLA_HOME/data/.htaccess +
# nothing in this directory is retrievable unless overriden by an .htaccess +# in a subdirectory; the only exception is duplicates.rdf, which is used by +# duplicates.xul and must be loadable over the web +deny from all +<Files duplicates.rdf> + allow from all +</Files> +
+

$BUGZILLA_HOME/data/webdot +
# Restrict access to .dot files to the public webdot server at research.att.com +# if research.att.com ever changed their IP, or if you use a different +# webdot server, you'll need to edit this +<FilesMatch ^[0-9]+\.dot$> + Allow from 192.20.225.10 + Deny from all +</FilesMatch> + +# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and +# .map files +<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> + Allow from all +</FilesMatch> + +# And no directory listings, either. +Deny from all +
+

$BUGZILLA_HOME/Bugzilla/.htaccess +
# nothing in this directory is retrievable unless overriden by an .htaccess +# in a subdirectory +deny from all +
+

$BUGZILLA_HOME/template/.htaccess +
# nothing in this directory is retrievable unless overriden by an .htaccess +# in a subdirectory +deny from all +
+

4.4.2. Microsoft Internet Information Services

If you need, or for some reason even want, to use Microsoft's + Internet Information Services or + Personal Web Server you should be able + to. You will need to configure them to know how to run CGI scripts, + however. This is described in Microsoft Knowledge Base article + Q245225 + for Internet Information Services and + Q231998 + for Personal Web Server. +

Also, and this can't be stressed enough, make sure that files such as + localconfig and your data + directory are secured as described in Section 5.6. +

4.4.3. AOL Server

Ben FrantzDale reported success using AOL Server with Bugzilla. He + reported his experience and what appears below is based on that. +

AOL Server will have to be configured to run + CGI scripts, please consult + the documentation that came with your server for more information on + how to do this. +

Because AOL Server doesn't support .htaccess + files, you'll have to create a TCL + script. You should create an aolserver/modules/tcl/filter.tcl + file (the filename shouldn't matter) with the following contents (change + /bugzilla/ to the web-based path to + your Bugzilla installation): +

ns_register_filter preauth GET /bugzilla/localconfig filter_deny
+ns_register_filter preauth GET /bugzilla/*.pl filter_deny
+ns_register_filter preauth GET /bugzilla/localconfig filter_deny
+ns_register_filter preauth GET /bugzilla/processmail filter_deny
+ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
+ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
+
+proc filter_deny { why } {
+    ns_log Notice "filter_deny"
+    return "filter_return"
+}
+

This doesn't appear to account for everything mentioned in + Section 5.6. In particular, it doesn't block access + to the data or + template directories. It also + doesn't account for the editor backup files that were the topic of + bug + 186383, Bugtraq ID 6501, + and a partial cause for the 2.16.2 release. +

Prev	Home	Next
OS Specific Installation Notes	Up	Troubleshooting

\ No newline at end of file diff --git a/docs/html/index.html b/docs/html/index.html index 57c05dbf2..4dfd2a8df 100644 --- a/docs/html/index.html +++ b/docs/html/index.html @@ -60,13 +60,16 @@ NAME="AEN9" >The Bugzilla Team

2.17.3 Development Release Edition

2003-01-02

This is a development version of this guide. Information in it @@ -201,13 +203,13 @@ HREF="extraconfig.html" >

4.3. Win32 Installation NotesOS Specific Installation Notes

4.4. Mac OS X Installation NotesHTTP Server Configuration

4.5.

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

4-1. Installing ActivePerl ppd Modules on Microsoft - Windows

4-2. Installing OpenInteract ppd Modules manually on Microsoft - Windows

4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or - earlier.htaccess files for Apache

5-1.

4.1.1. Introduction
4.1.2. Package List

4.1.6. HTTP Server
4.1.7. Bugzilla
4.1.8. Setting Up the MySQL Database
4.1.9. checksetup.pl
4.1.10. Securing MySQL
4.1.11. Configuring Bugzilla

4.2.1. Dependency Charts

4.2.2. Bug Graphs

4.2.3. The Whining Cron

4.3. Win32 Installation NotesOS Specific Installation Notes

4.3.1. Win32 Installation: Step-by-stepMicrosoft Windows
4.3.2. Additional Windows TipsMac OS X

4.4. Mac OS X Installation NotesHTTP Server Configuration

4.4.1. Apache httpd
4.4.2. Microsoft Internet Information Services
4.4.3. AOL Server

4.5.
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
4.5.2. DBD::Sponge::db prepare failed
OS Specific Installation Notes
The Bugzilla Guide
Prev Chapter 4. Installation Next
4.3. OS Specific Installation Notes
Many aspects of the Bugzilla installation can be affected by the + the operating system you choose to install it on. Sometimes it can be made + easier and others more difficult. This section will attempt to help you + understand both the difficulties of running on specific operating systems + and the utilities available to make it easier. +
If you have anything to add or notes for an operating system not + covered, please file a bug in Bugzilla Documentation. +
4.3.1. Microsoft Windows
Making Bugzilla work on windows is still a very painful processes. + The Bugzilla Team is working to make it easier, but that goal is not + considered a top priority. If you wish to run Bugzilla, we still + recommend doing so on a Unix based system such as GNU/Linux. As of this + writing, all members of the Bugzilla team and all known large installations + run on Unix based systems. +
If after hearing all that, you have enough pain tolerance to attempt + installing Bugzilla on Win32, here are some pointers. + + Because this is a development version of the guide, these instructions + are subject to change without notice. In fact, the Bugzilla Team hopes + they do as we would like to have Bugzilla resonabally close to "out of + the box" compatibility by the 2.18 release. + +
4.3.1.1. Win32 Perl
Perl for Windows can be obtained from ActiveState. You should be + able to find a compiled binary at http://aspn.activestate.com/ASPN/Downloads/ActivePerl/. +
4.3.1.2. Perl Modules on Win32
Bugzilla on Windows requires the same perl modules found in + Section 4.1.2. The main difference is that + windows uses ppm instead of CPAN. +
C:\perl> ppm <module name> +
The above syntax should work for all modules with the exception + of Template Toolkit. The Template Toolkit website + suggests using the instructions on OpenInteract's website. +
A complete list of modules that can be installed using ppm can + be found at http://www.activestate.com/PPMPackages/5.6plus. +
4.3.1.3. Code changes required to run on win32
Unfortunately, Bugzilla still doesn't run "out of the box" on + Windows. There is work in progress to make this easier, but until that + happens code will have to be modified. This section is an attempt to + list the required changes. It is an attempt to be all inclusive, but + there may be other changes required. If you find something is missing, + please file a bug in Bugzilla Documentation. +
4.3.1.3.1. Changes to checksetup.pl
In checksetup.pl, the line reading:
my $mysql_binaries = `which mysql`; +
to
my $mysql_binaries = "D:\\mysql\\bin\\mysql"; +
And you'll also need to change:
my $webservergid = getgrnam($my_webservergroup) +
to
my $webservergid = '8' +
4.3.1.3.2. Making mail work
The easiest way to get mail working is to use the mail patches + on bug + 124174. With any luck, this patch will receive the required + reviews and integrated into the main Bugzilla distribution very soon. + Until that happens, there's at least one report of this patch working + well on Windows. +
4.3.1.3.3. System Calls
In order to get system calls to work on win32's perl, you need + to tell the windows shell what interpreter to use. This is done by + changing the system calls. You will need to + search all of Bugzilla's code for system calls. + To tell perl your interpreter, it needs to be the first argument to + the system call. For example, you'll need to + change: +
system("./processmail", $id, $exporter); +
with
system("C:\\perl\\bin\\perl", "processmail", $id, $exporter); +
Notice that the ./ is also + removed. +
The grep command is very helpful in finding + these system calls, assuming you have the + cygwin utilities. +
4.3.1.4. Serving the web pages
As is the case on Unix based systems, any web server should be + able to handle Bugzilla; however, the Bugzilla Team still recommends + Apache whenever asked. No matter what web server you choose, be sure + to pay attention to the security notes in Section 5.6. + More information on configuring specific web servers can be found in + Section 4.4. +
If using Apache on windows, you can set the ScriptInterpreterSource + directive in your Apache config, if you don't do this, you'll have + to modify the first line of every script to contain your path to + perl instead of /usr/bonsaitools/bin/perl. +
4.3.2. Mac OS X
There are a lot of common libraries and utilities out there that + Apple did not include with Mac OS X, but which run perfectly well on it. + The GD library, which Bugzilla needs to do bug graphs, is one of + these.
The easiest way to get a lot of these is with a program called + Fink, which is similar in nature to the CPAN installer, but installs + common GNU utilities. Fink is available from + http://sourceforge.net/projects/fink/.
Follow the instructions for setting up Fink. Once it's installed, + you'll want to run the following as root: + fink install gd +
It will prompt you for a number of dependencies, type 'y' and hit + enter to install all of the dependencies. Then watch it work.
To prevent creating conflicts with the software that Apple installs + by default, Fink creates its own directory tree at /sw where it installs + most of the software that it installs. This means your libraries and + headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib + and /usr/local/include. Because of these changed locations for the + libraries, the Perl GD module will not install directly via CPAN, because it + looks for the specific paths instead of getting them from your + environment. But there's a way around that :-)
Instead of typing + "install GD" + at the + cpan> + prompt, type + look GD. + This should go through the motions of downloading the latest version of + the GD module, then it will open a shell and drop you into the build + directory. Apply this patch + to the Makefile.PL file (save the + patch into a file and use the command + patch < patchfile.) +
Then, run these commands to finish the installation of the GD + module: +
perl Makefile.PL +
make +
make test +
make install +
And don't forget to run + exit + + to get back to CPAN.
+
Prev Home Next
Optional Additional Configuration Up HTTP Server Configuration
\ No newline at end of file diff --git a/docs/html/osx.html b/docs/html/osx.html deleted file mode 100644 index 664dea1da..000000000 --- a/docs/html/osx.html +++ /dev/null @@ -1,260 +0,0 @@ -Mac OS X Installation Notes
The Bugzilla Guide
Prev Chapter 4. Installation Next
4.4. Mac OS X Installation Notes
There are a lot of common libraries and utilities out there that - Apple did not include with Mac OS X, but which run perfectly well on it. - The GD library, which Bugzilla needs to do bug graphs, is one of - these.
The easiest way to get a lot of these is with a program called - Fink, which is similar in nature to the CPAN installer, but installs - common GNU utilities. Fink is available from - <http://sourceforge.net/projects/fink/>.
Follow the instructions for setting up Fink. Once it's installed, - you'll want to run the following as root: - fink install gd -
It will prompt you for a number of dependencies, type 'y' and hit - enter to install all of the dependencies. Then watch it work.
To prevent creating conflicts with the software that Apple installs - by default, Fink creates its own directory tree at /sw where it installs - most of the software that it installs. This means your libraries and - headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib - and /usr/local/include. Because of these changed locations for the - libraries, the Perl GD module will not install directly via CPAN, because it - looks for the specific paths instead of getting them from your - environment. But there's a way around that :-)
Instead of typing - "install GD" - at the - cpan> - prompt, type - look GD. - This should go through the motions of downloading the latest version of - the GD module, then it will open a shell and drop you into the build - directory. Apply this patch - to the Makefile.PL file (save the - patch into a file and use the command - patch < patchfile.) -
Then, run these commands to finish the installation of the GD - module: -
perl Makefile.PL -
make -
make test -
make install -
And don't forget to run - exit - - to get back to CPAN.
-
Prev Home Next
Win32 Installation Notes Up Troubleshooting
\ No newline at end of file diff --git a/docs/html/security.html b/docs/html/security.html index dc4b5b7c4..8d1b047d0 100644 --- a/docs/html/security.html +++ b/docs/html/security.html @@ -446,156 +446,11 @@ CLASS="filename" is provided for those that want to know exactly what is created.
Note the instructions which follow are Apache-specific. If you +>FIX ME BEFORE RELEASE!!!!! + 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.
$BUGZILLA_HOME/.htaccess -
# don't allow people to retrieve non-cgi executable files or our private data -<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$> - deny from all -</FilesMatch> -<FilesMatch ^(localconfig.js|localconfig.rdf)$> - allow from all -</FilesMatch> -
-
$BUGZILLA_HOME/data/.htaccess -
# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory; the only exception is duplicates.rdf, which is used by -# duplicates.xul and must be loadable over the web -deny from all -<Files duplicates.rdf> - allow from all -</Files> -
-
$BUGZILLA_HOME/data/webdot -
# Restrict access to .dot files to the public webdot server at research.att.com -# if research.att.com ever changed their IP, or if you use a different -# webdot server, you'll need to edit this -<FilesMatch ^[0-9]+\.dot$> - Allow from 192.20.225.10 - Deny from all -</FilesMatch> - -# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and -# .map files -<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> - Allow from all -</FilesMatch> - -# And no directory listings, either. -Deny from all -
-
$BUGZILLA_HOME/Bugzilla/.htaccess -
# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all -
-
$BUGZILLA_HOME/template/.htaccess -
# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all -
-
diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html index 27870e9ae..d925b25cb 100644 --- a/docs/html/stepbystep.html +++ b/docs/html/stepbystep.html @@ -81,17 +81,17 @@ CLASS="section" >
4.1.1. Introduction
Bugzilla has been successfully installed under Solaris, Linux, and Win32. Win32 is not yet officially supported, but many people have got it working fine. - Please see the + Please see Win32 Installation NotesSection 4.3.1 for further advice on getting Bugzilla to work on Microsoft Windows.
4.1.2. Package List
DBD::mysql - (1.2209) + (2.1010)
DBI - (1.13) + (1.32)
4.1.5.1. DBI
4.1.5.2. Data::Dumper
4.1.5.3. MySQL-related modules
4.1.5.4. TimeDate modules
4.1.5.5. GD (optional)
The GD library was written by Thomas Boutell a long while ago to programatically generate images in C. Since then it's become the - defacto standard for programatic image construction. The Perl bindings + defacto standard for programmatic image construction. The Perl bindings to it found in the GD library are used on millions of web pages to generate graphs on the fly. That's what Bugzilla will be using it for so you must install it if you want any of the graphing to work.
4.1.5.6. Chart::Base (optional)
4.1.5.7. Template Toolkit
4.1.6. HTTP Server
You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can run the web server on a - different machine than MySQL, but need to adjust the MySQL - "bugs"You have freedom of choice here, pretty much any web server that + is capable of running CGI - user permissions accordingly. -
Section 4.4 has more information about + configuring web servers to work with Bugzilla. +

-
You'll want to make sure that your web server will run - any file - with the .cgi extension as a CGI program and not simply display the source - code. If you're - using Apache that means uncommenting the following line in the httpd.conf - file: -
AddHandler cgi-script .cgi -
-
With Apache you'll also want to make sure that within the - httpd.conf file these lines: -
Options +ExecCGI -AllowOverride Limit -
- - are in the stanza that covers the directories into which you intend to - put the bugzilla .html and .cgi files. - -
AllowOverride Limit allows the use of a Deny statement in the - .htaccess file generated by checksetup.pl
Users of older versions of Apache may find the above lines - in the srm.conf and access.conf files, respectively.
-
There are important files and directories that should not be a - served by the HTTP server - most files in the - "data" - directory and the - "localconfig" - file. You should configure your HTTP server to not serve - these files. Failure to do so will expose critical passwords and - other data. Please see - .htaccess files and security - for details on how to do this for Apache; the checksetup.pl - script should create appropriate .htaccess files for you.

4.1.7. Bugzilla

If you symlink the bugzilla directory into your Apache's HTML - heirarchy, you may receive + hierarchy, you may receive Forbidden

4.1.8. Setting Up the MySQL Database

4.1.9. `4.1.10. Securing MySQL This means anyone from anywhere on the internet can not only drop +>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. 4.1.11. Configuring Bugzilla Prev 4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 4.5.2. DBD::Sponge::db prepare failed PrevMac OS X Installation NotesHTTP Server Configuration 3.2.1. Autolinkification 3.2.5. Filing Bugs D.4. Scarab`

Scarab is a new open source bug-tracking system built using Java - Serlet technology. It is currently at version 1.0 beta 8.

URL:

This section last updated 27 Jul 2002

This section last updated 18 Jan 2003

NextNextGlossaryGNU Free Documentation License

Win32 Installation Notes

The Bugzilla Guide
Prev	Chapter 4. Installation	Next

`4.3. Win32 Installation Notes`

This section covers installation on Microsoft Windows. - Bugzilla has been made to work on Win32 platforms, but the Bugzilla team - wish to emphasise that The easiest way to install Bugzilla on - Intel-archiecture machines - is to install some variant of GNU/Linux, then follow the UNIX - installation instructions in this Guide. If you have any influence in the - platform choice for running this system, please choose GNU/Linux instead - of Microsoft Windows.

If you still want to try this, to have any hope of getting it to work, - you'll need to apply the - mail patch from - bug 124174. - After that, you'll need to read the (outdated) installation - instructions below, some (probably a lot better) more - recent ones kindly provided by Toms Baugis and Jean-Sebastien - Guay, and also check the - Bugzilla 2.16 Win32 update page - . If we get time, - we'll write some better installation instructions for 2.16 and put - them up there. But no promises. -

`4.3.1. Win32 Installation: Step-by-step`

You should be familiar with, and cross-reference, the rest of - the - Bugzilla Installation - - section while performing your Win32 installation.

Install - Apache Web Server - - for Windows, and copy the Bugzilla files somewhere Apache can serve - them. Please follow all the instructions referenced in - Bugzilla Installation - - regarding your Apache configuration, particularly instructions - regarding the - "AddHandler" - - parameter and - "ExecCGI" - - .

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.

Install - ActivePerl - - for Windows. Check - http://aspn.activestate.com/ASPN/Downloads/ActivePerl - - for a current compiled binary.
Please also check the following links to fully understand the - status of ActivePerl on Win32: - Perl Porting - - , and - Perl on Win32 FAQ -

Use ppm from your perl\bin directory to install the following - packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD, - AppConfig, and Template. You may need to extract them from .zip - format using Winzip or other unzip program first. Most of these - additional ppm modules can be downloaded from ActiveState, but - AppConfig and Template should be obtained from OpenInteract using - the - instructions on the Template Toolkit web site - - .

You can find a list of modules at - http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ - - or - http://www.activestate.com/PPMPackages/5.6plus -

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

Example 4-1. Installing ActivePerl ppd Modules on Microsoft - Windows C:> - - ppm - DBD-Mysql - - Watch your capitalization!

ActiveState's 5.6Plus directory also contains an AppConfig - ppm, so you might see the following error when trying to install - the version at OpenInteract:

Error installing package 'AppConfig': Read a PPD - for 'AppConfig', but it is not intended for this build of Perl - (MSWin32-x86-multi-thread) -

If so, download both - the tarball - - and - the ppd - - directly from OpenInteract, then run ppm from within the same - directory to which you downloaded those files and install the - package by referencing the ppd file explicitly via in the install - command, f.e.: -

Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft - Windows install - C:\AppConfig.ppd - - -

-

Install MySQL for NT. -

You can download MySQL for Windows NT from - MySQL.com - - . Some find it helpful to use the WinMySqlAdmin utility, included - with the download, to set up the database.

-

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'; - -
  "new_password" - - , above, indicates whatever password you wish to use for your - "root" - - user.
4. mysql> - - GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, - ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost - IDENTIFIED BY 'bugs_password'; - - "bugs_password" - - , above, indicates whatever password you wish to use for your - "bugs" - - user.
5. mysql> - - FLUSH PRIVILEGES; - -
6. mysql> - - create database bugs; - -
7. mysql> - - exit; - -
8. C:> - - C:\mysql\bin\mysqladmin -u root -p - reload - -
Edit - checksetup.pl - - in your Bugzilla directory. Change this line:
my $webservergid = - getgrnam($my_webservergroup); -
to
my $webservergid = - $my_webservergroup; - - or the name of the group you wish to own the files explicitly: - my $webservergid = - 'Administrators' -
Run - checksetup.pl - - from the Bugzilla directory.
Edit - localconfig - - to suit your requirements. Set - $db_pass - - to your - "bugs_password" - - from - step 5.d - - , and - $webservergroup - - to - "8" - - .
Not sure on the - "8" - - for - $webservergroup - - above. If it's wrong, please send corrections.

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

This is yet another step I'm not sure of, since the - maintainer of this documentation does not maintain Bugzilla on - NT. If you can confirm or deny that this step is required, please - let me know.

There are several alternatives to Sendmail that will work - on Win32. The one mentioned here is a - suggestion - - , not a requirement. Some other mail packages that can work - include - BLAT - - , - Windmail - - , - Mercury - Sendmail - - , and the CPAN Net::SMTP Perl module (available in .ppm). Every - option requires some hacking of the Perl scripts for Bugzilla to - make it work. The option here simply requires the least.

Download NTsendmail, available from - www.ntsendmail.com - - . You must have a "real" mail server which allows you to relay - off it in your $ENV{"NTsendmail"} (which you should probably - place in globals.pl)
Put ntsendmail.pm into your .\perl\lib directory.

Add to globals.pl:

# these settings configure the NTsendmail
-              process use NTsendmail;
-              $ENV{"NTsendmail"}="your.smtpserver.box";
-              $ENV{"NTsendmail_debug"}=1;
-              $ENV{"NTsendmail_max_tries"}=5;

Some mention to also edit - $db_pass - - in - globals.pl - - to be your - "bugs_password" - - . Although this may get you around some problem - authenticating to your database, since globals.pl is not - normally restricted by - .htaccess - - , your database password is exposed to whoever uses your web - server.

Find and comment out all occurences of - " - open(SENDMAIL - " - - in your Bugzilla directory. Then replace them with: - # new sendmail functionality my $mail=new - NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my - $to=$login; my $subject=$urlbase; - $mail->send($from,$to,$subject,$msg); -

Some have found success using the commercial product, - Windmail - - . You could try replacing your sendmail calls with: -
open SENDMAIL, - "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > - mail.log";
- - or something to that effect.

Change all references in all files from - processmail - - to - processmail.pl - - , and rename - processmail - - to - processmail.pl - - .

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. -
- -my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server -$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here -$smtp->to($tolist); # recipient's address -$smtp->data(); # Start the mail -$smtp->datasend($msg); -$smtp->dataend(); # Finish sending the mail -$smtp->quit; # Close the SMTP connection -$logstr = "$logstr; mail sent to $tolist $cclist"; -} - - -
- - here is a test mail program for Net::SMTP: -
- -use Net::SMTP; - my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug -=> 1, ); # connect to SMTP server - $smtp->auth; - $smtp->mail('you@yourcompany.com');# use the sender's adress -here - $smtp->to('someotherAddress@someotherdomain.com'); # -recipient's address - $smtp->data(); # Start the mail - $smtp->datasend('test'); - $smtp->dataend(); # Finish sending the mail - $smtp->quit; # Close the SMTP connection -exit; - - -
-

This step is optional if you are using IIS or another web - server which only decides on an interpreter based upon the file - extension (.pl), rather than the - "shebang" - - line (#/usr/bonsaitools/bin/perl)

Modify the path to perl on the first line (#!) of all files - to point to your Perl installation, and add - "perl" - - to the beginning of all Perl system calls that use a perl script as - an argument. This may take you a while. There is a - "setperl.csh" - - utility to speed part of this procedure, available in the - Useful Patches and Utilities for Bugzilla - - section of The Bugzilla Guide. However, it requires the Cygwin - GNU-compatible environment for Win32 be set up in order to work. - See - http://www.cygwin.com/ - - for details on obtaining Cygwin.

Modify the invocation of all system() calls in all perl - scripts in your Bugzilla directory. You should specify the full - path to perl for each system() call. For instance, change this line - in processmail: - -system ("./processmail",@ARGLIST); - </programlisting> to - <programlisting> -system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST); - - -

If you are using IIS or Personal Web Server, you must add cgi - relationships to Properties -> Home directory (tab) -> - Application Settings (section) -> Configuration (button), such - as:

.cgi to: <perl install directory>\perl.exe %s - %s .pl to: <perl install directory>\perl.exe %s %s - GET,HEAD,POST
- - Change the path to Perl to match your install, of course.

`4.3.2. Additional Windows Tips`

From Andrew Pearson: -

You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP -
Basically you need to add two String Keys in the registry at - the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
-
The keys should be called ".pl" and ".cgi", and both should - have a value something like: - c:/perl/bin/perl.exe "%s" "%s" -
The KB article only talks about .pl, but it goes into more - detail and provides a perl test script.

If attempting to run Bugzilla 2.12 or older, you will need to - remove encrypt() calls from the Perl source. This is - not necessary - - for Bugzilla 2.13 and later, which includes the current release, - Bugzilla &bz-ver;. -

Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or - earlier

Replace this: -
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . - ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my - $enteredcryptpwd = FetchOneColumn();
- - with this: -
my $enteredcryptpwd = $enteredpwd
- - in cgi.pl.

Prev	Home	Next
Optional Additional Configuration	Up	Mac OS X Installation Notes

\ No newline at end of file -- cgit v1.2.3-24-g4f1b