Skip to content

bugzilla
bugzilla
Commit 393f13a4 authored by jake%bugzilla.org's avatar jake%bugzilla.org
Browse files
Options

Recompiling the docs because of the large change to the installation section just checked in.

parent 3b3f69d7
Show whitespace changes
Inline Side-by-side
Showing with 4874 additions and 3710 deletions
docs/html/Bugzilla-Guide.html
View file @ 393f13a4
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/html/administration.html
View file @ 393f13a4
......@@ -156,22 +156,22 @@ HREF="cust-templates.html"
><DL
><DT
>5.7.1. <A
HREF="cust-templates.html#AEN1610"
HREF="cust-templates.html#AEN1409"
>What to Edit</A
></DT
><DT
>5.7.2. <A
HREF="cust-templates.html#AEN1629"
HREF="cust-templates.html#AEN1428"
>How To Edit Templates</A
></DT
><DT
>5.7.3. <A
HREF="cust-templates.html#AEN1639"
HREF="cust-templates.html#AEN1438"
>Template Formats</A
></DT
><DT
>5.7.4. <A
HREF="cust-templates.html#AEN1652"
HREF="cust-templates.html#AEN1451"
>Particular Templates</A
></DT
></DL
......
docs/html/conventions.html
View file @ 393f13a4
......@@ -81,7 +81,7 @@ NAME="conventions"
><DIV
CLASS="informaltable"
><A
NAME="AEN175"
NAME="AEN80"
></A
><P
></P
......
docs/html/copyright.html
View file @ 393f13a4
......@@ -77,7 +77,7 @@ NAME="copyright"
></A
>1.1. Copyright Information</H1
><A
NAME="AEN33"
NAME="AEN34"
></A
><TABLE
BORDER="0"
......@@ -99,7 +99,10 @@ VALIGN="TOP"
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
the license is included below.
the license is included in <A
HREF="gfdl.html"
>Appendix E</A
>.
</P
></TD
><TD
......@@ -114,7 +117,7 @@ ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
>Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
>Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN
></TD
><TD
WIDTH="10%"
......@@ -126,507 +129,6 @@ WIDTH="10%"
copyright, or publishing this document in non-electronic form,
please contact The Bugzilla Team.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="gfdl"
></A
>1.1.1. GNU Free Documentation License</H2
><P
>Version 1.1, March 2000</P
><A
NAME="AEN40"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>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.</P
></BLOCKQUOTE
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-0"
></A
>0. PREAMBLE</H3
><P
>The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone the
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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-1"
></A
>1. APPLICABILITY AND DEFINITIONS</H3
><P
>This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed under
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".</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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".</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-2"
></A
>2. VERBATIM COPYING</H3
><P
>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.</P
><P
>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-3"
></A
>3. COPYING IN QUANTITY</H3
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-4"
></A
>4. MODIFICATIONS</H3
><P
>You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you release
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:</P
><P
></P
><OL
TYPE="A"
><LI
><P
>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.</P
></LI
><LI
><P
>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).</P
></LI
><LI
><P
>State on the Title page the name of the publisher of the
Modified Version, as the publisher.</P
></LI
><LI
><P
>Preserve all the copyright notices of the Document.</P
></LI
><LI
><P
>Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's license
notice.</P
></LI
><LI
><P
>Include an unaltered copy of this License.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>Delete any section entitled "Endorsements". Such a section may
not be included in the Modified Version.</P
></LI
><LI
><P
>Do not retitle any existing section as "Endorsements" or to
conflict in title with any Invariant Section.</P
></LI
></OL
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-5"
></A
>5. COMBINING DOCUMENTS</H3
><P
>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.</P
><P
>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.</P
><P
>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."</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-6"
></A
>6. COLLECTIONS OF DOCUMENTS</H3
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-7"
></A
>7. AGGREGATION WITH INDEPENDENT WORKS</H3
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-8"
></A
>8. TRANSLATION</H3
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-9"
></A
>9. TERMINATION</H3
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-10"
></A
>10. FUTURE REVISIONS OF THIS LICENSE</H3
><P
>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
<A
HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
>&#13; http://www.gnu.org/copyleft/</A
>
.</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-howto"
></A
>How to use this License for your documents</H3
><P
>To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN130"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>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".</P
></BLOCKQUOTE
><P
>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.</P
><P
>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.</P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/cust-templates.html
View file @ 393f13a4
......@@ -99,7 +99,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1610"
NAME="AEN1409"
></A
>5.7.1. What to Edit</H2
><P
......@@ -214,7 +214,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1629"
NAME="AEN1428"
></A
>5.7.2. How To Edit Templates</H2
><P
......@@ -296,7 +296,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1639"
NAME="AEN1438"
></A
>5.7.3. Template Formats</H2
><P
......@@ -358,7 +358,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1652"
NAME="AEN1451"
></A
>5.7.4. Particular Templates</H2
><P
......
docs/html/dbdoc.html
View file @ 393f13a4
......@@ -135,7 +135,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2258"
NAME="AEN2057"
></A
>B.2.1. Bugzilla Database Basics</H2
><P
......@@ -251,7 +251,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN2285"
NAME="AEN2084"
></A
>B.2.1.1. Bugzilla Database Tables</H3
><P
......
docs/html/extraconfig.html
View file @ 393f13a4
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Step-by-step Install"
HREF="stepbystep.html"><LINK
REL="NEXT"
TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD
TITLE="OS Specific Installation Notes"
HREF="os-specific.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="win32.html"
HREF="os-specific.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -81,7 +81,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN858"
NAME="AEN751"
></A
>4.2.1. Dependency Charts</H2
><P
......@@ -137,7 +137,7 @@ TARGET="_top"
Alternatively, you could set up a webdot server, or use the AT&#38;T
public webdot server (the
default for the webdotbase param). Note that AT&#38;T's server won't work
if Bugzilla is only accessible using HTTPS.
if Bugzilla is only accessible using HARTS.
</P
></DIV
><DIV
......@@ -145,7 +145,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN873"
NAME="AEN766"
></A
>4.2.2. Bug Graphs</H2
><P
......@@ -204,7 +204,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN886"
NAME="AEN779"
></A
>4.2.3. The Whining Cron</H2
><P
......@@ -838,7 +838,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="win32.html"
HREF="os-specific.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -862,7 +862,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Win32 Installation Notes</TD
>OS Specific Installation Notes</TD
></TR
></TABLE
></DIV
......
docs/html/faq.html
View file @ 393f13a4
......@@ -87,64 +87,64 @@ HREF="faq.html#faq-general"
><DL
><DT
>A.1.1. <A
HREF="faq.html#AEN1813"
HREF="faq.html#AEN1612"
>&#13; Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
HREF="faq.html#AEN1819"
HREF="faq.html#AEN1618"
>&#13; What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
HREF="faq.html#AEN1825"
HREF="faq.html#AEN1624"
>&#13; How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
HREF="faq.html#AEN1834"
HREF="faq.html#AEN1633"
>&#13; What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
HREF="faq.html#AEN1858"
HREF="faq.html#AEN1657"
>&#13; Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
HREF="faq.html#AEN1864"
HREF="faq.html#AEN1663"
>&#13; How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
HREF="faq.html#AEN1870"
HREF="faq.html#AEN1669"
>&#13; Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
HREF="faq.html#AEN1877"
HREF="faq.html#AEN1676"
>&#13; Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
HREF="faq.html#AEN1886"
HREF="faq.html#AEN1685"
>&#13; Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
><DT
>A.1.10. <A
HREF="faq.html#AEN1892"
HREF="faq.html#AEN1691"
>&#13; Is there an easy way to change the Bugzilla cookie name?
</A
></DT
......@@ -159,41 +159,41 @@ HREF="faq.html#faq-phb"
><DL
><DT
>A.2.1. <A
HREF="faq.html#AEN1902"
HREF="faq.html#AEN1701"
>&#13; Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
HREF="faq.html#AEN1907"
HREF="faq.html#AEN1706"
>&#13; Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
HREF="faq.html#AEN1912"
HREF="faq.html#AEN1711"
>&#13; Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
HREF="faq.html#AEN1917"
HREF="faq.html#AEN1716"
>&#13; 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
></DT
><DT
>A.2.5. <A
HREF="faq.html#AEN1922"
HREF="faq.html#AEN1721"
>&#13; Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
HREF="faq.html#AEN1927"
HREF="faq.html#AEN1726"
>&#13; Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values?
......@@ -201,35 +201,35 @@ HREF="faq.html#AEN1927"
></DT
><DT
>A.2.7. <A
HREF="faq.html#AEN1934"
HREF="faq.html#AEN1733"
>&#13; Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
HREF="faq.html#AEN1941"
HREF="faq.html#AEN1740"
>&#13; Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
HREF="faq.html#AEN1946"
HREF="faq.html#AEN1745"
>&#13; Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
HREF="faq.html#AEN1951"
HREF="faq.html#AEN1750"
>&#13; Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
HREF="faq.html#AEN1958"
HREF="faq.html#AEN1757"
>&#13; Does Bugzilla allow data to be imported and exported? If I had outsiders
write up a bug report using a MS Word bug template, could that template be
imported into "matching" fields? If I wanted to take the results of a query
......@@ -238,28 +238,28 @@ HREF="faq.html#AEN1958"
></DT
><DT
>A.2.12. <A
HREF="faq.html#AEN1970"
HREF="faq.html#AEN1769"
>&#13; Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
HREF="faq.html#AEN1977"
HREF="faq.html#AEN1776"
>&#13; Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
HREF="faq.html#AEN1982"
HREF="faq.html#AEN1781"
>&#13; Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
HREF="faq.html#AEN1987"
HREF="faq.html#AEN1786"
>&#13; Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use
or how are they notified?
......@@ -267,19 +267,19 @@ HREF="faq.html#AEN1987"
></DT
><DT
>A.2.16. <A
HREF="faq.html#AEN1992"
HREF="faq.html#AEN1791"
>&#13; Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
HREF="faq.html#AEN1998"
HREF="faq.html#AEN1797"
>&#13; Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
HREF="faq.html#AEN2003"
HREF="faq.html#AEN1802"
>&#13; What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to
have? I need to find out if we were to go with Bugzilla, what types of
......@@ -289,7 +289,7 @@ HREF="faq.html#AEN2003"
></DT
><DT
>A.2.19. <A
HREF="faq.html#AEN2009"
HREF="faq.html#AEN1808"
>&#13; What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to
install and a couple of hours per week to maintain and customize or is this
......@@ -299,7 +299,7 @@ HREF="faq.html#AEN2009"
></DT
><DT
>A.2.20. <A
HREF="faq.html#AEN2014"
HREF="faq.html#AEN1813"
>&#13; 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
......@@ -315,20 +315,20 @@ HREF="faq.html#faq-security"
><DL
><DT
>A.3.1. <A
HREF="faq.html#AEN2021"
HREF="faq.html#AEN1820"
>&#13; 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
></DT
><DT
>A.3.2. <A
HREF="faq.html#AEN2027"
HREF="faq.html#AEN1826"
>&#13; Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
HREF="faq.html#AEN2032"
HREF="faq.html#AEN1831"
>&#13; I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly.
......@@ -345,48 +345,48 @@ HREF="faq.html#faq-email"
><DL
><DT
>A.4.1. <A
HREF="faq.html#AEN2039"
HREF="faq.html#AEN1838"
>&#13; 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
></DT
><DT
>A.4.2. <A
HREF="faq.html#AEN2045"
HREF="faq.html#AEN1844"
>&#13; I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.4.3. <A
HREF="faq.html#AEN2050"
HREF="faq.html#AEN1849"
>&#13; I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
HREF="faq.html#AEN2056"
HREF="faq.html#AEN1855"
>&#13; I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
HREF="faq.html#AEN2063"
HREF="faq.html#AEN1862"
>&#13; How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
HREF="faq.html#AEN2068"
HREF="faq.html#AEN1867"
>&#13; Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
HREF="faq.html#AEN2075"
HREF="faq.html#AEN1874"
>&#13; How come email from Bugzilla changes never reaches me?
</A
></DT
......@@ -401,33 +401,33 @@ HREF="faq.html#faq-db"
><DL
><DT
>A.5.1. <A
HREF="faq.html#AEN2083"
HREF="faq.html#AEN1882"
>&#13; I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
HREF="faq.html#AEN2088"
HREF="faq.html#AEN1887"
>&#13; I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
HREF="faq.html#AEN2096"
HREF="faq.html#AEN1895"
>&#13; I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
HREF="faq.html#AEN2104"
HREF="faq.html#AEN1903"
>&#13; I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
>A.5.5. <A
HREF="faq.html#AEN2112"
HREF="faq.html#AEN1911"
>&#13; How do I synchronize bug information among multiple different Bugzilla
databases?
</A
......@@ -443,26 +443,26 @@ HREF="faq.html#faq-nt"
><DL
><DT
>A.6.1. <A
HREF="faq.html#AEN2121"
HREF="faq.html#AEN1920"
>&#13; What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
HREF="faq.html#AEN2126"
HREF="faq.html#AEN1925"
>&#13; Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
HREF="faq.html#AEN2131"
HREF="faq.html#AEN1930"
>&#13; CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
HREF="faq.html#AEN2139"
HREF="faq.html#AEN1938"
>&#13; I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
......@@ -478,33 +478,33 @@ HREF="faq.html#faq-use"
><DL
><DT
>A.7.1. <A
HREF="faq.html#AEN2160"
HREF="faq.html#AEN1959"
>&#13; How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
HREF="faq.html#AEN2165"
HREF="faq.html#AEN1964"
>&#13; The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
HREF="faq.html#AEN2170"
HREF="faq.html#AEN1969"
>&#13; 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
></DT
><DT
>A.7.4. <A
HREF="faq.html#AEN2180"
HREF="faq.html#AEN1979"
>&#13; I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
HREF="faq.html#AEN2185"
HREF="faq.html#AEN1984"
>&#13; How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
......@@ -519,26 +519,26 @@ HREF="faq.html#faq-hacking"
><DL
><DT
>A.8.1. <A
HREF="faq.html#AEN2192"
HREF="faq.html#AEN1991"
>&#13; What kind of style should I use for templatization?
</A
></DT
><DT
>A.8.2. <A
HREF="faq.html#AEN2200"
HREF="faq.html#AEN1999"
>&#13; What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.3. <A
HREF="faq.html#AEN2209"
HREF="faq.html#AEN2008"
>&#13; How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.8.4. <A
HREF="faq.html#AEN2215"
HREF="faq.html#AEN2014"
>&#13; What's the best way to submit patches? What guidelines should I follow?
</A
></DT
......@@ -558,7 +558,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1813"
NAME="AEN1612"
></A
><B
>A.1.1. </B
......@@ -586,7 +586,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1819"
NAME="AEN1618"
></A
><B
>A.1.2. </B
......@@ -615,7 +615,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1825"
NAME="AEN1624"
></A
><B
>A.1.3. </B
......@@ -661,7 +661,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1834"
NAME="AEN1633"
></A
><B
>A.1.4. </B
......@@ -767,7 +767,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1858"
NAME="AEN1657"
></A
><B
>A.1.5. </B
......@@ -797,7 +797,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1864"
NAME="AEN1663"
></A
><B
>A.1.6. </B
......@@ -835,7 +835,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1870"
NAME="AEN1669"
></A
><B
>A.1.7. </B
......@@ -875,7 +875,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1877"
NAME="AEN1676"
></A
><B
>A.1.8. </B
......@@ -920,7 +920,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1886"
NAME="AEN1685"
></A
><B
>A.1.9. </B
......@@ -953,7 +953,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1892"
NAME="AEN1691"
></A
><B
>A.1.10. </B
......@@ -1015,7 +1015,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1902"
NAME="AEN1701"
></A
><B
>A.2.1. </B
......@@ -1041,7 +1041,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1907"
NAME="AEN1706"
></A
><B
>A.2.2. </B
......@@ -1067,7 +1067,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1912"
NAME="AEN1711"
></A
><B
>A.2.3. </B
......@@ -1092,7 +1092,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1917"
NAME="AEN1716"
></A
><B
>A.2.4. </B
......@@ -1117,7 +1117,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1922"
NAME="AEN1721"
></A
><B
>A.2.5. </B
......@@ -1146,7 +1146,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1927"
NAME="AEN1726"
></A
><B
>A.2.6. </B
......@@ -1183,7 +1183,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1934"
NAME="AEN1733"
></A
><B
>A.2.7. </B
......@@ -1221,7 +1221,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1941"
NAME="AEN1740"
></A
><B
>A.2.8. </B
......@@ -1248,7 +1248,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1946"
NAME="AEN1745"
></A
><B
>A.2.9. </B
......@@ -1273,7 +1273,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1951"
NAME="AEN1750"
></A
><B
>A.2.10. </B
......@@ -1332,7 +1332,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1958"
NAME="AEN1757"
></A
><B
>A.2.11. </B
......@@ -1394,7 +1394,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1970"
NAME="AEN1769"
></A
><B
>A.2.12. </B
......@@ -1432,7 +1432,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1977"
NAME="AEN1776"
></A
><B
>A.2.13. </B
......@@ -1457,7 +1457,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1982"
NAME="AEN1781"
></A
><B
>A.2.14. </B
......@@ -1483,7 +1483,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1987"
NAME="AEN1786"
></A
><B
>A.2.15. </B
......@@ -1510,7 +1510,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1992"
NAME="AEN1791"
></A
><B
>A.2.16. </B
......@@ -1540,7 +1540,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN1998"
NAME="AEN1797"
></A
><B
>A.2.17. </B
......@@ -1566,7 +1566,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2003"
NAME="AEN1802"
></A
><B
>A.2.18. </B
......@@ -1601,7 +1601,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2009"
NAME="AEN1808"
></A
><B
>A.2.19. </B
......@@ -1634,7 +1634,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2014"
NAME="AEN1813"
></A
><B
>A.2.20. </B
......@@ -1668,7 +1668,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2021"
NAME="AEN1820"
></A
><B
>A.3.1. </B
......@@ -1697,7 +1697,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2027"
NAME="AEN1826"
></A
><B
>A.3.2. </B
......@@ -1725,7 +1725,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2032"
NAME="AEN1831"
></A
><B
>A.3.3. </B
......@@ -1761,7 +1761,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2039"
NAME="AEN1838"
></A
><B
>A.4.1. </B
......@@ -1791,7 +1791,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2045"
NAME="AEN1844"
></A
><B
>A.4.2. </B
......@@ -1817,7 +1817,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2050"
NAME="AEN1849"
></A
><B
>A.4.3. </B
......@@ -1849,7 +1849,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2056"
NAME="AEN1855"
></A
><B
>A.4.4. </B
......@@ -1867,7 +1867,7 @@ CLASS="answer"
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
NAME="AEN2060"
NAME="AEN1859"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1888,7 +1888,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2063"
NAME="AEN1862"
></A
><B
>A.4.5. </B
......@@ -1913,7 +1913,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2068"
NAME="AEN1867"
></A
><B
>A.4.6. </B
......@@ -1948,7 +1948,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2075"
NAME="AEN1874"
></A
><B
>A.4.7. </B
......@@ -1988,7 +1988,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2083"
NAME="AEN1882"
></A
><B
>A.5.1. </B
......@@ -2016,7 +2016,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2088"
NAME="AEN1887"
></A
><B
>A.5.2. </B
......@@ -2063,7 +2063,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2096"
NAME="AEN1895"
></A
><B
>A.5.3. </B
......@@ -2104,7 +2104,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2104"
NAME="AEN1903"
></A
><B
>A.5.4. </B
......@@ -2165,7 +2165,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2112"
NAME="AEN1911"
></A
><B
>A.5.5. </B
......@@ -2211,7 +2211,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2121"
NAME="AEN1920"
></A
><B
>A.6.1. </B
......@@ -2236,7 +2236,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2126"
NAME="AEN1925"
></A
><B
>A.6.2. </B
......@@ -2262,7 +2262,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2131"
NAME="AEN1930"
></A
><B
>A.6.3. </B
......@@ -2285,7 +2285,7 @@ CLASS="answer"
><P
>&#13; Microsoft has some advice on this matter, as well:
<A
NAME="AEN2136"
NAME="AEN1935"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -2310,7 +2310,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2139"
NAME="AEN1938"
></A
><B
>A.6.4. </B
......@@ -2387,7 +2387,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2160"
NAME="AEN1959"
></A
><B
>A.7.1. </B
......@@ -2412,7 +2412,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2165"
NAME="AEN1964"
></A
><B
>A.7.2. </B
......@@ -2438,7 +2438,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2170"
NAME="AEN1969"
></A
><B
>A.7.3. </B
......@@ -2493,7 +2493,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2180"
NAME="AEN1979"
></A
><B
>A.7.4. </B
......@@ -2520,7 +2520,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2185"
NAME="AEN1984"
></A
><B
>A.7.5. </B
......@@ -2554,7 +2554,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2192"
NAME="AEN1991"
></A
><B
>A.8.1. </B
......@@ -2613,7 +2613,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2200"
NAME="AEN1999"
></A
><B
>A.8.2. </B
......@@ -2659,7 +2659,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2209"
NAME="AEN2008"
></A
><B
>A.8.3. </B
......@@ -2691,7 +2691,7 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
NAME="AEN2215"
NAME="AEN2014"
></A
><B
>A.8.4. </B
......
docs/html/gfdl-0.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="NEXT"
TITLE="APPLICABILITY AND DEFINITIONS"
HREF="gfdl-1.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-1.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-0"
></A
>0. PREAMBLE</H1
><P
>The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone the
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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-1.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>GNU Free Documentation License</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>APPLICABILITY AND DEFINITIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-1.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="PREAMBLE"
HREF="gfdl-0.html"><LINK
REL="NEXT"
TITLE="VERBATIM COPYING"
HREF="gfdl-2.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-0.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-2.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-1"
></A
>1. APPLICABILITY AND DEFINITIONS</H1
><P
>This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed under
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".</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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".</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-0.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-2.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>PREAMBLE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>VERBATIM COPYING</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/osx.html → docs/html/gfdl-10.html
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>Mac OS X Installation Notes</TITLE
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
......@@ -10,14 +10,14 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="Win32 Installation Notes"
HREF="win32.html"><LINK
TITLE="TERMINATION"
HREF="gfdl-9.html"><LINK
REL="NEXT"
TITLE="Troubleshooting"
HREF="troubleshooting.html"></HEAD
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="win32.html"
HREF="gfdl-9.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -53,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="troubleshooting.html"
HREF="gfdl-howto.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -73,125 +73,30 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="osx"
NAME="gfdl-10"
></A
>4.4. Mac OS X Installation Notes</H1
>10. FUTURE REVISIONS OF THIS LICENSE</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
The GD library, which Bugzilla needs to do bug graphs, is one of
these.</P
><P
>The easiest way to get a lot of these is with a program called
Fink, which is similar in nature to the CPAN installer, but installs
common GNU utilities. Fink is available from
&#60;http://sourceforge.net/projects/fink/&#62;.</P
><P
>Follow the instructions for setting up Fink. Once it's installed,
you'll want to run the following as root:
<B
CLASS="command"
>fink install gd</B
>
</P
><P
>It will prompt you for a number of dependencies, type 'y' and hit
enter to install all of the dependencies. Then watch it work.</P
><P
>To prevent creating conflicts with the software that Apple installs
by default, Fink creates its own directory tree at /sw where it installs
most of the software that it installs. This means your libraries and
headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
and /usr/local/include. Because of these changed locations for the
libraries, the Perl GD module will not install directly via CPAN, because it
looks for the specific paths instead of getting them from your
environment. But there's a way around that :-)</P
><P
>Instead of typing
<SPAN
CLASS="QUOTE"
>"install GD"</SPAN
>
at the
<TT
CLASS="prompt"
>cpan&#62;</TT
>
prompt, type
<B
CLASS="command"
>look GD</B
>.
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 <A
HREF="../sgml/gd-makefile.patch"
>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
<A
HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
>this patch</A
>
to the Makefile.PL file (save the
patch into a file and use the command
<B
CLASS="command"
>patch &#60; patchfile</B
>.)
</P
><P
>Then, run these commands to finish the installation of the GD
module:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <B
CLASS="command"
>perl Makefile.PL</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make test</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make install</B
>
</TD
></TR
><TR
><TD
>And don't forget to run
<B
CLASS="command"
>exit</B
>&#13; http://www.gnu.org/copyleft/</A
>
to get back to CPAN.</TD
></TR
></TBODY
></TABLE
.</P
><P
></P
>
</P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......@@ -209,7 +114,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="win32.html"
HREF="gfdl-9.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -227,7 +132,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="troubleshooting.html"
HREF="gfdl-howto.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -237,13 +142,13 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Win32 Installation Notes</TD
>TERMINATION</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
......@@ -251,7 +156,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Troubleshooting</TD
>How to use this License for your documents</TD
></TR
></TABLE
></DIV
......
docs/html/gfdl-2.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="APPLICABILITY AND DEFINITIONS"
HREF="gfdl-1.html"><LINK
REL="NEXT"
TITLE="COPYING IN QUANTITY"
HREF="gfdl-3.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-2"
></A
>2. VERBATIM COPYING</H1
><P
>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
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.</P
><P
>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>APPLICABILITY AND DEFINITIONS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COPYING IN QUANTITY</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-3.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="VERBATIM COPYING"
HREF="gfdl-2.html"><LINK
REL="NEXT"
TITLE="MODIFICATIONS"
HREF="gfdl-4.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-2.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-4.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-3"
></A
>3. COPYING IN QUANTITY</H1
><P
>If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you must
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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-2.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-4.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>VERBATIM COPYING</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>MODIFICATIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-4.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COPYING IN QUANTITY"
HREF="gfdl-3.html"><LINK
REL="NEXT"
TITLE="COMBINING DOCUMENTS"
HREF="gfdl-5.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-3.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-5.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-4"
></A
>4. MODIFICATIONS</H1
><P
>You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you release
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:</P
><P
></P
><OL
TYPE="A"
><LI
><P
>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.</P
></LI
><LI
><P
>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).</P
></LI
><LI
><P
>State on the Title page the name of the publisher of the
Modified Version, as the publisher.</P
></LI
><LI
><P
>Preserve all the copyright notices of the Document.</P
></LI
><LI
><P
>Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's license
notice.</P
></LI
><LI
><P
>Include an unaltered copy of this License.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>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.</P
></LI
><LI
><P
>Delete any section entitled "Endorsements". Such a section may
not be included in the Modified Version.</P
></LI
><LI
><P
>Do not retitle any existing section as "Endorsements" or to
conflict in title with any Invariant Section.</P
></LI
></OL
><P
>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.</P
><P
>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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-3.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-5.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COPYING IN QUANTITY</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COMBINING DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-5.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="MODIFICATIONS"
HREF="gfdl-4.html"><LINK
REL="NEXT"
TITLE="COLLECTIONS OF DOCUMENTS"
HREF="gfdl-6.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-4.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-6.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-5"
></A
>5. COMBINING DOCUMENTS</H1
><P
>You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for modified
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.</P
><P
>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.</P
><P
>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."</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-4.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-6.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>MODIFICATIONS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COLLECTIONS OF DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-6.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COMBINING DOCUMENTS"
HREF="gfdl-5.html"><LINK
REL="NEXT"
TITLE="AGGREGATION WITH INDEPENDENT WORKS"
HREF="gfdl-7.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-5.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-7.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-6"
></A
>6. COLLECTIONS OF DOCUMENTS</H1
><P
>You may make a collection consisting of the Document and other
documents released under this License, and replace the individual copies
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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-5.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-7.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COMBINING DOCUMENTS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>AGGREGATION WITH INDEPENDENT WORKS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-7.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COLLECTIONS OF DOCUMENTS"
HREF="gfdl-6.html"><LINK
REL="NEXT"
TITLE="TRANSLATION"
HREF="gfdl-8.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-6.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-8.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-7"
></A
>7. AGGREGATION WITH INDEPENDENT WORKS</H1
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-6.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-8.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COLLECTIONS OF DOCUMENTS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TRANSLATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-8.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="AGGREGATION WITH INDEPENDENT WORKS"
HREF="gfdl-7.html"><LINK
REL="NEXT"
TITLE="TERMINATION"
HREF="gfdl-9.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-7.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-9.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-8"
></A
>8. TRANSLATION</H1
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-7.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-9.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>AGGREGATION WITH INDEPENDENT WORKS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TERMINATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-9.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="TRANSLATION"
HREF="gfdl-8.html"><LINK
REL="NEXT"
TITLE="FUTURE REVISIONS OF THIS LICENSE"
HREF="gfdl-10.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-8.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-10.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-9"
></A
>9. TERMINATION</H1
><P
>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-8.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-10.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>TRANSLATION</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>FUTURE REVISIONS OF THIS LICENSE</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-howto.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="FUTURE REVISIONS OF THIS LICENSE"
HREF="gfdl-10.html"><LINK
REL="NEXT"
TITLE="Glossary"
HREF="glossary.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-10.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="glossary.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="gfdl-howto"
></A
>How to use this License for your documents</H1
><P
>To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN2262"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>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".</P
></BLOCKQUOTE
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-10.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="glossary.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>FUTURE REVISIONS OF THIS LICENSE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Glossary</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>GNU Free Documentation License</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="SourceForge"
HREF="variant-sourceforge.html"><LINK
REL="NEXT"
TITLE="PREAMBLE"
HREF="gfdl-0.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-sourceforge.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-0.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="gfdl"
></A
>Appendix E. GNU Free Documentation License</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>0. <A
HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
></DIV
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2172"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>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.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-sourceforge.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-0.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SourceForge</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>PREAMBLE</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/glossary.html
View file @ 393f13a4
......@@ -10,8 +10,8 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="SourceForge"
HREF="variant-sourceforge.html"></HEAD
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="glossary"
BGCOLOR="#FFFFFF"
......@@ -39,7 +39,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-sourceforge.html"
HREF="gfdl-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -70,7 +70,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2371"
NAME="AEN2267"
></A
>0-9, high ascii</H1
><DL
......@@ -109,18 +109,16 @@ NAME="gloss-a"
>A</H1
><DL
><DT
><A
NAME="gloss-apache"
></A
><B
>Apache</B
></DT
><DD
><P
>In this context, Apache is the web server most commonly used
for serving up
<I
CLASS="glossterm"
>Bugzilla</I
>
for serving up Bugzilla
pages. Contrary to popular belief, the apache web server has nothing
to do with the ancient and noble Native American tribe, but instead
derived its name from the fact that it was
......@@ -128,14 +126,123 @@ CLASS="glossterm"
CLASS="QUOTE"
>"a patchy"</SPAN
>
version of the original
<SPAN
CLASS="acronym"
>NCSA</SPAN
>
world-wide-web server.</P
><P
></P
><DIV
CLASS="variablelist"
><P
><B
>Useful Directives when configuring Bugzilla</B
></P
><DL
><DT
><TT
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
TARGET="_top"
>AddHandler</A
></TT
></DT
><DD
><P
>Tell Apache that it's OK to run CGI scripts.</P
></DD
><DT
><TT
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
TARGET="_top"
>AllowOverride</A
></TT
>, <TT
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
TARGET="_top"
>Options</A
></TT
></DT
><DD
><P
>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 <TT
CLASS="filename"
>.htaccess</TT
>
overrides.
</P
></DD
><DT
><TT
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
TARGET="_top"
>DirectoryIndex</A
></TT
></DT
><DD
><P
>Used to tell Apache what files are indexes. If you can
not add <TT
CLASS="filename"
>index.cgi</TT
> to the list of valid files,
you'll need to set <TT
CLASS="computeroutput"
>$index_html</TT
> to
1 in <TT
CLASS="filename"
>localconfig</TT
> so
<B
CLASS="command"
>./checksetup.pl</B
> will create an
<TT
CLASS="filename"
>index.html</TT
> that redirects to
<TT
CLASS="filename"
>index.cgi</TT
>.
</P
></DD
><DT
><TT
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>ScriptInterpreterSource</A
></TT
></DT
><DD
><P
>Used when running Apache on windows so the shebang line
doesn't have to be changed in every Bugzilla script.
</P
></DD
></DL
></DIV
><P
>For more information about how to configure Apache for Bugzilla,
see <A
HREF="http.html#http-apache"
>Section 4.4.1</A
>.
</P
></DD
></DL
></DIV
......@@ -206,6 +313,26 @@ NAME="gloss-c"
><DL
><DT
><A
NAME="gloss-cgi"
></A
><B
>Common Gateway Interface</B
></DT
> (CGI)<DD
><P
><SPAN
CLASS="acronym"
>CGI</SPAN
> 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 <SPAN
CLASS="acronym"
>CGI</SPAN
> application.
</P
></DD
><DT
><A
NAME="gloss-component"
></A
><B
......@@ -289,9 +416,12 @@ CLASS="glossdiv"
><A
NAME="gloss-g"
></A
></H1
>G</H1
><DL
><DT
><A
NAME="gloss-groups"
></A
><B
>Groups</B
></DT
......@@ -324,6 +454,29 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-j"
></A
>J</H1
><DL
><DT
><A
NAME="gloss-javascript"
></A
><B
>JavaScript</B
></DT
><DD
><P
>JavaScript is cool, we should talk about it.
</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-m"
></A
>M</H1
......@@ -542,6 +695,21 @@ CLASS="QUOTE"
giving you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.</P
></DD
><DT
><A
NAME="gloss-tcl"
></A
><B
>Tool Command Language</B
></DT
> (TCL)<DD
><P
>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.
</P
></DD
></DL
></DIV
><DIV
......@@ -585,7 +753,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-sourceforge.html"
HREF="gfdl-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -609,7 +777,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SourceForge</TD
>How to use this License for your documents</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/hintsandtips.html
View file @ 393f13a4
......@@ -84,7 +84,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN431"
NAME="AEN336"
></A
>3.2.1. Autolinkification</H2
><P
......@@ -232,7 +232,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN460"
NAME="AEN365"
></A
>3.2.5. Filing Bugs</H2
><P
......
docs/html/http.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>HTTP Server Configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="OS Specific Installation Notes"
HREF="os-specific.html"><LINK
REL="NEXT"
TITLE="Troubleshooting"
HREF="troubleshooting.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="os-specific.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="http"
></A
>4.4. HTTP Server Configuration</H1
><P
>The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
that can be configured to run <A
HREF="glossary.html#gloss-cgi"
><I
CLASS="glossterm"
>CGI</I
></A
> scripts
should be able to handle Bugzilla. No matter what web server you choose, but
especially if you choose something other than Apache, you should be sure to read
<A
HREF="security.html"
>Section 5.6</A
>.
</P
><P
>The plan for this section is to eventually document the specifics of how to lock
down permissions on individual web servers.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="http-apache"
></A
>4.4.1. Apache <SPAN
CLASS="productname"
>httpd</SPAN
></H2
><P
>As mentioned above, the Bugzilla Team recommends Apache for use
with Bugzilla. You will have to make sure that Apache is properly
configured to run the Bugzilla CGI scripts. You also need to make sure
that the <TT
CLASS="filename"
>.htaccess</TT
> files created by
<B
CLASS="command"
>./checksetup.pl</B
> (shown in <A
HREF="http.html#http-apache-htaccess"
>Example 4-1</A
>
for the curious) are allowed to override Apache's normal access
permissions or else important password information may be exposed to the
Internet.
</P
><P
>Many Apache installations are not configured to run scripts
anywhere but in the <TT
CLASS="filename"
>cgi-bin</TT
>
directory; however, we recommend that Bugzilla not be installed in the
<TT
CLASS="filename"
>cgi-bin</TT
>, otherwise the static
files such as images and <A
HREF="glossary.html#gloss-javascript"
><I
CLASS="glossterm"
>JavaScript</I
></A
>
will not work correctly. To allow scripts to run in the normal
web space, the following changes should be made to your
<TT
CLASS="filename"
>httpd.conf</TT
> file.
</P
><P
>To allow files with a .cgi extension to be run, make sure the
following line exists and is uncommented:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;AddHandler cgi-script .cgi
</PRE
></FONT
></TD
></TR
></TABLE
><P
>To allow <TT
CLASS="filename"
>.htaccess</TT
> files to override
permissions and .cgi files to run in the Bugzilla directory, make sure
the following two lines are in a <TT
CLASS="computeroutput"
>Directory</TT
>
directive that applies to the Bugzilla directory on your system
(either the Bugzilla directory or one of its parents).
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Options +ExecCGI
AllowOverride Limit
</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>For more information on Apache and its directives, see the
glossary entry on <A
HREF="glossary.html#gloss-apache"
><I
CLASS="glossterm"
>Apache</I
></A
>.
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="http-apache-htaccess"
></A
><P
><B
>Example 4-1. <TT
CLASS="filename"
>.htaccess</TT
> files for Apache</B
></P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# don't allow people to retrieve non-cgi executable files or our private data
&#60;FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$&#62;
deny from all
&#60;/FilesMatch&#62;
&#60;FilesMatch ^(localconfig.js|localconfig.rdf)$&#62;
allow from all
&#60;/FilesMatch&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/data/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory; the only exception is duplicates.rdf, which is used by
# duplicates.xul and must be loadable over the web
deny from all
&#60;Files duplicates.rdf&#62;
allow from all
&#60;/Files&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/data/webdot</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# Restrict access to .dot files to the public webdot server at research.att.com
# if research.att.com ever changed their IP, or if you use a different
# webdot server, you'll need to edit this
&#60;FilesMatch ^[0-9]+\.dot$&#62;
Allow from 192.20.225.10
Deny from all
&#60;/FilesMatch&#62;
# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
# .map files
&#60;FilesMatch ^[0-9]+\.(png|gif|jpg|map)$&#62;
Allow from all
&#60;/FilesMatch&#62;
# And no directory listings, either.
Deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/Bugzilla/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/template/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="http-iis"
></A
>4.4.2. Microsoft <SPAN
CLASS="productname"
>Internet Information Services</SPAN
></H2
><P
>If you need, or for some reason even want, to use Microsoft's
<SPAN
CLASS="productname"
>Internet Information Services</SPAN
> or
<SPAN
CLASS="productname"
>Personal Web Server</SPAN
> you should be able
to. You will need to configure them to know how to run CGI scripts,
however. This is described in Microsoft Knowledge Base article
<A
HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
TARGET="_top"
>Q245225 </A
>
for <SPAN
CLASS="productname"
>Internet Information Services</SPAN
> and
<A
HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp"
TARGET="_top"
>Q231998</A
>
for <SPAN
CLASS="productname"
>Personal Web Server</SPAN
>.
</P
><P
>Also, and this can't be stressed enough, make sure that files such as
<TT
CLASS="filename"
>localconfig</TT
> and your <TT
CLASS="filename"
>data</TT
>
directory are secured as described in <A
HREF="security.html"
>Section 5.6</A
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="http-aol"
></A
>4.4.3. AOL Server</H2
><P
>Ben FrantzDale reported success using AOL Server with Bugzilla. He
reported his experience and what appears below is based on that.
</P
><P
>AOL Server will have to be configured to run
<A
HREF="glossary.html#gloss-cgi"
><I
CLASS="glossterm"
>CGI</I
></A
> scripts, please consult
the documentation that came with your server for more information on
how to do this.
</P
><P
>Because AOL Server doesn't support <TT
CLASS="filename"
>.htaccess</TT
>
files, you'll have to create a <A
HREF="glossary.html#gloss-tcl"
><I
CLASS="glossterm"
>TCL</I
></A
>
script. You should create an <TT
CLASS="filename"
>aolserver/modules/tcl/filter.tcl</TT
>
file (the filename shouldn't matter) with the following contents (change
<TT
CLASS="computeroutput"
>/bugzilla/</TT
> to the web-based path to
your Bugzilla installation):
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;ns_register_filter preauth GET /bugzilla/localconfig filter_deny
ns_register_filter preauth GET /bugzilla/*.pl filter_deny
ns_register_filter preauth GET /bugzilla/localconfig filter_deny
ns_register_filter preauth GET /bugzilla/processmail filter_deny
ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
proc filter_deny { why } {
ns_log Notice "filter_deny"
return "filter_return"
}
</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This doesn't appear to account for everything mentioned in
<A
HREF="security.html"
>Section 5.6</A
>. In particular, it doesn't block access
to the <TT
CLASS="filename"
>data</TT
> or
<TT
CLASS="filename"
>template</TT
> directories. It also
doesn't account for the editor backup files that were the topic of
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
TARGET="_top"
>bug
186383</A
>, <A
HREF="http://online.securityfocus.com/bid/6501"
TARGET="_top"
>Bugtraq ID 6501</A
>,
and a partial cause for the 2.16.2 release.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="os-specific.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>OS Specific Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Troubleshooting</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/index.html
View file @ 393f13a4
......@@ -60,13 +60,16 @@ NAME="AEN9"
></A
>The Bugzilla Team</H3
><P
CLASS="edition"
>2.17.3 Development Release&nbsp;Edition </P
><P
CLASS="pubdate"
>2003-01-02<BR></P
><DIV
><DIV
CLASS="abstract"
><A
NAME="AEN14"
NAME="AEN15"
></A
><P
></P
......@@ -81,12 +84,11 @@ NAME="AEN14"
>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a bug filed in
<A
to a bug filed in the <A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
>mozilla.org's Bugzilla</A
>.
>Bugzilla Documentation</A
> compontent.
</P
><P
>This is a development version of this guide. Information in it
......@@ -201,13 +203,13 @@ HREF="extraconfig.html"
></DT
><DT
>4.3. <A
HREF="win32.html"
>Win32 Installation Notes</A
HREF="os-specific.html"
>OS Specific Installation Notes</A
></DT
><DT
>4.4. <A
HREF="osx.html"
>Mac OS X Installation Notes</A
HREF="http.html"
>HTTP Server Configuration</A
></DT
><DT
>4.5. <A
......@@ -364,6 +366,75 @@ HREF="variant-sourceforge.html"
></DL
></DD
><DT
>E. <A
HREF="gfdl.html"
>GNU Free Documentation License</A
></DT
><DD
><DL
><DT
>0. <A
HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
></DD
><DT
><A
HREF="glossary.html"
>Glossary</A
......@@ -380,21 +451,11 @@ CLASS="LOT"
></DT
><DT
>4-1. <A
HREF="win32.html#AEN1032"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
HREF="win32.html#AEN1045"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
HREF="win32.html#AEN1211"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
HREF="http.html#http-apache-htaccess"
><TT
CLASS="filename"
>.htaccess</TT
> files for Apache</A
></DT
><DT
>5-1. <A
......
docs/html/installation.html
View file @ 393f13a4
......@@ -88,12 +88,12 @@ HREF="stepbystep.html"
><DL
><DT
>4.1.1. <A
HREF="stepbystep.html#AEN489"
HREF="stepbystep.html#intstall-into"
>Introduction</A
></DT
><DT
>4.1.2. <A
HREF="stepbystep.html#AEN493"
HREF="stepbystep.html#install-package-list"
>Package List</A
></DT
><DT
......@@ -113,22 +113,22 @@ HREF="stepbystep.html#perl-modules"
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#AEN674"
HREF="stepbystep.html#sbs-http"
>HTTP Server</A
></DT
><DT
>4.1.7. <A
HREF="stepbystep.html#AEN693"
HREF="stepbystep.html#AEN586"
>Bugzilla</A
></DT
><DT
>4.1.8. <A
HREF="stepbystep.html#AEN718"
HREF="stepbystep.html#AEN611"
>Setting Up the MySQL Database</A
></DT
><DT
>4.1.9. <A
HREF="stepbystep.html#AEN754"
HREF="stepbystep.html#AEN647"
><TT
CLASS="filename"
>checksetup.pl</TT
......@@ -136,12 +136,12 @@ CLASS="filename"
></DT
><DT
>4.1.10. <A
HREF="stepbystep.html#AEN786"
HREF="stepbystep.html#AEN679"
>Securing MySQL</A
></DT
><DT
>4.1.11. <A
HREF="stepbystep.html#AEN852"
HREF="stepbystep.html#AEN745"
>Configuring Bugzilla</A
></DT
></DL
......@@ -155,17 +155,17 @@ HREF="extraconfig.html"
><DL
><DT
>4.2.1. <A
HREF="extraconfig.html#AEN858"
HREF="extraconfig.html#AEN751"
>Dependency Charts</A
></DT
><DT
>4.2.2. <A
HREF="extraconfig.html#AEN873"
HREF="extraconfig.html#AEN766"
>Bug Graphs</A
></DT
><DT
>4.2.3. <A
HREF="extraconfig.html#AEN886"
HREF="extraconfig.html#AEN779"
>The Whining Cron</A
></DT
><DT
......@@ -218,28 +218,56 @@ CLASS="filename"
></DD
><DT
>4.3. <A
HREF="win32.html"
>Win32 Installation Notes</A
HREF="os-specific.html"
>OS Specific Installation Notes</A
></DT
><DD
><DL
><DT
>4.3.1. <A
HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
HREF="os-specific.html#os-win32"
>Microsoft Windows</A
></DT
><DT
>4.3.2. <A
HREF="win32.html#addlwintips"
>Additional Windows Tips</A
HREF="os-specific.html#os-macosx"
><SPAN
CLASS="productname"
>Mac OS X</SPAN
></A
></DT
></DL
></DD
><DT
>4.4. <A
HREF="osx.html"
>Mac OS X Installation Notes</A
HREF="http.html"
>HTTP Server Configuration</A
></DT
><DD
><DL
><DT
>4.4.1. <A
HREF="http.html#http-apache"
>Apache <SPAN
CLASS="productname"
>httpd</SPAN
></A
></DT
><DT
>4.4.2. <A
HREF="http.html#http-iis"
>Microsoft <SPAN
CLASS="productname"
>Internet Information Services</SPAN
></A
></DT
><DT
>4.4.3. <A
HREF="http.html#http-aol"
>AOL Server</A
></DT
></DL
></DD
><DT
>4.5. <A
HREF="troubleshooting.html"
......@@ -249,12 +277,12 @@ HREF="troubleshooting.html"
><DL
><DT
>4.5.1. <A
HREF="troubleshooting.html#AEN1245"
HREF="troubleshooting.html#AEN1059"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.5.2. <A
HREF="troubleshooting.html#AEN1250"
HREF="troubleshooting.html#AEN1064"
>DBD::Sponge::db prepare failed</A
></DT
><DT
......
docs/html/os-specific.html 0 → 100644
View file @ 393f13a4
<HTML
><HEAD
><TITLE
>OS Specific Installation Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Optional Additional Configuration"
HREF="extraconfig.html"><LINK
REL="NEXT"
TITLE="HTTP Server Configuration"
HREF="http.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="extraconfig.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="http.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="os-specific"
></A
>4.3. OS Specific Installation Notes</H1
><P
>Many aspects of the Bugzilla installation can be affected by the
the operating system you choose to install it on. Sometimes it can be made
easier and others more difficult. This section will attempt to help you
understand both the difficulties of running on specific operating systems
and the utilities available to make it easier.
</P
><P
>If you have anything to add or notes for an operating system not
covered, please file a bug in <A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
>.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="os-win32"
></A
>4.3.1. Microsoft Windows</H2
><P
>Making Bugzilla work on windows is still a very painful processes.
The Bugzilla Team is working to make it easier, but that goal is not
considered a top priority. If you wish to run Bugzilla, we still
recommend doing so on a Unix based system such as GNU/Linux. As of this
writing, all members of the Bugzilla team and all known large installations
run on Unix based systems.
</P
><P
>If after hearing all that, you have enough pain tolerance to attempt
installing Bugzilla on Win32, here are some pointers.
Because this is a development version of the guide, these instructions
are subject to change without notice. In fact, the Bugzilla Team hopes
they do as we would like to have Bugzilla resonabally close to "out of
the box" compatibility by the 2.18 release.
</P
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="win32-perl"
></A
>4.3.1.1. Win32 Perl</H3
><P
>Perl for Windows can be obtained from <A
HREF="http://www.activestate.com/"
TARGET="_top"
>ActiveState</A
>. You should be
able to find a compiled binary at <A
HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
TARGET="_top"
>http://aspn.activestate.com/ASPN/Downloads/ActivePerl/</A
>.
</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="win32-perl-modules"
></A
>4.3.1.2. Perl Modules on Win32</H3
><P
>Bugzilla on Windows requires the same perl modules found in
<A
HREF="stepbystep.html#install-package-list"
>Section 4.1.2</A
>. The main difference is that
windows uses <B
CLASS="command"
>ppm</B
> instead of CPAN.
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;C:\perl&#62; <B
CLASS="command"
>ppm &#60;module name&#62;</B
>
</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The above syntax should work for all modules with the exception
of Template Toolkit. The <A
HREF="http://tt2.org/download.html#win32"
TARGET="_top"
>Template Toolkit website</A
>
suggests using the instructions on <A
HREF="http://openinteract.sourceforge.net/"
TARGET="_top"
>OpenInteract's website</A
>.
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>A complete list of modules that can be installed using ppm can
be found at <A
HREF="http://www.activestate.com/PPMPackages/5.6plus"
TARGET="_top"
>http://www.activestate.com/PPMPackages/5.6plus</A
>.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="win32-code-changes"
></A
>4.3.1.3. Code changes required to run on win32</H3
><P
>Unfortunately, Bugzilla still doesn't run "out of the box" on
Windows. There is work in progress to make this easier, but until that
happens code will have to be modified. This section is an attempt to
list the required changes. It is an attempt to be all inclusive, but
there may be other changes required. If you find something is missing,
please file a bug in <A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
>.
</P
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="win32-code-checksetup"
></A
>4.3.1.3.1. Changes to <TT
CLASS="filename"
>checksetup.pl</TT
></H4
><P
>In <TT
CLASS="filename"
>checksetup.pl</TT
>, the line reading:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;my $mysql_binaries = `which mysql`;
</PRE
></FONT
></TD
></TR
></TABLE
><P
>to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;my $mysql_binaries = "D:\\mysql\\bin\\mysql";
</PRE
></FONT
></TD
></TR
></TABLE
><P
>And you'll also need to change:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;my $webservergid = getgrnam($my_webservergroup)
</PRE
></FONT
></TD
></TR
></TABLE
><P
>to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;my $webservergid = '8'
</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="win32-code-mail"
></A
>4.3.1.3.2. Making mail work</H4
><P
>The easiest way to get mail working is to use the mail patches
on <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=124174"
TARGET="_top"
>bug
124174</A
>. With any luck, this patch will receive the required
reviews and integrated into the main Bugzilla distribution very soon.
Until that happens, there's at least one report of this patch working
well on Windows.
</P
></DIV
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="AEN926"
></A
>4.3.1.3.3. System Calls</H4
><P
>In order to get system calls to work on win32's perl, you need
to tell the windows shell what interpreter to use. This is done by
changing the <TT
CLASS="function"
>system</TT
> calls. You will need to
search all of Bugzilla's code for <TT
CLASS="function"
>system</TT
> calls.
To tell perl your interpreter, it needs to be the first argument to
the <TT
CLASS="function"
>system</TT
> call. For example, you'll need to
change:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;system("./processmail", $id, $exporter);
</PRE
></FONT
></TD
></TR
></TABLE
><P
>with</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;system("C:\\perl\\bin\\perl", "processmail", $id, $exporter);
</PRE
></FONT
></TD
></TR
></TABLE
><P
>Notice that the <TT
CLASS="computeroutput"
>./</TT
> is also
removed.
</P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The <B
CLASS="command"
>grep</B
> command is very helpful in finding
these <TT
CLASS="function"
>system</TT
> calls, assuming you have the
<SPAN
CLASS="productname"
>cygwin</SPAN
> utilities.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="win32-http"
></A
>4.3.1.4. Serving the web pages</H3
><P
>As is the case on Unix based systems, any web server should be
able to handle Bugzilla; however, the Bugzilla Team still recommends
Apache whenever asked. No matter what web server you choose, be sure
to pay attention to the security notes in <A
HREF="security.html"
>Section 5.6</A
>.
More information on configuring specific web servers can be found in
<A
HREF="http.html"
>Section 4.4</A
>.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If using Apache on windows, you can set the <A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>ScriptInterpreterSource</A
>
directive in your Apache config, if you don't do this, you'll have
to modify the first line of every script to contain your path to
perl instead of <TT
CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
>.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="os-macosx"
></A
>4.3.2. <SPAN
CLASS="productname"
>Mac OS X</SPAN
></H2
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
The GD library, which Bugzilla needs to do bug graphs, is one of
these.</P
><P
>The easiest way to get a lot of these is with a program called
Fink, which is similar in nature to the CPAN installer, but installs
common GNU utilities. Fink is available from
<A
HREF="http://sourceforge.net/projects/fink/"
TARGET="_top"
>http://sourceforge.net/projects/fink/</A
>.</P
><P
>Follow the instructions for setting up Fink. Once it's installed,
you'll want to run the following as root:
<B
CLASS="command"
>fink install gd</B
>
</P
><P
>It will prompt you for a number of dependencies, type 'y' and hit
enter to install all of the dependencies. Then watch it work.</P
><P
>To prevent creating conflicts with the software that Apple installs
by default, Fink creates its own directory tree at /sw where it installs
most of the software that it installs. This means your libraries and
headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
and /usr/local/include. Because of these changed locations for the
libraries, the Perl GD module will not install directly via CPAN, because it
looks for the specific paths instead of getting them from your
environment. But there's a way around that :-)</P
><P
>Instead of typing
<SPAN
CLASS="QUOTE"
>"install GD"</SPAN
>
at the
<TT
CLASS="prompt"
>cpan&#62;</TT
>
prompt, type
<B
CLASS="command"
>look GD</B
>.
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 <A
HREF="../sgml/gd-makefile.patch"
TARGET="_top"
>this patch</A
>
to the Makefile.PL file (save the
patch into a file and use the command
<B
CLASS="command"
>patch &#60; patchfile</B
>.)
</P
><P
>Then, run these commands to finish the installation of the GD
module:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <B
CLASS="command"
>perl Makefile.PL</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make test</B
>
</TD
></TR
><TR
><TD
>&#13; <B
CLASS="command"
>make install</B
>
</TD
></TR
><TR
><TD
>And don't forget to run
<B
CLASS="command"
>exit</B
>
to get back to CPAN.</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="extraconfig.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="http.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Optional Additional Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>HTTP Server Configuration</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/security.html
View file @ 393f13a4
......@@ -446,156 +446,11 @@ CLASS="filename"
is provided for those that want to know exactly what is created.
</P
><P
>Note the instructions which follow are Apache-specific. If you
>FIX ME BEFORE RELEASE!!!!!
Note the instructions which follow are Apache-specific. If you
use IIS, Netscape, or other non-Apache web servers, please consult
your system documentation for how to secure these files from being
transmitted to curious users.</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# don't allow people to retrieve non-cgi executable files or our private data
&#60;FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$&#62;
deny from all
&#60;/FilesMatch&#62;
&#60;FilesMatch ^(localconfig.js|localconfig.rdf)$&#62;
allow from all
&#60;/FilesMatch&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/data/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory; the only exception is duplicates.rdf, which is used by
# duplicates.xul and must be loadable over the web
deny from all
&#60;Files duplicates.rdf&#62;
allow from all
&#60;/Files&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/data/webdot</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# Restrict access to .dot files to the public webdot server at research.att.com
# if research.att.com ever changed their IP, or if you use a different
# webdot server, you'll need to edit this
&#60;FilesMatch ^[0-9]+\.dot$&#62;
Allow from 192.20.225.10
Deny from all
&#60;/FilesMatch&#62;
# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
# .map files
&#60;FilesMatch ^[0-9]+\.(png|gif|jpg|map)$&#62;
Allow from all
&#60;/FilesMatch&#62;
# And no directory listings, either.
Deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/Bugzilla/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
><TT
CLASS="filename"
>$BUGZILLA_HOME/template/.htaccess</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
></OL
>
......
docs/html/stepbystep.html
View file @ 393f13a4
......@@ -81,17 +81,17 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN489"
NAME="intstall-into"
></A
>4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
have got it working fine.
Please see the
Please see
<A
HREF="win32.html"
>Win32 Installation Notes</A
HREF="os-specific.html#os-win32"
>Section 4.3.1</A
>
for further advice on getting Bugzilla to work on Microsoft
Windows.</P
......@@ -101,7 +101,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN493"
NAME="install-package-list"
></A
>4.1.2. Package List</H2
><DIV
......@@ -244,7 +244,7 @@ TARGET="_top"
>DBD::mysql
</A
>
(1.2209)
(2.1010)
</P
></LI
><LI
......@@ -254,7 +254,7 @@ HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top"
>DBI</A
>
(1.13)
(1.32)
</P
></LI
><LI
......@@ -863,7 +863,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN647"
NAME="AEN552"
></A
>4.1.5.1. DBI</H3
><P
......@@ -878,7 +878,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN650"
NAME="AEN555"
></A
>4.1.5.2. Data::Dumper</H3
><P
......@@ -892,7 +892,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN653"
NAME="AEN558"
></A
>4.1.5.3. MySQL-related modules</H3
><P
......@@ -918,7 +918,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN658"
NAME="AEN563"
></A
>4.1.5.4. TimeDate modules</H3
><P
......@@ -934,13 +934,13 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN661"
NAME="AEN566"
></A
>4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
defacto standard for programatic image construction. The Perl bindings
defacto standard for programmatic image construction. The Perl bindings
to it found in the GD library are used on millions of web pages to
generate graphs on the fly. That's what Bugzilla will be using it for
so you must install it if you want any of the graphing to work.</P
......@@ -989,7 +989,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN668"
NAME="AEN573"
></A
>4.1.5.6. Chart::Base (optional)</H3
><P
......@@ -1004,7 +1004,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN671"
NAME="AEN576"
></A
>4.1.5.7. Template Toolkit</H3
><P
......@@ -1020,19 +1020,25 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN674"
NAME="sbs-http"
></A
>4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
different machine than MySQL, but need to adjust the MySQL
<SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>You have freedom of choice here, pretty much any web server that
is capable of running <A
HREF="glossary.html#gloss-cgi"
><I
CLASS="glossterm"
>CGI</I
></A
>
user permissions accordingly.
<DIV
scripts will work. <A
HREF="http.html"
>Section 4.4</A
> has more information about
configuring web servers to work with Bugzilla.
</P
><DIV
CLASS="note"
><P
></P
......@@ -1061,144 +1067,13 @@ VALIGN="TOP"
></TR
></TABLE
></DIV
>
</P
><P
>You'll want to make sure that your web server will <EM
>run</EM
>
any file
with the .cgi extension as a CGI program and not simply display the source
code. If you're
using Apache that means uncommenting the following line in the httpd.conf
file:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;AddHandler cgi-script .cgi
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>With Apache you'll also want to make sure that within the
httpd.conf file these lines:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Options +ExecCGI
AllowOverride Limit
</PRE
></FONT
></TD
></TR
></TABLE
>
are in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>AllowOverride Limit allows the use of a Deny statement in the
.htaccess file generated by checksetup.pl</P
><P
>Users of older versions of Apache may find the above lines
in the srm.conf and access.conf files, respectively.</P
></TD
></TR
></TABLE
></DIV
>
</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>There are important files and directories that should not be a
served by the HTTP server - most files in the
<SPAN
CLASS="QUOTE"
>"data"</SPAN
>
directory and the
<SPAN
CLASS="QUOTE"
>"localconfig"</SPAN
>
file. You should configure your HTTP server to not serve
these files. Failure to do so will expose critical passwords and
other data. Please see
<A
HREF="extraconfig.html#htaccess"
>.htaccess files and security</A
>
for details on how to do this for Apache; the checksetup.pl
script should create appropriate .htaccess files for you.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN693"
NAME="AEN586"
></A
>4.1.7. Bugzilla</H2
><P
......@@ -1238,7 +1113,7 @@ ALIGN="LEFT"
VALIGN="TOP"
><P
>If you symlink the bugzilla directory into your Apache's HTML
heirarchy, you may receive
hierarchy, you may receive
<SPAN
CLASS="errorname"
>Forbidden</SPAN
......@@ -1368,7 +1243,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN718"
NAME="AEN611"
></A
>4.1.8. Setting Up the MySQL Database</H2
><P
......@@ -1541,7 +1416,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN754"
NAME="AEN647"
></A
>4.1.9. <TT
CLASS="filename"
......@@ -1694,7 +1569,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN786"
NAME="AEN679"
></A
>4.1.10. Securing MySQL</H2
><P
......@@ -1737,7 +1612,7 @@ BORDER="0"
>
</P
><P
>This means anyone from anywhere on the internet can not only drop
>This means anyone from anywhere on the Internet can not only drop
the database with one SQL command, and they can write as root to the
system.</P
><P
......@@ -1972,7 +1847,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN852"
NAME="AEN745"
></A
>4.1.11. Configuring Bugzilla</H2
><P
......
docs/html/troubleshooting.html
View file @ 393f13a4
......@@ -13,8 +13,8 @@ REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Mac OS X Installation Notes"
HREF="osx.html"><LINK
TITLE="HTTP Server Configuration"
HREF="http.html"><LINK
REL="NEXT"
TITLE="Administering Bugzilla"
HREF="administration.html"></HEAD
......@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="osx.html"
HREF="http.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -85,7 +85,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1245"
NAME="AEN1059"
></A
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
......@@ -110,7 +110,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1250"
NAME="AEN1064"
></A
>4.5.2. DBD::Sponge::db prepare failed</H2
><P
......@@ -266,7 +266,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="osx.html"
HREF="http.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -294,7 +294,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Mac OS X Installation Notes</TD
>HTTP Server Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/using.html
View file @ 393f13a4
......@@ -122,7 +122,7 @@ HREF="hintsandtips.html"
><DL
><DT
>3.2.1. <A
HREF="hintsandtips.html#AEN431"
HREF="hintsandtips.html#AEN336"
>Autolinkification</A
></DT
><DT
......@@ -142,7 +142,7 @@ HREF="hintsandtips.html#attachments"
></DT
><DT
>3.2.5. <A
HREF="hintsandtips.html#AEN460"
HREF="hintsandtips.html#AEN365"
>Filing Bugs</A
></DT
></DL
......
docs/html/variant-scarab.html
View file @ 393f13a4
......@@ -78,7 +78,7 @@ NAME="variant-scarab"
>D.4. Scarab</H1
><P
>Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.</P
Servlet technology. It is currently at version 1.0 beta 13.</P
><P
>URL:
<A
......@@ -88,7 +88,7 @@ TARGET="_top"
>
</P
><P
>This section last updated 27 Jul 2002</P
>This section last updated 18 Jan 2003</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/variant-sourceforge.html
View file @ 393f13a4
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant-perforce.html"><LINK
REL="NEXT"
TITLE="Glossary"
HREF="glossary.html"></HEAD
TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="glossary.html"
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -125,7 +125,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="glossary.html"
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -149,7 +149,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Glossary</TD
>GNU Free Documentation License</TD
></TR
></TABLE
></DIV
......
docs/html/win32.html deleted 100644 → 0
View file @ 3b3f69d7
<HTML
><HEAD
><TITLE
>Win32 Installation Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Optional Additional Configuration"
HREF="extraconfig.html"><LINK
REL="NEXT"
TITLE="Mac OS X Installation Notes"
HREF="osx.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="extraconfig.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="osx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="win32"
></A
>4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
wish to emphasise that The easiest way to install Bugzilla on
Intel-archiecture machines
is to install some variant of GNU/Linux, then follow the UNIX
installation instructions in this Guide. If you have any influence in the
platform choice for running this system, please choose GNU/Linux instead
of Microsoft Windows.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>After that warning, here's the situation for 2.16
and Windows. It doesn't work at all out of the box.
You are almost certainly better off getting
the 2.17 version from CVS (after consultation with the Bugzilla Team to
make sure you are pulling on a stable day) because we'll be doing a load
of work to make the Win32 experience more pleasant than it is now.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; If you still want to try this, to have any hope of getting it to work,
you'll need to apply the
<A
HREF=""
TARGET="_top"
>mail patch</A
> from
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=124174"
TARGET="_top"
>bug 124174</A
>.
After that, you'll need to read the (outdated) installation
instructions below, some (probably a lot better) <A
HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view"
TARGET="_top"
>more
recent ones</A
> kindly provided by Toms Baugis and Jean-Sebastien
Guay, and also check the
<A
HREF="http://www.bugzilla.org/releases/2.16/docs/win32.html"
TARGET="_top"
>Bugzilla 2.16 Win32 update page
</A
>. If we get time,
we'll write some better installation instructions for 2.16 and put
them up there. But no promises.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="wininstall"
></A
>4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You should be familiar with, and cross-reference, the rest of
the
<A
HREF="installation.html"
>Bugzilla Installation</A
>
section while performing your Win32 installation.</P
><P
>Making Bugzilla work on Microsoft Windows is no picnic. Support
for Win32 has improved dramatically in the last few releases, but, if
you choose to proceed, you should be a
<EM
>very</EM
>
skilled Windows Systems Administrator with strong troubleshooting
abilities, a high tolerance for pain, and moderate perl skills.
Bugzilla on NT requires hacking source code and implementing some
advanced utilities. What follows is the recommended installation
procedure for Win32; additional suggestions are provided in
<A
HREF="faq.html"
>Appendix A</A
>
.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
>Install
<A
HREF="http://www.apache.org/"
TARGET="_top"
>Apache Web Server</A
>
for Windows, and copy the Bugzilla files somewhere Apache can serve
them. Please follow all the instructions referenced in
<A
HREF="installation.html"
>Bugzilla Installation</A
>
regarding your Apache configuration, particularly instructions
regarding the
<SPAN
CLASS="QUOTE"
>"AddHandler"</SPAN
>
parameter and
<SPAN
CLASS="QUOTE"
>"ExecCGI"</SPAN
>
.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You may also use Internet Information Server or Personal
Web Server for this purpose. However, setup is quite different.
If ActivePerl doesn't seem to handle your file associations
correctly (for .cgi and .pl files), please consult
<A
HREF="faq.html"
>Appendix A</A
>
.</P
><P
>If you are going to use IIS, if on Windows NT you must be
updated to at least Service Pack 4. Windows 2000 ships with a
sufficient version of IIS.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>Install
<A
HREF="http://www.activestate.com/"
TARGET="_top"
>ActivePerl</A
>
for Windows. Check
<A
HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
TARGET="_top"
>&#13; http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A
>
for a current compiled binary.</P
><P
>Please also check the following links to fully understand the
status of ActivePerl on Win32:
<A
HREF="http://language.perl.com/newdocs/pod/perlport.html"
TARGET="_top"
>&#13; Perl Porting</A
>
, and
<A
HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
TARGET="_top"
>&#13; Perl on Win32 FAQ</A
>
</P
></LI
><LI
><P
>Use ppm from your perl\bin directory to install the following
packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
AppConfig, and Template. You may need to extract them from .zip
format using Winzip or other unzip program first. Most of these
additional ppm modules can be downloaded from ActiveState, but
AppConfig and Template should be obtained from OpenInteract using
<A
HREF="http://openinteract.sourceforge.net/"
TARGET="_top"
>the
instructions on the Template Toolkit web site</A
>
.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You can find a list of modules at
<A
HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
TARGET="_top"
>&#13; http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
>
or
<A
HREF="http://www.activestate.com/PPMPackages/5.6plus"
TARGET="_top"
>&#13; http://www.activestate.com/PPMPackages/5.6plus</A
>
</P
></TD
></TR
></TABLE
></DIV
><P
>The syntax for ppm is:
<TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>C:&#62;</TT
>
<B
CLASS="command"
>ppm &#60;modulename&#62;</B
>
</TT
>
</P
><DIV
CLASS="example"
><A
NAME="AEN1032"
></A
><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
></P
><P
>&#13; <TT
CLASS="prompt"
>C:&#62;</TT
>
<B
CLASS="command"
>ppm
<TT
CLASS="option"
>DBD-Mysql</TT
>
</B
>
</P
><P
>Watch your capitalization!</P
></DIV
><P
>ActiveState's 5.6Plus directory also contains an AppConfig
ppm, so you might see the following error when trying to install
the version at OpenInteract:</P
><P
>&#13; <TT
CLASS="computeroutput"
>Error installing package 'AppConfig': Read a PPD
for 'AppConfig', but it is not intended for this build of Perl
(MSWin32-x86-multi-thread)</TT
>
</P
><P
>If so, download both
<A
HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.tar.gz"
TARGET="_top"
>&#13; the tarball</A
>
and
<A
HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.ppd"
TARGET="_top"
>&#13; the ppd</A
>
directly from OpenInteract, then run ppm from within the same
directory to which you downloaded those files and install the
package by referencing the ppd file explicitly via in the install
command, f.e.:
<DIV
CLASS="example"
><A
NAME="AEN1045"
></A
><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
></P
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <B
CLASS="command"
>install
<TT
CLASS="filename"
>C:\AppConfig.ppd</TT
>
</B
>
</TT
>
</P
></DIV
>
</P
></LI
><LI
><P
>Install MySQL for NT.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You can download MySQL for Windows NT from
<A
HREF="http://www.mysql.com/"
TARGET="_top"
>MySQL.com</A
>
. Some find it helpful to use the WinMySqlAdmin utility, included
with the download, to set up the database.</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>Setup MySQL</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>C:&#62;</TT
>
<B
CLASS="command"
>C:\mysql\bin\mysql -u root mysql</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>DELETE FROM user WHERE Host='localhost' AND
User='';</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';</B
>
</TT
>
</P
><P
>&#13; <SPAN
CLASS="QUOTE"
>"new_password"</SPAN
>
, above, indicates whatever password you wish to use for your
<SPAN
CLASS="QUOTE"
>"root"</SPAN
>
user.</P
></LI
><LI
><A
NAME="ntbugs-password"
></A
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>GRANT SELECT, INSERT, UPDATE, DELETE, INDEX,
ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
IDENTIFIED BY 'bugs_password';</B
>
</TT
>
</P
><P
>&#13; <SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
>
, above, indicates whatever password you wish to use for your
<SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>
user.</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>FLUSH PRIVILEGES;</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>create database bugs;</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>exit;</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>C:&#62;</TT
>
<B
CLASS="command"
>C:\mysql\bin\mysqladmin -u root -p
reload</B
>
</TT
>
</P
></LI
></OL
></LI
><LI
><P
>Edit
<TT
CLASS="filename"
>checksetup.pl</TT
>
in your Bugzilla directory. Change this line:</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>my $webservergid =
getgrnam($my_webservergroup);</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>to</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>my $webservergid =
$my_webservergroup;</PRE
></FONT
></TD
></TR
></TABLE
>
or the name of the group you wish to own the files explicitly:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>my $webservergid =
'Administrators'</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>Run
<TT
CLASS="filename"
>checksetup.pl</TT
>
from the Bugzilla directory.</P
></LI
><LI
><P
>Edit
<TT
CLASS="filename"
>localconfig</TT
>
to suit your requirements. Set
<TT
CLASS="varname"
>$db_pass</TT
>
to your
<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
>
from
<A
HREF="win32.html#ntbugs-password"
>step 5.d</A
>
, and
<TT
CLASS="varname"
>$webservergroup</TT
>
to
<SPAN
CLASS="QUOTE"
>"8"</SPAN
>
.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Not sure on the
<SPAN
CLASS="QUOTE"
>"8"</SPAN
>
for
<TT
CLASS="varname"
>$webservergroup</TT
>
above. If it's wrong, please send corrections.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>Edit
<TT
CLASS="filename"
>defparams.pl</TT
>
to suit your requirements. Particularly, set
<TT
CLASS="varname"
>DefParam("maintainer")</TT
>
and
<TT
CLASS="varname"
>DefParam("urlbase") to match your install.</TT
>
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This is yet another step I'm not sure of, since the
maintainer of this documentation does not maintain Bugzilla on
NT. If you can confirm or deny that this step is required, please
let me know.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>There are several alternatives to Sendmail that will work
on Win32. The one mentioned here is a
<EM
>suggestion</EM
>
, not a requirement. Some other mail packages that can work
include
<A
HREF="http://www.blat.net/"
TARGET="_top"
>BLAT</A
>
,
<A
HREF="http://www.geocel.com/windmail/"
TARGET="_top"
>Windmail</A
>
,
<A
HREF="http://www.dynamicstate.com/"
TARGET="_top"
>Mercury
Sendmail</A
>
, and the CPAN Net::SMTP Perl module (available in .ppm). Every
option requires some hacking of the Perl scripts for Bugzilla to
make it work. The option here simply requires the least.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
>Download NTsendmail, available from
<A
HREF="http://www.ntsendmail.com/"
TARGET="_top"
>&#13; www.ntsendmail.com</A
>
. You must have a "real" mail server which allows you to relay
off it in your $ENV{"NTsendmail"} (which you should probably
place in globals.pl)</P
></LI
><LI
><P
>Put ntsendmail.pm into your .\perl\lib directory.</P
></LI
><LI
><P
>Add to globals.pl:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
># these settings configure the NTsendmail
process use NTsendmail;
$ENV{"NTsendmail"}="your.smtpserver.box";
$ENV{"NTsendmail_debug"}=1;
$ENV{"NTsendmail_max_tries"}=5;</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Some mention to also edit
<TT
CLASS="varname"
>$db_pass</TT
>
in
<TT
CLASS="filename"
>globals.pl</TT
>
to be your
<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
>
. Although this may get you around some problem
authenticating to your database, since globals.pl is not
normally restricted by
<TT
CLASS="filename"
>.htaccess</TT
>
, your database password is exposed to whoever uses your web
server.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>Find and comment out all occurences of
<SPAN
CLASS="QUOTE"
>"
<B
CLASS="command"
>open(SENDMAIL</B
>
"</SPAN
>
in your Bugzilla directory. Then replace them with:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
># new sendmail functionality my $mail=new
NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
$to=$login; my $subject=$urlbase;
$mail-&#62;send($from,$to,$subject,$msg);</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Some have found success using the commercial product,
<SPAN
CLASS="productname"
>Windmail</SPAN
>
. You could try replacing your sendmail calls with:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>open SENDMAIL,
"|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62;
mail.log";</PRE
></FONT
></TD
></TR
></TABLE
>
or something to that effect.</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
></DIV
></LI
><LI
><P
>Change all references in all files from
<TT
CLASS="filename"
>processmail</TT
>
to
<TT
CLASS="filename"
>processmail.pl</TT
>
, and rename
<TT
CLASS="filename"
>processmail</TT
>
to
<TT
CLASS="filename"
>processmail.pl</TT
>
.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Many think this may be a change we want to make for
main-tree Bugzilla. It's painless for the UNIX folks, and will
make the Win32 people happier.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Some people have suggested using the Net::SMTP Perl module
instead of NTsendmail or the other options listed here. You can
change processmail.pl to make this work.
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
my $smtp = Net::SMTP-&#62;new('&#60;Name of your SMTP server&#62;'); #connect to SMTP server
$smtp-&#62;mail('&#60;your name&#62;@&#60;you smpt server&#62;');# use the sender's adress here
$smtp-&#62;to($tolist); # recipient's address
$smtp-&#62;data(); # Start the mail
$smtp-&#62;datasend($msg);
$smtp-&#62;dataend(); # Finish sending the mail
$smtp-&#62;quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist";
}
</PRE
></FONT
></TD
></TR
></TABLE
>
here is a test mail program for Net::SMTP:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
use Net::SMTP;
my $smtp = Net::SMTP-&#62;new('&#60;Name of your SMTP server', Timeout =&#62; 30, Debug
=&#62; 1, ); # connect to SMTP server
$smtp-&#62;auth;
$smtp-&#62;mail('you@yourcompany.com');# use the sender's adress
here
$smtp-&#62;to('someotherAddress@someotherdomain.com'); #
recipient's address
$smtp-&#62;data(); # Start the mail
$smtp-&#62;datasend('test');
$smtp-&#62;dataend(); # Finish sending the mail
$smtp-&#62;quit; # Close the SMTP connection
exit;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This step is optional if you are using IIS or another web
server which only decides on an interpreter based upon the file
extension (.pl), rather than the
<SPAN
CLASS="QUOTE"
>"shebang"</SPAN
>
line (#/usr/bonsaitools/bin/perl)</P
></TD
></TR
></TABLE
></DIV
><P
>Modify the path to perl on the first line (#!) of all files
to point to your Perl installation, and add
<SPAN
CLASS="QUOTE"
>"perl"</SPAN
>
to the beginning of all Perl system calls that use a perl script as
an argument. This may take you a while. There is a
<SPAN
CLASS="QUOTE"
>"setperl.csh"</SPAN
>
utility to speed part of this procedure, available in the
<A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
>
section of The Bugzilla Guide. However, it requires the Cygwin
GNU-compatible environment for Win32 be set up in order to work.
See
<A
HREF="http://www.cygwin.com/"
TARGET="_top"
>http://www.cygwin.com/</A
>
for details on obtaining Cygwin.</P
></LI
><LI
><P
>Modify the invocation of all system() calls in all perl
scripts in your Bugzilla directory. You should specify the full
path to perl for each system() call. For instance, change this line
in processmail:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
system ("./processmail",@ARGLIST);
&#60;/programlisting&#62; to
&#60;programlisting&#62;
system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
></OL
></DIV
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you are using IIS or Personal Web Server, you must add cgi
relationships to Properties -&#62; Home directory (tab) -&#62;
Application Settings (section) -&#62; Configuration (button), such
as:</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>.cgi to: &#60;perl install directory&#62;\perl.exe %s
%s .pl to: &#60;perl install directory&#62;\perl.exe %s %s
GET,HEAD,POST</PRE
></FONT
></TD
></TR
></TABLE
>
Change the path to Perl to match your install, of course.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="addlwintips"
></A
>4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>From Andrew Pearson:
<A
NAME="AEN1199"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
Windows 98 and higher, as well as for IIS 4.0. Microsoft has
information available at
<A
HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
TARGET="_top"
>&#13; http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
>
</P
><P
>Basically you need to add two String Keys in the registry at
the following location:</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13; HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>The keys should be called ".pl" and ".cgi", and both should
have a value something like:
<B
CLASS="command"
>c:/perl/bin/perl.exe "%s" "%s"</B
>
</P
><P
>The KB article only talks about .pl, but it goes into more
detail and provides a perl test script.</P
></BLOCKQUOTE
>
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If attempting to run Bugzilla 2.12 or older, you will need to
remove encrypt() calls from the Perl source. This is
<EM
>not necessary</EM
>
for Bugzilla 2.13 and later, which includes the current release,
Bugzilla &#38;bz-ver;.
<DIV
CLASS="example"
><A
NAME="AEN1211"
></A
><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
></P
><P
>Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
$enteredcryptpwd = FetchOneColumn();</PRE
></FONT
></TD
></TR
></TABLE
>
with this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>my $enteredcryptpwd = $enteredpwd</PRE
></FONT
></TD
></TR
></TABLE
>
in cgi.pl.</P
></DIV
>
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="extraconfig.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="osx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Optional Additional Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Mac OS X Installation Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/makedocs.pl
View file @ 393f13a4
......@@ -74,5 +74,5 @@ MakeDocs('separate HTML', "jade -t sgml -i html -d $LDP_HOME/ldp.dsl\#html " .
MakeDocs('big HTML', "jade -V nochunks -t sgml -i html -d " .
"$LDP_HOME/ldp.dsl\#html $JADE_PUB/xml.dcl " .
"../sgml/Bugzilla-Guide.sgml > Bugzilla-Guide.html");
MakeDocs('big text', "lynx -dump -nolist Bugzilla-Guide.html " .
MakeDocs('big text', "lynx -dump -justify=off -nolist Bugzilla-Guide.html " .
"> ../txt/Bugzilla-Guide.txt");
docs/txt/Bugzilla-Guide.txt
View file @ 393f13a4
......@@ -5,6 +5,8 @@ Matthew P. Barnson
The Bugzilla Team
2.17.3 Development Release Edition
2003-01-02
This is the documentation for Bugzilla, the mozilla.org bug-tracking
......@@ -14,7 +16,7 @@ The Bugzilla Team
This documentation is maintained in DocBook 4.1.2 XML format. Changes
are best submitted as plain text or SGML diffs, attached to a bug
filed in mozilla.org's Bugzilla.
filed in the Bugzilla Documentation compontent.
This is a development version of this guide. Information in it is
subject to change before the 2.18 release of this guide (which will
......@@ -45,8 +47,8 @@ The Bugzilla Team
4.1. Step-by-step Install
4.2. Optional Additional Configuration
4.3. Win32 Installation Notes
4.4. Mac OS X Installation Notes
4.3. OS Specific Installation Notes
4.4. HTTP Server Configuration
4.5. Troubleshooting
5. Administering Bugzilla
......@@ -82,399 +84,47 @@ The Bugzilla Team
D.5. Perforce SCM
D.6. SourceForge
Glossary
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
5-1. Upgrading using CVS
5-2. Upgrading using the tarball
5-3. Upgrading using patches
_________________________________________________________________
Chapter 1. About This Guide
1.1. Copyright Information
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 no
Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included below.
--Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team
If you have any questions regarding this document, its copyright, or
publishing this document in non-electronic form, please contact 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.
_________________________________________________________________
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
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:
A. 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.
B. 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).
C. State on the Title page the name of the publisher of the Modified
Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. 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.
G. Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's license
notice.
H. Include an unaltered copy of this License.
I. 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.
J. 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.
K. 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.
L. 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.
M. Delete any section entitled "Endorsements". Such a section may not
be included in the Modified Version.
N. 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/ .
Glossary
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.
List of Examples
4-1. .htaccess files for Apache
5-1. Upgrading using CVS
5-2. Upgrading using the tarball
5-3. Upgrading using patches
_________________________________________________________________
How to use this License for your documents
Chapter 1. About This Guide
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:
1.1. Copyright Information
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.
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 no
Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in Appendix E.
--Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team
If you have any questions regarding this document, its copyright, or
publishing this document in non-electronic form, please contact The
Bugzilla Team.
_________________________________________________________________
1.2. Disclaimer
......@@ -1013,8 +663,8 @@ Chapter 4. Installation
Bugzilla has been successfully installed under Solaris, Linux, and
Win32. Win32 is not yet officially supported, but many people have got
it working fine. Please see the Win32 Installation Notes for further
advice on getting Bugzilla to work on Microsoft Windows.
it working fine. Please see Section 4.3.1 for further advice on
getting Bugzilla to work on Microsoft Windows.
_________________________________________________________________
4.1.2. Package List
......@@ -1040,8 +690,8 @@ Chapter 4. Installation
d. Text::Wrap (2001.0131)
e. File::Spec (0.82)
f. Data::Dumper (any)
g. DBD::mysql (1.2209)
h. DBI (1.13)
g. DBD::mysql (2.1010)
h. DBI (1.32)
i. Date::Parse (any)
j. CGI (2.88)
and, optionally:
......@@ -1215,10 +865,11 @@ Chapter 4. Installation
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on millions of web pages to
generate graphs on the fly. That's what Bugzilla will be using it for
so you must install it if you want any of the graphing to work.
defacto standard for programmatic image construction. The Perl
bindings to it found in the GD library are used on millions of web
pages to generate graphs on the fly. That's what Bugzilla will be
using it for so you must install it if you want any of the graphing to
work.
Note
......@@ -1246,10 +897,9 @@ Chapter 4. Installation
4.1.6. HTTP Server
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a different
machine than MySQL, but need to adjust the MySQL "bugs" user
permissions accordingly.
You have freedom of choice here, pretty much any web server that is
capable of running CGI scripts will work. Section 4.4 has more
information about configuring web servers to work with Bugzilla.
Note
......@@ -1257,38 +907,6 @@ Chapter 4. Installation
Guide installation instructions, in general, assume you are using
Apache. If you have got Bugzilla working using another webserver,
please share your experiences with us.
You'll want to make sure that your web server will run any file with
the .cgi extension as a CGI program and not simply display the source
code. If you're using Apache that means uncommenting the following
line in the httpd.conf file:
AddHandler cgi-script .cgi
With Apache you'll also want to make sure that within the httpd.conf
file these lines:
Options +ExecCGI
AllowOverride Limit
are in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
Note
AllowOverride Limit allows the use of a Deny statement in the
.htaccess file generated by checksetup.pl
Users of older versions of Apache may find the above lines in the
srm.conf and access.conf files, respectively.
Warning
There are important files and directories that should not be a served
by the HTTP server - most files in the "data" directory and the
"localconfig" file. You should configure your HTTP server to not serve
these files. Failure to do so will expose critical passwords and other
data. Please see .htaccess files and security for details on how to do
this for Apache; the checksetup.pl script should create appropriate
.htaccess files for you.
_________________________________________________________________
4.1.7. Bugzilla
......@@ -1302,7 +920,7 @@ AllowOverride Limit
Tip
If you symlink the bugzilla directory into your Apache's HTML
heirarchy, you may receive Forbidden errors unless you add the
hierarchy, you may receive Forbidden errors unless you add the
"FollowSymLinks" directive to the <Directory> entry for the HTML root
in httpd.conf.
......@@ -1427,7 +1045,7 @@ processmail syncshadowdb
it defaults to no passwords whatsoever
it defaults to allowing "File_Priv"
This means anyone from anywhere on the internet can not only drop the
This means anyone from anywhere on the Internet can not only drop the
database with one SQL command, and they can write as root to the
system.
......@@ -1502,7 +1120,7 @@ processmail syncshadowdb
enable server-side image maps in Apache. Alternatively, you could set
up a webdot server, or use the AT&T public webdot server (the default
for the webdotbase param). Note that AT&T's server won't work if
Bugzilla is only accessible using HTTPS.
Bugzilla is only accessible using HARTS.
_________________________________________________________________
4.2.2. Bug Graphs
......@@ -1702,339 +1320,131 @@ set=ISO-8859-1/i" *.cgi *.pl
for more information.
_________________________________________________________________
4.3. Win32 Installation Notes
This section covers installation on Microsoft Windows. Bugzilla has
been made to work on Win32 platforms, but the Bugzilla team wish to
emphasise that The easiest way to install Bugzilla on
Intel-archiecture machines is to install some variant of GNU/Linux,
then follow the UNIX installation instructions in this Guide. If you
have any influence in the platform choice for running this system,
please choose GNU/Linux instead of Microsoft Windows.
4.3. OS Specific Installation Notes
Warning
Many aspects of the Bugzilla installation can be affected by the the
operating system you choose to install it on. Sometimes it can be made
easier and others more difficult. This section will attempt to help
you understand both the difficulties of running on specific operating
systems and the utilities available to make it easier.
After that warning, here's the situation for 2.16 and Windows. It
doesn't work at all out of the box. You are almost certainly better
off getting the 2.17 version from CVS (after consultation with the
Bugzilla Team to make sure you are pulling on a stable day) because
we'll be doing a load of work to make the Win32 experience more
pleasant than it is now.
If you still want to try this, to have any hope of getting it to work,
you'll need to apply the mail patch from bug 124174. After that,
you'll need to read the (outdated) installation instructions below,
some (probably a lot better) more recent ones kindly provided by Toms
Baugis and Jean-Sebastien Guay, and also check the Bugzilla 2.16 Win32
update page . If we get time, we'll write some better installation
instructions for 2.16 and put them up there. But no promises.
If you have anything to add or notes for an operating system not
covered, please file a bug in Bugzilla Documentation.
_________________________________________________________________
4.3.1. Win32 Installation: Step-by-step
Note
You should be familiar with, and cross-reference, the rest of the
Bugzilla Installation section while performing your Win32
installation.
Making Bugzilla work on Microsoft Windows is no picnic. Support for
Win32 has improved dramatically in the last few releases, but, if you
choose to proceed, you should be a very skilled Windows Systems
Administrator with strong troubleshooting abilities, a high tolerance
for pain, and moderate perl skills. Bugzilla on NT requires hacking
source code and implementing some advanced utilities. What follows is
the recommended installation procedure for Win32; additional
suggestions are provided in Appendix A .
1. Install Apache Web Server for Windows, and copy the Bugzilla files
somewhere Apache can serve them. Please follow all the
instructions referenced in Bugzilla Installation regarding your
Apache configuration, particularly instructions regarding the
"AddHandler" parameter and "ExecCGI" .
Note
You may also use Internet Information Server or Personal Web Server
for this purpose. However, setup is quite different. If ActivePerl
doesn't seem to handle your file associations correctly (for .cgi and
.pl files), please consult Appendix A .
If you are going to use IIS, if on Windows NT you must be updated to
at least Service Pack 4. Windows 2000 ships with a sufficient version
of IIS.
2. Install ActivePerl for Windows. Check
http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a
current compiled binary.
Please also check the following links to fully understand the
status of ActivePerl on Win32: Perl Porting , and Perl on Win32
FAQ
3. Use ppm from your perl\bin directory to install the following
packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
AppConfig, and Template. You may need to extract them from .zip
format using Winzip or other unzip program first. Most of these
additional ppm modules can be downloaded from ActiveState, but
AppConfig and Template should be obtained from OpenInteract using
the instructions on the Template Toolkit web site .
Note
You can find a list of modules at
http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or
http://www.activestate.com/PPMPackages/5.6plus
The syntax for ppm is: C:> ppm <modulename>
Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows
C:> ppm DBD-Mysql
Watch your capitalization!
ActiveState's 5.6Plus directory also contains an AppConfig ppm, so
you might see the following error when trying to install the
version at OpenInteract:
Error installing package 'AppConfig': Read a PPD for 'AppConfig',
but it is not intended for this build of Perl
(MSWin32-x86-multi-thread)
If so, download both the tarball and the ppd directly from
OpenInteract, then run ppm from within the same directory to which
you downloaded those files and install the package by referencing
the ppd file explicitly via in the install command, f.e.:
Example 4-2. Installing OpenInteract ppd Modules manually on
Microsoft Windows
install C:\AppConfig.ppd
4. Install MySQL for NT.
Note
You can download MySQL for Windows NT from MySQL.com . Some find it
helpful to use the WinMySqlAdmin utility, included with the download,
to set up the database.
5. Setup MySQL
a. C:> C:\mysql\bin\mysql -u root mysql
b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
"new_password" , above, indicates whatever password you wish
to use for your "root" user.
d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
IDENTIFIED BY 'bugs_password';
"bugs_password" , above, indicates whatever password you wish
to use for your "bugs" user.
e. mysql> FLUSH PRIVILEGES;
f. mysql> create database bugs;
g. mysql> exit;
h. C:> C:\mysql\bin\mysqladmin -u root -p reload
6. Edit checksetup.pl in your Bugzilla directory. Change this line:
my $webservergid =
getgrnam($my_webservergroup);
to
my $webservergid =
$my_webservergroup;
or the name of the group you wish to own the files explicitly:
my $webservergid =
'Administrators'
7. Run checksetup.pl from the Bugzilla directory.
8. Edit localconfig to suit your requirements. Set $db_pass to your
"bugs_password" from step 5.d , and $webservergroup to "8" .
Note
Not sure on the "8" for $webservergroup above. If it's wrong, please
send corrections.
9. Edit defparams.pl to suit your requirements. Particularly, set
DefParam("maintainer") and DefParam("urlbase") to match your
install.
Note
This is yet another step I'm not sure of, since the maintainer of this
documentation does not maintain Bugzilla on NT. If you can confirm or
deny that this step is required, please let me know.
10.
Note
There are several alternatives to Sendmail that will work on Win32.
The one mentioned here is a suggestion , not a requirement. Some other
mail packages that can work include BLAT , Windmail , Mercury Sendmail
, and the CPAN Net::SMTP Perl module (available in .ppm). Every option
requires some hacking of the Perl scripts for Bugzilla to make it
work. The option here simply requires the least.
1. Download NTsendmail, available from www.ntsendmail.com . You
must have a "real" mail server which allows you to relay off
it in your $ENV{"NTsendmail"} (which you should probably
place in globals.pl)
2. Put ntsendmail.pm into your .\perl\lib directory.
3. Add to globals.pl:
# these settings configure the NTsendmail
process use NTsendmail;
$ENV{"NTsendmail"}="your.smtpserver.box";
$ENV{"NTsendmail_debug"}=1;
$ENV{"NTsendmail_max_tries"}=5;
Note
Some mention to also edit $db_pass in globals.pl to be your
"bugs_password" . Although this may get you around some problem
authenticating to your database, since globals.pl is not normally
restricted by .htaccess , your database password is exposed to whoever
uses your web server.
4. Find and comment out all occurences of " open(SENDMAIL " in
your Bugzilla directory. Then replace them with:
# new sendmail functionality my $mail=new
NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
$to=$login; my $subject=$urlbase;
$mail->send($from,$to,$subject,$msg);
Note
4.3.1. Microsoft Windows
Making Bugzilla work on windows is still a very painful processes. The
Bugzilla Team is working to make it easier, but that goal is not
considered a top priority. If you wish to run Bugzilla, we still
recommend doing so on a Unix based system such as GNU/Linux. As of
this writing, all members of the Bugzilla team and all known large
installations run on Unix based systems.
If after hearing all that, you have enough pain tolerance to attempt
installing Bugzilla on Win32, here are some pointers. Because this is
a development version of the guide, these instructions are subject to
change without notice. In fact, the Bugzilla Team hopes they do as we
would like to have Bugzilla resonabally close to "out of the box"
compatibility by the 2.18 release.
_________________________________________________________________
Some have found success using the commercial product, Windmail . You
could try replacing your sendmail calls with:
open SENDMAIL,
"|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
mail.log";
4.3.1.1. Win32 Perl
or something to that effect.
11. Change all references in all files from processmail to
processmail.pl , and rename processmail to processmail.pl .
Perl for Windows can be obtained from ActiveState. You should be able
to find a compiled binary at
http://aspn.activestate.com/ASPN/Downloads/ActivePerl/.
_________________________________________________________________
Note
4.3.1.2. Perl Modules on Win32
Many think this may be a change we want to make for main-tree
Bugzilla. It's painless for the UNIX folks, and will make the Win32
people happier.
Bugzilla on Windows requires the same perl modules found in Section
4.1.2. The main difference is that windows uses ppm instead of CPAN.
C:\perl> ppm <module name>
Note
Some people have suggested using the Net::SMTP Perl module instead of
NTsendmail or the other options listed here. You can change
processmail.pl to make this work.
my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
ver
$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
$smtp->to($tolist); # recipient's address
$smtp->data(); # Start the mail
$smtp->datasend($msg);
$smtp->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist";
}
here is a test mail program for Net::SMTP:
use Net::SMTP;
my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
=> 1, ); # connect to SMTP server
$smtp->auth;
$smtp->mail('you@yourcompany.com');# use the sender's adress
here
$smtp->to('someotherAddress@someotherdomain.com'); #
recipient's address
$smtp->data(); # Start the mail
$smtp->datasend('test');
$smtp->dataend(); # Finish sending the mail
$smtp->quit; # Close the SMTP connection
exit;
12.
The above syntax should work for all modules with the exception of
Template Toolkit. The Template Toolkit website suggests using the
instructions on OpenInteract's website.
Note
This step is optional if you are using IIS or another web server which
only decides on an interpreter based upon the file extension (.pl),
rather than the "shebang" line (#/usr/bonsaitools/bin/perl)
Modify the path to perl on the first line (#!) of all files to
point to your Perl installation, and add "perl" to the beginning
of all Perl system calls that use a perl script as an argument.
This may take you a while. There is a "setperl.csh" utility to
speed part of this procedure, available in the Useful Patches and
Utilities for Bugzilla section of The Bugzilla Guide. However, it
requires the Cygwin GNU-compatible environment for Win32 be set up
in order to work. See http://www.cygwin.com/ for details on
obtaining Cygwin.
13. Modify the invocation of all system() calls in all perl scripts in
your Bugzilla directory. You should specify the full path to perl
for each system() call. For instance, change this line in
processmail:
A complete list of modules that can be installed using ppm can be
found at http://www.activestate.com/PPMPackages/5.6plus.
_________________________________________________________________
system ("./processmail",@ARGLIST);
</programlisting> to
<programlisting>
system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
4.3.1.3. Code changes required to run on win32
Unfortunately, Bugzilla still doesn't run "out of the box" on Windows.
There is work in progress to make this easier, but until that happens
code will have to be modified. This section is an attempt to list the
required changes. It is an attempt to be all inclusive, but there may
be other changes required. If you find something is missing, please
file a bug in Bugzilla Documentation.
_________________________________________________________________
4.3.1.3.1. Changes to checksetup.pl
Tip
In checksetup.pl, the line reading:
my $mysql_binaries = `which mysql`;
If you are using IIS or Personal Web Server, you must add cgi
relationships to Properties -> Home directory (tab) -> Application
Settings (section) -> Configuration (button), such as:
to
my $mysql_binaries = "D:\\mysql\\bin\\mysql";
.cgi to: <perl install directory>\perl.exe %s
%s .pl to: <perl install directory>\perl.exe %s %s
GET,HEAD,POST
And you'll also need to change:
my $webservergid = getgrnam($my_webservergroup)
Change the path to Perl to match your install, of course.
to
my $webservergid = '8'
_________________________________________________________________
4.3.2. Additional Windows Tips
Tip
From Andrew Pearson:
4.3.1.3.2. Making mail work
You can make Bugzilla work with Personal Web Server for Windows 98
and higher, as well as for IIS 4.0. Microsoft has information
available at
http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP
The easiest way to get mail working is to use the mail patches on bug
124174. With any luck, this patch will receive the required reviews
and integrated into the main Bugzilla distribution very soon. Until
that happens, there's at least one report of this patch working well
on Windows.
_________________________________________________________________
Basically you need to add two String Keys in the registry at the
following location:
4.3.1.3.3. System Calls
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramete
rs\ScriptMap
In order to get system calls to work on win32's perl, you need to tell
the windows shell what interpreter to use. This is done by changing
the system calls. You will need to search all of Bugzilla's code for
system calls. To tell perl your interpreter, it needs to be the first
argument to the system call. For example, you'll need to change:
system("./processmail", $id, $exporter);
The keys should be called ".pl" and ".cgi", and both should have a
value something like: c:/perl/bin/perl.exe "%s" "%s"
with
system("C:\\perl\\bin\\perl", "processmail", $id, $exporter);
The KB article only talks about .pl, but it goes into more detail
and provides a perl test script.
Notice that the ./ is also removed.
Tip
If attempting to run Bugzilla 2.12 or older, you will need to remove
encrypt() calls from the Perl source. This is not necessary for
Bugzilla 2.13 and later, which includes the current release, Bugzilla
&bz-ver;.
The grep command is very helpful in finding these system calls,
assuming you have the cygwin utilities.
_________________________________________________________________
Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12
or earlier
4.3.1.4. Serving the web pages
Replace this:
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
$enteredcryptpwd = FetchOneColumn();
As is the case on Unix based systems, any web server should be able to
handle Bugzilla; however, the Bugzilla Team still recommends Apache
whenever asked. No matter what web server you choose, be sure to pay
attention to the security notes in Section 5.6. More information on
configuring specific web servers can be found in Section 4.4.
with this:
my $enteredcryptpwd = $enteredpwd
Note
in cgi.pl.
If using Apache on windows, you can set the ScriptInterpreterSource
directive in your Apache config, if you don't do this, you'll have to
modify the first line of every script to contain your path to perl
instead of /usr/bonsaitools/bin/perl.
_________________________________________________________________
4.4. Mac OS X Installation Notes
4.3.2. Mac OS X
There are a lot of common libraries and utilities out there that Apple
did not include with Mac OS X, but which run perfectly well on it. The
......@@ -2043,7 +1453,7 @@ SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
The easiest way to get a lot of these is with a program called Fink,
which is similar in nature to the CPAN installer, but installs common
GNU utilities. Fink is available from
<http://sourceforge.net/projects/fink/>.
http://sourceforge.net/projects/fink/.
Follow the instructions for setting up Fink. Once it's installed,
you'll want to run the following as root: fink install gd
......@@ -2075,6 +1485,149 @@ SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
And don't forget to run exit to get back to CPAN.
_________________________________________________________________
4.4. HTTP Server Configuration
The Bugzilla Team recommends Apache when using Bugzilla, however, any
web server that can be configured to run CGI scripts should be able to
handle Bugzilla. No matter what web server you choose, but especially
if you choose something other than Apache, you should be sure to read
Section 5.6.
The plan for this section is to eventually document the specifics of
how to lock down permissions on individual web servers.
_________________________________________________________________
4.4.1. Apache httpd
As mentioned above, the Bugzilla Team recommends Apache for use with
Bugzilla. You will have to make sure that Apache is properly
configured to run the Bugzilla CGI scripts. You also need to make sure
that the .htaccess files created by ./checksetup.pl (shown in Example
4-1 for the curious) are allowed to override Apache's normal access
permissions or else important password information may be exposed to
the Internet.
Many Apache installations are not configured to run scripts anywhere
but in the cgi-bin directory; however, we recommend that Bugzilla not
be installed in the cgi-bin, otherwise the static files such as images
and JavaScript will not work correctly. To allow scripts to run in the
normal web space, the following changes should be made to your
httpd.conf file.
To allow files with a .cgi extension to be run, make sure the
following line exists and is uncommented:
AddHandler cgi-script .cgi
To allow .htaccess files to override permissions and .cgi files to run
in the Bugzilla directory, make sure the following two lines are in a
Directory directive that applies to the Bugzilla directory on your
system (either the Bugzilla directory or one of its parents).
Options +ExecCGI
AllowOverride Limit
Note
For more information on Apache and its directives, see the glossary
entry on Apache.
Example 4-1. .htaccess files for Apache
$BUGZILLA_HOME/.htaccess
# don't allow people to retrieve non-cgi executable files or our private data
<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$>
deny from all
</FilesMatch>
<FilesMatch ^(localconfig.js|localconfig.rdf)$>
allow from all
</FilesMatch>
$BUGZILLA_HOME/data/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory; the only exception is duplicates.rdf, which is used by
# duplicates.xul and must be loadable over the web
deny from all
<Files duplicates.rdf>
allow from all
</Files>
$BUGZILLA_HOME/data/webdot
# Restrict access to .dot files to the public webdot server at research.att.com
# if research.att.com ever changed their IP, or if you use a different
# webdot server, you'll need to edit this
<FilesMatch ^[0-9]+\.dot$>
Allow from 192.20.225.10
Deny from all
</FilesMatch>
# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
# .map files
<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$>
Allow from all
</FilesMatch>
# And no directory listings, either.
Deny from all
$BUGZILLA_HOME/Bugzilla/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
$BUGZILLA_HOME/template/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
_________________________________________________________________
4.4.2. Microsoft Internet Information Services
If you need, or for some reason even want, to use Microsoft's Internet
Information Services or Personal Web Server you should be able to. You
will need to configure them to know how to run CGI scripts, however.
This is described in Microsoft Knowledge Base article Q245225 for
Internet Information Services and Q231998 for Personal Web Server.
Also, and this can't be stressed enough, make sure that files such as
localconfig and your data directory are secured as described in
Section 5.6.
_________________________________________________________________
4.4.3. AOL Server
Ben FrantzDale reported success using AOL Server with Bugzilla. He
reported his experience and what appears below is based on that.
AOL Server will have to be configured to run CGI scripts, please
consult the documentation that came with your server for more
information on how to do this.
Because AOL Server doesn't support .htaccess files, you'll have to
create a TCL script. You should create an
aolserver/modules/tcl/filter.tcl file (the filename shouldn't matter)
with the following contents (change /bugzilla/ to the web-based path
to your Bugzilla installation):
ns_register_filter preauth GET /bugzilla/localconfig filter_deny
ns_register_filter preauth GET /bugzilla/*.pl filter_deny
ns_register_filter preauth GET /bugzilla/localconfig filter_deny
ns_register_filter preauth GET /bugzilla/processmail filter_deny
ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
proc filter_deny { why } {
ns_log Notice "filter_deny"
return "filter_return"
}
Warning
This doesn't appear to account for everything mentioned in Section
5.6. In particular, it doesn't block access to the data or template
directories. It also doesn't account for the editor backup files that
were the topic of bug 186383, Bugtraq ID 6501, and a partial cause for
the 2.16.2 release.
_________________________________________________________________
4.5. Troubleshooting
This section gives solutions to common Bugzilla installation problems.
......@@ -2637,76 +2190,20 @@ Chapter 5. Administering Bugzilla
This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will be
able to take control of your Bugzilla installation.
On Apache, you can use .htaccess files to protect access to these
directories, as outlined in Bugs 57161 and 186383 for the
localconfig file, and Bug 65572 for adequate protection in your
data/ directory. Also, don't forget about the template/ and
Bugzilla/ directories and to allow access to the data/webdot
directory for the 192.20.225.10 IP address if you are using webdot
from research.att.com. The easiest way to accomplish this is to
set $create_htaccess to 1 in localconfig. However, the information
below is provided for those that want to know exactly what is
created.
Note the instructions which follow are Apache-specific. If you use
IIS, Netscape, or other non-Apache web servers, please consult
your system documentation for how to secure these files from being
transmitted to curious users.
$BUGZILLA_HOME/.htaccess
# don't allow people to retrieve non-cgi executable files or our private data
<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$>
deny from all
</FilesMatch>
<FilesMatch ^(localconfig.js|localconfig.rdf)$>
allow from all
</FilesMatch>
$BUGZILLA_HOME/data/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory; the only exception is duplicates.rdf, which is used by
# duplicates.xul and must be loadable over the web
deny from all
<Files duplicates.rdf>
allow from all
</Files>
$BUGZILLA_HOME/data/webdot
# Restrict access to .dot files to the public webdot server at research.att.com
# if research.att.com ever changed their IP, or if you use a different
# webdot server, you'll need to edit this
<FilesMatch ^[0-9]+\.dot$>
Allow from 192.20.225.10
Deny from all
</FilesMatch>
# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
# .map files
<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$>
Allow from all
</FilesMatch>
# And no directory listings, either.
Deny from all
$BUGZILLA_HOME/Bugzilla/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
$BUGZILLA_HOME/template/.htaccess
# nothing in this directory is retrievable unless overriden by an .htaccess
# in a subdirectory
deny from all
On Apache, you can use .htaccess files to protect access to these
directories, as outlined in Bugs 57161 and 186383 for the
localconfig file, and Bug 65572 for adequate protection in your
data/ directory. Also, don't forget about the template/ and
Bugzilla/ directories and to allow access to the data/webdot
directory for the 192.20.225.10 IP address if you are using webdot
from research.att.com. The easiest way to accomplish this is to
set $create_htaccess to 1 in localconfig. However, the information
below is provided for those that want to know exactly what is
created.
FIX ME BEFORE RELEASE!!!!! Note the instructions which follow are
Apache-specific. If you use IIS, Netscape, or other non-Apache web
servers, please consult your system documentation for how to
secure these files from being transmitted to curious users.
_________________________________________________________________
5.7. Template Customization
......@@ -4351,105 +3848,468 @@ C.2. Command-line Bugzilla Queries
(post-templatisation.). There are three files - query.conf, buglist
and bugs.
query.conf contains the mapping from options to field names and
comparison types. Quoted option names are "grepped" for, so it should
be easy to edit this file. Comments (#) have no effect; you must make
sure these lines do not contain any quoted "option".
query.conf contains the mapping from options to field names and
comparison types. Quoted option names are "grepped" for, so it should
be easy to edit this file. Comments (#) have no effect; you must make
sure these lines do not contain any quoted "option".
buglist is a shell script which submits a Bugzilla query and writes
the resulting HTML page to stdout. It supports both short options,
(such as "-Afoo" or "-Rbar") and long options (such as
"--assignedto=foo" or "--reporter=bar"). If the first character of an
option is not "-", it is treated as if it were prefixed with
"--default=".
The column list is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list bugs
in buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
in your cookies file to see your current COLUMNLIST setting.
bugs is a simple shell script which calls buglist and extracts the bug
numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list
into a working link if any bugs are found. Counting bugs is easy. Pipe
the results through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
Akkana Peck says she has good results piping buglist output through
w3m -T text/html -dump
_________________________________________________________________
Appendix D. Bugzilla Variants and Competitors
I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of
what I wanted to discuss. Rather than quote it in its entirety, I'll
simply refer you here: http://linas.org/linux/pm.html
_________________________________________________________________
D.1. Red Hat Bugzilla
Red Hat's old fork of Bugzilla which was based on version 2.8 is now
obsolete. The newest version in use is based on version 2.17.1 and is
in the process of being integrated into the main Bugzilla source tree.
The back-end is modified to work with PostgreSQL instead of MySQL and
they have custom templates to get their desired look and feel, but
other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put
forth a great deal of effort to make sure that the changes he made
could be integrated back into the main tree. Bug 98304 exists to track
this integration.
URL: http://bugzilla.redhat.com/bugzilla/
This section last updated 24 Dec 2002
_________________________________________________________________
D.2. Loki Bugzilla (Fenris)
Fenris was a fork from Bugzilla made by Loki Games; when Loki went
into receivership, it died. While Loki's other code lives on, its
custodians recommend Bugzilla for future bug-tracker deployments.
This section last updated 27 Jul 2002
_________________________________________________________________
D.3. Issuezilla
Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of
bug-tracking at tigris.org is their Java-based bug-tracker, Scarab.
This section last updated 27 Jul 2002
_________________________________________________________________
D.4. Scarab
Scarab is a new open source bug-tracking system built using Java
Servlet technology. It is currently at version 1.0 beta 13.
URL: http://scarab.tigris.org
This section last updated 18 Jan 2003
_________________________________________________________________
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as such
through the "jobs" functionality.
URL: http://www.perforce.com/perforce/technotes/note052.html
This section last updated 27 Jul 2002
_________________________________________________________________
D.6. SourceForge
SourceForge is a way of coordinating geographically distributed free
software and open source projects over the Internet. It has a built-in
bug tracker, but it's not highly thought of.
URL: http://www.sourceforge.net
This section last updated 27 Jul 2002
_________________________________________________________________
Appendix E. GNU Free Documentation License
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy
and distribute verbatim copies of this license document, but
changing it is not allowed.
_________________________________________________________________
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone
the effective freedom to copy and redistribute it, with or without
modifying it, either commercially or noncommercially. Secondarily,
this License preserves for the author and publisher a way to get
credit for their work, while not being considered responsible for
modifications made by others.
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals; it
can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
_________________________________________________________________
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed
under the terms of this License. The "Document", below, refers to any
such manual or work. Any member of the public is a licensee, and is
addressed as "you".
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (For example, if the Document is
in part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The "Invariant Sections" are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License.
The "Cover Texts" are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License.
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, whose contents can be viewed and edited directly and
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup has been designed to thwart or discourage
subsequent modification by readers is not Transparent. A copy that is
not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
or XML using a publicly available DTD, and standard-conforming simple
HTML designed for human modification. Opaque formats include
PostScript, PDF, proprietary formats that can be read and edited only
by proprietary word processors, SGML or XML for which the DTD and/or
processing tools are not generally available, and the
machine-generated HTML produced by some word processors for output
purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, "Title Page" means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
_________________________________________________________________
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no
other conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
_________________________________________________________________
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
buglist is a shell script which submits a Bugzilla query and writes
the resulting HTML page to stdout. It supports both short options,
(such as "-Afoo" or "-Rbar") and long options (such as
"--assignedto=foo" or "--reporter=bar"). If the first character of an
option is not "-", it is treated as if it were prefixed with
"--default=".
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:
The column list is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list bugs
in buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
in your cookies file to see your current COLUMNLIST setting.
A. 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.
B. 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).
C. State on the Title page the name of the publisher of the Modified
Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. 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.
G. Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's license
notice.
H. Include an unaltered copy of this License.
I. 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.
J. 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.
K. 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.
L. 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.
M. Delete any section entitled "Endorsements". Such a section may not
be included in the Modified Version.
N. Do not retitle any existing section as "Endorsements" or to
conflict in title with any Invariant Section.
bugs is a simple shell script which calls buglist and extracts the bug
numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list
into a working link if any bugs are found. Counting bugs is easy. Pipe
the results through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
Akkana Peck says she has good results piping buglist output through
w3m -T text/html -dump
_________________________________________________________________
You may add a section entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
Appendix D. Bugzilla Variants and Competitors
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.
I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of
what I wanted to discuss. Rather than quote it in its entirety, I'll
simply refer you here: http://linas.org/linux/pm.html
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.
_________________________________________________________________
D.1. Red Hat Bugzilla
5. COMBINING DOCUMENTS
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.
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.
URL: http://bugzilla.redhat.com/bugzilla/
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.
This section last updated 24 Dec 2002
In the combination, you must combine any sections entitled "History"
in the various original documents, forming one section entitled
"History"; likewise combine any sections entitled "Acknowledgements",
and any sections entitled "Dedications". You must delete all sections
entitled "Endorsements."
_________________________________________________________________
D.2. Loki Bugzilla (Fenris)
6. COLLECTIONS OF DOCUMENTS
Fenris was a fork from Bugzilla made by Loki Games; when Loki went
into receivership, it died. While Loki's other code lives on, its
custodians recommend Bugzilla for future bug-tracker deployments.
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.
This section last updated 27 Jul 2002
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert a
copy of this License into the extracted document, and follow this
License in all other respects regarding verbatim copying of that
document.
_________________________________________________________________
D.3. Issuezilla
7. AGGREGATION WITH INDEPENDENT WORKS
Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of
bug-tracking at tigris.org is their Java-based bug-tracker, Scarab.
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, does not as a whole count as a Modified Version
of the Document, provided no compilation copyright is claimed for the
compilation. Such a compilation is called an "aggregate", and this
License does not apply to the other self-contained works thus compiled
with the Document, on account of their being thus compiled, if they
are not themselves derivative works of the Document.
This section last updated 27 Jul 2002
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one quarter
of the entire aggregate, the Document's Cover Texts may be placed on
covers that surround only the Document within the aggregate. Otherwise
they must appear on covers around the whole aggregate.
_________________________________________________________________
D.4. Scarab
8. TRANSLATION
Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.
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.
_________________________________________________________________
URL: http://scarab.tigris.org
9. TERMINATION
This section last updated 27 Jul 2002
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt
to copy, modify, sublicense or distribute the Document is void, and
will automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
_________________________________________________________________
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as such
through the "jobs" functionality.
10. FUTURE REVISIONS OF THIS LICENSE
URL: http://www.perforce.com/perforce/technotes/note052.html
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/ .
This section last updated 27 Jul 2002
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
_________________________________________________________________
D.6. SourceForge
How to use this License for your documents
SourceForge is a way of coordinating geographically distributed free
software and open source projects over the Internet. It has a built-in
bug tracker, but it's not highly thought of.
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
URL: http://www.sourceforge.net
Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
distribute and/or modify this document under the terms of the GNU
Free Documentation License, Version 1.1 or any later version
published by the Free Software Foundation; with the Invariant
Sections being LIST THEIR TITLES, with the Front-Cover Texts being
LIST, and with the Back-Cover Texts being LIST. A copy of the
license is included in the section entitled "GNU Free Documentation
License".
This section last updated 27 Jul 2002
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.
Glossary
......@@ -4473,6 +4333,30 @@ A
fact that it was "a patchy" version of the original NCSA
world-wide-web server.
Useful Directives when configuring Bugzilla
AddHandler
Tell Apache that it's OK to run CGI scripts.
AllowOverride, Options
These directives are used to tell Apache many things
about the directory they apply to. For Bugzilla's
purposes, we need them to allow script execution and
.htaccess overrides.
DirectoryIndex
Used to tell Apache what files are indexes. If you can
not add index.cgi to the list of valid files, you'll need
to set $index_html to 1 in localconfig so ./checksetup.pl
will create an index.html that redirects to index.cgi.
ScriptInterpreterSource
Used when running Apache on windows so the shebang line
doesn't have to be changed in every Bugzilla script.
For more information about how to configure Apache for
Bugzilla, see Section 4.4.1.
B
Bug
......@@ -4491,6 +4375,11 @@ B
Bugzilla is the world-leading free software bug tracking
system.
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.
Component
A Component is a subsection of a Product. It should be a narrow
category, tailored to your organization. All Products must
......@@ -4512,12 +4401,19 @@ D
mysqld, the MySQL server, and apache, a web server, are
generally run as daemons.
G
Groups
The word "Groups" has a very special meaning to Bugzilla.
Bugzilla's main security mechanism comes by placing users in
groups, and assigning those groups certain privileges to view
bugs in particular Products in the Bugzilla database.
J
JavaScript
JavaScript is cool, we should talk about it.
M
mysqld
......@@ -4576,6 +4472,12 @@ T
to declare by which milestone a bug will be fixed, or an
enhancement will be implemented.
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.
Z
Zarro Boogs Found
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment