This documentation is maintained in DocBook 4.1.2 XML format. - Changes are best submitted as plain text or SGML diffs, attached + Changes are best submitted as plain text or XML diffs, attached to a bug filed in

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

List of Figures

4-1. Other File::Temp error messages

4-2. Patch for File::Temp in Perl 5.6.0

List of Examples
4-1. Installing ActivePerl ppd Modules on Microsoft Windows
4-2. Installing OpenInteract ppd Modules manually on Microsoft Windows
4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier

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.16.3 version of The Bugzilla Guide. It is so named + to match the version of Bugzilla it is disributed with. If you are + reading this from any source other than those below, please + check one of these mirrors to make sure you are reading an + up-to-date version of the Guide. +

The "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 <mbarnson@sisna.com>

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.
for the Herculaean task of pulling together the Bugzilla Guide + and shepherding it to 2.14. +
Terry Weissman <terry@mozilla.org>
Do not retitle any existing section as "Endorsements" or to - conflict in title with any Invariant Section.

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

Tara Hernandez <tara@tequilarists.org>

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.

for keeping Bugzilla development going strong after Terry left + mozilla.org and for running landfill. +

Dave Lawrence <dkl@redhat.com>

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.

for providing insight into the key differences between Red + Hat's customized Bugzilla, and being largely responsible for + Section D.1. +

Dawn Endico <endico@mozilla.org>

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.

for being a hacker extraordinaire and putting up with Matthew's + incessant questions and arguments on irc.mozilla.org in #mozwebtools +

Jacob Steenhagen <jake@bugzilla.org>

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.

for taking over documentation during the 2.17 development + period and backporting relevent docs changes to this 2.16 branch. +

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.

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

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

Thanks also go to the following people for significant contributions + to this documentation (in alphabetical order): + Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption + . +

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.

1.5. Document Conventions

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.

This document uses the following conventions:

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

Use cautionWarnings

A.1.5. core team, - led by Dave Miller (justdave@syndicomm.com). + led by Dave Miller (justdave@netscape.com).

A.1.6.

A.1.7. - Why doesn't Bugzilla offer this or that feature or compatability + Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software?

A.1.8. - There is DB-independence work afoot. PostgreSQL support is planned - for 2.18, and full DB-independence can't be far further on. + MySQL was originally chosen because it is free, easy to install, + and was available for the hardware Netscape intended to run it on.

There is currently work in progress to make Bugzilla work on + PostgreSQL and Sybase in the default distribution. You can track + the progress of these initiatives in bugs 98304 + and 173130 + respectively. +

Once both of these are done, adding support for additional + database servers should be trivial. +

A.1.9. - Why do the scripts say "/usr/bonsaitools/bin/perl" instead of - "/usr/bin/perl" or something else? + Why do the scripts say + /usr/bonsaitools/bin/perl instead of + /usr/bin/perl or something else?

- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally - Terry wanted a place to put a version of Perl and other tools - that was strictly under his control. -

/usr/bonsaitools/bin/perl, + because originally Terry wanted a place to put a version of Perl + and other tools that was strictly under his control. +

We always recommend that, if possible, you keep the path - as /usr/bonsaitools/bin/perl, and simply add symlink. - This will make upgrading - your Bugzilla much easier in the future. -

Descriptions Appearance

Use caution

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.

Don't run with scissors!

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

Hint

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.

Would you like a breath mint?

How to use this License for your documents

Notes

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

Warnings

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.

Read this or the cat gets it.

1.2. Disclaimer

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

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

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

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

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

1.3. New Versions

This is the 2.16.3 version of The Bugzilla Guide. It is so named - to match the current version of Bugzilla. If you are - reading this from any source other than those below, please - check one of these mirrors to make sure you are reading an - up-to-date version of the Guide. -

This document can be found in the following places: -

bugzilla.org -
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:

Directory NamesCommands to be typed

A.1.5. core team, - led by Dave Miller (justdave@syndicomm.com). + led by Dave Miller (justdave@netscape.com).

A.1.6.

A.1.7. - Why doesn't Bugzilla offer this or that feature or compatability + Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software?

Once both of these are done, adding support for additional + database servers should be trivial. +

- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally - Terry wanted a place to put a version of Perl and other tools - that was strictly under his control. -

/usr/bonsaitools/bin/perl, + because originally Terry wanted a place to put a version of Perl + and other tools that was strictly under his control. +

We always recommend that, if possible, you keep the path - as /usr/bonsaitools/bin/perl, and simply add symlink. - This will make upgrading - your Bugzilla much easier in the future. -

Descriptions File Names Appearance filename +

Warnings

Don't run with scissors!

directory

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 command

Term found in the glossary Bugzilla +

Code Example

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 + 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 @@ -2225,7 +1876,7 @@ CLASS="section" >

3.2.1. Autolinkification

3.2.5. Filing Bugs

4.1.1. Introduction

4.1.2. Package List

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)

4.1.5.6. Chart::Base (optional)

4.1.5.7. Template Toolkit

4.1.6. HTTP Server

4.1.7. Bugzilla

4.1.8. Setting Up the MySQL Database

If you are using MySQL 4, the bugs user also needs to be granted + the LOCK TABLES and CREATE TEMPORARY TABLES permissions. +

4.1.9. 4.1.10. Configuring Bugzilla 4.2.1. Dependency Charts 4.2.2. Bug Graphs 4.2.3. The Whining Cron From Andrew Pearson: this patch @@ -6487,7 +6166,7 @@ CLASS="section" > 4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 4.5.2. DBD::Sponge::db prepare failed 4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT This is caused by a bug in the version of + File::Temp that is distributed with perl + 5.6.0. Many minor variations of this error have been reported. Examples + can be found in Figure 4-1. + Figure 4-1. Other File::Temp error messages Your vendor has not defined Fcntl macro O_NOINHERIT, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208. + +Your vendor has not defined Fcntl macro O_EXLOCK, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210. + +Your vendor has not defined Fcntl macro O_TEMPORARY, used +at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. + Numerous people have reported that upgrading to version 5.6.1 + or higher solved the problem for them. A less involved fix is to apply + the patch in Figure 4-2. The patch is also + available as a patch file. + Figure 4-2. Patch for File::Temp in Perl 5.6.0 --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003 ++++ File/Temp.pm Thu Feb 6 16:26:23 2003 +@@ -205,6 +205,7 @@ + # eg CGI::Carp + local $SIG{__DIE__} = sub {}; + local $SIG{__WARN__} = sub {}; ++ local *CORE::GLOBAL::die = sub {}; + $bit = &$func(); + 1; + }; +@@ -226,6 +227,7 @@ + # eg CGI::Carp + local $SIG{__DIE__} = sub {}; + local $SIG{__WARN__} = sub {}; ++ local *CORE::GLOBAL::die = sub {}; + $bit = &$func(); + 1; + }; +

`5.7.1. What to Edit`

`5.7.2. How To Edit Templates`

`5.7.3. Template Formats`

`5.7.4. Particular Templates`

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 compatability +HREF="#faq-general-bzmissing" +> 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? +HREF="#faq-general-bonsaitools" +> 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?

AtHome Corporation

Red Hat Software

This convention was abonded during the 2.17 development cycle so + it will no longer be an issue when 2.18 comes out. +

A.1.10.

A.2.1.

A.2.2.

A.2.3. - Absolutely! You can track any number of Products (although you - are limited to about 55 or so if - you are using Product-Based Groups), that can each be composed of any - number of Components. + Absolutely! You can track any number of Products that can each be + composed of any number of Components.

There are only 55 groups available in version 2.16 of + Bugzilla. If you are using product groups, this will also limit + the number of products you can have. This limit does not exist in + the current 2.17 development releases and will not exist in 2.18. +

A.2.4.

A.2.5. Yes - any sort of attachment is allowed, although administrators can configure a maximum size. - There are many specific MIME-types that are pre-defined by Bugzilla, - but you may specify any arbitrary MIME-type you need when you - upload the file. + Bugzilla gives the user the option of either using the MIME-type + supplied by the browser, choosing from a pre-defined list or + manually typing any arbitrary MIME-type.

A.2.6. http://bugzilla.mozilla.org/show_bug.cgi?id=91037 +>.

A.2.7. http://bugzilla.mozilla.org/reports.cgi for basic reporting - and graphing facilities. +>http://bugzilla.mozilla.org/reports.cgi + for samples of what Bugzilla can do in reporting and graphing.

For more advanced reporting, I recommend hooking up a professional - reporting package, such as Crystal Reports, and use ODBC to access - the MySQL database. You can do a lot through the Query page of - Bugzilla as well, but right now Advanced Reporting is much - better accomplished through third-party utilities that can - interface with the database directly. +> If you can not get the reports you want from the included reporting + scripts, it is possible to hook up a professional reporting package + such as Crystal Reports using ODBC. If you choose to do this, + beware that giving direct access to the database does contain some + security implications. Even if you give read-only access to the + bugs database it will bypass the secure bugs features of Bugzilla.

Bugzilla's current development versions can do a lot more in the + way of reporting. To see examples, check out + http://bugzilla.mozilla.org/report.cgi. +

A.2.8.

A.2.9.

A.2.10.

A.2.11. - Mozilla allows data export through a custom DTD in XML format. - It does not, however, export to specific formats other than the - XML Mozilla DTD. Importing the data into Excel or any other application - is left as an exercise for the reader. -

If you create import filters to other applications from Mozilla's XML, - please submit your modifications for inclusion in future Bugzilla - distributions. -

Bugzilla can export bugs using xml.cgi with + either a bug number or list of bug numbers. +

As for data import, any application can send data to Bugzilla through - the HTTP protocol, or through Mozilla's XML API. However, it seems - kind of silly to put another front-end in front of Bugzilla; - it makes more sense to create a simplified bug submission form in - HTML. You can find an excellent example at - http://www.mozilla.org/quality/help/bugzilla-helper.html Currently the only script included with Bugzilla that can import + data is importxml.pl which is intended to be + used for importing the data generated by xml.cgi -

There are also scripts included in the contrib/ + directory for using e-mail to import information into Bugzilla, + but these scripts are not currently supported and included for + educational purposes. +

A.2.12. - To a certain extent, yes. 2.16's templates mean that you can localise - the user-facing UI (and several projects are doing exactly that.) However, - error messages and the admin interface are currently not localisable. - This should be achieved by 2.18. + Yes. For more information including available translated templates, + see http://www.bugzilla.org/download.html#localizations. + The admin interfaces are still not included in these translated + templates and is therefore still English only. Also, there may be + issues with the charset not being declared. See bug 126226 + for more information.

A.2.13. - Yes. No. No. + Yes. No. Not in 2.16.

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. The user should be able to set - this in user email preferences (uncheck all boxes.) + this in user email preferences (uncheck all boxes) or you can add + their email address to the data/nomail file.

A.4.2. - Edit the "changedmail" Param. Replace "To:" with "X-Real-To:", + Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".

A.4.3. Try Klaas Freitag's excellent patch for "whineatassigned" functionality. - You can find it at http://bugzilla.mozilla.org/show_bug.cgi?id=6679http://bugzilla.mozilla.org/show_bug.cgi?id=6679. This patch is against an older version of Bugzilla, so you must apply the diffs manually. @@ -11283,7 +11208,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.4.

A.4.5.
A.4.6.
A.4.7.
A.5.1. - Red Hat Bugzilla works with Oracle. The current version - from Mozilla.org does not have this capability. Unfortunately, though - you will sacrifice a lot of the really great features available in - Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version. + Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. + Red Hat's newer version (based on 2.17.1 and soon to be merged into + the main distribution) runs on PostgreSQL. At this time we know of + no recent ports of Bugzilla to Oracle but do intend to support it + in the future (possibly the 2.20 time-frame).
A.5.2.
A.5.3. There is no facility in Bugzilla itself to do this. It's also generally not a smart thing to do if you don't know exactly what you're doing. - However, if you understand SQL you can use the mysqladmin utility to - manually insert, delete, and modify table information. Personally, I - use "phpMyAdmin". You have to compile a PHP module with MySQL - support to make it work, but it's very clean and easy to use. -
A.5.4. - I try to add myself as a user, but Bugzilla always tells me my password is wrong. -
mysql - Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled - the "crypt()" function. This prevented MySQL from storing encrypted passwords. - Upgrade to the "3.23 stable" version of MySQL and you should be good to go. + command line utility to manually insert, delete and modify table + information. There are also more intuitive GUI clients available. + Personal favorites of the Bugzilla team are phpMyAdmin and MySQL Control + Center.
A.5.5. A.5.4. I think I've set up MySQL permissions correctly, but Bugzilla still can't connect. @@ -11568,10 +11480,42 @@ CLASS="answer" > Try running MySQL from its binary: "mysqld --skip-grant-tables". This will allow you to completely rule out grant tables as the cause of your - frustration. However, I do not recommend you run it this way on a regular - basis, unless you really want your web site defaced and your machine - cracked. -
localconfig. +
Running MySQL with this command line option is very insecure and + should only be done when not connected to the external network + as a troubleshooting step. +
A.5.6. A.5.5. How do I synchronize bug information among multiple different Bugzilla databases? @@ -11626,7 +11570,7 @@ CLASS="qandaentry" CLASS="question" >
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. - Email submissions to Bugzilla that have attachments end up asking me to - save it as a "cgi" file. -
- Yup. Just rename it once you download it, or save it under a different - filename. This will not be fixed anytime soon, because it would - cripple some other functionality. -
A.7.6. How do I change a keyword in Bugzilla, once some bugs are using it?
A.8.1. Bugzilla Project Page for details on how to @@ -12042,7 +11959,7 @@ CLASS="qandaentry" CLASS="question" >
A.8.2.
A.8.3.
B.2.1. Bugzilla Database Basics
B.2.1.1. Bugzilla Database Tables
Appendix C. Useful Patches and Utilities for Bugzilla
Are you looking for a way to put your Bugzilla into overdrive? Catch + some of the niftiest tricks here in this section.
C.1. Apache + mod_rewrite + + magic
Apache's + mod_rewrite + + module lets you do some truly amazing things with URL rewriting. Here are + a couple of examples of what you can do.
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> +
There are many, many more things you can do with mod_rewrite. + Please refer to the mod_rewrite documentation at + http://www.apache.org. +
C.2. Command-line Bugzilla Queries
There are a suite of Unix utilities for querying Bugzilla from the + command line. They live in the + contrib/cmdline + directory. However, they + have not yet been updated to work with 2.16 (post-templatisation.). + There are three files - query.conf, + buglist and bugs.
query.conf + contains the mapping from options to field + names and comparison types. Quoted option names are "grepped" for, so it + should be easy to edit this file. Comments (#) have no effect; you must + make sure these lines do not contain any quoted "option".
buglist + is a shell script which submits a Bugzilla query and writes + the resulting HTML page to stdout. It supports both short options, (such + as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or + "--reporter=bar"). If the first character of an option is not "-", it is + treated as if it were prefixed with "--default=".
The column list is taken from the COLUMNLIST environment variable. + This is equivalent to the "Change Columns" option when you list bugs in + buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST + in your cookies file to see your current COLUMNLIST setting.
bugs is a simple shell script which calls + buglist and extracts the + bug numbers from the output. Adding the prefix + "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into + a working link if any bugs are found. Counting bugs is easy. Pipe the + results through + sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}' +
Akkana Peck says she has good results piping + buglist output through + w3m -T text/html -dump +
Appendix D. Bugzilla Variants and Competitors
I created this section to answer questions about Bugzilla competitors + and variants, then found a wonderful site which covers an awful lot of what + I wanted to discuss. Rather than quote it in its entirety, I'll simply + refer you here: + http://linas.org/linux/pm.html +
D.1. Red Hat Bugzilla
Red Hat's old fork of Bugzilla which was based on version 2.8 is now + obsolete. The newest version in use is based on version 2.17.1 and is in + the process of being integrated into the main Bugzilla source tree. The + back-end is modified to work with PostgreSQL instead of MySQL and they have + custom templates to get their desired look and feel, but other than that it + is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of + effort to make sure that the changes he made could be integrated back into + the main tree. + Bug + 98304 exists to track this integration. +
URL: + http://bugzilla.redhat.com/bugzilla/ +
This section last updated 24 Dec 2002
D.2. Loki Bugzilla (Fenris)
Fenris was a fork from Bugzilla made by Loki Games; when + Loki went into receivership, it died. While Loki's other code lives on, + its custodians recommend Bugzilla for future bug-tracker deployments. +
This section last updated 27 Jul 2002
D.3. Issuezilla
Issuezilla was another fork from Bugzilla, made by collab.net and + hosted at tigris.org. It is also dead; the primary focus of bug-tracking + at tigris.org is their Java-based bug-tracker, + Section D.4.
This section last updated 27 Jul 2002
D.4. Scarab
Scarab is a new open source bug-tracking system built using Java + Servlet technology. It is currently at version 1.0 beta 13.
URL: + http://scarab.tigris.org +
This section last updated 18 Jan 2003
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as + such through the "jobs" + functionality.
URL: + http://www.perforce.com/perforce/technotes/note052.html + +
This section last updated 27 Jul 2002
D.6. SourceForge
SourceForge is a way of coordinating geographically + distributed free software and open source projects over the Internet. + It has a built-in bug tracker, but it's not highly thought of.
URL: + http://www.sourceforge.net +
This section last updated 27 Jul 2002
Appendix E. GNU Free Documentation License
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, + Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and + distribute verbatim copies of this license document, but changing it is + not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other + written document "free" in the sense of freedom: to assure everyone the + effective freedom to copy and redistribute it, with or without modifying + it, either commercially or noncommercially. Secondarily, this License + preserves for the author and publisher a way to get credit for their + work, while not being considered responsible for modifications made by + others.
This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. It + complements the GNU General Public License, which is a copyleft license + designed for free software.
We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a free + program should come with manuals providing the same freedoms that the + software does. But this License is not limited to software manuals; it + can be used for any textual work, regardless of subject matter or whether + it is published as a printed book. We recommend this License principally + for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be distributed under + the terms of this License. The "Document", below, refers to any such + manual or work. Any member of the public is a licensee, and is addressed + as "you".
A "Modified Version" of the Document means any work containing the + Document or a portion of it, either copied verbatim, or with + modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section + of the Document that deals exclusively with the relationship of the + publishers or authors of the Document to the Document's overall subject + (or to related matters) and contains nothing that could fall directly + within that overall subject. (For example, if the Document is in part a + textbook of mathematics, a Secondary Section may not explain any + mathematics.) The relationship could be a matter of historical connection + with the subject or with related matters, or of legal, commercial, + philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose + titles are designated, as being those of Invariant Sections, in the + notice that says that the Document is released under this License.
The "Cover Texts" are certain short passages of text that are + listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says + that the Document is released under this License.
A "Transparent" copy of the Document means a machine-readable copy, + represented in a format whose specification is available to the general + public, whose contents can be viewed and edited directly and + straightforwardly with generic text editors or (for images composed of + pixels) generic paint programs or (for drawings) some widely available + drawing editor, and that is suitable for input to text formatters or for + automatic translation to a variety of formats suitable for input to text + formatters. A copy made in an otherwise Transparent file format whose + markup has been designed to thwart or discourage subsequent modification + by readers is not Transparent. A copy that is not "Transparent" is called + "Opaque".
Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, SGML or + XML using a publicly available DTD, and standard-conforming simple HTML + designed for human modification. Opaque formats include PostScript, PDF, + proprietary formats that can be read and edited only by proprietary word + processors, SGML or XML for which the DTD and/or processing tools are not + generally available, and the machine-generated HTML produced by some word + processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the material + this License requires to appear in the title page. For works in formats + which do not have any title page as such, "Title Page" means the text + near the most prominent appearance of the work's title, preceding the + beginning of the body of the text.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License applies to + the Document are reproduced in all copies, and that you add no other + conditions whatsoever to those of this License. You may not use technical + measures to obstruct or control the reading or further copying of the + copies you make or distribute. However, you may accept compensation in + exchange for copies. If you distribute a large enough number of copies + you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, + and you may publicly display copies.
Appendix C. Useful Patches and Utilities for Bugzilla
3. COPYING IN QUANTITY
Are you looking for a way to put your Bugzilla into overdrive? Catch - some of the niftiest tricks here in this section.
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.
C.1. Apache - mod_rewrite - - magic
4. MODIFICATIONS
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.
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:
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> -
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.
There are many, many more things you can do with mod_rewrite. - Please refer to the mod_rewrite documentation at - http://www.apache.org. -
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.
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.
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.
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".
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.
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=".
Delete any section entitled "Endorsements". Such a section may + not be included in the Modified Version.
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.
Do not retitle any existing section as "Endorsements" or to + conflict in title with any Invariant Section.
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"}' -
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.
Akkana Peck says she has good results piping - buglist output through - w3m -T text/html -dump -
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.
Appendix D. Bugzilla Variants and Competitors
5. COMBINING DOCUMENTS
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 -
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."
D.1. Red Hat Bugzilla
6. COLLECTIONS OF DOCUMENTS
Red Hat Bugzilla is a fork of Bugzilla 2.8. - One of its major benefits is the ability - to work with Oracle, MySQL, and PostGreSQL databases serving as the - back-end, instead of just MySQL. Dave Lawrence of Red Hat is - active in the Bugzilla community, and we hope to see a reunification - of the fork before too long.
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.
URL: - http://bugzilla.redhat.com/bugzilla/ -
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.2. Loki Bugzilla (Fenris)
7. AGGREGATION WITH INDEPENDENT WORKS
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. -
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.
D.3. Issuezilla
8. TRANSLATION
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.
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.
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.
9. TERMINATION
URL: - http://scarab.tigris.org -
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.
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as - such through the "jobs" - functionality.
10. FUTURE REVISIONS OF THIS LICENSE
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://www.perforce.com/perforce/technotes/note052.html - 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.
D.6. SourceForge
How to use this License for your documents
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.
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:
URL: - http://www.sourceforge.net -
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.
0-9, high ascii
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. +
Bugzilla
C
Common Gateway Interface
(CGI)
CGI is an acronym for Common Gateway Interface. + This is a standard for interfacing an external application with a web + server. Bugzilla is an example of a CGI application. +
G
M
Message Transport Agent
(MTA)
A Message Transport Agent is used to control the flow of email + on a system. Many unix based systems use + sendmail which is what + Bugzilla expects to find by default at /usr/sbin/sendmail. + Many other MTA's will work, but they all require that the + sendmailnow param be set to on. +
mysqldMySQL
mysqld is the name of the - MySQL is currently the required + daemon - - for the MySQL database. In general, it is invoked automatically - through the use of the System V init scripts on GNU/Linux and - AT&T System V-based systems, such as Solaris and HP/UX, or - through the RC scripts on BSD-based systems.
RDBMS for Bugzilla. MySQL + can be downloaded from http://www.mysql.com. While you + should familiarize yourself with all of the documentation, some high + points are: +
MySQL + Privilege System - Much more detailed information about + the suggestions in Section 5.6.2. +
R
Relational DataBase Managment System
(RDBMS)
A relational database management system is a database system + that stores information in tables that are related to each other. +
S
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. +
Zarro Boogs Found
This is the cryptic response sent by Bugzilla when a query - returned no results. It is just a goofy way of saying "Zero Bugs - Found".
This is just a goofy way of saying that there were no bugs + found matching your query. When asked to explain this message, + Terry had the following to say: +

I've been asked to explain this ... way back when, when + Netscape released version 4.0 of its browser, we had a release + party. Naturally, there had been a big push to try and fix every + known bug before the release. Naturally, that hadn't actually + happened. (This is not unique to Netscape or to 4.0; the same thing + has happened with every software project I've ever seen.) Anyway, + at the release party, T-shirts were handed out that said something + like "Netscape 4.0: Zarro Boogs". Just like the software, the + T-shirt had no known bugs. Uh-huh. +
So, when you query for a list of bugs, and it gets no results, + you can think of this as a friendly reminder. Of *course* there are + bugs matching your query, they just aren't in the bugsystem yet... +

--Terry Weissman
5.7.1. What to Edit
5.7.2. How To Edit Templates
5.7.3. Template Formats
5.7.4. Particular Templates

Warnings

Information requiring special attention

Term found in the glossary

Bugzilla +

Code Example

Appendix E.

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

1. APPLICABILITY AND DEFINITIONS

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.

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.

2. VERBATIM COPYING

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

3. COPYING IN QUANTITY

4. MODIFICATIONS

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.

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

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

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

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

Matthew P. Barnson <mbarnson@sisna.com>

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

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

Terry Weissman <terry@mozilla.org>

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

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

Tara Hernandez <tara@tequilarists.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 -

for keeping Bugzilla development going strong after Terry left + mozilla.org and for running landfill. +

Dave Lawrence <dkl@redhat.com>

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

for providing insight into the key differences between Red + Hat's customized Bugzilla, and being largely responsible for + Section D.1. +

Dawn Endico <endico@mozilla.org>

for being a hacker extraordinaire and putting up with Matthew's + incessant questions and arguments on irc.mozilla.org in #mozwebtools +

Jacob Steenhagen <jake@bugzilla.org>

for taking over documentation during the 2.17 development + period and backporting relevent docs changes to this 2.16 branch. +

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

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

Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, - Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham. + to this documentation (in alphabetical order): + Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption + .

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

4.2.1. Dependency Charts

4.2.2. Bug Graphs

4.2.3. The Whining Cron

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 compatability +HREF="faq.html#faq-general-bzmissing" +> 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? +HREF="faq.html#faq-general-bonsaitools" +> 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?

AtHome Corporation

Red Hat Software

This convention was abonded during the 2.17 development cycle so + it will no longer be an issue when 2.18 comes out. +

A.4.3. Try Klaas Freitag's excellent patch for "whineatassigned" functionality. - You can find it at http://bugzilla.mozilla.org/show_bug.cgi?id=6679http://bugzilla.mozilla.org/show_bug.cgi?id=6679. This patch is against an older version of Bugzilla, so you must apply the diffs manually. @@ -1805,7 +1941,7 @@ CLASS="qandaentry" CLASS="question" >

Prev	Home	Next
GNU Free Documentation License	Up	APPLICABILITY AND DEFINITIONS

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

1.2. Disclaimer

1.3. New Versions

1.4. Credits

1.5. Document Conventions

3.2.1. Autolinkification

3.2.5. Filing Bugs

4.1.1. Introduction

4.1.2. Package List

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)

4.1.5.6. Chart::Base (optional)

4.1.5.7. Template Toolkit

4.1.6. HTTP Server

4.1.7. Bugzilla

4.1.8. Setting Up the MySQL Database

4.1.10. Configuring Bugzilla

4.2.1. Dependency Charts

4.2.2. Bug Graphs

4.2.3. The Whining Cron

4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1

4.5.2. DBD::Sponge::db prepare failed

4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT

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

Appendix C. Useful Patches and Utilities for Bugzilla

C.1. Apache + mod_rewrite + + magic

C.2. Command-line Bugzilla Queries

Appendix D. Bugzilla Variants and Competitors

D.1. Red Hat Bugzilla

D.2. Loki Bugzilla (Fenris)

D.3. Issuezilla

D.4. Scarab

D.5. Perforce SCM

D.6. SourceForge

Appendix E. GNU Free Documentation License

0. PREAMBLE

1. APPLICABILITY AND DEFINITIONS

2. VERBATIM COPYING

Appendix C. Useful Patches and Utilities for Bugzilla

C.1. Apache - mod_rewrite - - magic

C.2. Command-line Bugzilla Queries

Appendix D. Bugzilla Variants and Competitors

D.1. Red Hat Bugzilla

D.2. Loki Bugzilla (Fenris)

D.3. Issuezilla

D.4. Scarab

D.5. Perforce SCM

D.6. SourceForge

0-9, high ascii

R

S

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

`5.7.1. What to Edit`

`5.7.2. How To Edit Templates`

`5.7.3. Template Formats`

`5.7.4. Particular Templates`

C.1. Apache + `mod_rewrite` + + magic

C.1. Apache - `mod_rewrite` - - magic

4.1.9. `4.1.10. Configuring Bugzilla 4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 4.5.2. DBD::Sponge::db prepare failed`

`4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT`

`D.1. Red Hat Bugzilla`