Skip to content

bugzilla
bugzilla
Commit 2d4d7c92 authored by barnboy%trilobyte.net's avatar barnboy%trilobyte.net
Browse files
Options

Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242.

The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove.
parent 064f6ba6
Hide whitespace changes
Inline Side-by-side
Showing with 10107 additions and 2119 deletions
README
View file @ 2d4d7c92
This is Bugzilla. See <http://www.mozilla.org/bugs/>.
=====================
BUGZILLA 2.12 RELEASE
=====================
* Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt.
* The new preferred documentation for Bugzilla is available in docs/, with
a variety of document types available. Please refer to these documents when
installing, configuring, and maintaining your Bugzilla installation. The majority
of the contents of this file is now considered to be largely deprecated and will
go away in the 2.14 release.
==========
DISCLAIMER
==========
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
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
of third-party utilities. To install Bugzilla on Win32 requires
fair Perl proficiency, and if you use a webserver other than Apache you
should be intimately familiar with the security mechanisms and CGI
environment thereof.
Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.
===========
CONVENTIONS
===========
Throughout this README and "The Bugzilla Guide" in the docs/ folder,
we use some writing conventions. Bourne shell prompts are used
generically to indicate any shell.
File Names file.extension
Directory Names directory/
Commands to be typed <shell> command
Prompt of user command under bash shell: bash$
Prompt of root user command under bash shell: bash#
Prompt of user command under tcsh shell: tcsh$
Environment Variables VARIABLE
Emphasized word *word*
============
INSTALLATION
============
0. Introduction
Installation of bugzilla is pretty straightforward, particularly if your
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
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.
Bugzilla has been successfully installed under Solaris, Linux, and
Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
included in this README; please consult the Bugzilla Guide for more
detailed Win32 installation instructions.
The Bugzilla Guide is contained in the "docs/" folder. It is available
in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
1. Installing the Prerequisites
The software packages necessary for the proper running of bugzilla are:
1. MySQL database server and the mysql client (3.22.5 or greater)
2. Perl (5.004 or greater)
3. DBI Perl module
4. Data::Dumper Perl module
5. DBD::mySQL
6. TimeDate Perl module collection
7. GD perl module (1.8.3) (optional, for bug charting)
8. Chart::Base Perl module (0.99c) (optional, for bug charting)
9. DB_File Perl module (optional, for bug charting)
10. The web server of your choice. Apache is recommended.
For the contrib/bug_email.pl interface, you also need:
11. MIME::Parser Perl module
You must also run Bugzilla on a filesystem that supports file locking via
flock(). This is necessary for Bugzilla to operate safely with multiple
instances.
It is a good idea, while installing Bugzilla, to ensure it is not
accessible from the Internet. The machine may be vulnerable to attacks
while you are installing.
1.1. Getting and setting up MySQL database (3.22.5 or greater)
Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
release of the server. Both binaries and source are available and which
you get shouldn't matter. Be aware that many of the binary versions
of MySQL store their data files in /var which on many installations
(particularly common with linux installations) is part of a smaller
root partition. If you decide to build from sources you can easily set
the dataDir as an option to configure.
If you've installed from source or non-package (RPM, deb, etc.) binaries
you'll want to make sure to add mysqld to your init scripts so the server
daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that
mysqld will accept large packets. By default, mysqld is set up to only
accept packets up to 64K long. This limits the size of attachments you
may put on bugs. If you add something like "-O max_allowed_packet=1M"
to the command that starts mysqld (or safe_mysqld), then you will be
able to have attachments up to about 1 megabyte.
If you plan on running Bugzilla and MySQL on the same machine,
consider using the "--skip-networking" option in the init script.
This enhances security by preventing network access to MySQL.
1.2. Perl (5.004 or greater)
Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from http://www.perl.com.
Perl is now a far cry from the the single compiler/interpreter binary it
once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
SHORTCUT: You can skip the following Perl module installation
steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
All Perl module installation steps require you have an active Internet
connection.
bash# perl -MCPAN -e 'install "Bundle::Bugzilla"'
Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
which are not essential to a basic Bugzilla install. If installing
this bundle fails, you should install each module individually to
isolate the problem.
1.3. DBI Perl module
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
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
MakeMaker system simplifies the C compilation greatly.
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
real tendency to bog down, so please use mirrors. The current location
at the time of this writing (02/17/99) can be found in Appendix A.
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
which does all the hard work for you.
To use the CPAN shell to install DBI:
bash# perl -MCPAN -e 'install "DBI"'
(replace DBI with the name of the module you wish to install, Data::Dumper,
etc...)
To do it the hard way:
1. Untar the module tarball -- it should create its own directory
2. Enter the following commands:
perl Makefile.PL
make
make test
make install
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
1.4 Data::Dumper Perl module
The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
1.5. MySQL related Perl module collection
The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN (link
in Appendix A). After the archive file has been downloaded it should
be untarred.
The MySQL modules are all build using one make file which is generated
by running:
perl Makefile.PL
The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
1.6. TimeDate Perl module collection
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of them
is probably a good idea anyway. The standard Perl module installation
instructions should work perfectly for this simple package.
1.7. GD Perl module (1.8.3)
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to generate
graphs on the fly. That's what bugzilla will be using it for so you'd
better install it if you want any of the graphing to work.
Actually bugzilla uses the Graph module which relies on GD itself,
but isn't that always the way with OOP. At any rate, you can find the
GD library on CPAN (link in Appendix A).
The latest version of the GD library can be found at:
http://www.boutell.com/gd/
1.8. Chart::Base Perl module (0.99c)
The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
fetched from CPAN where it is found as the Chart-x.x... tarball in a
directory to be listed in Appendix A. Note that as with the GD perl
module, only the specific versions listed above will work. Earlier
versions used GIF's, which are no longer supported by the latest
versions of GD.
1.9. DB_File Perl module
DB_File is a module which allows Perl programs to make use of the facilities provided by
Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
bug charting. If you plan to make use of bug charting, you must install this module.
1.10. HTTP server
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a different
machine than MySQL, but need to adjust the MySQL "bugs" user permissions
accordingly.
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. If you're using
apache that means uncommenting the following line in the srm.conf file:
AddHandler cgi-script .cgi
With apache you'll also want to make sure that within the access.conf
file the line:
Options ExecCGI
is in the stanza that covers the directories you intend to put the
bugzilla .html and .cgi files into.
If you are using a newer version of Apache, both of the above lines will be
(or will need to be) in the httpd.conf file, rather than srm.conf or
access.conf.
There are two critical directories and a file that should not be a served by
the HTTP server. These are the 'data' and 'shadow' directories and the
'localconfig' file. You should configure your HTTP server to not serve
content from these files. Failure to do so will expose critical passwords
and other data. Please see your HTTP server configuration manual on how
to do this. If you use quips (at the top of the buglist pages) you will want
the 'data/comments' file to still be served. This file contains those quips.
2. Installing the Bugzilla Files
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directories if they were accidentally tarred up with the rest of Bugzilla)
and make sure you can access the files in that directory through your
web server.
HINT: If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive "Forbidden" errors unless you
add the "FollowSymLinks" directive to the <Directory> entry
for the HTML root.
* This README is no longer used to house installation instructions. Instead,
it contains pointers to where you may find the information you need.
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable). This is a temporary step until you run
the post-install "checksetup.pl" script, which locks down your
installation.
Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
to the correct location of your perl executable (probably /usr/bin/perl).
Otherwise you must hack all the .cgi files to change where they look
for perl. To make future upgrades easier, you should use the symlink
approach.
3. Setting Up the MySQL database
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
quality bug tracker.
First, you'll want to fix MySQL permissions to allow access from
Bugzilla. For the purpose of this README, the Bugzilla username
will be "bugs", and will have minimal permissions. Bugzilla has
not undergone a thorough security audit. It may be possible for
a system cracker to somehow trick Bugzilla into executing a command
such as "; DROP DATABASE mysql".
That would be bad.
Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
bash$ mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
mysql> FLUSH PRIVILEGES;
From this point on, if you need to access MySQL as the
MySQL root user, you will need to use "mysql -u root -p" and
enter your new_password. Remember that MySQL user names have
nothing to do with Unix user names (login names).
Next, we create the "bugs" user, and grant sufficient
permissions for checksetup.pl, which we'll use later, to work
its magic. This also restricts the "bugs" user to operations
within a database called "bugs", and only allows the account
to connect from "localhost". Modify it to reflect your setup
if you will be connecting from another machine or as a different
user.
Remember to set bugs_password to some unique password.
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
IDENTIFIED BY 'bugs_password';
mysql> FLUSH PRIVILEGES;
Next, run the magic checksetup.pl script. (Many thanks to Holger
Schurig <holgerschurig@nikocity.de> for writing this script!)
It will make sure Bugzilla files and directories have reasonable
permissions, set up the "data" directory, and create all the MySQL
tables.
bash$ ./checksetup.pl
The first time you run it, it will create a file called "localconfig".
4. Tweaking localconfig
This file contains a variety of settings you may need to tweak including
how Bugzilla should connect to the MySQL database.
The connection settings include:
1. server's host: just use "localhost" if the MySQL server is
local
2. database name: "bugs" if you're following these directions
3. MySQL username: "bugs" if you're following these directions
4. Password for the "bugs" MySQL account in item 3.
Once you are happy with the settings, re-run checksetup.pl. On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
When logged into an administrator account once Bugzilla is running,
if you go to the query page (off of the bugzilla main menu), you'll
find an 'edit parameters' option that is filled with editable treats.
Should everything work, you should have a nearly empty copy of the bug
tracking setup.
The second time around, checksetup.pl will stall if it is on a
filesystem that does not fully support file locking via flock(), such as
NFS mounts. This support is required for Bugzilla to operate safely with
multiple instances. If flock() is not fully supported, it will stall at:
"Now regenerating the shadow database for all bugs."
The checksetup.pl script is designed so that you can run it at any time
without causing harm. You should run it after any upgrade to Bugzilla.
5. Setting Up Maintainers Manually (Optional)
If you want to add someone else to every group by hand, you can do it
by typing the appropriate MySQL commands. Run 'mysql -u root -p bugs'
(you may need different parameters, depending on your security settings
according to section 3, above). Then:
mysql> update profiles set groupset=0x7fffffffffffffff
where login_name = 'XXX';
replacing XXX with the Bugzilla email address.
6. Setting Up the Whining Cron Job (Optional)
By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see that
crontab man page):
cd <your-bugzilla-directory> ; ./whineatnews.pl
7. Bug Graphs (Optional)
As long as you installed the GD and Graph::Base Perl modules you might
as well turn on the nifty bugzilla bug reporting graphs.
bash# crontab -e
Adding this entry runs collectstats daily at 5 after midnight:
5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
8. Real security for MySQL
If you followed the README for setting up your "bugs" and "root" user in
MySQL, much of this should not apply to you. If you are upgrading
an existing installation of Bugzilla, you should pay close attention
to this section.
MySQL has "interesting" default security parameters:
mysqld defaults to running as root
it defaults to allowing external network connections
it has a known port number, and is easy to detect
it defaults to no passwords whatsoever
it defaults to allowing "File_Priv"
This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the system.
To see your permissions do:
> mysql -u root -p
use mysql;
show tables;
select * from user;
select * from db;
To fix the gaping holes:
DELETE FROM user WHERE User='';
UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
FLUSH PRIVILEGES;
If you're not running "mit-pthreads" you can use:
GRANT USAGE ON *.* TO bugs@localhost;
GRANT ALL ON bugs.* TO bugs@localhost;
REVOKE DROP ON bugs.* FROM bugs@localhost;
FLUSH PRIVILEGES;
With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
GRANT USAGE ON *.* TO bugs@bounce.hop.com;
GRANT ALL ON bugs.* TO bugs@bounce.hop.com;
REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;
FLUSH PRIVILEGES;
Consider also:
o Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
o using the --user= option to mysqld to run it as an unprivileged
user.
o starting MySQL in a chroot jail
o running the httpd in a jail
o making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
o running MySQL on a separate untrusted machine
o making backups ;-)
---------[ Appendices ]-----------------------
Appendix A. Required Software Download Links
All of these sites are current as of February 17, 1999. Hopefully
they'll stay current for a while.
MySQL: http://www.mysql.org
Perl: http://www.perl.org
CPAN: http://www.cpan.org
DBI Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
Data::Dumper module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
MySQL related Perl modules:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
TimeDate Perl module collection:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
Chart::Base module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
Appendix B. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory (we said before it needs to be writable,
right?!)
If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't show
up!
That file gets automatically regenerated whenever it's more than an
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.
Appendix C. Upgrading from previous versions of Bugzilla
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
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
changed, you can read the comments in that file, starting from the end.
Appendix D. History
This document was originally adapted from the Bonsai installation
instructions by Terry Weissman <terry@mozilla.org>.
The February 25, 1999 re-write of this page was done by Ry4an Brase
<ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, & Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
* Installation instructions are now found in docs/, with a variety of document
types available. Please refer to these documents when installing, configuring,
and maintaining your Bugzilla installation. A helpful starting point is
docs/txt/Bugzilla-Guide.txt, or with a web browser at docs/html/index.html.
* Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt.
Comments from people using this document for the first time are
especially welcomed.
* If you wish to contribute to the documentation, please read docs/README.docs.
docs/html/Bugzilla-Guide.html
View file @ 2d4d7c92
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/html/about.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>About This Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/aboutthisguide.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Purpose and Scope of this Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/administration.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Administering Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -98,6 +98,30 @@ HREF="useradmin.html#DEFAULTUSER"
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>3.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
>3.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
>3.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
>3.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -152,7 +176,7 @@ COLOR="RED"
><P
>So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</P
></DIV
><DIV
......
docs/html/bonsai.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bonsai</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/bugprobs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bug Issues</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/bz30.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bugzilla 3.0</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/cleanupwork.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Cleaning up after mucking with Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
TITLE="Bugzilla Variants"
HREF="variants.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
......@@ -51,13 +51,13 @@ HREF="granttables.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
HREF="variants.html"
>Next</A
></TD
></TR
......@@ -71,11 +71,11 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CLEANUPWORK"
>B.4. Cleaning up after mucking with Bugzilla</A
>C.4. Cleaning up after mucking with Bugzilla</A
></H1
><P
CLASS="LITERALLAYOUT"
>Contributed&nbsp;by&nbsp;Eric&nbsp;Hansen:<br>
>Contributed&nbsp;by&nbsp;Eric&nbsp;Hanson:<br>
There&nbsp;are&nbsp;several&nbsp;things,&nbsp;and&nbsp;one&nbsp;trick.&nbsp;&nbsp;There&nbsp;is&nbsp;a&nbsp;small&nbsp;tiny&nbsp;piece&nbsp;of<br>
documentation&nbsp;I&nbsp;saw&nbsp;once&nbsp;that&nbsp;said&nbsp;something&nbsp;very&nbsp;important.<br>
1)&nbsp;&nbsp;After&nbsp;pretty&nbsp;much&nbsp;any&nbsp;manual&nbsp;working&nbsp;of&nbsp;the&nbsp;Mysql&nbsp;db,&nbsp;you&nbsp;must<br>
......@@ -124,7 +124,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
HREF="variants.html"
>Next</A
></TD
></TR
......@@ -146,7 +146,7 @@ HREF="database.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
>Bugzilla Variants</TD
></TR
></TABLE
></DIV
......
docs/html/cmdline.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Command-line Bugzilla Queries</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -13,7 +13,7 @@ REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="The setperl.pl Utility"
TITLE="The setperl.csh Utility"
HREF="setperl.html"><LINK
REL="NEXT"
TITLE="The Quicksearch Utility"
......@@ -51,7 +51,7 @@ HREF="setperl.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CMDLINE"
>C.2. Command-line Bugzilla Queries</A
>D.2. Command-line Bugzilla Queries</A
></H1
><P
> Users can query Bugzilla from the command line using
......@@ -240,7 +240,7 @@ HREF="quicksearch.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The setperl.pl Utility</TD
>The setperl.csh Utility</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/contributors.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Contributors</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,10 +74,15 @@ NAME="CONTRIBUTORS"
>1.6. Contributors</A
></H1
><P
> Thanks go to these people for significant contributions to this documentation:
> Thanks go to these people for significant contributions
to this documentation (in no particular order):
</P
><P
> Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
> Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</P
></DIV
><DIV
......
docs/html/conventions.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Document Conventions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -79,7 +79,7 @@ NAME="CONVENTIONS"
><DIV
CLASS="INFORMALTABLE"
><A
NAME="AEN111"
NAME="AEN117"
></A
><P
></P
......
docs/html/copyright.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Copyright Information</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,7 +74,7 @@ NAME="COPYRIGHT"
>1.2. Copyright Information</A
></H1
><A
NAME="AEN51"
NAME="AEN57"
></A
><TABLE
BORDER="0"
......
docs/html/credits.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Credits</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/cvs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>CVS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/database.html
View file @ 2d4d7c92
......@@ -4,14 +4,14 @@
>The Bugzilla Database</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
TITLE="Software Download Links"
HREF="downloadlinks.html"><LINK
REL="NEXT"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
......@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="faq.html"
HREF="downloadlinks.html"
>Prev</A
></TD
><TD
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="DATABASE"
>Appendix B. The Bugzilla Database</A
>Appendix C. The Bugzilla Database</A
></H1
><DIV
CLASS="TOC"
......@@ -77,22 +77,22 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>B.1. <A
>C.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>B.2. <A
>C.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>B.3. <A
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
><DT
>B.4. <A
>C.4. <A
HREF="cleanupwork.html"
>Cleaning up after mucking with Bugzilla</A
></DT
......@@ -105,7 +105,7 @@ CLASS="NOTE"
><P
><B
>Note: </B
>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
>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
></BLOCKQUOTE
></DIV
></DIV
......@@ -124,7 +124,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.html"
HREF="downloadlinks.html"
>Prev</A
></TD
><TD
......@@ -149,7 +149,7 @@ HREF="dbschema.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla FAQ</TD
>Software Download Links</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/dbaseintegrity.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Database Integrity</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/dbdoc.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MySQL Bugzilla Database Introduction</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="dbschema.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DBDOC"
>B.2. MySQL Bugzilla Database Introduction</A
>C.2. MySQL Bugzilla Database Introduction</A
></H1
><P
CLASS="LITERALLAYOUT"
......
docs/html/dbschema.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Database Schema Chart</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="database.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DBSCHEMA"
>B.1. Database Schema Chart</A
>C.1. Database Schema Chart</A
></H1
><P
> <DIV
......
docs/html/disclaimer.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Disclaimer</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/downloadlinks.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Software Download Links</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
REL="NEXT"
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
><BODY
CLASS="APPENDIX"
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="faq.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="database.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
><H1
><A
NAME="DOWNLOADLINKS"
>Appendix B. Software Download Links</A
></H1
><P
> All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
> Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
> Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
> MySQL: <A
HREF="http://www.mysql.org/"
TARGET="_top"
>http://www.mysql.org/</A
>
</P
><P
> Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
> CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
> DBI Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A
>
</P
><P
> Data::Dumper module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A
>
</P
><P
> MySQL related Perl modules:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A
>
</P
><P
> TimeDate Perl module collection:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A
>
</P
><P
> GD Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
HREF="http://www.boutell.com/gd/"
TARGET="_top"
>http://www.boutell.com/gd/</A
>
</P
><P
> Chart::Base module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A
>
</P
><P
> LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>http://www.linuxdoc.org/</A
>
(for documentation maintenance)
</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="faq.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="database.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla FAQ</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla Database</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/faq.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Bugzilla FAQ</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -13,8 +13,8 @@ REL="PREVIOUS"
TITLE="Bugzilla 3.0"
HREF="bz30.html"><LINK
REL="NEXT"
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
TITLE="Software Download Links"
HREF="downloadlinks.html"></HEAD
><BODY
CLASS="APPENDIX"
BGCOLOR="#FFFFFF"
......@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="database.html"
HREF="downloadlinks.html"
>Next</A
></TD
></TR
......@@ -81,63 +81,63 @@ HREF="faq.html#FAQ_GENERAL"
><DL
><DT
>A.1.1. <A
HREF="faq.html#AEN947"
HREF="faq.html#AEN1302"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
HREF="faq.html#AEN953"
HREF="faq.html#AEN1308"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
HREF="faq.html#AEN959"
HREF="faq.html#AEN1314"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
HREF="faq.html#AEN966"
HREF="faq.html#AEN1321"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
HREF="faq.html#AEN991"
HREF="faq.html#AEN1346"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
HREF="faq.html#AEN996"
HREF="faq.html#AEN1351"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
HREF="faq.html#AEN1003"
HREF="faq.html#AEN1358"
> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
HREF="faq.html#AEN1008"
HREF="faq.html#AEN1363"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
HREF="faq.html#AEN1015"
HREF="faq.html#AEN1370"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
HREF="faq.html#AEN1033"
HREF="faq.html#AEN1388"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
......@@ -153,19 +153,19 @@ HREF="faq.html#FAQ_REDHAT"
><DL
><DT
>A.2.1. <A
HREF="faq.html#AEN1046"
HREF="faq.html#AEN1405"
> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
HREF="faq.html#AEN1054"
HREF="faq.html#AEN1413"
> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
HREF="faq.html#AEN1082"
HREF="faq.html#AEN1441"
> What's the current status of Red Hat Bugzilla?
</A
></DT
......@@ -180,19 +180,19 @@ HREF="faq.html#FAQ_LOKI"
><DL
><DT
>A.3.1. <A
HREF="faq.html#AEN1097"
HREF="faq.html#AEN1457"
> What about Loki Bugzilla?
</A
></DT
><DT
>A.3.2. <A
HREF="faq.html#AEN1104"
HREF="faq.html#AEN1464"
> Who maintains Fenris (Loki Bugzilla) now?
</A
></DT
><DT
>A.3.3. <A
HREF="faq.html#AEN1109"
HREF="faq.html#AEN1469"
>
</A
></DT
......@@ -207,41 +207,41 @@ HREF="faq.html#FAQ_PHB"
><DL
><DT
>A.4.1. <A
HREF="faq.html#AEN1116"
HREF="faq.html#AEN1477"
> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
HREF="faq.html#AEN1121"
HREF="faq.html#AEN1482"
> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
HREF="faq.html#AEN1126"
HREF="faq.html#AEN1487"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
HREF="faq.html#AEN1131"
HREF="faq.html#AEN1492"
> 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.4.5. <A
HREF="faq.html#AEN1136"
HREF="faq.html#AEN1497"
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
HREF="faq.html#AEN1141"
HREF="faq.html#AEN1502"
> 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?
......@@ -249,35 +249,35 @@ HREF="faq.html#AEN1141"
></DT
><DT
>A.4.7. <A
HREF="faq.html#AEN1146"
HREF="faq.html#AEN1507"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.4.8. <A
HREF="faq.html#AEN1154"
HREF="faq.html#AEN1515"
> 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?
</A
></DT
><DT
>A.4.9. <A
HREF="faq.html#AEN1159"
HREF="faq.html#AEN1520"
> 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.4.10. <A
HREF="faq.html#AEN1164"
HREF="faq.html#AEN1525"
> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
>A.4.11. <A
HREF="faq.html#AEN1171"
HREF="faq.html#AEN1532"
> 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
owner, status or description etc.?
......@@ -285,7 +285,7 @@ HREF="faq.html#AEN1171"
></DT
><DT
>A.4.12. <A
HREF="faq.html#AEN1176"
HREF="faq.html#AEN1537"
> 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
......@@ -294,7 +294,7 @@ HREF="faq.html#AEN1176"
></DT
><DT
>A.4.13. <A
HREF="faq.html#AEN1184"
HREF="faq.html#AEN1545"
> Does Bugzilla allow fields to be added, changed or deleted? If I want to
customize the bug submission form to meet our needs, can I do that using our
terminology?
......@@ -302,47 +302,47 @@ HREF="faq.html#AEN1184"
></DT
><DT
>A.4.14. <A
HREF="faq.html#AEN1189"
HREF="faq.html#AEN1550"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
HREF="faq.html#AEN1194"
HREF="faq.html#AEN1555"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
HREF="faq.html#AEN1199"
HREF="faq.html#AEN1560"
> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
HREF="faq.html#AEN1204"
HREF="faq.html#AEN1565"
> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
HREF="faq.html#AEN1209"
HREF="faq.html#AEN1570"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
HREF="faq.html#AEN1214"
HREF="faq.html#AEN1575"
> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
HREF="faq.html#AEN1219"
HREF="faq.html#AEN1580"
> 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?
......@@ -350,19 +350,19 @@ HREF="faq.html#AEN1219"
></DT
><DT
>A.4.21. <A
HREF="faq.html#AEN1224"
HREF="faq.html#AEN1585"
> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
HREF="faq.html#AEN1230"
HREF="faq.html#AEN1591"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
HREF="faq.html#AEN1235"
HREF="faq.html#AEN1596"
> 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
......@@ -372,7 +372,7 @@ HREF="faq.html#AEN1235"
></DT
><DT
>A.4.24. <A
HREF="faq.html#AEN1242"
HREF="faq.html#AEN1603"
> 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
......@@ -382,7 +382,7 @@ HREF="faq.html#AEN1242"
></DT
><DT
>A.4.25. <A
HREF="faq.html#AEN1247"
HREF="faq.html#AEN1608"
> 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
......@@ -398,19 +398,19 @@ HREF="faq.html#FAQ_INSTALL"
><DL
><DT
>A.5.1. <A
HREF="faq.html#AEN1254"
HREF="faq.html#AEN1615"
> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
HREF="faq.html#AEN1260"
HREF="faq.html#AEN1621"
> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
HREF="faq.html#AEN1265"
HREF="faq.html#AEN1626"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
......@@ -425,20 +425,20 @@ HREF="faq.html#FAQ_SECURITY"
><DL
><DT
>A.6.1. <A
HREF="faq.html#AEN1272"
HREF="faq.html#AEN1633"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the README!)?
</A
></DT
><DT
>A.6.2. <A
HREF="faq.html#AEN1278"
HREF="faq.html#AEN1639"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
HREF="faq.html#AEN1283"
HREF="faq.html#AEN1644"
> 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.
......@@ -455,48 +455,48 @@ HREF="faq.html#FAQ_EMAIL"
><DL
><DT
>A.7.1. <A
HREF="faq.html#AEN1290"
HREF="faq.html#AEN1651"
> 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.7.2. <A
HREF="faq.html#AEN1295"
HREF="faq.html#AEN1656"
> 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.7.3. <A
HREF="faq.html#AEN1300"
HREF="faq.html#AEN1661"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
HREF="faq.html#AEN1306"
HREF="faq.html#AEN1667"
> 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.7.5. <A
HREF="faq.html#AEN1313"
HREF="faq.html#AEN1674"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
HREF="faq.html#AEN1318"
HREF="faq.html#AEN1679"
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
HREF="faq.html#AEN1325"
HREF="faq.html#AEN1686"
> How come email never reaches me from bugzilla changes?
</A
></DT
......@@ -511,60 +511,60 @@ HREF="faq.html#FAQ_DB"
><DL
><DT
>A.8.1. <A
HREF="faq.html#AEN1333"
HREF="faq.html#AEN1694"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
HREF="faq.html#AEN1338"
HREF="faq.html#AEN1699"
> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
HREF="faq.html#AEN1343"
HREF="faq.html#AEN1704"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
HREF="faq.html#AEN1348"
HREF="faq.html#AEN1709"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
HREF="faq.html#AEN1353"
HREF="faq.html#AEN1714"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
HREF="faq.html#AEN1358"
HREF="faq.html#AEN1719"
> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
HREF="faq.html#AEN1363"
HREF="faq.html#AEN1724"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
HREF="faq.html#AEN1370"
HREF="faq.html#AEN1731"
> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
HREF="faq.html#AEN1375"
HREF="faq.html#AEN1736"
> How come even after I delete bugs, the long descriptions show up?
</A
></DT
......@@ -579,32 +579,32 @@ HREF="faq.html#FAQ_NT"
><DL
><DT
>A.9.1. <A
HREF="faq.html#AEN1382"
HREF="faq.html#AEN1743"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
HREF="faq.html#AEN1387"
HREF="faq.html#AEN1748"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
HREF="faq.html#AEN1392"
HREF="faq.html#AEN1753"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
HREF="faq.html#AEN1400"
HREF="faq.html#AEN1761"
> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
HREF="faq.html#AEN1406"
HREF="faq.html#AEN1767"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
......@@ -620,34 +620,34 @@ HREF="faq.html#FAQ_USE"
><DL
><DT
>A.10.1. <A
HREF="faq.html#AEN1427"
HREF="faq.html#AEN1788"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
HREF="faq.html#AEN1433"
HREF="faq.html#AEN1794"
> 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.10.3. <A
HREF="faq.html#AEN1443"
HREF="faq.html#AEN1804"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
HREF="faq.html#AEN1448"
HREF="faq.html#AEN1809"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
HREF="faq.html#AEN1453"
HREF="faq.html#AEN1814"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
......@@ -662,13 +662,20 @@ HREF="faq.html#FAQ_HACKING"
><DL
><DT
>A.11.1. <A
HREF="faq.html#AEN1460"
HREF="faq.html#AEN1821"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
HREF="faq.html#AEN1469"
HREF="faq.html#AEN1830"
> 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.11.3. <A
HREF="faq.html#AEN1836"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
......@@ -688,7 +695,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN947"
NAME="AEN1302"
></A
><B
>A.1.1. </B
......@@ -714,7 +721,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN953"
NAME="AEN1308"
></A
><B
>A.1.2. </B
......@@ -741,7 +748,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN959"
NAME="AEN1314"
></A
><B
>A.1.3. </B
......@@ -776,7 +783,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN966"
NAME="AEN1321"
></A
><B
>A.1.4. </B
......@@ -884,7 +891,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN991"
NAME="AEN1346"
></A
><B
>A.1.5. </B
......@@ -912,7 +919,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN996"
NAME="AEN1351"
></A
><B
>A.1.6. </B
......@@ -947,7 +954,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1003"
NAME="AEN1358"
></A
><B
>A.1.7. </B
......@@ -970,7 +977,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1008"
NAME="AEN1363"
></A
><B
>A.1.8. </B
......@@ -1008,7 +1015,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1015"
NAME="AEN1370"
></A
><B
>A.1.9. </B
......@@ -1023,7 +1030,7 @@ CLASS="ANSWER"
> </B
>Terry Weissman answers,
<A
NAME="AEN1019"
NAME="AEN1374"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1099,7 +1106,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1033"
NAME="AEN1388"
></A
><B
>A.1.10. </B
......@@ -1119,7 +1126,7 @@ CLASS="ANSWER"
><P
> Here's Terry Weissman's comment, for some historical context:
<A
NAME="AEN1038"
NAME="AEN1393"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1161,13 +1168,30 @@ CLASS="QANDADIV"
NAME="FAQ_REDHAT"
></A
>2. Red Hat Bugzilla</H3
><P
> <DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> <EM
>This section is no longer up-to-date.</EM
>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</P
></BLOCKQUOTE
></DIV
>
</P
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1046"
NAME="AEN1405"
></A
><B
>A.2.1. </B
......@@ -1191,7 +1215,7 @@ CLASS="ANSWER"
><P
> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
NAME="AEN1051"
NAME="AEN1410"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1214,7 +1238,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1054"
NAME="AEN1413"
></A
><B
>A.2.2. </B
......@@ -1230,7 +1254,7 @@ CLASS="ANSWER"
>Dave Lawrence</EM
>:
<A
NAME="AEN1059"
NAME="AEN1418"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1346,7 +1370,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1082"
NAME="AEN1441"
></A
><B
>A.2.3. </B
......@@ -1366,7 +1390,8 @@ CLASS="NOTE"
><B
>Note: </B
> This information is somewhat dated; I last updated it
7 June 2000.
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</P
></BLOCKQUOTE
></DIV
......@@ -1375,7 +1400,7 @@ CLASS="NOTE"
>Dave Lawrence</EM
>:
<A
NAME="AEN1089"
NAME="AEN1448"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1409,7 +1434,7 @@ CLASS="BLOCKQUOTE"
thing going to help others that may need it.
</P
><P
> As Matt has mentioned it is still using out-dated code and with a
> 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
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
......@@ -1438,29 +1463,35 @@ CLASS="QANDADIV"
NAME="FAQ_LOKI"
></A
>3. Loki Bugzilla (AKA Fenris)</H3
><DIV
><P
> <DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> Loki's "Fenris" Bugzilla is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I left this section of the
FAQ principally for historical interest.
</P
> Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
tree, and is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I leave this section of the
FAQ principally for historical interest, but unless Loki has further
input into Bugzilla's future, it will be deprecated in future versions
of the Guide.
</P
></BLOCKQUOTE
></DIV
>
</P
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1097"
NAME="AEN1457"
></A
><B
>A.3.1. </B
......@@ -1475,7 +1506,7 @@ CLASS="ANSWER"
> Loki Games has a customized version of Bugzilla available at
http://fenris.lokigames.com. From that page,
<A
NAME="AEN1101"
NAME="AEN1461"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -1505,7 +1536,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1104"
NAME="AEN1464"
></A
><B
>A.3.2. </B
......@@ -1529,7 +1560,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1109"
NAME="AEN1469"
></A
><B
>A.3.3. </B
......@@ -1545,25 +1576,28 @@ CLASS="QANDADIV"
NAME="FAQ_PHB"
></A
>4. Pointy-Haired-Boss Questions</H3
><DIV
><P
> <DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> 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 :)
</P
> 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 :)
</P
></BLOCKQUOTE
></DIV
>
</P
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1116"
NAME="AEN1477"
></A
><B
>A.4.1. </B
......@@ -1587,7 +1621,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1121"
NAME="AEN1482"
></A
><B
>A.4.2. </B
......@@ -1614,7 +1648,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1126"
NAME="AEN1487"
></A
><B
>A.4.3. </B
......@@ -1640,7 +1674,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1131"
NAME="AEN1492"
></A
><B
>A.4.4. </B
......@@ -1663,7 +1697,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1136"
NAME="AEN1497"
></A
><B
>A.4.5. </B
......@@ -1691,7 +1725,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1141"
NAME="AEN1502"
></A
><B
>A.4.6. </B
......@@ -1717,7 +1751,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1146"
NAME="AEN1507"
></A
><B
>A.4.7. </B
......@@ -1756,7 +1790,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1154"
NAME="AEN1515"
></A
><B
>A.4.8. </B
......@@ -1781,7 +1815,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1159"
NAME="AEN1520"
></A
><B
>A.4.9. </B
......@@ -1804,7 +1838,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1164"
NAME="AEN1525"
></A
><B
>A.4.10. </B
......@@ -1845,7 +1879,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1171"
NAME="AEN1532"
></A
><B
>A.4.11. </B
......@@ -1872,7 +1906,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1176"
NAME="AEN1537"
></A
><B
>A.4.12. </B
......@@ -1917,7 +1951,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1184"
NAME="AEN1545"
></A
><B
>A.4.13. </B
......@@ -1941,7 +1975,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1189"
NAME="AEN1550"
></A
><B
>A.4.14. </B
......@@ -1967,7 +2001,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1194"
NAME="AEN1555"
></A
><B
>A.4.15. </B
......@@ -1990,7 +2024,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1199"
NAME="AEN1560"
></A
><B
>A.4.16. </B
......@@ -2012,7 +2046,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1204"
NAME="AEN1565"
></A
><B
>A.4.17. </B
......@@ -2035,7 +2069,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1209"
NAME="AEN1570"
></A
><B
>A.4.18. </B
......@@ -2059,7 +2093,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1214"
NAME="AEN1575"
></A
><B
>A.4.19. </B
......@@ -2082,7 +2116,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1219"
NAME="AEN1580"
></A
><B
>A.4.20. </B
......@@ -2107,7 +2141,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1224"
NAME="AEN1585"
></A
><B
>A.4.21. </B
......@@ -2135,7 +2169,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1230"
NAME="AEN1591"
></A
><B
>A.4.22. </B
......@@ -2159,7 +2193,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1235"
NAME="AEN1596"
></A
><B
>A.4.23. </B
......@@ -2198,7 +2232,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1242"
NAME="AEN1603"
></A
><B
>A.4.24. </B
......@@ -2229,7 +2263,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1247"
NAME="AEN1608"
></A
><B
>A.4.25. </B
......@@ -2261,7 +2295,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1254"
NAME="AEN1615"
></A
><B
>A.5.1. </B
......@@ -2289,7 +2323,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1260"
NAME="AEN1621"
></A
><B
>A.5.2. </B
......@@ -2312,7 +2346,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1265"
NAME="AEN1626"
></A
><B
>A.5.3. </B
......@@ -2342,7 +2376,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1272"
NAME="AEN1633"
></A
><B
>A.6.1. </B
......@@ -2370,7 +2404,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1278"
NAME="AEN1639"
></A
><B
>A.6.2. </B
......@@ -2395,7 +2429,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1283"
NAME="AEN1644"
></A
><B
>A.6.3. </B
......@@ -2429,7 +2463,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1290"
NAME="AEN1651"
></A
><B
>A.7.1. </B
......@@ -2453,7 +2487,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1295"
NAME="AEN1656"
></A
><B
>A.7.2. </B
......@@ -2477,7 +2511,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1300"
NAME="AEN1661"
></A
><B
>A.7.3. </B
......@@ -2507,7 +2541,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1306"
NAME="AEN1667"
></A
><B
>A.7.4. </B
......@@ -2523,7 +2557,7 @@ CLASS="ANSWER"
> You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
NAME="AEN1310"
NAME="AEN1671"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -2544,7 +2578,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1313"
NAME="AEN1674"
></A
><B
>A.7.5. </B
......@@ -2567,7 +2601,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1318"
NAME="AEN1679"
></A
><B
>A.7.6. </B
......@@ -2594,7 +2628,7 @@ CLASS="ANSWER"
is unavailable.
</P
><P
> This is now a configurable parameter called "sendmailparm", available
> This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
</P
></DIV
......@@ -2605,7 +2639,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1325"
NAME="AEN1686"
></A
><B
>A.7.7. </B
......@@ -2643,7 +2677,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1333"
NAME="AEN1694"
></A
><B
>A.8.1. </B
......@@ -2668,7 +2702,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1338"
NAME="AEN1699"
></A
><B
>A.8.2. </B
......@@ -2703,7 +2737,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1343"
NAME="AEN1704"
></A
><B
>A.8.3. </B
......@@ -2731,7 +2765,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1348"
NAME="AEN1709"
></A
><B
>A.8.4. </B
......@@ -2758,7 +2792,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1353"
NAME="AEN1714"
></A
><B
>A.8.5. </B
......@@ -2782,7 +2816,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1358"
NAME="AEN1719"
></A
><B
>A.8.6. </B
......@@ -2809,7 +2843,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1363"
NAME="AEN1724"
></A
><B
>A.8.7. </B
......@@ -2845,7 +2879,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1370"
NAME="AEN1731"
></A
><B
>A.8.8. </B
......@@ -2871,7 +2905,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1375"
NAME="AEN1736"
></A
><B
>A.8.9. </B
......@@ -2904,7 +2938,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1382"
NAME="AEN1743"
></A
><B
>A.9.1. </B
......@@ -2927,7 +2961,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1387"
NAME="AEN1748"
></A
><B
>A.9.2. </B
......@@ -2951,7 +2985,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1392"
NAME="AEN1753"
></A
><B
>A.9.3. </B
......@@ -2972,7 +3006,7 @@ CLASS="ANSWER"
><P
> Microsoft has some advice on this matter, as well:
<A
NAME="AEN1397"
NAME="AEN1758"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -2997,7 +3031,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1400"
NAME="AEN1761"
></A
><B
>A.9.4. </B
......@@ -3108,7 +3142,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1406"
NAME="AEN1767"
></A
><B
>A.9.5. </B
......@@ -3183,7 +3217,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1427"
NAME="AEN1788"
></A
><B
>A.10.1. </B
......@@ -3211,7 +3245,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1433"
NAME="AEN1794"
></A
><B
>A.10.2. </B
......@@ -3264,7 +3298,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1443"
NAME="AEN1804"
></A
><B
>A.10.3. </B
......@@ -3289,7 +3323,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1448"
NAME="AEN1809"
></A
><B
>A.10.4. </B
......@@ -3314,7 +3348,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1453"
NAME="AEN1814"
></A
><B
>A.10.5. </B
......@@ -3346,7 +3380,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1460"
NAME="AEN1821"
></A
><B
>A.11.1. </B
......@@ -3390,10 +3424,42 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
NAME="AEN1469"
NAME="AEN1830"
></A
><B
>A.11.2. </B
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> This is well-documented here: <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
TARGET="_top"
> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
>. Ultimately, it's as easy
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
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "resolved wontfix",
there may be a better way to handle this...
</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1836"
></A
><B
>A.11.3. </B
> What's the best way to submit patches? What guidelines should I follow?
</P
></DIV
......@@ -3486,7 +3552,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="database.html"
HREF="downloadlinks.html"
>Next</A
></TD
></TR
......@@ -3505,7 +3571,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla Database</TD
>Software Download Links</TD
></TR
></TABLE
></DIV
......
docs/html/feedback.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Feedback</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/future.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Future of Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -116,7 +116,7 @@ WIDTH="100%"
><TD
><PRE
CLASS="SYNOPSIS"
>This section largely contributed by Matthew Tuck</PRE
>Bugzilla's Future. Much of this is the present, now.</PRE
></TD
></TR
></TABLE
......
docs/html/gfdl.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>GNU Free Documentation License</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="GFDL"
>Appendix D. GNU Free Documentation License</A
>Appendix E. GNU Free Documentation License</A
></H1
><DIV
CLASS="TOC"
......@@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN1609"
NAME="AEN2019"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl_0.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_1.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_0.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_10.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_9.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_2.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_1.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_3.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_2.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_4.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_3.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_5.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_4.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_6.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_5.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_7.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_6.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_8.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_7.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_9.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_8.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_howto.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_10.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -78,7 +78,7 @@ NAME="GFDL_HOWTO"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN1699"
NAME="AEN2109"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/glossary.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Glossary</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -163,7 +163,7 @@ NAME="GLOSS_P"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN1735"
NAME="AEN2145"
></A
><P
><B
......
docs/html/granttables.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MySQL Permissions &#38; Grant Tables</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="dbdoc.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="GRANTTABLES"
>B.3. MySQL Permissions &#38; Grant Tables</A
>C.3. MySQL Permissions &#38; Grant Tables</A
></H1
><DIV
CLASS="NOTE"
......@@ -80,7 +80,13 @@ CLASS="NOTE"
><P
><B
>Note: </B
>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</P
>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</P
></BLOCKQUOTE
></DIV
><P
......
docs/html/how.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>How do I use Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -97,7 +97,7 @@ VALIGN="TOP"
></TR
></TABLE
><P
> Bugzilla is a large and complex system. Describing how to use it
> Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -112,11 +112,37 @@ HREF="http://landfill.tequilarista.org/"
TARGET="_top"
> landfill.tequilarista.org</A
>.
<DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <A
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>http://www.trilobyte.net/barnsons</A
>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<A
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
> news://news.mozilla.org/netscape.public.mozilla.webtools</A
>
</P
></BLOCKQUOTE
></DIV
>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</P
><DIV
CLASS="SECTION"
......@@ -318,7 +344,7 @@ TYPE="1"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN745"
NAME="AEN1095"
></A
><P
><B
......@@ -327,7 +353,7 @@ NAME="AEN745"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN747"
NAME="AEN1097"
></A
><P
></P
......@@ -379,7 +405,7 @@ NAME="AEN747"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN755"
NAME="AEN1105"
></A
><P
><B
......@@ -388,7 +414,7 @@ NAME="AEN755"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN757"
NAME="AEN1107"
></A
><P
></P
......
docs/html/index.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Bugzilla Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="NEXT"
TITLE="About This Guide"
......@@ -63,6 +63,84 @@ CLASS="ADDRESS"
></DIV
></DIV
><DIV
CLASS="REVHISTORY"
><TABLE
WIDTH="100%"
BORDER="0"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
COLSPAN="3"
><B
>Revision History</B
></TH
></TR
><TR
><TD
ALIGN="LEFT"
>Revision v2.11</TD
><TD
ALIGN="LEFT"
>20 December 2000</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Converted the README, FAQ, and DATABASE information into SGML
docbook format.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.11.1</TD
><TD
ALIGN="LEFT"
>06 March 2001</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
cleaned up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration information.
From this point on all new tags are lowercase in preparation for the
2.13 release of the Guide in XML format instead of SGML.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.12.0</TD
><TD
ALIGN="LEFT"
>24 April 2001</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.</TD
></TR
></TABLE
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
><A
......@@ -150,11 +228,143 @@ HREF="installation.html"
HREF="readme.unix.html"
>UNIX Installation</A
></DT
><DD
><DL
><DT
>2.1.1. <A
HREF="readme.unix.html#AEN190"
>ERRATA</A
></DT
><DT
>2.1.2. <A
HREF="readme.unix.html#AEN204"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
>2.1.2.1. <A
HREF="readme.unix.html#AEN206"
>Introduction</A
></DT
><DT
>2.1.2.2. <A
HREF="readme.unix.html#AEN211"
>Installing the Prerequisites</A
></DT
><DT
>2.1.2.3. <A
HREF="readme.unix.html#AEN242"
>Installing MySQL Database</A
></DT
><DT
>2.1.2.4. <A
HREF="readme.unix.html#AEN248"
>Perl (5.004 or greater)</A
></DT
><DT
>2.1.2.5. <A
HREF="readme.unix.html#AEN259"
>DBI Perl Module</A
></DT
><DT
>2.1.2.6. <A
HREF="readme.unix.html#AEN296"
>Data::Dumper Perl Module</A
></DT
><DT
>2.1.2.7. <A
HREF="readme.unix.html#AEN300"
>MySQL related Perl Module Collection</A
></DT
><DT
>2.1.2.8. <A
HREF="readme.unix.html#AEN309"
>TimeDate Perl Module Collection</A
></DT
><DT
>2.1.2.9. <A
HREF="readme.unix.html#AEN312"
>GD Perl Module (1.8.3)</A
></DT
><DT
>2.1.2.10. <A
HREF="readme.unix.html#AEN318"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>2.1.2.11. <A
HREF="readme.unix.html#AEN321"
>DB_File Perl Module</A
></DT
><DT
>2.1.2.12. <A
HREF="readme.unix.html#AEN324"
>HTTP Server</A
></DT
><DT
>2.1.2.13. <A
HREF="readme.unix.html#AEN334"
>Installing the Bugzilla Files</A
></DT
><DT
>2.1.2.14. <A
HREF="readme.unix.html#AEN343"
>Setting Up the MySQL Database</A
></DT
><DT
>2.1.2.15. <A
HREF="readme.unix.html#AEN379"
>Tweaking "localconfig"</A
></DT
><DT
>2.1.2.16. <A
HREF="readme.unix.html#AEN401"
>Setting Up Maintainers Manuall (Optional)</A
></DT
><DT
>2.1.2.17. <A
HREF="readme.unix.html#AEN410"
>The Whining Cron (Optional)</A
></DT
><DT
>2.1.2.18. <A
HREF="readme.unix.html#AEN417"
>Bug Graphs (Optional)</A
></DT
><DT
>2.1.2.19. <A
HREF="readme.unix.html#AEN429"
>Securing MySQL</A
></DT
><DT
>2.1.2.20. <A
HREF="readme.unix.html#AEN495"
>Installation General Notes</A
></DT
></DL
></DD
></DL
></DD
><DT
>2.2. <A
HREF="readme.windows.html"
>Win32 (Win98+/NT/2K) Installation</A
></DT
><DD
><DL
><DT
>2.2.1. <A
HREF="readme.windows.html#NTVERIFIED"
>Win32 Installation: Step-by-step</A
></DT
><DT
>2.2.2. <A
HREF="readme.windows.html#ADDLWINTIPS"
>Additional Windows Tips</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -174,11 +384,83 @@ HREF="postinstall-check.html"
HREF="useradmin.html"
>User Administration</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
>Creating the Default User</A
></DT
><DT
>3.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>3.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
>3.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
>3.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
>3.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
></DL
></DD
></DL
></DD
><DT
>3.3. <A
HREF="programadmin.html"
>Product, Component, Milestone, and Version Administration</A
></DT
><DD
><DL
><DT
>3.3.1. <A
HREF="programadmin.html#PRODUCTS"
>Products</A
></DT
><DT
>3.3.2. <A
HREF="programadmin.html#COMPONENTS"
>Components</A
></DT
><DT
>3.3.3. <A
HREF="programadmin.html#VERSIONS"
>Versions</A
></DT
><DT
>3.3.4. <A
HREF="programadmin.html#MILESTONES"
>Milestones</A
></DT
><DT
>3.3.5. <A
HREF="programadmin.html#VOTING"
>Voting</A
></DT
><DT
>3.3.6. <A
HREF="programadmin.html#GROUPS"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
>3.4. <A
HREF="security.html"
......@@ -208,11 +490,87 @@ HREF="why.html"
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DD
><DL
><DT
>4.3.1. <A
HREF="how.html#MYACCOUNT"
>Create a Bugzilla Account</A
></DT
><DT
>4.3.2. <A
HREF="how.html#QUERY"
>The Bugzilla Query Page</A
></DT
><DT
>4.3.3. <A
HREF="how.html#BUGREPORTS"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>4.3.3.1. <A
HREF="how.html#BUG_WRITING"
>Writing a Great Bug Report</A
></DT
><DT
>4.3.3.2. <A
HREF="how.html#BUG_MANAGE"
>Managing your Bug Reports</A
></DT
></DL
></DD
></DL
></DD
><DT
>4.4. <A
HREF="init4me.html"
>What's in it for me?</A
></DT
><DD
><DL
><DT
>4.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS"
>Account Settings</A
></DT
><DT
>4.4.2. <A
HREF="init4me.html#EMAILSETTINGS"
>Email Settings</A
></DT
><DD
><DL
><DT
>4.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
>Email Notification</A
></DT
><DT
>4.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
>New Email Technology</A
></DT
><DT
>4.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>4.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
>Page Footer</A
></DT
><DT
>4.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS"
>Permissions</A
></DT
></DL
></DD
><DT
>4.5. <A
HREF="usingbz-conc.html"
......@@ -295,59 +653,78 @@ HREF="faq.html"
></DT
><DT
>B. <A
HREF="downloadlinks.html"
>Software Download Links</A
></DT
><DT
>C. <A
HREF="database.html"
>The Bugzilla Database</A
></DT
><DD
><DL
><DT
>B.1. <A
>C.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>B.2. <A
>C.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>B.3. <A
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
><DT
>B.4. <A
>C.4. <A
HREF="cleanupwork.html"
>Cleaning up after mucking with Bugzilla</A
></DT
></DL
></DD
><DT
>C. <A
>7. <A
HREF="variants.html"
>Bugzilla Variants</A
></DT
><DD
><DL
><DT
>7.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
></DL
></DD
><DT
>D. <A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
></DT
><DD
><DL
><DT
>C.1. <A
>D.1. <A
HREF="setperl.html"
>The setperl.pl Utility</A
>The setperl.csh Utility</A
></DT
><DT
>C.2. <A
>D.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>C.3. <A
>D.3. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
></DL
></DD
><DT
>D. <A
>E. <A
HREF="gfdl.html"
>GNU Free Documentation License</A
></DT
......@@ -431,53 +808,65 @@ CLASS="LOT"
>List of Examples</B
></DT
><DT
>2-1. <A
HREF="readme.windows.html#AEN646"
>Removing encrypt() for Windows NT installations</A
></DT
><DT
>3-1. <A
HREF="programadmin.html#AEN491"
HREF="programadmin.html#AEN838"
>Creating some Components</A
></DT
><DT
>3-2. <A
HREF="programadmin.html#AEN520"
HREF="programadmin.html#AEN867"
>Common Use of Versions</A
></DT
><DT
>3-3. <A
HREF="programadmin.html#AEN524"
HREF="programadmin.html#AEN871"
>A Different Use of Versions</A
></DT
><DT
>3-4. <A
HREF="programadmin.html#AEN552"
HREF="programadmin.html#AEN899"
>Using SortKey with Target Milestone</A
></DT
><DT
>3-5. <A
HREF="programadmin.html#AEN590"
HREF="programadmin.html#AEN937"
>When to Use Group Security</A
></DT
><DT
>3-6. <A
HREF="programadmin.html#AEN607"
HREF="programadmin.html#AEN954"
>Creating a New Group</A
></DT
><DT
>4-1. <A
HREF="how.html#AEN745"
HREF="how.html#AEN1095"
>Some Famous Software Versions</A
></DT
><DT
>4-2. <A
HREF="how.html#AEN755"
HREF="how.html#AEN1105"
>Mozilla Webtools Components</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN1963"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN1735"
HREF="glossary.html#AEN2145"
>A Sample Product</A
></DT
></DL
></DIV
></DIV
>] &#62;
</DIV
><DIV
CLASS="NAVFOOTER"
><HR
......
docs/html/init4me.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>What's in it for me?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -150,6 +150,20 @@ CLASS="SECTION"
NAME="NOTIFICATION"
>4.4.2.1. Email Notification</A
></H3
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</P
></BLOCKQUOTE
></DIV
><P
> Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/html/installation.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Installing Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -81,6 +81,143 @@ CLASS="TOC"
HREF="readme.unix.html"
>UNIX Installation</A
></DT
><DD
><DL
><DT
>2.1.1. <A
HREF="readme.unix.html#AEN190"
>ERRATA</A
></DT
><DT
>2.1.2. <A
HREF="readme.unix.html#AEN204"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
>2.1.2.1. <A
HREF="readme.unix.html#AEN206"
>Introduction</A
></DT
><DT
>2.1.2.2. <A
HREF="readme.unix.html#AEN211"
>Installing the Prerequisites</A
></DT
><DT
>2.1.2.3. <A
HREF="readme.unix.html#AEN242"
>Installing MySQL Database</A
></DT
><DT
>2.1.2.4. <A
HREF="readme.unix.html#AEN248"
>Perl (5.004 or greater)</A
></DT
><DT
>2.1.2.5. <A
HREF="readme.unix.html#AEN259"
>DBI Perl Module</A
></DT
><DT
>2.1.2.6. <A
HREF="readme.unix.html#AEN296"
>Data::Dumper Perl Module</A
></DT
><DT
>2.1.2.7. <A
HREF="readme.unix.html#AEN300"
>MySQL related Perl Module Collection</A
></DT
><DT
>2.1.2.8. <A
HREF="readme.unix.html#AEN309"
>TimeDate Perl Module Collection</A
></DT
><DT
>2.1.2.9. <A
HREF="readme.unix.html#AEN312"
>GD Perl Module (1.8.3)</A
></DT
><DT
>2.1.2.10. <A
HREF="readme.unix.html#AEN318"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>2.1.2.11. <A
HREF="readme.unix.html#AEN321"
>DB_File Perl Module</A
></DT
><DT
>2.1.2.12. <A
HREF="readme.unix.html#AEN324"
>HTTP Server</A
></DT
><DT
>2.1.2.13. <A
HREF="readme.unix.html#AEN334"
>Installing the Bugzilla Files</A
></DT
><DT
>2.1.2.14. <A
HREF="readme.unix.html#AEN343"
>Setting Up the MySQL Database</A
></DT
><DT
>2.1.2.15. <A
HREF="readme.unix.html#AEN379"
>Tweaking "localconfig"</A
></DT
><DT
>2.1.2.16. <A
HREF="readme.unix.html#AEN401"
>Setting Up Maintainers Manuall (Optional)</A
></DT
><DT
>2.1.2.17. <A
HREF="readme.unix.html#AEN410"
>The Whining Cron (Optional)</A
></DT
><DT
>2.1.2.18. <A
HREF="readme.unix.html#AEN417"
>Bug Graphs (Optional)</A
></DT
><DT
>2.1.2.19. <A
HREF="readme.unix.html#AEN429"
>Securing MySQL</A
></DT
><DT
>2.1.2.20. <A
HREF="readme.unix.html#AEN495"
>Installation General Notes</A
></DT
><DD
><DL
><DT
>2.1.2.20.1. <A
HREF="readme.unix.html#AEN497"
>Modifying Your Running System</A
></DT
><DT
>2.1.2.20.2. <A
HREF="readme.unix.html#AEN502"
>Upgrading From Previous Versions</A
></DT
><DT
>2.1.2.20.3. <A
HREF="readme.unix.html#AEN505"
>UNIX Installation Instructions History</A
></DT
></DL
></DD
></DL
></DD
></DL
></DD
><DT
>2.2. <A
HREF="readme.windows.html"
......
docs/html/integration.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Integrating Bugzilla with Third-Party Tools</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/newversions.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>New Versions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/patches.html
View file @ 2d4d7c92
......@@ -4,16 +4,16 @@
>Useful Patches and Utilities for Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Cleaning up after mucking with Bugzilla"
HREF="cleanupwork.html"><LINK
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
REL="NEXT"
TITLE="The setperl.pl Utility"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
><BODY
CLASS="APPENDIX"
......@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cleanupwork.html"
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="PATCHES"
>Appendix C. Useful Patches and Utilities for Bugzilla</A
>Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1
><DIV
CLASS="TOC"
......@@ -77,17 +77,17 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>C.1. <A
>D.1. <A
HREF="setperl.html"
>The setperl.pl Utility</A
>The setperl.csh Utility</A
></DT
><DT
>C.2. <A
>D.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>C.3. <A
>D.3. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
......@@ -109,7 +109,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cleanupwork.html"
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
......@@ -134,7 +134,7 @@ HREF="setperl.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Cleaning up after mucking with Bugzilla</TD
>Red Hat Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
......@@ -144,7 +144,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The setperl.pl Utility</TD
>The setperl.csh Utility</TD
></TR
></TABLE
></DIV
......
docs/html/postinstall-check.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Post-Installation Checklist</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -86,6 +86,17 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
> Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <A
HREF="http://bugzilla.mozilla.org/editparams.cgi"
TARGET="_top"
> http://bugzilla.mozilla.org/editparams.cgi</A
>, also available under the "edit parameters"
link on your query page.
</P
></LI
><LI
><P
> Set "maintainer" to <EM
>your</EM
> email address.
......@@ -115,7 +126,7 @@ TYPE="1"
></LI
><LI
><P
> Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
> Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -152,14 +163,16 @@ CLASS="NOTE"
attempting to commit a change to the database.
</P
><P
> If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
> If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</P
></LI
><LI
><P
> If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<DIV
CLASS="NOTE"
><BLOCKQUOTE
......@@ -167,10 +180,12 @@ CLASS="NOTE"
><P
><B
>Note: </B
> The "headerhtml" text box is the HTML printed out <EM
> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</P
></BLOCKQUOTE
......@@ -187,27 +202,33 @@ CLASS="NOTE"
></LI
><LI
><P
> Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
> Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</P
></LI
><LI
><P
> Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
> Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</P
></LI
><LI
><P
> Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
> Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</P
></LI
><LI
><P
> Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
> Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<DIV
CLASS="NOTE"
......
docs/html/programadmin.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Product, Component, Milestone, and Version Administration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -194,7 +194,7 @@ NAME="COMPONENTS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN491"
NAME="AEN838"
></A
><P
><B
......@@ -203,7 +203,7 @@ NAME="AEN491"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN493"
NAME="AEN840"
></A
><P
></P
......@@ -324,7 +324,7 @@ NAME="VERSIONS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN520"
NAME="AEN867"
></A
><P
><B
......@@ -333,7 +333,7 @@ NAME="AEN520"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN522"
NAME="AEN869"
></A
><P
></P
......@@ -354,7 +354,7 @@ NAME="AEN522"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN524"
NAME="AEN871"
></A
><P
><B
......@@ -363,7 +363,7 @@ NAME="AEN524"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN526"
NAME="AEN873"
></A
><P
></P
......@@ -472,7 +472,7 @@ TYPE="1"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN552"
NAME="AEN899"
></A
><P
><B
......@@ -481,7 +481,7 @@ NAME="AEN552"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN554"
NAME="AEN901"
></A
><P
></P
......@@ -645,7 +645,7 @@ NAME="GROUPS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN590"
NAME="AEN937"
></A
><P
><B
......@@ -654,7 +654,7 @@ NAME="AEN590"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN592"
NAME="AEN939"
></A
><P
></P
......@@ -747,7 +747,7 @@ TYPE="1"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN607"
NAME="AEN954"
></A
><P
><B
......@@ -756,7 +756,7 @@ NAME="AEN607"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN609"
NAME="AEN956"
></A
><P
></P
......
docs/html/quicksearch.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Quicksearch Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="cmdline.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUICKSEARCH"
>C.3. The Quicksearch Utility</A
>D.3. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.
......
docs/html/readme.unix.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>UNIX Installation</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,16 +74,34 @@ NAME="README.UNIX"
>2.1. UNIX Installation</A
></H1
><DIV
CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN190"
>2.1.1. ERRATA</A
></H2
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> Please consult the README included with the Bugzilla distribution
as the current canonical source for UNIX installation instructions.
We do, however, have some installation notes for errata from the README.
</P
> If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<SPAN
CLASS="ERRORNAME"
>cannot chdir(/var/spool/mqueue): Permission denied</SPAN
>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<B
CLASS="COMMAND"
>chmod 755 /var/spool/mqueue</B
> as root to fix this problem.
</P
></BLOCKQUOTE
></DIV
><DIV
......@@ -93,22 +111,602 @@ CLASS="NOTE"
><P
><B
>Note: </B
> If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<SPAN
CLASS="ERRORNAME"
>cannot chdir(/var/spool/mqueue): Permission denied</SPAN
> Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> The preferred documentation for Bugzilla is available in docs/, with
a variety of document types available. Please refer to these documents when
installing, configuring, and maintaining your Bugzilla installation.
</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
> 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
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
of third-party utilities. To install Bugzilla on Win32 requires
fair Perl proficiency, and if you use a webserver other than Apache you
should be intimately familiar with the security mechanisms and CGI
environment thereof.
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
> Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN204"
>2.1.2. Step-by-step Install</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN206"
>2.1.2.1. Introduction</A
></H3
><P
> Installation of bugzilla is pretty straightforward, particularly if your
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
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.
</P
><P
> Bugzilla has been successfully installed under Solaris, Linux, and
Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
included in this section of the Guide; please check out the "Win32 Installation Instructions"
for further advice on getting Bugzilla to work on Microsoft Windows.
</P
><P
> The Bugzilla Guide is contained in the "docs/" folder. It is available
in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN211"
>2.1.2.2. Installing the Prerequisites</A
></H3
><P
> The software packages necessary for the proper running of bugzilla are:
<P
></P
><OL
TYPE="1"
><LI
><P
> MySQL database server and the mysql client (3.22.5 or greater)
</P
></LI
><LI
><P
> Perl (5.004 or greater)
</P
></LI
><LI
><P
> DBI Perl module
</P
></LI
><LI
><P
> Data::Dumper Perl module
</P
></LI
><LI
><P
> DBD::mySQL
</P
></LI
><LI
><P
> TimeDate Perl module collection
</P
></LI
><LI
><P
> GD perl module (1.8.3) (optional, for bug charting)
</P
></LI
><LI
><P
> Chart::Base Perl module (0.99c) (optional, for bug charting)
</P
></LI
><LI
><P
> DB_File Perl module (optional, for bug charting)
</P
></LI
><LI
><P
> The web server of your choice. Apache is recommended.
</P
></LI
><LI
><P
> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</P
></LI
></OL
>
<DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> You must run Bugzilla on a filesystem that supports file locking via
flock(). This is necessary for Bugzilla to operate safely with multiple
instances.
</P
></BLOCKQUOTE
></DIV
>
<DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
> It is a good idea, while installing Bugzilla, to ensure it is not
<EM
>accessible</EM
> by other machines on the Internet.
Your machine may be vulnerable to attacks
while you are installing. In other words, ensure there is some kind of firewall between you
and the rest of the Internet. Many installation steps require an active Internet connection
to complete, but you must take care to ensure that at no point is your machine vulnerable
to an attack.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN242"
>2.1.2.3. Installing MySQL Database</A
></H3
><P
> Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
release of the server. Both binaries and source are available and which
you get shouldn't matter. Be aware that many of the binary versions
of MySQL store their data files in /var which on many installations
(particularly common with linux installations) is part of a smaller
root partition. If you decide to build from sources you can easily set
the dataDir as an option to configure.
</P
><P
> If you've installed from source or non-package (RPM, deb, etc.) binaries
you'll want to make sure to add mysqld to your init scripts so the server
daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that
mysqld will accept large packets. By default, mysqld is set up to only
accept packets up to 64K long. This limits the size of attachments you
may put on bugs. If you add something like "-O max_allowed_packet=1M"
to the command that starts mysqld (or safe_mysqld), then you will be
able to have attachments up to about 1 megabyte.
</P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> If you plan on running Bugzilla and MySQL on the same machine,
consider using the "--skip-networking" option in the init script.
This enhances security by preventing network access to MySQL.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN248"
>2.1.2.4. Perl (5.004 or greater)</A
></H3
><P
> Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from http://www.perl.com.
</P
><P
> Perl is now a far cry from the the single compiler/interpreter binary it
once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
</P
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
> You can skip the following Perl module installation
steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
All Perl module installation steps require you have an active Internet
connection.
</P
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<B
<B
CLASS="COMMAND"
>chmod 755 /var/spool/mqueue</B
> as root to fix this problem.
</P
>perl -MCPAN -e 'install "Bundle::Bugzilla"'</B
>
</TT
>
</P
><P
> Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
which are not essential to a basic Bugzilla install. If installing
this bundle fails, you should install each module individually to
isolate the problem.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN259"
>2.1.2.5. DBI Perl Module</A
></H3
><P
> 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
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
MakeMaker system simplifies the C compilation greatly.
</P
><P
> 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
real tendency to bog down, so please use mirrors. The current location
at the time of this writing (02/17/99) can be found in Appendix A.
</P
><P
> 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
which does all the hard work for you.
</P
><P
> To use the CPAN shell to install DBI:
<DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN265"
></A
><P
></P
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>perl -MCPAN -e 'install "DBI"'</B
>
</TT
>
<DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>Replace "DBI" with the name of whichever module you wish
to install, such as Data::Dumper, TimeDate, GD, etc.</P
></BLOCKQUOTE
></DIV
>
</P
><P
></P
></DIV
>
To do it the hard way:
<DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN272"
></A
><P
></P
><P
> Untar the module tarball -- it should create its own directory
</P
><P
> CD to the directory just created, and enter the following commands:
<P
></P
><OL
TYPE="1"
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>perl Makefile.PL</B
>
</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>make</B
>
</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>make test</B
>
</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>make install</B
>
</TT
>
</P
></LI
></OL
>
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
</P
><P
></P
></DIV
>
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN296"
>2.1.2.6. Data::Dumper Perl Module</A
></H3
><P
> The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
</P
><P
> Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN300"
>2.1.2.7. MySQL related Perl Module Collection</A
></H3
><P
> The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should
be untarred.
</P
><P
> The MySQL modules are all built using one make file which is generated
by running:
<TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>perl Makefile.pl</B
>
</P
><P
> The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
</P
><P
> When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
</P
><P
> 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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN309"
>2.1.2.8. TimeDate Perl Module Collection</A
></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. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of them
is probably a good idea anyway. The standard Perl module installation
instructions should work perfectly for this simple package.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN312"
>2.1.2.9. GD Perl Module (1.8.3)</A
></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 almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to generate
graphs on the fly. That's what bugzilla will be using it for so you'd
better install it if you want any of the graphing to work.
</P
><P
> Actually bugzilla uses the Graph module which relies on GD itself,
but isn't that always the way with OOP. At any rate, you can find the
GD library on CPAN (link in Appendix "Required Software").
</P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
......@@ -116,12 +714,966 @@ CLASS="NOTE"
><P
><B
>Note: </B
>
</P
> The Perl GD library requires some other libraries that may or may not be
installed on your system, including "libpng" and "libgd". The full requirements
are listed in the Perl GD library README. Just realize that if compiling GD fails,
it's probably because you're missing a required library.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN318"
>2.1.2.10. Chart::Base Perl Module (0.99c)</A
></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
fetched from CPAN where it is found as the Chart-x.x... tarball in a
directory to be listed in Appendix "Required Software". Note that as with the GD perl
module, only the specific versions listed above (or newer) will work. Earlier
versions used GIF's, which are no longer supported by the latest
versions of GD.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN321"
>2.1.2.11. DB_File Perl Module</A
></H3
><P
> DB_File is a module which allows Perl programs to make use of the facilities provided by
Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
bug charting. If you plan to make use of bug charting, you must install this module.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN324"
>2.1.2.12. HTTP Server</A
></H3
><P
> You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a different
machine than MySQL, but need to adjust the MySQL "bugs" user permissions
accordingly.
</P
><P
> 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. If you're using
apache that means uncommenting the following line in the srm.conf file:
<TT
CLASS="COMPUTEROUTPUT"
>AddHandler cgi-script .cgi</TT
>
</P
><P
> With apache you'll also want to make sure that within the access.conf
file the line:
<TT
CLASS="COMPUTEROUTPUT"
> Options ExecCGI
</TT
>
is in the stanza that covers the directories you intend to put the bugzilla
.html and .cgi files into.
</P
><P
> If you are using a newer version of Apache, both of the above lines will be
(or will need to be) in the httpd.conf file, rather than srm.conf or
access.conf.
</P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
> There are two critical directories and a file that should not be a served by
the HTTP server. These are the 'data' and 'shadow' directories and the
'localconfig' file. You should configure your HTTP server to not serve
content from these files. Failure to do so will expose critical passwords
and other data. Please see your HTTP server configuration manual on how
to do this. If you use quips (at the top of the buglist pages) you will want
the 'data/comments' file to still be served. This file contains those quips.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN334"
>2.1.2.13. Installing the Bugzilla Files</A
></H3
><P
> You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directories if they were accidentally tarred up with the rest of Bugzilla)
and make sure you can access the files in that directory through your
web server.
</P
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
> HINT: If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive "Forbidden" errors unless you
add the "FollowSymLinks" directive to the &#60;Directory&#62; entry
for the HTML root.
</P
></BLOCKQUOTE
></DIV
><P
> Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable). This is a temporary step until you run
the post-install "checksetup.pl" script, which locks down your
installation.
</P
><P
> Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
to the correct location of your perl executable (probably /usr/bin/perl).
Otherwise you must hack all the .cgi files to change where they look
for perl. To make future upgrades easier, you should use the symlink
approach.
<DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
> If you don't have root access to set this symlink up, check out the
"setperl.csh" utility, listed in the Patches section of this
Guide. It will change the path to perl in all your Bugzilla files for
you.
</P
></BLOCKQUOTE
></DIV
>
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN343"
>2.1.2.14. Setting Up the MySQL Database</A
></H3
><P
> 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
quality bug tracker.
</P
><P
> First, you'll want to fix MySQL permissions to allow access from
Bugzilla. For the purpose of this Installation section, the Bugzilla username
will be "bugs", and will have minimal permissions. Bugzilla has
not undergone a thorough security audit. It may be possible for
a system cracker to somehow trick Bugzilla into executing a command
such as "; DROP DATABASE mysql".
</P
><P
> That would be bad.
</P
><P
> Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>mysql -u root mysql</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>FLUSH PRIVILEGES;</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
From this point on, if you need to access MySQL as the
MySQL root user, you will need to use "mysql -u root -p" and
enter your new_password. Remember that MySQL user names have
nothing to do with Unix user names (login names).
</P
><P
> Next, we create the "bugs" user, and grant sufficient
permissions for checksetup.pl, which we'll use later, to work
its magic. This also restricts the "bugs" user to operations
within a database called "bugs", and only allows the account
to connect from "localhost". Modify it to reflect your setup
if you will be connecting from another machine or as a different
user.
</P
><P
> Remember to set bugs_password to some unique password.
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
IDENTIFIED BY 'bugs_password';</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
> mysql&#62;
</TT
>
<B
CLASS="COMMAND"
> FLUSH PRIVILEGES;
</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> Next, run the magic checksetup.pl script. (Many thanks to Holger
Schurig &#60;holgerschurig@nikocity.de&#62; for writing this script!)
It will make sure Bugzilla files and directories have reasonable
permissions, set up the "data" directory, and create all the MySQL
tables.
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>./checksetup.pl</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
The first time you run it, it will create a file called "localconfig".
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN379"
>2.1.2.15. Tweaking "localconfig"</A
></H3
><P
> This file contains a variety of settings you may need to tweak including
how Bugzilla should connect to the MySQL database.
</P
><P
> The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
> server's host: just use "localhost" if the MySQL server is
local
</P
></LI
><LI
><P
> database name: "bugs" if you're following these directions
</P
></LI
><LI
><P
> MySQL username: "bugs" if you're following these directions
</P
></LI
><LI
><P
> Password for the "bugs" MySQL account above
</P
></LI
></OL
>
</P
><P
> Once you are happy with the settings, re-run checksetup.pl. On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
</P
><P
> When logged into an administrator account once Bugzilla is running,
if you go to the query page (off of the bugzilla main menu), you'll
find an 'edit parameters' option that is filled with editable treats.
</P
><P
> Should everything work, you should have a nearly empty copy of the bug
tracking setup.
</P
><P
> The second time around, checksetup.pl will stall if it is on a
filesystem that does not fully support file locking via flock(), such as
NFS mounts. This support is required for Bugzilla to operate safely with
multiple instances. If flock() is not fully supported, it will stall at:
<SPAN
CLASS="ERRORCODE"
>Now regenerating the shadow database for all bugs.</SPAN
>
<DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> The second time you run checksetup.pl, it is recommended you be the same
user as your web server runs under, and that you be sure you have set the
"webservergroup" parameter in localconfig to match the web server's group
name, if any. Under some systems, otherwise, checksetup.pl will goof up
your file permissions and make them unreadable to your web server.
</P
></BLOCKQUOTE
></DIV
>
</P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> The checksetup.pl script is designed so that you can run it at any time
without causing harm. You should run it after any upgrade to Bugzilla.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN401"
>2.1.2.16. Setting Up Maintainers Manuall (Optional)</A
></H3
><P
> If you want to add someone else to every group by hand, you can do it
by typing the appropriate MySQL commands. Run '<TT
CLASS="COMPUTEROUTPUT"
> mysql -u root -p bugs</TT
>'
(you may need different parameters, depending on your security settings
according to section 3, above). Then:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>update profiles set groupset=0x7fffffffffffffff
where login_name = 'XXX';</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
replacing XXX with the Bugzilla email address.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN410"
>2.1.2.17. The Whining Cron (Optional)</A
></H3
><P
> By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see that
crontab man page):
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <B
CLASS="COMMAND"
>cd &#60;your-bugzilla-directory&#62; ; ./whineatnews.pl</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN417"
>2.1.2.18. Bug Graphs (Optional)</A
></H3
><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
><P
> Add a cron entry like this to run collectstats daily at 5 after midnight:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>crontab -e</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> 5 0 * * * cd &#60;your-bugzilla-directory&#62; ; ./collectstats.pl
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN429"
>2.1.2.19. Securing MySQL</A
></H3
><P
> If you followed the README for setting up your "bugs" and "root" user in
MySQL, much of this should not apply to you. If you are upgrading
an existing installation of Bugzilla, you should pay close attention
to this section.
</P
><P
> Most MySQL installs have "interesting" default security parameters:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>mysqld defaults to running as root</TD
></TR
><TR
><TD
>it defaults to allowing external network connections</TD
></TR
><TR
><TD
>it has a known port number, and is easy to detect</TD
></TR
><TR
><TD
>it defaults to no passwords whatsoever</TD
></TR
><TR
><TD
>it defaults to allowing "File_Priv"</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the system.
</P
><P
> To see your permissions do:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>mysql -u root -p</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>use mysql;</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>show tables;</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>select * from user;</B
>
</TT
>
</TD
></TR
><TR
><TD
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>mysql&#62;</TT
>
<B
CLASS="COMMAND"
>select * from db;</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> To fix the gaping holes:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>DELETE FROM user WHERE User='';</TD
></TR
><TR
><TD
>UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';</TD
></TR
><TR
><TD
> FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> If you're not running "mit-pthreads" you can use:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>GRANT USAGE ON *.* TO bugs@localhost;</TD
></TR
><TR
><TD
>GRANT ALL ON bugs.* TO bugs@localhost;</TD
></TR
><TR
><TD
>REVOKE DROP ON bugs.* FROM bugs@localhost;</TD
></TR
><TR
><TD
>FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> 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
external connections:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>GRANT USAGE ON *.* TO bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>GRANT ALL ON bugs.* TO bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
> Consider also:
<P
></P
><OL
TYPE="1"
><LI
><P
> Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
</P
></LI
><LI
><P
> using the --user= option to mysqld to run it as an unprivileged
user.
</P
></LI
><LI
><P
> starting MySQL in a chroot jail
</P
></LI
><LI
><P
> running the httpd in a "chrooted" jail
</P
></LI
><LI
><P
> making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
</P
></LI
><LI
><P
> running MySQL on a separate untrusted machine
</P
></LI
><LI
><P
> making backups ;-)
</P
></LI
></OL
>
</P
></DIV
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN495"
>2.1.2.20. Installation General Notes</A
></H3
><DIV
CLASS="SECTION"
><H4
CLASS="SECTION"
><A
NAME="AEN497"
>2.1.2.20.1. Modifying Your Running System</A
></H4
><P
> Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory (we said before it needs to be writable,
right?!)
</P
><P
> If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't show
up!
</P
><P
> That file gets automatically regenerated whenever it's more than an
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.
</P
></DIV
><DIV
CLASS="SECTION"
><H4
CLASS="SECTION"
><A
NAME="AEN502"
>2.1.2.20.2. Upgrading From Previous Versions</A
></H4
><P
> 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
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
changed, you can read the comments in that file, starting from the end.
</P
></DIV
><DIV
CLASS="SECTION"
><H4
CLASS="SECTION"
><A
NAME="AEN505"
>2.1.2.20.3. UNIX Installation Instructions History</A
></H4
><P
> This document was originally adapted from the Bonsai installation
instructions by Terry Weissman &#60;terry@mozilla.org&#62;.
</P
><P
> The February 25, 1999 re-write of this page was done by Ry4an Brase
&#60;ry4an@ry4an.org&#62;, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, &#38; Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
</P
><P
> This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
</P
><P
> Finally, the README in its entirety was marked up in SGML and included into
the Guide on April 24, 2001.
</P
><P
> Comments from people using this Guide for the first time are particularly welcome.
</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
......
docs/html/readme.windows.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Win32 (Win98+/NT/2K) Installation</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -510,7 +510,7 @@ CLASS="TIP"
>Tip: </B
> From Andrew Pearson:
<A
NAME="AEN304"
NAME="AEN624"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -548,6 +548,149 @@ CLASS="COMMAND"
</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P
><A
NAME="AEN634"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
deleted the current dir and copied the files in).
</P
><P
> In checksetup.pl, I did the following...
</P
><DIV
CLASS="PROCEDURE"
><OL
TYPE="1"
><LI
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = getgrnam($my_webservergroup);
</PRE
></TD
></TR
></TABLE
><P
>to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = 'Administrators'
</PRE
></TD
></TR
></TABLE
></LI
><LI
><P
> I then ran checksetup.pl
</P
></LI
><LI
><P
> I removed all the encrypt()
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN646"
></A
><P
><B
>Example 2-1. Removing encrypt() for Windows NT installations</B
></P
><P
> Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PRE
></TD
></TR
></TABLE
>
with this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $enteredcryptpwd = $enteredpwd
</PRE
></TD
></TR
></TABLE
>
in cgi.pl.
</P
></DIV
>
</P
></LI
><LI
><P
> I renamed processmail to processmail.pl
</P
></LI
><LI
><P
> I altered the sendmail statements to windmail:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log";
</PRE
></TD
></TR
></TABLE
>
</P
><P
> The quotes around the dir is for the spaces. mail.log is for the output
</P
></LI
></OL
></DIV
></BLOCKQUOTE
></BLOCKQUOTE
></DIV
></DIV
></DIV
><DIV
......
docs/html/rhbugzilla.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Red Hat Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Variants"
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.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="variants.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="RHBUGZILLA"
>7.1. Red Hat Bugzilla</A
></H1
><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<A
NAME="AEN1913"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
CLASS="LITERALLAYOUT"
> &nbsp;&nbsp;Hello.&nbsp;I&nbsp;apologize&nbsp;that&nbsp;I&nbsp;am&nbsp;getting&nbsp;back&nbsp;to&nbsp;you&nbsp;so&nbsp;late.&nbsp;It&nbsp;has&nbsp;been&nbsp;difficult&nbsp;to&nbsp;keep<br>
up&nbsp;with&nbsp;email&nbsp;this&nbsp;past&nbsp;week.&nbsp;I&nbsp;have&nbsp;checked&nbsp;out&nbsp;your&nbsp;updated&nbsp;documentation&nbsp;and&nbsp;I&nbsp;will<br>
have&nbsp;to&nbsp;say&nbsp;very&nbsp;good&nbsp;work.&nbsp;A&nbsp;few&nbsp;notes&nbsp;and&nbsp;additions&nbsp;as&nbsp;follows.<br>
<br>
(ed:&nbsp;from&nbsp;the&nbsp;FAQ)<br>
&#62;For&nbsp;the&nbsp;record,&nbsp;we&nbsp;are&nbsp;not&nbsp;using&nbsp;any&nbsp;template&nbsp;type&nbsp;implementation&nbsp;for&nbsp;the&nbsp;cosmetic&nbsp;changes&nbsp;<br>
&#62;maded&nbsp;to&nbsp;Bugzilla.&nbsp;It&nbsp;is&nbsp;just&nbsp;alot&nbsp;of&nbsp;html&nbsp;changes&nbsp;in&nbsp;the&nbsp;code&nbsp;itself.&nbsp;I&nbsp;admit&nbsp;I&nbsp;may&nbsp;have&nbsp;<br>
&#62;gotten&nbsp;a&nbsp;little&nbsp;carried&nbsp;away&nbsp;with&nbsp;it&nbsp;but&nbsp;the&nbsp;corporate&nbsp;types&nbsp;asked&nbsp;for&nbsp;a&nbsp;more&nbsp;standardized&nbsp;<br>
&#62;interface&nbsp;to&nbsp;match&nbsp;up&nbsp;with&nbsp;other&nbsp;projects&nbsp;relating&nbsp;to&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.&nbsp;A&nbsp;lot&nbsp;of&nbsp;other&nbsp;web&nbsp;<br>
&#62;based&nbsp;internal&nbsp;tools&nbsp;I&nbsp;am&nbsp;working&nbsp;on&nbsp;also&nbsp;look&nbsp;like&nbsp;Bugzilla.&nbsp;<br>
<br>
<br>
This&nbsp;should&nbsp;probably&nbsp;be&nbsp;changed&nbsp;since&nbsp;we&nbsp;are&nbsp;now&nbsp;in&nbsp;fact&nbsp;using&nbsp;Text::Template&nbsp;for&nbsp;most<br>
of&nbsp;the&nbsp;html&nbsp;rendering.&nbsp;You&nbsp;actually&nbsp;state&nbsp;this&nbsp;later&nbsp;in&nbsp;your&nbsp;numbered&nbsp;list.<br>
<br>
Also&nbsp;number&nbsp;6&nbsp;contradicts&nbsp;number&nbsp;8&nbsp;where&nbsp;number&nbsp;6&nbsp;would&nbsp;be&nbsp;the&nbsp;most&nbsp;up&nbsp;to&nbsp;date&nbsp;status<br>
on&nbsp;the&nbsp;Oracle&nbsp;port.<br>
<br>
Additional&nbsp;Information:<br>
-----------------------------<br>
1.&nbsp;Comments&nbsp;are&nbsp;now&nbsp;stored&nbsp;in&nbsp;varchar&nbsp;fields&nbsp;of&nbsp;4k&nbsp;in&nbsp;size&nbsp;each.&nbsp;If&nbsp;the&nbsp;comment&nbsp;is&nbsp;more<br>
than&nbsp;4k&nbsp;it&nbsp;is&nbsp;broken&nbsp;up&nbsp;into&nbsp;chunks&nbsp;and&nbsp;given&nbsp;a&nbsp;sort&nbsp;number&nbsp;so&nbsp;each&nbsp;comment&nbsp;can&nbsp;be&nbsp;re<br>
assembled&nbsp;in&nbsp;the&nbsp;correct&nbsp;order.&nbsp;This&nbsp;was&nbsp;done&nbsp;because&nbsp;originally&nbsp;I&nbsp;was&nbsp;storing&nbsp;the&nbsp;comments<br>
in&nbsp;a&nbsp;long&nbsp;datatype&nbsp;which&nbsp;unfortunately&nbsp;cannot&nbsp;be&nbsp;indexed&nbsp;or&nbsp;joined&nbsp;with&nbsp;another&nbsp;table.&nbsp;This<br>
cause&nbsp;the&nbsp;search&nbsp;of&nbsp;text&nbsp;within&nbsp;the&nbsp;long&nbsp;description&nbsp;to&nbsp;be&nbsp;disabled&nbsp;for&nbsp;a&nbsp;long&nbsp;time.&nbsp;That<br>
is&nbsp;now&nbsp;working&nbsp;and&nbsp;is&nbsp;nto&nbsp;showing&nbsp;any&nbsp;noticeble&nbsp;performance&nbsp;hit&nbsp;that&nbsp;I&nbsp;can&nbsp;tell.&nbsp;<br>
<br>
2.&nbsp;Work&nbsp;is&nbsp;being&nbsp;started&nbsp;on&nbsp;internationalizing&nbsp;the&nbsp;Bugzilla&nbsp;source&nbsp;we&nbsp;have&nbsp;to&nbsp;allow&nbsp;our<br>
Japanese&nbsp;customers&nbsp;to&nbsp;enter&nbsp;bug&nbsp;reports&nbsp;into&nbsp;a&nbsp;single&nbsp;bugzilla&nbsp;system.&nbsp;This&nbsp;will&nbsp;probably<br>
be&nbsp;done&nbsp;by&nbsp;using&nbsp;the&nbsp;nvarchar&nbsp;data&nbsp;types&nbsp;supported&nbsp;by&nbsp;Oracle&nbsp;which&nbsp;allows&nbsp;storage&nbsp;of<br>
double&nbsp;byte&nbsp;characters&nbsp;and&nbsp;also&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;Accept-Language&nbsp;in&nbsp;the&nbsp;http&nbsp;header&nbsp;for&nbsp;<br>
detection&nbsp;by&nbsp;Bugilla&nbsp;of&nbsp;which&nbsp;language&nbsp;to&nbsp;render.<br>
<br>
3.&nbsp;Of&nbsp;course&nbsp;even&nbsp;more&nbsp;cosmetic&nbsp;changes.&nbsp;It&nbsp;is&nbsp;difficult&nbsp;to&nbsp;keep&nbsp;up&nbsp;with&nbsp;the&nbsp;ever&nbsp;<br>
changing&nbsp;faces&nbsp;of&nbsp;www.redhat.com.<br>
<br>
4.&nbsp;Some&nbsp;convenience&nbsp;enhancements&nbsp;in&nbsp;the&nbsp;administration&nbsp;utilities.&nbsp;And&nbsp;more&nbsp;integration<br>
with&nbsp;other&nbsp;internal/external&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.<br>
<br>
I&nbsp;hope&nbsp;this&nbsp;information&nbsp;may&nbsp;prove&nbsp;helpful&nbsp;for&nbsp;your&nbsp;documentation.&nbsp;Please&nbsp;contact<br>
me&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;more&nbsp;question&nbsp;or&nbsp;I&nbsp;can&nbsp;do&nbsp;anything&nbsp;else.<br>
<br>
Regards<br>
</P
></BLOCKQUOTE
>
</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="variants.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="patches.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Variants</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/scm.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,14 +74,38 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
> Richard Brooksby and his team have an integration tool
in public beta. You can find it at
> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<A
HREF="http://www.ravenbrook.com/project/p4dt"
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
> http://www.ravenbrook.com/project/p4dti</A
>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</P
><P
> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/searching.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Better Searching</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/security.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bugzilla Security</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -172,8 +172,10 @@ TARGET="_top"
></LI
><LI
><P
> Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
> Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</P
><P
......@@ -187,7 +189,7 @@ TARGET="_top"
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
TARGET="_top"
> Bug 65572</A
> for adequate protection in your data/ and shadow/ directories.
> for adequate protection in your data/ and shadow/ directories.
</P
><P
> Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -228,11 +230,6 @@ CLASS="LITERALLAYOUT"
>
</P
></LI
><LI
><P
>
</P
></LI
></OL
>
</P
......
docs/html/setperl.html
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>The setperl.pl Utility</TITLE
>The setperl.csh Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="patches.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,12 +71,14 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="SETPERL"
>C.1. The setperl.pl Utility</A
>D.1. The setperl.csh Utility</A
></H1
><P
>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</P
><DIV
CLASS="PROCEDURE"
......@@ -84,7 +86,7 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
> Download the "setperl.pl" utility to your Bugzilla
> Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
......@@ -116,7 +118,7 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
>
</TT
>
......@@ -132,7 +134,7 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>chmod u+x setperl.pl</B
>chmod u+x setperl.csh</B
>
</TT
>
......@@ -210,10 +212,35 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>./setperl.pl /your/path/to/perl</B
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1963"
></A
><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>./setperl.csh /usr/bin/perl</B
>
</TT
>
</P
></DIV
>
</P
></LI
></OL
......
docs/html/spamlite.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Reducing Spam</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -120,7 +120,11 @@ watching.&nbsp;&nbsp;With&nbsp;this,&nbsp;you&nbsp;could&nbsp;choose&nbsp;whethe
dependency&nbsp;and&nbsp;keyword&nbsp;changes,&nbsp;for&nbsp;example.<br>
<br>
Both&nbsp;of&nbsp;these&nbsp;proposals&nbsp;live&nbsp;at<br>
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".</P
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".<br>
Note&nbsp;that&nbsp;they&nbsp;also&nbsp;live&nbsp;at<br>
"http://bugzilla.mozilla.org/show_bug.cgi?id=17464",&nbsp;and&nbsp;the&nbsp;change&nbsp;<br>
has&nbsp;been&nbsp;checked&nbsp;in.&nbsp;&nbsp;This&nbsp;is&nbsp;fixed&nbsp;with&nbsp;Bugzilla&nbsp;2.12&nbsp;and&nbsp;is&nbsp;no&nbsp;longer<br>
an&nbsp;issue.&nbsp;&nbsp;Woo-Hoo!</P
></P
></DIV
><DIV
......
docs/html/tinderbox.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Tinderbox</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/trackingbugs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Description Flags and Tracking Bugs</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/translations.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Translations</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,7 +74,8 @@ NAME="TRANSLATIONS"
>1.8. Translations</A
></H1
><P
> The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
> The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<TT
CLASS="EMAIL"
......@@ -82,7 +83,8 @@ CLASS="EMAIL"
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>&#62;</TT
>
>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</P
></DIV
><DIV
......
docs/html/useradmin.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>User Administration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/using.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Using Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -131,6 +131,20 @@ HREF="how.html#QUERY"
HREF="how.html#BUGREPORTS"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>4.3.3.1. <A
HREF="how.html#BUG_WRITING"
>Writing a Great Bug Report</A
></DT
><DT
>4.3.3.2. <A
HREF="how.html#BUG_MANAGE"
>Managing your Bug Reports</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -150,6 +164,25 @@ HREF="init4me.html#ACCOUNTSETTINGS"
HREF="init4me.html#EMAILSETTINGS"
>Email Settings</A
></DT
><DD
><DL
><DT
>4.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
>Email Notification</A
></DT
><DT
>4.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
>New Email Technology</A
></DT
><DT
>4.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>4.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
......
docs/html/usingbz-conc.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Using Bugzilla-Conclusion</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/variants.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Bugzilla Variants</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Cleaning up after mucking with Bugzilla"
HREF="cleanupwork.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
><BODY
CLASS="CHAPTER"
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="cleanupwork.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="rhbugzilla.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="VARIANTS"
>Chapter 7. Bugzilla Variants</A
></H1
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> I <EM
>know</EM
> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</P
></BLOCKQUOTE
></DIV
></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="cleanupwork.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="rhbugzilla.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Cleaning up after mucking with Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Red Hat Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/whatis.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>What is Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -77,11 +77,14 @@ NAME="WHATIS"
> Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</P
......@@ -127,7 +130,8 @@ NAME="WHATIS"
></LI
><LI
><P
> integration with several automated software configuration management systems
> available integration with automated software configuration management systems, including
Perforce and CVS.
</P
></LI
><LI
......@@ -147,6 +151,12 @@ NAME="WHATIS"
no internationalization, and dependence on some nonstandard libraries.
</P
><P
> Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</P
><P
> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
>very</EM
>
......
docs/html/why.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Why Should We Use Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -124,7 +124,7 @@ VALIGN="TOP"
> Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......
docs/sgml/Bugzilla-Guide.sgml
View file @ 2d4d7c92
......@@ -16,6 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
]>
......@@ -58,7 +59,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>v2.11.1, 06 March 2001</PUBDATE>
<PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
......@@ -84,6 +85,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
......@@ -93,6 +95,20 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
2.13 release of the Guide in XML format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<KEYWORDSET>
......@@ -129,6 +145,9 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
<!-- Appendix: The Database Schema -->
&database;
......
docs/sgml/about.sgml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
<CHAPTER ID="about">
<TITLE>About This Guide</TITLE>
......@@ -176,10 +176,15 @@
<SECTION id="contributors">
<TITLE>Contributors</TITLE>
<PARA>
Thanks go to these people for significant contributions to this documentation:
Thanks go to these people for significant contributions
to this documentation (in no particular order):
</PARA>
<PARA>
Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</PARA>
</SECTION>
<SECTION ID="feedback">
......@@ -195,9 +200,11 @@
<SECTION ID="translations">
<TITLE>Translations</TITLE>
<PARA>
The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<email>mozilla-webtools@mozilla.org</email>
<email>mozilla-webtools@mozilla.org</email>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</PARA>
</SECTION>
......
docs/sgml/administration.sgml
View file @ 2d4d7c92
......@@ -30,7 +30,7 @@ Chapter: Administration
<PARA>
So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</PARA>
<SECTION id="postinstall-check">
......@@ -48,6 +48,14 @@ operating parameters for bugzilla.</PARA>
<PROCEDURE>
<STEP>
<PARA>
Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <ULINK URL="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ULINK>, also available under the "edit parameters"
link on your query page.
</PARA>
</STEP>
<STEP>
<PARA>
Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
This allows Bugzilla's error messages
to display your email
......@@ -71,7 +79,7 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -99,18 +107,22 @@ operating parameters for bugzilla.</PARA>
attempting to commit a change to the database.
</PARA>
<PARA>
If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</PARA>
</STEP>
<STEP>
<PARA>
If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<NOTE>
<PARA>
The "headerhtml" text box is the HTML printed out <EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
The "headerhtml" text box is the HTML printed out
<EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</PARA>
</NOTE>
......@@ -125,27 +137,33 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</PARA>
</STEP>
<STEP>
<PARA>
Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</PARA>
</STEP>
<STEP>
<PARA>
Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</PARA>
</STEP>
<STEP>
<PARA>
Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<NOTE>
<PARA>
......@@ -456,9 +474,6 @@ operating parameters for bugzilla.</PARA>
Dear Lord, we have to get our users to do WHAT?
</PARA>
</EPIGRAPH>
<REMARK>
Many thanks to Zach Lipton for his contributions to this section
</REMARK>
<SECTION id="products">
<TITLE>Products</TITLE>
......@@ -1033,15 +1048,17 @@ operating parameters for bugzilla.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</PARA>
<PARA>
On Apache, you can use .htaccess files to protect access to these directories, as outlined
in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
</PARA>
<PARA>
Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -1076,12 +1093,6 @@ operating parameters for bugzilla.</PARA>
</LITERALLAYOUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
......
docs/sgml/database.sgml
View file @ 2d4d7c92
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<APPENDIX id="database">
<TITLE>The Bugzilla Database</TITLE>
<NOTE>
<PARA>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? <REMARK>MPB</REMARK></PARA>
<PARA>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?</PARA>
</NOTE>
<SECTION id="dbschema">
<TITLE>Database Schema Chart</TITLE>
......@@ -405,7 +405,13 @@ http://www.devshed.com/Server_Side/MySQL/
<TITLE>MySQL Permissions & Grant Tables</TITLE>
<NOTE>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</PARA>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</PARA>
</NOTE>
<LITERALLAYOUT>
......@@ -589,7 +595,7 @@ NEW CONTACT INFORMATION:
<SECTION id="cleanupwork">
<TITLE>Cleaning up after mucking with Bugzilla</TITLE>
<LITERALLAYOUT>
Contributed by Eric Hansen:
Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece of
documentation I saw once that said something very important.
1) After pretty much any manual working of the Mysql db, you must
......
docs/sgml/faq.sgml
View file @ 2d4d7c92
......@@ -272,7 +272,14 @@
<qandadiv id="faq_redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
<para>
<emphasis>This section is no longer up-to-date.</emphasis>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</para>
</note>
</para>
<qandaentry>
<question>
<para>
......@@ -430,7 +437,8 @@
<note>
<para>
This information is somewhat dated; I last updated it
7 June 2000.
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</para>
</note>
<emphasis>Dave Lawrence</emphasis>:
......@@ -465,7 +473,7 @@
thing going to help others that may need it.
</para>
<para>
As Matt has mentioned it is still using out-dated code and with a
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
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
......@@ -490,16 +498,21 @@
<qandadiv id="faq_loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<note>
<para>
Loki's "Fenris" Bugzilla is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I left this section of the
FAQ principally for historical interest.
</para>
</note>
<para>
<note>
<para>
Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
tree, and is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I leave this section of the
FAQ principally for historical interest, but unless Loki has further
input into Bugzilla's future, it will be deprecated in future versions
of the Guide.
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -558,12 +571,14 @@
<qandadiv id="faq_phb">
<title>Pointy-Haired-Boss Questions</title>
<note>
<para>
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 :)
</para>
</note>
<para>
<note>
<para>
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 :)
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -1228,7 +1243,7 @@
is unavailable.
</para>
<para>
This is now a configurable parameter called "sendmailparm", available
This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
</para>
</answer>
......@@ -1767,6 +1782,26 @@ A: Sure! Here ya go!
<qandaentry>
<question>
<para>
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</para>
</question>
<answer>
<para>
This is well-documented here: <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=49862">
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
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
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "resolved wontfix",
there may be a better way to handle this...
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
What's the best way to submit patches? What guidelines should I follow?
</para>
</question>
......
docs/sgml/future.sgml
View file @ 2d4d7c92
......@@ -2,7 +2,7 @@
<chapter id="future">
<title>The Future of Bugzilla</title>
<synopsis>This section largely contributed by Matthew Tuck</synopsis>
<synopsis>Bugzilla's Future. Much of this is the present, now.</synopsis>
<section id="spamlite">
<title>Reducing Spam</title>
<para><literallayout>
......@@ -51,6 +51,10 @@ dependency and keyword changes, for example.
Both of these proposals live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
Note that they also live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change
has been checked in. This is fixed with Bugzilla 2.12 and is no longer
an issue. Woo-Hoo!
</literallayout></para>
</section>
......
docs/sgml/installation.sgml
View file @ 2d4d7c92
......@@ -5,31 +5,941 @@
<SECTION id="README.unix">
<TITLE>UNIX Installation</TITLE>
<NOTE>
<PARA>
Please consult the README included with the Bugzilla distribution
as the current canonical source for UNIX installation instructions.
We do, however, have some installation notes for errata from the README.
</PARA>
</NOTE>
<NOTE>
<PARA>
If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
</PARA>
</NOTE>
<NOTE>
<PARA>
</PARA>
</NOTE>
<SECTION>
<TITLE>ERRATA</TITLE>
<NOTE>
<PARA>
If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
</PARA>
</NOTE>
<NOTE>
<PARA>
Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
</PARA>
</NOTE>
<NOTE>
<PARA>
The preferred documentation for Bugzilla is available in docs/, with
a variety of document types available. Please refer to these documents when
installing, configuring, and maintaining your Bugzilla installation.
</PARA>
</NOTE>
<WARNING>
<PARA>
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
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
of third-party utilities. To install Bugzilla on Win32 requires
fair Perl proficiency, and if you use a webserver other than Apache you
should be intimately familiar with the security mechanisms and CGI
environment thereof.
</PARA>
</WARNING>
<WARNING>
<PARA>
Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.
</PARA>
</WARNING>
</SECTION>
<SECTION>
<TITLE>Step-by-step Install</TITLE>
<SECTION>
<TITLE>Introduction</TITLE>
<PARA>
Installation of bugzilla is pretty straightforward, particularly if your
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
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.
</PARA>
<PARA>
Bugzilla has been successfully installed under Solaris, Linux, and
Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
included in this section of the Guide; please check out the "Win32 Installation Instructions"
for further advice on getting Bugzilla to work on Microsoft Windows.
</PARA>
<PARA>
The Bugzilla Guide is contained in the "docs/" folder. It is available
in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</PARA>
</SECTION>
<SECTION>
<TITLE>Installing the Prerequisites</TITLE>
<PARA>
The software packages necessary for the proper running of bugzilla are:
<ORDEREDLIST>
<LISTITEM>
<PARA>
MySQL database server and the mysql client (3.22.5 or greater)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Perl (5.004 or greater)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DBI Perl module
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Data::Dumper Perl module
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DBD::mySQL
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
TimeDate Perl module collection
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
GD perl module (1.8.3) (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Chart::Base Perl module (0.99c) (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DB_File Perl module (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
The web server of your choice. Apache is recommended.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</PARA>
</LISTITEM>
</ORDEREDLIST>
<NOTE>
<PARA>
You must run Bugzilla on a filesystem that supports file locking via
flock(). This is necessary for Bugzilla to operate safely with multiple
instances.
</PARA>
</NOTE>
<WARNING>
<PARA>
It is a good idea, while installing Bugzilla, to ensure it is not
<EMPHASIS>accessible</EMPHASIS> by other machines on the Internet.
Your machine may be vulnerable to attacks
while you are installing. In other words, ensure there is some kind of firewall between you
and the rest of the Internet. Many installation steps require an active Internet connection
to complete, but you must take care to ensure that at no point is your machine vulnerable
to an attack.
</PARA>
</WARNING>
</PARA>
</SECTION>
<SECTION>
<TITLE>Installing MySQL Database</TITLE>
<PARA>
Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
release of the server. Both binaries and source are available and which
you get shouldn't matter. Be aware that many of the binary versions
of MySQL store their data files in /var which on many installations
(particularly common with linux installations) is part of a smaller
root partition. If you decide to build from sources you can easily set
the dataDir as an option to configure.
</PARA>
<PARA>
If you've installed from source or non-package (RPM, deb, etc.) binaries
you'll want to make sure to add mysqld to your init scripts so the server
daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that
mysqld will accept large packets. By default, mysqld is set up to only
accept packets up to 64K long. This limits the size of attachments you
may put on bugs. If you add something like "-O max_allowed_packet=1M"
to the command that starts mysqld (or safe_mysqld), then you will be
able to have attachments up to about 1 megabyte.
</PARA>
<NOTE>
<PARA>
If you plan on running Bugzilla and MySQL on the same machine,
consider using the "--skip-networking" option in the init script.
This enhances security by preventing network access to MySQL.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Perl (5.004 or greater)</TITLE>
<PARA>
Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from http://www.perl.com.
</PARA>
<PARA>
Perl is now a far cry from the the single compiler/interpreter binary it
once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
</PARA>
<TIP>
<PARA>
You can skip the following Perl module installation
steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
All Perl module installation steps require you have an active Internet
connection.
</PARA>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl -MCPAN -e 'install "Bundle::Bugzilla"'</COMMAND>
</COMPUTEROUTPUT>
</PARA>
<PARA>
Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
which are not essential to a basic Bugzilla install. If installing
this bundle fails, you should install each module individually to
isolate the problem.
</PARA>
</TIP>
</SECTION>
<SECTION>
<TITLE>DBI Perl Module</TITLE>
<PARA>
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
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
MakeMaker system simplifies the C compilation greatly.
</PARA>
<PARA>
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
real tendency to bog down, so please use mirrors. The current location
at the time of this writing (02/17/99) can be found in Appendix A.
</PARA>
<PARA>
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
which does all the hard work for you.
</PARA>
<PARA>
To use the CPAN shell to install DBI:
<INFORMALEXAMPLE>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl -MCPAN -e 'install "DBI"'</COMMAND>
</COMPUTEROUTPUT>
<NOTE>
<PARA>Replace "DBI" with the name of whichever module you wish
to install, such as Data::Dumper, TimeDate, GD, etc.</PARA>
</NOTE>
</PARA>
</INFORMALEXAMPLE>
To do it the hard way:
<INFORMALEXAMPLE>
<PARA>
Untar the module tarball -- it should create its own directory
</PARA>
<PARA>
CD to the directory just created, and enter the following commands:
<ORDEREDLIST>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl Makefile.PL</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make test</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make install</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
</ORDEREDLIST>
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
</PARA>
</INFORMALEXAMPLE>
</PARA>
</SECTION>
<SECTION>
<TITLE>Data::Dumper Perl Module</TITLE>
<PARA>
The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
</PARA>
<PARA>
Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
</PARA>
</SECTION>
<SECTION>
<TITLE>MySQL related Perl Module Collection</TITLE>
<PARA>
The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should
be untarred.
</PARA>
<PARA>
The MySQL modules are all built using one make file which is generated
by running:
<PROMPT>bash#</PROMPT>
<COMMAND>perl Makefile.pl</COMMAND>
</PARA>
<PARA>
The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
</PARA>
<PARA>
When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
</PARA>
<PARA>
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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
</PARA>
</SECTION>
<SECTION>
<TITLE>TimeDate Perl Module Collection</TITLE>
<PARA>
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of them
is probably a good idea anyway. The standard Perl module installation
instructions should work perfectly for this simple package.
</PARA>
</SECTION>
<SECTION>
<TITLE>GD Perl Module (1.8.3)</TITLE>
<PARA>
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to generate
graphs on the fly. That's what bugzilla will be using it for so you'd
better install it if you want any of the graphing to work.
</PARA>
<PARA>
Actually bugzilla uses the Graph module which relies on GD itself,
but isn't that always the way with OOP. At any rate, you can find the
GD library on CPAN (link in Appendix "Required Software").
</PARA>
<NOTE>
<PARA>
The Perl GD library requires some other libraries that may or may not be
installed on your system, including "libpng" and "libgd". The full requirements
are listed in the Perl GD library README. Just realize that if compiling GD fails,
it's probably because you're missing a required library.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Chart::Base Perl Module (0.99c)</TITLE>
<PARA>
The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
fetched from CPAN where it is found as the Chart-x.x... tarball in a
directory to be listed in Appendix "Required Software". Note that as with the GD perl
module, only the specific versions listed above (or newer) will work. Earlier
versions used GIF's, which are no longer supported by the latest
versions of GD.
</PARA>
</SECTION>
<SECTION>
<TITLE>DB_File Perl Module</TITLE>
<PARA>
DB_File is a module which allows Perl programs to make use of the facilities provided by
Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
bug charting. If you plan to make use of bug charting, you must install this module.
</PARA>
</SECTION>
<SECTION>
<TITLE>HTTP Server</TITLE>
<PARA>
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a different
machine than MySQL, but need to adjust the MySQL "bugs" user permissions
accordingly.
</PARA>
<PARA>
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. If you're using
apache that means uncommenting the following line in the srm.conf file:
<COMPUTEROUTPUT>AddHandler cgi-script .cgi</COMPUTEROUTPUT>
</PARA>
<PARA>
With apache you'll also want to make sure that within the access.conf
file the line:
<COMPUTEROUTPUT>
Options ExecCGI
</COMPUTEROUTPUT>
is in the stanza that covers the directories you intend to put the bugzilla
.html and .cgi files into.
</PARA>
<PARA>
If you are using a newer version of Apache, both of the above lines will be
(or will need to be) in the httpd.conf file, rather than srm.conf or
access.conf.
</PARA>
<WARNING>
<PARA>
There are two critical directories and a file that should not be a served by
the HTTP server. These are the 'data' and 'shadow' directories and the
'localconfig' file. You should configure your HTTP server to not serve
content from these files. Failure to do so will expose critical passwords
and other data. Please see your HTTP server configuration manual on how
to do this. If you use quips (at the top of the buglist pages) you will want
the 'data/comments' file to still be served. This file contains those quips.
</PARA>
</WARNING>
</SECTION>
<SECTION>
<TITLE>Installing the Bugzilla Files</TITLE>
<PARA>
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directories if they were accidentally tarred up with the rest of Bugzilla)
and make sure you can access the files in that directory through your
web server.
</PARA>
<TIP>
<PARA>
HINT: If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive "Forbidden" errors unless you
add the "FollowSymLinks" directive to the &lt;Directory&gt; entry
for the HTML root.
</PARA>
</TIP>
<PARA>
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable). This is a temporary step until you run
the post-install "checksetup.pl" script, which locks down your
installation.
</PARA>
<PARA>
Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
to the correct location of your perl executable (probably /usr/bin/perl).
Otherwise you must hack all the .cgi files to change where they look
for perl. To make future upgrades easier, you should use the symlink
approach.
<TIP>
<PARA>
If you don't have root access to set this symlink up, check out the
"setperl.csh" utility, listed in the Patches section of this
Guide. It will change the path to perl in all your Bugzilla files for
you.
</PARA>
</TIP>
</PARA>
</SECTION>
<SECTION>
<TITLE>Setting Up the MySQL Database</TITLE>
<PARA>
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
quality bug tracker.
</PARA>
<PARA>
First, you'll want to fix MySQL permissions to allow access from
Bugzilla. For the purpose of this Installation section, the Bugzilla username
will be "bugs", and will have minimal permissions. Bugzilla has
not undergone a thorough security audit. It may be possible for
a system cracker to somehow trick Bugzilla into executing a command
such as "; DROP DATABASE mysql".
</PARA>
<PARA>
That would be bad.
</PARA>
<PARA>
Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>mysql -u root mysql</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>
UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>FLUSH PRIVILEGES;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
From this point on, if you need to access MySQL as the
MySQL root user, you will need to use "mysql -u root -p" and
enter your new_password. Remember that MySQL user names have
nothing to do with Unix user names (login names).
</PARA>
<PARA>
Next, we create the "bugs" user, and grant sufficient
permissions for checksetup.pl, which we'll use later, to work
its magic. This also restricts the "bugs" user to operations
within a database called "bugs", and only allows the account
to connect from "localhost". Modify it to reflect your setup
if you will be connecting from another machine or as a different
user.
</PARA>
<PARA>
Remember to set bugs_password to some unique password.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
IDENTIFIED BY 'bugs_password';</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>
mysql>
</PROMPT>
<COMMAND>
FLUSH PRIVILEGES;
</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
Next, run the magic checksetup.pl script. (Many thanks to Holger
Schurig &lt;holgerschurig@nikocity.de&gt; for writing this script!)
It will make sure Bugzilla files and directories have reasonable
permissions, set up the "data" directory, and create all the MySQL
tables.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>./checksetup.pl</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
The first time you run it, it will create a file called "localconfig".
</PARA>
</SECTION>
<SECTION>
<TITLE>Tweaking "localconfig"</TITLE>
<PARA>
This file contains a variety of settings you may need to tweak including
how Bugzilla should connect to the MySQL database.
</PARA>
<PARA>
The connection settings include:
<ORDEREDLIST>
<LISTITEM>
<PARA>
server's host: just use "localhost" if the MySQL server is
local
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
database name: "bugs" if you're following these directions
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
MySQL username: "bugs" if you're following these directions
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Password for the "bugs" MySQL account above
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
<PARA>
Once you are happy with the settings, re-run checksetup.pl. On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
</PARA>
<PARA>
When logged into an administrator account once Bugzilla is running,
if you go to the query page (off of the bugzilla main menu), you'll
find an 'edit parameters' option that is filled with editable treats.
</PARA>
<PARA>
Should everything work, you should have a nearly empty copy of the bug
tracking setup.
</PARA>
<PARA>
The second time around, checksetup.pl will stall if it is on a
filesystem that does not fully support file locking via flock(), such as
NFS mounts. This support is required for Bugzilla to operate safely with
multiple instances. If flock() is not fully supported, it will stall at:
<ERRORCODE>Now regenerating the shadow database for all bugs.</ERRORCODE>
<NOTE>
<PARA>
The second time you run checksetup.pl, it is recommended you be the same
user as your web server runs under, and that you be sure you have set the
"webservergroup" parameter in localconfig to match the web server's group
name, if any. Under some systems, otherwise, checksetup.pl will goof up
your file permissions and make them unreadable to your web server.
</PARA>
</NOTE>
</PARA>
<NOTE>
<PARA>
The checksetup.pl script is designed so that you can run it at any time
without causing harm. You should run it after any upgrade to Bugzilla.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Setting Up Maintainers Manuall (Optional)</TITLE>
<PARA>
If you want to add someone else to every group by hand, you can do it
by typing the appropriate MySQL commands. Run '<COMPUTEROUTPUT>
mysql -u root -p bugs</COMPUTEROUTPUT>'
(you may need different parameters, depending on your security settings
according to section 3, above). Then:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>update profiles set groupset=0x7fffffffffffffff
where login_name = 'XXX';</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
replacing XXX with the Bugzilla email address.
</PARA>
</SECTION>
<SECTION>
<TITLE>The Whining Cron (Optional)</TITLE>
<PARA>
By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see that
crontab man page):
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<COMMAND>cd &lt;your-bugzilla-directory&gt; ; ./whineatnews.pl</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
</SECTION>
<SECTION>
<TITLE>Bug Graphs (Optional)</TITLE>
<PARA>
As long as you installed the GD and Graph::Base Perl modules you might
as well turn on the nifty bugzilla bug reporting graphs.
</PARA>
<PARA>
Add a cron entry like this to run collectstats daily at 5 after midnight:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>crontab -e</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
5 0 * * * cd &lt;your-bugzilla-directory&gt; ; ./collectstats.pl
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
</PARA>
</SECTION>
<SECTION>
<TITLE>Securing MySQL</TITLE>
<PARA>
If you followed the README for setting up your "bugs" and "root" user in
MySQL, much of this should not apply to you. If you are upgrading
an existing installation of Bugzilla, you should pay close attention
to this section.
</PARA>
<PARA>
Most MySQL installs have "interesting" default security parameters:
<SIMPLELIST>
<MEMBER>mysqld defaults to running as root</MEMBER>
<MEMBER>it defaults to allowing external network connections</MEMBER>
<MEMBER>it has a known port number, and is easy to detect</MEMBER>
<MEMBER>it defaults to no passwords whatsoever</MEMBER>
<MEMBER>it defaults to allowing "File_Priv"</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the system.
</PARA>
<PARA>
To see your permissions do:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>mysql -u root -p</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>use mysql;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>show tables;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>select * from user;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>select * from db;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
To fix the gaping holes:
<SIMPLELIST>
<MEMBER>DELETE FROM user WHERE User='';</MEMBER>
<MEMBER>UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';</MEMBER>
<MEMBER> FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
If you're not running "mit-pthreads" you can use:
<SIMPLELIST>
<MEMBER>GRANT USAGE ON *.* TO bugs@localhost;</MEMBER>
<MEMBER>GRANT ALL ON bugs.* TO bugs@localhost;</MEMBER>
<MEMBER>REVOKE DROP ON bugs.* FROM bugs@localhost;</MEMBER>
<MEMBER>FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
<SIMPLELIST>
<MEMBER>GRANT USAGE ON *.* TO bugs@bounce.hop.com;</MEMBER>
<MEMBER>GRANT ALL ON bugs.* TO bugs@bounce.hop.com;</MEMBER>
<MEMBER>REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;</MEMBER>
<MEMBER>FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
Consider also:
<ORDEREDLIST>
<LISTITEM>
<PARA>
Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
using the --user= option to mysqld to run it as an unprivileged
user.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
starting MySQL in a chroot jail
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
running the httpd in a "chrooted" jail
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
running MySQL on a separate untrusted machine
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
making backups ;-)
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
<SECTION>
<TITLE>Installation General Notes</TITLE>
<SECTION>
<TITLE>Modifying Your Running System</TITLE>
<PARA>
Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory (we said before it needs to be writable,
right?!)
</PARA>
<PARA>
If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't show
up!
</PARA>
<PARA>
That file gets automatically regenerated whenever it's more than an
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.
</PARA>
</SECTION>
<SECTION>
<TITLE>Upgrading From Previous Versions</TITLE>
<PARA>
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
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
changed, you can read the comments in that file, starting from the end.
</PARA>
</SECTION>
<SECTION>
<TITLE>UNIX Installation Instructions History</TITLE>
<PARA>
This document was originally adapted from the Bonsai installation
instructions by Terry Weissman &lt;terry@mozilla.org&gt;.
</PARA>
<PARA>
The February 25, 1999 re-write of this page was done by Ry4an Brase
&lt;ry4an@ry4an.org&gt;, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, & Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
</PARA>
<PARA>
This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
</PARA>
<PARA>
Finally, the README in its entirety was marked up in SGML and included into
the Guide on April 24, 2001.
</PARA>
<PARA>
Comments from people using this Guide for the first time are particularly welcome.
</PARA>
</SECTION>
</SECTION>
</SECTION>
</SECTION>
<SECTION id="README.windows">
......@@ -320,6 +1230,71 @@
</BLOCKQUOTE>
</PARA>
</TIP>
<TIP>
<PARA>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</PARA>
<BLOCKQUOTE>
<PARA>
Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
deleted the current dir and copied the files in).
</PARA>
<PARA>
In checksetup.pl, I did the following...
</PARA>
<PROCEDURE>
<STEP>
<PROGRAMLISTING>
my $webservergid = getgrnam($my_webservergroup);
</PROGRAMLISTING>
<PARA>to</PARA>
<PROGRAMLISTING>
my $webservergid = 'Administrators'
</PROGRAMLISTING>
</STEP>
<STEP>
<PARA>
I then ran checksetup.pl
</PARA>
</STEP>
<STEP>
<PARA>
I removed all the encrypt()
<EXAMPLE>
<TITLE>Removing encrypt() for Windows NT installations</TITLE>
<PARA>
Replace this:
<PROGRAMLISTING>
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PROGRAMLISTING>
with this:
<PROGRAMLISTING>
my $enteredcryptpwd = $enteredpwd
</PROGRAMLISTING>
in cgi.pl.
</PARA>
</EXAMPLE>
</PARA>
</STEP>
<STEP>
<PARA>
I renamed processmail to processmail.pl
</PARA>
</STEP>
<STEP>
<PARA>
I altered the sendmail statements to windmail:
<PROGRAMLISTING>
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
</PROGRAMLISTING>
</PARA>
<PARA>
The quotes around the dir is for the spaces. mail.log is for the output
</PARA>
</STEP>
</PROCEDURE>
</BLOCKQUOTE>
</TIP>
</SECTION>
</SECTION>
</CHAPTER>
......
docs/sgml/integration.sgml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
<!-- Keep these tools listings in alphabetical order please. -MPB -->
......@@ -18,10 +18,31 @@
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby and his team have an integration tool
in public beta. You can find it at
<ulink url="http://www.ravenbrook.com/project/p4dt">
http://www.ravenbrook.com/project/p4dti</ulink>.
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</para>
</section>
......
docs/sgml/patches.sgml
View file @ 2d4d7c92
......@@ -4,15 +4,17 @@
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<title>The setperl.pl Utility</title>
<title>The setperl.csh Utility</title>
<para>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</para>
<procedure>
<step>
<para>
Download the "setperl.pl" utility to your Bugzilla
Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</para>
<substeps>
......@@ -28,7 +30,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
</para>
</step>
......@@ -36,7 +38,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.pl</command>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para>
</step>
......@@ -80,8 +82,17 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.pl /your/path/to/perl</command>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
</para>
</step>
</procedure>
......@@ -206,4 +217,21 @@
</para>
</section>
</appendix>
\ No newline at end of file
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/sgml/readme.sgml deleted 100644 → 0
View file @ 064f6ba6
This is Bugzilla. See <http://www.mozilla.org/bugs/>.
==========
DISCLAIMER
==========
This is not very well packaged code. It's not packaged at all. Don't
come here expecting something you plop in a directory, twiddle a few
things, and you're off and using it. Work has to be done to get there.
We'd like to get there, but it wasn't clear when that would be, and so we
decided to let people see it first.
Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.
============
INSTALLATION
============
0. Introduction
Installation of bugzilla is pretty straight forward, especially if your
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
other necessary ingredient is a web server set up to run cgi scripts.
Bugzilla has been successfully installed under Solaris and Linux. Windows NT
is not officially supported. There have been a few successful installations
of Bugzilla under Windows NT. Please see this article for a discussion of what
one person hacked together to get it to work.
news://news.mozilla.org/19990913183810.SVTR29939.mta02@onebox.com
1. Installing the Prerequisites
The software packages necessary for the proper running of bugzilla are:
1. MySQL database server and the mysql client (3.22.5 or greater)
2. Perl (5.004 or greater)
3. DBI Perl module
4. Data::Dumper Perl module
5. MySQL related Perl module collection
6. TimeDate Perl module collection
7. GD perl module (1.18 or 1.19)
8. Chart::Base Perl module (0.99 through 0.99b)
9. The web server of your choice
Bugzilla has quite a few prerequisites, but none of them are TCL.
Previous versions required TCL, but it no longer needed (or used).
1.1. Getting and setting up MySQL database (3.22.5 or greater)
Visit MySQL homepage at http://www.mysql.org and grab the latest stable
release of the server. Both binaries and source are available and which
you get shouldn't matter. Be aware that many of the binary versions
of MySQL store their data files in /var which on many installations
(particularly common with linux installations) is part of a smaller
root partition. If you decide to build from sources you can easily set
the dataDir as an option to configure.
If you've installed from source or non-package (RPM, deb, etc.) binaries
you'll want to make sure to add mysqld to your init scripts so the server
daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that
mysqld will accept large packets. By default, mysqld is set up to only
accept packets up to 64K long. This limits the size of attachments you
may put on bugs. If you add something like "-O max_allowed_packet=1M"
to the command that starts mysqld (or safe_mysqld), then you will be
able to have attachments up to about 1 megabyte.
1.2. Perl (5.004 or greater)
Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from http://www.perl.com.
Perl is now a far cry from the the single compiler/interpreter binary it
once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
1.3. DBI Perl module
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
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
MakeMaker system simplifies the C compilation greatly.
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
real tendency to bog down, so please use mirrors. The current location
at the time of this writing (02/17/99) can be found in Appendix A.
Quality, general Perl module installation instructions can be found on
the CPAN website, but basically you'll just need to:
1. Untar the module tarball -- it should create its own directory
2. Enter the following commands:
perl Makefile.PL
make
make test
make install
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
1.4 Data::Dumper Perl module
The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
1.5. MySQL related Perl module collection
The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN (link
in Appendix A). After the archive file has been downloaded it should
be untarred.
The MySQL modules are all build using one make file which is generated
by running:
perl Makefile.PL
The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
1.6. TimeDate Perl module collection
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of them
is probably a good idea anyway. The standard Perl module installation
instructions should work perfectly for this simple package.
1.7. GD Perl module (1.18 or 1.19)
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to generate
graphs on the fly. That's what bugzilla will be using it for so you'd
better install it if you want any of the graphing to work.
Actually bugzilla uses the Graph module which relies on GD itself,
but isn't that always the way with OOP. At any rate, you can find the
GD library on CPAN (link in Appendix A). Note, however, that you MUST
use version 1.18 or 1.19, because newer versions have dropped support
for GIFs in favor of PNGs, and bugzilla has not yet been updated to
deal with this.
1.8. Chart::Base Perl module (0.99 through 0.99b)
The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
fetched from CPAN where it is found as the Chart-x.x... tarball in a
directory to be listed in Appendix A. Note that as with the GD perl
module, only the specific versions listed above will work.
1.9. HTTP server
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a different
machine than MySQL, but that makes MySQL permissions harder to manage.
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. If you're using
apache that means uncommenting the following line in the srm.conf file:
AddHandler cgi-script .cgi
With apache you'll also want to make sure that within the access.conf
file the line:
Options ExecCGI
is in the stanza that covers the directories you intend to put the
bugzilla .html and .cgi files into.
2. Installing the Bugzilla Files
You should untar the bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directory if it accidentally got tarred up with the rest of bugzilla)
and make sure you can get at the files in that directory through your
web server.
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable).
Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
to the correct location of your perl executable (probably /usr/bin/perl).
Or, you'll have to hack all the .cgi files to change where they look
for perl.
3. Setting Up the MySQL database
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
quality bug tracker.
First, you'll want to fix MySQL permissions. Bugzilla always logs
in as user "bugs", with no password. That needs to work. MySQL
permissions are a deep, nasty complicated thing. I've just turned
them off. If you want to do that, too, then the magic is to do run
"mysql mysql", and feed it commands like this (replace all instances of
HOSTNAME with the name of the machine mysql is running on):
DELETE FROM host;
DELETE FROM user;
INSERT INTO host VALUES
('localhost','%','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
INSERT INTO host VALUES
(HOSTNAME,'%','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
INSERT INTO user VALUES
('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y',
'Y','Y','Y','Y','Y');
INSERT INTO user VALUES
(HOSTNAME,'','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
'Y','Y','Y');
INSERT INTO user VALUES
(HOSTNAME,'root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
'Y','Y','Y','Y');
INSERT INTO user VALUES
('localhost','','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
'Y','Y','Y','Y');
The number of 'Y' entries to use varies with the version of MySQL; they
keep adding columns. The list here should work with version 3.22.23b.
This run of "mysql mysql" may need some extra parameters to deal with
whatever database permissions were set up previously. In particular,
you might have to say "mysql -uroot mysql", and give it an appropriate
password.
For much more information about MySQL permissions, see the MySQL
documentation.
After you've tweaked the permissions, run "mysqladmin reload" to make
sure that the database server knows to look at your new permission list.
Or, at the mysql prompt:
mysql> flush privileges;
You must explictly tell mysql to reload permissions before running checksetup.pl.
Next, you can just run the magic checksetup.pl script. (Many thanks
to Holger Schurig <holgerschurig@nikocity.de> for writing this script!)
It will make sure things have reasonable permissions, set up the "data"
directory, and create all the MySQL tables. Just run:
./checksetup.pl
The first time you run it, it will create a file called "localconfig"
which you should examine and perhaps tweak a bit. Then re-run
checksetup.pl and it will do the real work.
At ths point, you should have a nearly empty copy of the bug tracking
setup.
4. Tweaking the Bugzilla->MySQL Connection Data
If you have played with MySQL permissions, rather than just opening it
wide open as described above, then you may need to tweak the Bugzilla
code to connect appropriately.
In order for bugzilla to be able to connect to the MySQL database
you'll have to tell bugzilla where the database server is, what
database you're connecting to, and whom to connect as. Simply open up
the globals.pl file in the bugzilla directory and find the line that
begins like:
$::db = Mysql->Connect("
That line does the actual database connection. The Connect method
takes four parameters which are (with appropriate values):
1. server's host: just use "localhost"
2. database name: "bugs" if you're following these directions
3. MySQL username: whatever you created for your webserver user
probably "nobody"
4. Password for the MySQL account in item 3.
Just fill in those values and close up globals.pl
5. Setting up yourself as Maintainer
Start by creating your own bugzilla account. To do so, just try to
"add a bug" from the main bugzilla menu (now available from your system
through your web browser!). You'll be prompted for logon info, and you
should enter your email address and then select 'mail me my password'.
When you get the password mail, log in with it. Don't finish entering
that new bug.
Now, add yourself to every group. The magic checksetup.pl script
can do this for you, if you run it again now. That script will notice
if there's exactly one user in the database, and if so, add that person
to every group.
If you want to add someone to every group by hand, you can do it by
typing the appropriate MySQL commands. Run mysql, and type:
update profiles set groupset=0x7fffffffffffffff
where login_name = 'XXX';
replacing XXX with your Bugzilla email address.
Now, if you go to the query page (off of the bugzilla main menu) where
you'll now find a 'edit parameters' option which is filled with editable
treats.
6. Setting Up the Whining Cron Job (Optional)
By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see that
crontab man page):
cd <your-bugzilla-directory> ; ./whineatnews.pl
7. Bug Graphs (Optional)
As long as you installed the GD and Graph::Base Perl modules you might
as well turn on the nifty bugzilla bug reporting graphs. Just add
the command:
cd <your-bugzilla-directory> ; ./collectstats.pl
as a nightly entry to your crontab and after two days have passed you'll
be able to view bug graphs from the Bug Reports page.
8. Real security for MySQL
MySQL has "interesting" default security parameters:
mysqld defaults to running as root
it defaults to allowing external network connections
it has a known port number, and is easy to detect
it defaults to no passwords whatsoever
it defaults to allowing "File_Priv"
This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the system.
To see your permissions do:
> mysql -u root -p
use mysql;
show tables;
select * from user;
select * from db;
To fix the gaping holes:
DELETE FROM user WHERE User='';
UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
FLUSH PRIVILEGES;
If you're not running "mit-pthreads" you can use:
GRANT USAGE ON *.* TO bugs@localhost;
GRANT ALL ON bugs.* TO bugs@localhost;
REVOKE DROP ON bugs.* FROM bugs@localhost;
FLUSH PRIVILEGES;
With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
GRANT USAGE ON *.* TO bugs@bounce.hop.com;
GRANT ALL ON bugs.* TO bugs@bounce.hop.com;
REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;
FLUSH PRIVILEGES;
Consider also:
o Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
o using the --user= option to mysqld to run it as an unprivileged
user.
o starting MySQL in a chroot jail
o running the httpd in a jail
o making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
o running MySQL on a separate untrusted machine
o making backups ;-)
---------[ Appendices ]-----------------------
Appendix A. Required Software Download Links
All of these sites are current as of February 17, 1999. Hopefully
they'll stay current for a while.
MySQL: http://www.mysql.org
Perl: http://www.perl.org
CPAN: http://www.cpan.org
DBI Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
Data::Dumper module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
MySQL related Perl modules:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
TimeDate Perl module collection:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
Chart::Base module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
Appendix B. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory (we said before it needs to be writable,
right?!)
If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't show
up!
That file gets automatically regenerated whenever it's more than an
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.
Appendix C. Upgrading from previous versions of Bugzilla
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
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
changed, you can read the comments in that file, starting from the end.
Appendix D. History
This document was originally adapted from the Bonsai installation
instructions by Terry Weissman <terry@mozilla.org>.
The February 25, 1999 re-write of this page was done by Ry4an Brase
<ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, & Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
Comments from people using this document for the first time are
especially welcomed.
docs/sgml/requiredsoftware.sgml 0 → 100644
View file @ 2d4d7c92
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<appendix id="downloadlinks">
<title>Software Download Links</title>
<para>
All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</para>
<para>
Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</para>
<para>
Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/">
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.org/">http://www.mysql.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
DBI Perl module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</ulink>
</para>
<para>
Data::Dumper module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</ulink>
</para>
<para>
MySQL related Perl modules:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</ulink>
</para>
<para>
TimeDate Perl module collection:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</ulink>
</para>
<para>
GD Perl module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of
GD at <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
</para>
<para>
Chart::Base module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</ulink>
</para>
<para>
LinuxDoc Software:
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink>
(for documentation maintenance)
</para>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/sgml/using.sgml
View file @ 2d4d7c92
......@@ -41,11 +41,14 @@ Chapter: Using Bugzilla
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</para>
......@@ -89,7 +92,8 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
integration with several automated software configuration management systems
available integration with automated software configuration management systems, including
Perforce and CVS.
</para>
</listitem>
<listitem>
......@@ -108,6 +112,12 @@ Chapter: Using Bugzilla
no internationalization, and dependence on some nonstandard libraries.
</para>
<para>
Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</para>
<para>
Despite these small problems, Bugzilla is very hard to beat. It is under <emphasis>very</emphasis>
active development to address the current issues, and a long-awaited overhaul in the form
of Bugzilla 3.0 is expected sometime later this year.
......@@ -147,7 +157,7 @@ Chapter: Using Bugzilla
Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......@@ -178,7 +188,7 @@ Chapter: Using Bugzilla
</epigraph>
<para>
Bugzilla is a large and complex system. Describing how to use it
Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -190,11 +200,24 @@ Chapter: Using Bugzilla
options available at the Bugzilla test installation,
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
<note>
<para>
Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <ulink url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
</para>
</note>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</para>
<section id="myaccount">
......@@ -714,6 +737,14 @@ Chapter: Using Bugzilla
<title>Email Settings</title>
<section id="notification">
<title>Email Notification</title>
<note>
<para>
The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</para>
</note>
<para>
Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/sgml/variants.sgml
View file @ 2d4d7c92
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<section id="rhbugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>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 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 with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/txt/Bugzilla-Guide.txt
View file @ 2d4d7c92
......@@ -4,6 +4,26 @@ The Bugzilla Guide
Matthew P. Barnson
barnboy@trilobyte.net
Revision History
Revision v2.11 20 December 2000 Revised by: MPB
Converted the README, FAQ, and DATABASE information into SGML docbook
format.
Revision 2.11.1 06 March 2001 Revised by: MPB
Took way too long to revise this for 2.12 release. Updated FAQ to use
qandaset tags instead of literallayout, cleaned up administration
section, added User Guide section, miscellaneous FAQ updates and
third-party integration information. From this point on all new tags
are lowercase in preparation for the 2.13 release of the Guide in XML
format instead of SGML.
Revision 2.12.0 24 April 2001 Revised by: MPB
Things fixed this release: Elaborated on queryhelp interface, added
FAQ regarding moving bugs from one keyword to another, clarified
possible problems with the Landfill tutorial, fixed a boatload of
typos and unclear sentence structures. Incorporated the README into
the UNIX installation section, and changed the README to indicate the
deprecated status. Things I know need work: Used "simplelist" a lot,
where I should have used "procedure" to tag things. Need to lowercase
all tags to be XML compliant.
This is the documentation for Bugzilla, the Mozilla bug-tracking
system.
......@@ -25,13 +45,58 @@ Matthew P. Barnson
2. Installing Bugzilla
2.1. UNIX Installation
2.1.1. ERRATA
2.1.2. Step-by-step Install
2.1.2.1. Introduction
2.1.2.2. Installing the Prerequisites
2.1.2.3. Installing MySQL Database
2.1.2.4. Perl (5.004 or greater)
2.1.2.5. DBI Perl Module
2.1.2.6. Data::Dumper Perl Module
2.1.2.7. MySQL related Perl Module Collection
2.1.2.8. TimeDate Perl Module Collection
2.1.2.9. GD Perl Module (1.8.3)
2.1.2.10. Chart::Base Perl Module (0.99c)
2.1.2.11. DB_File Perl Module
2.1.2.12. HTTP Server
2.1.2.13. Installing the Bugzilla Files
2.1.2.14. Setting Up the MySQL Database
2.1.2.15. Tweaking "localconfig"
2.1.2.16. Setting Up Maintainers Manuall (Optional)
2.1.2.17. The Whining Cron (Optional)
2.1.2.18. Bug Graphs (Optional)
2.1.2.19. Securing MySQL
2.1.2.20. Installation General Notes
2.2. Win32 (Win98+/NT/2K) Installation
2.2.1. Win32 Installation: Step-by-step
2.2.2. Additional Windows Tips
3. Administering Bugzilla
3.1. Post-Installation Checklist
3.2. User Administration
3.2.1. Creating the Default User
3.2.2. Managing Other Users
3.2.2.1. Logging In
3.2.2.2. Creating new users
3.2.2.3. Disabling Users
3.2.2.4. Modifying Users
3.3. Product, Component, Milestone, and Version Administration
3.3.1. Products
3.3.2. Components
3.3.3. Versions
3.3.4. Milestones
3.3.5. Voting
3.3.6. Groups and Group Security
3.4. Bugzilla Security
4. Using Bugzilla
......@@ -39,7 +104,26 @@ Matthew P. Barnson
4.1. What is Bugzilla?
4.2. Why Should We Use Bugzilla?
4.3. How do I use Bugzilla?
4.3.1. Create a Bugzilla Account
4.3.2. The Bugzilla Query Page
4.3.3. Creating and Managing Bug Reports
4.3.3.1. Writing a Great Bug Report
4.3.3.2. Managing your Bug Reports
4.4. What's in it for me?
4.4.1. Account Settings
4.4.2. Email Settings
4.4.2.1. Email Notification
4.4.2.2. New Email Technology
4.4.2.3. "Watching" Users
4.4.3. Page Footer
4.4.4. Permissions
4.5. Using Bugzilla-Conclusion
5. Integrating Bugzilla with Third-Party Tools
......@@ -59,20 +143,25 @@ Matthew P. Barnson
6.6. Bugzilla 3.0
A. The Bugzilla FAQ
B. The Bugzilla Database
B. Software Download Links
C. The Bugzilla Database
C.1. Database Schema Chart
C.2. MySQL Bugzilla Database Introduction
C.3. MySQL Permissions & Grant Tables
C.4. Cleaning up after mucking with Bugzilla
B.1. Database Schema Chart
B.2. MySQL Bugzilla Database Introduction
B.3. MySQL Permissions & Grant Tables
B.4. Cleaning up after mucking with Bugzilla
7. Bugzilla Variants
C. Useful Patches and Utilities for Bugzilla
7.1. Red Hat Bugzilla
C.1. The setperl.pl Utility
C.2. Command-line Bugzilla Queries
C.3. The Quicksearch Utility
D. Useful Patches and Utilities for Bugzilla
D. GNU Free Documentation License
D.1. The setperl.csh Utility
D.2. Command-line Bugzilla Queries
D.3. The Quicksearch Utility
E. GNU Free Documentation License
0. PREAMBLE
1. APPLICABILITY AND DEFINITIONS
......@@ -90,6 +179,7 @@ Matthew P. Barnson
Glossary
List of Examples
2-1. Removing encrypt() for Windows NT installations
3-1. Creating some Components
3-2. Common Use of Versions
3-3. A Different Use of Versions
......@@ -98,7 +188,10 @@ Matthew P. Barnson
3-6. Creating a New Group
4-1. Some Famous Software Versions
4-2. Mozilla Webtools Components
D-1. Using Setperl to set your perl path
1. A Sample Product
] >
_________________________________________________________________
Chapter 1. About This Guide
......@@ -233,9 +326,10 @@ Chapter 1. About This Guide
1.6. Contributors
Thanks go to these people for significant contributions to this
documentation:
documentation (in no particular order):
Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
Zach Lipton (significant textual contributions), Andrew Pearson,
Spencer Smith, Eric Hanson, Kevin Brannen,
_________________________________________________________________
1.7. Feedback
......@@ -251,7 +345,9 @@ Chapter 1. About This Guide
The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will translate
this Guide, please notify the members of the mozilla-webtools mailing
list at <mozilla-webtools@mozilla.org>
list at <mozilla-webtools@mozilla.org>. Since The Bugzilla Guide is
also hosted on the Linux Documentation Project, you would also do well
to notify
_________________________________________________________________
1.9. Document Conventions
......@@ -294,10 +390,7 @@ Chapter 2. Installing Bugzilla
2.1. UNIX Installation
Note: Please consult the README included with the Bugzilla
distribution as the current canonical source for UNIX installation
instructions. We do, however, have some installation notes for
errata from the README.
2.1.1. ERRATA
Note: If you are installing Bugzilla on S.u.S.e. Linux, or some
other distributions with "paranoid" security options, it is
......@@ -306,7 +399,588 @@ Chapter 2. Installing Bugzilla
your /var/spool/mqueue directory has a mode of "drwx------". Type
chmod 755 /var/spool/mqueue as root to fix this problem.
Note:
Note: Release Notes for Bugzilla 2.12 are available at
docs/rel_notes.txt
Note: The preferred documentation for Bugzilla is available in
docs/, with a variety of document types available. Please refer to
these documents when installing, configuring, and maintaining your
Bugzilla installation.
Warning
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
know your variant of UNIX or Microsoft Windows well, are familiar with
the command line, and are comfortable compiling and installing a
plethora of third-party utilities. To install Bugzilla on Win32
requires fair Perl proficiency, and if you use a webserver other than
Apache you should be intimately familiar with the security mechanisms
and CGI environment thereof.
Warning
Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the
installation and usage of this software. Carefully consider the
implications of installing other network services with Bugzilla.
_________________________________________________________________
2.1.2. Step-by-step Install
2.1.2.1. Introduction
Installation of bugzilla is pretty straightforward, particularly if
your 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 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.
Bugzilla has been successfully installed under Solaris, Linux, and
Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
included in this section of the Guide; please check out the "Win32
Installation Instructions" for further advice on getting Bugzilla to
work on Microsoft Windows.
The Bugzilla Guide is contained in the "docs/" folder. It is available
in plain text (docs/txt), HTML (docs/html), or SGML source
(docs/sgml).
_________________________________________________________________
2.1.2.2. Installing the Prerequisites
The software packages necessary for the proper running of bugzilla
are:
1. MySQL database server and the mysql client (3.22.5 or greater)
2. Perl (5.004 or greater)
3. DBI Perl module
4. Data::Dumper Perl module
5. DBD::mySQL
6. TimeDate Perl module collection
7. GD perl module (1.8.3) (optional, for bug charting)
8. Chart::Base Perl module (0.99c) (optional, for bug charting)
9. DB_File Perl module (optional, for bug charting)
10. The web server of your choice. Apache is recommended.
11. MIME::Parser Perl module (optional, for contrib/bug_email.pl
interface)
Note: You must run Bugzilla on a filesystem that supports file
locking via flock(). This is necessary for Bugzilla to operate
safely with multiple instances.
Warning
It is a good idea, while installing Bugzilla, to ensure it is not
accessible by other machines on the Internet. Your machine may be
vulnerable to attacks while you are installing. In other words, ensure
there is some kind of firewall between you and the rest of the
Internet. Many installation steps require an active Internet
connection to complete, but you must take care to ensure that at no
point is your machine vulnerable to an attack.
_________________________________________________________________
2.1.2.3. Installing MySQL Database
Visit MySQL homepage at http://www.mysql.org/ and grab the latest
stable release of the server. Both binaries and source are available
and which you get shouldn't matter. Be aware that many of the binary
versions of MySQL store their data files in /var which on many
installations (particularly common with linux installations) is part
of a smaller root partition. If you decide to build from sources you
can easily set the dataDir as an option to configure.
If you've installed from source or non-package (RPM, deb, etc.)
binaries you'll want to make sure to add mysqld to your init scripts
so the server daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that mysqld
will accept large packets. By default, mysqld is set up to only accept
packets up to 64K long. This limits the size of attachments you may
put on bugs. If you add something like "-O max_allowed_packet=1M" to
the command that starts mysqld (or safe_mysqld), then you will be able
to have attachments up to about 1 megabyte.
Note: If you plan on running Bugzilla and MySQL on the same
machine, consider using the "--skip-networking" option in the init
script. This enhances security by preventing network access to
MySQL.
_________________________________________________________________
2.1.2.4. Perl (5.004 or greater)
Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from
http://www.perl.com.
Perl is now a far cry from the the single compiler/interpreter binary
it once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
Tip: You can skip the following Perl module installation steps by
installing "Bundle::Bugzilla" from CPAN, which includes them. All
Perl module installation steps require you have an active Internet
connection.
bash# perl -MCPAN -e 'install "Bundle::Bugzilla"'
Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
which are not essential to a basic Bugzilla install. If installing
this bundle fails, you should install each module individually to
isolate the problem.
_________________________________________________________________
2.1.2.5. DBI Perl Module
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
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
MakeMaker system simplifies the C compilation greatly.
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 real tendency to bog down, so please use mirrors. The current
location at the time of this writing (02/17/99) can be found in
Appendix A.
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 which does all the hard work for you.
To use the CPAN shell to install DBI:
bash# perl -MCPAN -e 'install "DBI"'
Note: Replace "DBI" with the name of whichever module you wish to
install, such as Data::Dumper, TimeDate, GD, etc.
To do it the hard way:
Untar the module tarball -- it should create its own directory
CD to the directory just created, and enter the following commands:
1. bash# perl Makefile.PL
2. bash# make
3. bash# make test
4. bash# make install
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
_________________________________________________________________
2.1.2.6. Data::Dumper Perl Module
The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
_________________________________________________________________
2.1.2.7. MySQL related Perl Module Collection
The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN. After
the archive file has been downloaded it should be untarred.
The MySQL modules are all built using one make file which is generated
by running: bash# perl Makefile.pl
The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the
questions the provided default will be adequate.
When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
_________________________________________________________________
2.1.2.8. TimeDate Perl Module Collection
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of
them is probably a good idea anyway. The standard Perl module
installation instructions should work perfectly for this simple
package.
_________________________________________________________________
2.1.2.9. GD Perl Module (1.8.3)
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to
generate graphs on the fly. That's what bugzilla will be using it for
so you'd better install it if you want any of the graphing to work.
Actually bugzilla uses the Graph module which relies on GD itself, but
isn't that always the way with OOP. At any rate, you can find the GD
library on CPAN (link in Appendix "Required Software").
Note: The Perl GD library requires some other libraries that may or
may not be installed on your system, including "libpng" and
"libgd". The full requirements are listed in the Perl GD library
README. Just realize that if compiling GD fails, it's probably
because you're missing a required library.
_________________________________________________________________
2.1.2.10. Chart::Base Perl Module (0.99c)
The Chart module provides bugzilla with on-the-fly charting abilities.
It can be installed in the usual fashion after it has been fetched
from CPAN where it is found as the Chart-x.x... tarball in a directory
to be listed in Appendix "Required Software". Note that as with the GD
perl module, only the specific versions listed above (or newer) will
work. Earlier versions used GIF's, which are no longer supported by
the latest versions of GD.
_________________________________________________________________
2.1.2.11. DB_File Perl Module
DB_File is a module which allows Perl programs to make use of the
facilities provided by Berkeley DB version 1.x. This module is
required by collectstats.pl which is used for bug charting. If you
plan to make use of bug charting, you must install this module.
_________________________________________________________________
2.1.2.12. HTTP Server
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a
different machine than MySQL, but need to adjust the MySQL "bugs" user
permissions accordingly.
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. If you're using
apache that means uncommenting the following line in the srm.conf
file: AddHandler cgi-script .cgi
With apache you'll also want to make sure that within the access.conf
file the line: Options ExecCGI is in the stanza that covers the
directories you intend to put the bugzilla .html and .cgi files into.
If you are using a newer version of Apache, both of the above lines
will be (or will need to be) in the httpd.conf file, rather than
srm.conf or access.conf.
Warning
There are two critical directories and a file that should not be a
served by the HTTP server. These are the 'data' and 'shadow'
directories and the 'localconfig' file. You should configure your HTTP
server to not serve content from these files. Failure to do so will
expose critical passwords and other data. Please see your HTTP server
configuration manual on how to do this. If you use quips (at the top
of the buglist pages) you will want the 'data/comments' file to still
be served. This file contains those quips.
_________________________________________________________________
2.1.2.13. Installing the Bugzilla Files
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directories if they were accidentally tarred up with the rest of
Bugzilla) and make sure you can access the files in that directory
through your web server.
Tip: HINT: If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive "Forbidden" errors unless you add
the "FollowSymLinks" directive to the <Directory> entry for the
HTML root.
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable). This is a temporary step until you run the
post-install "checksetup.pl" script, which locks down your
installation.
Lastly, you'll need to set up a symbolic link from
/usr/bonsaitools/bin to the correct location of your perl executable
(probably /usr/bin/perl). Otherwise you must hack all the .cgi files
to change where they look for perl. To make future upgrades easier,
you should use the symlink approach.
Tip: If you don't have root access to set this symlink up, check
out the "setperl.csh" utility, listed in the Patches section of
this Guide. It will change the path to perl in all your Bugzilla
files for you.
_________________________________________________________________
2.1.2.14. Setting Up the MySQL Database
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 quality bug tracker.
First, you'll want to fix MySQL permissions to allow access from
Bugzilla. For the purpose of this Installation section, the Bugzilla
username will be "bugs", and will have minimal permissions. Bugzilla
has not undergone a thorough security audit. It may be possible for a
system cracker to somehow trick Bugzilla into executing a command such
as "; DROP DATABASE mysql".
That would be bad.
Give the MySQL root user a password. MySQL passwords are limited to 16
characters.
bash# mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE
user='root';
mysql> FLUSH PRIVILEGES;
From this point on, if you need to access MySQL as the MySQL root
user, you will need to use "mysql -u root -p" and enter your
new_password. Remember that MySQL user names have nothing to do with
Unix user names (login names).
Next, we create the "bugs" user, and grant sufficient permissions for
checksetup.pl, which we'll use later, to work its magic. This also
restricts the "bugs" user to operations within a database called
"bugs", and only allows the account to connect from "localhost".
Modify it to reflect your setup if you will be connecting from another
machine or as a different user.
Remember to set bugs_password to some unique password.
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
'bugs_password';
mysql> FLUSH PRIVILEGES;
Next, run the magic checksetup.pl script. (Many thanks to Holger
Schurig <holgerschurig@nikocity.de> for writing this script!) It will
make sure Bugzilla files and directories have reasonable permissions,
set up the "data" directory, and create all the MySQL tables.
bash# ./checksetup.pl
The first time you run it, it will create a file called "localconfig".
_________________________________________________________________
2.1.2.15. Tweaking "localconfig"
This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.
The connection settings include:
1. server's host: just use "localhost" if the MySQL server is local
2. database name: "bugs" if you're following these directions
3. MySQL username: "bugs" if you're following these directions
4. Password for the "bugs" MySQL account above
Once you are happy with the settings, re-run checksetup.pl. On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
When logged into an administrator account once Bugzilla is running, if
you go to the query page (off of the bugzilla main menu), you'll find
an 'edit parameters' option that is filled with editable treats.
Should everything work, you should have a nearly empty copy of the bug
tracking setup.
The second time around, checksetup.pl will stall if it is on a
filesystem that does not fully support file locking via flock(), such
as NFS mounts. This support is required for Bugzilla to operate safely
with multiple instances. If flock() is not fully supported, it will
stall at: Now regenerating the shadow database for all bugs.
Note: The second time you run checksetup.pl, it is recommended you
be the same user as your web server runs under, and that you be
sure you have set the "webservergroup" parameter in localconfig to
match the web server's group name, if any. Under some systems,
otherwise, checksetup.pl will goof up your file permissions and
make them unreadable to your web server.
Note: The checksetup.pl script is designed so that you can run it
at any time without causing harm. You should run it after any
upgrade to Bugzilla.
_________________________________________________________________
2.1.2.16. Setting Up Maintainers Manuall (Optional)
If you want to add someone else to every group by hand, you can do it
by typing the appropriate MySQL commands. Run ' mysql -u root -p bugs'
(you may need different parameters, depending on your security
settings according to section 3, above). Then:
mysql> update profiles set groupset=0x7fffffffffffffff where
login_name = 'XXX';
replacing XXX with the Bugzilla email address.
_________________________________________________________________
2.1.2.17. The Whining Cron (Optional)
By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see
that crontab man page):
cd <your-bugzilla-directory> ; ./whineatnews.pl
_________________________________________________________________
2.1.2.18. Bug Graphs (Optional)
As long as you installed the GD and Graph::Base Perl modules you might
as well turn on the nifty bugzilla bug reporting graphs.
Add a cron entry like this to run collectstats daily at 5 after
midnight:
bash# crontab -e
5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
_________________________________________________________________
2.1.2.19. Securing MySQL
If you followed the README for setting up your "bugs" and "root" user
in MySQL, much of this should not apply to you. If you are upgrading
an existing installation of Bugzilla, you should pay close attention
to this section.
Most MySQL installs have "interesting" default security parameters:
mysqld defaults to running as root
it defaults to allowing external network connections
it has a known port number, and is easy to detect
it defaults to no passwords whatsoever
it defaults to allowing "File_Priv"
This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the
system.
To see your permissions do:
bash# mysql -u root -p
mysql> use mysql;
mysql> show tables;
mysql> select * from user;
mysql> select * from db;
To fix the gaping holes:
DELETE FROM user WHERE User='';
UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
FLUSH PRIVILEGES;
If you're not running "mit-pthreads" you can use:
GRANT USAGE ON *.* TO bugs@localhost;
GRANT ALL ON bugs.* TO bugs@localhost;
REVOKE DROP ON bugs.* FROM bugs@localhost;
FLUSH PRIVILEGES;
With "mit-pthreads" you'll need to modify the "globals.pl"
Mysql->Connect line to specify a specific host name instead of
"localhost", and accept external connections:
GRANT USAGE ON *.* TO bugs@bounce.hop.com;
GRANT ALL ON bugs.* TO bugs@bounce.hop.com;
REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;
FLUSH PRIVILEGES;
Consider also:
1. Turning off external networking with "--skip-networking", unless
you have "mit-pthreads", in which case you can't. Without
networking, MySQL connects with a Unix domain socket.
2. using the --user= option to mysqld to run it as an unprivileged
user.
3. starting MySQL in a chroot jail
4. running the httpd in a "chrooted" jail
5. making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
6. running MySQL on a separate untrusted machine
7. making backups ;-)
_________________________________________________________________
2.1.2.20. Installation General Notes
2.1.2.20.1. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/
subdirectory under your installation directory (we said before it
needs to be writable, right?!)
If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't
show up!
That file gets automatically regenerated whenever it's more than an
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.
_________________________________________________________________
2.1.2.20.2. Upgrading From Previous Versions
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 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 changed, you can read the comments in that file, starting
from the end.
_________________________________________________________________
2.1.2.20.3. UNIX Installation Instructions History
This document was originally adapted from the Bonsai installation
instructions by Terry Weissman <terry@mozilla.org>.
The February 25, 1999 re-write of this page was done by Ry4an Brase
<ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, & Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at
http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools,
component Bugzilla).
This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
Finally, the README in its entirety was marked up in SGML and included
into the Guide on April 24, 2001.
Comments from people using this Guide for the first time are
particularly welcome.
_________________________________________________________________
2.2. Win32 (Win98+/NT/2K) Installation
......@@ -430,6 +1104,50 @@ Chapter 2. Installing Bugzilla
The KB article only talks about .pl, but it goes into more detail
and provides a perl test script.
Tip: "Brian" had this to add, about upgrading to Bugzilla 2.12 from
previous versions:
Hi - I am updating bugzilla to 2.12 so I can tell you what I did
(after I deleted the current dir and copied the files in).
In checksetup.pl, I did the following...
1.
my $webservergid = getgrnam($my_webservergroup);
to
my $webservergid = 'Administrators'
2. I then ran checksetup.pl
3. I removed all the encrypt()
Example 2-1. Removing encrypt() for Windows NT installations
Replace this:
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
with this:
my $enteredcryptpwd = $enteredpwd
in cgi.pl.
4. I renamed processmail to processmail.pl
5. I altered the sendmail statements to windmail:
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.
log";
The quotes around the dir is for the spaces. mail.log is for the
output
_________________________________________________________________
Chapter 3. Administering Bugzilla
......@@ -440,7 +1158,7 @@ Chapter 3. Administering Bugzilla
So you followed the README isntructions to the letter, and just logged
into bugzilla with your super-duper god account and you are sitting at
the query screen. Yet, you have nothing to query. Your first act of
bisuness needs to be to setup the operating parameters for bugzilla.
business needs to be to setup the operating parameters for bugzilla.
_________________________________________________________________
3.1. Post-Installation Checklist
......@@ -449,22 +1167,25 @@ Chapter 3. Administering Bugzilla
a successful installation. If you do not see a recommended setting for
a parameter, consider leaving it at the default while you perform your
initial tests on your Bugzilla setup.
1. Set "maintainer" to your email address. This allows Bugzilla's
1. Bring up "editparams.cgi" in your web browser. For instance, to
edit parameters at mozilla.org, the URL would be
http://bugzilla.mozilla.org/editparams.cgi, also available under
the "edit parameters" link on your query page.
2. Set "maintainer" to your email address. This allows Bugzilla's
error messages to display your email address and allow people to
contact you for help.
2. Set "urlbase" to the URL reference for your Bugzilla installation.
3. Set "urlbase" to the URL reference for your Bugzilla installation.
If your bugzilla query page is at
http://www.foo.com/bugzilla/query.cgi, your url base is
http://www.foo.com/bugzilla/
3. Set "usebuggroups" to "1" only if you need to restrict access to
4. Set "usebuggroups" to "1" only if you need to restrict access to
products. I suggest leaving this parameter off while initially
testing your Bugzilla.
4. Set "usebuggroupsentry" to "1" if you want to be able to restrict
access to products. Once again, if you are simply testing your
installation, I suggest against turning this parameter on; the
strict security checking may stop you from being able to modify
your new entries.
5. Set "shadowdb" to "bug_shadowdb" if you will be running a *very*
5. Set "usebuggroupsentry" to "1" if you want to restrict access to
products. Once again, if you are simply testing your installation,
I suggest against turning this parameter on; the strict security
checking may stop you from being able to modify your new entries.
6. Set "shadowdb" to "bug_shadowdb" if you will be running a *very*
large installation of Bugzilla. The shadow database enables many
simultaneous users to read and write to the database without
interfering with one another.
......@@ -480,7 +1201,7 @@ Chapter 3. Administering Bugzilla
should turn the "queryagainstshadowdb" option "On" as well.
Otherwise you are replicating data into a shadow database for no
reason!
6. If you have custom logos or HTML you must put in place to fit
7. If you have custom logos or HTML you must put in place to fit
within your site design guidelines, place the code in the
"headerhtml", "footerhtml", "errorhtml", "bannerhtml", or
"blurbhtml" text boxes.
......@@ -489,22 +1210,23 @@ Chapter 3. Administering Bugzilla
other code on the page. If you have a special banner, put the code
for it in "bannerhtml". You may want to leave these settings at the
defaults initially.
7. Add any text you wish to the "passwordmail" parameter box. For
8. Add any text you wish to the "passwordmail" parameter box. For
instance, many people choose to use this box to give a quick
training blurb about how to use Bugzilla at your site.
8. Set "newemailtech" to "on". Your users will thank you. This is the
default in the post-2.12 world.
9. Do you want to use the qa contact ("useqacontact") and status
9. Ensure "newemailtech" is "on". Your users will thank you. This is
the default in the post-2.12 world, and is only an issue if you
are upgrading.
10. Do you want to use the qa contact ("useqacontact") and status
whiteboard ("usestatuswhiteboard") fields? These fields are useful
because they allow for more flexibility, particularly when you
have an existing Quality Assurance and/or Release Engineering
team, but they may not be needed for smaller installations.
10. Set "whinedays" to the amount of days you want to let bugs go in
11. Set "whinedays" to the amount of days you want to let bugs go in
the "New" or "Reopened" state before notifying people they have
untouched new bugs. If you do not plan to use this feature, simply
do not set up the whining cron job described in the README, or set
this value to "0".
11. Set the "commenton" options according to your site policy. It is a
12. Set the "commenton" options according to your site policy. It is a
wise idea to require comments when users resolve, reassign, or
reopen bugs.
......@@ -513,7 +1235,7 @@ Chapter 3. Administering Bugzilla
database users than having a developer mark a bug "fixed" without
any comment as to what the fix was (or even that it was truly
fixed!)
12. Set "supportwatchers" to "On". This feature is helpful for team
13. Set "supportwatchers" to "On". This feature is helpful for team
leads to monitor progress in their respective areas, and can offer
many other benefits, such as allowing a developer to pick up a
former engineer's bugs without requiring her to change all the
......@@ -1065,11 +1787,11 @@ Chapter 3. Administering Bugzilla
4. Do not run Apache as "nobody". This will require very lax
permissions in your Bugzilla directories. Run it, instead, as a
user with a name, set via your httpd.conf file.
5. Ensure you have adequate access controls for $BUGZILLA_HOME/data/
and $BUGZILLA_HOME/localconfig. The localconfig file stores your
"bugs" user password, which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store
sensitive information.
5. Ensure you have adequate access controls for $BUGZILLA_HOME/data/,
$BUGZILLA_HOME/localconfig, and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password, which would
be terrible to have in the hands of a criminal. Also some files
under $BUGZILLA_HOME/data store sensitive information.
On Apache, you can use .htaccess files to protect access to these
directories, as outlined in Bug 57161 for the localconfig file,
and Bug 65572 for adequate protection in your data/ and shadow/
......@@ -1095,8 +1817,6 @@ Chapter 3. Administering Bugzilla
Place the following text into a file named ".htaccess", readable
by your web server, in your $BUGZILLA_HOME/shadow directory.
deny from all
6.
_________________________________________________________________
Chapter 4. Using Bugzilla
......@@ -1111,15 +1831,15 @@ Chapter 4. Using Bugzilla
Bugzilla is one example of a class of programs called "Defect Tracking
Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
Systems allow individual or groups of developers to keep track of
outstanding bugs in their product effectively. At the time Bugzilla
was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors
in the market for bug-tracking software. Most commercial
defect-tracking software vendors at the time charged enormous
licensing fees. Bugzilla quickly became a favorite of the open-source
crowd (with its genesis in the open-source browser project, Mozilla)
and is now the de-facto standard defect-tracking system against which
all others are measured.
outstanding bugs in their product effectively. Bugzilla was originally
written by Terry Weissman in a programming language called "TCL", to
replace a crappy bug-tracking database used internally for Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in
Perl it remains to this day. Most commercial defect-tracking software
vendors at the time charged enormous licensing fees, and Bugzilla
quickly became a favorite of the open-source crowd (with its genesis
in the open-source browser project, Mozilla). It is now the de-facto
standard defect-tracking system against which all others are measured.
Bugzilla has matured immensely, and now boasts many advanced features.
These include:
......@@ -1132,8 +1852,8 @@ Chapter 4. Using Bugzilla
* a very well-understood and well-thought-out natural bug resolution
protocol
* email, XML, and HTTP APIs
* integration with several automated software configuration
management systems
* available integration with automated software configuration
management systems, including Perforce and CVS.
* too many more features to list
Despite its current robustness and popularity, however, Bugzilla faces
......@@ -1144,6 +1864,12 @@ Chapter 4. Using Bugzilla
queries, some unsupportable bug resolution options, no
internationalization, and dependence on some nonstandard libraries.
Some recent headway has been made on the query front, however. If you
are using the latest version of Bugzilla, you should see a "simple
search" form on the default front page of your Bugzilla install. Type
in two or three search terms and you should pull up some relevant
information. This is also available as "queryhelp.cgi".
Despite these small problems, Bugzilla is very hard to beat. It is
under very active development to address the current issues, and a
long-awaited overhaul in the form of Bugzilla 3.0 is expected sometime
......@@ -1179,11 +1905,11 @@ Chapter 4. Using Bugzilla
Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment
management, chip design and development problem tracking (both
pre-and-post fabrication), and software bug tracking for luminaries
such as Redhat, Loki software, Linux-Mandrake, and VA Systems.
Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
provides a powerful, easy-to-use solution to configuration management
and replication problems
pre-and-post fabrication), and software and hardware bug tracking for
luminaries such as Redhat, Loki software, Linux-Mandrake, and VA
Systems. Combined with systems such as CVS, Bonsai, or Perforce SCM,
Bugzilla provides a powerful, easy-to-use solution to configuration
management and replication problems
Bugzilla can dramatically increase the productivity and accountability
of individual employees by providing a documented workflow and
......@@ -1206,21 +1932,33 @@ Chapter 4. Using Bugzilla
Hey! I'm Woody! Howdy, Howdy, Howdy!
Bugzilla is a large and complex system. Describing how to use it
requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the Installing
and Administering Bugzilla portions of this Guide. This section is
principally aimed towards developing end-user mastery of Bugzilla, so
you may fully enjoy the benefits afforded by using this reliable
open-source bug-tracking software.
Bugzilla is a large, complex system. Describing how to use it requires
some time. If you are only interested in installing or administering a
Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed
towards developing end-user mastery of Bugzilla, so you may fully
enjoy the benefits afforded by using this reliable open-source
bug-tracking software.
Throughout this portion of the Guide, we will refer to user account
options available at the Bugzilla test installation,
landfill.tequilarista.org. Although Landfill serves as a great
introduction to Bugzilla, it does not offer all the options you would
have as a user on your own installation of Bugzilla, nor can it do
more than serve as a general introduction to Bugzilla. However, please
use it if you want to follow this tutorial.
landfill.tequilarista.org.
Note: Some people have run into difficulties completing this
tutorial. If you run into problems, please check the updated,
online documentation available at
http://www.trilobyte.net/barnsons. If you're still stumped, please
subscribe to the newsgroup and provide details of exactly what's
stumping you! If enough people complain, I'll have to fix it in the
next version of this Guide. You can subscribe to the newsgroup at
news://news.mozilla.org/netscape.public.mozilla.webtools
Although Landfill serves as a great introduction to Bugzilla, it does
not offer all the options you would have as a user on your own
installation of Bugzilla, nor can it do more than serve as a general
introduction to Bugzilla. Additionally, Landfill often runs
cutting-edge versions of Bugzilla for testing, so some things may work
slightly differently than mentioned here.
_________________________________________________________________
4.3.1. Create a Bugzilla Account
......@@ -1551,6 +2289,13 @@ Chapter 4. Using Bugzilla
4.4.2.1. Email Notification
Note: The email notification settings described below have been
obsoleted in Bugzilla 2.12, and this section will be replaced with
a comprehensive description of the amazing array of new options at
your disposal. However, in the meantime, throw this chunk out the
window and go crazy with goofing around with different notification
options.
Ahh, here you can reduce or increase the amount of email sent you from
Bugzilla! In the drop-down "Notify me of changes to", select one of
......@@ -1666,8 +2411,30 @@ Chapter 5. Integrating Bugzilla with Third-Party Tools
5.3. Perforce SCM
Richard Brooksby and his team have an integration tool in public beta.
You can find it at http://www.ravenbrook.com/project/p4dti.
Richard Brooksby created a Perforce integration tool for Bugzilla and
TeamTrack. You can find the main project page at
http://www.ravenbrook.com/project/p4dti. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public
Depot" p4dti page at
http://public.perforce.com/public/perforce/p4dti/index.html.
Integration of Perforce with Bugzilla, once patches are applied, is
fairly seamless. However, p4dti is a patch against the Bugzilla 2.10
release, not the current 2.12 release. I anticipate patches for 2.12
will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to
support multiple defect trackers, and maintains its own documentation
for it. Please consult the pages linked above for further information.
Right now, there is no way to synchronize the Bug ID and the Perforce
Transaction Number, or to change the Bug ID to read (PRODUCT).bugID
unless you hack it in. Additionally, if you have synchronization
problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce
change records. They will link anyway; merely reference the bug ID
fixed in your change description, and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process
issue, not a technology question.
_________________________________________________________________
5.4. Tinderbox
......@@ -1677,7 +2444,7 @@ Chapter 5. Integrating Bugzilla with Third-Party Tools
Chapter 6. The Future of Bugzilla
This section largely contributed by Matthew Tuck
Bugzilla's Future. Much of this is the present, now.
_________________________________________________________________
6.1. Reducing Spam
......@@ -1724,6 +2491,11 @@ Chapter 6. The Future of Bugzilla
dependency and keyword changes, for example.
Both of these proposals live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
Note that they also live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change
has been checked in. This is fixed with Bugzilla 2.12 and is no longe
r
an issue. Woo-Hoo!
_________________________________________________________________
6.2. Better Searching
......@@ -2188,7 +2960,11 @@ Appendix A. The Bugzilla FAQ
11. Bugzilla Hacking
A.11.1. What bugs are in Bugzilla right now?
A.11.2. What's the best way to submit patches? What guidelines
A.11.2. How can I change the default priority to a null value?
For instance, have the default priority be "---" instead
of "P2"?
A.11.3. What's the best way to submit patches? What guidelines
should I follow?
1. General Questions
......@@ -2341,6 +3117,9 @@ Appendix A. The Bugzilla FAQ
2. Red Hat Bugzilla
Note: This section is no longer up-to-date. Please see the section
on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
A.2.1. What about Red Hat Bugzilla?
Red Hat Bugzilla is arguably more user-friendly, customizable, and
......@@ -2434,7 +3213,8 @@ Appendix A. The Bugzilla FAQ
A.2.3. What's the current status of Red Hat Bugzilla?
Note: This information is somewhat dated; I last updated it 7 June
2000.
2000. Please see the "Variants" section of "The Bugzilla Guide" for
more up-to-date information regarding Red Hat Bugzilla.
Dave Lawrence:
......@@ -2484,11 +3264,14 @@ Appendix A. The Bugzilla FAQ
3. Loki Bugzilla (AKA Fenris)
Note: Loki's "Fenris" Bugzilla is no longer actively maintained. It
works well enough for Loki. Additionally, the major differences in
Fenris have now been integrated into the main source tree of
Bugzilla, so there's not much reason to go grab the source. I left
this section of the FAQ principally for historical interest.
Note: Loki's "Fenris" Bugzilla is based upon the (now ancient)
Bugzilla 2.8 tree, and is no longer actively maintained. It works
well enough for Loki. Additionally, the major differences in Fenris
have now been integrated into the main source tree of Bugzilla, so
there's not much reason to go grab the source. I leave this section
of the FAQ principally for historical interest, but unless Loki has
further input into Bugzilla's future, it will be deprecated in
future versions of the Guide.
A.3.1. What about Loki Bugzilla?
......@@ -2835,7 +3618,7 @@ Appendix A. The Bugzilla FAQ
Bugzilla Perl processes if the domain to which it must send mail is
unavailable.
This is now a configurable parameter called "sendmailparm", available
This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
A.7.7. How come email never reaches me from bugzilla changes?
......@@ -3160,7 +3943,19 @@ Appendix A. The Bugzilla FAQ
to check current sources out of CVS so you can have these bug fixes
early!
A.11.2. What's the best way to submit patches? What guidelines should
A.11.2. How can I change the default priority to a null value? For
instance, have the default priority be "---" instead of "P2"?
This is well-documented here:
http://bugzilla.mozilla.org/show_bug.cgi?id=49862. Ultimately, it's as
easy 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 "editparams.cgi". Hmm, now that
I think about it, that is kind of a klunky way to handle it, but for
now it's what we have! Although the bug has been closed "resolved
wontfix", there may be a better way to handle this...
A.11.3. What's the best way to submit patches? What guidelines should
I follow?
1. Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
......@@ -3185,21 +3980,60 @@ Appendix A. The Bugzilla FAQ
successful open-source bug-tracking software on the planet :)
_________________________________________________________________
Appendix B. The Bugzilla Database
Appendix B. Software Download Links
All of these sites are current as of April, 2001. Hopefully they'll
stay current for a while.
Apache Web Server: http://www.apache.org Optional web server for
Bugzilla, but recommended because of broad user base and support.
Bugzilla: http://www.mozilla.org/projects/bugzilla/
MySQL: http://www.mysql.org/
Perl: http://www.perl.org/
CPAN: http://www.cpan.org/
DBI Perl module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
Data::Dumper module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
MySQL related Perl modules:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
TimeDate Perl module collection:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
Alternately, you should be able to find the latest version of GD at
http://www.boutell.com/gd/
Chart::Base module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
LinuxDoc Software: http://www.linuxdoc.org/ (for documentation
maintenance)
_________________________________________________________________
Appendix C. The Bugzilla Database
Note: 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?
_________________________________________________________________
B.1. Database Schema Chart
C.1. Database Schema Chart
Database Relationships
Bugzilla database relationships chart
_________________________________________________________________
B.2. MySQL Bugzilla Database Introduction
C.2. MySQL Bugzilla Database Introduction
Contributor(s): Matthew P. Barnson (mbarnson@excitehome.net)
Last update: May 16, 2000
......@@ -3609,12 +4443,12 @@ B.2. MySQL Bugzilla Database Introduction
http://www.devshed.com/Server_Side/MySQL/
_________________________________________________________________
B.3. MySQL Permissions & Grant Tables
C.3. MySQL Permissions & Grant Tables
Note: The following portion of documentation comes from my answer
to an old discussion of Keynote, a cool product that does
to an old discussion of Keystone, a cool product that does
trouble-ticket tracking for IT departments. I wrote this post to
the Keynote support group regarding MySQL grant table permissions,
the Keystone support group regarding MySQL grant table permissions,
and how to use them effectively. It is badly in need of updating,
as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and
......@@ -3810,9 +4644,9 @@ B.3. MySQL Permissions & Grant Tables
(801)234-8300
_________________________________________________________________
B.4. Cleaning up after mucking with Bugzilla
C.4. Cleaning up after mucking with Bugzilla
Contributed by Eric Hansen:
Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece
of
documentation I saw once that said something very important.
......@@ -3833,28 +4667,105 @@ B.4. Cleaning up after mucking with Bugzilla
in localconfig pertaining to bug_status, this point is mainly a FYI.
_________________________________________________________________
Appendix C. Useful Patches and Utilities for Bugzilla
Chapter 7. Bugzilla Variants
Note: I know there are more variants than just RedHat Bugzilla out
there. Please help me get information about them, their project
status, and benefits there might be in using them or in using their
code in main-tree Bugzilla.
_________________________________________________________________
7.1. Red Hat Bugzilla
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside
from Mozilla Bugzilla, on the planet. One of the major benefits of Red
Hat Bugzilla is the ability to work with Oracle as a database, as well
as MySQL. Here's what Dave Lawrence had to say about the status of Red
Hat Bugzilla,
Hello. I apologize that I am getting back to you so late. It has
been difficult to keep
up with email this past week. I have checked out your updated docum
entation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>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 in the code its
elf. 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 with other projects relating to Red Hat web
sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text
::Template for most
of the html rendering. You actually state this later in your number
ed list.
Also number 6 contradicts number 8 where number 6 would be the most
up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If
the comment is more
than 4k it is broken up into chunks and given a sort number so each
comment can be re
assembled in the correct order. This was done because originally I
was storing the comments
in a long datatype which unfortunately cannot be indexed or joined
with another table. This
cause the search of text within the long description to be disabled
for a long time. That
is now working and is nto showing any noticeble performance hit tha
t I can tell.
2. Work is being started on internationalizing the Bugzilla source
we have to allow our
Japanese customers to enter bug reports into a single bugzilla syst
em. This will probably
be done by using the nvarchar data types supported by Oracle which
allows storage of
double byte characters and also the use of the Accept-Language in t
he http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up
with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. A
nd more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. P
lease contact
me if you have any more question or I can do anything else.
Regards
_________________________________________________________________
Appendix D. Useful Patches and Utilities for Bugzilla
C.1. The setperl.pl Utility
D.1. The setperl.csh Utility
You can use the "setperl.pl" utility to quickly and easily change the
path to perl on all your Bugzilla files.
1. Download the "setperl.pl" utility to your Bugzilla directory and
You can use the "setperl.csh" utility to quickly and easily change the
path to perl on all your Bugzilla files. This is a C-shell script; if
you do not have "csh" or "tcsh" in the search path on your system, it
will not work!
1. Download the "setperl.csh" utility to your Bugzilla directory and
make it executable.
a. bash# cd /your/path/to/bugzilla
b. bash# wget -O setperl.pl
b. bash# wget -O setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=107
95'
c. bash# chmod u+x setperl.pl
c. bash# chmod u+x setperl.csh
2. Prepare (and fix) Bugzilla file permissions.
a. bash# chmod u+w *
b. bash# chmod u+x duplicates.cgi
c. bash# chmod a-x bug_status.html
3. Run the script:
bash# ./setperl.pl /your/path/to/perl
bash# ./setperl.csh /your/path/to/perl
Example D-1. Using Setperl to set your perl path
bash# ./setperl.csh /usr/bin/perl
_________________________________________________________________
C.2. Command-line Bugzilla Queries
D.2. Command-line Bugzilla Queries
Users can query Bugzilla from the command line using this suite of
utilities.
......@@ -3897,7 +4808,7 @@ C.2. Command-line Bugzilla Queries
2. Make your utilities executable: bash$ chmod u+x buglist bugs
_________________________________________________________________
C.3. The Quicksearch Utility
D.3. The Quicksearch Utility
Quicksearch is a new, experimental feature of the 2.12 release. It
consist of two Javascript files, "quicksearch.js" and
......@@ -3928,7 +4839,7 @@ C.3. The Quicksearch Utility
has details.
_________________________________________________________________
Appendix D. GNU Free Documentation License
Appendix E. GNU Free Documentation License
Version 1.1, March 2000
......
docs/xml/Bugzilla-Guide.xml
View file @ 2d4d7c92
......@@ -16,6 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
]>
......@@ -58,7 +59,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>v2.11.1, 06 March 2001</PUBDATE>
<PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
......@@ -84,6 +85,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
......@@ -93,6 +95,20 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
2.13 release of the Guide in XML format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<KEYWORDSET>
......@@ -129,6 +145,9 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
<!-- Appendix: The Database Schema -->
&database;
......
docs/xml/about.xml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
<CHAPTER ID="about">
<TITLE>About This Guide</TITLE>
......@@ -176,10 +176,15 @@
<SECTION id="contributors">
<TITLE>Contributors</TITLE>
<PARA>
Thanks go to these people for significant contributions to this documentation:
Thanks go to these people for significant contributions
to this documentation (in no particular order):
</PARA>
<PARA>
Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</PARA>
</SECTION>
<SECTION ID="feedback">
......@@ -195,9 +200,11 @@
<SECTION ID="translations">
<TITLE>Translations</TITLE>
<PARA>
The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<email>mozilla-webtools@mozilla.org</email>
<email>mozilla-webtools@mozilla.org</email>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</PARA>
</SECTION>
......
docs/xml/administration.xml
View file @ 2d4d7c92
......@@ -30,7 +30,7 @@ Chapter: Administration
<PARA>
So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</PARA>
<SECTION id="postinstall-check">
......@@ -48,6 +48,14 @@ operating parameters for bugzilla.</PARA>
<PROCEDURE>
<STEP>
<PARA>
Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <ULINK URL="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ULINK>, also available under the "edit parameters"
link on your query page.
</PARA>
</STEP>
<STEP>
<PARA>
Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
This allows Bugzilla's error messages
to display your email
......@@ -71,7 +79,7 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -99,18 +107,22 @@ operating parameters for bugzilla.</PARA>
attempting to commit a change to the database.
</PARA>
<PARA>
If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</PARA>
</STEP>
<STEP>
<PARA>
If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<NOTE>
<PARA>
The "headerhtml" text box is the HTML printed out <EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
The "headerhtml" text box is the HTML printed out
<EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</PARA>
</NOTE>
......@@ -125,27 +137,33 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</PARA>
</STEP>
<STEP>
<PARA>
Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</PARA>
</STEP>
<STEP>
<PARA>
Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</PARA>
</STEP>
<STEP>
<PARA>
Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<NOTE>
<PARA>
......@@ -456,9 +474,6 @@ operating parameters for bugzilla.</PARA>
Dear Lord, we have to get our users to do WHAT?
</PARA>
</EPIGRAPH>
<REMARK>
Many thanks to Zach Lipton for his contributions to this section
</REMARK>
<SECTION id="products">
<TITLE>Products</TITLE>
......@@ -1033,15 +1048,17 @@ operating parameters for bugzilla.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</PARA>
<PARA>
On Apache, you can use .htaccess files to protect access to these directories, as outlined
in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
</PARA>
<PARA>
Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -1076,12 +1093,6 @@ operating parameters for bugzilla.</PARA>
</LITERALLAYOUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
......
docs/xml/database.xml
View file @ 2d4d7c92
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<APPENDIX id="database">
<TITLE>The Bugzilla Database</TITLE>
<NOTE>
<PARA>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? <REMARK>MPB</REMARK></PARA>
<PARA>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?</PARA>
</NOTE>
<SECTION id="dbschema">
<TITLE>Database Schema Chart</TITLE>
......@@ -405,7 +405,13 @@ http://www.devshed.com/Server_Side/MySQL/
<TITLE>MySQL Permissions & Grant Tables</TITLE>
<NOTE>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</PARA>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</PARA>
</NOTE>
<LITERALLAYOUT>
......@@ -589,7 +595,7 @@ NEW CONTACT INFORMATION:
<SECTION id="cleanupwork">
<TITLE>Cleaning up after mucking with Bugzilla</TITLE>
<LITERALLAYOUT>
Contributed by Eric Hansen:
Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece of
documentation I saw once that said something very important.
1) After pretty much any manual working of the Mysql db, you must
......
docs/xml/faq.xml
View file @ 2d4d7c92
......@@ -272,7 +272,14 @@
<qandadiv id="faq_redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
<para>
<emphasis>This section is no longer up-to-date.</emphasis>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</para>
</note>
</para>
<qandaentry>
<question>
<para>
......@@ -430,7 +437,8 @@
<note>
<para>
This information is somewhat dated; I last updated it
7 June 2000.
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</para>
</note>
<emphasis>Dave Lawrence</emphasis>:
......@@ -465,7 +473,7 @@
thing going to help others that may need it.
</para>
<para>
As Matt has mentioned it is still using out-dated code and with a
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
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
......@@ -490,16 +498,21 @@
<qandadiv id="faq_loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<note>
<para>
Loki's "Fenris" Bugzilla is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I left this section of the
FAQ principally for historical interest.
</para>
</note>
<para>
<note>
<para>
Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
tree, and is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I leave this section of the
FAQ principally for historical interest, but unless Loki has further
input into Bugzilla's future, it will be deprecated in future versions
of the Guide.
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -558,12 +571,14 @@
<qandadiv id="faq_phb">
<title>Pointy-Haired-Boss Questions</title>
<note>
<para>
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 :)
</para>
</note>
<para>
<note>
<para>
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 :)
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -1228,7 +1243,7 @@
is unavailable.
</para>
<para>
This is now a configurable parameter called "sendmailparm", available
This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
</para>
</answer>
......@@ -1767,6 +1782,26 @@ A: Sure! Here ya go!
<qandaentry>
<question>
<para>
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</para>
</question>
<answer>
<para>
This is well-documented here: <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=49862">
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
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
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "resolved wontfix",
there may be a better way to handle this...
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
What's the best way to submit patches? What guidelines should I follow?
</para>
</question>
......
docs/xml/installation.xml
View file @ 2d4d7c92
......@@ -5,31 +5,941 @@
<SECTION id="README.unix">
<TITLE>UNIX Installation</TITLE>
<NOTE>
<PARA>
Please consult the README included with the Bugzilla distribution
as the current canonical source for UNIX installation instructions.
We do, however, have some installation notes for errata from the README.
</PARA>
</NOTE>
<NOTE>
<PARA>
If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
</PARA>
</NOTE>
<NOTE>
<PARA>
</PARA>
</NOTE>
<SECTION>
<TITLE>ERRATA</TITLE>
<NOTE>
<PARA>
If you are installing Bugzilla on S.u.S.e. Linux, or some other
distributions with "paranoid" security options, it is possible
that the checksetup.pl script may fail with the error:
<ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
This is because your
/var/spool/mqueue directory has a mode of "drwx------". Type
<COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
</PARA>
</NOTE>
<NOTE>
<PARA>
Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
</PARA>
</NOTE>
<NOTE>
<PARA>
The preferred documentation for Bugzilla is available in docs/, with
a variety of document types available. Please refer to these documents when
installing, configuring, and maintaining your Bugzilla installation.
</PARA>
</NOTE>
<WARNING>
<PARA>
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
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
of third-party utilities. To install Bugzilla on Win32 requires
fair Perl proficiency, and if you use a webserver other than Apache you
should be intimately familiar with the security mechanisms and CGI
environment thereof.
</PARA>
</WARNING>
<WARNING>
<PARA>
Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.
</PARA>
</WARNING>
</SECTION>
<SECTION>
<TITLE>Step-by-step Install</TITLE>
<SECTION>
<TITLE>Introduction</TITLE>
<PARA>
Installation of bugzilla is pretty straightforward, particularly if your
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
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.
</PARA>
<PARA>
Bugzilla has been successfully installed under Solaris, Linux, and
Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
included in this section of the Guide; please check out the "Win32 Installation Instructions"
for further advice on getting Bugzilla to work on Microsoft Windows.
</PARA>
<PARA>
The Bugzilla Guide is contained in the "docs/" folder. It is available
in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
</PARA>
</SECTION>
<SECTION>
<TITLE>Installing the Prerequisites</TITLE>
<PARA>
The software packages necessary for the proper running of bugzilla are:
<ORDEREDLIST>
<LISTITEM>
<PARA>
MySQL database server and the mysql client (3.22.5 or greater)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Perl (5.004 or greater)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DBI Perl module
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Data::Dumper Perl module
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DBD::mySQL
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
TimeDate Perl module collection
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
GD perl module (1.8.3) (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Chart::Base Perl module (0.99c) (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
DB_File Perl module (optional, for bug charting)
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
The web server of your choice. Apache is recommended.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
</PARA>
</LISTITEM>
</ORDEREDLIST>
<NOTE>
<PARA>
You must run Bugzilla on a filesystem that supports file locking via
flock(). This is necessary for Bugzilla to operate safely with multiple
instances.
</PARA>
</NOTE>
<WARNING>
<PARA>
It is a good idea, while installing Bugzilla, to ensure it is not
<EMPHASIS>accessible</EMPHASIS> by other machines on the Internet.
Your machine may be vulnerable to attacks
while you are installing. In other words, ensure there is some kind of firewall between you
and the rest of the Internet. Many installation steps require an active Internet connection
to complete, but you must take care to ensure that at no point is your machine vulnerable
to an attack.
</PARA>
</WARNING>
</PARA>
</SECTION>
<SECTION>
<TITLE>Installing MySQL Database</TITLE>
<PARA>
Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
release of the server. Both binaries and source are available and which
you get shouldn't matter. Be aware that many of the binary versions
of MySQL store their data files in /var which on many installations
(particularly common with linux installations) is part of a smaller
root partition. If you decide to build from sources you can easily set
the dataDir as an option to configure.
</PARA>
<PARA>
If you've installed from source or non-package (RPM, deb, etc.) binaries
you'll want to make sure to add mysqld to your init scripts so the server
daemon will come back up whenever your machine reboots.
You also may want to edit those init scripts, to make sure that
mysqld will accept large packets. By default, mysqld is set up to only
accept packets up to 64K long. This limits the size of attachments you
may put on bugs. If you add something like "-O max_allowed_packet=1M"
to the command that starts mysqld (or safe_mysqld), then you will be
able to have attachments up to about 1 megabyte.
</PARA>
<NOTE>
<PARA>
If you plan on running Bugzilla and MySQL on the same machine,
consider using the "--skip-networking" option in the init script.
This enhances security by preventing network access to MySQL.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Perl (5.004 or greater)</TITLE>
<PARA>
Any machine that doesn't have perl on it is a sad machine indeed. Perl
for *nix systems can be gotten in source form from http://www.perl.com.
</PARA>
<PARA>
Perl is now a far cry from the the single compiler/interpreter binary it
once was. It now includes a great many required modules 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 it on your machine using some
sort of packaging system (be it RPM, deb, or what have you) to ensure
a sane install. In the subsequent sections you'll be installing quite
a few perl modules; this can be quite ornery if your perl installation
isn't up to snuff.
</PARA>
<TIP>
<PARA>
You can skip the following Perl module installation
steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
All Perl module installation steps require you have an active Internet
connection.
</PARA>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl -MCPAN -e 'install "Bundle::Bugzilla"'</COMMAND>
</COMPUTEROUTPUT>
</PARA>
<PARA>
Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
which are not essential to a basic Bugzilla install. If installing
this bundle fails, you should install each module individually to
isolate the problem.
</PARA>
</TIP>
</SECTION>
<SECTION>
<TITLE>DBI Perl Module</TITLE>
<PARA>
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
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
MakeMaker system simplifies the C compilation greatly.
</PARA>
<PARA>
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
real tendency to bog down, so please use mirrors. The current location
at the time of this writing (02/17/99) can be found in Appendix A.
</PARA>
<PARA>
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
which does all the hard work for you.
</PARA>
<PARA>
To use the CPAN shell to install DBI:
<INFORMALEXAMPLE>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl -MCPAN -e 'install "DBI"'</COMMAND>
</COMPUTEROUTPUT>
<NOTE>
<PARA>Replace "DBI" with the name of whichever module you wish
to install, such as Data::Dumper, TimeDate, GD, etc.</PARA>
</NOTE>
</PARA>
</INFORMALEXAMPLE>
To do it the hard way:
<INFORMALEXAMPLE>
<PARA>
Untar the module tarball -- it should create its own directory
</PARA>
<PARA>
CD to the directory just created, and enter the following commands:
<ORDEREDLIST>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>perl Makefile.PL</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make test</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>make install</COMMAND>
</COMPUTEROUTPUT>
</PARA>
</LISTITEM>
</ORDEREDLIST>
If everything went ok that should be all it takes. For the vast
majority of perl modules this is all that's required.
</PARA>
</INFORMALEXAMPLE>
</PARA>
</SECTION>
<SECTION>
<TITLE>Data::Dumper Perl Module</TITLE>
<PARA>
The Data::Dumper module provides data structure persistence for Perl
(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
hurt anything.
</PARA>
<PARA>
Data::Dumper is used by the MySQL related Perl modules. It can be
found on CPAN (link in Appendix A) and can be installed by following
the same four step make sequence used for the DBI module.
</PARA>
</SECTION>
<SECTION>
<TITLE>MySQL related Perl Module Collection</TITLE>
<PARA>
The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
Msql-Mysql-modules package. This package can be found at CPAN.
After the archive file has been downloaded it should
be untarred.
</PARA>
<PARA>
The MySQL modules are all built using one make file which is generated
by running:
<PROMPT>bash#</PROMPT>
<COMMAND>perl Makefile.pl</COMMAND>
</PARA>
<PARA>
The MakeMaker process will ask you a few questions about the desired
compilation target and your MySQL installation. For many of the questions
the provided default will be adequate.
</PARA>
<PARA>
When asked if your desired target is the MySQL or mSQL packages
selected the MySQL related ones. Later you will be asked if you wish
to provide backwards compatibility with the older MySQL packages; you
must answer YES to this question. The default will be no, and if you
select it things won't work later.
</PARA>
<PARA>
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
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
</PARA>
</SECTION>
<SECTION>
<TITLE>TimeDate Perl Module Collection</TITLE>
<PARA>
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
bundle is stored on the CPAN under the name TimeDate. A (hopefully
current) link can be found in Appendix A. The component module we're
most interested in is the Date::Format module, but installing all of them
is probably a good idea anyway. The standard Perl module installation
instructions should work perfectly for this simple package.
</PARA>
</SECTION>
<SECTION>
<TITLE>GD Perl Module (1.8.3)</TITLE>
<PARA>
The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become almost a
defacto standard for programatic image construction. The Perl bindings
to it found in the GD library are used on a million web pages to generate
graphs on the fly. That's what bugzilla will be using it for so you'd
better install it if you want any of the graphing to work.
</PARA>
<PARA>
Actually bugzilla uses the Graph module which relies on GD itself,
but isn't that always the way with OOP. At any rate, you can find the
GD library on CPAN (link in Appendix "Required Software").
</PARA>
<NOTE>
<PARA>
The Perl GD library requires some other libraries that may or may not be
installed on your system, including "libpng" and "libgd". The full requirements
are listed in the Perl GD library README. Just realize that if compiling GD fails,
it's probably because you're missing a required library.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Chart::Base Perl Module (0.99c)</TITLE>
<PARA>
The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
fetched from CPAN where it is found as the Chart-x.x... tarball in a
directory to be listed in Appendix "Required Software". Note that as with the GD perl
module, only the specific versions listed above (or newer) will work. Earlier
versions used GIF's, which are no longer supported by the latest
versions of GD.
</PARA>
</SECTION>
<SECTION>
<TITLE>DB_File Perl Module</TITLE>
<PARA>
DB_File is a module which allows Perl programs to make use of the facilities provided by
Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
bug charting. If you plan to make use of bug charting, you must install this module.
</PARA>
</SECTION>
<SECTION>
<TITLE>HTTP Server</TITLE>
<PARA>
You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can easily run the web server on a different
machine than MySQL, but need to adjust the MySQL "bugs" user permissions
accordingly.
</PARA>
<PARA>
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. If you're using
apache that means uncommenting the following line in the srm.conf file:
<COMPUTEROUTPUT>AddHandler cgi-script .cgi</COMPUTEROUTPUT>
</PARA>
<PARA>
With apache you'll also want to make sure that within the access.conf
file the line:
<COMPUTEROUTPUT>
Options ExecCGI
</COMPUTEROUTPUT>
is in the stanza that covers the directories you intend to put the bugzilla
.html and .cgi files into.
</PARA>
<PARA>
If you are using a newer version of Apache, both of the above lines will be
(or will need to be) in the httpd.conf file, rather than srm.conf or
access.conf.
</PARA>
<WARNING>
<PARA>
There are two critical directories and a file that should not be a served by
the HTTP server. These are the 'data' and 'shadow' directories and the
'localconfig' file. You should configure your HTTP server to not serve
content from these files. Failure to do so will expose critical passwords
and other data. Please see your HTTP server configuration manual on how
to do this. If you use quips (at the top of the buglist pages) you will want
the 'data/comments' file to still be served. This file contains those quips.
</PARA>
</WARNING>
</SECTION>
<SECTION>
<TITLE>Installing the Bugzilla Files</TITLE>
<PARA>
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
'nobody'). You may decide to put the files off of the main web space
for your web server or perhaps off of /usr/local with a symbolic link
in the web space that points to the bugzilla directory. At any rate,
just dump all the files in the same place (optionally omitting the CVS
directories if they were accidentally tarred up with the rest of Bugzilla)
and make sure you can access the files in that directory through your
web server.
</PARA>
<TIP>
<PARA>
HINT: If you symlink the bugzilla directory into your Apache's
HTML heirarchy, you may receive "Forbidden" errors unless you
add the "FollowSymLinks" directive to the &lt;Directory&gt; entry
for the HTML root.
</PARA>
</TIP>
<PARA>
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user (which may require just
making it world writable). This is a temporary step until you run
the post-install "checksetup.pl" script, which locks down your
installation.
</PARA>
<PARA>
Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
to the correct location of your perl executable (probably /usr/bin/perl).
Otherwise you must hack all the .cgi files to change where they look
for perl. To make future upgrades easier, you should use the symlink
approach.
<TIP>
<PARA>
If you don't have root access to set this symlink up, check out the
"setperl.csh" utility, listed in the Patches section of this
Guide. It will change the path to perl in all your Bugzilla files for
you.
</PARA>
</TIP>
</PARA>
</SECTION>
<SECTION>
<TITLE>Setting Up the MySQL Database</TITLE>
<PARA>
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
quality bug tracker.
</PARA>
<PARA>
First, you'll want to fix MySQL permissions to allow access from
Bugzilla. For the purpose of this Installation section, the Bugzilla username
will be "bugs", and will have minimal permissions. Bugzilla has
not undergone a thorough security audit. It may be possible for
a system cracker to somehow trick Bugzilla into executing a command
such as "; DROP DATABASE mysql".
</PARA>
<PARA>
That would be bad.
</PARA>
<PARA>
Give the MySQL root user a password. MySQL passwords are
limited to 16 characters.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>mysql -u root mysql</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>
UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>FLUSH PRIVILEGES;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
From this point on, if you need to access MySQL as the
MySQL root user, you will need to use "mysql -u root -p" and
enter your new_password. Remember that MySQL user names have
nothing to do with Unix user names (login names).
</PARA>
<PARA>
Next, we create the "bugs" user, and grant sufficient
permissions for checksetup.pl, which we'll use later, to work
its magic. This also restricts the "bugs" user to operations
within a database called "bugs", and only allows the account
to connect from "localhost". Modify it to reflect your setup
if you will be connecting from another machine or as a different
user.
</PARA>
<PARA>
Remember to set bugs_password to some unique password.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES
ON bugs.* TO bugs@localhost
IDENTIFIED BY 'bugs_password';</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>
mysql>
</PROMPT>
<COMMAND>
FLUSH PRIVILEGES;
</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
Next, run the magic checksetup.pl script. (Many thanks to Holger
Schurig &lt;holgerschurig@nikocity.de&gt; for writing this script!)
It will make sure Bugzilla files and directories have reasonable
permissions, set up the "data" directory, and create all the MySQL
tables.
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>./checksetup.pl</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
The first time you run it, it will create a file called "localconfig".
</PARA>
</SECTION>
<SECTION>
<TITLE>Tweaking "localconfig"</TITLE>
<PARA>
This file contains a variety of settings you may need to tweak including
how Bugzilla should connect to the MySQL database.
</PARA>
<PARA>
The connection settings include:
<ORDEREDLIST>
<LISTITEM>
<PARA>
server's host: just use "localhost" if the MySQL server is
local
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
database name: "bugs" if you're following these directions
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
MySQL username: "bugs" if you're following these directions
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Password for the "bugs" MySQL account above
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
<PARA>
Once you are happy with the settings, re-run checksetup.pl. On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
</PARA>
<PARA>
When logged into an administrator account once Bugzilla is running,
if you go to the query page (off of the bugzilla main menu), you'll
find an 'edit parameters' option that is filled with editable treats.
</PARA>
<PARA>
Should everything work, you should have a nearly empty copy of the bug
tracking setup.
</PARA>
<PARA>
The second time around, checksetup.pl will stall if it is on a
filesystem that does not fully support file locking via flock(), such as
NFS mounts. This support is required for Bugzilla to operate safely with
multiple instances. If flock() is not fully supported, it will stall at:
<ERRORCODE>Now regenerating the shadow database for all bugs.</ERRORCODE>
<NOTE>
<PARA>
The second time you run checksetup.pl, it is recommended you be the same
user as your web server runs under, and that you be sure you have set the
"webservergroup" parameter in localconfig to match the web server's group
name, if any. Under some systems, otherwise, checksetup.pl will goof up
your file permissions and make them unreadable to your web server.
</PARA>
</NOTE>
</PARA>
<NOTE>
<PARA>
The checksetup.pl script is designed so that you can run it at any time
without causing harm. You should run it after any upgrade to Bugzilla.
</PARA>
</NOTE>
</SECTION>
<SECTION>
<TITLE>Setting Up Maintainers Manuall (Optional)</TITLE>
<PARA>
If you want to add someone else to every group by hand, you can do it
by typing the appropriate MySQL commands. Run '<COMPUTEROUTPUT>
mysql -u root -p bugs</COMPUTEROUTPUT>'
(you may need different parameters, depending on your security settings
according to section 3, above). Then:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>update profiles set groupset=0x7fffffffffffffff
where login_name = 'XXX';</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
replacing XXX with the Bugzilla email address.
</PARA>
</SECTION>
<SECTION>
<TITLE>The Whining Cron (Optional)</TITLE>
<PARA>
By now you've got a fully functional bugzilla, but what good are bugs
if they're not annoying? To help make those bugs more annoying you can
set up bugzilla's automatic whining system. This can be done by adding
the following command as a daily crontab entry (for help on that see that
crontab man page):
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<COMMAND>cd &lt;your-bugzilla-directory&gt; ; ./whineatnews.pl</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
</SECTION>
<SECTION>
<TITLE>Bug Graphs (Optional)</TITLE>
<PARA>
As long as you installed the GD and Graph::Base Perl modules you might
as well turn on the nifty bugzilla bug reporting graphs.
</PARA>
<PARA>
Add a cron entry like this to run collectstats daily at 5 after midnight:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>crontab -e</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
5 0 * * * cd &lt;your-bugzilla-directory&gt; ; ./collectstats.pl
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
</PARA>
</SECTION>
<SECTION>
<TITLE>Securing MySQL</TITLE>
<PARA>
If you followed the README for setting up your "bugs" and "root" user in
MySQL, much of this should not apply to you. If you are upgrading
an existing installation of Bugzilla, you should pay close attention
to this section.
</PARA>
<PARA>
Most MySQL installs have "interesting" default security parameters:
<SIMPLELIST>
<MEMBER>mysqld defaults to running as root</MEMBER>
<MEMBER>it defaults to allowing external network connections</MEMBER>
<MEMBER>it has a known port number, and is easy to detect</MEMBER>
<MEMBER>it defaults to no passwords whatsoever</MEMBER>
<MEMBER>it defaults to allowing "File_Priv"</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
This means anyone from anywhere on the internet can not only drop the
database with one SQL command, and they can write as root to the system.
</PARA>
<PARA>
To see your permissions do:
<SIMPLELIST>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>bash#</PROMPT>
<COMMAND>mysql -u root -p</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>use mysql;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>show tables;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>select * from user;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
<MEMBER>
<COMPUTEROUTPUT>
<PROMPT>mysql></PROMPT>
<COMMAND>select * from db;</COMMAND>
</COMPUTEROUTPUT>
</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
To fix the gaping holes:
<SIMPLELIST>
<MEMBER>DELETE FROM user WHERE User='';</MEMBER>
<MEMBER>UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';</MEMBER>
<MEMBER> FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
If you're not running "mit-pthreads" you can use:
<SIMPLELIST>
<MEMBER>GRANT USAGE ON *.* TO bugs@localhost;</MEMBER>
<MEMBER>GRANT ALL ON bugs.* TO bugs@localhost;</MEMBER>
<MEMBER>REVOKE DROP ON bugs.* FROM bugs@localhost;</MEMBER>
<MEMBER>FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
line to specify a specific host name instead of "localhost", and accept
external connections:
<SIMPLELIST>
<MEMBER>GRANT USAGE ON *.* TO bugs@bounce.hop.com;</MEMBER>
<MEMBER>GRANT ALL ON bugs.* TO bugs@bounce.hop.com;</MEMBER>
<MEMBER>REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;</MEMBER>
<MEMBER>FLUSH PRIVILEGES;</MEMBER>
</SIMPLELIST>
</PARA>
<PARA>
Consider also:
<ORDEREDLIST>
<LISTITEM>
<PARA>
Turning off external networking with "--skip-networking",
unless you have "mit-pthreads", in which case you can't.
Without networking, MySQL connects with a Unix domain socket.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
using the --user= option to mysqld to run it as an unprivileged
user.
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
starting MySQL in a chroot jail
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
running the httpd in a "chrooted" jail
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
making sure the MySQL passwords are different from the OS
passwords (MySQL "root" has nothing to do with system "root").
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
running MySQL on a separate untrusted machine
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
making backups ;-)
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
<SECTION>
<TITLE>Installation General Notes</TITLE>
<SECTION>
<TITLE>Modifying Your Running System</TITLE>
<PARA>
Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory (we said before it needs to be writable,
right?!)
</PARA>
<PARA>
If you make a change to the structural data in your database (the
versions table for example), or to the "constants" encoded in
defparams.pl, you will need to remove the cached content from the data
directory (by doing a "rm data/versioncache"), or your changes won't show
up!
</PARA>
<PARA>
That file gets automatically regenerated whenever it's more than an
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.
</PARA>
</SECTION>
<SECTION>
<TITLE>Upgrading From Previous Versions</TITLE>
<PARA>
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
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
changed, you can read the comments in that file, starting from the end.
</PARA>
</SECTION>
<SECTION>
<TITLE>UNIX Installation Instructions History</TITLE>
<PARA>
This document was originally adapted from the Bonsai installation
instructions by Terry Weissman &lt;terry@mozilla.org&gt;.
</PARA>
<PARA>
The February 25, 1999 re-write of this page was done by Ry4an Brase
&lt;ry4an@ry4an.org&gt;, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, & Dan Mosedale (But don't send bug reports to them!
Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
</PARA>
<PARA>
This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
</PARA>
<PARA>
Finally, the README in its entirety was marked up in SGML and included into
the Guide on April 24, 2001.
</PARA>
<PARA>
Comments from people using this Guide for the first time are particularly welcome.
</PARA>
</SECTION>
</SECTION>
</SECTION>
</SECTION>
<SECTION id="README.windows">
......@@ -320,6 +1230,71 @@
</BLOCKQUOTE>
</PARA>
</TIP>
<TIP>
<PARA>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</PARA>
<BLOCKQUOTE>
<PARA>
Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
deleted the current dir and copied the files in).
</PARA>
<PARA>
In checksetup.pl, I did the following...
</PARA>
<PROCEDURE>
<STEP>
<PROGRAMLISTING>
my $webservergid = getgrnam($my_webservergroup);
</PROGRAMLISTING>
<PARA>to</PARA>
<PROGRAMLISTING>
my $webservergid = 'Administrators'
</PROGRAMLISTING>
</STEP>
<STEP>
<PARA>
I then ran checksetup.pl
</PARA>
</STEP>
<STEP>
<PARA>
I removed all the encrypt()
<EXAMPLE>
<TITLE>Removing encrypt() for Windows NT installations</TITLE>
<PARA>
Replace this:
<PROGRAMLISTING>
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PROGRAMLISTING>
with this:
<PROGRAMLISTING>
my $enteredcryptpwd = $enteredpwd
</PROGRAMLISTING>
in cgi.pl.
</PARA>
</EXAMPLE>
</PARA>
</STEP>
<STEP>
<PARA>
I renamed processmail to processmail.pl
</PARA>
</STEP>
<STEP>
<PARA>
I altered the sendmail statements to windmail:
<PROGRAMLISTING>
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
</PROGRAMLISTING>
</PARA>
<PARA>
The quotes around the dir is for the spaces. mail.log is for the output
</PARA>
</STEP>
</PROCEDURE>
</BLOCKQUOTE>
</TIP>
</SECTION>
</SECTION>
</CHAPTER>
......
docs/xml/integration.xml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
<!-- Keep these tools listings in alphabetical order please. -MPB -->
......@@ -18,10 +18,31 @@
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby and his team have an integration tool
in public beta. You can find it at
<ulink url="http://www.ravenbrook.com/project/p4dt">
http://www.ravenbrook.com/project/p4dti</ulink>.
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</para>
</section>
......
docs/xml/patches.xml
View file @ 2d4d7c92
......@@ -4,15 +4,17 @@
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<title>The setperl.pl Utility</title>
<title>The setperl.csh Utility</title>
<para>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</para>
<procedure>
<step>
<para>
Download the "setperl.pl" utility to your Bugzilla
Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</para>
<substeps>
......@@ -28,7 +30,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
</para>
</step>
......@@ -36,7 +38,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.pl</command>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para>
</step>
......@@ -80,8 +82,17 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.pl /your/path/to/perl</command>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
</para>
</step>
</procedure>
......@@ -206,4 +217,21 @@
</para>
</section>
</appendix>
\ No newline at end of file
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/xml/requiredsoftware.xml 0 → 100644
View file @ 2d4d7c92
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<appendix id="downloadlinks">
<title>Software Download Links</title>
<para>
All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</para>
<para>
Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</para>
<para>
Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/">
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.org/">http://www.mysql.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
DBI Perl module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</ulink>
</para>
<para>
Data::Dumper module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</ulink>
</para>
<para>
MySQL related Perl modules:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</ulink>
</para>
<para>
TimeDate Perl module collection:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</ulink>
</para>
<para>
GD Perl module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of
GD at <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
</para>
<para>
Chart::Base module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</ulink>
</para>
<para>
LinuxDoc Software:
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink>
(for documentation maintenance)
</para>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/xml/using.xml
View file @ 2d4d7c92
......@@ -41,11 +41,14 @@ Chapter: Using Bugzilla
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</para>
......@@ -89,7 +92,8 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
integration with several automated software configuration management systems
available integration with automated software configuration management systems, including
Perforce and CVS.
</para>
</listitem>
<listitem>
......@@ -108,6 +112,12 @@ Chapter: Using Bugzilla
no internationalization, and dependence on some nonstandard libraries.
</para>
<para>
Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</para>
<para>
Despite these small problems, Bugzilla is very hard to beat. It is under <emphasis>very</emphasis>
active development to address the current issues, and a long-awaited overhaul in the form
of Bugzilla 3.0 is expected sometime later this year.
......@@ -147,7 +157,7 @@ Chapter: Using Bugzilla
Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......@@ -178,7 +188,7 @@ Chapter: Using Bugzilla
</epigraph>
<para>
Bugzilla is a large and complex system. Describing how to use it
Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -190,11 +200,24 @@ Chapter: Using Bugzilla
options available at the Bugzilla test installation,
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
<note>
<para>
Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <ulink url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
</para>
</note>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</para>
<section id="myaccount">
......@@ -714,6 +737,14 @@ Chapter: Using Bugzilla
<title>Email Settings</title>
<section id="notification">
<title>Email Notification</title>
<note>
<para>
The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</para>
</note>
<para>
Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/xml/variants.xml
View file @ 2d4d7c92
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<section id="rhbugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>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 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 with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
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