COLOR="#000000"
><PRE
CLASS="programlisting"
->Options ExecCGI<br>AllowOverride Limit</PRE
+> Options ExecCGI
+AllowOverride Limit
+ </PRE
></FONT
></TD
></TR
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
><P
>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
><DL
><DT
>A.1.1. <A
-HREF="#AEN1723"
+HREF="#AEN1724"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="#AEN1729"
+HREF="#AEN1730"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="#AEN1735"
+HREF="#AEN1736"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="#AEN1742"
+HREF="#AEN1743"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="#AEN1767"
+HREF="#AEN1768"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="#AEN1773"
+HREF="#AEN1774"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="#AEN1779"
+HREF="#AEN1780"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
-HREF="#AEN1786"
+HREF="#AEN1787"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
-HREF="#AEN1791"
+HREF="#AEN1792"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
><DT
>A.1.10. <A
-HREF="#AEN1797"
+HREF="#AEN1798"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DL
><DT
>A.2.1. <A
-HREF="#AEN1807"
+HREF="#AEN1808"
> Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
-HREF="#AEN1812"
+HREF="#AEN1813"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="#AEN1817"
+HREF="#AEN1818"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="#AEN1822"
+HREF="#AEN1823"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="#AEN1827"
+HREF="#AEN1828"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="#AEN1832"
+HREF="#AEN1833"
> Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values?
></DT
><DT
>A.2.7. <A
-HREF="#AEN1839"
+HREF="#AEN1840"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="#AEN1846"
+HREF="#AEN1847"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="#AEN1851"
+HREF="#AEN1852"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="#AEN1856"
+HREF="#AEN1857"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="#AEN1863"
+HREF="#AEN1864"
> Does Bugzilla allow data to be imported and exported? If I had outsiders
write up a bug report using a MS Word bug template, could that template be
imported into "matching" fields? If I wanted to take the results of a query
></DT
><DT
>A.2.12. <A
-HREF="#AEN1871"
+HREF="#AEN1872"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="#AEN1876"
+HREF="#AEN1877"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="#AEN1881"
+HREF="#AEN1882"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="#AEN1886"
+HREF="#AEN1887"
> Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use
or how are they notified?
></DT
><DT
>A.2.16. <A
-HREF="#AEN1891"
+HREF="#AEN1892"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="#AEN1897"
+HREF="#AEN1898"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="#AEN1902"
+HREF="#AEN1903"
> What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to
have? I need to find out if we were to go with Bugzilla, what types of
></DT
><DT
>A.2.19. <A
-HREF="#AEN1908"
+HREF="#AEN1909"
> What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to
install and a couple of hours per week to maintain and customize or is this
></DT
><DT
>A.2.20. <A
-HREF="#AEN1913"
+HREF="#AEN1914"
> Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
</A
><DL
><DT
>A.3.1. <A
-HREF="#AEN1920"
+HREF="#AEN1921"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide)?
</A
></DT
><DT
>A.3.2. <A
-HREF="#AEN1926"
+HREF="#AEN1927"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="#AEN1931"
+HREF="#AEN1932"
> I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly.
><DL
><DT
>A.4.1. <A
-HREF="#AEN1938"
+HREF="#AEN1939"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.4.2. <A
-HREF="#AEN1943"
+HREF="#AEN1944"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.4.3. <A
-HREF="#AEN1948"
+HREF="#AEN1949"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="#AEN1954"
+HREF="#AEN1955"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="#AEN1961"
+HREF="#AEN1962"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="#AEN1966"
+HREF="#AEN1967"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="#AEN1973"
+HREF="#AEN1974"
> How come email from Bugzilla changes never reaches me?
</A
></DT
><DL
><DT
>A.5.1. <A
-HREF="#AEN1981"
+HREF="#AEN1982"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="#AEN1986"
+HREF="#AEN1987"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="#AEN1994"
+HREF="#AEN1995"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="#AEN1999"
+HREF="#AEN2000"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.5.5. <A
-HREF="#AEN2004"
+HREF="#AEN2005"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
>A.5.6. <A
-HREF="#AEN2009"
+HREF="#AEN2010"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
><DL
><DT
>A.6.1. <A
-HREF="#AEN2018"
+HREF="#AEN2019"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="#AEN2023"
+HREF="#AEN2024"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="#AEN2028"
+HREF="#AEN2029"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="#AEN2036"
+HREF="#AEN2037"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
><DL
><DT
>A.7.1. <A
-HREF="#AEN2057"
+HREF="#AEN2058"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="#AEN2062"
+HREF="#AEN2063"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="#AEN2067"
+HREF="#AEN2068"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.7.4. <A
-HREF="#AEN2077"
+HREF="#AEN2078"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="#AEN2082"
+HREF="#AEN2083"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.7.6. <A
-HREF="#AEN2087"
+HREF="#AEN2088"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DL
><DT
>A.8.1. <A
-HREF="#AEN2094"
+HREF="#AEN2095"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.2. <A
-HREF="#AEN2103"
+HREF="#AEN2104"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.8.3. <A
-HREF="#AEN2109"
+HREF="#AEN2110"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
CLASS="question"
><P
><A
-NAME="AEN1723"
+NAME="AEN1724"
></A
><B
>A.1.1. </B
CLASS="question"
><P
><A
-NAME="AEN1729"
+NAME="AEN1730"
></A
><B
>A.1.2. </B
CLASS="question"
><P
><A
-NAME="AEN1735"
+NAME="AEN1736"
></A
><B
>A.1.3. </B
CLASS="question"
><P
><A
-NAME="AEN1742"
+NAME="AEN1743"
></A
><B
>A.1.4. </B
CLASS="question"
><P
><A
-NAME="AEN1767"
+NAME="AEN1768"
></A
><B
>A.1.5. </B
CLASS="question"
><P
><A
-NAME="AEN1773"
+NAME="AEN1774"
></A
><B
>A.1.6. </B
CLASS="question"
><P
><A
-NAME="AEN1779"
+NAME="AEN1780"
></A
><B
>A.1.7. </B
CLASS="question"
><P
><A
-NAME="AEN1786"
+NAME="AEN1787"
></A
><B
>A.1.8. </B
CLASS="question"
><P
><A
-NAME="AEN1791"
+NAME="AEN1792"
></A
><B
>A.1.9. </B
CLASS="question"
><P
><A
-NAME="AEN1797"
+NAME="AEN1798"
></A
><B
>A.1.10. </B
CLASS="question"
><P
><A
-NAME="AEN1807"
+NAME="AEN1808"
></A
><B
>A.2.1. </B
CLASS="question"
><P
><A
-NAME="AEN1812"
+NAME="AEN1813"
></A
><B
>A.2.2. </B
CLASS="question"
><P
><A
-NAME="AEN1817"
+NAME="AEN1818"
></A
><B
>A.2.3. </B
CLASS="question"
><P
><A
-NAME="AEN1822"
+NAME="AEN1823"
></A
><B
>A.2.4. </B
CLASS="question"
><P
><A
-NAME="AEN1827"
+NAME="AEN1828"
></A
><B
>A.2.5. </B
CLASS="question"
><P
><A
-NAME="AEN1832"
+NAME="AEN1833"
></A
><B
>A.2.6. </B
CLASS="question"
><P
><A
-NAME="AEN1839"
+NAME="AEN1840"
></A
><B
>A.2.7. </B
CLASS="question"
><P
><A
-NAME="AEN1846"
+NAME="AEN1847"
></A
><B
>A.2.8. </B
CLASS="question"
><P
><A
-NAME="AEN1851"
+NAME="AEN1852"
></A
><B
>A.2.9. </B
CLASS="question"
><P
><A
-NAME="AEN1856"
+NAME="AEN1857"
></A
><B
>A.2.10. </B
CLASS="question"
><P
><A
-NAME="AEN1863"
+NAME="AEN1864"
></A
><B
>A.2.11. </B
CLASS="question"
><P
><A
-NAME="AEN1871"
+NAME="AEN1872"
></A
><B
>A.2.12. </B
CLASS="question"
><P
><A
-NAME="AEN1876"
+NAME="AEN1877"
></A
><B
>A.2.13. </B
CLASS="question"
><P
><A
-NAME="AEN1881"
+NAME="AEN1882"
></A
><B
>A.2.14. </B
CLASS="question"
><P
><A
-NAME="AEN1886"
+NAME="AEN1887"
></A
><B
>A.2.15. </B
CLASS="question"
><P
><A
-NAME="AEN1891"
+NAME="AEN1892"
></A
><B
>A.2.16. </B
CLASS="question"
><P
><A
-NAME="AEN1897"
+NAME="AEN1898"
></A
><B
>A.2.17. </B
CLASS="question"
><P
><A
-NAME="AEN1902"
+NAME="AEN1903"
></A
><B
>A.2.18. </B
CLASS="question"
><P
><A
-NAME="AEN1908"
+NAME="AEN1909"
></A
><B
>A.2.19. </B
CLASS="question"
><P
><A
-NAME="AEN1913"
+NAME="AEN1914"
></A
><B
>A.2.20. </B
CLASS="question"
><P
><A
-NAME="AEN1920"
+NAME="AEN1921"
></A
><B
>A.3.1. </B
CLASS="question"
><P
><A
-NAME="AEN1926"
+NAME="AEN1927"
></A
><B
>A.3.2. </B
CLASS="question"
><P
><A
-NAME="AEN1931"
+NAME="AEN1932"
></A
><B
>A.3.3. </B
CLASS="question"
><P
><A
-NAME="AEN1938"
+NAME="AEN1939"
></A
><B
>A.4.1. </B
CLASS="question"
><P
><A
-NAME="AEN1943"
+NAME="AEN1944"
></A
><B
>A.4.2. </B
CLASS="question"
><P
><A
-NAME="AEN1948"
+NAME="AEN1949"
></A
><B
>A.4.3. </B
CLASS="question"
><P
><A
-NAME="AEN1954"
+NAME="AEN1955"
></A
><B
>A.4.4. </B
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1958"
+NAME="AEN1959"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN1961"
+NAME="AEN1962"
></A
><B
>A.4.5. </B
CLASS="question"
><P
><A
-NAME="AEN1966"
+NAME="AEN1967"
></A
><B
>A.4.6. </B
CLASS="question"
><P
><A
-NAME="AEN1973"
+NAME="AEN1974"
></A
><B
>A.4.7. </B
CLASS="question"
><P
><A
-NAME="AEN1981"
+NAME="AEN1982"
></A
><B
>A.5.1. </B
CLASS="question"
><P
><A
-NAME="AEN1986"
+NAME="AEN1987"
></A
><B
>A.5.2. </B
CLASS="question"
><P
><A
-NAME="AEN1994"
+NAME="AEN1995"
></A
><B
>A.5.3. </B
CLASS="question"
><P
><A
-NAME="AEN1999"
+NAME="AEN2000"
></A
><B
>A.5.4. </B
CLASS="question"
><P
><A
-NAME="AEN2004"
+NAME="AEN2005"
></A
><B
>A.5.5. </B
CLASS="question"
><P
><A
-NAME="AEN2009"
+NAME="AEN2010"
></A
><B
>A.5.6. </B
CLASS="question"
><P
><A
-NAME="AEN2018"
+NAME="AEN2019"
></A
><B
>A.6.1. </B
CLASS="question"
><P
><A
-NAME="AEN2023"
+NAME="AEN2024"
></A
><B
>A.6.2. </B
CLASS="question"
><P
><A
-NAME="AEN2028"
+NAME="AEN2029"
></A
><B
>A.6.3. </B
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN2033"
+NAME="AEN2034"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN2036"
+NAME="AEN2037"
></A
><B
>A.6.4. </B
CLASS="question"
><P
><A
-NAME="AEN2057"
+NAME="AEN2058"
></A
><B
>A.7.1. </B
CLASS="question"
><P
><A
-NAME="AEN2062"
+NAME="AEN2063"
></A
><B
>A.7.2. </B
CLASS="question"
><P
><A
-NAME="AEN2067"
+NAME="AEN2068"
></A
><B
>A.7.3. </B
CLASS="question"
><P
><A
-NAME="AEN2077"
+NAME="AEN2078"
></A
><B
>A.7.4. </B
CLASS="question"
><P
><A
-NAME="AEN2082"
+NAME="AEN2083"
></A
><B
>A.7.5. </B
CLASS="question"
><P
><A
-NAME="AEN2087"
+NAME="AEN2088"
></A
><B
>A.7.6. </B
CLASS="question"
><P
><A
-NAME="AEN2094"
+NAME="AEN2095"
></A
><B
>A.8.1. </B
CLASS="question"
><P
><A
-NAME="AEN2103"
+NAME="AEN2104"
></A
><B
>A.8.2. </B
CLASS="question"
><P
><A
-NAME="AEN2109"
+NAME="AEN2110"
></A
><B
>A.8.3. </B
><HR><H2
CLASS="section"
><A
-NAME="AEN2151"
+NAME="AEN2152"
></A
>B.2.1. Bugzilla Database Basics</H2
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN2178"
+NAME="AEN2179"
></A
>B.2.1.1. Bugzilla Database Tables</H3
><P
><H1
CLASS="glossdiv"
><A
-NAME="AEN2257"
+NAME="AEN2258"
></A
>0-9, high ascii</H1
><DL
></DIV
></BODY
></HTML
->
+>
\ No newline at end of file
CLASS="chapter"
><H1
><A
-NAME="about">Chapter 1. About This Guide</H1
+NAME="about"
+></A
+>Chapter 1. About This Guide</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
+NAME="cmdline"
+></A
+>C.2. Command-line Bugzilla Queries</H1
><P
>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
><H1
CLASS="section"
><A
-NAME="conventions">1.5. Document Conventions</H1
+NAME="conventions"
+></A
+>1.5. Document Conventions</H1
><P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><A
-NAME="AEN178"><P
+NAME="AEN178"
+></A
+><P
></P
><TABLE
BORDER="0"
><H1
CLASS="section"
><A
-NAME="copyright">1.1. Copyright Information</H1
+NAME="copyright"
+></A
+>1.1. Copyright Information</H1
><A
-NAME="AEN31"><TABLE
+NAME="AEN31"
+></A
+><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
><H2
CLASS="section"
><A
-NAME="gfdl">1.1.1. GNU Free Documentation License</H2
+NAME="gfdl"
+></A
+>1.1.1. GNU Free Documentation License</H2
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN38"><BLOCKQUOTE
+NAME="AEN38"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
><H3
CLASS="section"
><A
-NAME="gfdl-0">0. PREAMBLE</H3
+NAME="gfdl-0"
+></A
+>0. PREAMBLE</H3
><P
>The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone the
><H3
CLASS="section"
><A
-NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H3
+NAME="gfdl-1"
+></A
+>1. APPLICABILITY AND DEFINITIONS</H3
><P
>This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed under
><H3
CLASS="section"
><A
-NAME="gfdl-2">2. VERBATIM COPYING</H3
+NAME="gfdl-2"
+></A
+>2. VERBATIM COPYING</H3
><P
>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
><H3
CLASS="section"
><A
-NAME="gfdl-3">3. COPYING IN QUANTITY</H3
+NAME="gfdl-3"
+></A
+>3. COPYING IN QUANTITY</H3
><P
>If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you must
><H3
CLASS="section"
><A
-NAME="gfdl-4">4. MODIFICATIONS</H3
+NAME="gfdl-4"
+></A
+>4. MODIFICATIONS</H3
><P
>You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you release
><H3
CLASS="section"
><A
-NAME="gfdl-5">5. COMBINING DOCUMENTS</H3
+NAME="gfdl-5"
+></A
+>5. COMBINING DOCUMENTS</H3
><P
>You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for modified
><H3
CLASS="section"
><A
-NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H3
+NAME="gfdl-6"
+></A
+>6. COLLECTIONS OF DOCUMENTS</H3
><P
>You may make a collection consisting of the Document and other
documents released under this License, and replace the individual copies
><H3
CLASS="section"
><A
-NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H3
+NAME="gfdl-7"
+></A
+>7. AGGREGATION WITH INDEPENDENT WORKS</H3
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
><H3
CLASS="section"
><A
-NAME="gfdl-8">8. TRANSLATION</H3
+NAME="gfdl-8"
+></A
+>8. TRANSLATION</H3
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
><H3
CLASS="section"
><A
-NAME="gfdl-9">9. TERMINATION</H3
+NAME="gfdl-9"
+></A
+>9. TERMINATION</H3
><P
>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
><H3
CLASS="section"
><A
-NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H3
+NAME="gfdl-10"
+></A
+>10. FUTURE REVISIONS OF THIS LICENSE</H3
><P
>The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new versions
><H3
CLASS="section"
><A
-NAME="gfdl-howto">How to use this License for your documents</H3
+NAME="gfdl-howto"
+></A
+>How to use this License for your documents</H3
><P
>To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
-NAME="AEN128"><BLOCKQUOTE
+NAME="AEN128"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
><H1
CLASS="section"
><A
-NAME="credits">1.4. Credits</H1
+NAME="credits"
+></A
+>1.4. Credits</H1
><P
> The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
><H1
CLASS="section"
><A
-NAME="cust-templates">5.7. Template Customisation</H1
+NAME="cust-templates"
+></A
+>5.7. Template Customisation</H1
><P
> One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
><H2
CLASS="section"
><A
-NAME="AEN1539">5.7.1. What to Edit</H2
+NAME="AEN1539"
+></A
+>5.7.1. What to Edit</H2
><P
> There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
><H2
CLASS="section"
><A
-NAME="AEN1558">5.7.2. How To Edit Templates</H2
+NAME="AEN1558"
+></A
+>5.7.2. How To Edit Templates</H2
><P
> The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
><H2
CLASS="section"
><A
-NAME="AEN1568">5.7.3. Template Formats</H2
+NAME="AEN1568"
+></A
+>5.7.3. Template Formats</H2
><P
> Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
><H2
CLASS="section"
><A
-NAME="AEN1581">5.7.4. Particular Templates</H2
+NAME="AEN1581"
+></A
+>5.7.4. Particular Templates</H2
><P
> There are a few templates you may be particularly interested in
customising for your installation.
CLASS="appendix"
><H1
><A
-NAME="database">Appendix B. The Bugzilla Database</H1
+NAME="database"
+></A
+>Appendix B. The Bugzilla Database</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
+NAME="dbdoc"
+></A
+>B.2. MySQL Bugzilla Database Introduction</H1
><P
>This information comes straight from my life. I was forced to learn
how Bugzilla organizes database because of nitpicky requests from users
><H2
CLASS="section"
><A
-NAME="AEN2077">B.2.1. Bugzilla Database Basics</H2
+NAME="AEN2152"
+></A
+>B.2.1. Bugzilla Database Basics</H2
><P
>If you were like me, at this point you're totally clueless about
the internals of MySQL, and if it weren't for this executive order from
><H3
CLASS="section"
><A
-NAME="AEN2104">B.2.1.1. Bugzilla Database Tables</H3
+NAME="AEN2179"
+></A
+>B.2.1.1. Bugzilla Database Tables</H3
><P
>Imagine your MySQL database as a series of spreadsheets, and
you won't be too far off. If you use this command:</P
><H1
CLASS="section"
><A
-NAME="dbschema">B.1. Database Schema Chart</H1
+NAME="dbschema"
+></A
+>B.1. Database Schema Chart</H1
><P
> <DIV
CLASS="mediaobject"
><H1
CLASS="section"
><A
-NAME="disclaimer">1.2. Disclaimer</H1
+NAME="disclaimer"
+></A
+>1.2. Disclaimer</H1
><P
> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
><H1
CLASS="section"
><A
-NAME="extraconfig">4.2. Optional Additional Configuration</H1
+NAME="extraconfig"
+></A
+>4.2. Optional Additional Configuration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN845">4.2.1. Dependency Charts</H2
+NAME="AEN845"
+></A
+>4.2.1. Dependency Charts</H2
><P
>As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
><H2
CLASS="section"
><A
-NAME="AEN860">4.2.2. Bug Graphs</H2
+NAME="AEN860"
+></A
+>4.2.2. Bug Graphs</H2
><P
>As long as you installed the GD and Graph::Base Perl modules you
might as well turn on the nifty Bugzilla bug reporting graphs.</P
><H2
CLASS="section"
><A
-NAME="AEN873">4.2.3. The Whining Cron</H2
+NAME="AEN873"
+></A
+>4.2.3. The Whining Cron</H2
><P
>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
><H2
CLASS="section"
><A
-NAME="bzldap">4.2.4. LDAP Authentication</H2
+NAME="bzldap"
+></A
+>4.2.4. LDAP Authentication</H2
><P
> <DIV
CLASS="warning"
><H2
CLASS="section"
><A
-NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
+NAME="content-type"
+></A
+>4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
><H2
CLASS="section"
><A
-NAME="htaccess">4.2.6. <TT
+NAME="htaccess"
+></A
+>4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
><H2
CLASS="section"
><A
-NAME="mod-throttle">4.2.7. <TT
+NAME="mod-throttle"
+></A
+>4.2.7. <TT
CLASS="filename"
>mod_throttle</TT
>
CLASS="appendix"
><H1
><A
-NAME="faq">Appendix A. The Bugzilla FAQ</H1
+NAME="faq"
+></A
+>Appendix A. The Bugzilla FAQ</H1
><P
> This FAQ includes questions not covered elsewhere in the Guide.
</P
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1649"
+HREF="faq.html#AEN1724"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1655"
+HREF="faq.html#AEN1730"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1661"
+HREF="faq.html#AEN1736"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1668"
+HREF="faq.html#AEN1743"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1693"
+HREF="faq.html#AEN1768"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1699"
+HREF="faq.html#AEN1774"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1705"
+HREF="faq.html#AEN1780"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1712"
+HREF="faq.html#AEN1787"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1717"
+HREF="faq.html#AEN1792"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1723"
+HREF="faq.html#AEN1798"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1733"
+HREF="faq.html#AEN1808"
> Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
-HREF="faq.html#AEN1738"
+HREF="faq.html#AEN1813"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1743"
+HREF="faq.html#AEN1818"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="faq.html#AEN1748"
+HREF="faq.html#AEN1823"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="faq.html#AEN1753"
+HREF="faq.html#AEN1828"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="faq.html#AEN1758"
+HREF="faq.html#AEN1833"
> Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values?
></DT
><DT
>A.2.7. <A
-HREF="faq.html#AEN1765"
+HREF="faq.html#AEN1840"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="faq.html#AEN1772"
+HREF="faq.html#AEN1847"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="faq.html#AEN1777"
+HREF="faq.html#AEN1852"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="faq.html#AEN1782"
+HREF="faq.html#AEN1857"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="faq.html#AEN1789"
+HREF="faq.html#AEN1864"
> Does Bugzilla allow data to be imported and exported? If I had outsiders
write up a bug report using a MS Word bug template, could that template be
imported into "matching" fields? If I wanted to take the results of a query
></DT
><DT
>A.2.12. <A
-HREF="faq.html#AEN1797"
+HREF="faq.html#AEN1872"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="faq.html#AEN1802"
+HREF="faq.html#AEN1877"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="faq.html#AEN1807"
+HREF="faq.html#AEN1882"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="faq.html#AEN1812"
+HREF="faq.html#AEN1887"
> Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use
or how are they notified?
></DT
><DT
>A.2.16. <A
-HREF="faq.html#AEN1817"
+HREF="faq.html#AEN1892"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="faq.html#AEN1823"
+HREF="faq.html#AEN1898"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="faq.html#AEN1828"
+HREF="faq.html#AEN1903"
> What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to
have? I need to find out if we were to go with Bugzilla, what types of
></DT
><DT
>A.2.19. <A
-HREF="faq.html#AEN1834"
+HREF="faq.html#AEN1909"
> What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to
install and a couple of hours per week to maintain and customize or is this
></DT
><DT
>A.2.20. <A
-HREF="faq.html#AEN1839"
+HREF="faq.html#AEN1914"
> Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
</A
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1846"
+HREF="faq.html#AEN1921"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide)?
</A
></DT
><DT
>A.3.2. <A
-HREF="faq.html#AEN1852"
+HREF="faq.html#AEN1927"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="faq.html#AEN1857"
+HREF="faq.html#AEN1932"
> I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly.
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1864"
+HREF="faq.html#AEN1939"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.4.2. <A
-HREF="faq.html#AEN1869"
+HREF="faq.html#AEN1944"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.4.3. <A
-HREF="faq.html#AEN1874"
+HREF="faq.html#AEN1949"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1880"
+HREF="faq.html#AEN1955"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="faq.html#AEN1887"
+HREF="faq.html#AEN1962"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1892"
+HREF="faq.html#AEN1967"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="faq.html#AEN1899"
+HREF="faq.html#AEN1974"
> How come email from Bugzilla changes never reaches me?
</A
></DT
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN1907"
+HREF="faq.html#AEN1982"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN1912"
+HREF="faq.html#AEN1987"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN1920"
+HREF="faq.html#AEN1995"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="faq.html#AEN1925"
+HREF="faq.html#AEN2000"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.5.5. <A
-HREF="faq.html#AEN1930"
+HREF="faq.html#AEN2005"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
>A.5.6. <A
-HREF="faq.html#AEN1935"
+HREF="faq.html#AEN2010"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN1944"
+HREF="faq.html#AEN2019"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="faq.html#AEN1949"
+HREF="faq.html#AEN2024"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN1954"
+HREF="faq.html#AEN2029"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="faq.html#AEN1962"
+HREF="faq.html#AEN2037"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN1983"
+HREF="faq.html#AEN2058"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="faq.html#AEN1988"
+HREF="faq.html#AEN2063"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="faq.html#AEN1993"
+HREF="faq.html#AEN2068"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.7.4. <A
-HREF="faq.html#AEN2003"
+HREF="faq.html#AEN2078"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="faq.html#AEN2008"
+HREF="faq.html#AEN2083"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.7.6. <A
-HREF="faq.html#AEN2013"
+HREF="faq.html#AEN2088"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN2020"
+HREF="faq.html#AEN2095"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN2029"
+HREF="faq.html#AEN2104"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN2035"
+HREF="faq.html#AEN2110"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
CLASS="qandadiv"
><H3
><A
-NAME="faq-general">1. General Questions</H3
+NAME="faq-general"
+></A
+>1. General Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1649"><B
+NAME="AEN1724"
+></A
+><B
>A.1.1. </B
>
Where can I find information about Bugzilla?</P
CLASS="question"
><P
><A
-NAME="AEN1655"><B
+NAME="AEN1730"
+></A
+><B
>A.1.2. </B
>
What license is Bugzilla distributed under?
CLASS="question"
><P
><A
-NAME="AEN1661"><B
+NAME="AEN1736"
+></A
+><B
>A.1.3. </B
>
How do I get commercial support for Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1668"><B
+NAME="AEN1743"
+></A
+><B
>A.1.4. </B
>
What major companies or projects are currently using Bugzilla
CLASS="question"
><P
><A
-NAME="AEN1693"><B
+NAME="AEN1768"
+></A
+><B
>A.1.5. </B
>
Who maintains Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1699"><B
+NAME="AEN1774"
+></A
+><B
>A.1.6. </B
>
How does Bugzilla stack up against other bug-tracking databases?
CLASS="question"
><P
><A
-NAME="AEN1705"><B
+NAME="AEN1780"
+></A
+><B
>A.1.7. </B
>
Why doesn't Bugzilla offer this or that feature or compatability
CLASS="question"
><P
><A
-NAME="AEN1712"><B
+NAME="AEN1787"
+></A
+><B
>A.1.8. </B
>
Why MySQL? I'm interested in seeing Bugzilla run on
CLASS="question"
><P
><A
-NAME="AEN1717"><B
+NAME="AEN1792"
+></A
+><B
>A.1.9. </B
>
Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
CLASS="question"
><P
><A
-NAME="AEN1723"><B
+NAME="AEN1798"
+></A
+><B
>A.1.10. </B
>
Is there an easy way to change the Bugzilla cookie name?
CLASS="qandadiv"
><H3
><A
-NAME="faq-phb">2. Managerial Questions</H3
+NAME="faq-phb"
+></A
+>2. Managerial Questions</H3
><P
> <DIV
CLASS="note"
CLASS="question"
><P
><A
-NAME="AEN1733"><B
+NAME="AEN1808"
+></A
+><B
>A.2.1. </B
>
Is Bugzilla web-based, or do you have to have specific software or
CLASS="question"
><P
><A
-NAME="AEN1738"><B
+NAME="AEN1813"
+></A
+><B
>A.2.2. </B
>
Can Bugzilla integrate with
CLASS="question"
><P
><A
-NAME="AEN1743"><B
+NAME="AEN1818"
+></A
+><B
>A.2.3. </B
>
Does Bugzilla allow the user to track multiple projects?
CLASS="question"
><P
><A
-NAME="AEN1748"><B
+NAME="AEN1823"
+></A
+><B
>A.2.4. </B
>
If I am on many projects, and search for all bugs assigned to me, will
CLASS="question"
><P
><A
-NAME="AEN1753"><B
+NAME="AEN1828"
+></A
+><B
>A.2.5. </B
>
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
CLASS="question"
><P
><A
-NAME="AEN1758"><B
+NAME="AEN1833"
+></A
+><B
>A.2.6. </B
>
Does Bugzilla allow us to define our own priorities and levels? Do we
CLASS="question"
><P
><A
-NAME="AEN1765"><B
+NAME="AEN1840"
+></A
+><B
>A.2.7. </B
>
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
CLASS="question"
><P
><A
-NAME="AEN1772"><B
+NAME="AEN1847"
+></A
+><B
>A.2.8. </B
>
Is there email notification and if so, what do you see when you get an
CLASS="question"
><P
><A
-NAME="AEN1777"><B
+NAME="AEN1852"
+></A
+><B
>A.2.9. </B
>
Can email notification be set up to send to multiple
CLASS="question"
><P
><A
-NAME="AEN1782"><B
+NAME="AEN1857"
+></A
+><B
>A.2.10. </B
>
Do users have to have any particular
CLASS="question"
><P
><A
-NAME="AEN1789"><B
+NAME="AEN1864"
+></A
+><B
>A.2.11. </B
>
Does Bugzilla allow data to be imported and exported? If I had outsiders
CLASS="question"
><P
><A
-NAME="AEN1797"><B
+NAME="AEN1872"
+></A
+><B
>A.2.12. </B
>
Has anyone converted Bugzilla to another language to be used in other
CLASS="question"
><P
><A
-NAME="AEN1802"><B
+NAME="AEN1877"
+></A
+><B
>A.2.13. </B
>
Can a user create and save reports? Can they do this in Word format?
CLASS="question"
><P
><A
-NAME="AEN1807"><B
+NAME="AEN1882"
+></A
+><B
>A.2.14. </B
>
Does Bugzilla have the ability to search by word, phrase, compound
CLASS="question"
><P
><A
-NAME="AEN1812"><B
+NAME="AEN1887"
+></A
+><B
>A.2.15. </B
>
Does Bugzilla provide record locking when there is simultaneous access
CLASS="question"
><P
><A
-NAME="AEN1817"><B
+NAME="AEN1892"
+></A
+><B
>A.2.16. </B
>
Are there any backup features provided?
CLASS="question"
><P
><A
-NAME="AEN1823"><B
+NAME="AEN1898"
+></A
+><B
>A.2.17. </B
>
Can users be on the system while a backup is in progress?
CLASS="question"
><P
><A
-NAME="AEN1828"><B
+NAME="AEN1903"
+></A
+><B
>A.2.18. </B
>
What type of human resources are needed to be on staff to install and
CLASS="question"
><P
><A
-NAME="AEN1834"><B
+NAME="AEN1909"
+></A
+><B
>A.2.19. </B
>
What time frame are we looking at if we decide to hire people to install
CLASS="question"
><P
><A
-NAME="AEN1839"><B
+NAME="AEN1914"
+></A
+><B
>A.2.20. </B
>
Is there any licensing fee or other fees for using Bugzilla? Any
CLASS="qandadiv"
><H3
><A
-NAME="faq-security">3. Bugzilla Security</H3
+NAME="faq-security"
+></A
+>3. Bugzilla Security</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1846"><B
+NAME="AEN1921"
+></A
+><B
>A.3.1. </B
>
How do I completely disable MySQL security if it's giving me problems
CLASS="question"
><P
><A
-NAME="AEN1852"><B
+NAME="AEN1927"
+></A
+><B
>A.3.2. </B
>
Are there any security problems with Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1857"><B
+NAME="AEN1932"
+></A
+><B
>A.3.3. </B
>
I've implemented the security fixes mentioned in Chris Yeh's security
CLASS="qandadiv"
><H3
><A
-NAME="faq-email">4. Bugzilla Email</H3
+NAME="faq-email"
+></A
+>4. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1864"><B
+NAME="AEN1939"
+></A
+><B
>A.4.1. </B
>
I have a user who doesn't want to receive any more email from Bugzilla.
CLASS="question"
><P
><A
-NAME="AEN1869"><B
+NAME="AEN1944"
+></A
+><B
>A.4.2. </B
>
I'm evaluating/testing Bugzilla, and don't want it to send email to
CLASS="question"
><P
><A
-NAME="AEN1874"><B
+NAME="AEN1949"
+></A
+><B
>A.4.3. </B
>
I want whineatnews.pl to whine at something more, or other than, only new
CLASS="question"
><P
><A
-NAME="AEN1880"><B
+NAME="AEN1955"
+></A
+><B
>A.4.4. </B
>
I don't like/want to use Procmail to hand mail off to bug_email.pl.
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1884"><BLOCKQUOTE
+NAME="AEN1959"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
CLASS="question"
><P
><A
-NAME="AEN1887"><B
+NAME="AEN1962"
+></A
+><B
>A.4.5. </B
>
How do I set up the email interface to submit/change bugs via email?
CLASS="question"
><P
><A
-NAME="AEN1892"><B
+NAME="AEN1967"
+></A
+><B
>A.4.6. </B
>
Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
CLASS="question"
><P
><A
-NAME="AEN1899"><B
+NAME="AEN1974"
+></A
+><B
>A.4.7. </B
>
How come email from Bugzilla changes never reaches me?
CLASS="qandadiv"
><H3
><A
-NAME="faq-db">5. Bugzilla Database</H3
+NAME="faq-db"
+></A
+>5. Bugzilla Database</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1907"><B
+NAME="AEN1982"
+></A
+><B
>A.5.1. </B
>
I've heard Bugzilla can be used with Oracle?
CLASS="question"
><P
><A
-NAME="AEN1912"><B
+NAME="AEN1987"
+></A
+><B
>A.5.2. </B
>
I think my database might be corrupted, or contain invalid entries. What
CLASS="question"
><P
><A
-NAME="AEN1920"><B
+NAME="AEN1995"
+></A
+><B
>A.5.3. </B
>
I want to manually edit some entries in my database. How?
CLASS="question"
><P
><A
-NAME="AEN1925"><B
+NAME="AEN2000"
+></A
+><B
>A.5.4. </B
>
I try to add myself as a user, but Bugzilla always tells me my password is wrong.
CLASS="question"
><P
><A
-NAME="AEN1930"><B
+NAME="AEN2005"
+></A
+><B
>A.5.5. </B
>
I think I've set up MySQL permissions correctly, but Bugzilla still can't
CLASS="question"
><P
><A
-NAME="AEN1935"><B
+NAME="AEN2010"
+></A
+><B
>A.5.6. </B
>
How do I synchronize bug information among multiple different Bugzilla
CLASS="qandadiv"
><H3
><A
-NAME="faq-nt">6. Bugzilla and Win32</H3
+NAME="faq-nt"
+></A
+>6. Bugzilla and Win32</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1944"><B
+NAME="AEN2019"
+></A
+><B
>A.6.1. </B
>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
CLASS="question"
><P
><A
-NAME="AEN1949"><B
+NAME="AEN2024"
+></A
+><B
>A.6.2. </B
>
Is there a "Bundle::Bugzilla" equivalent for Win32?
CLASS="question"
><P
><A
-NAME="AEN1954"><B
+NAME="AEN2029"
+></A
+><B
>A.6.3. </B
>
CGI's are failing with a "something.cgi is not a valid Windows NT
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1959"><BLOCKQUOTE
+NAME="AEN2034"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> "Set application mappings. In the ISM, map the extension for the script
CLASS="question"
><P
><A
-NAME="AEN1962"><B
+NAME="AEN2037"
+></A
+><B
>A.6.4. </B
>
I'm having trouble with the perl modules for NT not being able to talk to
CLASS="qandadiv"
><H3
><A
-NAME="faq-use">7. Bugzilla Usage</H3
+NAME="faq-use"
+></A
+>7. Bugzilla Usage</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1983"><B
+NAME="AEN2058"
+></A
+><B
>A.7.1. </B
>
How do I change my user name (email address) in Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1988"><B
+NAME="AEN2063"
+></A
+><B
>A.7.2. </B
>
The query page is very confusing. Isn't there a simpler way to query?
CLASS="question"
><P
><A
-NAME="AEN1993"><B
+NAME="AEN2068"
+></A
+><B
>A.7.3. </B
>
I'm confused by the behavior of the "accept" button in the Show Bug form.
CLASS="question"
><P
><A
-NAME="AEN2003"><B
+NAME="AEN2078"
+></A
+><B
>A.7.4. </B
>
I can't upload anything into the database via the "Create Attachment"
CLASS="question"
><P
><A
-NAME="AEN2008"><B
+NAME="AEN2083"
+></A
+><B
>A.7.5. </B
>
Email submissions to Bugzilla that have attachments end up asking me to
CLASS="question"
><P
><A
-NAME="AEN2013"><B
+NAME="AEN2088"
+></A
+><B
>A.7.6. </B
>
How do I change a keyword in Bugzilla, once some bugs are using it?
CLASS="qandadiv"
><H3
><A
-NAME="faq-hacking">8. Bugzilla Hacking</H3
+NAME="faq-hacking"
+></A
+>8. Bugzilla Hacking</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN2020"><B
+NAME="AEN2095"
+></A
+><B
>A.8.1. </B
>
What bugs are in Bugzilla right now?
CLASS="question"
><P
><A
-NAME="AEN2029"><B
+NAME="AEN2104"
+></A
+><B
>A.8.2. </B
>
How can I change the default priority to a null value? For instance, have the default
CLASS="question"
><P
><A
-NAME="AEN2035"><B
+NAME="AEN2110"
+></A
+><B
>A.8.3. </B
>
What's the best way to submit patches? What guidelines should I follow?
CLASS="GLOSSARY"
><H1
><A
-NAME="glossary">Glossary</H1
+NAME="glossary"
+></A
+>Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2183">0-9, high ascii</H1
+NAME="AEN2258"
+></A
+>0-9, high ascii</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-a">A</H1
+NAME="gloss-a"
+></A
+>A</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-b">B</H1
+NAME="gloss-b"
+></A
+>B</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-c"></H1
+NAME="gloss-c"
+></A
+></H1
><DL
><DT
><A
-NAME="gloss-component"><B
+NAME="gloss-component"
+></A
+><B
>Component</B
></DT
><DD
></DD
><DT
><A
-NAME="gloss-cpan"><B
+NAME="gloss-cpan"
+></A
+><B
> <SPAN
CLASS="acronym"
>CPAN</SPAN
><H1
CLASS="glossdiv"
><A
-NAME="gloss-d">D</H1
+NAME="gloss-d"
+></A
+>D</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-g"></H1
+NAME="gloss-g"
+></A
+></H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-m">M</H1
+NAME="gloss-m"
+></A
+>M</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-p">P</H1
+NAME="gloss-p"
+></A
+>P</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-q">Q</H1
+NAME="gloss-q"
+></A
+>Q</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-s">S</H1
+NAME="gloss-s"
+></A
+>S</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-t">T</H1
+NAME="gloss-t"
+></A
+>T</H1
><DL
><DT
><A
-NAME="gloss-target-milestone"><B
+NAME="gloss-target-milestone"
+></A
+><B
>Target Milestone</B
></DT
><DD
><H1
CLASS="glossdiv"
><A
-NAME="gloss-z">Z</H1
+NAME="gloss-z"
+></A
+>Z</H1
><DL
><DT
><A
-NAME="zarro-boogs-found"><B
+NAME="zarro-boogs-found"
+></A
+><B
>Zarro Boogs Found</B
></DT
><DD
><H1
CLASS="section"
><A
-NAME="groups">5.5. Groups and Group Security</H1
+NAME="groups"
+></A
+>5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
><H1
CLASS="section"
><A
-NAME="hintsandtips">3.2. Hints and Tips</H1
+NAME="hintsandtips"
+></A
+>3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
><H2
CLASS="section"
><A
-NAME="AEN434">3.2.1. Autolinkification</H2
+NAME="AEN434"
+></A
+>3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
><H2
CLASS="section"
><A
-NAME="quicksearch">3.2.2. Quicksearch</H2
+NAME="quicksearch"
+></A
+>3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
><H2
CLASS="section"
><A
-NAME="commenting">3.2.3. Comments</H2
+NAME="commenting"
+></A
+>3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
><H2
CLASS="section"
><A
-NAME="attachments">3.2.4. Attachments</H2
+NAME="attachments"
+></A
+>3.2.4. Attachments</H2
><P
> Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
><H2
CLASS="section"
><A
-NAME="AEN463">3.2.5. Filing Bugs</H2
+NAME="AEN463"
+></A
+>3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
><H1
CLASS="section"
><A
-NAME="how">3.1. How do I use Bugzilla?</H1
+NAME="how"
+></A
+>3.1. How do I use Bugzilla?</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
><H2
CLASS="section"
><A
-NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount"
+></A
+>3.1.1. Create a Bugzilla Account</H2
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
><H2
CLASS="section"
><A
-NAME="bug_page">3.1.2. Anatomy of a Bug</H2
+NAME="bug_page"
+></A
+>3.1.2. Anatomy of a Bug</H2
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
><H2
CLASS="section"
><A
-NAME="query">3.1.3. Searching for Bugs</H2
+NAME="query"
+></A
+>3.1.3. Searching for Bugs</H2
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
><H2
CLASS="section"
><A
-NAME="list">3.1.4. Bug Lists</H2
+NAME="list"
+></A
+>3.1.4. Bug Lists</H2
><P
>If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system - don't try
><H2
CLASS="section"
><A
-NAME="bugreports">3.1.5. Filing Bugs</H2
+NAME="bugreports"
+></A
+>3.1.5. Filing Bugs</H2
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
CLASS="chapter"
><H1
><A
-NAME="installation">Chapter 4. Installation</H1
+NAME="installation"
+></A
+>Chapter 4. Installation</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
+NAME="integration"
+></A
+>5.9. Integrating Bugzilla with Third-Party Tools</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="bonsai">5.9.1. Bonsai</H2
+NAME="bonsai"
+></A
+>5.9.1. Bonsai</H2
><P
>Bonsai is a web-based tool for managing
<A
><H2
CLASS="section"
><A
-NAME="cvs">5.9.2. CVS</H2
+NAME="cvs"
+></A
+>5.9.2. CVS</H2
><P
>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.</P
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
><P
>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
><H2
CLASS="section"
><A
-NAME="scm">5.9.3. Perforce SCM</H2
+NAME="scm"
+></A
+>5.9.3. Perforce SCM</H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
><H2
CLASS="section"
><A
-NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
+NAME="tinderbox"
+></A
+>5.9.4. Tinderbox/Tinderbox2</H2
><P
>We need Tinderbox integration information.</P
></DIV
CLASS="chapter"
><H1
><A
-NAME="introduction">Chapter 2. Introduction</H1
+NAME="introduction"
+></A
+>Chapter 2. Introduction</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="newversions">1.3. New Versions</H1
+NAME="newversions"
+></A
+>1.3. New Versions</H1
><P
> This is the 2.16 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. If you are
><H1
CLASS="section"
><A
-NAME="osx">4.4. Mac OS X Installation Notes</H1
+NAME="osx"
+></A
+>4.4. Mac OS X Installation Notes</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
><H1
CLASS="section"
><A
-NAME="parameters">5.1. Bugzilla Configuration</H1
+NAME="parameters"
+></A
+>5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
CLASS="appendix"
><H1
><A
-NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
+NAME="patches"
+></A
+>Appendix C. Useful Patches and Utilities for Bugzilla</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
+NAME="programadmin"
+></A
+>5.3. Product, Component, Milestone, and Version Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="products">5.3.1. Products</H2
+NAME="products"
+></A
+>5.3.1. Products</H2
><P
> <A
HREF="glossary.html#gloss-product"
><H2
CLASS="section"
><A
-NAME="components">5.3.2. Components</H2
+NAME="components"
+></A
+>5.3.2. Components</H2
><P
>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
><H2
CLASS="section"
><A
-NAME="versions">5.3.3. Versions</H2
+NAME="versions"
+></A
+>5.3.3. Versions</H2
><P
>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
><H2
CLASS="section"
><A
-NAME="milestones">5.3.4. Milestones</H2
+NAME="milestones"
+></A
+>5.3.4. Milestones</H2
><P
>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 release, it
><H1
CLASS="section"
><A
-NAME="rewrite">C.1. Apache
+NAME="rewrite"
+></A
+>C.1. Apache
<TT
CLASS="filename"
>mod_rewrite</TT
><H1
CLASS="section"
><A
-NAME="rhbugzilla">D.1. Red Hat Bugzilla</H1
+NAME="rhbugzilla"
+></A
+>D.1. Red Hat Bugzilla</H1
><P
>Red Hat Bugzilla is a fork of Bugzilla 2.8.
One of its major benefits is the ability
><H1
CLASS="section"
><A
-NAME="security">5.6. Bugzilla Security</H1
+NAME="security"
+></A
+>5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
><H1
CLASS="section"
><A
-NAME="stepbystep">4.1. Step-by-step Install</H1
+NAME="stepbystep"
+></A
+>4.1. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN492">4.1.1. Introduction</H2
+NAME="AEN492"
+></A
+>4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
><H2
CLASS="section"
><A
-NAME="AEN496">4.1.2. Package List</H2
+NAME="AEN496"
+></A
+>4.1.2. Package List</H2
><DIV
CLASS="note"
><P
><H2
CLASS="section"
><A
-NAME="install-mysql">4.1.3. MySQL</H2
+NAME="install-mysql"
+></A
+>4.1.3. MySQL</H2
><P
>Visit the MySQL homepage at
<A
><H2
CLASS="section"
><A
-NAME="install-perl">4.1.4. Perl</H2
+NAME="install-perl"
+></A
+>4.1.4. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
><DIV
CLASS="tip"
><A
-NAME="bundlebugzilla"><P
+NAME="bundlebugzilla"
+></A
+><P
></P
><TABLE
CLASS="tip"
><H2
CLASS="section"
><A
-NAME="perl-modules">4.1.5. Perl Modules</H2
+NAME="perl-modules"
+></A
+>4.1.5. Perl Modules</H2
><P
>
All Perl modules can be found on the
><H3
CLASS="section"
><A
-NAME="AEN642">4.1.5.1. DBI</H3
+NAME="AEN642"
+></A
+>4.1.5.1. DBI</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
><H3
CLASS="section"
><A
-NAME="AEN645">4.1.5.2. Data::Dumper</H3
+NAME="AEN645"
+></A
+>4.1.5.2. Data::Dumper</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
><H3
CLASS="section"
><A
-NAME="AEN648">4.1.5.3. MySQL-related modules</H3
+NAME="AEN648"
+></A
+>4.1.5.3. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
><H3
CLASS="section"
><A
-NAME="AEN653">4.1.5.4. TimeDate modules</H3
+NAME="AEN653"
+></A
+>4.1.5.4. TimeDate modules</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
><H3
CLASS="section"
><A
-NAME="AEN656">4.1.5.5. GD (optional)</H3
+NAME="AEN656"
+></A
+>4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
><H3
CLASS="section"
><A
-NAME="AEN663">4.1.5.6. Chart::Base (optional)</H3
+NAME="AEN663"
+></A
+>4.1.5.6. Chart::Base (optional)</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
><H3
CLASS="section"
><A
-NAME="AEN666">4.1.5.7. Template Toolkit</H3
+NAME="AEN666"
+></A
+>4.1.5.7. Template Toolkit</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
><H2
CLASS="section"
><A
-NAME="AEN669">4.1.6. HTTP Server</H2
+NAME="AEN669"
+></A
+>4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
COLOR="#000000"
><PRE
CLASS="programlisting"
->Options ExecCGI<br>AllowOverride Limit</PRE
+> Options ExecCGI
+AllowOverride Limit
+ </PRE
></FONT
></TD
></TR
><H2
CLASS="section"
><A
-NAME="AEN688">4.1.7. Bugzilla</H2
+NAME="AEN688"
+></A
+>4.1.7. Bugzilla</H2
><P
>You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
><H2
CLASS="section"
><A
-NAME="AEN705">4.1.8. Setting Up the MySQL Database</H2
+NAME="AEN705"
+></A
+>4.1.8. Setting Up the MySQL Database</H2
><P
>After you've gotten all the software installed and working you're
ready to start preparing the database for its life as the back end to
><H2
CLASS="section"
><A
-NAME="AEN741">4.1.9. <TT
+NAME="AEN741"
+></A
+>4.1.9. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><H2
CLASS="section"
><A
-NAME="AEN773">4.1.10. Securing MySQL</H2
+NAME="AEN773"
+></A
+>4.1.10. Securing MySQL</H2
><P
>If you followed the installation instructions for setting up your
"bugs" and "root" user in MySQL, much of this should not apply to you.
><H2
CLASS="section"
><A
-NAME="AEN839">4.1.11. Configuring Bugzilla</H2
+NAME="AEN839"
+></A
+>4.1.11. Configuring Bugzilla</H2
><P
> You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
></DIV
></BODY
></HTML
->
+>
\ No newline at end of file
><H1
CLASS="section"
><A
-NAME="troubleshooting">4.5. Troubleshooting</H1
+NAME="troubleshooting"
+></A
+>4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
><H2
CLASS="section"
><A
-NAME="AEN1218">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+NAME="AEN1218"
+></A
+>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
> Try executing <B
CLASS="command"
><H2
CLASS="section"
><A
-NAME="AEN1223">4.5.2. DBD::Sponge::db prepare failed</H2
+NAME="AEN1223"
+></A
+>4.5.2. DBD::Sponge::db prepare failed</H2
><P
> The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
><H2
CLASS="section"
><A
-NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
+NAME="paranoid-security"
+></A
+>4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
distributions with
><H1
CLASS="section"
><A
-NAME="useradmin">5.2. User Administration</H1
+NAME="useradmin"
+></A
+>5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="defaultuser">5.2.1. Creating the Default User</H2
+NAME="defaultuser"
+></A
+>5.2.1. Creating the Default User</H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
><H2
CLASS="section"
><A
-NAME="manageusers">5.2.2. Managing Other Users</H2
+NAME="manageusers"
+></A
+>5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
-NAME="createnewusers">5.2.2.1. Creating new users</H3
+NAME="createnewusers"
+></A
+>5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
><H3
CLASS="section"
><A
-NAME="modifyusers">5.2.2.2. Modifying Users</H3
+NAME="modifyusers"
+></A
+>5.2.2.2. Modifying Users</H3
><P
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
><H1
CLASS="section"
><A
-NAME="userpreferences">3.3. User Preferences</H1
+NAME="userpreferences"
+></A
+>3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
><H2
CLASS="section"
><A
-NAME="accountsettings">3.3.1. Account Settings</H2
+NAME="accountsettings"
+></A
+>3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
><H2
CLASS="section"
><A
-NAME="emailsettings">3.3.2. Email Settings</H2
+NAME="emailsettings"
+></A
+>3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
><H2
CLASS="section"
><A
-NAME="footersettings">3.3.3. Page Footer</H2
+NAME="footersettings"
+></A
+>3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
><H2
CLASS="section"
><A
-NAME="permissionsettings">3.3.4. Permissions</H2
+NAME="permissionsettings"
+></A
+>3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
CLASS="chapter"
><H1
><A
-NAME="using">Chapter 3. Using Bugzilla</H1
+NAME="using"
+></A
+>Chapter 3. Using Bugzilla</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
+NAME="variant-fenris"
+></A
+>D.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
><H1
CLASS="section"
><A
-NAME="variant-issuezilla">D.3. Issuezilla</H1
+NAME="variant-issuezilla"
+></A
+>D.3. Issuezilla</H1
><P
>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
><H1
CLASS="section"
><A
-NAME="variant-perforce">D.5. Perforce SCM</H1
+NAME="variant-perforce"
+></A
+>D.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used as
such through the <SPAN
><H1
CLASS="section"
><A
-NAME="variant-scarab">D.4. Scarab</H1
+NAME="variant-scarab"
+></A
+>D.4. Scarab</H1
><P
>Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.</P
><H1
CLASS="section"
><A
-NAME="variant-sourceforge">D.6. SourceForge</H1
+NAME="variant-sourceforge"
+></A
+>D.6. SourceForge</H1
><P
>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
CLASS="appendix"
><H1
><A
-NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
+NAME="variants"
+></A
+>Appendix D. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
><H1
CLASS="section"
><A
-NAME="voting">5.4. Voting</H1
+NAME="voting"
+></A
+>5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
><H1
CLASS="section"
><A
-NAME="whatis">2.1. What is Bugzilla?</H1
+NAME="whatis"
+></A
+>2.1. What is Bugzilla?</H1
><P
> Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
><H1
CLASS="section"
><A
-NAME="why">2.2. Why Should We Use Bugzilla?</H1
+NAME="why"
+></A
+>2.2. Why Should We Use Bugzilla?</H1
><P
>For many years, defect-tracking software has remained principally
the domain of large software development houses. Even then, most shops
><H1
CLASS="section"
><A
-NAME="win32">4.3. Win32 Installation Notes</H1
+NAME="win32"
+></A
+>4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
><H2
CLASS="section"
><A
-NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2
+NAME="wininstall"
+></A
+>4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
><DIV
CLASS="example"
><A
-NAME="AEN989"><P
+NAME="AEN989"
+></A
+><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
<DIV
CLASS="example"
><A
-NAME="AEN1002"><P
+NAME="AEN1002"
+></A
+><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
><H2
CLASS="section"
><A
-NAME="addlwintips">4.3.2. Additional Windows Tips</H2
+NAME="addlwintips"
+></A
+>4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
><P
>From Andrew Pearson:
<A
-NAME="AEN1172"><BLOCKQUOTE
+NAME="AEN1172"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
<DIV
CLASS="example"
><A
-NAME="AEN1184"><P
+NAME="AEN1184"
+></A
+><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</para>
+ you want to have the bug be closed automatically, you'll have to modify
+ the <filename>contrib/bugzilla_email_append.pl</filename> script.
+ </para>
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
With Apache you'll also want to make sure that within the httpd.conf
file the line:
- Options ExecCGI
- AllowOverride Limit
+Options ExecCGI
+AllowOverride Limit
is in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
Follow the instructions in this Guide for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to your
Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
- have CVS check-in comments append to your Bugzilla bug. If you have
- your check-in script include an @resolution field, you can even change
- the Bugzilla bug state.
+ have CVS check-in comments append to your Bugzilla bug. If you want to
+ have the bug be closed automatically, you'll have to modify the
+ contrib/bugzilla_email_append.pl script.
There is also a CVSZilla project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to email.
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</para>
+ you want to have the bug be closed automatically, you'll have to modify
+ the <filename>contrib/bugzilla_email_append.pl</filename> script.
+ </para>
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
projects / thirdparty / bugzilla.git / commitdiff
