Skip to content

bugzilla
bugzilla
You need to sign in or sign up before continuing.
Commit d7f38125 authored by jake%acutex.net's avatar jake%acutex.net
Browse files
Options

Latest version of compiled docs (picking up recent SGML changes).

parent ad00e1f0
Show whitespace changes
Inline Side-by-side
Showing with 5731 additions and 2596 deletions
docs/html/Bugzilla-Guide.html
View file @ d7f38125
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/html/about.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Purpose and Scope of this Guide" TITLE="Purpose and Scope of this Guide"
HREF="aboutthisguide.html"></HEAD HREF="aboutthisguide.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="aboutthisguide.html" ...@@ -63,10 +63,10 @@ HREF="aboutthisguide.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="ABOUT" NAME="about"
>Chapter 1. About This Guide</A >Chapter 1. About This Guide</A
></H1 ></H1
><DIV ><DIV
......
docs/html/aboutthisguide.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Copyright Information" TITLE="Copyright Information"
HREF="copyright.html"></HEAD HREF="copyright.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,28 +66,28 @@ HREF="copyright.html" ...@@ -66,28 +66,28 @@ HREF="copyright.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="ABOUTTHISGUIDE" NAME="aboutthisguide"
>1.1. Purpose and Scope of this Guide</A >1.1. Purpose and Scope of this Guide</A
></H1 ></H1
><P ><P
> This document was started on September 17, 2000 by Matthew P. >&#13; This document was started on September 17, 2000 by Matthew P.
Barnson after a great deal of procrastination updating the Barnson after a great deal of procrastination updating the
Bugzilla FAQ, which I left untouched for nearly half a year. Bugzilla FAQ, which I left untouched for nearly half a year.
After numerous complete rewrites and reformatting, it is the After numerous complete rewrites and reformatting, it is the
document you see today. document you see today.
</P </P
><P ><P
> Bugzilla is simply the best piece of bug-tracking software the >&#13; Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration, comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system. maintenance, and use of the Bugzilla bug-tracking system.
</P </P
><P ><P
> This release of the Bugzilla Guide is the >&#13; This release of the Bugzilla Guide is the
<EM <EM
>2.14</EM >2.14</EM
> release. It is so named that it > release. It is so named that it
...@@ -108,7 +108,7 @@ NAME="ABOUTTHISGUIDE" ...@@ -108,7 +108,7 @@ NAME="ABOUTTHISGUIDE"
developers, and those who enjoy a lot of pain. developers, and those who enjoy a lot of pain.
</P </P
><P ><P
> Newer revisions of the Bugzilla Guide follow the numbering >&#13; Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at conventions of the main-tree Bugzilla releases, available at
<A <A
HREF="http://www.mozilla.org/projects/bugzilla" HREF="http://www.mozilla.org/projects/bugzilla"
...@@ -123,13 +123,13 @@ TARGET="_top" ...@@ -123,13 +123,13 @@ TARGET="_top"
Got it? Good. Got it? Good.
</P </P
><P ><P
> I wrote this in response to the enormous demand for decent >&#13; I wrote this in response to the enormous demand for decent
Bugzilla documentation. I have incorporated instructions from Bugzilla documentation. I have incorporated instructions from
the Bugzilla README, Frequently Asked Questions, Database Schema the Bugzilla README, Frequently Asked Questions, Database Schema
Document, and various mailing lists to create it. Chances are, Document, and various mailing lists to create it. Chances are,
there are glaring errors in this documentation; please contact there are glaring errors in this documentation; please contact
<TT <TT
CLASS="EMAIL" CLASS="email"
>&#60;<A >&#60;<A
HREF="mailto:barnboy@trilobyte.net" HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A >barnboy@trilobyte.net</A
......
docs/html/administration.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Post-Installation Checklist" TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"></HEAD HREF="postinstall-check.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="postinstall-check.html" ...@@ -63,10 +63,10 @@ HREF="postinstall-check.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="ADMINISTRATION" NAME="administration"
>Chapter 4. Administering Bugzilla</A >Chapter 4. Administering Bugzilla</A
></H1 ></H1
><DIV ><DIV
...@@ -90,34 +90,34 @@ HREF="useradmin.html" ...@@ -90,34 +90,34 @@ HREF="useradmin.html"
><DL ><DL
><DT ><DT
>4.2.1. <A >4.2.1. <A
HREF="useradmin.html#DEFAULTUSER" HREF="useradmin.html#defaultuser"
>Creating the Default User</A >Creating the Default User</A
></DT ></DT
><DT ><DT
>4.2.2. <A >4.2.2. <A
HREF="useradmin.html#MANAGEUSERS" HREF="useradmin.html#manageusers"
>Managing Other Users</A >Managing Other Users</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>4.2.2.1. <A >4.2.2.1. <A
HREF="useradmin.html#LOGIN" HREF="useradmin.html#login"
>Logging In</A >Logging In</A
></DT ></DT
><DT ><DT
>4.2.2.2. <A >4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS" HREF="useradmin.html#createnewusers"
>Creating new users</A >Creating new users</A
></DT ></DT
><DT ><DT
>4.2.2.3. <A >4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS" HREF="useradmin.html#disableusers"
>Disabling Users</A >Disabling Users</A
></DT ></DT
><DT ><DT
>4.2.2.4. <A >4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS" HREF="useradmin.html#modifyusers"
>Modifying Users</A >Modifying Users</A
></DT ></DT
></DL ></DL
...@@ -134,32 +134,32 @@ HREF="programadmin.html" ...@@ -134,32 +134,32 @@ HREF="programadmin.html"
><DL ><DL
><DT ><DT
>4.3.1. <A >4.3.1. <A
HREF="programadmin.html#PRODUCTS" HREF="programadmin.html#products"
>Products</A >Products</A
></DT ></DT
><DT ><DT
>4.3.2. <A >4.3.2. <A
HREF="programadmin.html#COMPONENTS" HREF="programadmin.html#components"
>Components</A >Components</A
></DT ></DT
><DT ><DT
>4.3.3. <A >4.3.3. <A
HREF="programadmin.html#VERSIONS" HREF="programadmin.html#versions"
>Versions</A >Versions</A
></DT ></DT
><DT ><DT
>4.3.4. <A >4.3.4. <A
HREF="programadmin.html#MILESTONES" HREF="programadmin.html#milestones"
>Milestones</A >Milestones</A
></DT ></DT
><DT ><DT
>4.3.5. <A >4.3.5. <A
HREF="programadmin.html#VOTING" HREF="programadmin.html#voting"
>Voting</A >Voting</A
></DT ></DT
><DT ><DT
>4.3.6. <A >4.3.6. <A
HREF="programadmin.html#GROUPS" HREF="programadmin.html#groups"
>Groups and Group Security</A >Groups and Group Security</A
></DT ></DT
></DL ></DL
...@@ -173,11 +173,11 @@ HREF="security.html" ...@@ -173,11 +173,11 @@ HREF="security.html"
></DIV ></DIV
><FONT ><FONT
COLOR="RED" COLOR="RED"
> Or, I just got this cool thing installed. Now what the heck do I >&#13; Or, I just got this cool thing installed. Now what the heck do I
do with it? do with it?
</FONT </FONT
><P ><P
> So you followed <SPAN >&#13; So you followed <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"<A >"<A
HREF="installation.html" HREF="installation.html"
......
docs/html/bonsai.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="CVS" TITLE="CVS"
HREF="cvs.html"></HEAD HREF="cvs.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="cvs.html" ...@@ -66,11 +66,11 @@ HREF="cvs.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BONSAI" NAME="bonsai"
>5.1. Bonsai</A >5.1. Bonsai</A
></H1 ></H1
><P ><P
......
docs/html/bsdinstall.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Installation General Notes" TITLE="Installation General Notes"
HREF="geninstall.html"></HEAD HREF="geninstall.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="geninstall.html" ...@@ -66,15 +66,15 @@ HREF="geninstall.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BSDINSTALL" NAME="bsdinstall"
>3.4. BSD Installation Notes</A >3.4. BSD Installation Notes</A
></H1 ></H1
><P ><P
> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please >&#13; For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
consult <A consult <A
HREF="osx.html" HREF="osx.html"
>Section 3.3</A >Section 3.3</A
......
docs/html/bzhacking.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="GNU Free Documentation License" TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD HREF="gfdl.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,26 +66,26 @@ HREF="gfdl.html" ...@@ -66,26 +66,26 @@ HREF="gfdl.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BZHACKING" NAME="bzhacking"
>D.5. Hacking Bugzilla</A >D.5. Hacking Bugzilla</A
></H1 ></H1
><P ><P
> The following is a guide for reviewers when checking code into Bugzilla's >&#13; The following is a guide for reviewers when checking code into Bugzilla's
CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla, CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,
you should follow the rules and style conventions below. Any code that you should follow the rules and style conventions below. Any code that
does not adhere to these basic rules will not be added to Bugzilla's does not adhere to these basic rules will not be added to Bugzilla's
codebase. codebase.
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN2495" NAME="AEN2504"
>D.5.1. Things that have caused problems and should be avoided</A >D.5.1. Things that have caused problems and should be avoided</A
></H2 ></H2
><P ><P
...@@ -94,25 +94,25 @@ NAME="AEN2495" ...@@ -94,25 +94,25 @@ NAME="AEN2495"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Usage of variables in Regular Expressions >&#13; Usage of variables in Regular Expressions
</P </P
><P ><P
> It is very important that you don't use a variable in a regular >&#13; It is very important that you don't use a variable in a regular
expression unless that variable is supposed to contain an expression. expression unless that variable is supposed to contain an expression.
This especially applies when using grep. You should use: This especially applies when using grep. You should use:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="90%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>grep ($_ eq $value, @array); >&#13;grep ($_ eq $value, @array);
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -121,20 +121,20 @@ CLASS="PROGRAMLISTING" ...@@ -121,20 +121,20 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><P ><P
> -- NOT THIS -- >&#13; -- NOT THIS --
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="90%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>grep (/$value/, @array); >&#13;grep (/$value/, @array);
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -143,12 +143,12 @@ CLASS="PROGRAMLISTING" ...@@ -143,12 +143,12 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -163,9 +163,9 @@ ALT="Note"></TD ...@@ -163,9 +163,9 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you need to use a non-expression variable inside of an expression, be >&#13; If you need to use a non-expression variable inside of an expression, be
sure to quote it properly (using <TT sure to quote it properly (using <TT
CLASS="FUNCTION" CLASS="function"
>\Q..\E</TT >\Q..\E</TT
>). >).
</P </P
...@@ -177,68 +177,70 @@ CLASS="FUNCTION" ...@@ -177,68 +177,70 @@ CLASS="FUNCTION"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN2509" NAME="AEN2518"
>D.5.2. Coding Style for Bugzilla</A >D.5.2. Coding Style for Bugzilla</A
></H2 ></H2
><P ><P
> While it's true that not all of the code currently in Bugzilla adheres to >&#13; While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore, this (or any) styleguide, it is something that is being worked toward. Therefore,
we ask that all new code (submitted patches and new files) follow this guide we ask that all new code (submitted patches and new files) follow this guide
as closely as possible (if you're only changing 1 or 2 lines, you don't have as closely as possible (if you're only changing 1 or 2 lines, you don't have
to reformat the entire file :). to reformat the entire file :).
</P </P
><P ><P
> The Bugzilla development team has decided to adopt the perl style guide as >&#13; The Bugzilla development team has decided to adopt the perl style guide as
published by Larry Wall. This giude can be found in <SPAN published by Larry Wall. This giude can be found in <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Programming >"Programming
Perl"</SPAN Perl"</SPAN
> (the camel book) or by typing <B > (the camel book) or by typing <B
CLASS="COMMAND" CLASS="command"
>man perlstyle</B >man perlstyle</B
> at > at
your favorite shell prompt. your favorite shell prompt.
</P </P
><P ><P
> What appears below if a brief summary, please refer to the perl style >&#13; What appears below if a brief summary, please refer to the perl style
guide if you don't see your question covered here. guide if you don't see your question covered here. It is much better to submit
a patch which fails these criteria than no patch at all, but please try to meet
these minimum standards when submitting code to Bugzilla.
</P </P
><P ><P
></P ></P
><UL ><UL
><LI ><LI
><P ><P
> Whitespace >&#13; Whitespace
</P </P
><P ><P
> Bugzilla's prefered indentation is 4 spaces (no tabs, please). >&#13; Bugzilla's prefered indentation is 4 spaces (no tabs, please).
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Curly braces. >&#13; Curly braces.
</P </P
><P ><P
> The opening brace of a block should be on the same line as the statement >&#13; The opening brace of a block should be on the same line as the statement
that is causing the block and the closing brace should be at the same that is causing the block and the closing brace should be at the same
indentation level as that statement, for example: indentation level as that statement, for example:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="90%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>if ($var) { >&#13;if ($var) {
print "The variable is true"; print "The variable is true";
} }
else { else {
...@@ -252,20 +254,20 @@ else { ...@@ -252,20 +254,20 @@ else {
> >
</P </P
><P ><P
> -- NOT THIS -- >&#13; -- NOT THIS --
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="90%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>if ($var) >&#13;if ($var)
{ {
print "The variable is true"; print "The variable is true";
} }
...@@ -283,16 +285,27 @@ else ...@@ -283,16 +285,27 @@ else
></LI ></LI
><LI ><LI
><P ><P
> File Names >&#13; Cookies
</P
><P
>&#13; Bugzilla uses cookies to ease the user experience, but no new patches
should <EM
>require</EM
> user-side cookies.
</P
></LI
><LI
><P
>&#13; File Names
</P </P
><P ><P
> File names for bugzilla code and support documention should be legal across >&#13; File names for bugzilla code and support documention should be legal across
multiple platforms. <TT multiple platforms. <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>\ / : * ? " &#60; &#62;</TT >\ / : * ? " &#60; &#62;</TT
> >
and <TT and <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>|</TT >|</TT
> are all illegal characters for filenames > are all illegal characters for filenames
on various platforms. Also, file names should not have spaces in them as they on various platforms. Also, file names should not have spaces in them as they
...@@ -301,50 +314,111 @@ CLASS="COMPUTEROUTPUT" ...@@ -301,50 +314,111 @@ CLASS="COMPUTEROUTPUT"
></LI ></LI
><LI ><LI
><P ><P
> Variable Names >&#13; Javascript dependencies
</P
><P
>&#13; While Bugzilla uses Javascript to make the user experience easier, no patch
to Bugzilla should <EM
>require</EM
> Javascript.
</P
></LI
><LI
><P
>&#13; Patch Format
</P
><P
>&#13; All patches submitted for inclusion into Bugzilla should be in the form of a
<SPAN
CLASS="QUOTE"
>"unified diff"</SPAN
>. This comes from using <SPAN
CLASS="QUOTE"
>"diff -u"</SPAN
>
instead of simply <SPAN
CLASS="QUOTE"
>"diff"</SPAN
> when creating your patch. This will
result in quicker acceptance of the patch.
</P
></LI
><LI
><P
>&#13; Schema Changes
</P
><P
>&#13; If you make schema changes, you should modify <TT
CLASS="filename"
>sanitycheck.cgi</TT
>
to support the new schema. All referential columns should be checked.
</P
></LI
><LI
><P
>&#13; Taint Mode
</P
><P
>&#13; All new cgis must run in Taint mode (Perl taint and DBI taint), and existing cgi's
which run in taint mode must not have taint mode turned off.
</P
></LI
><LI
><P
>&#13; Templatization
</P
><P
>&#13; Patches to Bugzilla need to support templates so they do not force user interface choices
on Bugzilla administrators.
</P
></LI
><LI
><P
>&#13; Variable Names
</P </P
><P ><P
> If a variable is scoped globally (<TT >&#13; If a variable is scoped globally (<TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>$::variable</TT >$::variable</TT
>) >)
its name should be descriptive of what it contains. Local variables can be named its name should be descriptive of what it contains. Local variables can be named
a bit looser, provided the context makes their content obvious. For example, a bit looser, provided the context makes their content obvious. For example,
<TT <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>$ret</TT >$ret</TT
> could be used as a staging variable for a > could be used as a staging variable for a
routine's return value as the line <TT routine's return value as the line <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>return $ret;</TT >return $ret;</TT
> >
will make it blatantly obvious what the variable holds and most likely be shown will make it blatantly obvious what the variable holds and most likely be shown
on the same screen as <TT on the same screen as <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>my $ret = "";</TT >my $ret = "";</TT
>. >.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Cross Database Compatability >&#13; Cross Database Compatability
</P </P
><P ><P
> Bugzilla was originally written to work with MySQL and therefore took advantage >&#13; Bugzilla was originally written to work with MySQL and therefore took advantage
of some of its features that aren't contained in other RDBMS software. These of some of its features that aren't contained in other RDBMS software. These
should be avoided in all new code. Examples of these features are enums and should be avoided in all new code. Examples of these features are enums and
<TT <TT
CLASS="FUNCTION" CLASS="function"
>encrypt()</TT >encrypt()</TT
>. >.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Cross Platform Compatability >&#13; Cross Platform Compatability
</P </P
><P ><P
> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is >&#13; While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
still the only officially supported platform) there are many who desire/need to still the only officially supported platform) there are many who desire/need to
run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive
not to make the lives of these people any more complicated and avoid doing things not to make the lives of these people any more complicated and avoid doing things
......
docs/html/cmdline.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The Quicksearch Utility" TITLE="The Quicksearch Utility"
HREF="quicksearch.html"></HEAD HREF="quicksearch.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,26 +66,26 @@ HREF="quicksearch.html" ...@@ -66,26 +66,26 @@ HREF="quicksearch.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CMDLINE" NAME="cmdline"
>D.3. Command-line Bugzilla Queries</A >D.3. Command-line Bugzilla Queries</A
></H1 ></H1
><P ><P
> Users can query Bugzilla from the command line using this suite >&#13; Users can query Bugzilla from the command line using this suite
of utilities. of utilities.
</P </P
><P ><P
> The query.conf file contains the mapping from options to field >&#13; The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped" names and comparison types. Quoted option names are "grepped"
for, so it should be easy to edit this file. Comments (#) have for, so it should be easy to edit this file. Comments (#) have
no effect; you must make sure these lines do not contain any no effect; you must make sure these lines do not contain any
quoted "option" quoted "option"
</P </P
><P ><P
> buglist is a shell script which submits a Bugzilla query and >&#13; buglist is a shell script which submits a Bugzilla query and
writes the resulting HTML page to stdout. It supports both writes the resulting HTML page to stdout. It supports both
short options, (such as "-Afoo" or "-Rbar") and long options short options, (such as "-Afoo" or "-Rbar") and long options
(such as "--assignedto=foo" or "--reporter=bar"). If the first (such as "--assignedto=foo" or "--reporter=bar"). If the first
...@@ -93,53 +93,53 @@ NAME="CMDLINE" ...@@ -93,53 +93,53 @@ NAME="CMDLINE"
prefixed with "--default=". prefixed with "--default=".
</P </P
><P ><P
> The columlist is taken from the COLUMNLIST environment variable. >&#13; The columlist is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list This is equivalent to the "Change Columns" option when you list
bugs in buglist.cgi. If you have already used Bugzilla, use bugs in buglist.cgi. If you have already used Bugzilla, use
<B <B
CLASS="COMMAND" CLASS="command"
>grep COLUMLIST ~/.netscape/cookies</B >grep COLUMLIST ~/.netscape/cookies</B
> to see > to see
your current COLUMNLIST setting. your current COLUMNLIST setting.
</P </P
><P ><P
> bugs is a simple shell script which calls buglist and extracts >&#13; bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
list into a working link if any bugs are found. Counting bugs is list into a working link if any bugs are found. Counting bugs is
easy. Pipe the results through <B easy. Pipe the results through <B
CLASS="COMMAND" CLASS="command"
>sed -e 's/,/ /g' | wc | >sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</B awk '{printf $2 "\n"}'</B
> >
</P </P
><P ><P
> Akkana says she has good results piping buglist output through >&#13; Akkana says she has good results piping buglist output through
<B <B
CLASS="COMMAND" CLASS="command"
>w3m -T text/html -dump</B >w3m -T text/html -dump</B
> >
</P </P
><DIV ><DIV
CLASS="PROCEDURE" CLASS="procedure"
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Download three files: >&#13; Download three files:
</P </P
><OL ><OL
CLASS="SUBSTEPS" CLASS="SUBSTEPS"
TYPE="a" TYPE="a"
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash$</TT >bash$</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>wget -O >wget -O
query.conf query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
...@@ -149,13 +149,13 @@ CLASS="COMMAND" ...@@ -149,13 +149,13 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash$</TT >bash$</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>wget -O >wget -O
buglist buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
...@@ -165,13 +165,13 @@ CLASS="COMMAND" ...@@ -165,13 +165,13 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>wget -O >wget -O
bugs bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
...@@ -183,15 +183,15 @@ CLASS="COMMAND" ...@@ -183,15 +183,15 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> Make your utilities executable: >&#13; Make your utilities executable:
<TT <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash$</TT >bash$</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>chmod u+x buglist bugs</B >chmod u+x buglist bugs</B
> >
</TT </TT
......
docs/html/contributors.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Feedback" TITLE="Feedback"
HREF="feedback.html"></HEAD HREF="feedback.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,19 +66,19 @@ HREF="feedback.html" ...@@ -66,19 +66,19 @@ HREF="feedback.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CONTRIBUTORS" NAME="contributors"
>1.6. Contributors</A >1.6. Contributors</A
></H1 ></H1
><P ><P
> Thanks go to these people for significant contributions to this >&#13; Thanks go to these people for significant contributions to this
documentation (in no particular order): documentation (in no particular order):
</P </P
><P ><P
> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron >&#13; Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
Teitelbaum, Jacob Steenhagen, Joe Robins Teitelbaum, Jacob Steenhagen, Joe Robins
</P </P
></DIV ></DIV
......
docs/html/conventions.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Using Bugzilla" TITLE="Using Bugzilla"
HREF="using.html"></HEAD HREF="using.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,18 +66,18 @@ HREF="using.html" ...@@ -66,18 +66,18 @@ HREF="using.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CONVENTIONS" NAME="conventions"
>1.9. Document Conventions</A >1.9. Document Conventions</A
></H1 ></H1
><P ><P
> This document uses the following conventions >&#13; This document uses the following conventions
</P </P
><DIV ><DIV
CLASS="INFORMALTABLE" CLASS="informaltable"
><A ><A
NAME="AEN129" NAME="AEN129"
></A ></A
...@@ -90,11 +90,11 @@ CLASS="CALSTABLE" ...@@ -90,11 +90,11 @@ CLASS="CALSTABLE"
><TR ><TR
><TH ><TH
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Descriptions</TH >Descriptions</TH
><TH ><TH
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Appearance</TH >Appearance</TH
></TR ></TR
></THEAD ></THEAD
...@@ -102,17 +102,17 @@ VALIGN="TOP" ...@@ -102,17 +102,17 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Warnings</TD >Warnings</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><DIV ><DIV
CLASS="CAUTION" CLASS="caution"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="CAUTION" CLASS="caution"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -138,17 +138,17 @@ VALIGN="TOP" ...@@ -138,17 +138,17 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Hint</TD >Hint</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -174,17 +174,17 @@ VALIGN="TOP" ...@@ -174,17 +174,17 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Notes</TD >Notes</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -210,17 +210,17 @@ VALIGN="TOP" ...@@ -210,17 +210,17 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Information requiring special attention</TD >Information requiring special attention</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -246,115 +246,115 @@ VALIGN="TOP" ...@@ -246,115 +246,115 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>File Names</TD >File Names</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>file.extension</TT >file.extension</TT
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Directory Names</TD >Directory Names</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>directory</TT >directory</TT
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Commands to be typed</TD >Commands to be typed</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><B ><B
CLASS="COMMAND" CLASS="command"
>command</B >command</B
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Applications Names</TD >Applications Names</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><SPAN ><SPAN
CLASS="APPLICATION" CLASS="application"
>application</SPAN >application</SPAN
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><I ><I
CLASS="FOREIGNPHRASE" CLASS="foreignphrase"
>Prompt</I >Prompt</I
> of users command under bash shell</TD > of users command under bash shell</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>bash$</TD >bash$</TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><I ><I
CLASS="FOREIGNPHRASE" CLASS="foreignphrase"
>Prompt</I >Prompt</I
> of root users command under bash shell</TD > of root users command under bash shell</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>bash#</TD >bash#</TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><I ><I
CLASS="FOREIGNPHRASE" CLASS="foreignphrase"
>Prompt</I >Prompt</I
> of user command under tcsh shell</TD > of user command under tcsh shell</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>tcsh$</TD >tcsh$</TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Environment Variables</TD >Environment Variables</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><TT ><TT
CLASS="ENVAR" CLASS="envar"
>VARIABLE</TT >VARIABLE</TT
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Emphasized word</TD >Emphasized word</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><EM ><EM
>word</EM >word</EM
></TD ></TD
...@@ -362,11 +362,11 @@ VALIGN="TOP" ...@@ -362,11 +362,11 @@ VALIGN="TOP"
><TR ><TR
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
>Code Example</TD >Code Example</TD
><TD ><TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="MIDDLE"
><TABLE ><TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
...@@ -376,12 +376,12 @@ WIDTH="100%" ...@@ -376,12 +376,12 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
><TT ><TT
CLASS="SGMLTAG" CLASS="sgmltag"
>&#60;para&#62;</TT >&#60;para&#62;</TT
>Beginning and end of paragraph<TT >Beginning and end of paragraph<TT
CLASS="SGMLTAG" CLASS="sgmltag"
>&#60;/para&#62;</TT >&#60;/para&#62;</TT
></PRE ></PRE
></FONT ></FONT
......
docs/html/copyright.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Disclaimer" TITLE="Disclaimer"
HREF="disclaimer.html"></HEAD HREF="disclaimer.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="disclaimer.html" ...@@ -66,11 +66,11 @@ HREF="disclaimer.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="COPYRIGHT" NAME="copyright"
>1.2. Copyright Information</A >1.2. Copyright Information</A
></H1 ></H1
><A ><A
...@@ -91,7 +91,7 @@ VALIGN="TOP" ...@@ -91,7 +91,7 @@ VALIGN="TOP"
WIDTH="80%" WIDTH="80%"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Permission is granted to copy, distribute and/or modify this >&#13; Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation document under the terms of the GNU Free Documentation
License, Version 1.1 or any later version published by the License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no Free Software Foundation; with no Invariant Sections, no
...@@ -111,7 +111,7 @@ COLSPAN="2" ...@@ -111,7 +111,7 @@ COLSPAN="2"
ALIGN="RIGHT" ALIGN="RIGHT"
VALIGN="TOP" VALIGN="TOP"
>--<SPAN >--<SPAN
CLASS="ATTRIBUTION" CLASS="attribution"
>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN >Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
></TD ></TD
><TD ><TD
...@@ -120,7 +120,7 @@ WIDTH="10%" ...@@ -120,7 +120,7 @@ WIDTH="10%"
></TR ></TR
></TABLE ></TABLE
><P ><P
> If you have any questions regarding this document, its >&#13; If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form, copyright, or publishing this document in non-electronic form,
please contact Matthew P. Barnson. please contact Matthew P. Barnson.
</P </P
......
docs/html/credits.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Contributors" TITLE="Contributors"
HREF="contributors.html"></HEAD HREF="contributors.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,21 +66,21 @@ HREF="contributors.html" ...@@ -66,21 +66,21 @@ HREF="contributors.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CREDITS" NAME="credits"
>1.5. Credits</A >1.5. Credits</A
></H1 ></H1
><P ><P
> The people listed below have made enormous contributions to the >&#13; The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts, creation of this Guide, through their dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community: contribution to the Bugzilla community:
</P </P
><P ><P
> <A >&#13; <A
HREF="mailto://terry@mozilla.org" HREF="mailto://terry@mozilla.org"
TARGET="_top" TARGET="_top"
>Terry Weissman</A >Terry Weissman</A
...@@ -89,7 +89,7 @@ TARGET="_top" ...@@ -89,7 +89,7 @@ TARGET="_top"
README upon which the UNIX installation documentation is largely based. README upon which the UNIX installation documentation is largely based.
</P </P
><P ><P
> <A >&#13; <A
HREF="mailto://tara@tequilarista.org" HREF="mailto://tara@tequilarista.org"
TARGET="_top" TARGET="_top"
>Tara >Tara
...@@ -98,7 +98,7 @@ TARGET="_top" ...@@ -98,7 +98,7 @@ TARGET="_top"
strong after Terry left Mozilla.org strong after Terry left Mozilla.org
</P </P
><P ><P
> <A >&#13; <A
HREF="mailto://dkl@redhat.com" HREF="mailto://dkl@redhat.com"
TARGET="_top" TARGET="_top"
>Dave Lawrence</A >Dave Lawrence</A
...@@ -108,7 +108,7 @@ TARGET="_top" ...@@ -108,7 +108,7 @@ TARGET="_top"
Hat Bugzilla" appendix Hat Bugzilla" appendix
</P </P
><P ><P
> <A >&#13; <A
HREF="mailto://endico@mozilla.org" HREF="mailto://endico@mozilla.org"
TARGET="_top" TARGET="_top"
>Dawn Endico</A >Dawn Endico</A
...@@ -117,7 +117,7 @@ TARGET="_top" ...@@ -117,7 +117,7 @@ TARGET="_top"
questions and arguments on irc.mozilla.org in #mozwebtools questions and arguments on irc.mozilla.org in #mozwebtools
</P </P
><P ><P
> Last but not least, all the members of the <A >&#13; Last but not least, all the members of the <A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools" HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
TARGET="_top" TARGET="_top"
> netscape.public.mozilla.webtools</A > netscape.public.mozilla.webtools</A
......
docs/html/cvs.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Perforce SCM" TITLE="Perforce SCM"
HREF="scm.html"></HEAD HREF="scm.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="scm.html" ...@@ -66,11 +66,11 @@ HREF="scm.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CVS" NAME="cvs"
>5.2. CVS</A >5.2. CVS</A
></H1 ></H1
><P ><P
...@@ -80,7 +80,7 @@ NAME="CVS" ...@@ -80,7 +80,7 @@ NAME="CVS"
certain that Bugzilla is not tied into one particular software certain that Bugzilla is not tied into one particular software
management package.</P management package.</P
><P ><P
> Follow the instructions in the FAQ for enabling Bugzilla e-mail >&#13; Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <SPAN your Bugzilla e-mail gateway with the subject of <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -92,13 +92,13 @@ CLASS="QUOTE" ...@@ -92,13 +92,13 @@ CLASS="QUOTE"
state. state.
</P </P
><P ><P
> There is also a project, based upon somewhat dated Bugzilla >&#13; There is also a project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to code, to integrate CVS and Bugzilla through CVS' ability to
email. Check it out at: email. Check it out at:
<A <A
HREF="http://homepages.kcbbs.gen.nz/~tonyg/" HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
TARGET="_top" TARGET="_top"
> http://homepages.kcbbs.gen.nz/~tonyg/</A >&#13; http://homepages.kcbbs.gen.nz/~tonyg/</A
>, under the >, under the
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
......
docs/html/database.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Database Schema Chart" TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD HREF="dbschema.html"></HEAD
><BODY ><BODY
CLASS="APPENDIX" CLASS="appendix"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="dbschema.html" ...@@ -63,10 +63,10 @@ HREF="dbschema.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="APPENDIX" CLASS="appendix"
><H1 ><H1
><A ><A
NAME="DATABASE" NAME="database"
>Appendix C. The Bugzilla Database</A >Appendix C. The Bugzilla Database</A
></H1 ></H1
><DIV ><DIV
...@@ -94,11 +94,11 @@ HREF="granttables.html" ...@@ -94,11 +94,11 @@ HREF="granttables.html"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -114,7 +114,7 @@ ALT="Note"></TD ...@@ -114,7 +114,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers? >&#13; This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?
</P </P
></TD ></TD
></TR ></TR
......
docs/html/dbdoc.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="MySQL Permissions & Grant Tables" TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"></HEAD HREF="granttables.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="granttables.html" ...@@ -66,15 +66,15 @@ HREF="granttables.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="DBDOC" NAME="dbdoc"
>C.2. MySQL Bugzilla Database Introduction</A >C.2. MySQL Bugzilla Database Introduction</A
></H1 ></H1
><P ><P
> This information comes straight from my life. I was forced to learn how >&#13; This information comes straight from my life. I was forced to learn how
Bugzilla organizes database because of nitpicky requests from users for tiny Bugzilla organizes database because of nitpicky requests from users for tiny
changes in wording, rather than having people re-educate themselves or changes in wording, rather than having people re-educate themselves or
figure out how to work our procedures around the tool. It sucks, but it can figure out how to work our procedures around the tool. It sucks, but it can
...@@ -82,7 +82,7 @@ NAME="DBDOC" ...@@ -82,7 +82,7 @@ NAME="DBDOC"
comes. comes.
</P </P
><P ><P
> So, here you are with your brand-new installation of Bugzilla. You've got >&#13; So, here you are with your brand-new installation of Bugzilla. You've got
MySQL set up, Apache working right, Perl DBI and DBD talking to the database MySQL set up, Apache working right, Perl DBI and DBD talking to the database
flawlessly. Maybe you've even entered a few test bugs to make sure email's flawlessly. Maybe you've even entered a few test bugs to make sure email's
working; people seem to be notified of new bugs and changes, and you can working; people seem to be notified of new bugs and changes, and you can
...@@ -92,12 +92,12 @@ NAME="DBDOC" ...@@ -92,12 +92,12 @@ NAME="DBDOC"
testers. testers.
</P </P
><P ><P
> What's the next thing you do? Outline a training strategy for your >&#13; What's the next thing you do? Outline a training strategy for your
development team, of course, and bring them up to speed on the new tool you've development team, of course, and bring them up to speed on the new tool you've
labored over for hours. labored over for hours.
</P </P
><P ><P
> Your first training session starts off very well! You have a captive >&#13; Your first training session starts off very well! You have a captive
audience which seems enraptured by the efficiency embodied in this thing called audience which seems enraptured by the efficiency embodied in this thing called
"Bugzilla". You are caught up describing the nifty features, how people can "Bugzilla". You are caught up describing the nifty features, how people can
save favorite queries in the database, set them up as headers and footers on save favorite queries in the database, set them up as headers and footers on
...@@ -106,12 +106,12 @@ NAME="DBDOC" ...@@ -106,12 +106,12 @@ NAME="DBDOC"
and rescue Jane from the clutches of Certain Death! and rescue Jane from the clutches of Certain Death!
</P </P
><P ><P
> But Certain Death speaks up -- a tiny voice, from the dark corners of the >&#13; But Certain Death speaks up -- a tiny voice, from the dark corners of the
conference room. "I have a concern," the voice hisses from the darkness, conference room. "I have a concern," the voice hisses from the darkness,
"about the use of the word 'verified'. "about the use of the word 'verified'.
</P </P
><P ><P
> The room, previously filled with happy chatter, lapses into reverential >&#13; The room, previously filled with happy chatter, lapses into reverential
silence as Certain Death (better known as the Vice President of Software silence as Certain Death (better known as the Vice President of Software
Engineering) continues. "You see, for two years we've used the word 'verified' Engineering) continues. "You see, for two years we've used the word 'verified'
to indicate that a developer or quality assurance engineer has confirmed that, to indicate that a developer or quality assurance engineer has confirmed that,
...@@ -120,7 +120,7 @@ NAME="DBDOC" ...@@ -120,7 +120,7 @@ NAME="DBDOC"
'approved' as soon as possible. To avoid confusion, of course." 'approved' as soon as possible. To avoid confusion, of course."
</P </P
><P ><P
> Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I >&#13; Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
don't think that would be a problem," You review the changes with Certain don't think that would be a problem," You review the changes with Certain
Death, and continue to jabber on, "no, it's not too big a change. I mean, we Death, and continue to jabber on, "no, it's not too big a change. I mean, we
have the source code, right? You know, 'Use the Source, Luke' and all that... have the source code, right? You know, 'Use the Source, Luke' and all that...
...@@ -128,20 +128,20 @@ NAME="DBDOC" ...@@ -128,20 +128,20 @@ NAME="DBDOC"
burbling, and boiling on a hot Jamaican sand dune... burbling, and boiling on a hot Jamaican sand dune...
</P </P
><P ><P
> Thus begins your adventure into the heart of Bugzilla. You've been forced >&#13; Thus begins your adventure into the heart of Bugzilla. You've been forced
to learn about non-portable enum() fields, varchar columns, and tinyint to learn about non-portable enum() fields, varchar columns, and tinyint
definitions. The Adventure Awaits You! definitions. The Adventure Awaits You!
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN2331" NAME="AEN2340"
>C.2.1. Bugzilla Database Basics</A >C.2.1. Bugzilla Database Basics</A
></H2 ></H2
><P ><P
> If you were like me, at this point you're totally clueless >&#13; If you were like me, at this point you're totally clueless
about the internals of MySQL, and if it weren't for this about the internals of MySQL, and if it weren't for this
executive order from the Vice President you couldn't care less executive order from the Vice President you couldn't care less
about the difference between a <SPAN about the difference between a <SPAN
...@@ -165,24 +165,24 @@ TARGET="_top" ...@@ -165,24 +165,24 @@ TARGET="_top"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> To connect to your database: >&#13; To connect to your database:
</P </P
><P ><P
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
>mysql</B >mysql</B
><TT ><TT
CLASS="PARAMETER" CLASS="parameter"
><I ><I
>-u root</I >-u root</I
></TT ></TT
> >
</P </P
><P ><P
> If this works without asking you for a password, >&#13; If this works without asking you for a password,
<EM <EM
>shame on you</EM >shame on you</EM
>! You should have >! You should have
...@@ -200,7 +200,7 @@ CLASS="PARAMETER" ...@@ -200,7 +200,7 @@ CLASS="PARAMETER"
this:</P this:</P
><P ><P
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
></P ></P
><P ><P
...@@ -209,25 +209,25 @@ CLASS="QUOTE" ...@@ -209,25 +209,25 @@ CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> is the name > is the name
you chose in the<TT you chose in the<TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
> file > file
for your Bugzilla database, type:</P for your Bugzilla database, type:</P
><P ><P
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>mysql</TT >mysql</TT
><B ><B
CLASS="COMMAND" CLASS="command"
>use bugs;</B >use bugs;</B
></P ></P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -256,11 +256,11 @@ CLASS="QUOTE" ...@@ -256,11 +256,11 @@ CLASS="QUOTE"
> >
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN2360" NAME="AEN2369"
>C.2.1.1. Bugzilla Database Tables</A >C.2.1.1. Bugzilla Database Tables</A
></H3 ></H3
><P ><P
...@@ -269,10 +269,10 @@ NAME="AEN2360" ...@@ -269,10 +269,10 @@ NAME="AEN2360"
command:</P command:</P
><P ><P
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
><B ><B
CLASS="COMMAND" CLASS="command"
>show tables from bugs;</B >show tables from bugs;</B
></P ></P
><P ><P
...@@ -295,8 +295,8 @@ WIDTH="100%" ...@@ -295,8 +295,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>+-------------------+ >&#13;+-------------------+
| Tables in bugs | | Tables in bugs |
+-------------------+ +-------------------+
| attachments | | attachments |
...@@ -329,8 +329,9 @@ CLASS="PROGRAMLISTING" ...@@ -329,8 +329,9 @@ CLASS="PROGRAMLISTING"
></TABLE ></TABLE
></P ></P
><P ><P
CLASS="LITERALLAYOUT" CLASS="literallayout"
><br> ><br>
<br>
&nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br> &nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br> descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br>
<br> <br>
......
docs/html/dbschema.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="MySQL Bugzilla Database Introduction" TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"></HEAD HREF="dbdoc.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,23 +66,23 @@ HREF="dbdoc.html" ...@@ -66,23 +66,23 @@ HREF="dbdoc.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="DBSCHEMA" NAME="dbschema"
>C.1. Database Schema Chart</A >C.1. Database Schema Chart</A
></H1 ></H1
><P ><P
> <DIV >&#13; <DIV
CLASS="MEDIAOBJECT" CLASS="mediaobject"
><P ><P
><IMG ><IMG
SRC="../images/dbschema.jpg" SRC="../images/dbschema.jpg"
ALT="Database Relationships" ALT="Database Relationships"
></IMG ></IMG
><DIV ><DIV
CLASS="CAPTION" CLASS="caption"
><P ><P
>Bugzilla database relationships chart</P >Bugzilla database relationships chart</P
></DIV ></DIV
......
docs/html/disclaimer.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="New Versions" TITLE="New Versions"
HREF="newversions.html"></HEAD HREF="newversions.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="newversions.html" ...@@ -66,15 +66,15 @@ HREF="newversions.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="DISCLAIMER" NAME="disclaimer"
>1.3. Disclaimer</A >1.3. Disclaimer</A
></H1 ></H1
><P ><P
> No liability for the contents of this document can be accepted. >&#13; No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk. Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors As this is a new edition of this document, there may be errors
and inaccuracies that may damage your system. Use of this and inaccuracies that may damage your system. Use of this
...@@ -84,13 +84,13 @@ NAME="DISCLAIMER" ...@@ -84,13 +84,13 @@ NAME="DISCLAIMER"
war. Proceed with caution. war. Proceed with caution.
</P </P
><P ><P
> All copyrights are held by their respective owners, unless >&#13; All copyrights are held by their respective owners, unless
specifically noted otherwise. Use of a term in this document specifically noted otherwise. Use of a term in this document
should not be regarded as affecting the validity of any should not be regarded as affecting the validity of any
trademark or service mark. trademark or service mark.
</P </P
><P ><P
> Naming of particular products or brands should not be seen as >&#13; Naming of particular products or brands should not be seen as
endorsements, with the exception of the term "GNU/Linux". I endorsements, with the exception of the term "GNU/Linux". I
wholeheartedly endorse the use of GNU/Linux in every situation wholeheartedly endorse the use of GNU/Linux in every situation
where it is appropriate. It is an extremely versatile, stable, where it is appropriate. It is an extremely versatile, stable,
...@@ -98,13 +98,13 @@ NAME="DISCLAIMER" ...@@ -98,13 +98,13 @@ NAME="DISCLAIMER"
environment for Bugzilla. environment for Bugzilla.
</P </P
><P ><P
> You are strongly recommended to make a backup of your system >&#13; You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter. before installing Bugzilla and at regular intervals thereafter.
Heaven knows it's saved my bacon time after time; if you Heaven knows it's saved my bacon time after time; if you
implement any suggestion in this Guide, implement this one! implement any suggestion in this Guide, implement this one!
</P </P
><P ><P
> Although the Bugzilla development team has taken great care to >&#13; Although the Bugzilla development team has taken great care to
ensure that all easily-exploitable bugs or options are ensure that all easily-exploitable bugs or options are
documented or fixed in the code, security holes surely exist. documented or fixed in the code, security holes surely exist.
Great care should be taken both in the installation and usage of Great care should be taken both in the installation and usage of
......
docs/html/downloadlinks.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="The Bugzilla Database" TITLE="The Bugzilla Database"
HREF="database.html"></HEAD HREF="database.html"></HEAD
><BODY ><BODY
CLASS="APPENDIX" CLASS="appendix"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,18 +63,18 @@ HREF="database.html" ...@@ -63,18 +63,18 @@ HREF="database.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="APPENDIX" CLASS="appendix"
><H1 ><H1
><A ><A
NAME="DOWNLOADLINKS" NAME="downloadlinks"
>Appendix B. Software Download Links</A >Appendix B. Software Download Links</A
></H1 ></H1
><P ><P
> All of these sites are current as of April, 2001. Hopefully >&#13; All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while. they'll stay current for a while.
</P </P
><P ><P
> Apache Web Server: <A >&#13; Apache Web Server: <A
HREF="http://www.apache.org/" HREF="http://www.apache.org/"
TARGET="_top" TARGET="_top"
>http://www.apache.org</A >http://www.apache.org</A
...@@ -82,71 +82,71 @@ TARGET="_top" ...@@ -82,71 +82,71 @@ TARGET="_top"
Optional web server for Bugzilla, but recommended because of broad user base and support. Optional web server for Bugzilla, but recommended because of broad user base and support.
</P </P
><P ><P
> Bugzilla: <A >&#13; Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A >&#13; http://www.mozilla.org/projects/bugzilla/</A
> >
</P </P
><P ><P
> MySQL: <A >&#13; MySQL: <A
HREF="http://www.mysql.com/" HREF="http://www.mysql.com/"
TARGET="_top" TARGET="_top"
>http://www.mysql.com/</A >http://www.mysql.com/</A
> >
</P </P
><P ><P
> Perl: <A >&#13; Perl: <A
HREF="http://www.perl.org" HREF="http://www.perl.org"
TARGET="_top" TARGET="_top"
>http://www.perl.org/</A >http://www.perl.org/</A
> >
</P </P
><P ><P
> CPAN: <A >&#13; CPAN: <A
HREF="http://www.cpan.org/" HREF="http://www.cpan.org/"
TARGET="_top" TARGET="_top"
>http://www.cpan.org/</A >http://www.cpan.org/</A
> >
</P </P
><P ><P
> DBI Perl module: >&#13; DBI Perl module:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/" HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A >&#13; http://www.cpan.org/modules/by-module/DBI/</A
> >
</P </P
><P ><P
> Data::Dumper module: >&#13; Data::Dumper module:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/" HREF="http://www.cpan.org/modules/by-module/Data/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A >&#13; http://www.cpan.org/modules/by-module/Data/</A
> >
</P </P
><P ><P
> MySQL related Perl modules: >&#13; MySQL related Perl modules:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/" HREF="http://www.cpan.org/modules/by-module/Mysql/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A >&#13; http://www.cpan.org/modules/by-module/Mysql/</A
> >
</P </P
><P ><P
> TimeDate Perl module collection: >&#13; TimeDate Perl module collection:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/" HREF="http://www.cpan.org/modules/by-module/Date/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A >&#13; http://www.cpan.org/modules/by-module/Date/</A
> >
</P </P
><P ><P
> GD Perl module: >&#13; GD Perl module:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/" HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A >&#13; http://www.cpan.org/modules/by-module/GD/</A
> >
Alternately, you should be able to find the latest version of Alternately, you should be able to find the latest version of
GD at <A GD at <A
...@@ -156,15 +156,15 @@ TARGET="_top" ...@@ -156,15 +156,15 @@ TARGET="_top"
> >
</P </P
><P ><P
> Chart::Base module: >&#13; Chart::Base module:
<A <A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/" HREF="http://www.cpan.org/modules/by-module/Chart/"
TARGET="_top" TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A >&#13; http://www.cpan.org/modules/by-module/Chart/</A
> >
</P </P
><P ><P
> LinuxDoc Software: >&#13; LinuxDoc Software:
<A <A
HREF="http://www.linuxdoc.org/" HREF="http://www.linuxdoc.org/"
TARGET="_top" TARGET="_top"
......
docs/html/errata.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Step-by-step Install" TITLE="Step-by-step Install"
HREF="stepbystep.html"></HEAD HREF="stepbystep.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="stepbystep.html" ...@@ -66,11 +66,11 @@ HREF="stepbystep.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="ERRATA" NAME="errata"
>3.1. ERRATA</A >3.1. ERRATA</A
></H1 ></H1
><P ><P
...@@ -85,29 +85,29 @@ BORDER="0" ...@@ -85,29 +85,29 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
> If you are installing Bugzilla on S.u.S.e. Linux, or some >&#13; If you are installing Bugzilla on S.u.S.e. Linux, or some
other distributions with <SPAN other distributions with <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"paranoid"</SPAN >"paranoid"</SPAN
> security > security
options, it is possible that the checksetup.pl script may fail options, it is possible that the checksetup.pl script may fail
with the error: <SPAN with the error: <SPAN
CLASS="ERRORNAME" CLASS="errorname"
>cannot chdir(/var/spool/mqueue): >cannot chdir(/var/spool/mqueue):
Permission denied</SPAN Permission denied</SPAN
> This is because your > This is because your
<TT <TT
CLASS="FILENAME" CLASS="filename"
>/var/spool/mqueue</TT >/var/spool/mqueue</TT
> directory has a mode of > directory has a mode of
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"drwx------"</SPAN >"drwx------"</SPAN
>. Type <B >. Type <B
CLASS="COMMAND" CLASS="command"
>chmod 755 >chmod 755
<TT <TT
CLASS="FILENAME" CLASS="filename"
>/var/spool/mqueue</TT >/var/spool/mqueue</TT
></B ></B
> as root to > as root to
...@@ -116,7 +116,7 @@ CLASS="FILENAME" ...@@ -116,7 +116,7 @@ CLASS="FILENAME"
></TR ></TR
><TR ><TR
><TD ><TD
> Bugzilla may be installed on Macintosh OS X (10), which is a >&#13; Bugzilla may be installed on Macintosh OS X (10), which is a
unix-based (BSD) operating system. Everything required for unix-based (BSD) operating system. Everything required for
Bugzilla on OS X will install cleanly, but the optional GD Bugzilla on OS X will install cleanly, but the optional GD
perl module which is used for bug charting requires some perl module which is used for bug charting requires some
...@@ -126,9 +126,9 @@ CLASS="FILENAME" ...@@ -126,9 +126,9 @@ CLASS="FILENAME"
></TR ></TR
><TR ><TR
><TD ><TD
> Release Notes for Bugzilla 2.14 are available at >&#13; Release Notes for Bugzilla 2.14 are available at
<TT <TT
CLASS="FILENAME" CLASS="filename"
>docs/rel_notes.txt</TT >docs/rel_notes.txt</TT
> in your Bugzilla > in your Bugzilla
source distribution. source distribution.
...@@ -136,7 +136,7 @@ CLASS="FILENAME" ...@@ -136,7 +136,7 @@ CLASS="FILENAME"
></TR ></TR
><TR ><TR
><TD ><TD
> The preferred documentation for Bugzilla is available in >&#13; The preferred documentation for Bugzilla is available in
docs/, with a variety of document types available. Please docs/, with a variety of document types available. Please
refer to these documents when installing, configuring, and refer to these documents when installing, configuring, and
maintaining your Bugzilla installation. maintaining your Bugzilla installation.
...@@ -147,11 +147,11 @@ CLASS="FILENAME" ...@@ -147,11 +147,11 @@ CLASS="FILENAME"
><P ><P
></P ></P
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -167,7 +167,7 @@ ALT="Warning"></TD ...@@ -167,7 +167,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Bugzilla is not a package where you can just plop it in a directory, >&#13; Bugzilla is not a package where you can just plop it in a directory,
twiddle a few things, and you're off. Installing Bugzilla assumes you twiddle a few things, and you're off. Installing Bugzilla assumes you
know your variant of UNIX or Microsoft Windows well, are familiar with the know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora command line, and are comfortable compiling and installing a plethora
...@@ -181,11 +181,11 @@ VALIGN="TOP" ...@@ -181,11 +181,11 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -201,7 +201,7 @@ ALT="Warning"></TD ...@@ -201,7 +201,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Bugzilla has not undergone a complete security review. Security holes >&#13; Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla. installing other network services with Bugzilla.
......
docs/html/faq.html
View file @ d7f38125
...@@ -11,12 +11,12 @@ TITLE="The Bugzilla Guide" ...@@ -11,12 +11,12 @@ TITLE="The Bugzilla Guide"
HREF="index.html"><LINK HREF="index.html"><LINK
REL="PREVIOUS" REL="PREVIOUS"
TITLE="SourceForge" TITLE="SourceForge"
HREF="variant_sourceforge.html"><LINK HREF="variant-sourceforge.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Software Download Links" TITLE="Software Download Links"
HREF="downloadlinks.html"></HEAD HREF="downloadlinks.html"></HEAD
><BODY ><BODY
CLASS="APPENDIX" CLASS="appendix"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -41,7 +41,7 @@ WIDTH="10%" ...@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left" ALIGN="left"
VALIGN="bottom" VALIGN="bottom"
><A ><A
HREF="variant_sourceforge.html" HREF="variant-sourceforge.html"
>Prev</A >Prev</A
></TD ></TD
><TD ><TD
...@@ -63,82 +63,82 @@ HREF="downloadlinks.html" ...@@ -63,82 +63,82 @@ HREF="downloadlinks.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="APPENDIX" CLASS="appendix"
><H1 ><H1
><A ><A
NAME="FAQ" NAME="faq"
>Appendix A. The Bugzilla FAQ</A >Appendix A. The Bugzilla FAQ</A
></H1 ></H1
><DIV ><DIV
CLASS="QANDASET" CLASS="qandaset"
><DL ><DL
><DT ><DT
>1. <A >1. <A
HREF="faq.html#FAQ_GENERAL" HREF="faq.html#faq-general"
>General Questions</A >General Questions</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.1.1. <A >A.1.1. <A
HREF="faq.html#AEN1713" HREF="faq.html#AEN1722"
> Where can I find information about Bugzilla?</A >&#13; Where can I find information about Bugzilla?</A
></DT ></DT
><DT ><DT
>A.1.2. <A >A.1.2. <A
HREF="faq.html#AEN1719" HREF="faq.html#AEN1728"
> What license is Bugzilla distributed under? >&#13; What license is Bugzilla distributed under?
</A </A
></DT ></DT
><DT ><DT
>A.1.3. <A >A.1.3. <A
HREF="faq.html#AEN1725" HREF="faq.html#AEN1734"
> How do I get commercial support for Bugzilla? >&#13; How do I get commercial support for Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.1.4. <A >A.1.4. <A
HREF="faq.html#AEN1732" HREF="faq.html#AEN1741"
> What major companies or projects are currently using Bugzilla >&#13; What major companies or projects are currently using Bugzilla
for bug-tracking? for bug-tracking?
</A </A
></DT ></DT
><DT ><DT
>A.1.5. <A >A.1.5. <A
HREF="faq.html#AEN1757" HREF="faq.html#AEN1766"
> Who maintains Bugzilla? >&#13; Who maintains Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.1.6. <A >A.1.6. <A
HREF="faq.html#AEN1763" HREF="faq.html#AEN1772"
> How does Bugzilla stack up against other bug-tracking databases? >&#13; How does Bugzilla stack up against other bug-tracking databases?
</A </A
></DT ></DT
><DT ><DT
>A.1.7. <A >A.1.7. <A
HREF="faq.html#AEN1770" HREF="faq.html#AEN1779"
> How do I change my user name in Bugzilla? >&#13; How do I change my user name in Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.1.8. <A >A.1.8. <A
HREF="faq.html#AEN1775" HREF="faq.html#AEN1784"
> Why doesn't Bugzilla offer this or that feature or compatability >&#13; Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software? with this other tracking software?
</A </A
></DT ></DT
><DT ><DT
>A.1.9. <A >A.1.9. <A
HREF="faq.html#AEN1782" HREF="faq.html#AEN1791"
> Why MySQL? I'm interested in seeing Bugzilla run on >&#13; Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL? Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A </A
></DT ></DT
><DT ><DT
>A.1.10. <A >A.1.10. <A
HREF="faq.html#AEN1800" HREF="faq.html#AEN1809"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of >&#13; Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else? "/usr/bin/perl" or something else?
</A </A
></DT ></DT
...@@ -146,143 +146,143 @@ HREF="faq.html#AEN1800" ...@@ -146,143 +146,143 @@ HREF="faq.html#AEN1800"
></DD ></DD
><DT ><DT
>2. <A >2. <A
HREF="faq.html#FAQ_REDHAT" HREF="faq.html#faq-redhat"
>Red Hat Bugzilla</A >Red Hat Bugzilla</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.2.1. <A >A.2.1. <A
HREF="faq.html#AEN1817" HREF="faq.html#AEN1826"
> What about Red Hat Bugzilla? >&#13; What about Red Hat Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.2.2. <A >A.2.2. <A
HREF="faq.html#AEN1825" HREF="faq.html#AEN1834"
> What are the primary benefits of Red Hat Bugzilla? >&#13; What are the primary benefits of Red Hat Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.2.3. <A >A.2.3. <A
HREF="faq.html#AEN1853" HREF="faq.html#AEN1862"
> What's the current status of Red Hat Bugzilla? >&#13; What's the current status of Red Hat Bugzilla?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>3. <A >3. <A
HREF="faq.html#FAQ_LOKI" HREF="faq.html#faq-loki"
>Loki Bugzilla (AKA Fenris)</A >Loki Bugzilla (AKA Fenris)</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.3.1. <A >A.3.1. <A
HREF="faq.html#AEN1866" HREF="faq.html#AEN1875"
> What is Loki Bugzilla (Fenris)? >&#13; What is Loki Bugzilla (Fenris)?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>4. <A >4. <A
HREF="faq.html#FAQ_PHB" HREF="faq.html#faq-phb"
>Pointy-Haired-Boss Questions</A >Pointy-Haired-Boss Questions</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.4.1. <A >A.4.1. <A
HREF="faq.html#AEN1877" HREF="faq.html#AEN1886"
> Is Bugzilla web-based or do you have to have specific software or >&#13; Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine? specific operating system on your machine?
</A </A
></DT ></DT
><DT ><DT
>A.4.2. <A >A.4.2. <A
HREF="faq.html#AEN1882" HREF="faq.html#AEN1891"
> Has anyone you know of already done any Bugzilla integration with >&#13; Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)? Perforce (SCM software)?
</A </A
></DT ></DT
><DT ><DT
>A.4.3. <A >A.4.3. <A
HREF="faq.html#AEN1887" HREF="faq.html#AEN1896"
> Does Bugzilla allow the user to track multiple projects? >&#13; Does Bugzilla allow the user to track multiple projects?
</A </A
></DT ></DT
><DT ><DT
>A.4.4. <A >A.4.4. <A
HREF="faq.html#AEN1892" HREF="faq.html#AEN1901"
> If I am on many projects, and search for all bugs assigned to me, will >&#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? Bugzilla list them for me and allow me to sort by project, severity etc?
</A </A
></DT ></DT
><DT ><DT
>A.4.5. <A >A.4.5. <A
HREF="faq.html#AEN1897" HREF="faq.html#AEN1906"
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, >&#13; Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed? are there any that are NOT allowed?
</A </A
></DT ></DT
><DT ><DT
>A.4.6. <A >A.4.6. <A
HREF="faq.html#AEN1902" HREF="faq.html#AEN1911"
> Does Bugzilla allow us to define our own priorities and levels? Do we >&#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 have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values? the choice of acceptable values?
</A </A
></DT ></DT
><DT ><DT
>A.4.7. <A >A.4.7. <A
HREF="faq.html#AEN1909" HREF="faq.html#AEN1918"
> The index.html page doesn't show the footer. It's really annoying to have >&#13; The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages? on static HTML pages?
</A </A
></DT ></DT
><DT ><DT
>A.4.8. <A >A.4.8. <A
HREF="faq.html#AEN1931" HREF="faq.html#AEN1940"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You >&#13; Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :) know, the type of stuff that management likes to see. :)
</A </A
></DT ></DT
><DT ><DT
>A.4.9. <A >A.4.9. <A
HREF="faq.html#AEN1939" HREF="faq.html#AEN1948"
> Is there email notification and if so, what do you see when you get an >&#13; Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number? email? Do you see bug number and title or is it only the number?
</A </A
></DT ></DT
><DT ><DT
>A.4.10. <A >A.4.10. <A
HREF="faq.html#AEN1944" HREF="faq.html#AEN1953"
> Can email notification be set up to send to multiple >&#13; Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc? people, some on the To List, CC List, BCC List etc?
</A </A
></DT ></DT
><DT ><DT
>A.4.11. <A >A.4.11. <A
HREF="faq.html#AEN1949" HREF="faq.html#AEN1958"
> If there is email notification, do users have to have any particular >&#13; If there is email notification, do users have to have any particular
type of email application? type of email application?
</A </A
></DT ></DT
><DT ><DT
>A.4.12. <A >A.4.12. <A
HREF="faq.html#AEN1956" HREF="faq.html#AEN1965"
> If I just wanted to track certain bugs, as they go through life, can I >&#13; If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.? owner, status or description etc.?
</A </A
></DT ></DT
><DT ><DT
>A.4.13. <A >A.4.13. <A
HREF="faq.html#AEN1961" HREF="faq.html#AEN1970"
> Does Bugzilla allow data to be imported and exported? If I had outsiders >&#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 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 imported into "matching" fields? If I wanted to take the results of a query
and export that data to MS Excel, could I do that? and export that data to MS Excel, could I do that?
...@@ -290,68 +290,68 @@ HREF="faq.html#AEN1961" ...@@ -290,68 +290,68 @@ HREF="faq.html#AEN1961"
></DT ></DT
><DT ><DT
>A.4.14. <A >A.4.14. <A
HREF="faq.html#AEN1969" HREF="faq.html#AEN1978"
> Has anyone converted Bugzilla to another language to be used in other >&#13; Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable? countries? Is it localizable?
</A </A
></DT ></DT
><DT ><DT
>A.4.15. <A >A.4.15. <A
HREF="faq.html#AEN1974" HREF="faq.html#AEN1983"
> Can a user create and save reports? Can they do this in Word format? >&#13; Can a user create and save reports? Can they do this in Word format?
Excel format? Excel format?
</A </A
></DT ></DT
><DT ><DT
>A.4.16. <A >A.4.16. <A
HREF="faq.html#AEN1979" HREF="faq.html#AEN1988"
> Can a user re-run a report with a new project, same query? >&#13; Can a user re-run a report with a new project, same query?
</A </A
></DT ></DT
><DT ><DT
>A.4.17. <A >A.4.17. <A
HREF="faq.html#AEN1984" HREF="faq.html#AEN1993"
> Can a user modify an existing report and then save it into another name? >&#13; Can a user modify an existing report and then save it into another name?
</A </A
></DT ></DT
><DT ><DT
>A.4.18. <A >A.4.18. <A
HREF="faq.html#AEN1989" HREF="faq.html#AEN1998"
> Does Bugzilla have the ability to search by word, phrase, compound >&#13; Does Bugzilla have the ability to search by word, phrase, compound
search? search?
</A </A
></DT ></DT
><DT ><DT
>A.4.19. <A >A.4.19. <A
HREF="faq.html#AEN1994" HREF="faq.html#AEN2003"
> Can the admin person establish separate group and individual user >&#13; Can the admin person establish separate group and individual user
privileges? privileges?
</A </A
></DT ></DT
><DT ><DT
>A.4.20. <A >A.4.20. <A
HREF="faq.html#AEN1999" HREF="faq.html#AEN2008"
> Does Bugzilla provide record locking when there is simultaneous access >&#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 to the same bug? Does the second person get a notice that the bug is in use
or how are they notified? or how are they notified?
</A </A
></DT ></DT
><DT ><DT
>A.4.21. <A >A.4.21. <A
HREF="faq.html#AEN2004" HREF="faq.html#AEN2013"
> Are there any backup features provided? >&#13; Are there any backup features provided?
</A </A
></DT ></DT
><DT ><DT
>A.4.22. <A >A.4.22. <A
HREF="faq.html#AEN2010" HREF="faq.html#AEN2019"
> Can users be on the system while a backup is in progress? >&#13; Can users be on the system while a backup is in progress?
</A </A
></DT ></DT
><DT ><DT
>A.4.23. <A >A.4.23. <A
HREF="faq.html#AEN2015" HREF="faq.html#AEN2024"
> What type of human resources are needed to be on staff to install and >&#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 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 have? I need to find out if we were to go with Bugzilla, what types of
individuals would we need to hire and how much would that cost vs buying an individuals would we need to hire and how much would that cost vs buying an
...@@ -360,8 +360,8 @@ HREF="faq.html#AEN2015" ...@@ -360,8 +360,8 @@ HREF="faq.html#AEN2015"
></DT ></DT
><DT ><DT
>A.4.24. <A >A.4.24. <A
HREF="faq.html#AEN2022" HREF="faq.html#AEN2031"
> What time frame are we looking at if we decide to hire people to install >&#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 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 install and a couple of hours per week to maintain and customize or is this
a multi-week install process, plus a full time job for 1 person, 2 people, a multi-week install process, plus a full time job for 1 person, 2 people,
...@@ -370,8 +370,8 @@ HREF="faq.html#AEN2022" ...@@ -370,8 +370,8 @@ HREF="faq.html#AEN2022"
></DT ></DT
><DT ><DT
>A.4.25. <A >A.4.25. <A
HREF="faq.html#AEN2027" HREF="faq.html#AEN2036"
> Is there any licensing fee or other fees for using Bugzilla? Any >&#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? out-of-pocket cost other than the bodies needed as identified above?
</A </A
></DT ></DT
...@@ -379,55 +379,55 @@ HREF="faq.html#AEN2027" ...@@ -379,55 +379,55 @@ HREF="faq.html#AEN2027"
></DD ></DD
><DT ><DT
>5. <A >5. <A
HREF="faq.html#FAQ_INSTALL" HREF="faq.html#faq-install"
>Bugzilla Installation</A >Bugzilla Installation</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.5.1. <A >A.5.1. <A
HREF="faq.html#AEN2034" HREF="faq.html#AEN2043"
> How do I download and install Bugzilla? >&#13; How do I download and install Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.5.2. <A >A.5.2. <A
HREF="faq.html#AEN2040" HREF="faq.html#AEN2049"
> How do I install Bugzilla on Windows NT? >&#13; How do I install Bugzilla on Windows NT?
</A </A
></DT ></DT
><DT ><DT
>A.5.3. <A >A.5.3. <A
HREF="faq.html#AEN2045" HREF="faq.html#AEN2054"
> Is there an easy way to change the Bugzilla cookie name? >&#13; Is there an easy way to change the Bugzilla cookie name?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>6. <A >6. <A
HREF="faq.html#FAQ_SECURITY" HREF="faq.html#faq-security"
>Bugzilla Security</A >Bugzilla Security</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.6.1. <A >A.6.1. <A
HREF="faq.html#AEN2052" HREF="faq.html#AEN2061"
> How do I completely disable MySQL security if it's giving me problems >&#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!)? (I've followed the instructions in the installation section of this guide!)?
</A </A
></DT ></DT
><DT ><DT
>A.6.2. <A >A.6.2. <A
HREF="faq.html#AEN2058" HREF="faq.html#AEN2067"
> Are there any security problems with Bugzilla? >&#13; Are there any security problems with Bugzilla?
</A </A
></DT ></DT
><DT ><DT
>A.6.3. <A >A.6.3. <A
HREF="faq.html#AEN2063" HREF="faq.html#AEN2072"
> I've implemented the security fixes mentioned in Chris Yeh's security >&#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 advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly. problems with MySQL no longer working correctly.
</A </A
...@@ -436,164 +436,164 @@ HREF="faq.html#AEN2063" ...@@ -436,164 +436,164 @@ HREF="faq.html#AEN2063"
></DD ></DD
><DT ><DT
>7. <A >7. <A
HREF="faq.html#FAQ_EMAIL" HREF="faq.html#faq-email"
>Bugzilla Email</A >Bugzilla Email</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.7.1. <A >A.7.1. <A
HREF="faq.html#AEN2070" HREF="faq.html#AEN2079"
> I have a user who doesn't want to receive any more email from Bugzilla. >&#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? How do I stop it entirely for this user?
</A </A
></DT ></DT
><DT ><DT
>A.7.2. <A >A.7.2. <A
HREF="faq.html#AEN2075" HREF="faq.html#AEN2084"
> I'm evaluating/testing Bugzilla, and don't want it to send email to >&#13; I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it? anyone but me. How do I do it?
</A </A
></DT ></DT
><DT ><DT
>A.7.3. <A >A.7.3. <A
HREF="faq.html#AEN2080" HREF="faq.html#AEN2089"
> I want whineatnews.pl to whine at something more, or other than, only new >&#13; I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it? bugs. How do I do it?
</A </A
></DT ></DT
><DT ><DT
>A.7.4. <A >A.7.4. <A
HREF="faq.html#AEN2086" HREF="faq.html#AEN2095"
> I don't like/want to use Procmail to hand mail off to bug_email.pl. >&#13; I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have? What alternatives do I have?
</A </A
></DT ></DT
><DT ><DT
>A.7.5. <A >A.7.5. <A
HREF="faq.html#AEN2093" HREF="faq.html#AEN2102"
> How do I set up the email interface to submit/change bugs via email? >&#13; How do I set up the email interface to submit/change bugs via email?
</A </A
></DT ></DT
><DT ><DT
>A.7.6. <A >A.7.6. <A
HREF="faq.html#AEN2098" HREF="faq.html#AEN2107"
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. >&#13; Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives? What gives?
</A </A
></DT ></DT
><DT ><DT
>A.7.7. <A >A.7.7. <A
HREF="faq.html#AEN2105" HREF="faq.html#AEN2114"
> How come email never reaches me from bugzilla changes? >&#13; How come email never reaches me from bugzilla changes?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>8. <A >8. <A
HREF="faq.html#FAQ_DB" HREF="faq.html#faq-db"
>Bugzilla Database</A >Bugzilla Database</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.8.1. <A >A.8.1. <A
HREF="faq.html#AEN2113" HREF="faq.html#AEN2122"
> I've heard Bugzilla can be used with Oracle? >&#13; I've heard Bugzilla can be used with Oracle?
</A </A
></DT ></DT
><DT ><DT
>A.8.2. <A >A.8.2. <A
HREF="faq.html#AEN2118" HREF="faq.html#AEN2127"
> Bugs are missing from queries, but exist in the database (and I can pull >&#13; Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong? them up by specifying the bug ID). What's wrong?
</A </A
></DT ></DT
><DT ><DT
>A.8.3. <A >A.8.3. <A
HREF="faq.html#AEN2123" HREF="faq.html#AEN2132"
> I think my database might be corrupted, or contain invalid entries. What >&#13; I think my database might be corrupted, or contain invalid entries. What
do I do? do I do?
</A </A
></DT ></DT
><DT ><DT
>A.8.4. <A >A.8.4. <A
HREF="faq.html#AEN2131" HREF="faq.html#AEN2140"
> I want to manually edit some entries in my database. How? >&#13; I want to manually edit some entries in my database. How?
</A </A
></DT ></DT
><DT ><DT
>A.8.5. <A >A.8.5. <A
HREF="faq.html#AEN2136" HREF="faq.html#AEN2145"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong. >&#13; I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A </A
></DT ></DT
><DT ><DT
>A.8.6. <A >A.8.6. <A
HREF="faq.html#AEN2141" HREF="faq.html#AEN2150"
> I think I've set up MySQL permissions correctly, but bugzilla still can't >&#13; I think I've set up MySQL permissions correctly, but bugzilla still can't
connect. connect.
</A </A
></DT ></DT
><DT ><DT
>A.8.7. <A >A.8.7. <A
HREF="faq.html#AEN2146" HREF="faq.html#AEN2155"
> How do I synchronize bug information among multiple different Bugzilla >&#13; How do I synchronize bug information among multiple different Bugzilla
databases? databases?
</A </A
></DT ></DT
><DT ><DT
>A.8.8. <A >A.8.8. <A
HREF="faq.html#AEN2153" HREF="faq.html#AEN2162"
> Why do I get bizarre errors when trying to submit data, particularly problems >&#13; Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"? with "groupset"?
</A </A
></DT ></DT
><DT ><DT
>A.8.9. <A >A.8.9. <A
HREF="faq.html#AEN2158" HREF="faq.html#AEN2167"
> How come even after I delete bugs, the long descriptions show up? >&#13; How come even after I delete bugs, the long descriptions show up?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>9. <A >9. <A
HREF="faq.html#FAQ_NT" HREF="faq.html#faq-nt"
>Bugzilla and Win32</A >Bugzilla and Win32</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.9.1. <A >A.9.1. <A
HREF="faq.html#AEN2168" HREF="faq.html#AEN2177"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? >&#13; What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A </A
></DT ></DT
><DT ><DT
>A.9.2. <A >A.9.2. <A
HREF="faq.html#AEN2173" HREF="faq.html#AEN2182"
> Is there a "Bundle::Bugzilla" equivalent for Win32? >&#13; Is there a "Bundle::Bugzilla" equivalent for Win32?
</A </A
></DT ></DT
><DT ><DT
>A.9.3. <A >A.9.3. <A
HREF="faq.html#AEN2178" HREF="faq.html#AEN2187"
> CGI's are failing with a "something.cgi is not a valid Windows NT >&#13; CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why? application" error. Why?
</A </A
></DT ></DT
><DT ><DT
>A.9.4. <A >A.9.4. <A
HREF="faq.html#AEN2186" HREF="faq.html#AEN2195"
> Can I have some general instructions on how to make Bugzilla on Win32 work? >&#13; Can I have some general instructions on how to make Bugzilla on Win32 work?
</A </A
></DT ></DT
><DT ><DT
>A.9.5. <A >A.9.5. <A
HREF="faq.html#AEN2192" HREF="faq.html#AEN2201"
> I'm having trouble with the perl modules for NT not being able to talk to >&#13; I'm having trouble with the perl modules for NT not being able to talk to
to the database. to the database.
</A </A
></DT ></DT
...@@ -601,154 +601,160 @@ HREF="faq.html#AEN2192" ...@@ -601,154 +601,160 @@ HREF="faq.html#AEN2192"
></DD ></DD
><DT ><DT
>10. <A >10. <A
HREF="faq.html#FAQ_USE" HREF="faq.html#faq-use"
>Bugzilla Usage</A >Bugzilla Usage</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.10.1. <A >A.10.1. <A
HREF="faq.html#AEN2213" HREF="faq.html#AEN2222"
> The query page is very confusing. Isn't there a simpler way to query? >&#13; The query page is very confusing. Isn't there a simpler way to query?
</A </A
></DT ></DT
><DT ><DT
>A.10.2. <A >A.10.2. <A
HREF="faq.html#AEN2219" HREF="faq.html#AEN2228"
> I'm confused by the behavior of the "accept" button in the Show Bug form. >&#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? Why doesn't it assign the bug to me when I accept it?
</A </A
></DT ></DT
><DT ><DT
>A.10.3. <A >A.10.3. <A
HREF="faq.html#AEN2229" HREF="faq.html#AEN2238"
> I can't upload anything into the database via the "Create Attachment" >&#13; I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong? link. What am I doing wrong?
</A </A
></DT ></DT
><DT ><DT
>A.10.4. <A >A.10.4. <A
HREF="faq.html#AEN2234" HREF="faq.html#AEN2243"
> Email submissions to Bugzilla that have attachments end up asking me to >&#13; Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file. save it as a "cgi" file.
</A </A
></DT ></DT
><DT ><DT
>A.10.5. <A >A.10.5. <A
HREF="faq.html#AEN2239" HREF="faq.html#AEN2248"
> How do I change a keyword in Bugzilla, once some bugs are using it? >&#13; How do I change a keyword in Bugzilla, once some bugs are using it?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>11. <A >11. <A
HREF="faq.html#FAQ_HACKING" HREF="faq.html#faq-hacking"
>Bugzilla Hacking</A >Bugzilla Hacking</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>A.11.1. <A >A.11.1. <A
HREF="faq.html#AEN2246" HREF="faq.html#AEN2255"
> What bugs are in Bugzilla right now? >&#13; What bugs are in Bugzilla right now?
</A </A
></DT ></DT
><DT ><DT
>A.11.2. <A >A.11.2. <A
HREF="faq.html#AEN2255" HREF="faq.html#AEN2264"
> How can I change the default priority to a null value? For instance, have the default >&#13; How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"? priority be "---" instead of "P2"?
</A </A
></DT ></DT
><DT ><DT
>A.11.3. <A >A.11.3. <A
HREF="faq.html#AEN2261" HREF="faq.html#AEN2270"
> What's the best way to submit patches? What guidelines should I follow? >&#13; What's the best way to submit patches? What guidelines should I follow?
</A </A
></DT ></DT
></DL ></DL
></DD ></DD
></DL ></DL
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_GENERAL" NAME="faq-general"
></A ></A
>1. General Questions</H3 >1. General Questions</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1713" NAME="AEN1722"
></A ></A
><B ><B
>A.1.1. </B >A.1.1. </B
> Where can I find information about Bugzilla?</P >
Where can I find information about Bugzilla?</P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You can stay up-to-date with the latest Bugzilla >
You can stay up-to-date with the latest Bugzilla
information at <A information at <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A >&#13; http://www.mozilla.org/projects/bugzilla/</A
> >
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1719" NAME="AEN1728"
></A ></A
><B ><B
>A.1.2. </B >A.1.2. </B
> What license is Bugzilla distributed under? >
What license is Bugzilla distributed under?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Bugzilla is covered by the Mozilla Public License. >
Bugzilla is covered by the Mozilla Public License.
See details at <A See details at <A
HREF="http://www.mozilla.org/MPL/" HREF="http://www.mozilla.org/MPL/"
TARGET="_top" TARGET="_top"
> http://www.mozilla.org/MPL/</A >&#13; http://www.mozilla.org/MPL/</A
> >
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1725" NAME="AEN1734"
></A ></A
><B ><B
>A.1.3. </B >A.1.3. </B
> How do I get commercial support for Bugzilla? >
How do I get commercial support for Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> <A >
<A
HREF="http://www.collab.net/" HREF="http://www.collab.net/"
TARGET="_top" TARGET="_top"
>www.collab.net</A >www.collab.net</A
...@@ -758,7 +764,7 @@ TARGET="_top" ...@@ -758,7 +764,7 @@ TARGET="_top"
aren't interested in small projects. aren't interested in small projects.
</P </P
><P ><P
> There are several experienced >&#13; There are several experienced
Bugzilla hackers on the mailing list/newsgroup who are willing Bugzilla hackers on the mailing list/newsgroup who are willing
to whore themselves out for generous compensation. to whore themselves out for generous compensation.
Try sending a message to the mailing list asking for a volunteer. Try sending a message to the mailing list asking for a volunteer.
...@@ -766,25 +772,27 @@ TARGET="_top" ...@@ -766,25 +772,27 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1732" NAME="AEN1741"
></A ></A
><B ><B
>A.1.4. </B >A.1.4. </B
> What major companies or projects are currently using Bugzilla >
What major companies or projects are currently using Bugzilla
for bug-tracking? for bug-tracking?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> There are <EM >
There are <EM
>dozens</EM >dozens</EM
> of major comapanies with public > of major comapanies with public
Bugzilla sites to track bugs in their products. A few include: Bugzilla sites to track bugs in their products. A few include:
...@@ -868,30 +876,32 @@ BORDER="0" ...@@ -868,30 +876,32 @@ BORDER="0"
> >
</P </P
><P ><P
> Suffice to say, there are more than enough huge projects using Bugzilla >&#13; Suffice to say, there are more than enough huge projects using Bugzilla
that we can safely say it's extremely popular. that we can safely say it's extremely popular.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1757" NAME="AEN1766"
></A ></A
><B ><B
>A.1.5. </B >A.1.5. </B
> Who maintains Bugzilla? >
Who maintains Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Bugzilla maintenance has been in a state of flux recently. >
Bugzilla maintenance has been in a state of flux recently.
Please check <A Please check <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
...@@ -901,24 +911,26 @@ TARGET="_top" ...@@ -901,24 +911,26 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1763" NAME="AEN1772"
></A ></A
><B ><B
>A.1.6. </B >A.1.6. </B
> How does Bugzilla stack up against other bug-tracking databases? >
How does Bugzilla stack up against other bug-tracking databases?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> A year has gone by, and I <EM >
A year has gone by, and I <EM
>still</EM >still</EM
> can't > can't
find any head-to-head comparisons of Bugzilla against find any head-to-head comparisons of Bugzilla against
...@@ -931,7 +943,7 @@ CLASS="ANSWER" ...@@ -931,7 +943,7 @@ CLASS="ANSWER"
flexibility, and superior ease-of-use. flexibility, and superior ease-of-use.
</P </P
><P ><P
> If you happen to be a commercial bug-tracker vendor, please >&#13; If you happen to be a commercial bug-tracker vendor, please
step forward with a rebuttal so I can include it in the step forward with a rebuttal so I can include it in the
FAQ. We're not in pursuit of Bugzilla ueber alles; we FAQ. We're not in pursuit of Bugzilla ueber alles; we
simply love having a powerful, open-source tool to get our simply love having a powerful, open-source tool to get our
...@@ -940,55 +952,59 @@ CLASS="ANSWER" ...@@ -940,55 +952,59 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1770" NAME="AEN1779"
></A ></A
><B ><B
>A.1.7. </B >A.1.7. </B
> How do I change my user name in Bugzilla? >
How do I change my user name in Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You can't. However, the administrative account can, by simply opening >
You can't. However, the administrative account can, by simply opening
your user account in editusers.cgi and changing the login name. your user account in editusers.cgi and changing the login name.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1775" NAME="AEN1784"
></A ></A
><B ><B
>A.1.8. </B >A.1.8. </B
> Why doesn't Bugzilla offer this or that feature or compatability >
Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software? with this other tracking software?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> It may be that the support has not been built yet, or that you >
It may be that the support has not been built yet, or that you
have not yet found it. Bugzilla is making tremendous strides in have not yet found it. Bugzilla is making tremendous strides in
usability, customizability, scalability, and user interface. It usability, customizability, scalability, and user interface. It
is widely considered the most complete and popular open-source is widely considered the most complete and popular open-source
bug-tracking software in existence. bug-tracking software in existence.
</P </P
><P ><P
> That doesn't mean it can't use improvement! >&#13; That doesn't mean it can't use improvement!
You can help the project along by either hacking a patch yourself You can help the project along by either hacking a patch yourself
that supports the functionality you require, or else submitting a that supports the functionality you require, or else submitting a
"Request for Enhancement" (RFE) using the bug submission interface "Request for Enhancement" (RFE) using the bug submission interface
...@@ -1001,32 +1017,33 @@ TARGET="_top" ...@@ -1001,32 +1017,33 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1782" NAME="AEN1791"
></A ></A
><B ><B
>A.1.9. </B >A.1.9. </B
> Why MySQL? I'm interested in seeing Bugzilla run on >
Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL? Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
>Terry Weissman answers, >Terry Weissman answers,
<A <A
NAME="AEN1786" NAME="AEN1795"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> You're not the only one. But <EM >&#13; You're not the only one. But <EM
>I</EM >I</EM
> am not very interested. I'm not > am not very interested. I'm not
a real SQL or database person. I just wanted to make a useful tool, a real SQL or database person. I just wanted to make a useful tool,
...@@ -1044,7 +1061,7 @@ CLASS="BLOCKQUOTE" ...@@ -1044,7 +1061,7 @@ CLASS="BLOCKQUOTE"
> >
</P </P
><P ><P
> Things aren't quite that grim these days, however. Terry pretty much >&#13; Things aren't quite that grim these days, however. Terry pretty much
sums up much of the thinking many of us have for Bugzilla, but there sums up much of the thinking many of us have for Bugzilla, but there
is light on the horizon for database-independence! Here are some options: is light on the horizon for database-independence! Here are some options:
</P </P
...@@ -1055,7 +1072,7 @@ BORDER="0" ...@@ -1055,7 +1072,7 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
> <EM >&#13; <EM
><A ><A
HREF="http://bugzilla.redhat.com/" HREF="http://bugzilla.redhat.com/"
TARGET="_top" TARGET="_top"
...@@ -1067,7 +1084,7 @@ TARGET="_top" ...@@ -1067,7 +1084,7 @@ TARGET="_top"
></TR ></TR
><TR ><TR
><TD ><TD
> <EM >&#13; <EM
><A ><A
HREF="http://sourceforge.net/projects/interzilla" HREF="http://sourceforge.net/projects/interzilla"
TARGET="_top" TARGET="_top"
...@@ -1079,7 +1096,7 @@ TARGET="_top" ...@@ -1079,7 +1096,7 @@ TARGET="_top"
></TR ></TR
><TR ><TR
><TD ><TD
> <EM >&#13; <EM
>Bugzilla 3.0</EM >Bugzilla 3.0</EM
>: One of the primary stated goals >: One of the primary stated goals
is multiple database support. is multiple database support.
...@@ -1092,47 +1109,49 @@ TARGET="_top" ...@@ -1092,47 +1109,49 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1800" NAME="AEN1809"
></A ></A
><B ><B
>A.1.10. </B >A.1.10. </B
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of >
Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else? "/usr/bin/perl" or something else?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making >
Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
submissions is "don't break bugzilla.mozilla.org". If it breaks it, your submissions is "don't break bugzilla.mozilla.org". If it breaks it, your
patch will be reverted faster than you can do a diff. patch will be reverted faster than you can do a diff.
</P </P
><P ><P
> Here's Terry Weissman's comment, for some historical context: >&#13; Here's Terry Weissman's comment, for some historical context:
<A <A
NAME="AEN1805" NAME="AEN1814"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> [This was] purely my own convention. I wanted a place to put a version of >&#13; [This was] purely my own convention. I wanted a place to put a version of
Perl and other tools that was strictly under my control for the Perl and other tools that was strictly under my control for the
various webtools, and not subject to anyone else. Edit it to point various webtools, and not subject to anyone else. Edit it to point
to whatever you like. to whatever you like.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1148,14 +1167,14 @@ ALT="Note"></TD ...@@ -1148,14 +1167,14 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> We always recommend that, if possible, you keep the path >&#13; We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version and /usr/bonsaitools/bin directory, then symlink your version
of perl to /usr/bonsaitools/bin/perl. This will make upgrading of perl to /usr/bonsaitools/bin/perl. This will make upgrading
your Bugzilla much easier in the future. your Bugzilla much easier in the future.
</P </P
><P ><P
> Obviously, if you do not have root access to your Bugzilla >&#13; Obviously, if you do not have root access to your Bugzilla
box, our suggestion is irrelevant. box, our suggestion is irrelevant.
</P </P
></TD ></TD
...@@ -1169,19 +1188,19 @@ VALIGN="TOP" ...@@ -1169,19 +1188,19 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_REDHAT" NAME="faq-redhat"
></A ></A
>2. Red Hat Bugzilla</H3 >2. Red Hat Bugzilla</H3
><P ><P
> <DIV >&#13; <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1197,7 +1216,7 @@ ALT="Note"></TD ...@@ -1197,7 +1216,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> <EM >&#13; <EM
>This section is no longer up-to-date.</EM >This section is no longer up-to-date.</EM
> >
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
...@@ -1209,24 +1228,26 @@ VALIGN="TOP" ...@@ -1209,24 +1228,26 @@ VALIGN="TOP"
> >
</P </P
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1817" NAME="AEN1826"
></A ></A
><B ><B
>A.2.1. </B >A.2.1. </B
> What about Red Hat Bugzilla? >
What about Red Hat Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable >
Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
than stock Bugzilla. Check it out at than stock Bugzilla. Check it out at
http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/. http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/.
They've set their Bugzilla up to work with Oracle out of the box. They've set their Bugzilla up to work with Oracle out of the box.
...@@ -1236,14 +1257,14 @@ CLASS="ANSWER" ...@@ -1236,14 +1257,14 @@ CLASS="ANSWER"
yourself? yourself?
</P </P
><P ><P
> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: >&#13; Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A <A
NAME="AEN1822" NAME="AEN1831"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> Somebody needs to take the ball and run with it. I'm the only >&#13; Somebody needs to take the ball and run with it. I'm the only
maintainer and am very pressed for time. maintainer and am very pressed for time.
</P </P
></BLOCKQUOTE ></BLOCKQUOTE
...@@ -1256,33 +1277,35 @@ CLASS="BLOCKQUOTE" ...@@ -1256,33 +1277,35 @@ CLASS="BLOCKQUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1825" NAME="AEN1834"
></A ></A
><B ><B
>A.2.2. </B >A.2.2. </B
> What are the primary benefits of Red Hat Bugzilla? >
What are the primary benefits of Red Hat Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> <EM >
<EM
>Dave Lawrence</EM >Dave Lawrence</EM
>: >:
<A <A
NAME="AEN1830" NAME="AEN1839"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> For the record, we are not using any template type implementation for >&#13; For the record, we are not using any template type implementation for
the cosmetic changes maded to Bugzilla. It is just alot of html changes the cosmetic changes maded to Bugzilla. It is just alot of html changes
in the code itself. I admit I may have gotten a little carried away with it in the code itself. I admit I may have gotten a little carried away with it
but the corporate types asked for a more standardized interface to match up but the corporate types asked for a more standardized interface to match up
...@@ -1290,7 +1313,7 @@ CLASS="BLOCKQUOTE" ...@@ -1290,7 +1313,7 @@ CLASS="BLOCKQUOTE"
internal tools I am working on also look like Bugzilla. internal tools I am working on also look like Bugzilla.
</P </P
><P ><P
> I do want to land the changes that I have made to Bugzilla but I may >&#13; I do want to land the changes that I have made to Bugzilla but I may
have to back out a good deal and make a different version of Red Hat's have to back out a good deal and make a different version of Red Hat's
Bugzilla for checking in to CVS. Especially the cosmetic changes because it Bugzilla for checking in to CVS. Especially the cosmetic changes because it
seems they may not fit the general public. I will do that as soon as I can. seems they may not fit the general public. I will do that as soon as I can.
...@@ -1298,7 +1321,7 @@ CLASS="BLOCKQUOTE" ...@@ -1298,7 +1321,7 @@ CLASS="BLOCKQUOTE"
is difficult sometimes to come by. is difficult sometimes to come by.
</P </P
><P ><P
> There are also a good deal of other changes that were requested by >&#13; There are also a good deal of other changes that were requested by
management for things like support contracts and different permission management for things like support contracts and different permission
groups for making bugs private. Here is a short list of the major groups for making bugs private. Here is a short list of the major
changes that have been made: changes that have been made:
...@@ -1309,18 +1332,18 @@ CLASS="BLOCKQUOTE" ...@@ -1309,18 +1332,18 @@ CLASS="BLOCKQUOTE"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> No enum types. All old enum types are now separate smaller tables. >&#13; No enum types. All old enum types are now separate smaller tables.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> No bit wise operations. Not all databases support this so they were >&#13; No bit wise operations. Not all databases support this so they were
changed to a more generic way of doing this task changed to a more generic way of doing this task
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Bug reports can only be altered by the reporter, assignee, or a >&#13; Bug reports can only be altered by the reporter, assignee, or a
privileged bugzilla user. The rest of the world can see the bug but in privileged bugzilla user. The rest of the world can see the bug but in
a non-changeable format (unless the bug has been marked private). They a non-changeable format (unless the bug has been marked private). They
can however add comments, add and remove themselves from the CC list can however add comments, add and remove themselves from the CC list
...@@ -1328,7 +1351,7 @@ TYPE="1" ...@@ -1328,7 +1351,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Different group scheme. Each group has an id number related to it. >&#13; Different group scheme. Each group has an id number related to it.
There is a user_group table which contains userid to groupid mappings There is a user_group table which contains userid to groupid mappings
to determine which groups each user belongs to. Additionally there is to determine which groups each user belongs to. Additionally there is
a bug_group table that has bugid to groupid mappings to show which a bug_group table that has bugid to groupid mappings to show which
...@@ -1338,14 +1361,14 @@ TYPE="1" ...@@ -1338,14 +1361,14 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Product groups. product_table created to only allow certain products to >&#13; Product groups. product_table created to only allow certain products to
be visible for certain groups in both bug entry and query. This was be visible for certain groups in both bug entry and query. This was
particulary helpful for support contracts. particulary helpful for support contracts.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Of course many (too many) changes to Bugzilla code itself to allow use >&#13; Of course many (too many) changes to Bugzilla code itself to allow use
with Oracle and still allow operation with Mysql if so desired. with Oracle and still allow operation with Mysql if so desired.
Currently if you use Mysql it is set to use Mysql's old permission Currently if you use Mysql it is set to use Mysql's old permission
scheme to keep breakage to a minimum. Hopefully one day this will scheme to keep breakage to a minimum. Hopefully one day this will
...@@ -1355,7 +1378,7 @@ TYPE="1" ...@@ -1355,7 +1378,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Uses Text::Template perl module for rendering of the dynamic HTML pages >&#13; Uses Text::Template perl module for rendering of the dynamic HTML pages
such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and
footer parts of the page. This allows the html to be separate from the footer parts of the page. This allows the html to be separate from the
perl code for customizing the look and feel of the page to one's perl code for customizing the look and feel of the page to one's
...@@ -1364,7 +1387,7 @@ TYPE="1" ...@@ -1364,7 +1387,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> There are many other smaller changes. There is also a port to Oracle >&#13; There are many other smaller changes. There is also a port to Oracle
that I have been working on as time permits but is not completely that I have been working on as time permits but is not completely
finished but somewhat usable. I will merge it into our standard code finished but somewhat usable. I will merge it into our standard code
base when it becomes production quality. Unfortunately there will have base when it becomes production quality. Unfortunately there will have
...@@ -1374,7 +1397,7 @@ TYPE="1" ...@@ -1374,7 +1397,7 @@ TYPE="1"
></LI ></LI
></OL ></OL
><P ><P
> Both the Mysql and Oracle versions of our current code base are >&#13; Both the Mysql and Oracle versions of our current code base are
available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit
patch files for all of the changes I have made and he can determine what is patch files for all of the changes I have made and he can determine what is
suitable for addition to the main bugzilla cade base. But for me to commit suitable for addition to the main bugzilla cade base. But for me to commit
...@@ -1388,29 +1411,31 @@ TYPE="1" ...@@ -1388,29 +1411,31 @@ TYPE="1"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1853" NAME="AEN1862"
></A ></A
><B ><B
>A.2.3. </B >A.2.3. </B
> What's the current status of Red Hat Bugzilla? >
What's the current status of Red Hat Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> <DIV >
CLASS="NOTE" <DIV
CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1426,7 +1451,7 @@ ALT="Note"></TD ...@@ -1426,7 +1451,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This information is somewhat dated; I last updated it >&#13; This information is somewhat dated; I last updated it
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide" 7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla. for more up-to-date information regarding Red Hat Bugzilla.
</P </P
...@@ -1439,12 +1464,12 @@ VALIGN="TOP" ...@@ -1439,12 +1464,12 @@ VALIGN="TOP"
>Dave Lawrence</EM >Dave Lawrence</EM
>: >:
<A <A
NAME="AEN1860" NAME="AEN1869"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> I suppose the current thread warrants an update on the status of >&#13; I suppose the current thread warrants an update on the status of
Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on
Oracle for the last two days in our production environment. I Oracle for the last two days in our production environment. I
tried to do as much testing as possible with it before going live tried to do as much testing as possible with it before going live
...@@ -1473,7 +1498,7 @@ CLASS="BLOCKQUOTE" ...@@ -1473,7 +1498,7 @@ CLASS="BLOCKQUOTE"
thing going to help others that may need it. thing going to help others that may need it.
</P </P
><P ><P
> As Matt has mentioned it is still using out-dated code and with a >&#13; As Matt has mentioned it is still using out-dated code and with a
little help I would like to bring everything up to date for little help I would like to bring everything up to date for
eventual incorporation with the main cvs tree. Due to other eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be duties I have with the company any help with this wiould be
...@@ -1496,31 +1521,33 @@ CLASS="BLOCKQUOTE" ...@@ -1496,31 +1521,33 @@ CLASS="BLOCKQUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_LOKI" NAME="faq-loki"
></A ></A
>3. Loki Bugzilla (AKA Fenris)</H3 >3. Loki Bugzilla (AKA Fenris)</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1866" NAME="AEN1875"
></A ></A
><B ><B
>A.3.1. </B >A.3.1. </B
> What is Loki Bugzilla (Fenris)? >
What is Loki Bugzilla (Fenris)?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Loki Games has a customized version of Bugzilla available at >
Loki Games has a customized version of Bugzilla available at
<A <A
HREF="http://fenris.lokigames.com/" HREF="http://fenris.lokigames.com/"
TARGET="_top" TARGET="_top"
...@@ -1531,19 +1558,19 @@ TARGET="_top" ...@@ -1531,19 +1558,19 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_PHB" NAME="faq-phb"
></A ></A
>4. Pointy-Haired-Boss Questions</H3 >4. Pointy-Haired-Boss Questions</H3
><P ><P
> <DIV >&#13; <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1559,7 +1586,7 @@ ALT="Note"></TD ...@@ -1559,7 +1586,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> The title of this section doesn't mean you're a PHB -- it just means >&#13; The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :) you probably HAVE a PHB who wants to know this :)
</P </P
></TD ></TD
...@@ -1569,72 +1596,78 @@ VALIGN="TOP" ...@@ -1569,72 +1596,78 @@ VALIGN="TOP"
> >
</P </P
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1877" NAME="AEN1886"
></A ></A
><B ><B
>A.4.1. </B >A.4.1. </B
> Is Bugzilla web-based or do you have to have specific software or >
Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine? specific operating system on your machine?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> It is web and e-mail based. You can edit bugs by sending specially >
It is web and e-mail based. You can edit bugs by sending specially
formatted email to a properly configured Bugzilla, or control via the web. formatted email to a properly configured Bugzilla, or control via the web.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1882" NAME="AEN1891"
></A ></A
><B ><B
>A.4.2. </B >A.4.2. </B
> Has anyone you know of already done any Bugzilla integration with >
Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)? Perforce (SCM software)?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes! You can find more information elsewhere in "The Bugzilla >
Yes! You can find more information elsewhere in "The Bugzilla
Guide" in the "Integration with Third-Party Products" section. Guide" in the "Integration with Third-Party Products" section.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1887" NAME="AEN1896"
></A ></A
><B ><B
>A.4.3. </B >A.4.3. </B
> Does Bugzilla allow the user to track multiple projects? >
Does Bugzilla allow the user to track multiple projects?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Absolutely! You can track up to a "soft-limit" of around >
Absolutely! You can track up to a "soft-limit" of around
64 individual "Products", that can each be composed of as 64 individual "Products", that can each be composed of as
many "Components" as you want. Check the Administration many "Components" as you want. Check the Administration
section of the Bugzilla Guide for more information regarding section of the Bugzilla Guide for more information regarding
...@@ -1643,48 +1676,52 @@ CLASS="ANSWER" ...@@ -1643,48 +1676,52 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1892" NAME="AEN1901"
></A ></A
><B ><B
>A.4.4. </B >A.4.4. </B
> If I am on many projects, and search for all bugs assigned to me, will >
If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc? Bugzilla list them for me and allow me to sort by project, severity etc?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. >
Yes.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1897" NAME="AEN1906"
></A ></A
><B ><B
>A.4.5. </B >A.4.5. </B
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, >
Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed? are there any that are NOT allowed?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. There are many specific MIME-types that are pre-defined by Bugzilla, >
Yes. There are many specific MIME-types that are pre-defined by Bugzilla,
but you may specify any arbitrary MIME-type you need when you but you may specify any arbitrary MIME-type you need when you
upload the file. Since all attachments are stored in the database, upload the file. Since all attachments are stored in the database,
however, I recommend storing large binary attachments elsewhere however, I recommend storing large binary attachments elsewhere
...@@ -1694,31 +1731,33 @@ CLASS="ANSWER" ...@@ -1694,31 +1731,33 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1902" NAME="AEN1911"
></A ></A
><B ><B
>A.4.6. </B >A.4.6. </B
> Does Bugzilla allow us to define our own priorities and levels? Do we >
Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values? the choice of acceptable values?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. However, modifying some fields, notably those related to bug >
Yes. However, modifying some fields, notably those related to bug
progression states, also require adjusting the program logic to progression states, also require adjusting the program logic to
compensate for the change. compensate for the change.
</P </P
><P ><P
> There is no GUI for adding fields to Bugzilla at this >&#13; There is no GUI for adding fields to Bugzilla at this
time. You can follow development of this feature at time. You can follow development of this feature at
<A <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
...@@ -1729,41 +1768,43 @@ TARGET="_top" ...@@ -1729,41 +1768,43 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1909" NAME="AEN1918"
></A ></A
><B ><B
>A.4.7. </B >A.4.7. </B
> The index.html page doesn't show the footer. It's really annoying to have >
The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages? on static HTML pages?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> It's possible to get the footer on the static index page using >
It's possible to get the footer on the static index page using
Server Side Includes (SSI). The trick to doing this is making Server Side Includes (SSI). The trick to doing this is making
sure that your web server is set up to allow SSI and specifically, sure that your web server is set up to allow SSI and specifically,
the #exec directive. You should also rename <TT the #exec directive. You should also rename <TT
CLASS="FILENAME" CLASS="filename"
>index.html</TT >index.html</TT
> >
to <TT to <TT
CLASS="FILENAME" CLASS="filename"
>index.shtml</TT >index.shtml</TT
>. >.
</P </P
><P ><P
> After you've done all that, you can add the following line to >&#13; After you've done all that, you can add the following line to
<TT <TT
CLASS="FILENAME" CLASS="filename"
>index.shtml</TT >index.shtml</TT
>: >:
<TABLE <TABLE
...@@ -1775,8 +1816,11 @@ WIDTH="100%" ...@@ -1775,8 +1816,11 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>&#60;!--#exec cmd="/usr/bin/perl -e &#38;quot;require 'CGI.pl'; PutFooter();&#38;quot;" --&#62;</PRE >&#13;
&#60;!--#exec cmd="/usr/bin/perl -e &#38;quot;require 'CGI.pl'; PutFooter();&#38;quot;" --&#62;
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1785,11 +1829,11 @@ CLASS="PROGRAMLISTING" ...@@ -1785,11 +1829,11 @@ CLASS="PROGRAMLISTING"
</P </P
><P ><P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1805,7 +1849,7 @@ ALT="Note"></TD ...@@ -1805,7 +1849,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This line will be replaced with the actual HTML for the footer >&#13; This line will be replaced with the actual HTML for the footer
when the page is requested, so you should put this line where you when the page is requested, so you should put this line where you
want the footer to appear. want the footer to appear.
</P </P
...@@ -1815,10 +1859,10 @@ VALIGN="TOP" ...@@ -1815,10 +1859,10 @@ VALIGN="TOP"
></DIV ></DIV
></P ></P
><P ><P
> Because this method depends on being able to use a #exec directive, >&#13; Because this method depends on being able to use a #exec directive,
and most ISP's will not allow that, there is an alternative method. and most ISP's will not allow that, there is an alternative method.
You could have a small script (such as <TT You could have a small script (such as <TT
CLASS="FILENAME" CLASS="filename"
>api.cgi</TT >api.cgi</TT
>) >)
that basically looks like: that basically looks like:
...@@ -1831,8 +1875,9 @@ WIDTH="100%" ...@@ -1831,8 +1875,9 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>#!/usr/bonsaitools/bin/perl -w >&#13;
#!/usr/bonsaitools/bin/perl -w
require 'globals.pl'; require 'globals.pl';
...@@ -1840,14 +1885,16 @@ if ($::FORM{sub} eq 'PutFooter') { ...@@ -1840,14 +1885,16 @@ if ($::FORM{sub} eq 'PutFooter') {
PutFooter(); PutFooter();
} else { } else {
die 'api.cgi was incorrectly called'; die 'api.cgi was incorrectly called';
}</PRE }
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
></TABLE ></TABLE
> >
and then put this line in <TT and then put this line in <TT
CLASS="FILENAME" CLASS="filename"
>index.shtml</TT >index.shtml</TT
>. >.
<TABLE <TABLE
...@@ -1859,8 +1906,11 @@ WIDTH="100%" ...@@ -1859,8 +1906,11 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>&#60;!--#include virtual="api.cgi?sub=PutFooter"--&#62;</PRE >&#13;
&#60;!--#include virtual="api.cgi?sub=PutFooter"--&#62;
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1869,11 +1919,11 @@ CLASS="PROGRAMLISTING" ...@@ -1869,11 +1919,11 @@ CLASS="PROGRAMLISTING"
</P </P
><P ><P
> <DIV > <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1889,7 +1939,7 @@ ALT="Note"></TD ...@@ -1889,7 +1939,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This still requires being able to use Server Side Includes, if >&#13; This still requires being able to use Server Side Includes, if
this simply will not work for you, see <A this simply will not work for you, see <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183"
TARGET="_top" TARGET="_top"
...@@ -1905,33 +1955,35 @@ TARGET="_top" ...@@ -1905,33 +1955,35 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1931" NAME="AEN1940"
></A ></A
><B ><B
>A.4.8. </B >A.4.8. </B
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You >
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :) know, the type of stuff that management likes to see. :)
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. Look at <A >
Yes. Look at <A
HREF="http://bugzilla.mozilla.org/reports.cgi" HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top" TARGET="_top"
> http://bugzilla.mozilla.org/reports.cgi</A >&#13; http://bugzilla.mozilla.org/reports.cgi</A
> for basic reporting > for basic reporting
facilities. facilities.
</P </P
><P ><P
> For more advanced reporting, I recommend hooking up a professional >&#13; For more advanced reporting, I recommend hooking up a professional
reporting package, such as Crystal Reports, and use ODBC to access reporting package, such as Crystal Reports, and use ODBC to access
the MySQL database. You can do a lot through the Query page of the MySQL database. You can do a lot through the Query page of
Bugzilla as well, but right now Advanced Reporting is much Bugzilla as well, but right now Advanced Reporting is much
...@@ -1939,85 +1991,91 @@ TARGET="_top" ...@@ -1939,85 +1991,91 @@ TARGET="_top"
interface with the database directly. interface with the database directly.
</P </P
><P ><P
> Advanced Reporting is a Bugzilla 3.X proposed feature. >&#13; Advanced Reporting is a Bugzilla 3.X proposed feature.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1939" NAME="AEN1948"
></A ></A
><B ><B
>A.4.9. </B >A.4.9. </B
> Is there email notification and if so, what do you see when you get an >
Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number? email? Do you see bug number and title or is it only the number?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Email notification is user-configurable. The bug id and Topic >
Email notification is user-configurable. The bug id and Topic
of the bug report accompany each email notification, along with of the bug report accompany each email notification, along with
a list of the changes made. a list of the changes made.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1944" NAME="AEN1953"
></A ></A
><B ><B
>A.4.10. </B >A.4.10. </B
> Can email notification be set up to send to multiple >
Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc? people, some on the To List, CC List, BCC List etc?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. >
Yes.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1949" NAME="AEN1958"
></A ></A
><B ><B
>A.4.11. </B >A.4.11. </B
> If there is email notification, do users have to have any particular >
If there is email notification, do users have to have any particular
type of email application? type of email application?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Bugzilla email is sent in plain text, the most compatible mail format >
Bugzilla email is sent in plain text, the most compatible mail format
on the planet. on the planet.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -2033,7 +2091,7 @@ ALT="Note"></TD ...@@ -2033,7 +2091,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you decide to use the bugzilla_email integration features >&#13; If you decide to use the bugzilla_email integration features
to allow Bugzilla to record responses to mail with the associated bug, to allow Bugzilla to record responses to mail with the associated bug,
you may need to caution your users to set their mailer to "respond you may need to caution your users to set their mailer to "respond
to messages in the format in which they were sent". For security reasons to messages in the format in which they were sent". For security reasons
...@@ -2049,26 +2107,28 @@ VALIGN="TOP" ...@@ -2049,26 +2107,28 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1956" NAME="AEN1965"
></A ></A
><B ><B
>A.4.12. </B >A.4.12. </B
> If I just wanted to track certain bugs, as they go through life, can I >
If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.? owner, status or description etc.?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. Place yourself in the "cc" field of the bug you wish to monitor. >
Yes. Place yourself in the "cc" field of the bug you wish to monitor.
Then change your "Notify me of changes to" field in the Email Settings Then change your "Notify me of changes to" field in the Email Settings
tab of the User Preferences screen in Bugzilla to the "Only those tab of the User Preferences screen in Bugzilla to the "Only those
bugs which I am listed on the CC line" option. bugs which I am listed on the CC line" option.
...@@ -2076,38 +2136,40 @@ CLASS="ANSWER" ...@@ -2076,38 +2136,40 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1961" NAME="AEN1970"
></A ></A
><B ><B
>A.4.13. </B >A.4.13. </B
> Does Bugzilla allow data to be imported and exported? If I had outsiders >
Does Bugzilla allow data to be imported and exported? If I had outsiders
write up a bug report using a MS Word bug template, could that template be 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 imported into "matching" fields? If I wanted to take the results of a query
and export that data to MS Excel, could I do that? and export that data to MS Excel, could I do that?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Mozilla allows data export through a custom DTD in XML format. >
Mozilla allows data export through a custom DTD in XML format.
It does not, however, export to specific formats other than the It does not, however, export to specific formats other than the
XML Mozilla DTD. Importing the data into Excel or any other application XML Mozilla DTD. Importing the data into Excel or any other application
is left as an exercise for the reader. is left as an exercise for the reader.
</P </P
><P ><P
> If you create import filters to other applications from Mozilla's XML, >&#13; If you create import filters to other applications from Mozilla's XML,
please submit your modifications for inclusion in future Bugzilla please submit your modifications for inclusion in future Bugzilla
distributions. distributions.
</P </P
><P ><P
> As for data import, any application can send data to Bugzilla through >&#13; As for data import, any application can send data to Bugzilla through
the HTTP protocol, or through Mozilla's XML API. However, it seems the HTTP protocol, or through Mozilla's XML API. However, it seems
kind of silly to put another front-end in front of Bugzilla; kind of silly to put another front-end in front of Bugzilla;
it makes more sense to create a simplified bug submission form in it makes more sense to create a simplified bug submission form in
...@@ -2115,31 +2177,33 @@ CLASS="ANSWER" ...@@ -2115,31 +2177,33 @@ CLASS="ANSWER"
<A <A
HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
TARGET="_top" TARGET="_top"
> http://www.mozilla.org/quality/help/bugzilla-helper.html</A >&#13; http://www.mozilla.org/quality/help/bugzilla-helper.html</A
> >
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1969" NAME="AEN1978"
></A ></A
><B ><B
>A.4.14. </B >A.4.14. </B
> Has anyone converted Bugzilla to another language to be used in other >
Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable? countries? Is it localizable?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Currently, no. Internationalization support for Perl did not >
Currently, no. Internationalization support for Perl did not
exist in a robust fashion until the recent release of version 5.6.0; exist in a robust fashion until the recent release of version 5.6.0;
Bugzilla is, and likely will remain (until 3.X) completely Bugzilla is, and likely will remain (until 3.X) completely
non-localized. non-localized.
...@@ -2147,208 +2211,225 @@ CLASS="ANSWER" ...@@ -2147,208 +2211,225 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1974" NAME="AEN1983"
></A ></A
><B ><B
>A.4.15. </B >A.4.15. </B
> Can a user create and save reports? Can they do this in Word format? >
Can a user create and save reports? Can they do this in Word format?
Excel format? Excel format?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. No. No. >
Yes. No. No.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1979" NAME="AEN1988"
></A ></A
><B ><B
>A.4.16. </B >A.4.16. </B
> Can a user re-run a report with a new project, same query? >
Can a user re-run a report with a new project, same query?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. >
Yes.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1984" NAME="AEN1993"
></A ></A
><B ><B
>A.4.17. </B >A.4.17. </B
> Can a user modify an existing report and then save it into another name? >
Can a user modify an existing report and then save it into another name?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You can save an unlimited number of queries in Bugzilla. You are free >
You can save an unlimited number of queries in Bugzilla. You are free
to modify them and rename them to your heart's desire. to modify them and rename them to your heart's desire.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1989" NAME="AEN1998"
></A ></A
><B ><B
>A.4.18. </B >A.4.18. </B
> Does Bugzilla have the ability to search by word, phrase, compound >
Does Bugzilla have the ability to search by word, phrase, compound
search? search?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You have no idea. Bugzilla's query interface, particularly with the >
You have no idea. Bugzilla's query interface, particularly with the
advanced Boolean operators, is incredibly versatile. advanced Boolean operators, is incredibly versatile.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1994" NAME="AEN2003"
></A ></A
><B ><B
>A.4.19. </B >A.4.19. </B
> Can the admin person establish separate group and individual user >
Can the admin person establish separate group and individual user
privileges? privileges?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. >
Yes.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN1999" NAME="AEN2008"
></A ></A
><B ><B
>A.4.20. </B >A.4.20. </B
> Does Bugzilla provide record locking when there is simultaneous access >
Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use to the same bug? Does the second person get a notice that the bug is in use
or how are they notified? or how are they notified?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Bugzilla does not lock records. It provides mid-air collision detection, >
Bugzilla does not lock records. It provides mid-air collision detection,
and offers the offending user a choice of options to deal with the conflict. and offers the offending user a choice of options to deal with the conflict.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2004" NAME="AEN2013"
></A ></A
><B ><B
>A.4.21. </B >A.4.21. </B
> Are there any backup features provided? >
Are there any backup features provided?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> MySQL, the database back-end for Bugzilla, allows hot-backup of data. >
MySQL, the database back-end for Bugzilla, allows hot-backup of data.
You can find strategies for dealing with backup considerations You can find strategies for dealing with backup considerations
at <A at <A
HREF="http://www.mysql.com/doc/B/a/Backup.html" HREF="http://www.mysql.com/doc/B/a/Backup.html"
TARGET="_top" TARGET="_top"
> http://www.mysql.com/doc/B/a/Backup.html</A >&#13; http://www.mysql.com/doc/B/a/Backup.html</A
> >
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2010" NAME="AEN2019"
></A ></A
><B ><B
>A.4.22. </B >A.4.22. </B
> Can users be on the system while a backup is in progress? >
Can users be on the system while a backup is in progress?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yes. However, commits to the database must wait >
Yes. However, commits to the database must wait
until the tables are unlocked. Bugzilla databases are typically until the tables are unlocked. Bugzilla databases are typically
very small, and backups routinely take less than a minute. very small, and backups routinely take less than a minute.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2015" NAME="AEN2024"
></A ></A
><B ><B
>A.4.23. </B >A.4.23. </B
> What type of human resources are needed to be on staff to install and >
What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to 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 have? I need to find out if we were to go with Bugzilla, what types of
individuals would we need to hire and how much would that cost vs buying an individuals would we need to hire and how much would that cost vs buying an
...@@ -2356,21 +2437,22 @@ NAME="AEN2015" ...@@ -2356,21 +2437,22 @@ NAME="AEN2015"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> If Bugzilla is set up correctly from the start, continuing maintenance needs >
If Bugzilla is set up correctly from the start, continuing maintenance needs
are minimal and can be completed by unskilled labor. Things like rotate are minimal and can be completed by unskilled labor. Things like rotate
backup tapes and check log files for the word "error". backup tapes and check log files for the word "error".
</P </P
><P ><P
> Commercial Bug-tracking software typically costs somewhere upwards >&#13; Commercial Bug-tracking software typically costs somewhere upwards
of $20,000 or more for 5-10 floating licenses. Bugzilla consultation of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
is available from skilled members of the newsgroup. is available from skilled members of the newsgroup.
</P </P
><P ><P
> As an example, as of this writing I typically charge >&#13; As an example, as of this writing I typically charge
$115 for the first hour, and $89 each hour thereafter $115 for the first hour, and $89 each hour thereafter
for consulting work. It takes me three to five hours to make Bugzilla for consulting work. It takes me three to five hours to make Bugzilla
happy on a Development installation of Linux-Mandrake. happy on a Development installation of Linux-Mandrake.
...@@ -2378,16 +2460,17 @@ CLASS="ANSWER" ...@@ -2378,16 +2460,17 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2022" NAME="AEN2031"
></A ></A
><B ><B
>A.4.24. </B >A.4.24. </B
> What time frame are we looking at if we decide to hire people to install >
What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to 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 install and a couple of hours per week to maintain and customize or is this
a multi-week install process, plus a full time job for 1 person, 2 people, a multi-week install process, plus a full time job for 1 person, 2 people,
...@@ -2395,11 +2478,12 @@ NAME="AEN2022" ...@@ -2395,11 +2478,12 @@ NAME="AEN2022"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> It all depends on your level of commitment. Someone with much Bugzilla >
It all depends on your level of commitment. Someone with much Bugzilla
experience can get you up and running in less than a day, and experience can get you up and running in less than a day, and
your Bugzilla install can run untended for years. If your your Bugzilla install can run untended for years. If your
Bugzilla strategy is critical to your business workflow, hire somebody Bugzilla strategy is critical to your business workflow, hire somebody
...@@ -2409,137 +2493,147 @@ CLASS="ANSWER" ...@@ -2409,137 +2493,147 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2027" NAME="AEN2036"
></A ></A
><B ><B
>A.4.25. </B >A.4.25. </B
> Is there any licensing fee or other fees for using Bugzilla? Any >
Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above? out-of-pocket cost other than the bodies needed as identified above?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> No. MySQL asks, if you find their product valuable, that you purchase >
No. MySQL asks, if you find their product valuable, that you purchase
a support contract from them that suits your needs. a support contract from them that suits your needs.
</P </P
></DIV ></DIV
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_INSTALL" NAME="faq-install"
></A ></A
>5. Bugzilla Installation</H3 >5. Bugzilla Installation</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2034" NAME="AEN2043"
></A ></A
><B ><B
>A.5.1. </B >A.5.1. </B
> How do I download and install Bugzilla? >
How do I download and install Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Check <A >
Check <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A >&#13; http://www.mozilla.org/projects/bugzilla/</A
> for details. > for details.
Once you download it, untar it, read the Bugzilla Guide. Once you download it, untar it, read the Bugzilla Guide.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2040" NAME="AEN2049"
></A ></A
><B ><B
>A.5.2. </B >A.5.2. </B
> How do I install Bugzilla on Windows NT? >
How do I install Bugzilla on Windows NT?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Installation on Windows NT has its own section in >
Installation on Windows NT has its own section in
"The Bugzilla Guide". "The Bugzilla Guide".
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2045" NAME="AEN2054"
></A ></A
><B ><B
>A.5.3. </B >A.5.3. </B
> Is there an easy way to change the Bugzilla cookie name? >
Is there an easy way to change the Bugzilla cookie name?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> At present, no. >
At present, no.
</P </P
></DIV ></DIV
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_SECURITY" NAME="faq-security"
></A ></A
>6. Bugzilla Security</H3 >6. Bugzilla Security</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2052" NAME="AEN2061"
></A ></A
><B ><B
>A.6.1. </B >A.6.1. </B
> How do I completely disable MySQL security if it's giving me problems >
How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide!)? (I've followed the instructions in the installation section of this guide!)?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM >
Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM
>this >this
makes mysql as secure as taping a $100 to the floor of a football stadium makes mysql as secure as taping a $100 to the floor of a football stadium
bathroom for safekeeping.</EM bathroom for safekeeping.</EM
...@@ -2549,24 +2643,26 @@ CLASS="ANSWER" ...@@ -2549,24 +2643,26 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2058" NAME="AEN2067"
></A ></A
><B ><B
>A.6.2. </B >A.6.2. </B
> Are there any security problems with Bugzilla? >
Are there any security problems with Bugzilla?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> The Bugzilla code has not undergone a complete security audit. >
The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found installation, and follow the recommended security guidelines found
in The Bugzilla Guide. in The Bugzilla Guide.
...@@ -2574,26 +2670,28 @@ CLASS="ANSWER" ...@@ -2574,26 +2670,28 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2063" NAME="AEN2072"
></A ></A
><B ><B
>A.6.3. </B >A.6.3. </B
> I've implemented the security fixes mentioned in Chris Yeh's security >
I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly. problems with MySQL no longer working correctly.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> This is a common problem, related to running out of file descriptors. >
This is a common problem, related to running out of file descriptors.
Simply add "ulimit -n unlimited" to the script which starts Simply add "ulimit -n unlimited" to the script which starts
mysqld. mysqld.
</P </P
...@@ -2601,84 +2699,90 @@ CLASS="ANSWER" ...@@ -2601,84 +2699,90 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_EMAIL" NAME="faq-email"
></A ></A
>7. Bugzilla Email</H3 >7. Bugzilla Email</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2070" NAME="AEN2079"
></A ></A
><B ><B
>A.7.1. </B >A.7.1. </B
> I have a user who doesn't want to receive any more email from Bugzilla. >
I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user? How do I stop it entirely for this user?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> With the email changes to 2.12, the user should be able to set >
With the email changes to 2.12, the user should be able to set
this in user email preferences. this in user email preferences.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2075" NAME="AEN2084"
></A ></A
><B ><B
>A.7.2. </B >A.7.2. </B
> I'm evaluating/testing Bugzilla, and don't want it to send email to >
I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it? anyone but me. How do I do it?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Edit the param for the mail text. Replace "To:" with "X-Real-To:", >
Edit the param for the mail text. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)". replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2080" NAME="AEN2089"
></A ></A
><B ><B
>A.7.3. </B >A.7.3. </B
> I want whineatnews.pl to whine at something more, or other than, only new >
I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it? bugs. How do I do it?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Try Klaas Freitag's excellent patch for "whineatassigned" functionality. >
Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
You can find it at<A You can find it at<A
HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679" HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
TARGET="_top" TARGET="_top"
> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A >&#13; http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
>. This >. This
patch is against an older version of Bugzilla, so you must apply patch is against an older version of Bugzilla, so you must apply
the diffs manually. the diffs manually.
...@@ -2686,33 +2790,35 @@ TARGET="_top" ...@@ -2686,33 +2790,35 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2086" NAME="AEN2095"
></A ></A
><B ><B
>A.7.4. </B >A.7.4. </B
> I don't like/want to use Procmail to hand mail off to bug_email.pl. >
I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have? What alternatives do I have?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You can call bug_email.pl directly from your aliases file, with >
You can call bug_email.pl directly from your aliases file, with
an entry like this: an entry like this:
<A <A
NAME="AEN2090" NAME="AEN2099"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" >&#13; bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
</P </P
></BLOCKQUOTE ></BLOCKQUOTE
> >
...@@ -2723,53 +2829,57 @@ CLASS="BLOCKQUOTE" ...@@ -2723,53 +2829,57 @@ CLASS="BLOCKQUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2093" NAME="AEN2102"
></A ></A
><B ><B
>A.7.5. </B >A.7.5. </B
> How do I set up the email interface to submit/change bugs via email? >
How do I set up the email interface to submit/change bugs via email?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You can find an updated README.mailif file in the contrib/ directory >
You can find an updated README.mailif file in the contrib/ directory
of your Bugzilla distribution that walks you through the setup. of your Bugzilla distribution that walks you through the setup.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2098" NAME="AEN2107"
></A ></A
><B ><B
>A.7.6. </B >A.7.6. </B
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. >
Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives? What gives?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> If you are using an alternate Mail Transport Agent (MTA other than >
If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for all sendmail), make sure the options given in the "processmail" script for all
instances of "sendmail" are correct for your MTA. instances of "sendmail" are correct for your MTA.
</P </P
><P ><P
> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi. >&#13; If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
If you are using Postfix, you will also need to enable <SPAN If you are using Postfix, you will also need to enable <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"sendmailnow"</SPAN >"sendmailnow"</SPAN
...@@ -2778,30 +2888,32 @@ CLASS="QUOTE" ...@@ -2778,30 +2888,32 @@ CLASS="QUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2105" NAME="AEN2114"
></A ></A
><B ><B
>A.7.7. </B >A.7.7. </B
> How come email never reaches me from bugzilla changes? >
How come email never reaches me from bugzilla changes?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Double-check that you have not turned off email in your user preferences. >
Double-check that you have not turned off email in your user preferences.
Confirm that Bugzilla is able to send email by visiting the "Log In" Confirm that Bugzilla is able to send email by visiting the "Log In"
link of your Bugzilla installation and clicking the "Email me a password" link of your Bugzilla installation and clicking the "Email me a password"
button after entering your email address. button after entering your email address.
</P </P
><P ><P
> If you never receive mail from Bugzilla, chances you do not have >&#13; If you never receive mail from Bugzilla, chances you do not have
sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
to, "/usr/lib/sendmail". to, "/usr/lib/sendmail".
</P </P
...@@ -2809,31 +2921,33 @@ CLASS="ANSWER" ...@@ -2809,31 +2921,33 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_DB" NAME="faq-db"
></A ></A
>8. Bugzilla Database</H3 >8. Bugzilla Database</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2113" NAME="AEN2122"
></A ></A
><B ><B
>A.8.1. </B >A.8.1. </B
> I've heard Bugzilla can be used with Oracle? >
I've heard Bugzilla can be used with Oracle?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Red Hat Bugzilla, mentioned above, works with Oracle. The current version >
Red Hat Bugzilla, mentioned above, works with Oracle. The current version
from Mozilla.org does not have this capability. Unfortunately, though from Mozilla.org does not have this capability. Unfortunately, though
you will sacrifice a lot of the really great features available in you will sacrifice a lot of the really great features available in
Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version. Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version.
...@@ -2841,25 +2955,27 @@ CLASS="ANSWER" ...@@ -2841,25 +2955,27 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2118" NAME="AEN2127"
></A ></A
><B ><B
>A.8.2. </B >A.8.2. </B
> Bugs are missing from queries, but exist in the database (and I can pull >
Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong? them up by specifying the bug ID). What's wrong?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> You've almost certainly enabled the "shadow database", but for some >
You've almost certainly enabled the "shadow database", but for some
reason it hasn't been updated for all your bugs. This is the database reason it hasn't been updated for all your bugs. This is the database
against which queries are run, so that really complex or slow queries won't against which queries are run, so that really complex or slow queries won't
lock up portions of the database for other users. You can turn off the lock up portions of the database for other users. You can turn off the
...@@ -2876,30 +2992,32 @@ CLASS="ANSWER" ...@@ -2876,30 +2992,32 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2123" NAME="AEN2132"
></A ></A
><B ><B
>A.8.3. </B >A.8.3. </B
> I think my database might be corrupted, or contain invalid entries. What >
I think my database might be corrupted, or contain invalid entries. What
do I do? do I do?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Run the <SPAN >
Run the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"sanity check"</SPAN >"sanity check"</SPAN
> utility > utility
(<TT (<TT
CLASS="FILENAME" CLASS="filename"
>./sanitycheck.cgi</TT >./sanitycheck.cgi</TT
> in the > in the
Bugzilla_home directory) from your web browser to see! If Bugzilla_home directory) from your web browser to see! If
...@@ -2921,24 +3039,26 @@ CLASS="FILENAME" ...@@ -2921,24 +3039,26 @@ CLASS="FILENAME"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2131" NAME="AEN2140"
></A ></A
><B ><B
>A.8.4. </B >A.8.4. </B
> I want to manually edit some entries in my database. How? >
I want to manually edit some entries in my database. How?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> There is no facility in Bugzilla itself to do this. It's also generally >
There is no facility in Bugzilla itself to do this. It's also generally
not a smart thing to do if you don't know exactly what you're doing. not a smart thing to do if you don't know exactly what you're doing.
However, if you understand SQL you can use the mysqladmin utility to However, if you understand SQL you can use the mysqladmin utility to
manually insert, delete, and modify table information. Personally, I manually insert, delete, and modify table information. Personally, I
...@@ -2948,49 +3068,53 @@ CLASS="ANSWER" ...@@ -2948,49 +3068,53 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2136" NAME="AEN2145"
></A ></A
><B ><B
>A.8.5. </B >A.8.5. </B
> I try to add myself as a user, but Bugzilla always tells me my password is wrong. >
I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled >
Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
the "crypt()" function. This prevented MySQL from storing encrypted passwords. the "crypt()" function. This prevented MySQL from storing encrypted passwords.
Upgrade to the "3.23 stable" version of MySQL and you should be good to go. Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2141" NAME="AEN2150"
></A ></A
><B ><B
>A.8.6. </B >A.8.6. </B
> I think I've set up MySQL permissions correctly, but bugzilla still can't >
I think I've set up MySQL permissions correctly, but bugzilla still can't
connect. connect.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Try running MySQL from its binary: "mysqld --skip-grant-tables". This >
Try running MySQL from its binary: "mysqld --skip-grant-tables". This
will allow you to completely rule out grant tables as the cause of your will allow you to completely rule out grant tables as the cause of your
frustration. However, I do not recommend you run it this way on a regular frustration. However, I do not recommend you run it this way on a regular
basis, unless you really want your web site defaced and your machine basis, unless you really want your web site defaced and your machine
...@@ -2999,61 +3123,65 @@ CLASS="ANSWER" ...@@ -2999,61 +3123,65 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2146" NAME="AEN2155"
></A ></A
><B ><B
>A.8.7. </B >A.8.7. </B
> How do I synchronize bug information among multiple different Bugzilla >
How do I synchronize bug information among multiple different Bugzilla
databases? databases?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Well, you can synchronize or you can move bugs. Synchronization will >
Well, you can synchronize or you can move bugs. Synchronization will
only work one way -- you can create a read-only copy of the database only work one way -- you can create a read-only copy of the database
at one site, and have it regularly updated at intervals from the main at one site, and have it regularly updated at intervals from the main
database. database.
</P </P
><P ><P
> MySQL has some synchronization features builtin to the latest releases. >&#13; MySQL has some synchronization features builtin to the latest releases.
It would be great if someone looked into the possibilities there It would be great if someone looked into the possibilities there
and provided a report to the newsgroup on how to effectively and provided a report to the newsgroup on how to effectively
synchronize two Bugzilla installations. synchronize two Bugzilla installations.
</P </P
><P ><P
> If you simply need to transfer bugs from one Bugzilla to another, >&#13; If you simply need to transfer bugs from one Bugzilla to another,
checkout the "move.pl" script in the Bugzilla distribution. checkout the "move.pl" script in the Bugzilla distribution.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2153" NAME="AEN2162"
></A ></A
><B ><B
>A.8.8. </B >A.8.8. </B
> Why do I get bizarre errors when trying to submit data, particularly problems >
Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"? with "groupset"?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> If you're sure your MySQL parameters are correct, you might want turn >
If you're sure your MySQL parameters are correct, you might want turn
"strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set
"On", you also cannot submit a bug as readable by more than one group with "On", you also cannot submit a bug as readable by more than one group with
"strictvaluechecks" ON. "strictvaluechecks" ON.
...@@ -3061,35 +3189,37 @@ CLASS="ANSWER" ...@@ -3061,35 +3189,37 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2158" NAME="AEN2167"
></A ></A
><B ><B
>A.8.9. </B >A.8.9. </B
> How come even after I delete bugs, the long descriptions show up? >
How come even after I delete bugs, the long descriptions show up?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> This should only happen with Bugzilla 2.14 if you are >
This should only happen with Bugzilla 2.14 if you are
using the <SPAN using the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"shadow database"</SPAN >"shadow database"</SPAN
> feature, and your > feature, and your
shadow database is out of sync. Try running shadow database is out of sync. Try running
<TT <TT
CLASS="FILENAME" CLASS="filename"
>syncshadowdb</TT >syncshadowdb</TT
> >
<TT <TT
CLASS="OPTION" CLASS="option"
>-syncall</TT >-syncall</TT
> to make sure your shadow > to make sure your shadow
database is in synch with your primary database. database is in synch with your primary database.
...@@ -3098,92 +3228,98 @@ CLASS="OPTION" ...@@ -3098,92 +3228,98 @@ CLASS="OPTION"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_NT" NAME="faq-nt"
></A ></A
>9. Bugzilla and Win32</H3 >9. Bugzilla and Win32</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2168" NAME="AEN2177"
></A ></A
><B ><B
>A.9.1. </B >A.9.1. </B
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? >
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Remove Windows. Install Linux. Install Bugzilla. >
Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference. The boss will never know the difference.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2173" NAME="AEN2182"
></A ></A
><B ><B
>A.9.2. </B >A.9.2. </B
> Is there a "Bundle::Bugzilla" equivalent for Win32? >
Is there a "Bundle::Bugzilla" equivalent for Win32?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Not currently. Bundle::Bugzilla enormously simplifies Bugzilla >
Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
installation on UNIX systems. If someone can volunteer to installation on UNIX systems. If someone can volunteer to
create a suitable PPM bundle for Win32, it would be appreciated. create a suitable PPM bundle for Win32, it would be appreciated.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2178" NAME="AEN2187"
></A ></A
><B ><B
>A.9.3. </B >A.9.3. </B
> CGI's are failing with a "something.cgi is not a valid Windows NT >
CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why? application" error. Why?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Depending on what Web server you are using, you will have to configure >
Depending on what Web server you are using, you will have to configure
the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
adding *.cgi to the App Mappings with the &#60;path&#62;\perl.exe %s %s as the adding *.cgi to the App Mappings with the &#60;path&#62;\perl.exe %s %s as the
executable. executable.
</P </P
><P ><P
> Microsoft has some advice on this matter, as well: >&#13; Microsoft has some advice on this matter, as well:
<A <A
NAME="AEN2183" NAME="AEN2192"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> "Set application mappings. In the ISM, map the extension for the script >&#13; "Set application mappings. In the ISM, map the extension for the script
file(s) to the executable for the script interpreter. For example, you might file(s) to the executable for the script interpreter. For example, you might
map the extension .py to Python.exe, the executable for the Python script map the extension .py to Python.exe, the executable for the Python script
interpreter. Note For the ActiveState Perl script interpreter, the extension interpreter. Note For the ActiveState Perl script interpreter, the extension
...@@ -3198,29 +3334,32 @@ CLASS="BLOCKQUOTE" ...@@ -3198,29 +3334,32 @@ CLASS="BLOCKQUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2186" NAME="AEN2195"
></A ></A
><B ><B
>A.9.4. </B >A.9.4. </B
> Can I have some general instructions on how to make Bugzilla on Win32 work? >
Can I have some general instructions on how to make Bugzilla on Win32 work?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> The following couple entries are deprecated in favor of the Windows installation >
The following couple entries are deprecated in favor of the Windows installation
instructions available in the "Administration" portion of "The Bugzilla Guide". instructions available in the "Administration" portion of "The Bugzilla Guide".
However, they are provided here for historical interest and insight. However, they are provided here for historical interest and insight.
<P <P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>&nbsp;&nbsp;1.&nbsp;#!C:/perl/bin/perl&nbsp;had&nbsp;to&nbsp;be&nbsp;added&nbsp;to&nbsp;every&nbsp;perl&nbsp;file.<br> ><br>
&nbsp;&nbsp;1.&nbsp;#!C:/perl/bin/perl&nbsp;had&nbsp;to&nbsp;be&nbsp;added&nbsp;to&nbsp;every&nbsp;perl&nbsp;file.<br>
&nbsp;&nbsp;2.&nbsp;Converted&nbsp;to&nbsp;Net::SMTP&nbsp;to&nbsp;handle&nbsp;mail&nbsp;messages&nbsp;instead&nbsp;of<br> &nbsp;&nbsp;2.&nbsp;Converted&nbsp;to&nbsp;Net::SMTP&nbsp;to&nbsp;handle&nbsp;mail&nbsp;messages&nbsp;instead&nbsp;of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/usr/bin/sendmail.<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/usr/bin/sendmail.<br>
&nbsp;&nbsp;3.&nbsp;The&nbsp;crypt&nbsp;function&nbsp;isn't&nbsp;available&nbsp;on&nbsp;Windows&nbsp;NT&nbsp;(at&nbsp;least&nbsp;none&nbsp;that&nbsp;I<br> &nbsp;&nbsp;3.&nbsp;The&nbsp;crypt&nbsp;function&nbsp;isn't&nbsp;available&nbsp;on&nbsp;Windows&nbsp;NT&nbsp;(at&nbsp;least&nbsp;none&nbsp;that&nbsp;I<br>
...@@ -3309,56 +3448,58 @@ A:&nbsp;Sure!&nbsp;Here&nbsp;ya&nbsp;go!<br> ...@@ -3309,56 +3448,58 @@ A:&nbsp;Sure!&nbsp;Here&nbsp;ya&nbsp;go!<br>
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2192" NAME="AEN2201"
></A ></A
><B ><B
>A.9.5. </B >A.9.5. </B
> I'm having trouble with the perl modules for NT not being able to talk to >
I'm having trouble with the perl modules for NT not being able to talk to
to the database. to the database.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Your modules may be outdated or inaccurate. Try: >
Your modules may be outdated or inaccurate. Try:
<P <P
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Hitting http://www.activestate.com/ActivePerl >&#13; Hitting http://www.activestate.com/ActivePerl
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Download ActivePerl >&#13; Download ActivePerl
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Go to your prompt >&#13; Go to your prompt
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Type 'ppm' >&#13; Type 'ppm'
</P </P
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>PPM&#62;</TT >PPM&#62;</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>install DBI DBD-mysql GD</B >install DBI DBD-mysql GD</B
> >
</P </P
...@@ -3370,67 +3511,71 @@ CLASS="COMMAND" ...@@ -3370,67 +3511,71 @@ CLASS="COMMAND"
<A <A
HREF=" http://www.activestate.com/Packages/" HREF=" http://www.activestate.com/Packages/"
TARGET="_top" TARGET="_top"
> http://www.activestate.com/Packages/</A >&#13; http://www.activestate.com/Packages/</A
> >
</P </P
></DIV ></DIV
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_USE" NAME="faq-use"
></A ></A
>10. Bugzilla Usage</H3 >10. Bugzilla Usage</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2213" NAME="AEN2222"
></A ></A
><B ><B
>A.10.1. </B >A.10.1. </B
> The query page is very confusing. Isn't there a simpler way to query? >
The query page is very confusing. Isn't there a simpler way to query?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> We are developing in that direction. You can follow progress on this >
We are developing in that direction. You can follow progress on this
at <A at <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"
TARGET="_top" TARGET="_top"
> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A >&#13; http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
>. Some functionality >. Some functionality
is available in Bugzilla 2.12, and is available as "quicksearch.html" is available in Bugzilla 2.12, and is available as "quicksearch.html"
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2219" NAME="AEN2228"
></A ></A
><B ><B
>A.10.2. </B >A.10.2. </B
> I'm confused by the behavior of the "accept" button in the Show Bug form. >
I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it? Why doesn't it assign the bug to me when I accept it?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> The current behavior is acceptable to bugzilla.mozilla.org and most >
The current behavior is acceptable to bugzilla.mozilla.org and most
users. I personally don't like it. You have your choice of patches users. I personally don't like it. You have your choice of patches
to change this behavior, however. to change this behavior, however.
<P <P
...@@ -3443,7 +3588,7 @@ BORDER="0" ...@@ -3443,7 +3588,7 @@ BORDER="0"
><A ><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029" HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
TARGET="_top" TARGET="_top"
> Add a "and accept bug" radio button</A >&#13; Add a "and accept bug" radio button</A
></TD ></TD
></TR ></TR
><TR ><TR
...@@ -3451,7 +3596,7 @@ TARGET="_top" ...@@ -3451,7 +3596,7 @@ TARGET="_top"
><A ><A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153" HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
TARGET="_top" TARGET="_top"
> "Accept" button automatically assigns to you</A >&#13; "Accept" button automatically assigns to you</A
></TD ></TD
></TR ></TR
></TBODY ></TBODY
...@@ -3465,74 +3610,80 @@ TARGET="_top" ...@@ -3465,74 +3610,80 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2229" NAME="AEN2238"
></A ></A
><B ><B
>A.10.3. </B >A.10.3. </B
> I can't upload anything into the database via the "Create Attachment" >
I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong? link. What am I doing wrong?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> The most likely cause is a very old browser or a browser that is >
The most likely cause is a very old browser or a browser that is
incompatible with file upload via POST. Download the latest Netscape, incompatible with file upload via POST. Download the latest Netscape,
Microsoft, or Mozilla browser to handle uploads correctly. Microsoft, or Mozilla browser to handle uploads correctly.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2234" NAME="AEN2243"
></A ></A
><B ><B
>A.10.4. </B >A.10.4. </B
> Email submissions to Bugzilla that have attachments end up asking me to >
Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file. save it as a "cgi" file.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Yup. Just rename it once you download it, or save it under a different >
Yup. Just rename it once you download it, or save it under a different
filename. This will not be fixed anytime too soon, because it would filename. This will not be fixed anytime too soon, because it would
cripple some other functionality. cripple some other functionality.
</P </P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2239" NAME="AEN2248"
></A ></A
><B ><B
>A.10.5. </B >A.10.5. </B
> How do I change a keyword in Bugzilla, once some bugs are using it? >
How do I change a keyword in Bugzilla, once some bugs are using it?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> In the Bugzilla administrator UI, edit the keyword and it will let you >
In the Bugzilla administrator UI, edit the keyword and it will let you
replace the old keyword name with a new one. This will cause a problem replace the old keyword name with a new one. This will cause a problem
with the keyword cache. Run sanitycheck.cgi to fix it. with the keyword cache. Run sanitycheck.cgi to fix it.
</P </P
...@@ -3540,39 +3691,41 @@ CLASS="ANSWER" ...@@ -3540,39 +3691,41 @@ CLASS="ANSWER"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDADIV" CLASS="qandadiv"
><H3 ><H3
><A ><A
NAME="FAQ_HACKING" NAME="faq-hacking"
></A ></A
>11. Bugzilla Hacking</H3 >11. Bugzilla Hacking</H3
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2246" NAME="AEN2255"
></A ></A
><B ><B
>A.11.1. </B >A.11.1. </B
> What bugs are in Bugzilla right now? >
What bugs are in Bugzilla right now?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> Try <A >
Try <A
HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla" HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"
TARGET="_top" TARGET="_top"
> this link</A >&#13; this link</A
> to view current bugs or requests for > to view current bugs or requests for
enhancement for Bugzilla. enhancement for Bugzilla.
</P </P
><P ><P
> You can view bugs marked for 2.16 release >&#13; You can view bugs marked for 2.16 release
<A <A
HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16" HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16"
TARGET="_top" TARGET="_top"
...@@ -3583,7 +3736,7 @@ TARGET="_top" ...@@ -3583,7 +3736,7 @@ TARGET="_top"
<A <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
> Bugzilla Project Page</A >&#13; Bugzilla Project Page</A
> for details on how to > for details on how to
check current sources out of CVS so you can have these check current sources out of CVS so you can have these
bug fixes early! bug fixes early!
...@@ -3591,28 +3744,30 @@ TARGET="_top" ...@@ -3591,28 +3744,30 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2255" NAME="AEN2264"
></A ></A
><B ><B
>A.11.2. </B >A.11.2. </B
> How can I change the default priority to a null value? For instance, have the default >
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"? priority be "---" instead of "P2"?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
> This is well-documented here: <A >
This is well-documented here: <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
TARGET="_top" TARGET="_top"
> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A >&#13; http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
>. Ultimately, it's as easy >. Ultimately, it's as easy
as adding the "---" priority field to your localconfig file in the appropriate area, as adding the "---" priority field to your localconfig file in the appropriate area,
re-running checksetup.pl, and then changing the default priority in your browser using re-running checksetup.pl, and then changing the default priority in your browser using
...@@ -3623,20 +3778,21 @@ TARGET="_top" ...@@ -3623,20 +3778,21 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="QANDAENTRY" CLASS="qandaentry"
><DIV ><DIV
CLASS="QUESTION" CLASS="question"
><P ><P
><A ><A
NAME="AEN2261" NAME="AEN2270"
></A ></A
><B ><B
>A.11.3. </B >A.11.3. </B
> What's the best way to submit patches? What guidelines should I follow? >
What's the best way to submit patches? What guidelines should I follow?
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="ANSWER" CLASS="answer"
><P ><P
><B ><B
> </B > </B
...@@ -3646,7 +3802,7 @@ CLASS="ANSWER" ...@@ -3646,7 +3802,7 @@ CLASS="ANSWER"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Enter a bug into bugzilla.mozilla.org for the <SPAN >&#13; Enter a bug into bugzilla.mozilla.org for the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"<A >"<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla" HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
...@@ -3659,7 +3815,7 @@ TARGET="_top" ...@@ -3659,7 +3815,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Upload your patch as a unified DIFF (having used "diff -u" against >&#13; Upload your patch as a unified DIFF (having used "diff -u" against
the <EM the <EM
>current sources</EM >current sources</EM
> checked out of CVS), > checked out of CVS),
...@@ -3672,7 +3828,7 @@ TARGET="_top" ...@@ -3672,7 +3828,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Announce your patch and the associated URL >&#13; Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in
the newsgroup (netscape.public.mozilla.webtools). You'll get a really the newsgroup (netscape.public.mozilla.webtools). You'll get a really
good, fairly immediate reaction to the implications of your patch, good, fairly immediate reaction to the implications of your patch,
...@@ -3682,14 +3838,14 @@ TARGET="_top" ...@@ -3682,14 +3838,14 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> If it passes muster with minimal modification, the person to whom >&#13; If it passes muster with minimal modification, the person to whom
the bug is assigned in Bugzilla is responsible for seeing the patch the bug is assigned in Bugzilla is responsible for seeing the patch
is checked into CVS. is checked into CVS.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Bask in the glory of the fact that you helped write the most successful >&#13; Bask in the glory of the fact that you helped write the most successful
open-source bug-tracking software on the planet :) open-source bug-tracking software on the planet :)
</P </P
></LI ></LI
...@@ -3715,7 +3871,7 @@ WIDTH="33%" ...@@ -3715,7 +3871,7 @@ WIDTH="33%"
ALIGN="left" ALIGN="left"
VALIGN="top" VALIGN="top"
><A ><A
HREF="variant_sourceforge.html" HREF="variant-sourceforge.html"
>Prev</A >Prev</A
></TD ></TD
><TD ><TD
......
docs/html/feedback.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Translations" TITLE="Translations"
HREF="translations.html"></HEAD HREF="translations.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,26 +66,26 @@ HREF="translations.html" ...@@ -66,26 +66,26 @@ HREF="translations.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="FEEDBACK" NAME="feedback"
>1.7. Feedback</A >1.7. Feedback</A
></H1 ></H1
><P ><P
> I welcome feedback on this document. Without your submissions >&#13; I welcome feedback on this document. Without your submissions
and input, this Guide cannot continue to exist. Please mail and input, this Guide cannot continue to exist. Please mail
additions, comments, criticisms, etc. to additions, comments, criticisms, etc. to
<TT <TT
CLASS="EMAIL" CLASS="email"
>&#60;<A >&#60;<A
HREF="mailto:barnboy@trilobyte.net" HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A >barnboy@trilobyte.net</A
>&#62;</TT >&#62;</TT
>. Please send flames to >. Please send flames to
<TT <TT
CLASS="EMAIL" CLASS="email"
>&#60;<A >&#60;<A
HREF="mailto:devnull@localhost" HREF="mailto:devnull@localhost"
>devnull@localhost</A >devnull@localhost</A
......
docs/html/future.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Bugzilla Variants and Competitors" TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD HREF="variants.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,29 +63,29 @@ HREF="variants.html" ...@@ -63,29 +63,29 @@ HREF="variants.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="FUTURE" NAME="future"
>Chapter 6. The Future of Bugzilla</A >Chapter 6. The Future of Bugzilla</A
></H1 ></H1
><TABLE ><TABLE
BORDER="0" BORDER="0"
BGCOLOR="#6495ED" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="SYNOPSIS" CLASS="synopsis"
>Bugzilla's Future. Much of this is the present, now.</PRE >Bugzilla's Future. Much of this is the present, now.</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
></TABLE ></TABLE
><P ><P
> Bugzilla's future is a constantly-changing thing, as various developers >&#13; Bugzilla's future is a constantly-changing thing, as various developers
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"scratch an itch"</SPAN >"scratch an itch"</SPAN
...@@ -95,9 +95,10 @@ CLASS="QUOTE" ...@@ -95,9 +95,10 @@ CLASS="QUOTE"
not quite as readable as the rest of the Guide. not quite as readable as the rest of the Guide.
</P </P
><P ><P
> <P >&#13; <P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Bugzilla&nbsp;Blue&nbsp;Sky<br> ><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Bugzilla&nbsp;Blue&nbsp;Sky<br>
<br> <br>
Customisability<br> Customisability<br>
<br> <br>
......
docs/html/geninstall.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Win32 Installation Notes" TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD HREF="win32.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,28 +66,28 @@ HREF="win32.html" ...@@ -66,28 +66,28 @@ HREF="win32.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="GENINSTALL" NAME="geninstall"
>3.5. Installation General Notes</A >3.5. Installation General Notes</A
></H1 ></H1
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN941" NAME="AEN941"
>3.5.1. Modifying Your Running System</A >3.5.1. Modifying Your Running System</A
></H2 ></H2
><P ><P
> Bugzilla optimizes database lookups by storing all relatively static >&#13; Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory information in the versioncache file, located in the data/ subdirectory
under your installation directory. under your installation directory.
</P </P
><P ><P
> If you make a change to the structural data in your database >&#13; If you make a change to the structural data in your database
(the versions table for example), or to the (the versions table for example), or to the
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -101,66 +101,66 @@ CLASS="QUOTE" ...@@ -101,66 +101,66 @@ CLASS="QUOTE"
changes won't show up. changes won't show up.
</P </P
><P ><P
> That file gets automatically regenerated whenever it's more than an >&#13; That file gets automatically regenerated whenever it's more than an
hour old, so Bugzilla will eventually notice your changes by itself, but hour old, so Bugzilla will eventually notice your changes by itself, but
generally you want it to notice right away, so that you can test things. generally you want it to notice right away, so that you can test things.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN948" NAME="AEN948"
>3.5.2. Upgrading From Previous Versions</A >3.5.2. Upgrading From Previous Versions</A
></H2 ></H2
><P ><P
> The developers of Bugzilla are constantly adding new tables, columns and >&#13; The developers of Bugzilla are constantly adding new tables, columns and
fields. You'll get SQL errors if you just update the code. The strategy fields. You'll get SQL errors if you just update the code. The strategy
to update is to simply always run the checksetup.pl script whenever to update is to simply always run the checksetup.pl script whenever
you upgrade your installation of Bugzilla. If you want to see what has you upgrade your installation of Bugzilla. If you want to see what has
changed, you can read the comments in that file, starting from the end. changed, you can read the comments in that file, starting from the end.
</P </P
><P ><P
> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to >&#13; If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
the latest version, please consult the file, "UPGRADING-pre-2.8" in the the latest version, please consult the file, "UPGRADING-pre-2.8" in the
Bugzilla root directory after untarring the archive. Bugzilla root directory after untarring the archive.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="HTACCESS" NAME="htaccess"
>3.5.3. <TT >3.5.3. <TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> files and security</A > files and security</A
></H2 ></H2
><P ><P
> To enhance the security of your Bugzilla installation, >&#13; To enhance the security of your Bugzilla installation,
Bugzilla will generate Bugzilla will generate
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
></I ></I
> files > files
which the Apache webserver can use to restrict access to which the Apache webserver can use to restrict access to
the bugzilla data files. The checksetup script will the bugzilla data files. The checksetup script will
generate the <TT generate the <TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> files. > files.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -176,19 +176,19 @@ ALT="Note"></TD ...@@ -176,19 +176,19 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you are using an alternate provider of >&#13; If you are using an alternate provider of
<SPAN <SPAN
CLASS="PRODUCTNAME" CLASS="productname"
>webdot</SPAN >webdot</SPAN
> services for graphing > services for graphing
(as described when viewing (as described when viewing
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editparams.cgi</TT >editparams.cgi</TT
> in your web > in your web
browser), you will need to change the ip address in browser), you will need to change the ip address in
<TT <TT
CLASS="FILENAME" CLASS="filename"
>data/webdot/.htaccess</TT >data/webdot/.htaccess</TT
> to the ip > to the ip
address of the webdot server that you are using. address of the webdot server that you are using.
...@@ -201,22 +201,81 @@ CLASS="FILENAME" ...@@ -201,22 +201,81 @@ CLASS="FILENAME"
</P </P
><P ><P
> If you are using Internet Information Server or other web >&#13; The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration.
Be sure to check the &#60;Directory&#62; entries for your
Bugzilla directory so that the <TT
CLASS="filename"
>.htaccess</TT
>
file is allowed to override web server defaults. For instance,
let's assume your installation of Bugzilla is installed to
<TT
CLASS="filename"
>/usr/local/bugzilla</TT
>. You should have
this &#60;Directory&#62; entry in your <TT
CLASS="filename"
>httpd.conf</TT
>
file:
</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
&#60;Directory /usr/local/bugzilla/&#62;
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
&#60;/Directory&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13; The important part above is <SPAN
CLASS="QUOTE"
>"AllowOverride All"</SPAN
>.
Without that, the <TT
CLASS="filename"
>.htaccess</TT
> file created by
<TT
CLASS="filename"
>checksetup.pl</TT
> will not have sufficient
permissions to protect your Bugzilla installation.
</P
><P
>&#13; If you are using Internet Information Server or other web
server which does not observe <TT server which does not observe <TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> >
conventions, you can disable their creation by editing conventions, you can disable their creation by editing
<TT <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
> and setting the > and setting the
<TT <TT
CLASS="VARNAME" CLASS="varname"
>$create_htaccess</TT >$create_htaccess</TT
> variable to > variable to
<TT <TT
CLASS="PARAMETER" CLASS="parameter"
><I ><I
>0</I >0</I
></TT ></TT
...@@ -224,23 +283,23 @@ CLASS="PARAMETER" ...@@ -224,23 +283,23 @@ CLASS="PARAMETER"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="MOD_THROTTLE" NAME="mod-throttle"
>3.5.4. <TT >3.5.4. <TT
CLASS="FILENAME" CLASS="filename"
>mod_throttle</TT >mod_throttle</TT
> and Security</A > and Security</A
></H2 ></H2
><P ><P
> It is possible for a user, by mistake or on purpose, to access >&#13; It is possible for a user, by mistake or on purpose, to access
the database many times in a row which can result in very slow the database many times in a row which can result in very slow
access speeds for other users. If your Bugzilla installation access speeds for other users. If your Bugzilla installation
is experiencing this problem , you may install the Apache is experiencing this problem , you may install the Apache
module <TT module <TT
CLASS="FILENAME" CLASS="filename"
>mod_throttle</TT >mod_throttle</TT
> which can limit > which can limit
connections by ip-address. You may download this module at connections by ip-address. You may download this module at
...@@ -251,7 +310,7 @@ TARGET="_top" ...@@ -251,7 +310,7 @@ TARGET="_top"
>. Follow the instructions to install into your Apache install. <EM >. Follow the instructions to install into your Apache install. <EM
>This module only functions with the Apache web server!</EM >This module only functions with the Apache web server!</EM
>. You may use the <B >. You may use the <B
CLASS="COMMAND" CLASS="command"
>ThrottleClientIP</B >ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A > command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/" HREF="http://www.snert.com/Software/Throttle/"
...@@ -260,11 +319,11 @@ TARGET="_top" ...@@ -260,11 +319,11 @@ TARGET="_top"
> for more information. </P > for more information. </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CONTENT_TYPE" NAME="content-type"
>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A >3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></H2 ></H2
><P ><P
...@@ -286,8 +345,8 @@ WIDTH="100%" ...@@ -286,8 +345,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ >&#13;bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' &#62;$i.tmp; \ do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' &#62;$i.tmp; \
mv $i.tmp $i; done mv $i.tmp $i; done
</PRE </PRE
...@@ -297,7 +356,7 @@ CLASS="PROGRAMLISTING" ...@@ -297,7 +356,7 @@ CLASS="PROGRAMLISTING"
></TABLE ></TABLE
></P ></P
><P ><P
> All this one-liner command does is search for all instances of >&#13; All this one-liner command does is search for all instances of
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Content-type: text/html"</SPAN >"Content-type: text/html"</SPAN
...@@ -319,20 +378,20 @@ CLASS="QUOTE" ...@@ -319,20 +378,20 @@ CLASS="QUOTE"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="UNIXHISTORY" NAME="unixhistory"
>3.5.6. UNIX Installation Instructions History</A >3.5.6. UNIX Installation Instructions History</A
></H2 ></H2
><P ><P
> This document was originally adapted from the Bonsai >&#13; This document was originally adapted from the Bonsai
installation instructions by Terry Weissman installation instructions by Terry Weissman
&#60;terry@mozilla.org&#62;. &#60;terry@mozilla.org&#62;.
</P </P
><P ><P
> The February 25, 1999 re-write of this page was done by Ry4an >&#13; The February 25, 1999 re-write of this page was done by Ry4an
Brase &#60;ry4an@ry4an.org&#62;, with some edits by Terry Brase &#60;ry4an@ry4an.org&#62;, with some edits by Terry
Weissman, Bryce Nesbitt, Martin Pool, &#38; Dan Mosedale (But Weissman, Bryce Nesbitt, Martin Pool, &#38; Dan Mosedale (But
don't send bug reports to them; report them using bugzilla, at <A don't send bug reports to them; report them using bugzilla, at <A
...@@ -342,19 +401,19 @@ TARGET="_top" ...@@ -342,19 +401,19 @@ TARGET="_top"
> ). > ).
</P </P
><P ><P
> This document was heavily modified again Wednesday, March 07 >&#13; This document was heavily modified again Wednesday, March 07
2001 to reflect changes for Bugzilla 2.12 release by Matthew 2001 to reflect changes for Bugzilla 2.12 release by Matthew
P. Barnson. The securing MySQL section should be changed to P. Barnson. The securing MySQL section should be changed to
become standard procedure for Bugzilla installations. become standard procedure for Bugzilla installations.
</P </P
><P ><P
> Finally, the README in its entirety was marked up in SGML and >&#13; Finally, the README in its entirety was marked up in SGML and
included into the Guide on April 24, 2001 by Matt Barnson. included into the Guide on April 24, 2001 by Matt Barnson.
Since that time, it's undergone extensive modification as Since that time, it's undergone extensive modification as
Bugzilla grew. Bugzilla grew.
</P </P
><P ><P
> Comments from people using this Guide for the first time are >&#13; Comments from people using this Guide for the first time are
particularly welcome. particularly welcome.
</P </P
></DIV ></DIV
......
docs/html/gfdl-0.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-0"
>0. PREAMBLE</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-1.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-1"
>1. APPLICABILITY AND DEFINITIONS</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-0.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-2.html"
>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"
>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/gfdl-10.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="TERMINATION"
HREF="gfdl-9.html"><LINK
REL="NEXT"
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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-9.html"
>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-howto.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-10"
>10. FUTURE REVISIONS OF THIS LICENSE</A
></H1
><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"
>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="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-9.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-howto.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>TERMINATION</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How to use this License for your documents</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/gfdl-2.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-2"
>2. VERBATIM COPYING</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-1.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-3.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-3"
>3. COPYING IN QUANTITY</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-2.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-4.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-4"
>4. MODIFICATIONS</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-3.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-5.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-5"
>5. COMBINING DOCUMENTS</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-4.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-6.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-6"
>6. COLLECTIONS OF DOCUMENTS</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-5.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-7.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-7"
>7. AGGREGATION WITH INDEPENDENT WORKS</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-6.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-8.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-8"
>8. TRANSLATION</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-7.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-9.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-9"
>9. TERMINATION</A
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-8.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-10.html"
>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"
>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 @ d7f38125
<HTML
><HEAD
><TITLE
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><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="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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"
>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"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-howto"
>How to use this License for your documents</A
></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="AEN2673"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13; 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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-10.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="glossary.html"
>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"
>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
View file @ d7f38125
...@@ -14,9 +14,9 @@ TITLE="Hacking Bugzilla" ...@@ -14,9 +14,9 @@ TITLE="Hacking Bugzilla"
HREF="bzhacking.html"><LINK HREF="bzhacking.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="PREAMBLE" TITLE="PREAMBLE"
HREF="gfdl_0.html"></HEAD HREF="gfdl-0.html"></HEAD
><BODY ><BODY
CLASS="APPENDIX" CLASS="appendix"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -54,7 +54,7 @@ WIDTH="10%" ...@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right" ALIGN="right"
VALIGN="bottom" VALIGN="bottom"
><A ><A
HREF="gfdl_0.html" HREF="gfdl-0.html"
>Next</A >Next</A
></TD ></TD
></TR ></TR
...@@ -63,10 +63,10 @@ HREF="gfdl_0.html" ...@@ -63,10 +63,10 @@ HREF="gfdl_0.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="APPENDIX" CLASS="appendix"
><H1 ><H1
><A ><A
NAME="GFDL" NAME="gfdl"
>Appendix E. GNU Free Documentation License</A >Appendix E. GNU Free Documentation License</A
></H1 ></H1
><DIV ><DIV
...@@ -78,62 +78,62 @@ CLASS="TOC" ...@@ -78,62 +78,62 @@ CLASS="TOC"
></DT ></DT
><DT ><DT
>0. <A >0. <A
HREF="gfdl_0.html" HREF="gfdl-0.html"
>PREAMBLE</A >PREAMBLE</A
></DT ></DT
><DT ><DT
>1. <A >1. <A
HREF="gfdl_1.html" HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A >APPLICABILITY AND DEFINITIONS</A
></DT ></DT
><DT ><DT
>2. <A >2. <A
HREF="gfdl_2.html" HREF="gfdl-2.html"
>VERBATIM COPYING</A >VERBATIM COPYING</A
></DT ></DT
><DT ><DT
>3. <A >3. <A
HREF="gfdl_3.html" HREF="gfdl-3.html"
>COPYING IN QUANTITY</A >COPYING IN QUANTITY</A
></DT ></DT
><DT ><DT
>4. <A >4. <A
HREF="gfdl_4.html" HREF="gfdl-4.html"
>MODIFICATIONS</A >MODIFICATIONS</A
></DT ></DT
><DT ><DT
>5. <A >5. <A
HREF="gfdl_5.html" HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A >COMBINING DOCUMENTS</A
></DT ></DT
><DT ><DT
>6. <A >6. <A
HREF="gfdl_6.html" HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A >COLLECTIONS OF DOCUMENTS</A
></DT ></DT
><DT ><DT
>7. <A >7. <A
HREF="gfdl_7.html" HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A >AGGREGATION WITH INDEPENDENT WORKS</A
></DT ></DT
><DT ><DT
>8. <A >8. <A
HREF="gfdl_8.html" HREF="gfdl-8.html"
>TRANSLATION</A >TRANSLATION</A
></DT ></DT
><DT ><DT
>9. <A >9. <A
HREF="gfdl_9.html" HREF="gfdl-9.html"
>TERMINATION</A >TERMINATION</A
></DT ></DT
><DT ><DT
>10. <A >10. <A
HREF="gfdl_10.html" HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A >FUTURE REVISIONS OF THIS LICENSE</A
></DT ></DT
><DT ><DT
><A ><A
HREF="gfdl_howto.html" HREF="gfdl-howto.html"
>How to use this License for your documents</A >How to use this License for your documents</A
></DT ></DT
></DL ></DL
...@@ -141,7 +141,7 @@ HREF="gfdl_howto.html" ...@@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P ><P
>Version 1.1, March 2000</P >Version 1.1, March 2000</P
><A ><A
NAME="AEN2550" NAME="AEN2583"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
...@@ -183,7 +183,7 @@ WIDTH="33%" ...@@ -183,7 +183,7 @@ WIDTH="33%"
ALIGN="right" ALIGN="right"
VALIGN="top" VALIGN="top"
><A ><A
HREF="gfdl_0.html" HREF="gfdl-0.html"
>Next</A >Next</A
></TD ></TD
></TR ></TR
......
docs/html/glossary.html
View file @ d7f38125
...@@ -11,9 +11,9 @@ TITLE="The Bugzilla Guide" ...@@ -11,9 +11,9 @@ TITLE="The Bugzilla Guide"
HREF="index.html"><LINK HREF="index.html"><LINK
REL="PREVIOUS" REL="PREVIOUS"
TITLE="How to use this License for your documents" TITLE="How to use this License for your documents"
HREF="gfdl_howto.html"></HEAD HREF="gfdl-howto.html"></HEAD
><BODY ><BODY
CLASS="GLOSSARY" CLASS="glossary"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -38,7 +38,7 @@ WIDTH="10%" ...@@ -38,7 +38,7 @@ WIDTH="10%"
ALIGN="left" ALIGN="left"
VALIGN="bottom" VALIGN="bottom"
><A ><A
HREF="gfdl_howto.html" HREF="gfdl-howto.html"
>Prev</A >Prev</A
></TD ></TD
><TD ><TD
...@@ -60,15 +60,15 @@ WIDTH="100%"></DIV ...@@ -60,15 +60,15 @@ WIDTH="100%"></DIV
CLASS="GLOSSARY" CLASS="GLOSSARY"
><H1 ><H1
><A ><A
NAME="GLOSSARY" NAME="glossary"
>Glossary</A >Glossary</A
></H1 ></H1
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="AEN2645" NAME="AEN2678"
>0-9, high ascii</A >0-9, high ascii</A
></H1 ></H1
><DL ><DL
...@@ -78,17 +78,17 @@ NAME="AEN2645" ...@@ -78,17 +78,17 @@ NAME="AEN2645"
></DT ></DT
><DD ><DD
><P ><P
> Apache web server, and other NCSA-compliant web servers, >&#13; Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories observe the convention of using files in directories
called <TT called <TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> files. These > files. These
restrict parameters of the web server. In Bugzilla, they restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the otherwise compromise your installation. For instance, the
<TT <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
> file contains the > file contains the
password to your database. If this information were password to your database. If this information were
...@@ -100,11 +100,11 @@ CLASS="FILENAME" ...@@ -100,11 +100,11 @@ CLASS="FILENAME"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_A" NAME="gloss-a"
>A</A >A</A
></H1 ></H1
><DL ><DL
...@@ -117,7 +117,7 @@ NAME="GLOSS_A" ...@@ -117,7 +117,7 @@ NAME="GLOSS_A"
>In this context, Apache is the web server most >In this context, Apache is the web server most
commonly used for serving up commonly used for serving up
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Bugzilla</I >Bugzilla</I
> pages. Contrary to > pages. Contrary to
popular belief, the apache web server has nothing to do popular belief, the apache web server has nothing to do
...@@ -128,18 +128,18 @@ CLASS="QUOTE" ...@@ -128,18 +128,18 @@ CLASS="QUOTE"
>"a patchy"</SPAN >"a patchy"</SPAN
> version of the original > version of the original
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>NCSA</SPAN >NCSA</SPAN
> world-wide-web server.</P > world-wide-web server.</P
></DD ></DD
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_B" NAME="gloss-b"
>B</A >B</A
></H1 ></H1
><DL ><DL
...@@ -149,7 +149,7 @@ NAME="GLOSS_B" ...@@ -149,7 +149,7 @@ NAME="GLOSS_B"
></DT ></DT
><DD ><DD
><P ><P
> A <SPAN >&#13; A <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Bug"</SPAN >"Bug"</SPAN
> in Bugzilla refers to an issue > in Bugzilla refers to an issue
...@@ -171,7 +171,7 @@ CLASS="QUOTE" ...@@ -171,7 +171,7 @@ CLASS="QUOTE"
></DT ></DT
><DD ><DD
><P ><P
> Each Bugzilla Bug is assigned a number that uniquely >&#13; Each Bugzilla Bug is assigned a number that uniquely
identifies that Bug. The Bug associated with a Bug Number identifies that Bug. The Bug associated with a Bug Number
can be pulled up via a query, or easily from the very can be pulled up via a query, or easily from the very
front page by typing the number in the "Find" box. front page by typing the number in the "Find" box.
...@@ -201,31 +201,31 @@ CLASS="QUOTE" ...@@ -201,31 +201,31 @@ CLASS="QUOTE"
></DT ></DT
><DD ><DD
><P ><P
> Bugzilla is the industry-standard bug tracking system. It >&#13; Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts. is quite popular among Open Source enthusiasts.
</P </P
></DD ></DD
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_C" NAME="gloss-c"
></A ></A
></H1 ></H1
><DL ><DL
><DT ><DT
><A ><A
NAME="GLOSS_COMPONENT" NAME="gloss-component"
><B ><B
>Component</B >Component</B
></A ></A
></DT ></DT
><DD ><DD
><P ><P
> A Component is a subsection of a Product. It should be a >&#13; A Component is a subsection of a Product. It should be a
narrow category, tailored to your organization. All narrow category, tailored to your organization. All
Products must contain at least one Component (and, as a Products must contain at least one Component (and, as a
matter of fact, creating a Product with no Components will matter of fact, creating a Product with no Components will
...@@ -234,10 +234,10 @@ NAME="GLOSS_COMPONENT" ...@@ -234,10 +234,10 @@ NAME="GLOSS_COMPONENT"
></DD ></DD
><DT ><DT
><A ><A
NAME="GLOSS_CPAN" NAME="gloss-cpan"
><B ><B
><SPAN ><SPAN
CLASS="ACRONYM" CLASS="acronym"
>CPAN</SPAN >CPAN</SPAN
></B ></B
></A ></A
...@@ -245,7 +245,7 @@ CLASS="ACRONYM" ...@@ -245,7 +245,7 @@ CLASS="ACRONYM"
><DD ><DD
><P ><P
><SPAN ><SPAN
CLASS="ACRONYM" CLASS="acronym"
>CPAN</SPAN >CPAN</SPAN
> stands for the > stands for the
<SPAN <SPAN
...@@ -254,7 +254,7 @@ CLASS="QUOTE" ...@@ -254,7 +254,7 @@ CLASS="QUOTE"
>. CPAN >. CPAN
maintains a large number of extremely useful maintains a large number of extremely useful
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Perl</I >Perl</I
> modules. By themselves, Perl > modules. By themselves, Perl
modules generally do nothing, but when used as part of a modules generally do nothing, but when used as part of a
...@@ -264,11 +264,11 @@ CLASS="GLOSSTERM" ...@@ -264,11 +264,11 @@ CLASS="GLOSSTERM"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_D" NAME="gloss-d"
>D</A >D</A
></H1 ></H1
><DL ><DL
...@@ -282,11 +282,11 @@ NAME="GLOSS_D" ...@@ -282,11 +282,11 @@ NAME="GLOSS_D"
background. In general, most daemons are started at boot background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on time via System V init scripts, or through RC scripts on
BSD-based systems. <I BSD-based systems. <I
CLASS="GLOSSTERM" CLASS="glossterm"
>mysqld</I >mysqld</I
>, the >, the
MySQL server, and <I MySQL server, and <I
CLASS="GLOSSTERM" CLASS="glossterm"
>apache</I >apache</I
>, a web >, a web
server, are generally run as daemons.</P server, are generally run as daemons.</P
...@@ -294,11 +294,11 @@ CLASS="GLOSSTERM" ...@@ -294,11 +294,11 @@ CLASS="GLOSSTERM"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_G" NAME="gloss-g"
></A ></A
></H1 ></H1
><DL ><DL
...@@ -316,32 +316,32 @@ CLASS="QUOTE" ...@@ -316,32 +316,32 @@ CLASS="QUOTE"
comes by lumping users into groups, and assigning those comes by lumping users into groups, and assigning those
groups certain privileges to groups certain privileges to
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Products</I >Products</I
> and > and
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Components</I >Components</I
> in the > in the
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Bugzilla</I >Bugzilla</I
> database.</P > database.</P
></DD ></DD
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_I" NAME="gloss-i"
>I</A >I</A
></H1 ></H1
><DL ><DL
><DT ><DT
><A ><A
NAME="GLOSS_INFINITELOOP" NAME="gloss-infiniteloop"
><B ><B
>Infinite Loop</B >Infinite Loop</B
></A ></A
...@@ -353,11 +353,11 @@ NAME="GLOSS_INFINITELOOP" ...@@ -353,11 +353,11 @@ NAME="GLOSS_INFINITELOOP"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_M" NAME="gloss-m"
>M</A >M</A
></H1 ></H1
><DL ><DL
...@@ -369,7 +369,7 @@ NAME="GLOSS_M" ...@@ -369,7 +369,7 @@ NAME="GLOSS_M"
><P ><P
>mysqld is the name of the >mysqld is the name of the
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>daemon</I >daemon</I
> for the MySQL database. In > for the MySQL database. In
general, it is invoked automatically through the use of general, it is invoked automatically through the use of
...@@ -380,11 +380,11 @@ CLASS="GLOSSTERM" ...@@ -380,11 +380,11 @@ CLASS="GLOSSTERM"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_P" NAME="gloss-p"
>P</A >P</A
></H1 ></H1
><DL ><DL
...@@ -400,9 +400,9 @@ NAME="GLOSS_P" ...@@ -400,9 +400,9 @@ NAME="GLOSS_P"
Security) for all bugs entered into components beneath Security) for all bugs entered into components beneath
it.</P it.</P
><DIV ><DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN2736" NAME="AEN2769"
></A ></A
><P ><P
><B ><B
...@@ -457,7 +457,7 @@ CLASS="QUOTE" ...@@ -457,7 +457,7 @@ CLASS="QUOTE"
of an interpreted scripting language (such as shell of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled script), combined with the speed and power of a compiled
language, such as C. <I language, such as C. <I
CLASS="GLOSSTERM" CLASS="glossterm"
>Bugzilla</I >Bugzilla</I
> is > is
maintained in Perl.</P maintained in Perl.</P
...@@ -465,11 +465,11 @@ CLASS="GLOSSTERM" ...@@ -465,11 +465,11 @@ CLASS="GLOSSTERM"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_Q" NAME="gloss-q"
>Q</A >Q</A
></H1 ></H1
><DL ><DL
...@@ -506,17 +506,17 @@ CLASS="QUOTE" ...@@ -506,17 +506,17 @@ CLASS="QUOTE"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_R" NAME="gloss-r"
>R</A >R</A
></H1 ></H1
><DL ><DL
><DT ><DT
><A ><A
NAME="GLOSS_RECURSION" NAME="gloss-recursion"
><B ><B
>Recursion</B >Recursion</B
></A ></A
...@@ -538,25 +538,25 @@ CLASS="QUOTE" ...@@ -538,25 +538,25 @@ CLASS="QUOTE"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_S" NAME="gloss-s"
>S</A >S</A
></H1 ></H1
><DL ><DL
><DT ><DT
><B ><B
><SPAN ><SPAN
CLASS="ACRONYM" CLASS="acronym"
>SGML</SPAN >SGML</SPAN
></B ></B
></DT ></DT
><DD ><DD
><P ><P
><SPAN ><SPAN
CLASS="ACRONYM" CLASS="acronym"
>SGML</SPAN >SGML</SPAN
> stands for <SPAN > stands for <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -566,14 +566,14 @@ CLASS="QUOTE" ...@@ -566,14 +566,14 @@ CLASS="QUOTE"
1980's to provide an extensible means to maintain 1980's to provide an extensible means to maintain
documentation based upon content instead of presentation, documentation based upon content instead of presentation,
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>SGML</SPAN >SGML</SPAN
> has withstood the test of time as > has withstood the test of time as
a robust, powerful language. a robust, powerful language.
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
><SPAN ><SPAN
CLASS="ACRONYM" CLASS="acronym"
>XML</SPAN >XML</SPAN
></I ></I
> is the > is the
...@@ -582,20 +582,20 @@ CLASS="QUOTE" ...@@ -582,20 +582,20 @@ CLASS="QUOTE"
>"baby brother"</SPAN >"baby brother"</SPAN
> of SGML; any valid > of SGML; any valid
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>XML</SPAN >XML</SPAN
> document it, by definition, a valid > document it, by definition, a valid
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>SGML</SPAN >SGML</SPAN
> document. The document you are > document. The document you are
reading is written and maintained in reading is written and maintained in
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>SGML</SPAN >SGML</SPAN
>, and is also valid >, and is also valid
<SPAN <SPAN
CLASS="ACRONYM" CLASS="acronym"
>XML</SPAN >XML</SPAN
> if you modify the Document Type > if you modify the Document Type
Definition.</P Definition.</P
...@@ -603,24 +603,24 @@ CLASS="ACRONYM" ...@@ -603,24 +603,24 @@ CLASS="ACRONYM"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_T" NAME="gloss-t"
>T</A >T</A
></H1 ></H1
><DL ><DL
><DT ><DT
><A ><A
NAME="GLOSS_TARGET_MILESTONE" NAME="gloss-target-milestone"
><B ><B
>Target Milestone</B >Target Milestone</B
></A ></A
></DT ></DT
><DD ><DD
><P ><P
> Target Milestones are Product goals. They are >&#13; Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software configurable on a per-Product basis. Most software
development houses have a concept of development houses have a concept of
<SPAN <SPAN
...@@ -636,17 +636,17 @@ CLASS="QUOTE" ...@@ -636,17 +636,17 @@ CLASS="QUOTE"
></DL ></DL
></DIV ></DIV
><DIV ><DIV
CLASS="GLOSSDIV" CLASS="glossdiv"
><H1 ><H1
CLASS="GLOSSDIV" CLASS="glossdiv"
><A ><A
NAME="GLOSS_Z" NAME="gloss-z"
>Z</A >Z</A
></H1 ></H1
><DL ><DL
><DT ><DT
><A ><A
NAME="ZARRO-BOOGS-FOUND" NAME="zarro-boogs-found"
><B ><B
>Zarro Boogs Found</B >Zarro Boogs Found</B
></A ></A
...@@ -675,7 +675,7 @@ WIDTH="33%" ...@@ -675,7 +675,7 @@ WIDTH="33%"
ALIGN="left" ALIGN="left"
VALIGN="top" VALIGN="top"
><A ><A
HREF="gfdl_howto.html" HREF="gfdl-howto.html"
>Prev</A >Prev</A
></TD ></TD
><TD ><TD
......
docs/html/granttables.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla" TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD HREF="patches.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,19 +66,19 @@ HREF="patches.html" ...@@ -66,19 +66,19 @@ HREF="patches.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="GRANTTABLES" NAME="granttables"
>C.3. MySQL Permissions &#38; Grant Tables</A >C.3. MySQL Permissions &#38; Grant Tables</A
></H1 ></H1
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -107,7 +107,7 @@ VALIGN="TOP" ...@@ -107,7 +107,7 @@ VALIGN="TOP"
troubles to work on : ) Although it is of limited use, it troubles to work on : ) Although it is of limited use, it
still has SOME use, thus it's still included.</P still has SOME use, thus it's still included.</P
><P ><P
> Please note, however, that I was a relatively new user to >&#13; Please note, however, that I was a relatively new user to
MySQL at the time. Some of my suggestions, particularly in MySQL at the time. Some of my suggestions, particularly in
how to set up security, showed a terrible lack of how to set up security, showed a terrible lack of
security-related database experience. security-related database experience.
...@@ -117,8 +117,9 @@ VALIGN="TOP" ...@@ -117,8 +117,9 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>From&nbsp;matt_barnson@singletrac.com&nbsp;Wed&nbsp;Jul&nbsp;&nbsp;7&nbsp;09:00:07&nbsp;1999<br> ><br>
From&nbsp;matt_barnson@singletrac.com&nbsp;Wed&nbsp;Jul&nbsp;&nbsp;7&nbsp;09:00:07&nbsp;1999<br>
Date:&nbsp;Mon,&nbsp;1&nbsp;Mar&nbsp;1999&nbsp;21:37:04&nbsp;-0700&nbsp;<br> Date:&nbsp;Mon,&nbsp;1&nbsp;Mar&nbsp;1999&nbsp;21:37:04&nbsp;-0700&nbsp;<br>
From:&nbsp;Matthew&nbsp;Barnson&nbsp;matt_barnson@singletrac.com<br> From:&nbsp;Matthew&nbsp;Barnson&nbsp;matt_barnson@singletrac.com<br>
To:&nbsp;keystone-users@homeport.org<br> To:&nbsp;keystone-users@homeport.org<br>
......
docs/html/how.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Where can I find my user preferences?" TITLE="Where can I find my user preferences?"
HREF="init4me.html"></HEAD HREF="init4me.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="init4me.html" ...@@ -66,11 +66,11 @@ HREF="init4me.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="HOW" NAME="how"
>2.3. How do I use Bugzilla?</A >2.3. How do I use Bugzilla?</A
></H1 ></H1
><TABLE ><TABLE
...@@ -97,7 +97,7 @@ VALIGN="TOP" ...@@ -97,7 +97,7 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><P ><P
> Bugzilla is a large, complex system. Describing how to use it >&#13; Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide. Installing and Administering Bugzilla portions of this Guide.
...@@ -107,19 +107,19 @@ VALIGN="TOP" ...@@ -107,19 +107,19 @@ VALIGN="TOP"
software. software.
</P </P
><P ><P
> Throughout this portion of the Guide, we will refer to user >&#13; Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation, account options available at the Bugzilla test installation,
<A <A
HREF="http://landfill.tequilarista.org/" HREF="http://landfill.tequilarista.org/"
TARGET="_top" TARGET="_top"
> landfill.tequilarista.org</A >&#13; landfill.tequilarista.org</A
>. >.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -135,7 +135,7 @@ ALT="Note"></TD ...@@ -135,7 +135,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Some people have run into difficulties completing this >&#13; Some people have run into difficulties completing this
tutorial. If you run into problems, please check the tutorial. If you run into problems, please check the
updated online documentation available at <A updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/" HREF="http://www.trilobyte.net/barnsons/"
...@@ -160,15 +160,15 @@ TARGET="_top" ...@@ -160,15 +160,15 @@ TARGET="_top"
mentioned here. mentioned here.
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="MYACCOUNT" NAME="myaccount"
>2.3.1. Create a Bugzilla Account</A >2.3.1. Create a Bugzilla Account</A
></H2 ></H2
><P ><P
> First things first! If you want to use Bugzilla, first you >&#13; First things first! If you want to use Bugzilla, first you
need to create an account. Consult with the administrator need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you responsible for your installation of Bugzilla for the URL you
should use to access it. If you're test-driving the end-user should use to access it. If you're test-driving the end-user
...@@ -184,19 +184,19 @@ TARGET="_top" ...@@ -184,19 +184,19 @@ TARGET="_top"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Click the "Open a new Bugzilla account" link. >&#13; Click the "Open a new Bugzilla account" link.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Enter your "E-mail address" and "Real Name" (or whatever >&#13; Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided, name you want to call yourself) in the spaces provided,
then select the "Create Account" button. then select the "Create Account" button.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Within moments, you should receive an email to the address >&#13; Within moments, you should receive an email to the address
you provided above, which contains your login name you provided above, which contains your login name
(generally the same as the email address), and a password (generally the same as the email address), and a password
you can use to access your account. This password is you can use to access your account. This password is
...@@ -206,7 +206,7 @@ TYPE="1" ...@@ -206,7 +206,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Click the <SPAN >&#13; Click the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Log In"</SPAN >"Log In"</SPAN
> link in the yellow area at > link in the yellow area at
...@@ -224,12 +224,12 @@ CLASS="QUOTE" ...@@ -224,12 +224,12 @@ CLASS="QUOTE"
>"Login"</SPAN >"Login"</SPAN
>. >.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -244,7 +244,7 @@ ALT="Note"></TD ...@@ -244,7 +244,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you ever forget your password, you can come back to >&#13; If you ever forget your password, you can come back to
this page, enter your <SPAN this page, enter your <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"E-mail address"</SPAN >"E-mail address"</SPAN
...@@ -262,12 +262,12 @@ CLASS="QUOTE" ...@@ -262,12 +262,12 @@ CLASS="QUOTE"
></DIV ></DIV
> >
<DIV <DIV
CLASS="CAUTION" CLASS="caution"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="CAUTION" CLASS="caution"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -282,7 +282,7 @@ ALT="Caution"></TD ...@@ -282,7 +282,7 @@ ALT="Caution"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Many modern browsers include an >&#13; Many modern browsers include an
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Auto-Complete"</SPAN >"Auto-Complete"</SPAN
...@@ -307,7 +307,7 @@ CLASS="QUOTE" ...@@ -307,7 +307,7 @@ CLASS="QUOTE"
></LI ></LI
></OL ></OL
><P ><P
> Congratulations! If you followed these directions, you now >&#13; Congratulations! If you followed these directions, you now
are the proud owner of a user account on are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the install. You should now see in your browser a page called the
...@@ -319,46 +319,46 @@ CLASS="QUOTE" ...@@ -319,46 +319,46 @@ CLASS="QUOTE"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="QUERY" NAME="query"
>2.3.2. The Bugzilla Query Page</A >2.3.2. The Bugzilla Query Page</A
></H2 ></H2
><P ><P
> The Bugzilla Query Page is the heart and soul of the Bugzilla >&#13; The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug Bugzilla system. We'll go into how to create your own bug
report later on. report later on.
</P </P
><P ><P
> There are efforts underway to simplify query usage. If you >&#13; There are efforts underway to simplify query usage. If you
have a local installation of Bugzilla 2.12 or higher, you have a local installation of Bugzilla 2.12 or higher, you
should have <TT should have <TT
CLASS="FILENAME" CLASS="filename"
>quicksearch.html</TT >quicksearch.html</TT
> available to > available to
use and simplify your searches. There is also a helper for use and simplify your searches. There is also a helper for
the query interface, called the query interface, called
<TT <TT
CLASS="FILENAME" CLASS="filename"
>queryhelp.cgi</TT >queryhelp.cgi</TT
>. Landfill tends to run the >. Landfill tends to run the
latest code, so these two utilities should be available there latest code, so these two utilities should be available there
for your perusal. for your perusal.
</P </P
><P ><P
> At this point, please visit the main Bugzilla site, >&#13; At this point, let's visit the query page.
<A <A
HREF="http://bugzilla.mozilla.org/query.cgi" HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
TARGET="_top" TARGET="_top"
> bugzilla.mozilla.org</A >&#13; landfill.tequilarista.org/bugzilla-tip/query.cgi</A
>, to see a more fleshed-out query page. >
</P </P
><P ><P
> The first thing you need to notice about the Bugzilla Query >&#13; The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should the upper-left-hand corner of your browser window you should
...@@ -368,7 +368,7 @@ CLASS="QUOTE" ...@@ -368,7 +368,7 @@ CLASS="QUOTE"
> underlined. Select it. > underlined. Select it.
</P </P
><P ><P
> Notice the page that popped up? Every underlined word you see >&#13; Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface what everything here does. To return to the query interface
...@@ -379,7 +379,7 @@ CLASS="QUOTE" ...@@ -379,7 +379,7 @@ CLASS="QUOTE"
button in your browser. button in your browser.
</P </P
><P ><P
> I'm sure that after checking out the online help, you are now >&#13; I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the few successful queries to find out what there are in the
...@@ -391,7 +391,7 @@ CLASS="QUOTE" ...@@ -391,7 +391,7 @@ CLASS="QUOTE"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Ensure you are back on the <SPAN >&#13; Ensure you are back on the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"Bugzilla Query >"Bugzilla Query
Page"</SPAN Page"</SPAN
...@@ -407,7 +407,7 @@ CLASS="QUOTE" ...@@ -407,7 +407,7 @@ CLASS="QUOTE"
figured out. figured out.
</P </P
><P ><P
> Basically, selecting <EM >&#13; Basically, selecting <EM
>anything</EM >anything</EM
> on the > on the
query page narrows your search down. Leaving stuff query page narrows your search down. Leaving stuff
...@@ -416,7 +416,7 @@ CLASS="QUOTE" ...@@ -416,7 +416,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> You see the box immediately below the top six boxes that >&#13; You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to "Assigned To" checked by default? This allows you to
...@@ -424,12 +424,12 @@ CLASS="QUOTE" ...@@ -424,12 +424,12 @@ CLASS="QUOTE"
put my email address in there, and see what happens. put my email address in there, and see what happens.
</P </P
><P ><P
> Type "barnboy@trilobyte.net" in the top Email text box. >&#13; Type "barnboy@trilobyte.net" in the top Email text box.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Let's narrow the search some more. Scroll down until you >&#13; Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it. find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only This is where we can narrow our search down to only
specific products (software programs or product lines) in specific products (software programs or product lines) in
...@@ -443,13 +443,13 @@ CLASS="QUOTE" ...@@ -443,13 +443,13 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> Did you notice that some of the boxes to the right changed >&#13; Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product) when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a associated with it. A "Version" is the number of a
software program. software program.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN307" NAME="AEN307"
></A ></A
...@@ -458,14 +458,14 @@ NAME="AEN307" ...@@ -458,14 +458,14 @@ NAME="AEN307"
>Example 2-1. Some Famous Software Versions</B >Example 2-1. Some Famous Software Versions</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN309" NAME="AEN309"
></A ></A
><P ><P
></P ></P
><P ><P
> Do you remember the hype in 1995 when Microsoft >&#13; Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software. advertising this new Version of their software.
...@@ -475,7 +475,7 @@ NAME="AEN309" ...@@ -475,7 +475,7 @@ NAME="AEN309"
ME(Millenium Edition)(r). ME(Millenium Edition)(r).
</P </P
><P ><P
> Software "Versions" help a manufacturer >&#13; Software "Versions" help a manufacturer
differentiate their current product from their differentiate their current product from their
previous products. Most do not identify their previous products. Most do not identify their
products by the year they were released. Instead, products by the year they were released. Instead,
...@@ -492,7 +492,7 @@ NAME="AEN309" ...@@ -492,7 +492,7 @@ NAME="AEN309"
version than 1.1.1. version than 1.1.1.
</P </P
><P ><P
> In general, a "Version" in Bugzilla should refer to >&#13; In general, a "Version" in Bugzilla should refer to
<EM <EM
>released</EM >released</EM
> products, not products > products, not products
...@@ -507,13 +507,13 @@ NAME="AEN309" ...@@ -507,13 +507,13 @@ NAME="AEN309"
> >
</P </P
><P ><P
> A "Component" is a piece of a Product. >&#13; A "Component" is a piece of a Product.
It may be a standalone program, or some other logical It may be a standalone program, or some other logical
division of a Product or Program. division of a Product or Program.
Normally, a Component has a single Owner, who is responsible Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component. for overseeing efforts to improve that Component.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN317" NAME="AEN317"
></A ></A
...@@ -522,14 +522,14 @@ NAME="AEN317" ...@@ -522,14 +522,14 @@ NAME="AEN317"
>Example 2-2. Mozilla's Bugzilla Components</B >Example 2-2. Mozilla's Bugzilla Components</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN319" NAME="AEN319"
></A ></A
><P ><P
></P ></P
><P ><P
> Mozilla's "Bugzilla" Product is composed of several pieces (Components): >&#13; Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<P <P
></P ></P
><TABLE ><TABLE
...@@ -542,35 +542,35 @@ BORDER="0" ...@@ -542,35 +542,35 @@ BORDER="0"
>, >,
Administration of a bugzilla installation, including Administration of a bugzilla installation, including
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editcomponents.cgi</TT >editcomponents.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editgroups.cgi</TT >editgroups.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editkeywords.cgi</TT >editkeywords.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editparams.cgi</TT >editparams.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editproducts.cgi</TT >editproducts.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editusers.cgi</TT >editusers.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>editversions.cgi,</TT >editversions.cgi,</TT
> and > and
<TT <TT
CLASS="FILENAME" CLASS="filename"
>sanitycheck.cgi</TT >sanitycheck.cgi</TT
>. >.
</TD </TD
...@@ -591,19 +591,19 @@ CLASS="FILENAME" ...@@ -591,19 +591,19 @@ CLASS="FILENAME"
>, >,
Creating, changing, and viewing bugs. Creating, changing, and viewing bugs.
<TT <TT
CLASS="FILENAME" CLASS="filename"
>enter_bug.cgi</TT >enter_bug.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>post_bug.cgi</TT >post_bug.cgi</TT
>, >,
<TT <TT
CLASS="FILENAME" CLASS="filename"
>show_bug.cgi</TT >show_bug.cgi</TT
> and > and
<TT <TT
CLASS="FILENAME" CLASS="filename"
>process_bug.cgi</TT >process_bug.cgi</TT
>. >.
</TD </TD
...@@ -615,7 +615,7 @@ CLASS="FILENAME" ...@@ -615,7 +615,7 @@ CLASS="FILENAME"
>, >,
The bugzilla documentation, including anything in the The bugzilla documentation, including anything in the
<TT <TT
CLASS="FILENAME" CLASS="filename"
>docs/</TT >docs/</TT
> directory and The Bugzilla Guide > directory and The Bugzilla Guide
(This document :) (This document :)
...@@ -628,7 +628,7 @@ CLASS="FILENAME" ...@@ -628,7 +628,7 @@ CLASS="FILENAME"
>, >,
Anything to do with email sent by Bugzilla. Anything to do with email sent by Bugzilla.
<TT <TT
CLASS="FILENAME" CLASS="filename"
>processmail</TT >processmail</TT
> >
</TD </TD
...@@ -640,7 +640,7 @@ CLASS="FILENAME" ...@@ -640,7 +640,7 @@ CLASS="FILENAME"
>, >,
The installation process of Bugzilla. This includes The installation process of Bugzilla. This includes
<TT <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
> and whatever else it evolves into. > and whatever else it evolves into.
</TD </TD
...@@ -652,11 +652,11 @@ CLASS="FILENAME" ...@@ -652,11 +652,11 @@ CLASS="FILENAME"
>, >,
Anything to do with searching for bugs and viewing the buglists. Anything to do with searching for bugs and viewing the buglists.
<TT <TT
CLASS="FILENAME" CLASS="filename"
>query.cgi</TT >query.cgi</TT
> and > and
<TT <TT
CLASS="FILENAME" CLASS="filename"
>buglist.cgi</TT >buglist.cgi</TT
> >
</TD </TD
...@@ -668,11 +668,11 @@ CLASS="FILENAME" ...@@ -668,11 +668,11 @@ CLASS="FILENAME"
>, >,
Getting reports from Bugzilla. Getting reports from Bugzilla.
<TT <TT
CLASS="FILENAME" CLASS="filename"
>reports.cgi</TT >reports.cgi</TT
> and > and
<TT <TT
CLASS="FILENAME" CLASS="filename"
>duplicates.cgi</TT >duplicates.cgi</TT
> >
</TD </TD
...@@ -684,7 +684,7 @@ CLASS="FILENAME" ...@@ -684,7 +684,7 @@ CLASS="FILENAME"
>, >,
Anything about managing a user account from the user's perspective. Anything about managing a user account from the user's perspective.
<TT <TT
CLASS="FILENAME" CLASS="filename"
>userprefs.cgi</TT >userprefs.cgi</TT
>, saved queries, creating accounts, >, saved queries, creating accounts,
changing passwords, logging in, etc. changing passwords, logging in, etc.
...@@ -712,7 +712,7 @@ CLASS="FILENAME" ...@@ -712,7 +712,7 @@ CLASS="FILENAME"
> >
</P </P
><P ><P
> A "Milestone", or "Target Milestone" is a often a planned >&#13; A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though, future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a Milestones simply represent significant dates for a
developer. Having certain features in your Product is developer. Having certain features in your Product is
...@@ -727,7 +727,7 @@ CLASS="FILENAME" ...@@ -727,7 +727,7 @@ CLASS="FILENAME"
of reach by the time the important day arrives. of reach by the time the important day arrives.
</P </P
><P ><P
> The Bugzilla Project has set up Milestones for future >&#13; The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date, Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19". code name, or weird alphanumeric combination, like "M19".
...@@ -735,19 +735,19 @@ CLASS="FILENAME" ...@@ -735,19 +735,19 @@ CLASS="FILENAME"
></LI ></LI
><LI ><LI
><P ><P
> OK, now let's select the "Bugzilla" component from its scrollbox. >&#13; OK, now let's select the "Bugzilla" component from its scrollbox.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Skip down the page a bit -- do you see the "submit query" button? >&#13; Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run Select it, and let's run
this query! this query!
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Congratulations! You've completed your first Query, and >&#13; Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide, have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on well, you'll have a cryptic "Zarro Boogs Found" message on
...@@ -759,7 +759,7 @@ CLASS="FILENAME" ...@@ -759,7 +759,7 @@ CLASS="FILENAME"
></LI ></LI
></OL ></OL
><P ><P
> I encourage you to click the bug numbers in the left-hand >&#13; I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the you to context-sensitive help here, but instead sort the
...@@ -768,7 +768,7 @@ CLASS="FILENAME" ...@@ -768,7 +768,7 @@ CLASS="FILENAME"
this is a tremendous timesaver. this is a tremendous timesaver.
</P </P
><P ><P
> A couple more interesting things about the Bug List page: >&#13; A couple more interesting things about the Bug List page:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -817,11 +817,11 @@ BORDER="0" ...@@ -817,11 +817,11 @@ BORDER="0"
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -837,7 +837,7 @@ ALT="Note"></TD ...@@ -837,7 +837,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> There are many more options to the Bugzilla Query Page and >&#13; There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to enough for you to learn to get around. I encourage you to
check out the <A check out the <A
...@@ -852,11 +852,11 @@ TARGET="_top" ...@@ -852,11 +852,11 @@ TARGET="_top"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BUGREPORTS" NAME="bugreports"
>2.3.3. Creating and Managing Bug Reports</A >2.3.3. Creating and Managing Bug Reports</A
></H2 ></H2
><TABLE ><TABLE
...@@ -885,15 +885,15 @@ VALIGN="TOP" ...@@ -885,15 +885,15 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BUG_WRITING" NAME="bug-writing"
>2.3.3.1. Writing a Great Bug Report</A >2.3.3.1. Writing a Great Bug Report</A
></H3 ></H3
><P ><P
> Before we plunge into writing your first bug report, I >&#13; Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to or un-tarred Bugzilla distribution, you should be able to
...@@ -908,7 +908,7 @@ TARGET="_top" ...@@ -908,7 +908,7 @@ TARGET="_top"
>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you. >. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</P </P
><P ><P
> While you are at it, why not learn how to find previously >&#13; While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <A on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html" HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
...@@ -917,7 +917,7 @@ TARGET="_top" ...@@ -917,7 +917,7 @@ TARGET="_top"
>. >.
</P </P
><P ><P
> I realize this was a lot to read. However, understanding >&#13; I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on the mentality of writing great bug reports will help us on
the next part! the next part!
</P </P
...@@ -927,7 +927,7 @@ TARGET="_top" ...@@ -927,7 +927,7 @@ TARGET="_top"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Go back to <A >&#13; Go back to <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/" HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top" TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A > http://landfill.tequilarista.org/bugzilla-tip/</A
...@@ -936,7 +936,7 @@ TARGET="_top" ...@@ -936,7 +936,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Select the <A >&#13; Select the <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi" HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top" TARGET="_top"
> Enter a new bug report</A > Enter a new bug report</A
...@@ -945,12 +945,12 @@ TARGET="_top" ...@@ -945,12 +945,12 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Select a product. >&#13; Select a product.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Now you should be at the "Enter Bug" form. The >&#13; Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for "reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again -- you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password, you did keep the email with your username and password,
...@@ -959,12 +959,12 @@ TARGET="_top" ...@@ -959,12 +959,12 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Select a Component in the scrollbox. >&#13; Select a Component in the scrollbox.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Bugzilla should have made reasonable guesses, based upon >&#13; Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know! an SGI box running IRIX, we want to know!
...@@ -972,7 +972,7 @@ TARGET="_top" ...@@ -972,7 +972,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Fill in the "Assigned To" box with the email address you >&#13; Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's copies of your bug to lots of other people, since it's
just a test bug. just a test bug.
...@@ -980,33 +980,33 @@ TARGET="_top" ...@@ -980,33 +980,33 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Leave the "CC" text box blank. Fill in the "URL" box >&#13; Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org". with "http://www.mozilla.org".
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Enter "The Bugzilla Guide" in the Summary text box, and >&#13; Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the place any comments you have on this tutorial, or the
Guide in general, into the Description box. Guide in general, into the Description box.
</P </P
></LI ></LI
></OL ></OL
><P ><P
> Voila! Select "Commit" and send in your bug report! Next >&#13; Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs. we'll look at resolving bugs.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BUG_MANAGE" NAME="bug-manage"
>2.3.3.2. Managing your Bug Reports</A >2.3.3.2. Managing your Bug Reports</A
></H3 ></H3
><P ><P
> OK, you should have a link to the bug you just created near >&#13; OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this a link to the right saying "Back to BUG# XXXX". Select this
link. link.
...@@ -1017,7 +1017,7 @@ NAME="BUG_MANAGE" ...@@ -1017,7 +1017,7 @@ NAME="BUG_MANAGE"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Scroll down a bit on the subsequent page, until you see >&#13; Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box). the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case, ASSIGNED)", fix it, and then resolve. But in this case,
...@@ -1029,7 +1029,7 @@ TYPE="1" ...@@ -1029,7 +1029,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Hey! It said it couldn't take the change in a big red >&#13; Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with browser, add a Comment, then try Resolving the bug with
...@@ -1038,40 +1038,40 @@ TYPE="1" ...@@ -1038,40 +1038,40 @@ TYPE="1"
></LI ></LI
></OL ></OL
><P ><P
> You have now learned the basics of Bugzilla navigation, >&#13; You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them! explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there. this point on, so you are on your own there.
</P </P
><P ><P
> But I'll give a few last hints! >&#13; But I'll give a few last hints!
</P </P
><P ><P
> There is a <A >&#13; There is a <A
HREF="http://bugzilla.mozilla.org/help.html" HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html"
TARGET="_top" TARGET="_top"
>CLUE</A >CLUE</A
> on the Query page that will teach you more how to use the form. > on the Query page that will teach you more how to use the form.
</P </P
><P ><P
> If you click the hyperlink on the <A >&#13; If you click the hyperlink on the <A
HREF="http://bugzilla.mozilla.org/describecomponents.cgi" HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi"
TARGET="_top" TARGET="_top"
>Component</A >Component</A
> box of the Query page, you will be presented a form that will describe what all the components are. > box of the Query page, you will be presented a form that will describe what all the components are.
</P </P
><P ><P
> Possibly the most powerful feature of the Query page is the >&#13; Possibly the most powerful feature of the Query page is the
<A <A
HREF="http://bugzilla.mozilla.org/booleanchart.html" HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
TARGET="_top" TARGET="_top"
>Boolean Chart</A >Boolean Chart</A
> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. > section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P </P
><P ><P
> Finally, you can build some nifty <A >&#13; Finally, you can build some nifty <A
HREF="http://bugzilla.mozilla.org/reports.cgi" HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi"
TARGET="_top" TARGET="_top"
>Reports</A >Reports</A
> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. > using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
......
docs/html/index.html
View file @ d7f38125
...@@ -28,7 +28,7 @@ CONTENT="Mozilla"><META ...@@ -28,7 +28,7 @@ CONTENT="Mozilla"><META
NAME="KEYWORD" NAME="KEYWORD"
CONTENT="webtools"></HEAD CONTENT="webtools"></HEAD
><BODY ><BODY
CLASS="BOOK" CLASS="book"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -37,48 +37,48 @@ ALINK="#0000FF" ...@@ -37,48 +37,48 @@ ALINK="#0000FF"
><DIV ><DIV
CLASS="BOOK" CLASS="BOOK"
><A ><A
NAME="INDEX" NAME="index"
></A ></A
><DIV ><DIV
CLASS="TITLEPAGE" CLASS="TITLEPAGE"
><H1 ><H1
CLASS="TITLE" CLASS="title"
><A ><A
NAME="AEN2" NAME="AEN2"
>The Bugzilla Guide</A >The Bugzilla Guide</A
></H1 ></H1
><H3 ><H3
CLASS="AUTHOR" CLASS="author"
><A ><A
NAME="AEN27" NAME="AEN27"
>Matthew P. Barnson</A >Matthew P. Barnson</A
></H3 ></H3
><DIV ><DIV
CLASS="AFFILIATION" CLASS="affiliation"
><DIV ><DIV
CLASS="ADDRESS" CLASS="address"
><P ><P
CLASS="ADDRESS" CLASS="address"
>barnboy@trilobyte.net</P >barnboy@trilobyte.net</P
></DIV ></DIV
></DIV ></DIV
><SPAN ><SPAN
CLASS="COLLAB" CLASS="collab"
><SPAN ><SPAN
CLASS="COLLABNAME" CLASS="collabname"
>Zach Lipton</SPAN >Zach Lipton</SPAN
><DIV ><DIV
CLASS="AFFILIATION" CLASS="affiliation"
><DIV ><DIV
CLASS="ADDRESS" CLASS="address"
><P ><P
CLASS="ADDRESS" CLASS="address"
>zach AT zachlipton DOT com</P >zach AT zachlipton DOT com</P
></DIV ></DIV
></DIV ></DIV
><BR></SPAN ><BR></SPAN
><DIV ><DIV
CLASS="REVHISTORY" CLASS="revhistory"
><TABLE ><TABLE
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
...@@ -184,30 +184,30 @@ COLSPAN="3" ...@@ -184,30 +184,30 @@ COLSPAN="3"
></DIV ></DIV
><DIV ><DIV
><DIV ><DIV
CLASS="ABSTRACT" CLASS="abstract"
><A ><A
NAME="AEN39" NAME="AEN39"
></A ></A
><P ><P
></P ></P
><P ><P
> This is the documentation for Bugzilla, the Mozilla >&#13; This is the documentation for Bugzilla, the Mozilla
bug-tracking system. bug-tracking system.
</P </P
><P ><P
> Bugzilla is an enterprise-class set of software utilities >&#13; Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs. organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is very While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified for installing and maintaining this software is a qualified
professional on operating system upon which you install professional for the operating system upon which you install
Bugzilla. Bugzilla.
</P </P
><P ><P
> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. >&#13; THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML! ADDITIONS TO THE GUIDE WRITTEN IN HTML!
...@@ -304,29 +304,29 @@ HREF="how.html" ...@@ -304,29 +304,29 @@ HREF="how.html"
><DL ><DL
><DT ><DT
>2.3.1. <A >2.3.1. <A
HREF="how.html#MYACCOUNT" HREF="how.html#myaccount"
>Create a Bugzilla Account</A >Create a Bugzilla Account</A
></DT ></DT
><DT ><DT
>2.3.2. <A >2.3.2. <A
HREF="how.html#QUERY" HREF="how.html#query"
>The Bugzilla Query Page</A >The Bugzilla Query Page</A
></DT ></DT
><DT ><DT
>2.3.3. <A >2.3.3. <A
HREF="how.html#BUGREPORTS" HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A >Creating and Managing Bug Reports</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>2.3.3.1. <A >2.3.3.1. <A
HREF="how.html#BUG_WRITING" HREF="how.html#bug-writing"
>Writing a Great Bug Report</A >Writing a Great Bug Report</A
></DT ></DT
><DT ><DT
>2.3.3.2. <A >2.3.3.2. <A
HREF="how.html#BUG_MANAGE" HREF="how.html#bug-manage"
>Managing your Bug Reports</A >Managing your Bug Reports</A
></DT ></DT
></DL ></DL
...@@ -342,41 +342,41 @@ HREF="init4me.html" ...@@ -342,41 +342,41 @@ HREF="init4me.html"
><DL ><DL
><DT ><DT
>2.4.1. <A >2.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS" HREF="init4me.html#accountsettings"
>Account Settings</A >Account Settings</A
></DT ></DT
><DT ><DT
>2.4.2. <A >2.4.2. <A
HREF="init4me.html#EMAILSETTINGS" HREF="init4me.html#emailsettings"
>Email Settings</A >Email Settings</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>2.4.2.1. <A >2.4.2.1. <A
HREF="init4me.html#NOTIFICATION" HREF="init4me.html#notification"
>Email Notification</A >Email Notification</A
></DT ></DT
><DT ><DT
>2.4.2.2. <A >2.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH" HREF="init4me.html#newemailtech"
>New Email Technology</A >New Email Technology</A
></DT ></DT
><DT ><DT
>2.4.2.3. <A >2.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS" HREF="init4me.html#watchsettings"
>"Watching" Users</A >"Watching" Users</A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>2.4.3. <A >2.4.3. <A
HREF="init4me.html#FOOTERSETTINGS" HREF="init4me.html#footersettings"
>Page Footer</A >Page Footer</A
></DT ></DT
><DT ><DT
>2.4.4. <A >2.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS" HREF="init4me.html#permissionsettings"
>Permissions</A >Permissions</A
></DT ></DT
></DL ></DL
...@@ -419,12 +419,12 @@ HREF="stepbystep.html#AEN515" ...@@ -419,12 +419,12 @@ HREF="stepbystep.html#AEN515"
></DT ></DT
><DT ><DT
>3.2.3. <A >3.2.3. <A
HREF="stepbystep.html#INSTALL-MYSQL" HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A >Installing MySQL Database</A
></DT ></DT
><DT ><DT
>3.2.4. <A >3.2.4. <A
HREF="stepbystep.html#INSTALL-PERL" HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A >Perl (5.004 or greater)</A
></DT ></DT
><DT ><DT
...@@ -481,7 +481,7 @@ HREF="stepbystep.html#AEN721" ...@@ -481,7 +481,7 @@ HREF="stepbystep.html#AEN721"
>3.2.15. <A >3.2.15. <A
HREF="stepbystep.html#AEN768" HREF="stepbystep.html#AEN768"
>Tweaking <TT >Tweaking <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
></A ></A
></DT ></DT
...@@ -536,28 +536,28 @@ HREF="geninstall.html#AEN948" ...@@ -536,28 +536,28 @@ HREF="geninstall.html#AEN948"
></DT ></DT
><DT ><DT
>3.5.3. <A >3.5.3. <A
HREF="geninstall.html#HTACCESS" HREF="geninstall.html#htaccess"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> files and security</A > files and security</A
></DT ></DT
><DT ><DT
>3.5.4. <A >3.5.4. <A
HREF="geninstall.html#MOD_THROTTLE" HREF="geninstall.html#mod-throttle"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>mod_throttle</TT >mod_throttle</TT
> and Security</A > and Security</A
></DT ></DT
><DT ><DT
>3.5.5. <A >3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE" HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A >Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT ></DT
><DT ><DT
>3.5.6. <A >3.5.6. <A
HREF="geninstall.html#UNIXHISTORY" HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A >UNIX Installation Instructions History</A
></DT ></DT
></DL ></DL
...@@ -571,17 +571,17 @@ HREF="win32.html" ...@@ -571,17 +571,17 @@ HREF="win32.html"
><DL ><DL
><DT ><DT
>3.6.1. <A >3.6.1. <A
HREF="win32.html#WININSTALL" HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A >Win32 Installation: Step-by-step</A
></DT ></DT
><DT ><DT
>3.6.2. <A >3.6.2. <A
HREF="win32.html#ADDLWINTIPS" HREF="win32.html#addlwintips"
>Additional Windows Tips</A >Additional Windows Tips</A
></DT ></DT
><DT ><DT
>3.6.3. <A >3.6.3. <A
HREF="win32.html#BZLDAP" HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A >Bugzilla LDAP Integration</A
></DT ></DT
></DL ></DL
...@@ -609,34 +609,34 @@ HREF="useradmin.html" ...@@ -609,34 +609,34 @@ HREF="useradmin.html"
><DL ><DL
><DT ><DT
>4.2.1. <A >4.2.1. <A
HREF="useradmin.html#DEFAULTUSER" HREF="useradmin.html#defaultuser"
>Creating the Default User</A >Creating the Default User</A
></DT ></DT
><DT ><DT
>4.2.2. <A >4.2.2. <A
HREF="useradmin.html#MANAGEUSERS" HREF="useradmin.html#manageusers"
>Managing Other Users</A >Managing Other Users</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>4.2.2.1. <A >4.2.2.1. <A
HREF="useradmin.html#LOGIN" HREF="useradmin.html#login"
>Logging In</A >Logging In</A
></DT ></DT
><DT ><DT
>4.2.2.2. <A >4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS" HREF="useradmin.html#createnewusers"
>Creating new users</A >Creating new users</A
></DT ></DT
><DT ><DT
>4.2.2.3. <A >4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS" HREF="useradmin.html#disableusers"
>Disabling Users</A >Disabling Users</A
></DT ></DT
><DT ><DT
>4.2.2.4. <A >4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS" HREF="useradmin.html#modifyusers"
>Modifying Users</A >Modifying Users</A
></DT ></DT
></DL ></DL
...@@ -653,32 +653,32 @@ HREF="programadmin.html" ...@@ -653,32 +653,32 @@ HREF="programadmin.html"
><DL ><DL
><DT ><DT
>4.3.1. <A >4.3.1. <A
HREF="programadmin.html#PRODUCTS" HREF="programadmin.html#products"
>Products</A >Products</A
></DT ></DT
><DT ><DT
>4.3.2. <A >4.3.2. <A
HREF="programadmin.html#COMPONENTS" HREF="programadmin.html#components"
>Components</A >Components</A
></DT ></DT
><DT ><DT
>4.3.3. <A >4.3.3. <A
HREF="programadmin.html#VERSIONS" HREF="programadmin.html#versions"
>Versions</A >Versions</A
></DT ></DT
><DT ><DT
>4.3.4. <A >4.3.4. <A
HREF="programadmin.html#MILESTONES" HREF="programadmin.html#milestones"
>Milestones</A >Milestones</A
></DT ></DT
><DT ><DT
>4.3.5. <A >4.3.5. <A
HREF="programadmin.html#VOTING" HREF="programadmin.html#voting"
>Voting</A >Voting</A
></DT ></DT
><DT ><DT
>4.3.6. <A >4.3.6. <A
HREF="programadmin.html#GROUPS" HREF="programadmin.html#groups"
>Groups and Group Security</A >Groups and Group Security</A
></DT ></DT
></DL ></DL
...@@ -738,27 +738,27 @@ HREF="rhbugzilla.html" ...@@ -738,27 +738,27 @@ HREF="rhbugzilla.html"
></DT ></DT
><DT ><DT
>7.2. <A >7.2. <A
HREF="variant_fenris.html" HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A >Loki Bugzilla (Fenris)</A
></DT ></DT
><DT ><DT
>7.3. <A >7.3. <A
HREF="variant_issuezilla.html" HREF="variant-issuezilla.html"
>Issuezilla</A >Issuezilla</A
></DT ></DT
><DT ><DT
>7.4. <A >7.4. <A
HREF="variant_scarab.html" HREF="variant-scarab.html"
>Scarab</A >Scarab</A
></DT ></DT
><DT ><DT
>7.5. <A >7.5. <A
HREF="variant_perforce.html" HREF="variant-perforce.html"
>Perforce SCM</A >Perforce SCM</A
></DT ></DT
><DT ><DT
>7.6. <A >7.6. <A
HREF="variant_sourceforge.html" HREF="variant-sourceforge.html"
>SourceForge</A >SourceForge</A
></DT ></DT
></DL ></DL
...@@ -794,14 +794,14 @@ HREF="dbdoc.html" ...@@ -794,14 +794,14 @@ HREF="dbdoc.html"
><DL ><DL
><DT ><DT
>C.2.1. <A >C.2.1. <A
HREF="dbdoc.html#AEN2331" HREF="dbdoc.html#AEN2340"
>Bugzilla Database Basics</A >Bugzilla Database Basics</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>C.2.1.1. <A >C.2.1.1. <A
HREF="dbdoc.html#AEN2360" HREF="dbdoc.html#AEN2369"
>Bugzilla Database Tables</A >Bugzilla Database Tables</A
></DT ></DT
></DL ></DL
...@@ -826,7 +826,7 @@ HREF="patches.html" ...@@ -826,7 +826,7 @@ HREF="patches.html"
>D.1. <A >D.1. <A
HREF="rewrite.html" HREF="rewrite.html"
>Apache <TT >Apache <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> magic</A > magic</A
></DT ></DT
...@@ -854,12 +854,12 @@ HREF="bzhacking.html" ...@@ -854,12 +854,12 @@ HREF="bzhacking.html"
><DL ><DL
><DT ><DT
>D.5.1. <A >D.5.1. <A
HREF="bzhacking.html#AEN2495" HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A >Things that have caused problems and should be avoided</A
></DT ></DT
><DT ><DT
>D.5.2. <A >D.5.2. <A
HREF="bzhacking.html#AEN2509" HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A >Coding Style for Bugzilla</A
></DT ></DT
></DL ></DL
...@@ -875,62 +875,62 @@ HREF="gfdl.html" ...@@ -875,62 +875,62 @@ HREF="gfdl.html"
><DL ><DL
><DT ><DT
>0. <A >0. <A
HREF="gfdl_0.html" HREF="gfdl-0.html"
>PREAMBLE</A >PREAMBLE</A
></DT ></DT
><DT ><DT
>1. <A >1. <A
HREF="gfdl_1.html" HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A >APPLICABILITY AND DEFINITIONS</A
></DT ></DT
><DT ><DT
>2. <A >2. <A
HREF="gfdl_2.html" HREF="gfdl-2.html"
>VERBATIM COPYING</A >VERBATIM COPYING</A
></DT ></DT
><DT ><DT
>3. <A >3. <A
HREF="gfdl_3.html" HREF="gfdl-3.html"
>COPYING IN QUANTITY</A >COPYING IN QUANTITY</A
></DT ></DT
><DT ><DT
>4. <A >4. <A
HREF="gfdl_4.html" HREF="gfdl-4.html"
>MODIFICATIONS</A >MODIFICATIONS</A
></DT ></DT
><DT ><DT
>5. <A >5. <A
HREF="gfdl_5.html" HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A >COMBINING DOCUMENTS</A
></DT ></DT
><DT ><DT
>6. <A >6. <A
HREF="gfdl_6.html" HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A >COLLECTIONS OF DOCUMENTS</A
></DT ></DT
><DT ><DT
>7. <A >7. <A
HREF="gfdl_7.html" HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A >AGGREGATION WITH INDEPENDENT WORKS</A
></DT ></DT
><DT ><DT
>8. <A >8. <A
HREF="gfdl_8.html" HREF="gfdl-8.html"
>TRANSLATION</A >TRANSLATION</A
></DT ></DT
><DT ><DT
>9. <A >9. <A
HREF="gfdl_9.html" HREF="gfdl-9.html"
>TERMINATION</A >TERMINATION</A
></DT ></DT
><DT ><DT
>10. <A >10. <A
HREF="gfdl_10.html" HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A >FUTURE REVISIONS OF THIS LICENSE</A
></DT ></DT
><DT ><DT
><A ><A
HREF="gfdl_howto.html" HREF="gfdl-howto.html"
>How to use this License for your documents</A >How to use this License for your documents</A
></DT ></DT
></DL ></DL
...@@ -972,58 +972,58 @@ HREF="stepbystep.html#AEN799" ...@@ -972,58 +972,58 @@ HREF="stepbystep.html#AEN799"
></DT ></DT
><DT ><DT
>3-3. <A >3-3. <A
HREF="win32.html#AEN1038" HREF="win32.html#AEN1048"
>Installing ActivePerl ppd Modules on Microsoft Windows</A >Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT ></DT
><DT ><DT
>3-4. <A >3-4. <A
HREF="win32.html#AEN1224" HREF="win32.html#AEN1233"
>Removing encrypt() for Windows NT Bugzilla version >Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A 2.12 or earlier</A
></DT ></DT
><DT ><DT
>4-1. <A >4-1. <A
HREF="programadmin.html#AEN1461" HREF="programadmin.html#AEN1470"
>Creating some Components</A >Creating some Components</A
></DT ></DT
><DT ><DT
>4-2. <A >4-2. <A
HREF="programadmin.html#AEN1490" HREF="programadmin.html#AEN1499"
>Common Use of Versions</A >Common Use of Versions</A
></DT ></DT
><DT ><DT
>4-3. <A >4-3. <A
HREF="programadmin.html#AEN1494" HREF="programadmin.html#AEN1503"
>A Different Use of Versions</A >A Different Use of Versions</A
></DT ></DT
><DT ><DT
>4-4. <A >4-4. <A
HREF="programadmin.html#AEN1522" HREF="programadmin.html#AEN1531"
>Using SortKey with Target Milestone</A >Using SortKey with Target Milestone</A
></DT ></DT
><DT ><DT
>4-5. <A >4-5. <A
HREF="programadmin.html#AEN1558" HREF="programadmin.html#AEN1567"
>When to Use Group Security</A >When to Use Group Security</A
></DT ></DT
><DT ><DT
>4-6. <A >4-6. <A
HREF="programadmin.html#AEN1575" HREF="programadmin.html#AEN1584"
>Creating a New Group</A >Creating a New Group</A
></DT ></DT
><DT ><DT
>4-7. <A >4-7. <A
HREF="programadmin.html#AEN1592" HREF="programadmin.html#AEN1601"
>Bugzilla Groups</A >Bugzilla Groups</A
></DT ></DT
><DT ><DT
>D-1. <A >D-1. <A
HREF="setperl.html#AEN2439" HREF="setperl.html#AEN2448"
>Using Setperl to set your perl path</A >Using Setperl to set your perl path</A
></DT ></DT
><DT ><DT
>1. <A >1. <A
HREF="glossary.html#AEN2736" HREF="glossary.html#AEN2769"
>A Sample Product</A >A Sample Product</A
></DT ></DT
></DL ></DL
......
docs/html/init4me.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Using Bugzilla-Conclusion" TITLE="Using Bugzilla-Conclusion"
HREF="usingbz-conc.html"></HEAD HREF="usingbz-conc.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="usingbz-conc.html" ...@@ -66,11 +66,11 @@ HREF="usingbz-conc.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="INIT4ME" NAME="init4me"
>2.4. Where can I find my user preferences?</A >2.4. Where can I find my user preferences?</A
></H1 ></H1
><TABLE ><TABLE
...@@ -101,7 +101,7 @@ VALIGN="TOP" ...@@ -101,7 +101,7 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><P ><P
> Customized User Preferences offer tremendous versatility to your >&#13; Customized User Preferences offer tremendous versatility to your
individual Bugzilla experience. Let's plunge into what you can individual Bugzilla experience. Let's plunge into what you can
do! The first step is to click the "Edit prefs" link at the do! The first step is to click the "Edit prefs" link at the
footer of each page once you have logged in to <A footer of each page once you have logged in to <A
...@@ -111,15 +111,15 @@ TARGET="_top" ...@@ -111,15 +111,15 @@ TARGET="_top"
>. >.
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="ACCOUNTSETTINGS" NAME="accountsettings"
>2.4.1. Account Settings</A >2.4.1. Account Settings</A
></H2 ></H2
><P ><P
> On this page, you can change your basic Account Settings, >&#13; On this page, you can change your basic Account Settings,
including your password and full name. For security reasons, including your password and full name. For security reasons,
in order to change anything on this page you must type your in order to change anything on this page you must type your
<EM <EM
...@@ -146,23 +146,23 @@ CLASS="QUOTE" ...@@ -146,23 +146,23 @@ CLASS="QUOTE"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="EMAILSETTINGS" NAME="emailsettings"
>2.4.2. Email Settings</A >2.4.2. Email Settings</A
></H2 ></H2
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="NOTIFICATION" NAME="notification"
>2.4.2.1. Email Notification</A >2.4.2.1. Email Notification</A
></H3 ></H3
><P ><P
> Here you can reduce or increase the amount of email sent you >&#13; Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as from Bugzilla. Although this is referred to as
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -188,19 +188,19 @@ HREF="tinderbox.html" ...@@ -188,19 +188,19 @@ HREF="tinderbox.html"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="NEWEMAILTECH" NAME="newemailtech"
>2.4.2.2. New Email Technology</A >2.4.2.2. New Email Technology</A
></H3 ></H3
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -216,7 +216,7 @@ ALT="Note"></TD ...@@ -216,7 +216,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This option may not be available in all Bugzilla >&#13; This option may not be available in all Bugzilla
installations, depending upon the preferences of the installations, depending upon the preferences of the
systems administrator responsible for the setup of your systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality, Bugzilla. However, if you really want this functionality,
...@@ -229,13 +229,13 @@ VALIGN="TOP" ...@@ -229,13 +229,13 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> Disregard the warnings about "experimental and bleeding >&#13; Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and that historically used for Bugzilla is quite robust and
well-tested now. well-tested now.
</P </P
><P ><P
> I recommend you enable the option, "Click here to sign up >&#13; I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it. (and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a standard UNIX "diff" output, which is quite ugly, to a
...@@ -243,19 +243,19 @@ VALIGN="TOP" ...@@ -243,19 +243,19 @@ VALIGN="TOP"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="WATCHSETTINGS" NAME="watchsettings"
>2.4.2.3. "Watching" Users</A >2.4.2.3. "Watching" Users</A
></H3 ></H3
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -271,7 +271,7 @@ ALT="Note"></TD ...@@ -271,7 +271,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This option may not be available in all Bugzilla >&#13; This option may not be available in all Bugzilla
installations, depending upon the preferences of the installations, depending upon the preferences of the
systems administrator responsible for the setup of your systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality, Bugzilla. However, if you really want this functionality,
...@@ -282,7 +282,7 @@ VALIGN="TOP" ...@@ -282,7 +282,7 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> By entering user email names into the "Users to watch" text >&#13; By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to transitions as developers change projects, managers wish to
...@@ -294,19 +294,19 @@ VALIGN="TOP" ...@@ -294,19 +294,19 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="FOOTERSETTINGS" NAME="footersettings"
>2.4.3. Page Footer</A >2.4.3. Page Footer</A
></H2 ></H2
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -322,7 +322,7 @@ ALT="Note"></TD ...@@ -322,7 +322,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> By default, this page is quite barren. However, go explore >&#13; By default, this page is quite barren. However, go explore
the Query Page some more; you will find that you can store the Query Page some more; you will find that you can store
numerous queries on the server, so if you regularly run a numerous queries on the server, so if you regularly run a
particular query it is just a drop-down menu away. On this particular query it is just a drop-down menu away. On this
...@@ -334,7 +334,7 @@ VALIGN="TOP" ...@@ -334,7 +334,7 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> If you have many stored queries on the server, here you will >&#13; If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful footer of every page in Bugzilla! This gives you powerful
...@@ -342,11 +342,11 @@ VALIGN="TOP" ...@@ -342,11 +342,11 @@ VALIGN="TOP"
is an excellent way to impress your boss... is an excellent way to impress your boss...
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -380,15 +380,15 @@ VALIGN="TOP" ...@@ -380,15 +380,15 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="PERMISSIONSETTINGS" NAME="permissionsettings"
>2.4.4. Permissions</A >2.4.4. Permissions</A
></H2 ></H2
><P ><P
> This is a purely informative page which outlines your current >&#13; This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer. "other users" link appears on this page as well as the footer.
......
docs/html/installation.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="ERRATA" TITLE="ERRATA"
HREF="errata.html"></HEAD HREF="errata.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="errata.html" ...@@ -63,10 +63,10 @@ HREF="errata.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="INSTALLATION" NAME="installation"
>Chapter 3. Installation</A >Chapter 3. Installation</A
></H1 ></H1
><DIV ><DIV
...@@ -100,12 +100,12 @@ HREF="stepbystep.html#AEN515" ...@@ -100,12 +100,12 @@ HREF="stepbystep.html#AEN515"
></DT ></DT
><DT ><DT
>3.2.3. <A >3.2.3. <A
HREF="stepbystep.html#INSTALL-MYSQL" HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A >Installing MySQL Database</A
></DT ></DT
><DT ><DT
>3.2.4. <A >3.2.4. <A
HREF="stepbystep.html#INSTALL-PERL" HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A >Perl (5.004 or greater)</A
></DT ></DT
><DT ><DT
...@@ -162,7 +162,7 @@ HREF="stepbystep.html#AEN721" ...@@ -162,7 +162,7 @@ HREF="stepbystep.html#AEN721"
>3.2.15. <A >3.2.15. <A
HREF="stepbystep.html#AEN768" HREF="stepbystep.html#AEN768"
>Tweaking <TT >Tweaking <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
></A ></A
></DT ></DT
...@@ -217,28 +217,28 @@ HREF="geninstall.html#AEN948" ...@@ -217,28 +217,28 @@ HREF="geninstall.html#AEN948"
></DT ></DT
><DT ><DT
>3.5.3. <A >3.5.3. <A
HREF="geninstall.html#HTACCESS" HREF="geninstall.html#htaccess"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
> files and security</A > files and security</A
></DT ></DT
><DT ><DT
>3.5.4. <A >3.5.4. <A
HREF="geninstall.html#MOD_THROTTLE" HREF="geninstall.html#mod-throttle"
><TT ><TT
CLASS="FILENAME" CLASS="filename"
>mod_throttle</TT >mod_throttle</TT
> and Security</A > and Security</A
></DT ></DT
><DT ><DT
>3.5.5. <A >3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE" HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A >Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT ></DT
><DT ><DT
>3.5.6. <A >3.5.6. <A
HREF="geninstall.html#UNIXHISTORY" HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A >UNIX Installation Instructions History</A
></DT ></DT
></DL ></DL
...@@ -252,17 +252,17 @@ HREF="win32.html" ...@@ -252,17 +252,17 @@ HREF="win32.html"
><DL ><DL
><DT ><DT
>3.6.1. <A >3.6.1. <A
HREF="win32.html#WININSTALL" HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A >Win32 Installation: Step-by-step</A
></DT ></DT
><DT ><DT
>3.6.2. <A >3.6.2. <A
HREF="win32.html#ADDLWINTIPS" HREF="win32.html#addlwintips"
>Additional Windows Tips</A >Additional Windows Tips</A
></DT ></DT
><DT ><DT
>3.6.3. <A >3.6.3. <A
HREF="win32.html#BZLDAP" HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A >Bugzilla LDAP Integration</A
></DT ></DT
></DL ></DL
...@@ -270,7 +270,7 @@ HREF="win32.html#BZLDAP" ...@@ -270,7 +270,7 @@ HREF="win32.html#BZLDAP"
></DL ></DL
></DIV ></DIV
><P ><P
> These installation instructions are presented assuming you are >&#13; These installation instructions are presented assuming you are
installing on a UNIX or completely POSIX-compliant system. If installing on a UNIX or completely POSIX-compliant system. If
you are installing on Microsoft Windows or another oddball you are installing on Microsoft Windows or another oddball
operating system, please consult the appropriate sections in operating system, please consult the appropriate sections in
......
docs/html/integration.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Bonsai" TITLE="Bonsai"
HREF="bonsai.html"></HEAD HREF="bonsai.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="bonsai.html" ...@@ -63,10 +63,10 @@ HREF="bonsai.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="INTEGRATION" NAME="integration"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</A >Chapter 5. Integrating Bugzilla with Third-Party Tools</A
></H1 ></H1
><DIV ><DIV
......
docs/html/newversions.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Credits" TITLE="Credits"
HREF="credits.html"></HEAD HREF="credits.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,29 +66,29 @@ HREF="credits.html" ...@@ -66,29 +66,29 @@ HREF="credits.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="NEWVERSIONS" NAME="newversions"
>1.4. New Versions</A >1.4. New Versions</A
></H1 ></H1
><P ><P
> This is the 2.14 version of The Bugzilla Guide. If you are >&#13; This is the 2.14 version of The Bugzilla Guide. If you are
reading this from any source other than those below, please reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an check one of these mirrors to make sure you are reading an
up-to-date version of the Guide. up-to-date version of the Guide.
</P </P
><P ><P
> This document can be found in the following places: >&#13; This document can be found in the following places:
</P </P
><P ><P
> <P >&#13; <P
></P ></P
><UL ><UL
><LI ><LI
><P ><P
> <A >&#13; <A
HREF="http://www.trilobyte.net/barnsons/" HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top" TARGET="_top"
>TriloBYTE</A >TriloBYTE</A
...@@ -97,7 +97,7 @@ TARGET="_top" ...@@ -97,7 +97,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> <A >&#13; <A
HREF="http://www.mozilla.org/projects/bugzilla/" HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top" TARGET="_top"
>Mozilla.org</A >Mozilla.org</A
...@@ -106,7 +106,7 @@ TARGET="_top" ...@@ -106,7 +106,7 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> <A >&#13; <A
HREF="http://www.linuxdoc.org/" HREF="http://www.linuxdoc.org/"
TARGET="_top" TARGET="_top"
>The Linux >The Linux
...@@ -118,7 +118,7 @@ TARGET="_top" ...@@ -118,7 +118,7 @@ TARGET="_top"
> >
</P </P
><P ><P
> The latest version of this document can be checked out via CVS. >&#13; The latest version of this document can be checked out via CVS.
Please follow the instructions available at <A Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html" HREF="http://www.mozilla.org/cvs.html"
TARGET="_top" TARGET="_top"
......
docs/html/osx.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="BSD Installation Notes" TITLE="BSD Installation Notes"
HREF="bsdinstall.html"></HEAD HREF="bsdinstall.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,40 +66,40 @@ HREF="bsdinstall.html" ...@@ -66,40 +66,40 @@ HREF="bsdinstall.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="OSX" NAME="osx"
>3.3. Mac OS X Installation Notes</A >3.3. Mac OS X Installation Notes</A
></H1 ></H1
><P ><P
> There are a lot of common libraries and utilities out there >&#13; There are a lot of common libraries and utilities out there
that Apple did not include with Mac OS X, but which run that Apple did not include with Mac OS X, but which run
perfectly well on it. The GD library, which Bugzilla needs to perfectly well on it. The GD library, which Bugzilla needs to
do bug graphs, is one of these. do bug graphs, is one of these.
</P </P
><P ><P
> The easiest way to get a lot of these is with a program called >&#13; 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 Fink, which is similar in nature to the CPAN installer, but
installs common GNU utilities. Fink is available from installs common GNU utilities. Fink is available from
&#60;http://sourceforge.net/projects/fink/&#62;. &#60;http://sourceforge.net/projects/fink/&#62;.
</P </P
><P ><P
> Follow the instructions for setting up Fink. Once it's >&#13; Follow the instructions for setting up Fink. Once it's
installed, you'll want to run the following as root: installed, you'll want to run the following as root:
<B <B
CLASS="COMMAND" CLASS="command"
>fink install gd</B >fink install gd</B
> >
</P </P
><P ><P
> It will prompt you for a number of dependencies, type 'y' and >&#13; It will prompt you for a number of dependencies, type 'y' and
hit enter to install all of the dependencies. Then watch it hit enter to install all of the dependencies. Then watch it
work. work.
</P </P
><P ><P
> To prevent creating conflicts with the software that Apple >&#13; To prevent creating conflicts with the software that Apple
installs by default, Fink creates its own directory tree at installs by default, Fink creates its own directory tree at
/sw where it installs most of the software that it installs. /sw where it installs most of the software that it installs.
This means your libraries and headers for libgd will be at This means your libraries and headers for libgd will be at
...@@ -111,15 +111,15 @@ CLASS="COMMAND" ...@@ -111,15 +111,15 @@ CLASS="COMMAND"
:-) :-)
</P </P
><P ><P
> Instead of typing <SPAN >&#13; Instead of typing <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"install GD"</SPAN >"install GD"</SPAN
> at the > at the
<TT <TT
CLASS="PROMPT" CLASS="prompt"
>cpan&#62;</TT >cpan&#62;</TT
> prompt, type <B > prompt, type <B
CLASS="COMMAND" CLASS="command"
>look >look
GD</B GD</B
>. This should go through the motions of >. This should go through the motions of
...@@ -127,13 +127,13 @@ CLASS="COMMAND" ...@@ -127,13 +127,13 @@ CLASS="COMMAND"
open a shell and drop you into the build directory. Apply the open a shell and drop you into the build directory. Apply the
following patch to the Makefile.PL file (save the patch into a following patch to the Makefile.PL file (save the patch into a
file and use the command <B file and use the command <B
CLASS="COMMAND" CLASS="command"
>patch &#60; >patch &#60;
patchfile</B patchfile</B
>: >:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -142,8 +142,9 @@ WIDTH="100%" ...@@ -142,8 +142,9 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> >&#13;
--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000 --- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
+++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001 +++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
@@ -3,8 +3,8 @@ @@ -3,8 +3,8 @@
...@@ -176,7 +177,7 @@ CLASS="PROGRAMLISTING" ...@@ -176,7 +177,7 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><P ><P
> Then, run these commands to finish the installation of the perl module: >&#13; Then, run these commands to finish the installation of the perl module:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -185,35 +186,35 @@ BORDER="0" ...@@ -185,35 +186,35 @@ BORDER="0"
><TR ><TR
><TD ><TD
><B ><B
CLASS="COMMAND" CLASS="command"
>perl Makefile.PL</B >perl Makefile.PL</B
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
><B ><B
CLASS="COMMAND" CLASS="command"
>make</B >make</B
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
><B ><B
CLASS="COMMAND" CLASS="command"
>make test</B >make test</B
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
><B ><B
CLASS="COMMAND" CLASS="command"
>make install</B >make install</B
></TD ></TD
></TR ></TR
><TR ><TR
><TD ><TD
>And don't forget to run <B >And don't forget to run <B
CLASS="COMMAND" CLASS="command"
>exit</B >exit</B
> to get back to cpan.</TD > to get back to cpan.</TD
></TR ></TR
...@@ -224,7 +225,7 @@ CLASS="COMMAND" ...@@ -224,7 +225,7 @@ CLASS="COMMAND"
> >
</P </P
><P ><P
> Happy Hacking! >&#13; Happy Hacking!
</P </P
></DIV ></DIV
><DIV ><DIV
......
docs/html/patches.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Apache mod_rewrite magic" TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"></HEAD HREF="rewrite.html"></HEAD
><BODY ><BODY
CLASS="APPENDIX" CLASS="appendix"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="rewrite.html" ...@@ -63,10 +63,10 @@ HREF="rewrite.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="APPENDIX" CLASS="appendix"
><H1 ><H1
><A ><A
NAME="PATCHES" NAME="patches"
>Appendix D. Useful Patches and Utilities for Bugzilla</A >Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1 ></H1
><DIV ><DIV
...@@ -80,7 +80,7 @@ CLASS="TOC" ...@@ -80,7 +80,7 @@ CLASS="TOC"
>D.1. <A >D.1. <A
HREF="rewrite.html" HREF="rewrite.html"
>Apache <TT >Apache <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> magic</A > magic</A
></DT ></DT
...@@ -108,12 +108,12 @@ HREF="bzhacking.html" ...@@ -108,12 +108,12 @@ HREF="bzhacking.html"
><DL ><DL
><DT ><DT
>D.5.1. <A >D.5.1. <A
HREF="bzhacking.html#AEN2495" HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A >Things that have caused problems and should be avoided</A
></DT ></DT
><DT ><DT
>D.5.2. <A >D.5.2. <A
HREF="bzhacking.html#AEN2509" HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A >Coding Style for Bugzilla</A
></DT ></DT
></DL ></DL
...@@ -174,7 +174,7 @@ WIDTH="33%" ...@@ -174,7 +174,7 @@ WIDTH="33%"
ALIGN="right" ALIGN="right"
VALIGN="top" VALIGN="top"
>Apache <TT >Apache <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> magic</TD > magic</TD
></TR ></TR
......
docs/html/postinstall-check.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="User Administration" TITLE="User Administration"
HREF="useradmin.html"></HEAD HREF="useradmin.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,28 +66,28 @@ HREF="useradmin.html" ...@@ -66,28 +66,28 @@ HREF="useradmin.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="POSTINSTALL-CHECK" NAME="postinstall-check"
>4.1. Post-Installation Checklist</A >4.1. Post-Installation Checklist</A
></H1 ></H1
><P ><P
> After installation, follow the checklist below to help ensure >&#13; After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla default while you perform your initial tests on your Bugzilla
setup. setup.
</P </P
><DIV ><DIV
CLASS="PROCEDURE" CLASS="procedure"
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Bring up <TT >&#13; Bring up <TT
CLASS="FILENAME" CLASS="filename"
>editparams.cgi</TT >editparams.cgi</TT
> in your web > in your web
browser. This should be available as the <SPAN browser. This should be available as the <SPAN
...@@ -110,7 +110,7 @@ CLASS="QUOTE" ...@@ -110,7 +110,7 @@ CLASS="QUOTE"
will be sent with the maintainer as the return email will be sent with the maintainer as the return email
address.</P address.</P
><P ><P
> Set <SPAN >&#13; Set <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"maintainer"</SPAN >"maintainer"</SPAN
> to <EM > to <EM
...@@ -129,7 +129,7 @@ CLASS="QUOTE" ...@@ -129,7 +129,7 @@ CLASS="QUOTE"
qualified domain name and web server path to your Bugzilla qualified domain name and web server path to your Bugzilla
installation.</P installation.</P
><P ><P
> For example, if your bugzilla query page is >&#13; For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your http://www.foo.com/bugzilla/query.cgi, set your
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -148,7 +148,7 @@ CLASS="QUOTE" ...@@ -148,7 +148,7 @@ CLASS="QUOTE"
which groups of users are allowed to see and edit the which groups of users are allowed to see and edit the
bug.</P bug.</P
><P ><P
> Set "usebuggroups" to "on" <EM >&#13; Set "usebuggroups" to "on" <EM
>only</EM >only</EM
> if you > if you
may wish to restrict access to products. I suggest leaving may wish to restrict access to products. I suggest leaving
...@@ -160,7 +160,7 @@ CLASS="QUOTE" ...@@ -160,7 +160,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> <SPAN >&#13; <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"usebuggroupsentry"</SPAN >"usebuggroupsentry"</SPAN
>, when set to >, when set to
...@@ -172,7 +172,7 @@ CLASS="QUOTE" ...@@ -172,7 +172,7 @@ CLASS="QUOTE"
installations where product isolation is a necessity. installations where product isolation is a necessity.
</P </P
><P ><P
> Set "usebuggroupsentry" to "on" if you absolutely need to >&#13; Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter your installation, I suggest against turning this parameter
...@@ -182,7 +182,7 @@ CLASS="QUOTE" ...@@ -182,7 +182,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> You run into an interesting problem when Bugzilla reaches a >&#13; You run into an interesting problem when Bugzilla reaches a
high level of continuous activity. MySQL supports only high level of continuous activity. MySQL supports only
table-level write locking. What this means is that if table-level write locking. What this means is that if
someone needs to make a change to a bug, they will lock the someone needs to make a change to a bug, they will lock the
...@@ -200,16 +200,16 @@ CLASS="QUOTE" ...@@ -200,16 +200,16 @@ CLASS="QUOTE"
extremely high-traffic Bugzilla databases. extremely high-traffic Bugzilla databases.
</P </P
><P ><P
> Set "shadowdb" to "bug_shadowdb" if you will be running a >&#13; Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database *very* large installation of Bugzilla. The shadow database
enables many simultaneous users to read and write to the enables many simultaneous users to read and write to the
database without interfering with one another. database without interfering with one another.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -225,7 +225,7 @@ ALT="Note"></TD ...@@ -225,7 +225,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Enabling "shadowdb" can adversely affect the stability >&#13; Enabling "shadowdb" can adversely affect the stability
of your installation of Bugzilla. You should regularly of your installation of Bugzilla. You should regularly
check that your database is in sync. It is often check that your database is in sync. It is often
advisable to force a shadow database sync nightly via advisable to force a shadow database sync nightly via
...@@ -253,7 +253,7 @@ CLASS="QUOTE" ...@@ -253,7 +253,7 @@ CLASS="QUOTE"
comments per day. comments per day.
</P </P
><P ><P
> If you use the "shadowdb" option, it is only natural that >&#13; If you use the "shadowdb" option, it is only natural that
you should turn the "queryagainstshadowdb" option "On" as you should turn the "queryagainstshadowdb" option "On" as
well. Otherwise you are replicating data into a shadow well. Otherwise you are replicating data into a shadow
database for no reason! database for no reason!
...@@ -284,27 +284,27 @@ CLASS="QUOTE" ...@@ -284,27 +284,27 @@ CLASS="QUOTE"
these, but it is really best just to monkey around with them these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy a bit to see what they do. I strongly recommend you copy
your <TT your <TT
CLASS="FILENAME" CLASS="filename"
>data/params</TT >data/params</TT
> file somewhere safe > file somewhere safe
before playing with these values, though. If they are before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have display Bugzilla pages to fix the problem until you have
restored your <TT restored your <TT
CLASS="FILENAME" CLASS="filename"
>data/params</TT >data/params</TT
> file.</P > file.</P
><P ><P
> If you have custom logos or HTML you must put in place to >&#13; If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in fit within your site design guidelines, place the code in
the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
or "blurbhtml" text boxes. or "blurbhtml" text boxes.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -320,7 +320,7 @@ ALT="Note"></TD ...@@ -320,7 +320,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> The "headerhtml" text box is the HTML printed out >&#13; The "headerhtml" text box is the HTML printed out
<EM <EM
>before</EM >before</EM
> any other code on the page, > any other code on the page,
...@@ -346,7 +346,7 @@ CLASS="QUOTE" ...@@ -346,7 +346,7 @@ CLASS="QUOTE"
is read as the text to send to the new user along with their is read as the text to send to the new user along with their
password message.</P password message.</P
><P ><P
> Add any text you wish to the "passwordmail" parameter box. >&#13; Add any text you wish to the "passwordmail" parameter box.
For instance, many people choose to use this box to give a For instance, many people choose to use this box to give a
quick training blurb about how to use Bugzilla at your site. quick training blurb about how to use Bugzilla at your site.
</P </P
...@@ -389,7 +389,7 @@ CLASS="QUOTE" ...@@ -389,7 +389,7 @@ CLASS="QUOTE"
their status even more than that which can be indicated by their status even more than that which can be indicated by
the Resolution fields.</P the Resolution fields.</P
><P ><P
> Do you want to use the QA Contact ("useqacontact") and >&#13; Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility, fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance particularly when you have an existing Quality Assurance
...@@ -399,7 +399,7 @@ CLASS="QUOTE" ...@@ -399,7 +399,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> Set "whinedays" to the amount of days you want to let bugs >&#13; Set "whinedays" to the amount of days you want to let bugs
go in the "New" or "Reopened" state before notifying people go in the "New" or "Reopened" state before notifying people
they have untouched new bugs. If you do not plan to use they have untouched new bugs. If you do not plan to use
this feature, simply do not set up the whining cron job this feature, simply do not set up the whining cron job
...@@ -421,15 +421,15 @@ CLASS="QUOTE" ...@@ -421,15 +421,15 @@ CLASS="QUOTE"
require that most other changes come with an require that most other changes come with an
explanation.</P explanation.</P
><P ><P
> Set the "commenton" options according to your site policy. >&#13; Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users resolve, It is a wise idea to require comments when users resolve,
reassign, or reopen bugs at the very least. reassign, or reopen bugs at the very least.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -445,7 +445,7 @@ ALT="Note"></TD ...@@ -445,7 +445,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> It is generally far better to require a developer >&#13; It is generally far better to require a developer
comment when resolving bugs than not. Few things are comment when resolving bugs than not. Few things are
more annoying to bug database users than having a more annoying to bug database users than having a
developer mark a bug "fixed" without any comment as to developer mark a bug "fixed" without any comment as to
...@@ -482,7 +482,7 @@ CLASS="QUOTE" ...@@ -482,7 +482,7 @@ CLASS="QUOTE"
security to prevent snooping, watchers are not a good security to prevent snooping, watchers are not a good
idea.</P idea.</P
><P ><P
> However, for most sites you should set >&#13; However, for most sites you should set
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"supportwatchers"</SPAN >"supportwatchers"</SPAN
......
docs/html/programadmin.html
View file @ d7f38125
...@@ -20,7 +20,7 @@ REL="NEXT" ...@@ -20,7 +20,7 @@ REL="NEXT"
TITLE="Bugzilla Security" TITLE="Bugzilla Security"
HREF="security.html"></HEAD HREF="security.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -67,11 +67,11 @@ HREF="security.html" ...@@ -67,11 +67,11 @@ HREF="security.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="PROGRAMADMIN" NAME="programadmin"
>4.3. Product, Component, Milestone, and Version >4.3. Product, Component, Milestone, and Version
Administration</A Administration</A
></H1 ></H1
...@@ -99,11 +99,11 @@ VALIGN="TOP" ...@@ -99,11 +99,11 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="PRODUCTS" NAME="products"
>4.3.1. Products</A >4.3.1. Products</A
></H2 ></H2
><FONT ><FONT
...@@ -111,10 +111,10 @@ COLOR="RED" ...@@ -111,10 +111,10 @@ COLOR="RED"
>Formerly, and in some spots still, called >Formerly, and in some spots still, called
"Programs"</FONT "Programs"</FONT
><P ><P
> <A >&#13; <A
HREF="glossary.html#GLOSS_PRODUCT" HREF="glossary.html#gloss-product"
><I ><I
CLASS="GLOSSTERM" CLASS="glossterm"
>Products</I >Products</I
></A ></A
> are > are
...@@ -124,7 +124,7 @@ CLASS="GLOSSTERM" ...@@ -124,7 +124,7 @@ CLASS="GLOSSTERM"
products (website, meetings...) products (website, meetings...)
</P </P
><P ><P
> A Product (formerly called "Program", and still referred to >&#13; A Product (formerly called "Program", and still referred to
that way in some portions of the source code) controls some that way in some portions of the source code) controls some
very important functions. The number of "votes" available for very important functions. The number of "votes" available for
users to vote for the most important bugs is set per-product, users to vote for the most important bugs is set per-product,
...@@ -141,15 +141,15 @@ CLASS="GLOSSTERM" ...@@ -141,15 +141,15 @@ CLASS="GLOSSTERM"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Select "components" from the yellow footer >&#13; Select "components" from the yellow footer
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -164,7 +164,7 @@ ALT="Tip"></TD ...@@ -164,7 +164,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> It may seem counterintuitive to click "components" when >&#13; It may seem counterintuitive to click "components" when
you want to edit the properties associated with you want to edit the properties associated with
Products. This is one of a long list of things we want Products. This is one of a long list of things we want
in Bugzilla 3.0... in Bugzilla 3.0...
...@@ -176,22 +176,22 @@ VALIGN="TOP" ...@@ -176,22 +176,22 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> Select the "Add" link to the right of "Add a new product". >&#13; Select the "Add" link to the right of "Add a new product".
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Enter the name of the product and a description. The >&#13; Enter the name of the product and a description. The
Description field is free-form. Description field is free-form.
</P </P
></LI ></LI
></OL ></OL
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -207,7 +207,7 @@ ALT="Tip"></TD ...@@ -207,7 +207,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Don't worry about the "Closed for bug entry", "Maximum Votes >&#13; Don't worry about the "Closed for bug entry", "Maximum Votes
per person", "Maximum votes a person can put on a single per person", "Maximum votes a person can put on a single
bug", "Number of votes a bug in this Product needs to bug", "Number of votes a bug in this Product needs to
automatically get out of the UNCOMFIRMED state", and automatically get out of the UNCOMFIRMED state", and
...@@ -219,34 +219,34 @@ VALIGN="TOP" ...@@ -219,34 +219,34 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="COMPONENTS" NAME="components"
>4.3.2. Components</A >4.3.2. Components</A
></H2 ></H2
><P ><P
> Components are subsections of a Product. >&#13; Components are subsections of a Product.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1461" NAME="AEN1470"
></A ></A
><P ><P
><B ><B
>Example 4-1. Creating some Components</B >Example 4-1. Creating some Components</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1463" NAME="AEN1472"
></A ></A
><P ><P
></P ></P
><P ><P
> The computer game you are designing may have a "UI" >&#13; The computer game you are designing may have a "UI"
component, an "API" component, a "Sound System" component, an "API" component, a "Sound System"
component, and a "Plugins" component, each overseen by component, and a "Plugins" component, each overseen by
a different programmer. It often makes sense to divide a different programmer. It often makes sense to divide
...@@ -272,7 +272,7 @@ NAME="AEN1463" ...@@ -272,7 +272,7 @@ NAME="AEN1463"
to the Component. to the Component.
</P </P
><P ><P
> To create a new Component: >&#13; To create a new Component:
</P </P
><P ><P
></P ></P
...@@ -280,31 +280,31 @@ NAME="AEN1463" ...@@ -280,31 +280,31 @@ NAME="AEN1463"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Select the "Edit components" link from the "Edit product" >&#13; Select the "Edit components" link from the "Edit product"
page page
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Select the "Add" link to the right of the "Add a new >&#13; Select the "Add" link to the right of the "Add a new
component" text on the "Select Component" page. component" text on the "Select Component" page.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Fill out the "Component" field, a short "Description", and >&#13; Fill out the "Component" field, a short "Description", and
the "Initial Owner". The Component and Description fields the "Initial Owner". The Component and Description fields
are free-form; the "Initial Owner" field must be that of a are free-form; the "Initial Owner" field must be that of a
user ID already existing in the database. If the initial user ID already existing in the database. If the initial
owner does not exist, Bugzilla will refuse to create the owner does not exist, Bugzilla will refuse to create the
component. component.
<DIV <DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -319,7 +319,7 @@ ALT="Tip"></TD ...@@ -319,7 +319,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Is your "Default Owner" a user who is not yet in the >&#13; Is your "Default Owner" a user who is not yet in the
database? No problem. database? No problem.
<P <P
></P ></P
...@@ -327,19 +327,19 @@ VALIGN="TOP" ...@@ -327,19 +327,19 @@ VALIGN="TOP"
TYPE="a" TYPE="a"
><LI ><LI
><P ><P
> Select the "Log out" link on the footer of the >&#13; Select the "Log out" link on the footer of the
page. page.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Select the "New Account" link on the footer of >&#13; Select the "New Account" link on the footer of
the "Relogin" page the "Relogin" page
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Type in the email address of the default owner >&#13; Type in the email address of the default owner
you want to create in the "E-mail address" you want to create in the "E-mail address"
field, and her full name in the "Real name" field, and her full name in the "Real name"
field, then select the "Submit Query" button. field, then select the "Submit Query" button.
...@@ -347,7 +347,7 @@ TYPE="a" ...@@ -347,7 +347,7 @@ TYPE="a"
></LI ></LI
><LI ><LI
><P ><P
> Now select "Log in" again, type in your login >&#13; Now select "Log in" again, type in your login
information, and you can modify the product to information, and you can modify the product to
use the Default Owner information you require. use the Default Owner information you require.
</P </P
...@@ -364,7 +364,7 @@ TYPE="a" ...@@ -364,7 +364,7 @@ TYPE="a"
></LI ></LI
><LI ><LI
><P ><P
> Either Edit more components or return to the Bugzilla >&#13; Either Edit more components or return to the Bugzilla
Query Page. To return to the Product you were editing, you Query Page. To return to the Product you were editing, you
must select the Components link as before. must select the Components link as before.
</P </P
...@@ -372,36 +372,36 @@ TYPE="a" ...@@ -372,36 +372,36 @@ TYPE="a"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="VERSIONS" NAME="versions"
>4.3.3. Versions</A >4.3.3. Versions</A
></H2 ></H2
><P ><P
> Versions are the revisions of the product, such as "Flinders >&#13; Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Using Versions 3.1", "Flinders 95", and "Flinders 2000". Using Versions
helps you isolate code changes and are an aid in reporting. helps you isolate code changes and are an aid in reporting.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1490" NAME="AEN1499"
></A ></A
><P ><P
><B ><B
>Example 4-2. Common Use of Versions</B >Example 4-2. Common Use of Versions</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1492" NAME="AEN1501"
></A ></A
><P ><P
></P ></P
><P ><P
> A user reports a bug against Version "Beta 2.0" of your >&#13; A user reports a bug against Version "Beta 2.0" of your
product. The current Version of your software is product. The current Version of your software is
"Release Candidate 1", and no longer has the bug. This "Release Candidate 1", and no longer has the bug. This
will help you triage and classify bugs according to will help you triage and classify bugs according to
...@@ -416,23 +416,23 @@ NAME="AEN1492" ...@@ -416,23 +416,23 @@ NAME="AEN1492"
></DIV ></DIV
> >
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1494" NAME="AEN1503"
></A ></A
><P ><P
><B ><B
>Example 4-3. A Different Use of Versions</B >Example 4-3. A Different Use of Versions</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1496" NAME="AEN1505"
></A ></A
><P ><P
></P ></P
><P ><P
> This field has been used to good effect by an online >&#13; This field has been used to good effect by an online
service provider in a slightly different way. They had service provider in a slightly different way. They had
three versions of the product: "Production", "QA", and three versions of the product: "Production", "QA", and
"Dev". Although it may be the same product, a bug in "Dev". Although it may be the same product, a bug in
...@@ -450,7 +450,7 @@ NAME="AEN1496" ...@@ -450,7 +450,7 @@ NAME="AEN1496"
> >
</P </P
><P ><P
> To create and edit Versions: >&#13; To create and edit Versions:
</P </P
><P ><P
></P ></P
...@@ -458,32 +458,32 @@ NAME="AEN1496" ...@@ -458,32 +458,32 @@ NAME="AEN1496"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> From the "Edit product" screen, select "Edit Versions" >&#13; From the "Edit product" screen, select "Edit Versions"
</P </P
></LI ></LI
><LI ><LI
><P ><P
> You will notice that the product already has the default >&#13; You will notice that the product already has the default
version "undefined". If your product doesn't use version version "undefined". If your product doesn't use version
numbers, you may want to leave this as it is or edit it so numbers, you may want to leave this as it is or edit it so
that it is "---". You can then go back to the edit that it is "---". You can then go back to the edit
versions page and add new versions to your product. versions page and add new versions to your product.
</P </P
><P ><P
> Otherwise, click the "Add" button to the right of the "Add >&#13; Otherwise, click the "Add" button to the right of the "Add
a new version" text. a new version" text.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Enter the name of the Version. This can be free-form >&#13; Enter the name of the Version. This can be free-form
characters up to the limit of the text box. Then select characters up to the limit of the text box. Then select
the "Add" button. the "Add" button.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> At this point you can select "Edit" to edit more Versions, >&#13; At this point you can select "Edit" to edit more Versions,
or return to the "Query" page, from which you can navigate or return to the "Query" page, from which you can navigate
back to the product through the "components" link at the back to the product through the "components" link at the
foot of the Query page. foot of the Query page.
...@@ -492,26 +492,26 @@ TYPE="1" ...@@ -492,26 +492,26 @@ TYPE="1"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="MILESTONES" NAME="milestones"
>4.3.4. Milestones</A >4.3.4. Milestones</A
></H2 ></H2
><P ><P
> Milestones are "targets" that you plan to get a bug fixed by. >&#13; Milestones are "targets" that you plan to get a bug fixed by.
For example, you have a bug that you plan to fix for your 3.0 For example, you have a bug that you plan to fix for your 3.0
release, it would be assigned the milestone of 3.0. Or, you release, it would be assigned the milestone of 3.0. Or, you
have a bug that you plan to fix for 2.8, this would have a have a bug that you plan to fix for 2.8, this would have a
milestone of 2.8. milestone of 2.8.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -527,7 +527,7 @@ ALT="Note"></TD ...@@ -527,7 +527,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Milestone options will only appear for a Product if you >&#13; Milestone options will only appear for a Product if you
turned the "usetargetmilestone" field in the "Edit turned the "usetargetmilestone" field in the "Edit
Parameters" screen "On". Parameters" screen "On".
</P </P
...@@ -536,7 +536,7 @@ VALIGN="TOP" ...@@ -536,7 +536,7 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> To create new Milestones, set Default Milestones, and set >&#13; To create new Milestones, set Default Milestones, and set
Milestone URL: Milestone URL:
</P </P
><P ><P
...@@ -545,40 +545,40 @@ VALIGN="TOP" ...@@ -545,40 +545,40 @@ VALIGN="TOP"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Select "edit milestones" >&#13; Select "edit milestones"
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Select "Add" to the right of the "Add a new milestone" >&#13; Select "Add" to the right of the "Add a new milestone"
text text
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Enter the name of the Milestone in the "Milestone" field. >&#13; Enter the name of the Milestone in the "Milestone" field.
You can optionally set the "Sortkey", which is a positive You can optionally set the "Sortkey", which is a positive
or negative number (-255 to 255) that defines where in the or negative number (-255 to 255) that defines where in the
list this particular milestone appears. Select "Add". list this particular milestone appears. Select "Add".
</P </P
><DIV ><DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1522" NAME="AEN1531"
></A ></A
><P ><P
><B ><B
>Example 4-4. Using SortKey with Target Milestone</B >Example 4-4. Using SortKey with Target Milestone</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1524" NAME="AEN1533"
></A ></A
><P ><P
></P ></P
><P ><P
> Let's say you create a target milestone called >&#13; Let's say you create a target milestone called
"Release 1.0", with Sortkey set to "0". Later, you "Release 1.0", with Sortkey set to "0". Later, you
realize that you will have a public beta, called realize that you will have a public beta, called
"Beta1". You can create a Milestone called "Beta1", "Beta1". You can create a Milestone called "Beta1",
...@@ -593,17 +593,17 @@ NAME="AEN1524" ...@@ -593,17 +593,17 @@ NAME="AEN1524"
></LI ></LI
><LI ><LI
><P ><P
> If you want to add more milestones, select the "Edit" >&#13; If you want to add more milestones, select the "Edit"
link. If you don't, well shoot, you have to go back to the link. If you don't, well shoot, you have to go back to the
"query" page and select "components" again, and make your "query" page and select "components" again, and make your
way back to the Product you were editing. way back to the Product you were editing.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -618,7 +618,7 @@ ALT="Note"></TD ...@@ -618,7 +618,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This is another in the list of unusual user interface >&#13; This is another in the list of unusual user interface
decisions that we'd like to get cleaned up. Shouldn't decisions that we'd like to get cleaned up. Shouldn't
there be a link to the effect of "edit the Product I there be a link to the effect of "edit the Product I
was editing when I ended up here"? In any case, was editing when I ended up here"? In any case,
...@@ -635,21 +635,21 @@ VALIGN="TOP" ...@@ -635,21 +635,21 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> From the Edit product screen again (once you've made your >&#13; From the Edit product screen again (once you've made your
way back), enter the URL for a description of what your way back), enter the URL for a description of what your
milestones are for this product in the "Milestone URL" milestones are for this product in the "Milestone URL"
field. It should be of the format field. It should be of the format
"http://www.foo.com/bugzilla/product_milestones.html" "http://www.foo.com/bugzilla/product_milestones.html"
</P </P
><P ><P
> Some common uses of this field include product >&#13; Some common uses of this field include product
descriptions, product roadmaps, and of course a simple descriptions, product roadmaps, and of course a simple
description of the meaning of each milestone. description of the meaning of each milestone.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> If you're using Target Milestones, the "Default Milestone" >&#13; If you're using Target Milestones, the "Default Milestone"
field must have some kind of entry. If you really don't field must have some kind of entry. If you really don't
care if people set coherent Target Milestones, simply care if people set coherent Target Milestones, simply
leave this at the default, "---". However, controlling leave this at the default, "---". However, controlling
...@@ -662,15 +662,15 @@ VALIGN="TOP" ...@@ -662,15 +662,15 @@ VALIGN="TOP"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="VOTING" NAME="voting"
>4.3.5. Voting</A >4.3.5. Voting</A
></H2 ></H2
><P ><P
> The concept of "voting" is a poorly understood, yet powerful >&#13; The concept of "voting" is a poorly understood, yet powerful
feature for the management of open-source projects. Each user feature for the management of open-source projects. Each user
is assigned so many Votes per product, which they can freely is assigned so many Votes per product, which they can freely
reassign (or assign multiple votes to a single bug). This reassign (or assign multiple votes to a single bug). This
...@@ -681,7 +681,7 @@ NAME="VOTING" ...@@ -681,7 +681,7 @@ NAME="VOTING"
attention so they don't sit for a long time awaiting triage. attention so they don't sit for a long time awaiting triage.
</P </P
><P ><P
> The daunting challenge of Votes is deciding where you draw the >&#13; The daunting challenge of Votes is deciding where you draw the
line for a "vocal majority". If you only have a user base of line for a "vocal majority". If you only have a user base of
100 users, setting a low threshold for bugs to move from 100 users, setting a low threshold for bugs to move from
UNCONFIRMED to NEW makes sense. As the Bugzilla user base UNCONFIRMED to NEW makes sense. As the Bugzilla user base
...@@ -698,19 +698,19 @@ NAME="VOTING" ...@@ -698,19 +698,19 @@ NAME="VOTING"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Navigate to the "Edit product" screen for the Product you >&#13; Navigate to the "Edit product" screen for the Product you
wish to modify wish to modify
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Set "Maximum Votes per person" to your calculated value. >&#13; Set "Maximum Votes per person" to your calculated value.
Setting this field to "0" disables voting. Setting this field to "0" disables voting.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Set "Maximum Votes a person can put on a single bug" to >&#13; Set "Maximum Votes a person can put on a single bug" to
your calculated value. It should probably be some number your calculated value. It should probably be some number
lower than the "Maximum votes per person". Setting this lower than the "Maximum votes per person". Setting this
field to "0" disables voting, but leaves the voting field to "0" disables voting, but leaves the voting
...@@ -719,7 +719,7 @@ TYPE="1" ...@@ -719,7 +719,7 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Set "Number of votes a bug in this product needs to >&#13; Set "Number of votes a bug in this product needs to
automatically get out of the UNCONFIRMED state" to your automatically get out of the UNCONFIRMED state" to your
calculated number. Setting this field to "0" disables calculated number. Setting this field to "0" disables
the automatic move of bugs from UNCONFIRMED to NEW. Some the automatic move of bugs from UNCONFIRMED to NEW. Some
...@@ -727,12 +727,12 @@ TYPE="1" ...@@ -727,12 +727,12 @@ TYPE="1"
Votes if your Bugzilla user base is unable to affect which Votes if your Bugzilla user base is unable to affect which
bugs appear on Development radar? bugs appear on Development radar?
<DIV <DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -747,7 +747,7 @@ ALT="Tip"></TD ...@@ -747,7 +747,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You should probably set this number to higher than a >&#13; You should probably set this number to higher than a
small coalition of Bugzilla users can influence it. small coalition of Bugzilla users can influence it.
Most sites use this as a "referendum" mechanism -- if Most sites use this as a "referendum" mechanism -- if
users are able to vote a bug out of UNCONFIRMED, it is users are able to vote a bug out of UNCONFIRMED, it is
...@@ -764,44 +764,44 @@ VALIGN="TOP" ...@@ -764,44 +764,44 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> Once you have adjusted the values to your preference, >&#13; Once you have adjusted the values to your preference,
select the "Update" button. select the "Update" button.
</P </P
></LI ></LI
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="GROUPS" NAME="groups"
>4.3.6. Groups and Group Security</A >4.3.6. Groups and Group Security</A
></H2 ></H2
><P ><P
> Groups can be very useful in bugzilla, because they allow >&#13; Groups can be very useful in bugzilla, because they allow
users to isolate bugs or products that should only be seen by users to isolate bugs or products that should only be seen by
certain people. Groups can also be a complicated minefield of certain people. Groups can also be a complicated minefield of
interdependencies and weirdness if mismanaged. interdependencies and weirdness if mismanaged.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1558" NAME="AEN1567"
></A ></A
><P ><P
><B ><B
>Example 4-5. When to Use Group Security</B >Example 4-5. When to Use Group Security</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1560" NAME="AEN1569"
></A ></A
><P ><P
></P ></P
><P ><P
> Many Bugzilla sites isolate "Security-related" bugs from >&#13; Many Bugzilla sites isolate "Security-related" bugs from
all other bugs. This way, they can have a fix ready all other bugs. This way, they can have a fix ready
before the security vulnerability is announced to the before the security vulnerability is announced to the
world. You can create a "Security" product which, by world. You can create a "Security" product which, by
...@@ -825,11 +825,11 @@ NAME="AEN1560" ...@@ -825,11 +825,11 @@ NAME="AEN1560"
into two categories: Generic and Product-Based. into two categories: Generic and Product-Based.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -845,7 +845,7 @@ ALT="Note"></TD ...@@ -845,7 +845,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Groups in Bugzilla are a complicated beast that evolved out >&#13; Groups in Bugzilla are a complicated beast that evolved out
of very simple user permission bitmasks, apparently itself of very simple user permission bitmasks, apparently itself
derived from common concepts in UNIX access controls. A derived from common concepts in UNIX access controls. A
"bitmask" is a fixed-length number whose value can describe "bitmask" is a fixed-length number whose value can describe
...@@ -863,7 +863,7 @@ VALIGN="TOP" ...@@ -863,7 +863,7 @@ VALIGN="TOP"
next 32, etc. next 32, etc.
</P </P
><P ><P
> Similarly, Bugzilla offers a bitmask to define group >&#13; Similarly, Bugzilla offers a bitmask to define group
permissions, with an internal limit of 64. Several are permissions, with an internal limit of 64. Several are
already occupied by built-in permissions. The way around already occupied by built-in permissions. The way around
this limitation is to avoid assigning groups to products if this limitation is to avoid assigning groups to products if
...@@ -879,7 +879,7 @@ VALIGN="TOP" ...@@ -879,7 +879,7 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> To enable Generic Group Security ("usebuggroups"): >&#13; To enable Generic Group Security ("usebuggroups"):
</P </P
><P ><P
></P ></P
...@@ -887,47 +887,47 @@ VALIGN="TOP" ...@@ -887,47 +887,47 @@ VALIGN="TOP"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Turn "On" "usebuggroups" in the "Edit Parameters" screen. >&#13; Turn "On" "usebuggroups" in the "Edit Parameters" screen.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> You will generally have no groups set up. Select the >&#13; You will generally have no groups set up. Select the
"groups" link in the footer. "groups" link in the footer.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Take a moment to understand the instructions on the "Edit >&#13; Take a moment to understand the instructions on the "Edit
Groups" screen. Once you feel confident you understand Groups" screen. Once you feel confident you understand
what is expected of you, select the "Add Group" link. what is expected of you, select the "Add Group" link.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Fill out the "New Name" (remember, no spaces!), "New >&#13; Fill out the "New Name" (remember, no spaces!), "New
Description", and "New User RegExp" fields. "New User Description", and "New User RegExp" fields. "New User
RegExp" allows you to automatically place all users who RegExp" allows you to automatically place all users who
fulfill the Regular Expression into the new group. fulfill the Regular Expression into the new group.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1575" NAME="AEN1584"
></A ></A
><P ><P
><B ><B
>Example 4-6. Creating a New Group</B >Example 4-6. Creating a New Group</B
></P ></P
><DIV ><DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN1577" NAME="AEN1586"
></A ></A
><P ><P
></P ></P
><P ><P
> I created a group called DefaultGroup with a >&#13; I created a group called DefaultGroup with a
description of <SPAN description of <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"This is simply a group to play >"This is simply a group to play
...@@ -950,14 +950,14 @@ CLASS="QUOTE" ...@@ -950,14 +950,14 @@ CLASS="QUOTE"
></LI ></LI
></OL ></OL
><P ><P
> To enable Product-Based Group Security (usebuggroupsentry): >&#13; To enable Product-Based Group Security (usebuggroupsentry):
</P </P
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -973,7 +973,7 @@ ALT="Warning"></TD ...@@ -973,7 +973,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Don't forget that you only have 64 groups masks available, >&#13; Don't forget that you only have 64 groups masks available,
total, for your installation of Bugzilla! If you plan on total, for your installation of Bugzilla! If you plan on
having more than 50 products in your individual Bugzilla having more than 50 products in your individual Bugzilla
installation, and require group security for your products, installation, and require group security for your products,
...@@ -991,16 +991,16 @@ VALIGN="TOP" ...@@ -991,16 +991,16 @@ VALIGN="TOP"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Turn "On" "usebuggroups" and "usebuggroupsentry" in the >&#13; Turn "On" "usebuggroups" and "usebuggroupsentry" in the
"Edit Parameters" screen. "Edit Parameters" screen.
</P </P
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -1015,7 +1015,7 @@ ALT="Warning"></TD ...@@ -1015,7 +1015,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> "usebuggroupsentry" has the capacity to prevent the >&#13; "usebuggroupsentry" has the capacity to prevent the
administrative user from directly altering bugs because administrative user from directly altering bugs because
of conflicting group permissions. If you plan on using of conflicting group permissions. If you plan on using
"usebuggroupsentry", you should plan on restricting "usebuggroupsentry", you should plan on restricting
...@@ -1031,7 +1031,7 @@ VALIGN="TOP" ...@@ -1031,7 +1031,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> You will generally have no Groups set up, unless you >&#13; You will generally have no Groups set up, unless you
enabled "usebuggroupsentry" prior to creating any enabled "usebuggroupsentry" prior to creating any
Products. To create "Generic Group Security" groups, Products. To create "Generic Group Security" groups,
follow the instructions given above. To create follow the instructions given above. To create
...@@ -1044,19 +1044,20 @@ VALIGN="TOP" ...@@ -1044,19 +1044,20 @@ VALIGN="TOP"
></LI ></LI
></OL ></OL
><P ><P
> You may find this example illustrative for how bug groups work. >&#13; You may find this example illustrative for how bug groups work.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1592" NAME="AEN1601"
></A ></A
><P ><P
><B ><B
>Example 4-7. Bugzilla Groups</B >Example 4-7. Bugzilla Groups</B
></P ></P
><P ><P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>Bugzilla&nbsp;Groups&nbsp;example<br> ><br>
Bugzilla&nbsp;Groups&nbsp;example<br>
-----------------------<br> -----------------------<br>
<br> <br>
For&nbsp;this&nbsp;example,&nbsp;let&nbsp;us&nbsp;suppose&nbsp;we&nbsp;have&nbsp;four&nbsp;groups,&nbsp;call&nbsp;them<br> For&nbsp;this&nbsp;example,&nbsp;let&nbsp;us&nbsp;suppose&nbsp;we&nbsp;have&nbsp;four&nbsp;groups,&nbsp;call&nbsp;them<br>
......
docs/html/quicksearch.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Hacking Bugzilla" TITLE="Hacking Bugzilla"
HREF="bzhacking.html"></HEAD HREF="bzhacking.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,30 +66,30 @@ HREF="bzhacking.html" ...@@ -66,30 +66,30 @@ HREF="bzhacking.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="QUICKSEARCH" NAME="quicksearch"
>D.4. The Quicksearch Utility</A >D.4. The Quicksearch Utility</A
></H1 ></H1
><P ><P
> Quicksearch is a new, experimental feature of the 2.12 release. >&#13; Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files, "localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html" "quicksearch.html" and "quicksearchhack.html"
</P </P
><P ><P
> The index.html page has been updated to include the QuickSearch >&#13; The index.html page has been updated to include the QuickSearch
text box. text box.
</P </P
><P ><P
> To take full advantage of the query power, the Bugzilla >&#13; To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value maintainer must edit "localconfig.js" according to the value
sets used in the local installation. sets used in the local installation.
</P </P
><P ><P
> Currently, keywords must be hard-coded in localconfig.js. If >&#13; Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo" for a bug with the "foo" keyword will only find bugs with "foo"
...@@ -97,7 +97,7 @@ NAME="QUICKSEARCH" ...@@ -97,7 +97,7 @@ NAME="QUICKSEARCH"
but not those with the keyword "foo". but not those with the keyword "foo".
</P </P
><P ><P
> Workarounds for Bugzilla users: >&#13; Workarounds for Bugzilla users:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -120,7 +120,7 @@ BORDER="0" ...@@ -120,7 +120,7 @@ BORDER="0"
> >
</P </P
><P ><P
> When this tool is ported from client-side JavaScript to >&#13; When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can server-side Perl, the requirement for hard-coding keywords can
be fixed. <A be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"
......
docs/html/rewrite.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The setperl.csh Utility" TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD HREF="setperl.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,19 +66,19 @@ HREF="setperl.html" ...@@ -66,19 +66,19 @@ HREF="setperl.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="REWRITE" NAME="rewrite"
>D.1. Apache <TT >D.1. Apache <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> magic</A > magic</A
></H1 ></H1
><P ><P
>Apache's <TT >Apache's <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P > module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P
><P ><P
...@@ -87,9 +87,9 @@ CLASS="FILENAME" ...@@ -87,9 +87,9 @@ CLASS="FILENAME"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Make it so if someone types >&#13; Make it so if someone types
<TT <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
>http://www.foo.com/12345</TT >http://www.foo.com/12345</TT
>, >,
Bugzilla spits back Bugzilla spits back
...@@ -99,17 +99,19 @@ CLASS="COMPUTEROUTPUT" ...@@ -99,17 +99,19 @@ CLASS="COMPUTEROUTPUT"
><TABLE ><TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="90%" WIDTH="100%"
><TR ><TR
><TD ><TD
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>&#60;VirtualHost 12.34.56.78&#62; >&#13;
&#60;VirtualHost 12.34.56.78&#62;
RewriteEngine On RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
&#60;/VirtualHost&#62; &#60;/VirtualHost&#62;
</PRE </PRE
></FONT ></FONT
></TD ></TD
......
docs/html/rhbugzilla.html
View file @ d7f38125
...@@ -17,9 +17,9 @@ TITLE="Bugzilla Variants and Competitors" ...@@ -17,9 +17,9 @@ TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK HREF="variants.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Loki Bugzilla (Fenris)" TITLE="Loki Bugzilla (Fenris)"
HREF="variant_fenris.html"></HEAD HREF="variant-fenris.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -57,7 +57,7 @@ WIDTH="10%" ...@@ -57,7 +57,7 @@ WIDTH="10%"
ALIGN="right" ALIGN="right"
VALIGN="bottom" VALIGN="bottom"
><A ><A
HREF="variant_fenris.html" HREF="variant-fenris.html"
>Next</A >Next</A
></TD ></TD
></TR ></TR
...@@ -66,15 +66,15 @@ HREF="variant_fenris.html" ...@@ -66,15 +66,15 @@ HREF="variant_fenris.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="RHBUGZILLA" NAME="rhbugzilla"
>7.1. Red Hat Bugzilla</A >7.1. Red Hat Bugzilla</A
></H1 ></H1
><P ><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant >&#13; Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence serving as the back-end, instead of just MySQL. Dave Lawrence
...@@ -120,7 +120,7 @@ WIDTH="33%" ...@@ -120,7 +120,7 @@ WIDTH="33%"
ALIGN="right" ALIGN="right"
VALIGN="top" VALIGN="top"
><A ><A
HREF="variant_fenris.html" HREF="variant-fenris.html"
>Next</A >Next</A
></TD ></TD
></TR ></TR
......
docs/html/scm.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Tinderbox/Tinderbox2" TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD HREF="tinderbox.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="tinderbox.html" ...@@ -66,15 +66,15 @@ HREF="tinderbox.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="SCM" NAME="scm"
>5.3. Perforce SCM</A >5.3. Perforce SCM</A
></H1 ></H1
><P ><P
> You can find the project page for Bugzilla and Teamtrack >&#13; You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <A Perforce integration (p4dti) at: <A
HREF="http://www.ravenbrook.com/project/p4dti/" HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top" TARGET="_top"
...@@ -89,7 +89,7 @@ TARGET="_top" ...@@ -89,7 +89,7 @@ TARGET="_top"
>. >.
</P </P
><P ><P
> Integration of Perforce with Bugzilla, once patches are applied, >&#13; Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is patches for the Bugzilla version you are installing. p4dti is
......
docs/html/security.html
View file @ d7f38125
...@@ -20,7 +20,7 @@ REL="NEXT" ...@@ -20,7 +20,7 @@ REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools" TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD HREF="integration.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -67,11 +67,11 @@ HREF="integration.html" ...@@ -67,11 +67,11 @@ HREF="integration.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="SECURITY" NAME="security"
>4.4. Bugzilla Security</A >4.4. Bugzilla Security</A
></H1 ></H1
><TABLE ><TABLE
...@@ -100,11 +100,11 @@ VALIGN="TOP" ...@@ -100,11 +100,11 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -120,7 +120,7 @@ ALT="Note"></TD ...@@ -120,7 +120,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Poorly-configured MySQL, Bugzilla, and FTP installations have >&#13; Poorly-configured MySQL, Bugzilla, and FTP installations have
given attackers full access to systems in the past. Please given attackers full access to systems in the past. Please
take these guidelines seriously, even for Bugzilla machines take these guidelines seriously, even for Bugzilla machines
hidden away behind your firewall. 80% of all computer hidden away behind your firewall. 80% of all computer
...@@ -131,13 +131,13 @@ VALIGN="TOP" ...@@ -131,13 +131,13 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> Secure your installation. >&#13; Secure your installation.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -153,7 +153,7 @@ ALT="Note"></TD ...@@ -153,7 +153,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> These instructions must, of necessity, be somewhat vague >&#13; These instructions must, of necessity, be somewhat vague
since Bugzilla runs on so many different platforms. If you since Bugzilla runs on so many different platforms. If you
have refinements of these directions for specific platforms, have refinements of these directions for specific platforms,
please submit them to <A please submit them to <A
...@@ -173,7 +173,7 @@ TARGET="_top" ...@@ -173,7 +173,7 @@ TARGET="_top"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Ensure you are running at least MysQL version 3.22.32 or >&#13; Ensure you are running at least MysQL version 3.22.32 or
newer. Earlier versions had notable security holes and newer. Earlier versions had notable security holes and
poorly secured default configuration choices. poorly secured default configuration choices.
</P </P
...@@ -189,7 +189,7 @@ TARGET="_top" ...@@ -189,7 +189,7 @@ TARGET="_top"
> The MySQL Privilege System</A > The MySQL Privilege System</A
> until you can recite it from memory!</P > until you can recite it from memory!</P
><P ><P
> At the very least, ensure you password the "mysql -u root" >&#13; At the very least, ensure you password the "mysql -u root"
account and the "bugs" account, establish grant table account and the "bugs" account, establish grant table
rights (consult the Keystone guide in Appendix C: The rights (consult the Keystone guide in Appendix C: The
Bugzilla Database for some easy-to-use details) that do Bugzilla Database for some easy-to-use details) that do
...@@ -200,14 +200,14 @@ TARGET="_top" ...@@ -200,14 +200,14 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Lock down /etc/inetd.conf. Heck, disable inet entirely on >&#13; Lock down /etc/inetd.conf. Heck, disable inet entirely on
this box. It should only listen to port 25 for Sendmail this box. It should only listen to port 25 for Sendmail
and port 80 for Apache. and port 80 for Apache.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Do not run Apache as <SPAN >&#13; Do not run Apache as <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"nobody"</SPAN >"nobody"</SPAN
>. This will >. This will
...@@ -215,12 +215,12 @@ CLASS="QUOTE" ...@@ -215,12 +215,12 @@ CLASS="QUOTE"
Run it, instead, as a user with a name, set via your Run it, instead, as a user with a name, set via your
httpd.conf file. httpd.conf file.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -235,7 +235,7 @@ ALT="Note"></TD ...@@ -235,7 +235,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> <SPAN >&#13; <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"nobody"</SPAN >"nobody"</SPAN
> is a real user on UNIX systems. > is a real user on UNIX systems.
...@@ -259,7 +259,7 @@ CLASS="QUOTE" ...@@ -259,7 +259,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> Ensure you have adequate access controls for the >&#13; Ensure you have adequate access controls for the
$BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/ $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
directories, as well as the $BUGZILLA_HOME/localconfig and directories, as well as the $BUGZILLA_HOME/localconfig and
$BUGZILLA_HOME/globals.pl files. The localconfig file $BUGZILLA_HOME/globals.pl files. The localconfig file
...@@ -274,12 +274,12 @@ CLASS="QUOTE" ...@@ -274,12 +274,12 @@ CLASS="QUOTE"
bug information to those who may not be allowed to see it. bug information to those who may not be allowed to see it.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -294,7 +294,7 @@ ALT="Note"></TD ...@@ -294,7 +294,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Bugzilla provides default .htaccess files to protect the >&#13; Bugzilla provides default .htaccess files to protect the
most common Apache installations. However, you should most common Apache installations. However, you should
verify these are adequate according to the site-wide verify these are adequate according to the site-wide
security policy of your web server, and ensure that the security policy of your web server, and ensure that the
...@@ -305,7 +305,7 @@ VALIGN="TOP" ...@@ -305,7 +305,7 @@ VALIGN="TOP"
details. details.
</P </P
><P ><P
> If you are using a web server that does not support the >&#13; If you are using a web server that does not support the
.htaccess control method, <EM .htaccess control method, <EM
>you are at >you are at
risk!</EM risk!</EM
...@@ -322,7 +322,7 @@ TARGET="_top" ...@@ -322,7 +322,7 @@ TARGET="_top"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> On Apache, you can use .htaccess files to protect access >&#13; On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
TARGET="_top" TARGET="_top"
...@@ -334,34 +334,34 @@ TARGET="_top" ...@@ -334,34 +334,34 @@ TARGET="_top"
> for adequate protection in your data/ and shadow/ directories. > for adequate protection in your data/ and shadow/ directories.
</P </P
><P ><P
> Note the instructions which follow are Apache-specific. >&#13; Note the instructions which follow are Apache-specific.
If you use IIS, Netscape, or other non-Apache web servers, If you use IIS, Netscape, or other non-Apache web servers,
please consult your system documentation for how to secure please consult your system documentation for how to secure
these files from being transmitted to curious users. these files from being transmitted to curious users.
</P </P
><P ><P
> Place the following text into a file named ".htaccess", >&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data readable by your web server, in your $BUGZILLA_HOME/data
directory. <P directory. <P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>&nbsp;&#60;Files&nbsp;comments&#62;&nbsp;allow<br> >&nbsp;&#60;Files&nbsp;comments&#62;&nbsp;allow<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
> >
</P </P
><P ><P
> Place the following text into a file named ".htaccess", >&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/ readable by your web server, in your $BUGZILLA_HOME/
directory. <P directory. <P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>&nbsp;&#60;Files&nbsp;localconfig&#62;&nbsp;deny<br> >&nbsp;&#60;Files&nbsp;localconfig&#62;&nbsp;deny<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;</P &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;</P
> >
</P </P
><P ><P
> Place the following text into a file named ".htaccess", >&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/shadow readable by your web server, in your $BUGZILLA_HOME/shadow
directory. <P directory. <P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P >&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
> >
</P </P
......
docs/html/setperl.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Command-line Bugzilla Queries" TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD HREF="cmdline.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="cmdline.html" ...@@ -66,11 +66,11 @@ HREF="cmdline.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="SETPERL" NAME="setperl"
>D.2. The setperl.csh Utility</A >D.2. The setperl.csh Utility</A
></H1 ></H1
><P ><P
...@@ -80,12 +80,12 @@ NAME="SETPERL" ...@@ -80,12 +80,12 @@ NAME="SETPERL"
search path on your system, it will not work! search path on your system, it will not work!
</P </P
><DIV ><DIV
CLASS="PROCEDURE" CLASS="procedure"
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Download the "setperl.csh" utility to your Bugzilla >&#13; Download the "setperl.csh" utility to your Bugzilla
directory and make it executable. directory and make it executable.
</P </P
><OL ><OL
...@@ -93,14 +93,14 @@ CLASS="SUBSTEPS" ...@@ -93,14 +93,14 @@ CLASS="SUBSTEPS"
TYPE="a" TYPE="a"
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>cd /your/path/to/bugzilla</B >cd /your/path/to/bugzilla</B
> >
</TT </TT
...@@ -109,13 +109,13 @@ CLASS="COMMAND" ...@@ -109,13 +109,13 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>wget -O >wget -O
setperl.csh setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
...@@ -125,13 +125,13 @@ CLASS="COMMAND" ...@@ -125,13 +125,13 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>chmod >chmod
u+x setperl.csh</B u+x setperl.csh</B
> </TT > </TT
...@@ -142,21 +142,21 @@ CLASS="COMMAND" ...@@ -142,21 +142,21 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> Prepare (and fix) Bugzilla file permissions. >&#13; Prepare (and fix) Bugzilla file permissions.
</P </P
><OL ><OL
CLASS="SUBSTEPS" CLASS="SUBSTEPS"
TYPE="a" TYPE="a"
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>chmod u+w *</B >chmod u+w *</B
> >
</TT </TT
...@@ -165,13 +165,13 @@ CLASS="COMMAND" ...@@ -165,13 +165,13 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>chmod >chmod
u+x duplicates.cgi</B u+x duplicates.cgi</B
> </TT > </TT
...@@ -180,14 +180,14 @@ CLASS="COMMAND" ...@@ -180,14 +180,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>chmod a-x bug_status.html</B >chmod a-x bug_status.html</B
> >
</TT </TT
...@@ -198,39 +198,39 @@ CLASS="COMMAND" ...@@ -198,39 +198,39 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> Run the script: >&#13; Run the script:
</P </P
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>./setperl.csh /your/path/to/perl</B >./setperl.csh /your/path/to/perl</B
> >
</TT </TT
> >
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN2439" NAME="AEN2448"
></A ></A
><P ><P
><B ><B
>Example D-1. Using Setperl to set your perl path</B >Example D-1. Using Setperl to set your perl path</B
></P ></P
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>./setperl.csh /usr/bin/perl</B >./setperl.csh /usr/bin/perl</B
> >
</TT </TT
...@@ -284,7 +284,7 @@ WIDTH="33%" ...@@ -284,7 +284,7 @@ WIDTH="33%"
ALIGN="left" ALIGN="left"
VALIGN="top" VALIGN="top"
>Apache <TT >Apache <TT
CLASS="FILENAME" CLASS="filename"
>mod_rewrite</TT >mod_rewrite</TT
> magic</TD > magic</TD
><TD ><TD
......
docs/html/stepbystep.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Mac OS X Installation Notes" TITLE="Mac OS X Installation Notes"
HREF="osx.html"></HEAD HREF="osx.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,30 +66,30 @@ HREF="osx.html" ...@@ -66,30 +66,30 @@ HREF="osx.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="STEPBYSTEP" NAME="stepbystep"
>3.2. Step-by-step Install</A >3.2. Step-by-step Install</A
></H1 ></H1
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN509" NAME="AEN509"
>3.2.1. Introduction</A >3.2.1. Introduction</A
></H2 ></H2
><P ><P
> Installation of bugzilla is pretty straightforward, particularly if your >&#13; Installation of bugzilla is pretty straightforward, particularly if your
machine already has MySQL and the MySQL-related perl packages installed. machine already has MySQL and the MySQL-related perl packages installed.
If those aren't installed yet, then that's the first order of business. The If those aren't installed yet, then that's the first order of business. The
other necessary ingredient is a web server set up to run cgi scripts. other necessary ingredient is a web server set up to run cgi scripts.
While using Apache for your webserver is not required, it is recommended. While using Apache for your webserver is not required, it is recommended.
</P </P
><P ><P
> Bugzilla has been successfully installed under Solaris, Linux, >&#13; Bugzilla has been successfully installed under Solaris, Linux,
and Win32. The peculiarities of installing on Win32 (Microsoft and Win32. The peculiarities of installing on Win32 (Microsoft
Windows) are not included in this section of the Guide; please Windows) are not included in this section of the Guide; please
check out the <A check out the <A
...@@ -99,25 +99,25 @@ HREF="win32.html" ...@@ -99,25 +99,25 @@ HREF="win32.html"
on getting Bugzilla to work on Microsoft Windows. on getting Bugzilla to work on Microsoft Windows.
</P </P
><P ><P
> The Bugzilla Guide is contained in the "docs/" folder in your >&#13; The Bugzilla Guide is contained in the "docs/" folder in your
Bugzilla distribution. It is available in plain text Bugzilla distribution. It is available in plain text
(docs/txt), HTML (docs/html), or SGML source (docs/sgml). (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN515" NAME="AEN515"
>3.2.2. Installing the Prerequisites</A >3.2.2. Installing the Prerequisites</A
></H2 ></H2
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -138,7 +138,7 @@ VALIGN="TOP" ...@@ -138,7 +138,7 @@ VALIGN="TOP"
most recent version of Perl and MySQL (both the executables most recent version of Perl and MySQL (both the executables
and development libraries) on your system, check out and development libraries) on your system, check out
Bundle::Bugzilla in <A Bundle::Bugzilla in <A
HREF="stepbystep.html#BUNDLEBUGZILLA" HREF="stepbystep.html#bundlebugzilla"
>Using Bundle::Bugzilla instead of manually installing Perl modules</A >Using Bundle::Bugzilla instead of manually installing Perl modules</A
></P ></P
></TD ></TD
...@@ -146,76 +146,76 @@ HREF="stepbystep.html#BUNDLEBUGZILLA" ...@@ -146,76 +146,76 @@ HREF="stepbystep.html#BUNDLEBUGZILLA"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> The software packages necessary for the proper running of bugzilla are: >&#13; The software packages necessary for the proper running of bugzilla are:
<P <P
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> MySQL database server and the mysql client (3.22.5 or greater) >&#13; MySQL database server and the mysql client (3.22.5 or greater)
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Perl (5.004 or greater, 5.6.1 is recommended if you wish >&#13; Perl (5.004 or greater, 5.6.1 is recommended if you wish
to use Bundle::Bugzilla) to use Bundle::Bugzilla)
</P </P
></LI ></LI
><LI ><LI
><P ><P
> DBI Perl module >&#13; DBI Perl module
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Data::Dumper Perl module >&#13; Data::Dumper Perl module
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Bundle::Mysql Perl module collection >&#13; Bundle::Mysql Perl module collection
</P </P
></LI ></LI
><LI ><LI
><P ><P
> TimeDate Perl module collection >&#13; TimeDate Perl module collection
</P </P
></LI ></LI
><LI ><LI
><P ><P
> GD perl module (1.8.3) (optional, for bug charting) >&#13; GD perl module (1.8.3) (optional, for bug charting)
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Chart::Base Perl module (0.99c) (optional, for bug charting) >&#13; Chart::Base Perl module (0.99c) (optional, for bug charting)
</P </P
></LI ></LI
><LI ><LI
><P ><P
> DB_File Perl module (optional, for bug charting) >&#13; DB_File Perl module (optional, for bug charting)
</P </P
></LI ></LI
><LI ><LI
><P ><P
> The web server of your choice. Apache is recommended. >&#13; The web server of your choice. Apache is recommended.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface) >&#13; MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</P </P
></LI ></LI
></OL ></OL
> >
<DIV <DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -231,7 +231,7 @@ ALT="Warning"></TD ...@@ -231,7 +231,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> It is a good idea, while installing Bugzilla, to ensure it >&#13; It is a good idea, while installing Bugzilla, to ensure it
is not <EM is not <EM
>accessible</EM >accessible</EM
> by other machines > by other machines
...@@ -249,11 +249,11 @@ VALIGN="TOP" ...@@ -249,11 +249,11 @@ VALIGN="TOP"
></DIV ></DIV
> >
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -273,12 +273,12 @@ VALIGN="TOP" ...@@ -273,12 +273,12 @@ VALIGN="TOP"
every required and optional library for Bugzilla. The every required and optional library for Bugzilla. The
easiest way to install them is by using the easiest way to install them is by using the
<TT <TT
CLASS="FILENAME" CLASS="filename"
>urpmi</TT >urpmi</TT
> utility. If you follow these > utility. If you follow these
commands, you should have everything you need for commands, you should have everything you need for
Bugzilla, and <TT Bugzilla, and <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
> should > should
not complain about any missing libraries. You may already not complain about any missing libraries. You may already
...@@ -291,10 +291,10 @@ BORDER="0" ...@@ -291,10 +291,10 @@ BORDER="0"
><TR ><TR
><TD ><TD
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
> urpmi > urpmi
perl-mysql</B perl-mysql</B
></TD ></TD
...@@ -302,10 +302,10 @@ CLASS="COMMAND" ...@@ -302,10 +302,10 @@ CLASS="COMMAND"
><TR ><TR
><TD ><TD
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
> urpmi > urpmi
perl-chart</B perl-chart</B
></TD ></TD
...@@ -313,10 +313,10 @@ CLASS="COMMAND" ...@@ -313,10 +313,10 @@ CLASS="COMMAND"
><TR ><TR
><TD ><TD
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
> urpmi > urpmi
perl-gd</B perl-gd</B
></TD ></TD
...@@ -324,10 +324,10 @@ CLASS="COMMAND" ...@@ -324,10 +324,10 @@ CLASS="COMMAND"
><TR ><TR
><TD ><TD
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
> urpmi > urpmi
perl-MailTools</B perl-MailTools</B
> (for Bugzilla email > (for Bugzilla email
...@@ -336,10 +336,10 @@ CLASS="COMMAND" ...@@ -336,10 +336,10 @@ CLASS="COMMAND"
><TR ><TR
><TD ><TD
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
><B ><B
CLASS="COMMAND" CLASS="command"
> urpmi > urpmi
apache-modules</B apache-modules</B
></TD ></TD
...@@ -357,42 +357,42 @@ CLASS="COMMAND" ...@@ -357,42 +357,42 @@ CLASS="COMMAND"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="INSTALL-MYSQL" NAME="install-mysql"
>3.2.3. Installing MySQL Database</A >3.2.3. Installing MySQL Database</A
></H2 ></H2
><P ><P
> Visit MySQL homepage at <A >&#13; Visit MySQL homepage at <A
HREF="http://www.mysql.com" HREF="http://www.mysql.com"
TARGET="_top" TARGET="_top"
>www.mysql.com</A >www.mysql.com</A
> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT > and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT
CLASS="FILENAME" CLASS="filename"
>/var</TT >/var</TT
> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT > which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
CLASS="FILENAME" CLASS="filename"
>configure</TT >configure</TT
>. >.
</P </P
><P ><P
> If you install from source or non-package (RPM, deb, etc.) >&#13; If you install from source or non-package (RPM, deb, etc.)
binaries you need to add binaries you need to add
<I <I
CLASS="FIRSTTERM" CLASS="firstterm"
>mysqld</I >mysqld</I
> to your > to your
init scripts so the server daemon will come back up whenever init scripts so the server daemon will come back up whenever
your machine reboots. Further discussion of UNIX init your machine reboots. Further discussion of UNIX init
sequences are beyond the scope of this guide. sequences are beyond the scope of this guide.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -410,25 +410,25 @@ VALIGN="TOP" ...@@ -410,25 +410,25 @@ VALIGN="TOP"
><P ><P
>You should have your init script start >You should have your init script start
<I <I
CLASS="GLOSSTERM" CLASS="glossterm"
>mysqld</I >mysqld</I
> with the ability to accept > with the ability to accept
large packets. By default, <TT large packets. By default, <TT
CLASS="FILENAME" CLASS="filename"
>mysqld</TT >mysqld</TT
> >
only accepts packets up to 64K long. This limits the size only accepts packets up to 64K long. This limits the size
of attachments you may put on bugs. If you add <TT of attachments you may put on bugs. If you add <TT
CLASS="OPTION" CLASS="option"
>-O >-O
max_allowed_packet=1M</TT max_allowed_packet=1M</TT
> to the command that starts > to the command that starts
<TT <TT
CLASS="FILENAME" CLASS="filename"
>mysqld</TT >mysqld</TT
> (or > (or
<TT <TT
CLASS="FILENAME" CLASS="filename"
>safe_mysqld</TT >safe_mysqld</TT
>), then you will be able >), then you will be able
to have attachments up to about 1 megabyte.</P to have attachments up to about 1 megabyte.</P
...@@ -440,11 +440,11 @@ CLASS="FILENAME" ...@@ -440,11 +440,11 @@ CLASS="FILENAME"
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -460,9 +460,9 @@ ALT="Note"></TD ...@@ -460,9 +460,9 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you plan on running Bugzilla and MySQL on the same >&#13; If you plan on running Bugzilla and MySQL on the same
machine, consider using the <TT machine, consider using the <TT
CLASS="OPTION" CLASS="option"
>--skip-networking</TT >--skip-networking</TT
> >
option in the init script. This enhances security by option in the init script. This enhances security by
...@@ -474,15 +474,15 @@ CLASS="OPTION" ...@@ -474,15 +474,15 @@ CLASS="OPTION"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="INSTALL-PERL" NAME="install-perl"
>3.2.4. Perl (5.004 or greater)</A >3.2.4. Perl (5.004 or greater)</A
></H2 ></H2
><P ><P
> Any machine that doesn't have perl on it is a sad machine >&#13; Any machine that doesn't have perl on it is a sad machine
indeed. Perl for *nix systems can be gotten in source form indeed. Perl for *nix systems can be gotten in source form
from http://www.perl.com. Although Bugzilla runs with most from http://www.perl.com. Although Bugzilla runs with most
post-5.004 versions of Perl, it's a good idea to be up to the post-5.004 versions of Perl, it's a good idea to be up to the
...@@ -490,7 +490,7 @@ NAME="INSTALL-PERL" ...@@ -490,7 +490,7 @@ NAME="INSTALL-PERL"
this writing, that is perl version 5.6.1. this writing, that is perl version 5.6.1.
</P </P
><P ><P
> Perl is now a far cry from the the single compiler/interpreter >&#13; Perl is now a far cry from the the single compiler/interpreter
binary it once was. It includes a great many required modules binary it once was. It includes a great many required modules
and quite a few other support files. If you're not up to or and quite a few other support files. If you're not up to or
not inclined to build perl from source, you'll want to install not inclined to build perl from source, you'll want to install
...@@ -501,11 +501,11 @@ NAME="INSTALL-PERL" ...@@ -501,11 +501,11 @@ NAME="INSTALL-PERL"
isn't up to snuff. isn't up to snuff.
</P </P
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -543,14 +543,14 @@ CLASS="QUOTE" ...@@ -543,14 +543,14 @@ CLASS="QUOTE"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><A ><A
NAME="BUNDLEBUGZILLA" NAME="bundlebugzilla"
></A ></A
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -566,15 +566,15 @@ ALT="Tip"></TD ...@@ -566,15 +566,15 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You can skip the following Perl module installation steps by >&#13; You can skip the following Perl module installation steps by
installing <SPAN installing <SPAN
CLASS="PRODUCTNAME" CLASS="productname"
>Bundle::Bugzilla</SPAN >Bundle::Bugzilla</SPAN
> from > from
<A <A
HREF="glossary.html#GLOSS_CPAN" HREF="glossary.html#gloss-cpan"
><I ><I
CLASS="GLOSSTERM" CLASS="glossterm"
>CPAN</I >CPAN</I
></A ></A
>, which >, which
...@@ -584,13 +584,13 @@ CLASS="GLOSSTERM" ...@@ -584,13 +584,13 @@ CLASS="GLOSSTERM"
version of Perl (at this writing, version 5.6.1) version of Perl (at this writing, version 5.6.1)
</P </P
><P ><P
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>perl -MCPAN >perl -MCPAN
-e 'install "Bundle::Bugzilla"'</B -e 'install "Bundle::Bugzilla"'</B
> >
...@@ -598,7 +598,7 @@ CLASS="COMMAND" ...@@ -598,7 +598,7 @@ CLASS="COMMAND"
> >
</P </P
><P ><P
> Bundle::Bugzilla doesn't include GD, Chart::Base, or >&#13; Bundle::Bugzilla doesn't include GD, Chart::Base, or
MIME::Parser, which are not essential to a basic Bugzilla MIME::Parser, which are not essential to a basic Bugzilla
install. If installing this bundle fails, you should install. If installing this bundle fails, you should
install each module individually to isolate the problem. install each module individually to isolate the problem.
...@@ -609,22 +609,22 @@ CLASS="COMMAND" ...@@ -609,22 +609,22 @@ CLASS="COMMAND"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN602" NAME="AEN602"
>3.2.5. DBI Perl Module</A >3.2.5. DBI Perl Module</A
></H2 ></H2
><P ><P
> The DBI module is a generic Perl module used by other database related >&#13; The DBI module is a generic Perl module used by other database related
Perl modules. For our purposes it's required by the MySQL-related Perl modules. For our purposes it's required by the MySQL-related
modules. As long as your Perl installation was done correctly the modules. As long as your Perl installation was done correctly the
DBI module should be a breeze. It's a mixed Perl/C module, but Perl's DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
MakeMaker system simplifies the C compilation greatly. MakeMaker system simplifies the C compilation greatly.
</P </P
><P ><P
> Like almost all Perl modules DBI can be found on the Comprehensive Perl >&#13; Like almost all Perl modules DBI can be found on the Comprehensive Perl
Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
real tendency to bog down, so please use mirrors. The current location real tendency to bog down, so please use mirrors. The current location
at the time of this writing can be found in <A at the time of this writing can be found in <A
...@@ -633,38 +633,38 @@ HREF="downloadlinks.html" ...@@ -633,38 +633,38 @@ HREF="downloadlinks.html"
>. >.
</P </P
><P ><P
> Quality, general Perl module installation instructions can be found on >&#13; Quality, general Perl module installation instructions can be found on
the CPAN website, but the easy thing to do is to just use the CPAN shell the CPAN website, but the easy thing to do is to just use the CPAN shell
which does all the hard work for you. which does all the hard work for you.
</P </P
><P ><P
> To use the CPAN shell to install DBI: >&#13; To use the CPAN shell to install DBI:
<DIV <DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN609" NAME="AEN609"
></A ></A
><P ><P
></P ></P
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>perl -MCPAN -e 'install "DBI"'</B >perl -MCPAN -e 'install "DBI"'</B
> >
</TT </TT
> >
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -694,31 +694,31 @@ VALIGN="TOP" ...@@ -694,31 +694,31 @@ VALIGN="TOP"
> >
To do it the hard way: To do it the hard way:
<DIV <DIV
CLASS="INFORMALEXAMPLE" CLASS="informalexample"
><A ><A
NAME="AEN616" NAME="AEN616"
></A ></A
><P ><P
></P ></P
><P ><P
> Untar the module tarball -- it should create its own directory >&#13; Untar the module tarball -- it should create its own directory
</P </P
><P ><P
> CD to the directory just created, and enter the following commands: >&#13; CD to the directory just created, and enter the following commands:
<P <P
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>perl Makefile.PL</B >perl Makefile.PL</B
> >
</TT </TT
...@@ -727,14 +727,14 @@ CLASS="COMMAND" ...@@ -727,14 +727,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>make</B >make</B
> >
</TT </TT
...@@ -743,14 +743,14 @@ CLASS="COMMAND" ...@@ -743,14 +743,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>make test</B >make test</B
> >
</TT </TT
...@@ -759,14 +759,14 @@ CLASS="COMMAND" ...@@ -759,14 +759,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>make install</B >make install</B
> >
</TT </TT
...@@ -785,21 +785,21 @@ CLASS="COMMAND" ...@@ -785,21 +785,21 @@ CLASS="COMMAND"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN640" NAME="AEN640"
>3.2.6. Data::Dumper Perl Module</A >3.2.6. Data::Dumper Perl Module</A
></H2 ></H2
><P ><P
> The Data::Dumper module provides data structure persistence for Perl >&#13; The Data::Dumper module provides data structure persistence for Perl
(similar to Java's serialization). It comes with later sub-releases of (similar to Java's serialization). It comes with later sub-releases of
Perl 5.004, but a re-installation just to be sure it's available won't Perl 5.004, but a re-installation just to be sure it's available won't
hurt anything. hurt anything.
</P </P
><P ><P
> Data::Dumper is used by the MySQL-related Perl modules. It >&#13; Data::Dumper is used by the MySQL-related Perl modules. It
can be found on CPAN (see <A can be found on CPAN (see <A
HREF="downloadlinks.html" HREF="downloadlinks.html"
>Appendix B</A >Appendix B</A
...@@ -810,45 +810,45 @@ HREF="downloadlinks.html" ...@@ -810,45 +810,45 @@ HREF="downloadlinks.html"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN645" NAME="AEN645"
>3.2.7. MySQL related Perl Module Collection</A >3.2.7. MySQL related Perl Module Collection</A
></H2 ></H2
><P ><P
> The Perl/MySQL interface requires a few mutually-dependent perl >&#13; The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN. Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should After the archive file has been downloaded it should
be untarred. be untarred.
</P </P
><P ><P
> The MySQL modules are all built using one make file which is generated >&#13; The MySQL modules are all built using one make file which is generated
by running: by running:
<TT <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>perl Makefile.pl</B >perl Makefile.pl</B
> >
</P </P
><P ><P
> The MakeMaker process will ask you a few questions about the desired >&#13; The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions compilation target and your MySQL installation. For many of the questions
the provided default will be adequate. the provided default will be adequate.
</P </P
><P ><P
> When asked if your desired target is the MySQL or mSQL packages, >&#13; When asked if your desired target is the MySQL or mSQL packages,
select the MySQL related ones. Later you will be asked if you wish select the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you to provide backwards compatibility with the older MySQL packages; you
should answer YES to this question. The default is NO. should answer YES to this question. The default is NO.
</P </P
><P ><P
> A host of 'localhost' should be fine and a testing user of 'test' and >&#13; A host of 'localhost' should be fine and a testing user of 'test' and
a null password should find itself with sufficient access to run tests a null password should find itself with sufficient access to run tests
on the 'test' database which MySQL created upon installation. If 'make on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready test' and 'make install' go through without errors you should be ready
...@@ -856,15 +856,15 @@ CLASS="COMMAND" ...@@ -856,15 +856,15 @@ CLASS="COMMAND"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN654" NAME="AEN654"
>3.2.8. TimeDate Perl Module Collection</A >3.2.8. TimeDate Perl Module Collection</A
></H2 ></H2
><P ><P
> Many of the more common date/time/calendar related Perl >&#13; Many of the more common date/time/calendar related Perl
modules have been grouped into a bundle similar to the MySQL modules have been grouped into a bundle similar to the MySQL
modules bundle. This bundle is stored on the CPAN under the modules bundle. This bundle is stored on the CPAN under the
name TimeDate (see link: <A name TimeDate (see link: <A
...@@ -878,15 +878,15 @@ HREF="downloadlinks.html" ...@@ -878,15 +878,15 @@ HREF="downloadlinks.html"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN658" NAME="AEN658"
>3.2.9. GD Perl Module (1.8.3)</A >3.2.9. GD Perl Module (1.8.3)</A
></H2 ></H2
><P ><P
> The GD library was written by Thomas Boutell a long while >&#13; The GD library was written by Thomas Boutell a long while
ago to programatically generate images in C. Since then it's ago to programatically generate images in C. Since then it's
become the defacto standard for programatic image become the defacto standard for programatic image
construction. The Perl bindings to it found in the GD library construction. The Perl bindings to it found in the GD library
...@@ -895,7 +895,7 @@ NAME="AEN658" ...@@ -895,7 +895,7 @@ NAME="AEN658"
install it if you want any of the graphing to work. install it if you want any of the graphing to work.
</P </P
><P ><P
> Actually bugzilla uses the Graph module which relies on GD >&#13; Actually bugzilla uses the Graph module which relies on GD
itself. Isn't that always the way with object-oriented itself. Isn't that always the way with object-oriented
programming? At any rate, you can find the GD library on CPAN programming? At any rate, you can find the GD library on CPAN
in <A in <A
...@@ -904,11 +904,11 @@ HREF="downloadlinks.html" ...@@ -904,11 +904,11 @@ HREF="downloadlinks.html"
>. >.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -924,14 +924,14 @@ ALT="Note"></TD ...@@ -924,14 +924,14 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> The Perl GD library requires some other libraries that may >&#13; The Perl GD library requires some other libraries that may
or may not be installed on your system, including or may not be installed on your system, including
<TT <TT
CLASS="CLASSNAME" CLASS="classname"
>libpng</TT >libpng</TT
> and > and
<TT <TT
CLASS="CLASSNAME" CLASS="classname"
>libgd</TT >libgd</TT
>. The full requirements are >. The full requirements are
listed in the Perl GD library README. Just realize that if listed in the Perl GD library README. Just realize that if
...@@ -944,15 +944,15 @@ CLASS="CLASSNAME" ...@@ -944,15 +944,15 @@ CLASS="CLASSNAME"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN667" NAME="AEN667"
>3.2.10. Chart::Base Perl Module (0.99c)</A >3.2.10. Chart::Base Perl Module (0.99c)</A
></H2 ></H2
><P ><P
> The Chart module provides bugzilla with on-the-fly charting >&#13; The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it abilities. It can be installed in the usual fashion after it
has been fetched from CPAN where it is found as the has been fetched from CPAN where it is found as the
Chart-x.x... tarball, linked in <A Chart-x.x... tarball, linked in <A
...@@ -965,15 +965,15 @@ HREF="downloadlinks.html" ...@@ -965,15 +965,15 @@ HREF="downloadlinks.html"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN671" NAME="AEN671"
>3.2.11. DB_File Perl Module</A >3.2.11. DB_File Perl Module</A
></H2 ></H2
><P ><P
> DB_File is a module which allows Perl programs to make use >&#13; DB_File is a module which allows Perl programs to make use
of the facilities provided by Berkeley DB version 1.x. This of the facilities provided by Berkeley DB version 1.x. This
module is required by collectstats.pl which is used for bug module is required by collectstats.pl which is used for bug
charting. If you plan to make use of bug charting, you must charting. If you plan to make use of bug charting, you must
...@@ -981,15 +981,15 @@ NAME="AEN671" ...@@ -981,15 +981,15 @@ NAME="AEN671"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN674" NAME="AEN674"
>3.2.12. HTTP Server</A >3.2.12. HTTP Server</A
></H2 ></H2
><P ><P
> You have a freedom of choice here - Apache, Netscape or any >&#13; You have a freedom of choice here - Apache, Netscape or any
other server on UNIX would do. You can easily run the web other server on UNIX would do. You can easily run the web
server on a different machine than MySQL, but need to adjust server on a different machine than MySQL, but need to adjust
the MySQL <SPAN the MySQL <SPAN
...@@ -997,11 +997,11 @@ CLASS="QUOTE" ...@@ -997,11 +997,11 @@ CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> user permissions accordingly. > user permissions accordingly.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1030,7 +1030,7 @@ VALIGN="TOP" ...@@ -1030,7 +1030,7 @@ VALIGN="TOP"
> >
</P </P
><P ><P
> You'll want to make sure that your web server will run any >&#13; You'll want to make sure that your web server will run any
file with the .cgi extension as a cgi and not just display it. file with the .cgi extension as a cgi and not just display it.
If you're using apache that means uncommenting the following If you're using apache that means uncommenting the following
line in the srm.conf file: line in the srm.conf file:
...@@ -1043,8 +1043,8 @@ WIDTH="100%" ...@@ -1043,8 +1043,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>AddHandler cgi-script .cgi >&#13;AddHandler cgi-script .cgi
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -1053,7 +1053,7 @@ CLASS="PROGRAMLISTING" ...@@ -1053,7 +1053,7 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><P ><P
> With apache you'll also want to make sure that within the >&#13; With apache you'll also want to make sure that within the
access.conf file the line: access.conf file the line:
<TABLE <TABLE
BORDER="0" BORDER="0"
...@@ -1064,8 +1064,9 @@ WIDTH="100%" ...@@ -1064,8 +1064,9 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>Options ExecCGI</PRE >&#13;Options ExecCGI
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1075,11 +1076,11 @@ CLASS="PROGRAMLISTING" ...@@ -1075,11 +1076,11 @@ CLASS="PROGRAMLISTING"
you intend to put the bugzilla .html and .cgi files. you intend to put the bugzilla .html and .cgi files.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1095,7 +1096,7 @@ ALT="Note"></TD ...@@ -1095,7 +1096,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Users of newer versions of Apache will generally find both >&#13; Users of newer versions of Apache will generally find both
of the above lines will be in the httpd.conf file, rather of the above lines will be in the httpd.conf file, rather
than srm.conf or access.conf. than srm.conf or access.conf.
</P </P
...@@ -1104,11 +1105,11 @@ VALIGN="TOP" ...@@ -1104,11 +1105,11 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1124,7 +1125,7 @@ ALT="Warning"></TD ...@@ -1124,7 +1125,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> There are important files and directories that should not >&#13; There are important files and directories that should not
be a served by the HTTP server. These are most files in the be a served by the HTTP server. These are most files in the
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1140,7 +1141,7 @@ CLASS="QUOTE" ...@@ -1140,7 +1141,7 @@ CLASS="QUOTE"
configure your HTTP server to not serve content from these configure your HTTP server to not serve content from these
files. Failure to do so will expose critical passwords and files. Failure to do so will expose critical passwords and
other data. Please see <A other data. Please see <A
HREF="geninstall.html#HTACCESS" HREF="geninstall.html#htaccess"
>.htaccess files and security</A >.htaccess files and security</A
> for details > for details
on how to do this for Apache. I appreciate notes on how to on how to do this for Apache. I appreciate notes on how to
...@@ -1152,15 +1153,15 @@ HREF="geninstall.html#HTACCESS" ...@@ -1152,15 +1153,15 @@ HREF="geninstall.html#HTACCESS"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN692" NAME="AEN692"
>3.2.13. Installing the Bugzilla Files</A >3.2.13. Installing the Bugzilla Files</A
></H2 ></H2
><P ><P
> You should untar the Bugzilla files into a directory that >&#13; You should untar the Bugzilla files into a directory that
you're willing to make writable by the default web server user you're willing to make writable by the default web server user
(probably <SPAN (probably <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1168,7 +1169,7 @@ CLASS="QUOTE" ...@@ -1168,7 +1169,7 @@ CLASS="QUOTE"
>). You may decide to put the >). You may decide to put the
files off of the main web space for your web server or perhaps files off of the main web space for your web server or perhaps
off of <TT off of <TT
CLASS="FILENAME" CLASS="filename"
>/usr/local</TT >/usr/local</TT
> with a symbolic link in > with a symbolic link in
the web space that points to the Bugzilla directory. At any the web space that points to the Bugzilla directory. At any
...@@ -1177,11 +1178,11 @@ CLASS="FILENAME" ...@@ -1177,11 +1178,11 @@ CLASS="FILENAME"
server. server.
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1197,10 +1198,10 @@ ALT="Tip"></TD ...@@ -1197,10 +1198,10 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you symlink the bugzilla directory into your Apache's >&#13; If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive HTML heirarchy, you may receive
<SPAN <SPAN
CLASS="ERRORNAME" CLASS="errorname"
>Forbidden</SPAN >Forbidden</SPAN
> errors unless you add the > errors unless you add the
<SPAN <SPAN
...@@ -1214,24 +1215,24 @@ CLASS="QUOTE" ...@@ -1214,24 +1215,24 @@ CLASS="QUOTE"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> Once all the files are in a web accessible directory, make >&#13; Once all the files are in a web accessible directory, make
that directory writable by your webserver's user. This is a that directory writable by your webserver's user. This is a
temporary step until you run the post-install temporary step until you run the post-install
<TT <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
> script, which locks down your > script, which locks down your
installation. installation.
</P </P
><P ><P
> Lastly, you'll need to set up a symbolic link to >&#13; Lastly, you'll need to set up a symbolic link to
<TT <TT
CLASS="FILENAME" CLASS="filename"
>/usr/bonsaitools/bin/perl</TT >/usr/bonsaitools/bin/perl</TT
> for the correct > for the correct
location of your perl executable (probably location of your perl executable (probably
<TT <TT
CLASS="FILENAME" CLASS="filename"
>/usr/bin/perl</TT >/usr/bin/perl</TT
>). Otherwise you must hack >). Otherwise you must hack
all the .cgi files to change where they look for perl, or use all the .cgi files to change where they look for perl, or use
...@@ -1245,7 +1246,7 @@ HREF="patches.html" ...@@ -1245,7 +1246,7 @@ HREF="patches.html"
>. I suggest using the symlink >. I suggest using the symlink
approach for future release compatability. approach for future release compatability.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN708" NAME="AEN708"
></A ></A
...@@ -1254,7 +1255,7 @@ NAME="AEN708" ...@@ -1254,7 +1255,7 @@ NAME="AEN708"
>Example 3-1. Setting up bonsaitools symlink</B >Example 3-1. Setting up bonsaitools symlink</B
></P ></P
><P ><P
> Here's how you set up the Perl symlink on Linux to make >&#13; Here's how you set up the Perl symlink on Linux to make
Bugzilla work. Your mileage may vary. For some UNIX Bugzilla work. Your mileage may vary. For some UNIX
operating systems, you probably need to subsitute operating systems, you probably need to subsitute
<SPAN <SPAN
...@@ -1279,8 +1280,8 @@ WIDTH="100%" ...@@ -1279,8 +1280,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>bash# mkdir /usr/bonsaitools >&#13;bash# mkdir /usr/bonsaitools
bash# mkdir /usr/bonsaitools/bin bash# mkdir /usr/bonsaitools/bin
bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl
</PRE </PRE
...@@ -1291,7 +1292,7 @@ bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl ...@@ -1291,7 +1292,7 @@ bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl
> >
</P </P
><P ><P
> Alternately, you can simply run this perl one-liner to >&#13; Alternately, you can simply run this perl one-liner to
change your path to perl in all the files in your Bugzilla change your path to perl in all the files in your Bugzilla
installation: installation:
<TABLE <TABLE
...@@ -1303,8 +1304,8 @@ WIDTH="100%" ...@@ -1303,8 +1304,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm >&#13;perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -1316,11 +1317,11 @@ CLASS="PROGRAMLISTING" ...@@ -1316,11 +1317,11 @@ CLASS="PROGRAMLISTING"
></DIV ></DIV
> >
<DIV <DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1336,7 +1337,7 @@ ALT="Tip"></TD ...@@ -1336,7 +1337,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you don't have root access to set this symlink up, >&#13; If you don't have root access to set this symlink up,
check out the check out the
<A <A
HREF="setperl.html" HREF="setperl.html"
...@@ -1354,20 +1355,20 @@ HREF="patches.html" ...@@ -1354,20 +1355,20 @@ HREF="patches.html"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN721" NAME="AEN721"
>3.2.14. Setting Up the MySQL Database</A >3.2.14. Setting Up the MySQL Database</A
></H2 ></H2
><P ><P
> After you've gotten all the software installed and working you're ready >&#13; After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high to start preparing the database for its life as a the back end to a high
quality bug tracker. quality bug tracker.
</P </P
><P ><P
> First, you'll want to fix MySQL permissions to allow access >&#13; First, you'll want to fix MySQL permissions to allow access
from Bugzilla. For the purpose of this Installation section, from Bugzilla. For the purpose of this Installation section,
the Bugzilla username will be <SPAN the Bugzilla username will be <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1376,11 +1377,11 @@ CLASS="QUOTE" ...@@ -1376,11 +1377,11 @@ CLASS="QUOTE"
have minimal permissions. have minimal permissions.
<DIV <DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1396,10 +1397,10 @@ ALT="Warning"></TD ...@@ -1396,10 +1397,10 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Bugzilla has not undergone a thorough security audit. It >&#13; Bugzilla has not undergone a thorough security audit. It
may be possible for a system cracker to somehow trick may be possible for a system cracker to somehow trick
Bugzilla into executing a command such as <B Bugzilla into executing a command such as <B
CLASS="COMMAND" CLASS="command"
>DROP >DROP
DATABASE mysql</B DATABASE mysql</B
>. >.
...@@ -1413,7 +1414,7 @@ CLASS="COMMAND" ...@@ -1413,7 +1414,7 @@ CLASS="COMMAND"
> >
</P </P
><P ><P
> Give the MySQL root user a password. MySQL passwords are >&#13; Give the MySQL root user a password. MySQL passwords are
limited to 16 characters. limited to 16 characters.
<P <P
></P ></P
...@@ -1422,13 +1423,13 @@ BORDER="0" ...@@ -1422,13 +1423,13 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>mysql >mysql
-u root mysql</B -u root mysql</B
> </TT > </TT
...@@ -1437,14 +1438,14 @@ CLASS="COMMAND" ...@@ -1437,14 +1438,14 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT >mysql&#62;</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
> UPDATE user SET Password=PASSWORD ('new_password') >&#13; UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root'; </B WHERE user='root'; </B
> </TT > </TT
> >
...@@ -1452,13 +1453,13 @@ CLASS="COMMAND" ...@@ -1452,13 +1453,13 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT >mysql&#62;</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>FLUSH >FLUSH
PRIVILEGES;</B PRIVILEGES;</B
> </TT > </TT
...@@ -1472,14 +1473,14 @@ CLASS="COMMAND" ...@@ -1472,14 +1473,14 @@ CLASS="COMMAND"
> From this point on, if you need to access > From this point on, if you need to access
MySQL as the MySQL root user, you will need to use MySQL as the MySQL root user, you will need to use
<B <B
CLASS="COMMAND" CLASS="command"
>mysql -u root -p</B >mysql -u root -p</B
> and enter your > and enter your
new_password. Remember that MySQL user names have nothing to new_password. Remember that MySQL user names have nothing to
do with Unix user names (login names). do with Unix user names (login names).
</P </P
><P ><P
> Next, we create the <SPAN >&#13; Next, we create the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> user, and grant > user, and grant
...@@ -1501,7 +1502,7 @@ CLASS="QUOTE" ...@@ -1501,7 +1502,7 @@ CLASS="QUOTE"
as a different user. as a different user.
</P </P
><P ><P
> Remember to set bugs_password to some unique password. >&#13; Remember to set bugs_password to some unique password.
<P <P
></P ></P
><TABLE ><TABLE
...@@ -1509,14 +1510,14 @@ BORDER="0" ...@@ -1509,14 +1510,14 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, >GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost ON bugs.* TO bugs@localhost
...@@ -1528,16 +1529,16 @@ CLASS="COMMAND" ...@@ -1528,16 +1529,16 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
> mysql&#62; >&#13; mysql&#62;
</TT </TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
> FLUSH PRIVILEGES; >&#13; FLUSH PRIVILEGES;
</B </B
> >
</TT </TT
...@@ -1551,12 +1552,12 @@ CLASS="COMMAND" ...@@ -1551,12 +1552,12 @@ CLASS="COMMAND"
> >
</P </P
><P ><P
> Next, run the magic checksetup.pl script. (Many thanks to >&#13; Next, run the magic checksetup.pl script. (Many thanks to
Holger Schurig &#60;holgerschurig@nikocity.de&#62; for writing Holger Schurig &#60;holgerschurig@nikocity.de&#62; for writing
this script!) It will make sure Bugzilla files and directories this script!) It will make sure Bugzilla files and directories
have reasonable permissions, set up the have reasonable permissions, set up the
<TT <TT
CLASS="FILENAME" CLASS="filename"
>data</TT >data</TT
> directory, and create all the MySQL > directory, and create all the MySQL
tables. tables.
...@@ -1567,14 +1568,14 @@ BORDER="0" ...@@ -1567,14 +1568,14 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>./checksetup.pl</B >./checksetup.pl</B
> </TT > </TT
> >
...@@ -1586,35 +1587,35 @@ CLASS="COMMAND" ...@@ -1586,35 +1587,35 @@ CLASS="COMMAND"
></P ></P
> The first time you run it, it will create a > The first time you run it, it will create a
file called <TT file called <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
>. >.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN768" NAME="AEN768"
>3.2.15. Tweaking <TT >3.2.15. Tweaking <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
></A ></A
></H2 ></H2
><P ><P
> This file contains a variety of settings you may need to tweak including >&#13; This file contains a variety of settings you may need to tweak including
how Bugzilla should connect to the MySQL database. how Bugzilla should connect to the MySQL database.
</P </P
><P ><P
> The connection settings include: >&#13; The connection settings include:
<P <P
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> server's host: just use <SPAN >&#13; server's host: just use <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"localhost"</SPAN >"localhost"</SPAN
> if the > if the
...@@ -1623,7 +1624,7 @@ CLASS="QUOTE" ...@@ -1623,7 +1624,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> database name: <SPAN >&#13; database name: <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> if you're following > if you're following
...@@ -1632,7 +1633,7 @@ CLASS="QUOTE" ...@@ -1632,7 +1633,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> MySQL username: <SPAN >&#13; MySQL username: <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> if you're following > if you're following
...@@ -1641,7 +1642,7 @@ CLASS="QUOTE" ...@@ -1641,7 +1642,7 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> Password for the <SPAN >&#13; Password for the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"bugs"</SPAN >"bugs"</SPAN
> MySQL account above > MySQL account above
...@@ -1651,24 +1652,24 @@ CLASS="QUOTE" ...@@ -1651,24 +1652,24 @@ CLASS="QUOTE"
> >
</P </P
><P ><P
> You should also install .htaccess files that the Apache >&#13; You should also install .htaccess files that the Apache
webserver will use to restrict access to Bugzilla data files. webserver will use to restrict access to Bugzilla data files.
See <A See <A
HREF="geninstall.html#HTACCESS" HREF="geninstall.html#htaccess"
>.htaccess files and security</A >.htaccess files and security</A
>. >.
</P </P
><P ><P
> Once you are happy with the settings, re-run >&#13; Once you are happy with the settings, re-run
<TT <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
>. On this second run, it will >. On this second run, it will
create the database and an administrator account for which create the database and an administrator account for which
you will be prompted to provide information. you will be prompted to provide information.
</P </P
><P ><P
> When logged into an administrator account once Bugzilla is >&#13; When logged into an administrator account once Bugzilla is
running, if you go to the query page (off of the Bugzilla main running, if you go to the query page (off of the Bugzilla main
menu), you'll find an <SPAN menu), you'll find an <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1677,20 +1678,20 @@ CLASS="QUOTE" ...@@ -1677,20 +1678,20 @@ CLASS="QUOTE"
that is filled with editable treats. that is filled with editable treats.
</P </P
><P ><P
> Should everything work, you will have a nearly empty Bugzilla >&#13; Should everything work, you will have a nearly empty Bugzilla
database and a newly-created <TT database and a newly-created <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
> >
file in your Bugzilla root directory. file in your Bugzilla root directory.
</P </P
><P ><P
> <DIV >&#13; <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1706,7 +1707,7 @@ ALT="Note"></TD ...@@ -1706,7 +1707,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> The second time you run checksetup.pl, you should become >&#13; The second time you run checksetup.pl, you should become
the user your web server runs as, and that you ensure that the user your web server runs as, and that you ensure that
you set the <SPAN you set the <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1720,7 +1721,7 @@ CLASS="QUOTE" ...@@ -1720,7 +1721,7 @@ CLASS="QUOTE"
> parameter in > parameter in
localconfig as well. localconfig as well.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN799" NAME="AEN799"
></A ></A
...@@ -1729,7 +1730,7 @@ NAME="AEN799" ...@@ -1729,7 +1730,7 @@ NAME="AEN799"
>Example 3-2. Running checksetup.pl as the web user</B >Example 3-2. Running checksetup.pl as the web user</B
></P ></P
><P ><P
> Assuming your web server runs as user "apache", and >&#13; Assuming your web server runs as user "apache", and
Bugzilla is installed in "/usr/local/bugzilla", here's Bugzilla is installed in "/usr/local/bugzilla", here's
one way to run checksetup.pl as the web server user. one way to run checksetup.pl as the web server user.
As root, for the <EM As root, for the <EM
...@@ -1745,7 +1746,7 @@ WIDTH="100%" ...@@ -1745,7 +1746,7 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> >
bash# chown -R apache:apache /usr/local/bugzilla bash# chown -R apache:apache /usr/local/bugzilla
bash# su - apache bash# su - apache
...@@ -1768,11 +1769,11 @@ bash# ./checksetup.pl ...@@ -1768,11 +1769,11 @@ bash# ./checksetup.pl
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1788,7 +1789,7 @@ ALT="Note"></TD ...@@ -1788,7 +1789,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> The checksetup.pl script is designed so that you can run >&#13; The checksetup.pl script is designed so that you can run
it at any time without causing harm. You should run it it at any time without causing harm. You should run it
after any upgrade to Bugzilla. after any upgrade to Bugzilla.
</P </P
...@@ -1798,18 +1799,18 @@ VALIGN="TOP" ...@@ -1798,18 +1799,18 @@ VALIGN="TOP"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN806" NAME="AEN806"
>3.2.16. Setting Up Maintainers Manually (Optional)</A >3.2.16. Setting Up Maintainers Manually (Optional)</A
></H2 ></H2
><P ><P
> If you want to add someone else to every group by hand, you >&#13; If you want to add someone else to every group by hand, you
can do it by typing the appropriate MySQL commands. Run can do it by typing the appropriate MySQL commands. Run
<B <B
CLASS="COMMAND" CLASS="command"
> mysql -u root -p bugs</B > mysql -u root -p bugs</B
> You > You
may need different parameters, depending on your security may need different parameters, depending on your security
...@@ -1821,13 +1822,13 @@ BORDER="0" ...@@ -1821,13 +1822,13 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT >mysql&#62;</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>update >update
profiles set groupset=0x7fffffffffffffff where profiles set groupset=0x7fffffffffffffff where
login_name = 'XXX';</B login_name = 'XXX';</B
...@@ -1848,15 +1849,15 @@ CLASS="QUOTE" ...@@ -1848,15 +1849,15 @@ CLASS="QUOTE"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN817" NAME="AEN817"
>3.2.17. The Whining Cron (Optional)</A >3.2.17. The Whining Cron (Optional)</A
></H2 ></H2
><P ><P
> By now you have a fully functional bugzilla, but what good >&#13; By now you have a fully functional bugzilla, but what good
are bugs if they're not annoying? To help make those bugs are bugs if they're not annoying? To help make those bugs
more annoying you can set up bugzilla's automatic whining more annoying you can set up bugzilla's automatic whining
system. This can be done by adding the following command as a system. This can be done by adding the following command as a
...@@ -1869,10 +1870,10 @@ BORDER="0" ...@@ -1869,10 +1870,10 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <B > <B
CLASS="COMMAND" CLASS="command"
>cd >cd
&#60;your-bugzilla-directory&#62; ; &#60;your-bugzilla-directory&#62; ;
./whineatnews.pl</B ./whineatnews.pl</B
...@@ -1887,11 +1888,11 @@ CLASS="COMMAND" ...@@ -1887,11 +1888,11 @@ CLASS="COMMAND"
> >
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1907,7 +1908,7 @@ ALT="Tip"></TD ...@@ -1907,7 +1908,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Depending on your system, crontab may have several manpages. >&#13; Depending on your system, crontab may have several manpages.
The following command should lead you to the most useful The following command should lead you to the most useful
page for this purpose: page for this purpose:
<TABLE <TABLE
...@@ -1919,8 +1920,8 @@ WIDTH="100%" ...@@ -1919,8 +1920,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> man 5 crontab >&#13; man 5 crontab
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -1934,20 +1935,20 @@ CLASS="PROGRAMLISTING" ...@@ -1934,20 +1935,20 @@ CLASS="PROGRAMLISTING"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN827" NAME="AEN827"
>3.2.18. Bug Graphs (Optional)</A >3.2.18. Bug Graphs (Optional)</A
></H2 ></H2
><P ><P
> As long as you installed the GD and Graph::Base Perl modules >&#13; As long as you installed the GD and Graph::Base Perl modules
you might as well turn on the nifty bugzilla bug reporting you might as well turn on the nifty bugzilla bug reporting
graphs. graphs.
</P </P
><P ><P
> Add a cron entry like this to run collectstats daily at 5 >&#13; Add a cron entry like this to run collectstats daily at 5
after midnight: after midnight:
<P <P
></P ></P
...@@ -1956,13 +1957,13 @@ BORDER="0" ...@@ -1956,13 +1957,13 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
>&#13; <TT
CLASS="computeroutput"
> <TT > <TT
CLASS="COMPUTEROUTPUT" CLASS="prompt"
> <TT
CLASS="PROMPT"
>bash#</TT >bash#</TT
> <B > <B
CLASS="COMMAND" CLASS="command"
>crontab >crontab
-e</B -e</B
> </TT > </TT
...@@ -1971,8 +1972,8 @@ CLASS="COMMAND" ...@@ -1971,8 +1972,8 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> 5 0 * * * cd > 5 0 * * * cd
&#60;your-bugzilla-directory&#62; ; ./collectstats.pl &#60;your-bugzilla-directory&#62; ; ./collectstats.pl
</TT </TT
...@@ -1986,26 +1987,26 @@ CLASS="COMPUTEROUTPUT" ...@@ -1986,26 +1987,26 @@ CLASS="COMPUTEROUTPUT"
> >
</P </P
><P ><P
> After two days have passed you'll be able to view bug graphs >&#13; After two days have passed you'll be able to view bug graphs
from the Bug Reports page. from the Bug Reports page.
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="AEN839" NAME="AEN839"
>3.2.19. Securing MySQL</A >3.2.19. Securing MySQL</A
></H2 ></H2
><P ><P
> If you followed the installation instructions for setting up >&#13; If you followed the installation instructions for setting up
your "bugs" and "root" user in MySQL, much of this should not your "bugs" and "root" user in MySQL, much of this should not
apply to you. If you are upgrading an existing installation apply to you. If you are upgrading an existing installation
of Bugzilla, you should pay close attention to this section. of Bugzilla, you should pay close attention to this section.
</P </P
><P ><P
> Most MySQL installs have "interesting" default security parameters: >&#13; Most MySQL installs have "interesting" default security parameters:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -2038,12 +2039,12 @@ BORDER="0" ...@@ -2038,12 +2039,12 @@ BORDER="0"
> >
</P </P
><P ><P
> This means anyone from anywhere on the internet can not only >&#13; This means anyone from anywhere on the internet can not only
drop the database with one SQL command, and they can write as drop the database with one SQL command, and they can write as
root to the system. root to the system.
</P </P
><P ><P
> To see your permissions do: >&#13; To see your permissions do:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -2051,14 +2052,14 @@ BORDER="0" ...@@ -2051,14 +2052,14 @@ BORDER="0"
><TBODY ><TBODY
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>bash#</TT >bash#</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>mysql -u root -p</B >mysql -u root -p</B
> >
</TT </TT
...@@ -2067,14 +2068,14 @@ CLASS="COMMAND" ...@@ -2067,14 +2068,14 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>use mysql;</B >use mysql;</B
> >
</TT </TT
...@@ -2083,14 +2084,14 @@ CLASS="COMMAND" ...@@ -2083,14 +2084,14 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>show tables;</B >show tables;</B
> >
</TT </TT
...@@ -2099,14 +2100,14 @@ CLASS="COMMAND" ...@@ -2099,14 +2100,14 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>select * from user;</B >select * from user;</B
> >
</TT </TT
...@@ -2115,14 +2116,14 @@ CLASS="COMMAND" ...@@ -2115,14 +2116,14 @@ CLASS="COMMAND"
></TR ></TR
><TR ><TR
><TD ><TD
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>select * from db;</B >select * from db;</B
> >
</TT </TT
...@@ -2136,7 +2137,7 @@ CLASS="COMMAND" ...@@ -2136,7 +2137,7 @@ CLASS="COMMAND"
> >
</P </P
><P ><P
> To fix the gaping holes: >&#13; To fix the gaping holes:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -2161,7 +2162,7 @@ BORDER="0" ...@@ -2161,7 +2162,7 @@ BORDER="0"
> >
</P </P
><P ><P
> If you're not running "mit-pthreads" you can use: >&#13; If you're not running "mit-pthreads" you can use:
<P <P
></P ></P
><TABLE ><TABLE
...@@ -2190,7 +2191,7 @@ BORDER="0" ...@@ -2190,7 +2191,7 @@ BORDER="0"
> >
</P </P
><P ><P
> With "mit-pthreads" you'll need to modify the "globals.pl" Mysql-&#62;Connect >&#13; With "mit-pthreads" you'll need to modify the "globals.pl" Mysql-&#62;Connect
line to specify a specific host name instead of "localhost", and accept line to specify a specific host name instead of "localhost", and accept
external connections: external connections:
<P <P
...@@ -2221,55 +2222,55 @@ BORDER="0" ...@@ -2221,55 +2222,55 @@ BORDER="0"
> >
</P </P
><P ><P
> Use .htaccess files with the Apache webserver to secure your >&#13; Use .htaccess files with the Apache webserver to secure your
bugzilla install. See <A bugzilla install. See <A
HREF="geninstall.html#HTACCESS" HREF="geninstall.html#htaccess"
>.htaccess files and security</A >.htaccess files and security</A
> >
</P </P
><P ><P
> Consider also: >&#13; Consider also:
<P <P
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Turning off external networking with "--skip-networking", >&#13; Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't. unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket. Without networking, MySQL connects with a Unix domain socket.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> using the --user= option to mysqld to run it as an unprivileged >&#13; using the --user= option to mysqld to run it as an unprivileged
user. user.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> starting MySQL in a chroot jail >&#13; starting MySQL in a chroot jail
</P </P
></LI ></LI
><LI ><LI
><P ><P
> running the httpd in a "chrooted" jail >&#13; running the httpd in a "chrooted" jail
</P </P
></LI ></LI
><LI ><LI
><P ><P
> making sure the MySQL passwords are different from the OS >&#13; making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root"). passwords (MySQL "root" has nothing to do with system "root").
</P </P
></LI ></LI
><LI ><LI
><P ><P
> running MySQL on a separate untrusted machine >&#13; running MySQL on a separate untrusted machine
</P </P
></LI ></LI
><LI ><LI
><P ><P
> making backups ;-) >&#13; making backups ;-)
</P </P
></LI ></LI
></OL ></OL
......
docs/html/tinderbox.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The Future of Bugzilla" TITLE="The Future of Bugzilla"
HREF="future.html"></HEAD HREF="future.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="future.html" ...@@ -66,11 +66,11 @@ HREF="future.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="TINDERBOX" NAME="tinderbox"
>5.4. Tinderbox/Tinderbox2</A >5.4. Tinderbox/Tinderbox2</A
></H1 ></H1
><P ><P
......
docs/html/translations.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Document Conventions" TITLE="Document Conventions"
HREF="conventions.html"></HEAD HREF="conventions.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,20 +66,20 @@ HREF="conventions.html" ...@@ -66,20 +66,20 @@ HREF="conventions.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="TRANSLATIONS" NAME="translations"
>1.8. Translations</A >1.8. Translations</A
></H1 ></H1
><P ><P
> The Bugzilla Guide needs translators! Please volunteer your >&#13; The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will translation into the language of your choice. If you will
translate this Guide, please notify the members of the translate this Guide, please notify the members of the
mozilla-webtools mailing list at mozilla-webtools mailing list at
<TT <TT
CLASS="EMAIL" CLASS="email"
>&#60;<A >&#60;<A
HREF="mailto:mozilla-webtools@mozilla.org" HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A >mozilla-webtools@mozilla.org</A
......
docs/html/useradmin.html
View file @ d7f38125
...@@ -20,7 +20,7 @@ TITLE="Product, Component, Milestone, and Version ...@@ -20,7 +20,7 @@ TITLE="Product, Component, Milestone, and Version
Administration" Administration"
HREF="programadmin.html"></HEAD HREF="programadmin.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -67,28 +67,28 @@ HREF="programadmin.html" ...@@ -67,28 +67,28 @@ HREF="programadmin.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="USERADMIN" NAME="useradmin"
>4.2. User Administration</A >4.2. User Administration</A
></H1 ></H1
><P ><P
> User administration is one of the easiest parts of Bugzilla. >&#13; User administration is one of the easiest parts of Bugzilla.
Keeping it from getting out of hand, however, can become a Keeping it from getting out of hand, however, can become a
challenge. challenge.
</P </P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="DEFAULTUSER" NAME="defaultuser"
>4.2.1. Creating the Default User</A >4.2.1. Creating the Default User</A
></H2 ></H2
><P ><P
> When you first run checksetup.pl after installing Bugzilla, it >&#13; When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email will prompt you for the administrative username (email
address) and password for this "super user". If for some address) and password for this "super user". If for some
reason you were to delete the "super user" account, re-running reason you were to delete the "super user" account, re-running
...@@ -96,11 +96,11 @@ NAME="DEFAULTUSER" ...@@ -96,11 +96,11 @@ NAME="DEFAULTUSER"
password. password.
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -116,21 +116,21 @@ ALT="Tip"></TD ...@@ -116,21 +116,21 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you wish to add more administrative users, you must use the >&#13; If you wish to add more administrative users, you must use the
MySQL interface. Run "mysql" from the command line, and use MySQL interface. Run "mysql" from the command line, and use
these commands ("mysql&#62;" denotes the mysql prompt, not these commands ("mysql&#62;" denotes the mysql prompt, not
something you should type in): something you should type in):
<B <B
CLASS="COMMAND" CLASS="command"
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> use bugs;</B > use bugs;</B
> >
<B <B
CLASS="COMMAND" CLASS="command"
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> update profiles set > update profiles set
groupset=0x7ffffffffffffff where login_name = "(user's groupset=0x7ffffffffffffff where login_name = "(user's
...@@ -152,19 +152,19 @@ CLASS="QUOTE" ...@@ -152,19 +152,19 @@ CLASS="QUOTE"
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="MANAGEUSERS" NAME="manageusers"
>4.2.2. Managing Other Users</A >4.2.2. Managing Other Users</A
></H2 ></H2
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="LOGIN" NAME="login"
>4.2.2.1. Logging In</A >4.2.2.1. Logging In</A
></H3 ></H3
><P ><P
...@@ -173,23 +173,23 @@ NAME="LOGIN" ...@@ -173,23 +173,23 @@ NAME="LOGIN"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Open the index.html page for your Bugzilla installation >&#13; Open the index.html page for your Bugzilla installation
in your browser window. in your browser window.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Click the "Query Existing Bug Reports" link. >&#13; Click the "Query Existing Bug Reports" link.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Click the "Log In" link at the foot of the page. >&#13; Click the "Log In" link at the foot of the page.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Type your email address, and the password which was >&#13; Type your email address, and the password which was
emailed to you when you created your Bugzilla account, emailed to you when you created your Bugzilla account,
into the spaces provided. into the spaces provided.
</P </P
...@@ -199,15 +199,15 @@ TYPE="1" ...@@ -199,15 +199,15 @@ TYPE="1"
>Congratulations, you are logged in!</P >Congratulations, you are logged in!</P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="CREATENEWUSERS" NAME="createnewusers"
>4.2.2.2. Creating new users</A >4.2.2.2. Creating new users</A
></H3 ></H3
><P ><P
> Your users can create their own user accounts by clicking >&#13; Your users can create their own user accounts by clicking
the "New Account" link at the bottom of each page. However, the "New Account" link at the bottom of each page. However,
should you desire to create user accounts ahead of time, should you desire to create user accounts ahead of time,
here is how you do it. here is how you do it.
...@@ -218,24 +218,24 @@ NAME="CREATENEWUSERS" ...@@ -218,24 +218,24 @@ NAME="CREATENEWUSERS"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> After logging in, click the "Users" link at the footer >&#13; After logging in, click the "Users" link at the footer
of the query page. of the query page.
</P </P
></LI ></LI
><LI ><LI
><P ><P
> To see a specific user, type a portion of their login >&#13; To see a specific user, type a portion of their login
name in the box provided and click "submit". To see all name in the box provided and click "submit". To see all
users, simply click the "submit" button. You must click users, simply click the "submit" button. You must click
"submit" here to be able to add a new user. "submit" here to be able to add a new user.
</P </P
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -250,12 +250,12 @@ ALT="Tip"></TD ...@@ -250,12 +250,12 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> More functionality is available via the list on the >&#13; More functionality is available via the list on the
right-hand side of the text entry box. You can match right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive default) of all users on your system, a case-sensitive
regular expression (please see the <B regular expression (please see the <B
CLASS="COMMAND" CLASS="command"
>man >man
regexp</B regexp</B
> manual page for details on regular > manual page for details on regular
...@@ -272,22 +272,22 @@ CLASS="COMMAND" ...@@ -272,22 +272,22 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> Click the "Add New User" link at the bottom of the user >&#13; Click the "Add New User" link at the bottom of the user
list list
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Fill out the form presented. This page is >&#13; Fill out the form presented. This page is
self-explanatory. When done, click "submit". self-explanatory. When done, click "submit".
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -302,7 +302,7 @@ ALT="Note"></TD ...@@ -302,7 +302,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Adding a user this way will <EM >&#13; Adding a user this way will <EM
>not</EM >not</EM
> >
send an email informing them of their username and send an email informing them of their username and
...@@ -326,15 +326,15 @@ CLASS="QUOTE" ...@@ -326,15 +326,15 @@ CLASS="QUOTE"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="DISABLEUSERS" NAME="disableusers"
>4.2.2.3. Disabling Users</A >4.2.2.3. Disabling Users</A
></H3 ></H3
><P ><P
> I bet you noticed that big "Disabled Text" entry box >&#13; I bet you noticed that big "Disabled Text" entry box
available from the "Add New User" screen, when you edit an available from the "Add New User" screen, when you edit an
account? By entering any text in this box and selecting account? By entering any text in this box and selecting
"submit", you have prevented the user from using Bugzilla "submit", you have prevented the user from using Bugzilla
...@@ -342,11 +342,11 @@ NAME="DISABLEUSERS" ...@@ -342,11 +342,11 @@ NAME="DISABLEUSERS"
text box, will be presented to the user the next time she text box, will be presented to the user the next time she
attempts to use the system. attempts to use the system.
<DIV <DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -362,7 +362,7 @@ ALT="Warning"></TD ...@@ -362,7 +362,7 @@ ALT="Warning"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Don't disable your own administrative account, or you >&#13; Don't disable your own administrative account, or you
will hate life! will hate life!
</P </P
><P ><P
...@@ -382,15 +382,15 @@ CLASS="QUOTE" ...@@ -382,15 +382,15 @@ CLASS="QUOTE"
</P </P
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H3 ><H3
CLASS="SECTION" CLASS="section"
><A ><A
NAME="MODIFYUSERS" NAME="modifyusers"
>4.2.2.4. Modifying Users</A >4.2.2.4. Modifying Users</A
></H3 ></H3
><P ><P
> Here I will attempt to describe the function of each option >&#13; Here I will attempt to describe the function of each option
on the Edit User screen. on the Edit User screen.
</P </P
><P ><P
...@@ -398,19 +398,19 @@ NAME="MODIFYUSERS" ...@@ -398,19 +398,19 @@ NAME="MODIFYUSERS"
><UL ><UL
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Login Name</EM >Login Name</EM
>: This is generally the >: This is generally the
user's email address. However, if you have edited your user's email address. However, if you have edited your
system parameters, this may just be the user's login system parameters, this may just be the user's login
name or some other identifier. name or some other identifier.
<DIV <DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -425,7 +425,7 @@ ALT="Tip"></TD ...@@ -425,7 +425,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> For compatability reasons, you should probably stick >&#13; For compatability reasons, you should probably stick
with email addresses as user login names. It will with email addresses as user login names. It will
make your life easier. make your life easier.
</P </P
...@@ -438,14 +438,14 @@ VALIGN="TOP" ...@@ -438,14 +438,14 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Real Name</EM >Real Name</EM
>: Duh! >: Duh!
</P </P
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Password</EM >Password</EM
>: You can change the user >: You can change the user
password here. It is normal to only see asterisks. password here. It is normal to only see asterisks.
...@@ -453,7 +453,7 @@ VALIGN="TOP" ...@@ -453,7 +453,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Email Notification</EM >Email Notification</EM
>: You may choose >: You may choose
from one of three options: from one of three options:
...@@ -463,7 +463,7 @@ VALIGN="TOP" ...@@ -463,7 +463,7 @@ VALIGN="TOP"
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> All qualifying bugs except those which I change: >&#13; All qualifying bugs except those which I change:
The user will be notified of any change to any bug The user will be notified of any change to any bug
for which she is the reporter, assignee, QA for which she is the reporter, assignee, QA
Contact, CC recipient, or "watcher". Contact, CC recipient, or "watcher".
...@@ -471,18 +471,18 @@ TYPE="1" ...@@ -471,18 +471,18 @@ TYPE="1"
></LI ></LI
><LI ><LI
><P ><P
> Only those bugs which I am listed on the CC line: >&#13; Only those bugs which I am listed on the CC line:
The user will not be notified of changes to bugs The user will not be notified of changes to bugs
where she is the assignee, reporter, or QA where she is the assignee, reporter, or QA
Contact, but will receive them if she is on the CC Contact, but will receive them if she is on the CC
list. list.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -497,7 +497,7 @@ ALT="Note"></TD ...@@ -497,7 +497,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> She will still receive whining cron emails if >&#13; She will still receive whining cron emails if
you set up the "whinemail" feature. you set up the "whinemail" feature.
</P </P
></TD ></TD
...@@ -509,7 +509,7 @@ VALIGN="TOP" ...@@ -509,7 +509,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>All Qualifying Bugs</EM >All Qualifying Bugs</EM
>: This >: This
user is a glutton for punishment. If her name is user is a glutton for punishment. If her name is
...@@ -519,9 +519,10 @@ VALIGN="TOP" ...@@ -519,9 +519,10 @@ VALIGN="TOP"
</P </P
></LI ></LI
></OL ></OL
></P >
</P
><P ><P
> <EM >&#13; <EM
>Disable Text</EM >Disable Text</EM
>: If you type anything >: If you type anything
in this box, including just a space, the user account is in this box, including just a space, the user account is
...@@ -529,12 +530,12 @@ VALIGN="TOP" ...@@ -529,12 +530,12 @@ VALIGN="TOP"
interface, and what you type in this box is presented as interface, and what you type in this box is presented as
the reason. the reason.
<DIV <DIV
CLASS="WARNING" CLASS="warning"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="WARNING" CLASS="warning"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -556,12 +557,12 @@ VALIGN="TOP" ...@@ -556,12 +557,12 @@ VALIGN="TOP"
></DIV ></DIV
> >
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -576,7 +577,7 @@ ALT="Note"></TD ...@@ -576,7 +577,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> As of this writing, the user can still submit bugs >&#13; As of this writing, the user can still submit bugs
via the e-mail gateway, if you set it up, despite via the e-mail gateway, if you set it up, despite
the disabled text field. The e-mail gateway should the disabled text field. The e-mail gateway should
<EM <EM
...@@ -593,7 +594,7 @@ VALIGN="TOP" ...@@ -593,7 +594,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>CanConfirm</EM >CanConfirm</EM
>: This field is only used >: This field is only used
if you have enabled "unconfirmed" status in your if you have enabled "unconfirmed" status in your
...@@ -606,7 +607,7 @@ VALIGN="TOP" ...@@ -606,7 +607,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Creategroups</EM >Creategroups</EM
>: This option will >: This option will
allow a user to create and destroy groups in Bugzilla. allow a user to create and destroy groups in Bugzilla.
...@@ -617,18 +618,18 @@ VALIGN="TOP" ...@@ -617,18 +618,18 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Editbugs</EM >Editbugs</EM
>: Unless a user has this >: Unless a user has this
bit set, they can only edit those bugs for which they bit set, they can only edit those bugs for which they
are the assignee or the reporter. are the assignee or the reporter.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="90%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
><TD ><TD
...@@ -643,7 +644,7 @@ ALT="Note"></TD ...@@ -643,7 +644,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Leaving this option unchecked does not prevent users >&#13; Leaving this option unchecked does not prevent users
from adding comments to a bug! They simply cannot from adding comments to a bug! They simply cannot
change a bug priority, severity, etc. unless they change a bug priority, severity, etc. unless they
are the assignee or reporter. are the assignee or reporter.
...@@ -657,7 +658,7 @@ VALIGN="TOP" ...@@ -657,7 +658,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Editcomponents</EM >Editcomponents</EM
>: This flag allows a >: This flag allows a
user to create new products and components, as well as user to create new products and components, as well as
...@@ -673,7 +674,7 @@ VALIGN="TOP" ...@@ -673,7 +674,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Editkeywords</EM >Editkeywords</EM
>: If you use Bugzilla's >: If you use Bugzilla's
keyword functionality, enabling this feature allows a keyword functionality, enabling this feature allows a
...@@ -690,7 +691,7 @@ VALIGN="TOP" ...@@ -690,7 +691,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>Editusers</EM >Editusers</EM
>: This flag allows a user >: This flag allows a user
do what you're doing right now: edit other users. This do what you're doing right now: edit other users. This
...@@ -701,7 +702,7 @@ VALIGN="TOP" ...@@ -701,7 +702,7 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><P ><P
> <EM >&#13; <EM
>PRODUCT</EM >PRODUCT</EM
>: PRODUCT bugs access. This >: PRODUCT bugs access. This
allows an administrator, with product-level granularity, allows an administrator, with product-level granularity,
......
docs/html/using.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="What is Bugzilla?" TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD HREF="whatis.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="whatis.html" ...@@ -63,10 +63,10 @@ HREF="whatis.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="USING" NAME="using"
>Chapter 2. Using Bugzilla</A >Chapter 2. Using Bugzilla</A
></H1 ></H1
><TABLE ><TABLE
...@@ -118,29 +118,29 @@ HREF="how.html" ...@@ -118,29 +118,29 @@ HREF="how.html"
><DL ><DL
><DT ><DT
>2.3.1. <A >2.3.1. <A
HREF="how.html#MYACCOUNT" HREF="how.html#myaccount"
>Create a Bugzilla Account</A >Create a Bugzilla Account</A
></DT ></DT
><DT ><DT
>2.3.2. <A >2.3.2. <A
HREF="how.html#QUERY" HREF="how.html#query"
>The Bugzilla Query Page</A >The Bugzilla Query Page</A
></DT ></DT
><DT ><DT
>2.3.3. <A >2.3.3. <A
HREF="how.html#BUGREPORTS" HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A >Creating and Managing Bug Reports</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>2.3.3.1. <A >2.3.3.1. <A
HREF="how.html#BUG_WRITING" HREF="how.html#bug-writing"
>Writing a Great Bug Report</A >Writing a Great Bug Report</A
></DT ></DT
><DT ><DT
>2.3.3.2. <A >2.3.3.2. <A
HREF="how.html#BUG_MANAGE" HREF="how.html#bug-manage"
>Managing your Bug Reports</A >Managing your Bug Reports</A
></DT ></DT
></DL ></DL
...@@ -156,41 +156,41 @@ HREF="init4me.html" ...@@ -156,41 +156,41 @@ HREF="init4me.html"
><DL ><DL
><DT ><DT
>2.4.1. <A >2.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS" HREF="init4me.html#accountsettings"
>Account Settings</A >Account Settings</A
></DT ></DT
><DT ><DT
>2.4.2. <A >2.4.2. <A
HREF="init4me.html#EMAILSETTINGS" HREF="init4me.html#emailsettings"
>Email Settings</A >Email Settings</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>2.4.2.1. <A >2.4.2.1. <A
HREF="init4me.html#NOTIFICATION" HREF="init4me.html#notification"
>Email Notification</A >Email Notification</A
></DT ></DT
><DT ><DT
>2.4.2.2. <A >2.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH" HREF="init4me.html#newemailtech"
>New Email Technology</A >New Email Technology</A
></DT ></DT
><DT ><DT
>2.4.2.3. <A >2.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS" HREF="init4me.html#watchsettings"
>"Watching" Users</A >"Watching" Users</A
></DT ></DT
></DL ></DL
></DD ></DD
><DT ><DT
>2.4.3. <A >2.4.3. <A
HREF="init4me.html#FOOTERSETTINGS" HREF="init4me.html#footersettings"
>Page Footer</A >Page Footer</A
></DT ></DT
><DT ><DT
>2.4.4. <A >2.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS" HREF="init4me.html#permissionsettings"
>Permissions</A >Permissions</A
></DT ></DT
></DL ></DL
......
docs/html/usingbz-conc.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Installation" TITLE="Installation"
HREF="installation.html"></HEAD HREF="installation.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="installation.html" ...@@ -66,15 +66,15 @@ HREF="installation.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="USINGBZ-CONC" NAME="usingbz-conc"
>2.5. Using Bugzilla-Conclusion</A >2.5. Using Bugzilla-Conclusion</A
></H1 ></H1
><P ><P
> Thank you for reading through this portion of the Bugzilla >&#13; Thank you for reading through this portion of the Bugzilla
Guide. I anticipate it may not yet meet the needs of all Guide. I anticipate it may not yet meet the needs of all
readers. If you have additional comments or corrections to readers. If you have additional comments or corrections to
make, please submit your contributions to the <A make, please submit your contributions to the <A
......
docs/html/variant-fenris.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>Loki Bugzilla (Fenris)</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
REL="NEXT"
TITLE="Issuezilla"
HREF="variant-issuezilla.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-issuezilla.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-fenris"
>7.2. Loki Bugzilla (Fenris)</A
></H1
><P
>Fenris can be found at <A
HREF="http://fenris.lokigames.com/"
TARGET="_top"
>http://fenris.lokigames.com</A
>. It is a fork from Bugzilla.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-issuezilla.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Red Hat Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Issuezilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/variant-issuezilla.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>Issuezilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Loki Bugzilla (Fenris)"
HREF="variant-fenris.html"><LINK
REL="NEXT"
TITLE="Scarab"
HREF="variant-scarab.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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-fenris.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-scarab.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-issuezilla"
>7.3. Issuezilla</A
></H1
><P
>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <A
HREF="variant-scarab.html"
>Scarab, a newfangled Java-based issue tracker</A
>, is under heavy development
and looks promising!</P
><P
>URL: <A
HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
TARGET="_top"
>http://issuezilla.tigris.org/servlets/ProjectHome</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-fenris.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-scarab.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Loki Bugzilla (Fenris)</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Scarab</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/variant-perforce.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Scarab"
HREF="variant-scarab.html"><LINK
REL="NEXT"
TITLE="SourceForge"
HREF="variant-sourceforge.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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-scarab.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-sourceforge.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-perforce"
>7.5. Perforce SCM</A
></H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
CLASS="QUOTE"
>"jobs"</SPAN
> functionality.</P
><P
><A
HREF="http://www.perforce.com/perforce/technotes/note052.html"
TARGET="_top"
>http://www.perforce.com/perforce/technotes/note052.html</A
>http://www.perforce.com/perforce/technotes/note052.html</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-scarab.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-sourceforge.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Scarab</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>SourceForge</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/variant-scarab.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>Scarab</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Issuezilla"
HREF="variant-issuezilla.html"><LINK
REL="NEXT"
TITLE="Perforce SCM"
HREF="variant-perforce.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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-issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-perforce.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-scarab"
>7.4. Scarab</A
></H1
><P
>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</P
><P
>URL: <A
HREF="http://scarab.tigris.org/"
TARGET="_top"
>http://scarab.tigris.org</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-perforce.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Issuezilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Perforce SCM</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/variant-sourceforge.html 0 → 100644
View file @ d7f38125
<HTML
><HEAD
><TITLE
>SourceForge</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant-perforce.html"><LINK
REL="NEXT"
TITLE="The Bugzilla FAQ"
HREF="faq.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><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-perforce.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-sourceforge"
>7.6. SourceForge</A
></H1
><P
>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</P
><P
>URL: <A
HREF="http://www.sourceforge.net"
TARGET="_top"
>http://www.sourceforge.net</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-perforce.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Perforce SCM</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla FAQ</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/variants.html
View file @ d7f38125
...@@ -16,7 +16,7 @@ REL="NEXT" ...@@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Red Hat Bugzilla" TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD HREF="rhbugzilla.html"></HEAD
><BODY ><BODY
CLASS="CHAPTER" CLASS="chapter"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -63,10 +63,10 @@ HREF="rhbugzilla.html" ...@@ -63,10 +63,10 @@ HREF="rhbugzilla.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="CHAPTER" CLASS="chapter"
><H1 ><H1
><A ><A
NAME="VARIANTS" NAME="variants"
>Chapter 7. Bugzilla Variants and Competitors</A >Chapter 7. Bugzilla Variants and Competitors</A
></H1 ></H1
><DIV ><DIV
...@@ -83,27 +83,27 @@ HREF="rhbugzilla.html" ...@@ -83,27 +83,27 @@ HREF="rhbugzilla.html"
></DT ></DT
><DT ><DT
>7.2. <A >7.2. <A
HREF="variant_fenris.html" HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A >Loki Bugzilla (Fenris)</A
></DT ></DT
><DT ><DT
>7.3. <A >7.3. <A
HREF="variant_issuezilla.html" HREF="variant-issuezilla.html"
>Issuezilla</A >Issuezilla</A
></DT ></DT
><DT ><DT
>7.4. <A >7.4. <A
HREF="variant_scarab.html" HREF="variant-scarab.html"
>Scarab</A >Scarab</A
></DT ></DT
><DT ><DT
>7.5. <A >7.5. <A
HREF="variant_perforce.html" HREF="variant-perforce.html"
>Perforce SCM</A >Perforce SCM</A
></DT ></DT
><DT ><DT
>7.6. <A >7.6. <A
HREF="variant_sourceforge.html" HREF="variant-sourceforge.html"
>SourceForge</A >SourceForge</A
></DT ></DT
></DL ></DL
......
docs/html/whatis.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Why Should We Use Bugzilla?" TITLE="Why Should We Use Bugzilla?"
HREF="why.html"></HEAD HREF="why.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,15 +66,15 @@ HREF="why.html" ...@@ -66,15 +66,15 @@ HREF="why.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="WHATIS" NAME="whatis"
>2.1. What is Bugzilla?</A >2.1. What is Bugzilla?</A
></H1 ></H1
><P ><P
> Bugzilla is one example of a class of programs called "Defect >&#13; Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was track of outstanding bugs in their product effectively. Bugzilla was
...@@ -89,48 +89,48 @@ project, Mozilla). It is now the de-facto standard defect-tracking ...@@ -89,48 +89,48 @@ project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured. system against which all others are measured.
</P </P
><P ><P
> Bugzilla has matured immensely, and now boasts many advanced features. These include: >&#13; Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P <P
></P ></P
><UL ><UL
><LI ><LI
><P ><P
> integrated, product-based granular security schema >&#13; integrated, product-based granular security schema
</P </P
></LI ></LI
><LI ><LI
><P ><P
> inter-bug dependencies and dependency graphing >&#13; inter-bug dependencies and dependency graphing
</P </P
></LI ></LI
><LI ><LI
><P ><P
> advanced reporting capabilities >&#13; advanced reporting capabilities
</P </P
></LI ></LI
><LI ><LI
><P ><P
> a robust, stable RDBMS back-end >&#13; a robust, stable RDBMS back-end
</P </P
></LI ></LI
><LI ><LI
><P ><P
> extensive configurability >&#13; extensive configurability
</P </P
></LI ></LI
><LI ><LI
><P ><P
> a very well-understood and well-thought-out natural bug resolution protocol >&#13; a very well-understood and well-thought-out natural bug resolution protocol
</P </P
></LI ></LI
><LI ><LI
><P ><P
> email, XML, console, and HTTP APIs >&#13; email, XML, console, and HTTP APIs
</P </P
></LI ></LI
><LI ><LI
><P ><P
> available integration with automated software >&#13; available integration with automated software
configuration management systems, including Perforce and configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and CVS (through the Bugzilla email interface and
checkin/checkout scripts) checkin/checkout scripts)
...@@ -138,14 +138,14 @@ system against which all others are measured. ...@@ -138,14 +138,14 @@ system against which all others are measured.
></LI ></LI
><LI ><LI
><P ><P
> too many more features to list >&#13; too many more features to list
</P </P
></LI ></LI
></UL ></UL
> >
</P </P
><P ><P
> Despite its current robustness and popularity, Bugzilla faces >&#13; Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but program logic, verbose email bug notifications, a powerful but
...@@ -156,7 +156,7 @@ system against which all others are measured. ...@@ -156,7 +156,7 @@ system against which all others are measured.
some nonstandard libraries. some nonstandard libraries.
</P </P
><P ><P
> Some recent headway has been made on the query front, however. >&#13; Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see If you are using the latest version of Bugzilla, you should see
a <SPAN a <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -167,7 +167,7 @@ CLASS="QUOTE" ...@@ -167,7 +167,7 @@ CLASS="QUOTE"
available as "queryhelp.cgi". available as "queryhelp.cgi".
</P </P
><P ><P
> Despite these small problems, Bugzilla is very hard to beat. It >&#13; Despite these small problems, Bugzilla is very hard to beat. It
is under <EM is under <EM
>very</EM >very</EM
> active development to address > active development to address
......
docs/html/why.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="How do I use Bugzilla?" TITLE="How do I use Bugzilla?"
HREF="how.html"></HEAD HREF="how.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="how.html" ...@@ -66,11 +66,11 @@ HREF="how.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="WHY" NAME="why"
>2.2. Why Should We Use Bugzilla?</A >2.2. Why Should We Use Bugzilla?</A
></H1 ></H1
><TABLE ><TABLE
...@@ -97,7 +97,7 @@ VALIGN="TOP" ...@@ -97,7 +97,7 @@ VALIGN="TOP"
></TR ></TR
></TABLE ></TABLE
><P ><P
> For many years, defect-tracking software has remained >&#13; For many years, defect-tracking software has remained
principally the domain of large software development houses. principally the domain of large software development houses.
Even then, most shops never bothered with bug-tracking software, Even then, most shops never bothered with bug-tracking software,
and instead simply relied on shared lists and email to monitor and instead simply relied on shared lists and email to monitor
...@@ -106,7 +106,7 @@ VALIGN="TOP" ...@@ -106,7 +106,7 @@ VALIGN="TOP"
dropped or ignored. dropped or ignored.
</P </P
><P ><P
> These days, many companies are finding that integrated >&#13; These days, many companies are finding that integrated
defect-tracking systems reduce downtime, increase productivity, defect-tracking systems reduce downtime, increase productivity,
and raise customer satisfaction with their systems. Along with and raise customer satisfaction with their systems. Along with
full disclosure, an open bug-tracker allows manufacturers to full disclosure, an open bug-tracker allows manufacturers to
...@@ -118,12 +118,12 @@ VALIGN="TOP" ...@@ -118,12 +118,12 @@ VALIGN="TOP"
system for accounting for unusual system or software issues. system for accounting for unusual system or software issues.
</P </P
><P ><P
> But why should <EM >&#13; But why should <EM
>you</EM >you</EM
> use Bugzilla? > use Bugzilla?
</P </P
><P ><P
> Bugzilla is very adaptable to various situations. Known uses >&#13; Bugzilla is very adaptable to various situations. Known uses
currently include IT support queues, Systems Administration currently include IT support queues, Systems Administration
deployment management, chip design and development problem deployment management, chip design and development problem
tracking (both pre-and-post fabrication), and software and tracking (both pre-and-post fabrication), and software and
...@@ -134,7 +134,7 @@ VALIGN="TOP" ...@@ -134,7 +134,7 @@ VALIGN="TOP"
replication problems replication problems
</P </P
><P ><P
> Bugzilla can dramatically increase the productivity and >&#13; Bugzilla can dramatically increase the productivity and
accountability of individual employees by providing a documented accountability of individual employees by providing a documented
workflow and positive feedback for good performance. How many workflow and positive feedback for good performance. How many
times do you wake up in the morning, remembering that you were times do you wake up in the morning, remembering that you were
...@@ -148,7 +148,7 @@ VALIGN="TOP" ...@@ -148,7 +148,7 @@ VALIGN="TOP"
led to critical decisions. led to critical decisions.
</P </P
><P ><P
> Ultimately, Bugzilla puts the power in your hands to improve >&#13; Ultimately, Bugzilla puts the power in your hands to improve
your value to your employer or business while providing a usable your value to your employer or business while providing a usable
framework for your natural attention to detail and knowledge framework for your natural attention to detail and knowledge
store to flourish. store to flourish.
......
docs/html/win32.html
View file @ d7f38125
...@@ -19,7 +19,7 @@ REL="NEXT" ...@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Administering Bugzilla" TITLE="Administering Bugzilla"
HREF="administration.html"></HEAD HREF="administration.html"></HEAD
><BODY ><BODY
CLASS="SECTION" CLASS="section"
BGCOLOR="#FFFFFF" BGCOLOR="#FFFFFF"
TEXT="#000000" TEXT="#000000"
LINK="#0000FF" LINK="#0000FF"
...@@ -66,11 +66,11 @@ HREF="administration.html" ...@@ -66,11 +66,11 @@ HREF="administration.html"
ALIGN="LEFT" ALIGN="LEFT"
WIDTH="100%"></DIV WIDTH="100%"></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H1 ><H1
CLASS="SECTION" CLASS="section"
><A ><A
NAME="WIN32" NAME="win32"
>3.6. Win32 Installation Notes</A >3.6. Win32 Installation Notes</A
></H1 ></H1
><P ><P
...@@ -94,19 +94,19 @@ NAME="WIN32" ...@@ -94,19 +94,19 @@ NAME="WIN32"
any influence in the platform choice for running this system, any influence in the platform choice for running this system,
please choose GNU/Linux instead of Microsoft Windows.</P please choose GNU/Linux instead of Microsoft Windows.</P
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="WININSTALL" NAME="wininstall"
>3.6.1. Win32 Installation: Step-by-step</A >3.6.1. Win32 Installation: Step-by-step</A
></H2 ></H2
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -122,7 +122,7 @@ ALT="Note"></TD ...@@ -122,7 +122,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You should be familiar with, and cross-reference, the rest >&#13; You should be familiar with, and cross-reference, the rest
of the of the
<A <A
HREF="installation.html" HREF="installation.html"
...@@ -152,12 +152,12 @@ HREF="faq.html" ...@@ -152,12 +152,12 @@ HREF="faq.html"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="PROCEDURE" CLASS="procedure"
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Install <A >&#13; Install <A
HREF="http://www.apache.org/" HREF="http://www.apache.org/"
TARGET="_top" TARGET="_top"
>Apache Web >Apache Web
...@@ -179,11 +179,11 @@ CLASS="QUOTE" ...@@ -179,11 +179,11 @@ CLASS="QUOTE"
>. >.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -199,7 +199,7 @@ ALT="Note"></TD ...@@ -199,7 +199,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You may also use Internet Information Server or Personal >&#13; You may also use Internet Information Server or Personal
Web Server for this purpose. However, setup is quite Web Server for this purpose. However, setup is quite
different. If ActivePerl doesn't seem to handle your different. If ActivePerl doesn't seem to handle your
file associations correctly (for .cgi and .pl files), file associations correctly (for .cgi and .pl files),
...@@ -209,7 +209,7 @@ HREF="faq.html" ...@@ -209,7 +209,7 @@ HREF="faq.html"
>. >.
</P </P
><P ><P
> If you are going to use IIS, if on Windows NT you must >&#13; If you are going to use IIS, if on Windows NT you must
be updated to at least Service Pack 4. Windows 2000 be updated to at least Service Pack 4. Windows 2000
ships with a sufficient version of IIS. ships with a sufficient version of IIS.
</P </P
...@@ -220,7 +220,7 @@ HREF="faq.html" ...@@ -220,7 +220,7 @@ HREF="faq.html"
></LI ></LI
><LI ><LI
><P ><P
> Install <A >&#13; Install <A
HREF="http://www.activestate.com/" HREF="http://www.activestate.com/"
TARGET="_top" TARGET="_top"
>ActivePerl</A >ActivePerl</A
...@@ -231,33 +231,33 @@ TARGET="_top" ...@@ -231,33 +231,33 @@ TARGET="_top"
> for a current compiled binary. > for a current compiled binary.
</P </P
><P ><P
> Please also check the following links to fully understand the status >&#13; Please also check the following links to fully understand the status
of ActivePerl on Win32: of ActivePerl on Win32:
<A <A
HREF="http://language.perl.com/newdocs/pod/perlport.html" HREF="http://language.perl.com/newdocs/pod/perlport.html"
TARGET="_top" TARGET="_top"
> Perl Porting</A >&#13; Perl Porting</A
>, and >, and
<A <A
HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html" HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
TARGET="_top" TARGET="_top"
> Perl on Win32 FAQ</A >&#13; Perl on Win32 FAQ</A
> >
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Use ppm from your perl\bin directory to install the following packs: DBI, >&#13; Use ppm from your perl\bin directory to install the following packs: DBI,
DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
to extract them from .zip format using Winzip or other unzip program first. to extract them from .zip format using Winzip or other unzip program first.
These additional ppm modules can be downloaded from ActiveState. These additional ppm modules can be downloaded from ActiveState.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -273,11 +273,11 @@ ALT="Note"></TD ...@@ -273,11 +273,11 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You can find a list of modules at >&#13; You can find a list of modules at
<A <A
HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only" HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
TARGET="_top" TARGET="_top"
> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A >&#13; http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
> >
</P </P
></TD ></TD
...@@ -285,23 +285,23 @@ TARGET="_top" ...@@ -285,23 +285,23 @@ TARGET="_top"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> The syntax for ppm is: >&#13; The syntax for ppm is:
<TT <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>C:&#62; </TT >C:&#62; </TT
><B ><B
CLASS="COMMAND" CLASS="command"
>ppm &#60;modulename&#62;</B >ppm &#60;modulename&#62;</B
> >
</TT </TT
> >
</P </P
><DIV ><DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1038" NAME="AEN1048"
></A ></A
><P ><P
><B ><B
...@@ -309,13 +309,13 @@ NAME="AEN1038" ...@@ -309,13 +309,13 @@ NAME="AEN1038"
></P ></P
><P ><P
><TT ><TT
CLASS="PROMPT" CLASS="prompt"
>C:&#62;</TT >C:&#62;</TT
><B ><B
CLASS="COMMAND" CLASS="command"
>ppm >ppm
<TT <TT
CLASS="OPTION" CLASS="option"
>DBD-Mysql</TT >DBD-Mysql</TT
></B ></B
></P ></P
...@@ -323,23 +323,23 @@ CLASS="OPTION" ...@@ -323,23 +323,23 @@ CLASS="OPTION"
>Watch your capitalization!</P >Watch your capitalization!</P
></DIV ></DIV
><P ><P
> You can find ActiveState ppm modules at >&#13; You can find ActiveState ppm modules at
<A <A
HREF="http://www.activestate.com/PPMPackages/5.6plus/" HREF="http://www.activestate.com/PPMPackages/5.6plus/"
TARGET="_top" TARGET="_top"
> http://www.activestate.com/PPMPackages/5.6plus</A >&#13; http://www.activestate.com/PPMPackages/5.6plus</A
> >
</P </P
></LI ></LI
><LI ><LI
><P ><P
> Install MySQL for NT. >&#13; Install MySQL for NT.
<DIV <DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -355,7 +355,7 @@ ALT="Note"></TD ...@@ -355,7 +355,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> You can download MySQL for Windows NT from <A >&#13; You can download MySQL for Windows NT from <A
HREF="http://www.mysql.com/" HREF="http://www.mysql.com/"
TARGET="_top" TARGET="_top"
>MySQL.com</A >MySQL.com</A
...@@ -370,21 +370,21 @@ TARGET="_top" ...@@ -370,21 +370,21 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Setup MySQL >&#13; Setup MySQL
</P </P
><OL ><OL
CLASS="SUBSTEPS" CLASS="SUBSTEPS"
TYPE="a" TYPE="a"
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>C:&#62; </TT >C:&#62; </TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>C:\mysql\bin\mysql -u root mysql</B >C:\mysql\bin\mysql -u root mysql</B
> >
</TT </TT
...@@ -393,14 +393,14 @@ CLASS="COMMAND" ...@@ -393,14 +393,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>DELETE FROM user WHERE Host='localhost' AND User='';</B >DELETE FROM user WHERE Host='localhost' AND User='';</B
> >
</TT </TT
...@@ -409,14 +409,14 @@ CLASS="COMMAND" ...@@ -409,14 +409,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>UPDATE user SET Password=PASSWORD ('new_password') >UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';</B WHERE user='root';</B
> >
...@@ -436,17 +436,17 @@ CLASS="QUOTE" ...@@ -436,17 +436,17 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><A ><A
NAME="NTBUGS-PASSWORD" NAME="ntbugs-password"
></A ></A
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>GRANT SELECT, INSERT, UPDATE, DELETE, >GRANT SELECT, INSERT, UPDATE, DELETE,
INDEX, ALTER, CREATE, DROP, REFERENCES INDEX, ALTER, CREATE, DROP, REFERENCES
ON bugs.* to bugs@localhost ON bugs.* to bugs@localhost
...@@ -468,14 +468,14 @@ CLASS="QUOTE" ...@@ -468,14 +468,14 @@ CLASS="QUOTE"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>FLUSH PRIVILEGES;</B >FLUSH PRIVILEGES;</B
> >
</TT </TT
...@@ -484,14 +484,14 @@ CLASS="COMMAND" ...@@ -484,14 +484,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>create database bugs;</B >create database bugs;</B
> >
</TT </TT
...@@ -500,14 +500,14 @@ CLASS="COMMAND" ...@@ -500,14 +500,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>mysql&#62;</TT >mysql&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>exit;</B >exit;</B
> >
</TT </TT
...@@ -516,14 +516,14 @@ CLASS="COMMAND" ...@@ -516,14 +516,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> <TT >&#13; <TT
CLASS="COMPUTEROUTPUT" CLASS="computeroutput"
> <TT >&#13; <TT
CLASS="PROMPT" CLASS="prompt"
>C:&#62;</TT >C:&#62;</TT
> >
<B <B
CLASS="COMMAND" CLASS="command"
>C:\mysql\bin\mysqladmin -u root -p reload</B >C:\mysql\bin\mysqladmin -u root -p reload</B
> >
</TT </TT
...@@ -534,14 +534,14 @@ CLASS="COMMAND" ...@@ -534,14 +534,14 @@ CLASS="COMMAND"
></LI ></LI
><LI ><LI
><P ><P
> Edit <TT >&#13; Edit <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
> in your Bugzilla directory. Change > in your Bugzilla directory. Change
this line: this line:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -550,8 +550,8 @@ WIDTH="100%" ...@@ -550,8 +550,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>my $webservergid = getgrnam($my_webservergroup); >&#13;my $webservergid = getgrnam($my_webservergroup);
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -560,10 +560,10 @@ CLASS="PROGRAMLISTING" ...@@ -560,10 +560,10 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><P ><P
> to >&#13; to
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -572,8 +572,8 @@ WIDTH="100%" ...@@ -572,8 +572,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>my $webservergid = $my_webservergroup; >&#13;my $webservergid = $my_webservergroup;
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -590,8 +590,8 @@ WIDTH="100%" ...@@ -590,8 +590,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>my $webservergid = 'Administrators' >&#13;my $webservergid = 'Administrators'
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -602,8 +602,8 @@ CLASS="PROGRAMLISTING" ...@@ -602,8 +602,8 @@ CLASS="PROGRAMLISTING"
></LI ></LI
><LI ><LI
><P ><P
> Run <TT >&#13; Run <TT
CLASS="FILENAME" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
> from the Bugzilla directory. > from the Bugzilla directory.
</P </P
...@@ -611,32 +611,32 @@ CLASS="FILENAME" ...@@ -611,32 +611,32 @@ CLASS="FILENAME"
><LI ><LI
><P ><P
>Edit <TT >Edit <TT
CLASS="FILENAME" CLASS="filename"
>localconfig</TT >localconfig</TT
> to suit your > to suit your
requirements. Set <TT requirements. Set <TT
CLASS="VARNAME" CLASS="varname"
>$db_pass</TT >$db_pass</TT
> to your > to your
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"bugs_password"</SPAN >"bugs_password"</SPAN
> from <A > from <A
HREF="win32.html#NTBUGS-PASSWORD" HREF="win32.html#ntbugs-password"
>step 5.d</A >step 5.d</A
>, and <TT >, and <TT
CLASS="VARNAME" CLASS="varname"
>$webservergroup</TT >$webservergroup</TT
> to <SPAN > to <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"8"</SPAN >"8"</SPAN
>.</P >.</P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -657,7 +657,7 @@ CLASS="QUOTE" ...@@ -657,7 +657,7 @@ CLASS="QUOTE"
>"8"</SPAN >"8"</SPAN
> for > for
<TT <TT
CLASS="VARNAME" CLASS="varname"
>$webservergroup</TT >$webservergroup</TT
> above. If it's > above. If it's
wrong, please send corrections.</P wrong, please send corrections.</P
...@@ -668,27 +668,27 @@ CLASS="VARNAME" ...@@ -668,27 +668,27 @@ CLASS="VARNAME"
></LI ></LI
><LI ><LI
><P ><P
> Edit <TT >&#13; Edit <TT
CLASS="FILENAME" CLASS="filename"
>defparams.pl</TT >defparams.pl</TT
> to suit your > to suit your
requirements. Particularly, set requirements. Particularly, set
<TT <TT
CLASS="VARNAME" CLASS="varname"
>DefParam("maintainer")</TT >DefParam("maintainer")</TT
> and > and
<TT <TT
CLASS="VARNAME" CLASS="varname"
>DefParam("urlbase") to match your >DefParam("urlbase") to match your
install.</TT install.</TT
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -715,11 +715,11 @@ VALIGN="TOP" ...@@ -715,11 +715,11 @@ VALIGN="TOP"
></LI ></LI
><LI ><LI
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -735,7 +735,7 @@ ALT="Note"></TD ...@@ -735,7 +735,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> There are several alternatives to Sendmail that will work on Win32. >&#13; There are several alternatives to Sendmail that will work on Win32.
The one mentioned here is a <EM The one mentioned here is a <EM
>suggestion</EM >suggestion</EM
>, not >, not
...@@ -764,12 +764,12 @@ TARGET="_top" ...@@ -764,12 +764,12 @@ TARGET="_top"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="PROCEDURE" CLASS="procedure"
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><P
> Download NTsendmail, available from<A >&#13; Download NTsendmail, available from<A
HREF="http://www.ntsendmail.com/" HREF="http://www.ntsendmail.com/"
TARGET="_top" TARGET="_top"
> www.ntsendmail.com</A > www.ntsendmail.com</A
...@@ -792,8 +792,8 @@ WIDTH="100%" ...@@ -792,8 +792,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
># these settings configure the NTsendmail process >&#13;# these settings configure the NTsendmail process
use NTsendmail; use NTsendmail;
$ENV{"NTsendmail"}="your.smtpserver.box"; $ENV{"NTsendmail"}="your.smtpserver.box";
$ENV{"NTsendmail_debug"}=1; $ENV{"NTsendmail_debug"}=1;
...@@ -804,11 +804,11 @@ $ENV{"NTsendmail_max_tries"}=5; ...@@ -804,11 +804,11 @@ $ENV{"NTsendmail_max_tries"}=5;
></TR ></TR
></TABLE ></TABLE
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -824,13 +824,13 @@ ALT="Note"></TD ...@@ -824,13 +824,13 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Some mention to also edit >&#13; Some mention to also edit
<TT <TT
CLASS="VARNAME" CLASS="varname"
>$db_pass</TT >$db_pass</TT
> in > in
<TT <TT
CLASS="FILENAME" CLASS="filename"
>globals.pl</TT >globals.pl</TT
> to be your > to be your
<SPAN <SPAN
...@@ -840,7 +840,7 @@ CLASS="QUOTE" ...@@ -840,7 +840,7 @@ CLASS="QUOTE"
you around some problem authenticating to your you around some problem authenticating to your
database, since globals.pl is not normally database, since globals.pl is not normally
restricted by <TT restricted by <TT
CLASS="FILENAME" CLASS="filename"
>.htaccess</TT >.htaccess</TT
>, your >, your
database password is exposed to whoever uses your database password is exposed to whoever uses your
...@@ -853,11 +853,11 @@ CLASS="FILENAME" ...@@ -853,11 +853,11 @@ CLASS="FILENAME"
></LI ></LI
><LI ><LI
><P ><P
> Find and comment out all occurences of >&#13; Find and comment out all occurences of
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"<B >"<B
CLASS="COMMAND" CLASS="command"
>open(SENDMAIL</B >open(SENDMAIL</B
>"</SPAN >"</SPAN
> in > in
...@@ -871,8 +871,8 @@ WIDTH="100%" ...@@ -871,8 +871,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
># new sendmail functionality >&#13;# new sendmail functionality
my $mail=new NTsendmail; my $mail=new NTsendmail;
my $from="bugzilla\@your.machine.name.tld"; my $from="bugzilla\@your.machine.name.tld";
my $to=$login; my $to=$login;
...@@ -886,11 +886,11 @@ $mail-&#62;send($from,$to,$subject,$msg); ...@@ -886,11 +886,11 @@ $mail-&#62;send($from,$to,$subject,$msg);
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -906,9 +906,9 @@ ALT="Note"></TD ...@@ -906,9 +906,9 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Some have found success using the commercial product, >&#13; Some have found success using the commercial product,
<SPAN <SPAN
CLASS="PRODUCTNAME" CLASS="productname"
>Windmail</SPAN >Windmail</SPAN
>. >.
You could try replacing your sendmail calls with: You could try replacing your sendmail calls with:
...@@ -921,8 +921,8 @@ WIDTH="100%" ...@@ -921,8 +921,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log"; >&#13;open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log";
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -941,30 +941,30 @@ CLASS="PROGRAMLISTING" ...@@ -941,30 +941,30 @@ CLASS="PROGRAMLISTING"
></LI ></LI
><LI ><LI
><P ><P
> Change all references in all files from >&#13; Change all references in all files from
<TT <TT
CLASS="FILENAME" CLASS="filename"
>processmail</TT >processmail</TT
> to > to
<TT <TT
CLASS="FILENAME" CLASS="filename"
>processmail.pl</TT >processmail.pl</TT
>, and >, and
rename <TT rename <TT
CLASS="FILENAME" CLASS="filename"
>processmail</TT >processmail</TT
> to > to
<TT <TT
CLASS="FILENAME" CLASS="filename"
>processmail.pl</TT >processmail.pl</TT
>. >.
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -980,7 +980,7 @@ ALT="Note"></TD ...@@ -980,7 +980,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> Many think this may be a change we want to make for >&#13; Many think this may be a change we want to make for
main-tree Bugzilla. It's painless for the UNIX folks, main-tree Bugzilla. It's painless for the UNIX folks,
and will make the Win32 people happier. and will make the Win32 people happier.
</P </P
...@@ -989,11 +989,11 @@ VALIGN="TOP" ...@@ -989,11 +989,11 @@ VALIGN="TOP"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1009,7 +1009,7 @@ ALT="Note"></TD ...@@ -1009,7 +1009,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><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. >&#13; 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 <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
...@@ -1019,8 +1019,10 @@ WIDTH="100%" ...@@ -1019,8 +1019,10 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>&#13;my $smtp = Net::SMTP-&#62;new('&#60;Name of your SMTP server&#62;'); #connect to SMTP server >&#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;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;to($tolist); # recipient's address
$smtp-&#62;data(); # Start the mail $smtp-&#62;data(); # Start the mail
...@@ -1028,7 +1030,10 @@ $smtp-&#62;datasend($msg); ...@@ -1028,7 +1030,10 @@ $smtp-&#62;datasend($msg);
$smtp-&#62;dataend(); # Finish sending the mail $smtp-&#62;dataend(); # Finish sending the mail
$smtp-&#62;quit; # Close the SMTP connection $smtp-&#62;quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist"; $logstr = "$logstr; mail sent to $tolist $cclist";
}&#13;</PRE }
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1044,8 +1049,10 @@ WIDTH="100%" ...@@ -1044,8 +1049,10 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>&#13;use Net::SMTP; >&#13;
use Net::SMTP;
my $smtp = Net::SMTP-&#62;new('&#60;Name of your SMTP server', Timeout =&#62; 30, Debug my $smtp = Net::SMTP-&#62;new('&#60;Name of your SMTP server', Timeout =&#62; 30, Debug
=&#62; 1, ); # connect to SMTP server =&#62; 1, ); # connect to SMTP server
$smtp-&#62;auth; $smtp-&#62;auth;
...@@ -1057,7 +1064,10 @@ recipient's address ...@@ -1057,7 +1064,10 @@ recipient's address
$smtp-&#62;datasend('test'); $smtp-&#62;datasend('test');
$smtp-&#62;dataend(); # Finish sending the mail $smtp-&#62;dataend(); # Finish sending the mail
$smtp-&#62;quit; # Close the SMTP connection $smtp-&#62;quit; # Close the SMTP connection
exit;&#13;</PRE exit;
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1071,11 +1081,11 @@ exit;&#13;</PRE ...@@ -1071,11 +1081,11 @@ exit;&#13;</PRE
></LI ></LI
><LI ><LI
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1091,7 +1101,7 @@ ALT="Note"></TD ...@@ -1091,7 +1101,7 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> This step is optional if you are using IIS or another >&#13; This step is optional if you are using IIS or another
web server which only decides on an interpreter based web server which only decides on an interpreter based
upon the file extension (.pl), rather than the upon the file extension (.pl), rather than the
<SPAN <SPAN
...@@ -1104,7 +1114,7 @@ CLASS="QUOTE" ...@@ -1104,7 +1114,7 @@ CLASS="QUOTE"
></TABLE ></TABLE
></DIV ></DIV
><P ><P
> Modify the path to perl on the first line (#!) of all >&#13; Modify the path to perl on the first line (#!) of all
files to point to your Perl installation, and add files to point to your Perl installation, and add
<SPAN <SPAN
CLASS="QUOTE" CLASS="QUOTE"
...@@ -1130,8 +1140,9 @@ TARGET="_top" ...@@ -1130,8 +1140,9 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
> Modify the invocation of all system() calls in all perl >&#13; Modify the invocation of all system() calls in all perl
scripts in your Bugzilla directory. For instance, change scripts in your Bugzilla directory. You should specify the
full path to perl for each system() call. For instance, change
this line in processmail: this line in processmail:
<TABLE <TABLE
BORDER="0" BORDER="0"
...@@ -1142,27 +1153,12 @@ WIDTH="100%" ...@@ -1142,27 +1153,12 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>
system ("./processmail.pl",@ARGLIST);
</PRE
></FONT
></TD
></TR
></TABLE
> to
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
> >
system ("perl processmail.pl",@ARGLIST); system ("./processmail",@ARGLIST);
&#60;/programlisting&#62; to
&#60;programlisting&#62;
system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -1173,8 +1169,8 @@ system ("perl processmail.pl",@ARGLIST); ...@@ -1173,8 +1169,8 @@ system ("perl processmail.pl",@ARGLIST);
></LI ></LI
><LI ><LI
><P ><P
> Add <TT >&#13; Add <TT
CLASS="FUNCTION" CLASS="function"
>binmode()</TT >binmode()</TT
> calls so attachments > calls so attachments
will work (<A will work (<A
...@@ -1184,23 +1180,24 @@ TARGET="_top" ...@@ -1184,23 +1180,24 @@ TARGET="_top"
>). >).
</P </P
><P ><P
> Because Microsoft Windows based systems handle binary >&#13; Because Microsoft Windows based systems handle binary
files different than Unix based systems, you need to add files different than Unix based systems, you need to add
the following lines to the following lines to
<TT <TT
CLASS="FILENAME" CLASS="filename"
>createattachment.cgi</TT >createattachment.cgi</TT
> and > and
<TT <TT
CLASS="FILENAME" CLASS="filename"
>showattachment.cgi</TT >showattachment.cgi</TT
> before the > before the
<TT <TT
CLASS="FUNCTION" CLASS="function"
>require 'CGI.pl';</TT >require 'CGI.pl';</TT
> line.</P > line.
</P
><P ><P
><TABLE >&#13;<TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -1209,9 +1206,12 @@ WIDTH="100%" ...@@ -1209,9 +1206,12 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>binmode(STDIN); >&#13;
binmode(STDOUT);</PRE binmode(STDIN);
binmode(STDOUT);
</PRE
></FONT ></FONT
></TD ></TD
></TR ></TR
...@@ -1219,11 +1219,11 @@ binmode(STDOUT);</PRE ...@@ -1219,11 +1219,11 @@ binmode(STDOUT);</PRE
> >
</P </P
><DIV ><DIV
CLASS="NOTE" CLASS="note"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="NOTE" CLASS="note"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1239,18 +1239,18 @@ ALT="Note"></TD ...@@ -1239,18 +1239,18 @@ ALT="Note"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> According to <A >&#13; According to <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000" HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
TARGET="_top" TARGET="_top"
>bug 62000</A >bug 62000</A
>, the perl documentation says that you should always use <TT >, the perl documentation says that you should always use <TT
CLASS="FUNCTION" CLASS="function"
>binmode()</TT >binmode()</TT
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT > when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
CLASS="FUNCTION" CLASS="function"
>binmode()</TT >binmode()</TT
> at the begining of the attachment files, there should be logic to determine if <TT > at the begining of the attachment files, there should be logic to determine if <TT
CLASS="FUNCTION" CLASS="function"
>binmode()</TT >binmode()</TT
> is needed or not. > is needed or not.
</P </P
...@@ -1262,11 +1262,11 @@ CLASS="FUNCTION" ...@@ -1262,11 +1262,11 @@ CLASS="FUNCTION"
></OL ></OL
></DIV ></DIV
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1282,13 +1282,13 @@ ALT="Tip"></TD ...@@ -1282,13 +1282,13 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If you are using IIS or Personal Web Server, you must add cgi >&#13; If you are using IIS or Personal Web Server, you must add cgi
relationships to Properties -&#62; Home directory (tab) -&#62; relationships to Properties -&#62; Home directory (tab) -&#62;
Application Settings (section) -&#62; Configuration (button), Application Settings (section) -&#62; Configuration (button),
such as: such as:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -1297,7 +1297,7 @@ WIDTH="100%" ...@@ -1297,7 +1297,7 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> >
.cgi to: &#60;perl install directory&#62;\perl.exe %s %s .cgi to: &#60;perl install directory&#62;\perl.exe %s %s
.pl to: &#60;perl install directory&#62;\perl.exe %s %s .pl to: &#60;perl install directory&#62;\perl.exe %s %s
...@@ -1317,19 +1317,19 @@ GET,HEAD,POST ...@@ -1317,19 +1317,19 @@ GET,HEAD,POST
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="ADDLWINTIPS" NAME="addlwintips"
>3.6.2. Additional Windows Tips</A >3.6.2. Additional Windows Tips</A
></H2 ></H2
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1345,14 +1345,14 @@ ALT="Tip"></TD ...@@ -1345,14 +1345,14 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> From Andrew Pearson: >&#13; From Andrew Pearson:
<A <A
NAME="AEN1212" NAME="AEN1221"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
><P ><P
> You can make Bugzilla work with Personal Web Server for >&#13; You can make Bugzilla work with Personal Web Server for
Windows 98 and higher, as well as for IIS 4.0. Windows 98 and higher, as well as for IIS 4.0.
Microsoft has information available at <A Microsoft has information available at <A
HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
...@@ -1361,11 +1361,11 @@ TARGET="_top" ...@@ -1361,11 +1361,11 @@ TARGET="_top"
> >
</P </P
><P ><P
> Basically you need to add two String Keys in the >&#13; Basically you need to add two String Keys in the
registry at the following location: registry at the following location:
</P </P
><P ><P
> <TABLE >&#13; <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
WIDTH="100%" WIDTH="100%"
...@@ -1374,8 +1374,8 @@ WIDTH="100%" ...@@ -1374,8 +1374,8 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap >&#13;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
</PRE </PRE
></FONT ></FONT
></TD ></TD
...@@ -1384,15 +1384,15 @@ CLASS="PROGRAMLISTING" ...@@ -1384,15 +1384,15 @@ CLASS="PROGRAMLISTING"
> >
</P </P
><P ><P
> The keys should be called ".pl" and ".cgi", and both >&#13; The keys should be called ".pl" and ".cgi", and both
should have a value something like: should have a value something like:
<B <B
CLASS="COMMAND" CLASS="command"
>c:/perl/bin/perl.exe "%s" "%s"</B >c:/perl/bin/perl.exe "%s" "%s"</B
> >
</P </P
><P ><P
> The KB article only talks about .pl, but it goes into >&#13; The KB article only talks about .pl, but it goes into
more detail and provides a perl test script. more detail and provides a perl test script.
</P </P
></BLOCKQUOTE ></BLOCKQUOTE
...@@ -1403,11 +1403,11 @@ CLASS="COMMAND" ...@@ -1403,11 +1403,11 @@ CLASS="COMMAND"
></TABLE ></TABLE
></DIV ></DIV
><DIV ><DIV
CLASS="TIP" CLASS="tip"
><P ><P
></P ></P
><TABLE ><TABLE
CLASS="TIP" CLASS="tip"
WIDTH="100%" WIDTH="100%"
BORDER="0" BORDER="0"
><TR ><TR
...@@ -1423,7 +1423,7 @@ ALT="Tip"></TD ...@@ -1423,7 +1423,7 @@ ALT="Tip"></TD
ALIGN="LEFT" ALIGN="LEFT"
VALIGN="TOP" VALIGN="TOP"
><P ><P
> If attempting to run Bugzilla 2.12 or older, you will need >&#13; If attempting to run Bugzilla 2.12 or older, you will need
to remove encrypt() calls from the Perl source. This is to remove encrypt() calls from the Perl source. This is
<EM <EM
>not necessary</EM >not necessary</EM
...@@ -1431,9 +1431,9 @@ VALIGN="TOP" ...@@ -1431,9 +1431,9 @@ VALIGN="TOP"
later, which includes the current release, Bugzilla later, which includes the current release, Bugzilla
2.14. 2.14.
<DIV <DIV
CLASS="EXAMPLE" CLASS="example"
><A ><A
NAME="AEN1224" NAME="AEN1233"
></A ></A
><P ><P
><B ><B
...@@ -1441,7 +1441,7 @@ NAME="AEN1224" ...@@ -1441,7 +1441,7 @@ NAME="AEN1224"
2.12 or earlier</B 2.12 or earlier</B
></P ></P
><P ><P
> Replace this: >&#13; Replace this:
<TABLE <TABLE
BORDER="0" BORDER="0"
BGCOLOR="#E0E0E0" BGCOLOR="#E0E0E0"
...@@ -1451,7 +1451,7 @@ WIDTH="100%" ...@@ -1451,7 +1451,7 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> >
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn(); my $enteredcryptpwd = FetchOneColumn();
...@@ -1471,7 +1471,7 @@ WIDTH="100%" ...@@ -1471,7 +1471,7 @@ WIDTH="100%"
><FONT ><FONT
COLOR="#000000" COLOR="#000000"
><PRE ><PRE
CLASS="PROGRAMLISTING" CLASS="programlisting"
> >
my $enteredcryptpwd = $enteredpwd my $enteredcryptpwd = $enteredpwd
</PRE </PRE
...@@ -1491,22 +1491,23 @@ my $enteredcryptpwd = $enteredpwd ...@@ -1491,22 +1491,23 @@ my $enteredcryptpwd = $enteredpwd
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="SECTION" CLASS="section"
><H2 ><H2
CLASS="SECTION" CLASS="section"
><A ><A
NAME="BZLDAP" NAME="bzldap"
>3.6.3. Bugzilla LDAP Integration</A >3.6.3. Bugzilla LDAP Integration</A
></H2 ></H2
><P ><P
> What follows is some late-breaking information on using the >&#13; What follows is some late-breaking information on using the
LDAP authentication options with Bugzilla. The author has not LDAP authentication options with Bugzilla. The author has not
tested these (nor even formatted this section!) so please tested these (nor even formatted this section!) so please
contribute feedback to the newsgroup. contribute feedback to the newsgroup.
</P </P
><P ><P
CLASS="LITERALLAYOUT" CLASS="literallayout"
>Mozilla::LDAP&nbsp;module<br> ><br>
Mozilla::LDAP&nbsp;module<br>
<br> <br>
The&nbsp;Mozilla::LDAP&nbsp;module&nbsp;allows&nbsp;you&nbsp;to&nbsp;use&nbsp;LDAP&nbsp;for&nbsp;authentication&nbsp;to<br> The&nbsp;Mozilla::LDAP&nbsp;module&nbsp;allows&nbsp;you&nbsp;to&nbsp;use&nbsp;LDAP&nbsp;for&nbsp;authentication&nbsp;to<br>
the&nbsp;Bugzilla&nbsp;system.&nbsp;&nbsp;This&nbsp;module&nbsp;is&nbsp;not&nbsp;required&nbsp;if&nbsp;you&nbsp;are&nbsp;not&nbsp;using<br> the&nbsp;Bugzilla&nbsp;system.&nbsp;&nbsp;This&nbsp;module&nbsp;is&nbsp;not&nbsp;required&nbsp;if&nbsp;you&nbsp;are&nbsp;not&nbsp;using<br>
......
docs/txt/Bugzilla-Guide.txt
View file @ d7f38125
...@@ -41,14 +41,14 @@ Matthew P. Barnson ...@@ -41,14 +41,14 @@ Matthew P. Barnson
Bugzilla is an enterprise-class set of software utilities that, when Bugzilla is an enterprise-class set of software utilities that, when
used together, power issue-tracking for hundreds of organizations used together, power issue-tracking for hundreds of organizations
around the world, tracking millions of bugs. While it is easy to use around the world, tracking millions of bugs. While it is easy to use
and quite flexible, it is very difficult for a novice to install and and quite flexible, it is difficult for a novice to install and
maintain. Although we have provided step-by-step directions, Bugzilla maintain. Although we have provided step-by-step directions, Bugzilla
is not always easy to get working. Please be sure the person is not always easy to get working. Please be sure the person
responsible for installing and maintaining this software is a responsible for installing and maintaining this software is a
qualified professional on operating system upon which you install qualified professional for the operating system upon which you install
Bugzilla. Bugzilla.
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. IF YOU THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT. IF YOU
WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS
AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN
HTML! HTML!
...@@ -649,8 +649,8 @@ Chapter 2. Using Bugzilla ...@@ -649,8 +649,8 @@ Chapter 2. Using Bugzilla
tends to run the latest code, so these two utilities should be tends to run the latest code, so these two utilities should be
available there for your perusal. available there for your perusal.
At this point, please visit the main Bugzilla site, At this point, let's visit the query page.
bugzilla.mozilla.org, to see a more fleshed-out query page. landfill.tequilarista.org/bugzilla-tip/query.cgi
The first thing you need to notice about the Bugzilla Query Page is The first thing you need to notice about the Bugzilla Query Page is
that nearly every box you see on your screen has a hyperlink nearby, that nearly every box you see on your screen has a hyperlink nearby,
...@@ -1823,6 +1823,23 @@ sr/local/lib); ...@@ -1823,6 +1823,23 @@ sr/local/lib);
will need to change the ip address in data/webdot/.htaccess to the ip will need to change the ip address in data/webdot/.htaccess to the ip
address of the webdot server that you are using. address of the webdot server that you are using.
The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration. Be sure to
check the <Directory> entries for your Bugzilla directory so that the
.htaccess file is allowed to override web server defaults. For
instance, let's assume your installation of Bugzilla is installed to
/usr/local/bugzilla. You should have this <Directory> entry in your
httpd.conf file:
<Directory /usr/local/bugzilla/>
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
</Directory>
The important part above is "AllowOverride All". Without that,
the .htaccess file created by checksetup.pl will not have sufficient
permissions to protect your Bugzilla installation.
If you are using Internet Information Server or other web server which If you are using Internet Information Server or other web server which
does not observe .htaccess conventions, you can disable their creation does not observe .htaccess conventions, you can disable their creation
by editing localconfig and setting the $create_htaccess variable to 0. by editing localconfig and setting the $create_htaccess variable to 0.
...@@ -2082,6 +2099,7 @@ log"; ...@@ -2082,6 +2099,7 @@ log";
Some people have suggested using the Net::SMTP Perl module instead of Some people have suggested using the Net::SMTP Perl module instead of
NTsendmail or the other options listed here. You can change NTsendmail or the other options listed here. You can change
processmail.pl to make this work. processmail.pl to make this work.
my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
ver ver
$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here $smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
...@@ -2093,7 +2111,9 @@ $smtp->quit; # Close the SMTP connection ...@@ -2093,7 +2111,9 @@ $smtp->quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist"; $logstr = "$logstr; mail sent to $tolist $cclist";
} }
here is a test mail program for Net::SMTP: here is a test mail program for Net::SMTP:
use Net::SMTP; use Net::SMTP;
my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
=> 1, ); # connect to SMTP server => 1, ); # connect to SMTP server
...@@ -2108,6 +2128,7 @@ recipient's address ...@@ -2108,6 +2128,7 @@ recipient's address
$smtp->quit; # Close the SMTP connection $smtp->quit; # Close the SMTP connection
exit; exit;
12. 12.
Note Note
...@@ -2125,17 +2146,15 @@ exit; ...@@ -2125,17 +2146,15 @@ exit;
in order to work. See http://www.cygwin.com/ for details on in order to work. See http://www.cygwin.com/ for details on
obtaining Cygwin. obtaining Cygwin.
13. Modify the invocation of all system() calls in all perl scripts in 13. Modify the invocation of all system() calls in all perl scripts in
your Bugzilla directory. For instance, change this line in your Bugzilla directory. You should specify the full path to perl
for each system() call. For instance, change this line in
processmail: processmail:
system ("./processmail.pl",@ARGLIST); system ("./processmail",@ARGLIST);
</programlisting> to
<programlisting>
to system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
system ("perl processmail.pl",@ARGLIST);
14. Add binmode() calls so attachments will work (bug 62000). 14. Add binmode() calls so attachments will work (bug 62000).
...@@ -4520,7 +4539,7 @@ if ($::FORM{sub} eq 'PutFooter') { ...@@ -4520,7 +4539,7 @@ if ($::FORM{sub} eq 'PutFooter') {
} }
and then put this line in index.shtml. and then put this line in index.shtml.
<!--#include virtual="api.cgi?sub=PutFooter"--> <!--#include virtual="api.cgi?sub=PutFooter"-->
Note Note
...@@ -5165,24 +5184,21 @@ Appendix B. Software Download Links ...@@ -5165,24 +5184,21 @@ Appendix B. Software Download Links
CPAN: http://www.cpan.org/ CPAN: http://www.cpan.org/
DBI Perl module: DBI Perl module: http://www.cpan.org/modules/by-module/DBI/
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
Data::Dumper module: Data::Dumper module: http://www.cpan.org/modules/by-module/Data/
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
MySQL related Perl modules: MySQL related Perl modules:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/ http://www.cpan.org/modules/by-module/Mysql/
TimeDate Perl module collection: TimeDate Perl module collection:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/ http://www.cpan.org/modules/by-module/Date/
GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/ GD Perl module: http://www.cpan.org/modules/by-module/GD/ Alternately,
Alternately, you should be able to find the latest version of GD at you should be able to find the latest version of GD at
http://www.boutell.com/gd/ http://www.boutell.com/gd/
Chart::Base module: Chart::Base module: http://www.cpan.org/modules/by-module/Chart/
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
LinuxDoc Software: http://www.linuxdoc.org/ (for documentation LinuxDoc Software: http://www.linuxdoc.org/ (for documentation
maintenance) maintenance)
...@@ -5751,10 +5767,10 @@ RewriteEngine On ...@@ -5751,10 +5767,10 @@ RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost> </VirtualHost>
2. There are many, many more things you can do with mod_rewrite. As 2. There are many, many more things you can do with
time goes on, I will include many more in the Guide. For now, mod_rewrite. As time goes on, I will include many more in the
though, please refer to the mod_rewrite documentation at Guide. For now, though, please refer to the mod_rewrite
http://www.apache.org documentation at http://www.apache.org
_________________________________________________________________ _________________________________________________________________
D.2. The setperl.csh Utility D.2. The setperl.csh Utility
...@@ -5899,7 +5915,10 @@ D.5.2. Coding Style for Bugzilla ...@@ -5899,7 +5915,10 @@ D.5.2. Coding Style for Bugzilla
favorite shell prompt. favorite shell prompt.
What appears below if a brief summary, please refer to the perl style What appears below if a brief summary, please refer to the perl style
guide if you don't see your question covered here. guide if you don't see your question covered here. It is much better
to submit a patch which fails these criteria than no patch at all, but
please try to meet these minimum standards when submitting code to
Bugzilla.
* Whitespace * Whitespace
Bugzilla's prefered indentation is 4 spaces (no tabs, please). Bugzilla's prefered indentation is 4 spaces (no tabs, please).
...@@ -5928,12 +5947,33 @@ else ...@@ -5928,12 +5947,33 @@ else
} }
* Cookies
Bugzilla uses cookies to ease the user experience, but no new
patches should require user-side cookies.
* File Names * File Names
File names for bugzilla code and support documention should be File names for bugzilla code and support documention should be
legal across multiple platforms. \ / : * ? " < > and | are all legal across multiple platforms. \ / : * ? " < > and | are all
illegal characters for filenames on various platforms. Also, file illegal characters for filenames on various platforms. Also, file
names should not have spaces in them as they can cause confusion names should not have spaces in them as they can cause confusion
in CVS and other mozilla.org utilities. in CVS and other mozilla.org utilities.
* Javascript dependencies
While Bugzilla uses Javascript to make the user experience easier,
no patch to Bugzilla should require Javascript.
* Patch Format
All patches submitted for inclusion into Bugzilla should be in the
form of a "unified diff". This comes from using "diff -u" instead
of simply "diff" when creating your patch. This will result in
quicker acceptance of the patch.
* Schema Changes
If you make schema changes, you should modify sanitycheck.cgi to
support the new schema. All referential columns should be checked.
* Taint Mode
All new cgis must run in Taint mode (Perl taint and DBI taint),
and existing cgi's which run in taint mode must not have taint
mode turned off.
* Templatization
Patches to Bugzilla need to support templates so they do not force
user interface choices on Bugzilla administrators.
* Variable Names * Variable Names
If a variable is scoped globally ($::variable) its name should be If a variable is scoped globally ($::variable) its name should be
descriptive of what it contains. Local variables can be named a descriptive of what it contains. Local variables can be named a
......
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