From d749474311698d52abfecf3ddb0f9d9a2293b4ad Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" Date: Wed, 23 Apr 2003 02:34:37 +0000 Subject: [PATCH] Recompile the docs in anticipation of the 2.16.3 release. git-svn-id: svn://10.0.0.236/branches/BUGZILLA-2_16-BRANCH@141657 18797224-902f-48f8-a5cc-f745e15eee43 --- .../bugzilla/docs/html/Bugzilla-Guide.html | 2537 +++++++++++------ .../bugzilla/docs/html/administration.html | 8 +- .../bugzilla/docs/html/conventions.html | 23 +- .../bugzilla/docs/html/copyright.html | 508 +--- .../webtools/bugzilla/docs/html/credits.html | 145 +- .../bugzilla/docs/html/cust-templates.html | 8 +- .../webtools/bugzilla/docs/html/dbdoc.html | 4 +- .../bugzilla/docs/html/extraconfig.html | 6 +- mozilla/webtools/bugzilla/docs/html/faq.html | 662 +++-- .../webtools/bugzilla/docs/html/gfdl-0.html | 165 ++ .../webtools/bugzilla/docs/html/gfdl-1.html | 200 ++ .../webtools/bugzilla/docs/html/gfdl-10.html | 165 ++ .../webtools/bugzilla/docs/html/gfdl-2.html | 157 + .../webtools/bugzilla/docs/html/gfdl-3.html | 179 ++ .../webtools/bugzilla/docs/html/gfdl-4.html | 273 ++ .../webtools/bugzilla/docs/html/gfdl-5.html | 166 ++ .../webtools/bugzilla/docs/html/gfdl-6.html | 156 + .../webtools/bugzilla/docs/html/gfdl-7.html | 159 ++ .../webtools/bugzilla/docs/html/gfdl-8.html | 155 + .../html/{rhbugzilla.html => gfdl-9.html} | 55 +- .../bugzilla/docs/html/gfdl-howto.html | 172 ++ mozilla/webtools/bugzilla/docs/html/gfdl.html | 218 ++ .../webtools/bugzilla/docs/html/glossary.html | 321 ++- .../bugzilla/docs/html/hintsandtips.html | 4 +- .../webtools/bugzilla/docs/html/index.html | 101 +- .../bugzilla/docs/html/installation.html | 29 +- .../bugzilla/docs/html/newversions.html | 36 +- mozilla/webtools/bugzilla/docs/html/osx.html | 2 +- .../bugzilla/docs/html/stepbystep.html | 56 +- .../bugzilla/docs/html/troubleshooting.html | 114 +- .../webtools/bugzilla/docs/html/using.html | 4 +- .../bugzilla/docs/html/variant-fenris.html | 8 +- .../docs/html/variant-issuezilla.html | 4 +- .../bugzilla/docs/html/variant-perforce.html | 2 + .../bugzilla/docs/html/variant-redhat.html | 4 +- .../bugzilla/docs/html/variant-scarab.html | 4 +- .../docs/html/variant-sourceforge.html | 12 +- .../webtools/bugzilla/docs/html/variants.html | 8 +- .../webtools/bugzilla/docs/html/whatis.html | 10 +- .../webtools/bugzilla/docs/html/win32.html | 8 +- .../bugzilla/docs/txt/Bugzilla-Guide.txt | 2 +- 41 files changed, 4966 insertions(+), 1884 deletions(-) create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-0.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-1.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-10.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-2.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-3.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-4.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-5.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-6.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-7.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-8.html rename mozilla/webtools/bugzilla/docs/html/{rhbugzilla.html => gfdl-9.html} (60%) create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl-howto.html create mode 100644 mozilla/webtools/bugzilla/docs/html/gfdl.html diff --git a/mozilla/webtools/bugzilla/docs/html/Bugzilla-Guide.html b/mozilla/webtools/bugzilla/docs/html/Bugzilla-Guide.html index 9f78b6aac06..1e70196e65a 100644 --- a/mozilla/webtools/bugzilla/docs/html/Bugzilla-Guide.html +++ b/mozilla/webtools/bugzilla/docs/html/Bugzilla-Guide.html @@ -58,7 +58,7 @@ NAME="AEN9" >The Bugzilla Team

2003-02-16

2003-04-23

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

D.1. Red Hat Bugzilla
E. GNU Free Documentation License
0. PREAMBLE
1. APPLICABILITY AND DEFINITIONS
2. VERBATIM COPYING
3. COPYING IN QUANTITY
4. MODIFICATIONS
5. COMBINING DOCUMENTS
6. COLLECTIONS OF DOCUMENTS
7. AGGREGATION WITH INDEPENDENT WORKS
8. TRANSLATION
9. TERMINATION
10. FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
Glossary
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
Appendix E.

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

  1. Use in the Title Page (and on the covers, if any) a title - distinct from that of the Document, and from those of previous - versions (which should, if there were any, be listed in the History - section of the Document). You may use the same title as a previous - version if the original publisher of that version gives - permission.

  2. List on the Title Page, as authors, one or more persons or - entities responsible for authorship of the modifications in the - Modified Version, together with at least five of the principal - authors of the Document (all of its principal authors, if it has less - than five).

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

  4. Preserve all the copyright notices of the Document.

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

  6. Include, immediately after the copyright notices, a license - notice giving the public permission to use the Modified Version under - the terms of this License, in the form shown in the Addendum - below.

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

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add - to it an item stating at least the title, year, new authors, and - publisher of the Modified Version as given on the Title Page. If - there is no section entitled "History" in the Document, create one - stating the title, year, authors, and publisher of the Document as - given on its Title Page, then add an item describing the Modified - Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document - for public access to a Transparent copy of the Document, and likewise - the network locations given in the Document for previous versions it - was based on. These may be placed in the "History" section. You may - omit a network location for a work that was published at least four - years before the Document itself, or if the original publisher of the - version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", - preserve the section's title, and preserve in the section all the - substance and tone of each of the contributor acknowledgements and/or - dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered - in their text and in their titles. Section numbers or the equivalent - are not considered part of the section titles.

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

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

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

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

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

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

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

This document can be found in the following places: -

+>The Linux Documentation Project.

The latest version of this document can always be checked out via CVS. @@ -1100,66 +679,115 @@ NAME="credits" contribution to the Bugzilla community:

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

WarningsUse cautionInformation requiring special attentionWarningsTerm 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?
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? @@ -9679,35 +9475,35 @@ HREF="#AEN1875" >
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 @@ -9716,28 +9512,28 @@ HREF="#AEN1906" >
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? @@ -9745,19 +9541,19 @@ HREF="#AEN1929" >
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 @@ -9767,7 +9563,7 @@ HREF="#AEN1945" >
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 @@ -9777,7 +9573,7 @@ HREF="#AEN1951" >
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. @@ -9823,48 +9619,48 @@ HREF="#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 try to add myself as a user, but Bugzilla always tells me my password is wrong. -
A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla still can't connect.
A.5.6. 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. Email submissions to Bugzilla that have attachments end up asking me to - save it as a "cgi" file. -
A.7.6. How do I change a keyword in Bugzilla, once some bugs are using it?
A.8.1. What bugs are in Bugzilla right now?
A.8.2. How can I change the default priority to a null value? For instance, have the default priority be "---" instead of "P2"?
A.8.3. What's the best way to submit patches? What guidelines should I follow?

A.1.1.

A.1.2.

A.1.3. - http://bugzilla.org/consulting.html + is a list of people and companies who have asked us to list them + as consultants for Bugzilla. +

www.collab.net

A.1.4. There are dozens of major comapanies with public +> of major companies with public Bugzilla sites to track bugs in their products. A few include:

AtHome CorporationRed Hat Software

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

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. + However, if you understand SQL you can use the mysql + 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.4. - I try to add myself as a user, but Bugzilla always tells me my password is wrong. -

- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled - the "crypt()" function. This prevented MySQL from storing encrypted passwords. - Upgrade to the "3.23 stable" version of MySQL and you should be good to go. -

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

D.1. Red Hat Bugzilla

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.

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

This section last updated 27 Jul 2002

ScarabSection D.4.

This section last updated 27 Jul 2002

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: http://scarab.tigris.org

This section last updated 18 Jan 2003

This section last updated 27 Jul 2002

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.

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:

  1. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of previous + versions (which should, if there were any, be listed in the History + section of the Document). You may use the same title as a previous + version if the original publisher of that version gives + permission.

  2. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in the + Modified Version, together with at least five of the principal + authors of the Document (all of its principal authors, if it has less + than five).

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

  4. Preserve all the copyright notices of the Document.

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

  6. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified Version under + the terms of this License, in the form shown in the Addendum + below.

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

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document + for public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions it + was based on. These may be placed in the "History" section. You may + omit a network location for a work that was published at least four + years before the Document itself, or if the original publisher of the + version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", + preserve the section's title, and preserve in the section all the + substance and tone of each of the contributor acknowledgements and/or + dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered + in their text and in their titles. Section numbers or the equivalent + are not considered part of the section titles.

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

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

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

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

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

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

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.

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

MySQL

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

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

WarningsUse cautionInformation requiring special attentionWarningsTerm found in the glossary Bugzilla + Code ExampleAppendix E.

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

  1. Use in the Title Page (and on the covers, if any) a title - distinct from that of the Document, and from those of previous - versions (which should, if there were any, be listed in the History - section of the Document). You may use the same title as a previous - version if the original publisher of that version gives - permission.

  2. List on the Title Page, as authors, one or more persons or - entities responsible for authorship of the modifications in the - Modified Version, together with at least five of the principal - authors of the Document (all of its principal authors, if it has less - than five).

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

  4. Preserve all the copyright notices of the Document.

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

  6. Include, immediately after the copyright notices, a license - notice giving the public permission to use the Modified Version under - the terms of this License, in the form shown in the Addendum - below.

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

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add - to it an item stating at least the title, year, new authors, and - publisher of the Modified Version as given on the Title Page. If - there is no section entitled "History" in the Document, create one - stating the title, year, authors, and publisher of the Document as - given on its Title Page, then add an item describing the Modified - Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document - for public access to a Transparent copy of the Document, and likewise - the network locations given in the Document for previous versions it - was based on. These may be placed in the "History" section. You may - omit a network location for a work that was published at least four - years before the Document itself, or if the original publisher of the - version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", - preserve the section's title, and preserve in the section all the - substance and tone of each of the contributor acknowledgements and/or - dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered - in their text and in their titles. Section numbers or the equivalent - are not considered part of the section titles.

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

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

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

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

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

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

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.

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?
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 +208,35 @@ HREF="faq.html#AEN1875" >
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 +245,28 @@ HREF="faq.html#AEN1906" >
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 +274,19 @@ HREF="faq.html#AEN1929" >
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 +296,7 @@ HREF="faq.html#AEN1945" >
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 +306,7 @@ HREF="faq.html#AEN1951" >
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 +352,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 try to add myself as a user, but Bugzilla always tells me my password is wrong. -
A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla still can't connect.
A.5.6. 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. Email submissions to Bugzilla that have attachments end up asking me to - save it as a "cgi" file. -
A.7.6. How do I change a keyword in Bugzilla, once some bugs are using it?
A.8.1. What bugs are in Bugzilla right now?
A.8.2. How can I change the default priority to a null value? For instance, have the default priority be "---" instead of "P2"?
A.8.3. What's the best way to submit patches? What guidelines should I follow?

A.1.1.

A.1.2.

A.1.3. - http://bugzilla.org/consulting.html + is a list of people and companies who have asked us to list them + as consultants for Bugzilla. +

www.collab.net

A.1.4. There are dozens of major comapanies with public +> of major companies with public Bugzilla sites to track bugs in their products. A few include:

AtHome CorporationRed Hat Software

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

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. @@ -1805,7 +1941,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. + However, if you understand SQL you can use the mysql + 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.4. - I try to add myself as a user, but Bugzilla always tells me my password is wrong. -

- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled - the "crypt()" function. This prevented MySQL from storing encrypted passwords. - Upgrade to the "3.23 stable" version of MySQL and you should be good to go. -

A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla still can't connect. @@ -2090,10 +2213,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? @@ -2148,7 +2303,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 @@ -2564,7 +2692,7 @@ CLASS="qandaentry" CLASS="question" >

A.8.2.

A.8.3. PREAMBLE

The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other + written document "free" in the sense of freedom: to assure everyone the + effective freedom to copy and redistribute it, with or without modifying + it, either commercially or noncommercially. Secondarily, this License + preserves for the author and publisher a way to get credit for their + work, while not being considered responsible for modifications made by + others.

This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. It + complements the GNU General Public License, which is a copyleft license + designed for free software.

We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a free + program should come with manuals providing the same freedoms that the + software does. But this License is not limited to software manuals; it + can be used for any textual work, regardless of subject matter or whether + it is published as a printed book. We recommend this License principally + for works whose purpose is instruction or reference.

PrevHomeNext
GNU Free Documentation LicenseUpAPPLICABILITY AND DEFINITIONS
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-1.html b/mozilla/webtools/bugzilla/docs/html/gfdl-1.html new file mode 100644 index 00000000000..8c611d6dfd3 --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-1.html @@ -0,0 +1,200 @@ +APPLICABILITY AND DEFINITIONS
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be distributed under + the terms of this License. The "Document", below, refers to any such + manual or work. Any member of the public is a licensee, and is addressed + as "you".

A "Modified Version" of the Document means any work containing the + Document or a portion of it, either copied verbatim, or with + modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section + of the Document that deals exclusively with the relationship of the + publishers or authors of the Document to the Document's overall subject + (or to related matters) and contains nothing that could fall directly + within that overall subject. (For example, if the Document is in part a + textbook of mathematics, a Secondary Section may not explain any + mathematics.) The relationship could be a matter of historical connection + with the subject or with related matters, or of legal, commercial, + philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose + titles are designated, as being those of Invariant Sections, in the + notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are + listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says + that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, + represented in a format whose specification is available to the general + public, whose contents can be viewed and edited directly and + straightforwardly with generic text editors or (for images composed of + pixels) generic paint programs or (for drawings) some widely available + drawing editor, and that is suitable for input to text formatters or for + automatic translation to a variety of formats suitable for input to text + formatters. A copy made in an otherwise Transparent file format whose + markup has been designed to thwart or discourage subsequent modification + by readers is not Transparent. A copy that is not "Transparent" is called + "Opaque".

Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, SGML or + XML using a publicly available DTD, and standard-conforming simple HTML + designed for human modification. Opaque formats include PostScript, PDF, + proprietary formats that can be read and edited only by proprietary word + processors, SGML or XML for which the DTD and/or processing tools are not + generally available, and the machine-generated HTML produced by some word + processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the material + this License requires to appear in the title page. For works in formats + which do not have any title page as such, "Title Page" means the text + near the most prominent appearance of the work's title, preceding the + beginning of the body of the text.

PrevHomeNext
PREAMBLEUpVERBATIM COPYING
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-10.html b/mozilla/webtools/bugzilla/docs/html/gfdl-10.html new file mode 100644 index 00000000000..9ab07bdb1ad --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-10.html @@ -0,0 +1,165 @@ +FUTURE REVISIONS OF THIS LICENSE
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

10. FUTURE REVISIONS OF THIS LICENSE

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

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

PrevHomeNext
TERMINATIONUpHow to use this License for your documents
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-2.html b/mozilla/webtools/bugzilla/docs/html/gfdl-2.html new file mode 100644 index 00000000000..0e7b5928324 --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-2.html @@ -0,0 +1,157 @@ +VERBATIM COPYING
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License applies to + the Document are reproduced in all copies, and that you add no other + conditions whatsoever to those of this License. You may not use technical + measures to obstruct or control the reading or further copying of the + copies you make or distribute. However, you may accept compensation in + exchange for copies. If you distribute a large enough number of copies + you must also follow the conditions in section 3.

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

PrevHomeNext
APPLICABILITY AND DEFINITIONSUpCOPYING IN QUANTITY
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-3.html b/mozilla/webtools/bugzilla/docs/html/gfdl-3.html new file mode 100644 index 00000000000..eb6f8bef89b --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-3.html @@ -0,0 +1,179 @@ +COPYING IN QUANTITY
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

3. COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than + 100, and the Document's license notice requires Cover Texts, you must + enclose the copies in covers that carry, clearly and legibly, all these + Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts + on the back cover. Both covers must also clearly and legibly identify you + as the publisher of these copies. The front cover must present the full + title with all words of the title equally prominent and visible. You may + add other material on the covers in addition. Copying with changes + limited to the covers, as long as they preserve the title of the Document + and satisfy these conditions, can be treated as verbatim copying in other + respects.

If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit reasonably) + on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a machine-readable + Transparent copy along with each Opaque copy, or state in or with each + Opaque copy a publicly-accessible computer-network location containing a + complete Transparent copy of the Document, free of added material, which + the general network-using public has access to download anonymously at no + charge using public-standard network protocols. If you use the latter + option, you must take reasonably prudent steps, when you begin + distribution of Opaque copies in quantity, to ensure that this + Transparent copy will remain thus accessible at the stated location until + at least one year after the last time you distribute an Opaque copy + (directly or through your agents or retailers) of that edition to the + public.

It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of copies, to + give them a chance to provide you with an updated version of the + Document.

PrevHomeNext
VERBATIM COPYINGUpMODIFICATIONS
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-4.html b/mozilla/webtools/bugzilla/docs/html/gfdl-4.html new file mode 100644 index 00000000000..282817958e1 --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-4.html @@ -0,0 +1,273 @@ +MODIFICATIONS
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you release + the Modified Version under precisely this License, with the Modified + Version filling the role of the Document, thus licensing distribution and + modification of the Modified Version to whoever possesses a copy of it. + In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of previous + versions (which should, if there were any, be listed in the History + section of the Document). You may use the same title as a previous + version if the original publisher of that version gives + permission.

  2. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in the + Modified Version, together with at least five of the principal + authors of the Document (all of its principal authors, if it has less + than five).

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

  4. Preserve all the copyright notices of the Document.

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

  6. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified Version under + the terms of this License, in the form shown in the Addendum + below.

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

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document + for public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions it + was based on. These may be placed in the "History" section. You may + omit a network location for a work that was published at least four + years before the Document itself, or if the original publisher of the + version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", + preserve the section's title, and preserve in the section all the + substance and tone of each of the contributor acknowledgements and/or + dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered + in their text and in their titles. Section numbers or the equivalent + are not considered part of the section titles.

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

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

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

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

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

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

PrevHomeNext
COPYING IN QUANTITYUpCOMBINING DOCUMENTS
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-5.html b/mozilla/webtools/bugzilla/docs/html/gfdl-5.html new file mode 100644 index 00000000000..943cce21983 --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-5.html @@ -0,0 +1,166 @@ +COMBINING DOCUMENTS
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

5. COMBINING DOCUMENTS

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

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

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

PrevHomeNext
MODIFICATIONSUpCOLLECTIONS OF DOCUMENTS
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-6.html b/mozilla/webtools/bugzilla/docs/html/gfdl-6.html new file mode 100644 index 00000000000..82219372d6b --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-6.html @@ -0,0 +1,156 @@ +COLLECTIONS OF DOCUMENTS
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

6. COLLECTIONS OF DOCUMENTS

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

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

PrevHomeNext
COMBINING DOCUMENTSUpAGGREGATION WITH INDEPENDENT WORKS
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-7.html b/mozilla/webtools/bugzilla/docs/html/gfdl-7.html new file mode 100644 index 00000000000..5fb7e44336f --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-7.html @@ -0,0 +1,159 @@ +AGGREGATION WITH INDEPENDENT WORKS
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

7. AGGREGATION WITH INDEPENDENT WORKS

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

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

PrevHomeNext
COLLECTIONS OF DOCUMENTSUpTRANSLATION
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl-8.html b/mozilla/webtools/bugzilla/docs/html/gfdl-8.html new file mode 100644 index 00000000000..c2b9526faec --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-8.html @@ -0,0 +1,155 @@ +TRANSLATION
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

8. TRANSLATION

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

PrevHomeNext
AGGREGATION WITH INDEPENDENT WORKSUpTERMINATION
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/rhbugzilla.html b/mozilla/webtools/bugzilla/docs/html/gfdl-9.html similarity index 60% rename from mozilla/webtools/bugzilla/docs/html/rhbugzilla.html rename to mozilla/webtools/bugzilla/docs/html/gfdl-9.html index f02c9165c60..ca5f5715300 100644 --- a/mozilla/webtools/bugzilla/docs/html/rhbugzilla.html +++ b/mozilla/webtools/bugzilla/docs/html/gfdl-9.html @@ -1,7 +1,7 @@ Red Hat BugzillaTERMINATIONPrevAppendix D. Bugzilla Variants and CompetitorsAppendix E. GNU Free Documentation LicenseNext

D.1. Red Hat Bugzilla

9. TERMINATION

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.

URL: - http://bugzilla.redhat.com/bugzilla/ -

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.

PrevNextBugzilla Variants and CompetitorsTRANSLATIONUpLoki Bugzilla (Fenris)FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
The Bugzilla Guide - 2.16.3 Release
PrevAppendix E. GNU Free Documentation LicenseNext

How to use this License for your documents

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

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

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

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

PrevHomeNext
FUTURE REVISIONS OF THIS LICENSEUpGlossary
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/gfdl.html b/mozilla/webtools/bugzilla/docs/html/gfdl.html new file mode 100644 index 00000000000..d7a9ffe2c3a --- /dev/null +++ b/mozilla/webtools/bugzilla/docs/html/gfdl.html @@ -0,0 +1,218 @@ +GNU Free Documentation License
The Bugzilla Guide - 2.16.3 Release
PrevNext

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.

PrevHomeNext
SourceForge PREAMBLE
\ No newline at end of file diff --git a/mozilla/webtools/bugzilla/docs/html/glossary.html b/mozilla/webtools/bugzilla/docs/html/glossary.html index e2280366a56..06257255b96 100644 --- a/mozilla/webtools/bugzilla/docs/html/glossary.html +++ b/mozilla/webtools/bugzilla/docs/html/glossary.html @@ -10,8 +10,8 @@ REL="HOME" TITLE="The Bugzilla Guide - 2.16.3 Release" HREF="index.html">Prev

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

MySQL

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

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 
PrevSourceForgeHow to use this License for your documents

3.2.1. Autolinkification

3.2.5. Filing Bugs

The Bugzilla Team

2003-02-16

2003-04-23

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

D.1. Red Hat Bugzilla
E. GNU Free Documentation License
0. PREAMBLE
1. APPLICABILITY AND DEFINITIONS
2. VERBATIM COPYING
3. COPYING IN QUANTITY
4. MODIFICATIONS
5. COMBINING DOCUMENTS
6. COLLECTIONS OF DOCUMENTS
7. AGGREGATION WITH INDEPENDENT WORKS
8. TRANSLATION
9. TERMINATION
10. FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
Glossary
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
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. 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
cannot chdir(/var/spool/mqueue)
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
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 + 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.

This document can be found in the following places: -

+>The Linux Documentation Project.

The latest version of this document can always be checked out via CVS. diff --git a/mozilla/webtools/bugzilla/docs/html/osx.html b/mozilla/webtools/bugzilla/docs/html/osx.html index 94a388a2da7..62ed7445625 100644 --- a/mozilla/webtools/bugzilla/docs/html/osx.html +++ b/mozilla/webtools/bugzilla/docs/html/osx.html @@ -125,7 +125,7 @@ CLASS="command" 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 diff --git a/mozilla/webtools/bugzilla/docs/html/stepbystep.html b/mozilla/webtools/bugzilla/docs/html/stepbystep.html index 6950950f8f1..c3a9c01cf92 100644 --- a/mozilla/webtools/bugzilla/docs/html/stepbystep.html +++ b/mozilla/webtools/bugzilla/docs/html/stepbystep.html @@ -81,7 +81,7 @@ CLASS="section" >

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.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;
+   };
+
3.2.1. Autolinkification
3.2.5. Filing Bugs
Prev

This section last updated 27 Jul 2002

PrevScarabSection D.4.

This section last updated 27 Jul 2002

This section last updated 27 Jul 2002

The Bugzilla Guide - 2.17.4 Development ReleaseThe Bugzilla Guide - 2.16.3 ReleaseD.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: http://scarab.tigris.org

This section last updated 18 Jan 2003

Next http://www.sourceforge.net

This section last updated 27 Jul 2002

NextGlossaryGNU Free Documentation License
Next
D.1. Red Hat Bugzilla
Next 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 diff --git a/mozilla/webtools/bugzilla/docs/html/win32.html b/mozilla/webtools/bugzilla/docs/html/win32.html index 9cae93b7737..840a4303df5 100644 --- a/mozilla/webtools/bugzilla/docs/html/win32.html +++ b/mozilla/webtools/bugzilla/docs/html/win32.html @@ -389,7 +389,7 @@ CLASS="command" >

From Andrew Pearson: