diff --git a/CGI.pl b/CGI.pl
index a6d3e22448205f02e4fdad19f2d6cf6d9e350ae5..de983122b14eabb4c126c455b502df0168bfd10a 100644
--- a/CGI.pl
+++ b/CGI.pl
@@ -80,7 +80,7 @@ if (Param("shutdownhtml") && $0 !~ m:[\\/](do)?editparams.cgi$:) {
sub url_decode {
my ($todecode) = (@_);
$todecode =~ tr/+/ /; # pluses become spaces
- $todecode =~ s/%([0-9a-fA-F]{2})/pack("c",hex($1))/ge;
+ $todecode =~ s/%([0-9a-fA-F]{2})/pack("C",hex($1))/ge;
return $todecode;
}
diff --git a/CVS/Entries b/CVS/Entries
index b6435a819c4bc9652177f95b29241e709e92cea6..7322ba7ada6d9dae5284e180ec9556014d405775 100644
--- a/CVS/Entries
+++ b/CVS/Entries
@@ -1,78 +1,79 @@
-/.cvsignore/1.5.2.1/Mon May 13 22:31:47 2002//TBUGZILLA-2_16_2
-/1x1.gif/1.1/Wed Aug 26 06:14:15 1998/-kb/TBUGZILLA-2_16_2
-/Attachment.pm/1.8/Sat Mar 23 17:58:36 2002//TBUGZILLA-2_16_2
-/Bug.pm/1.12/Sat Apr 27 06:25:41 2002//TBUGZILLA-2_16_2
-/CGI.pl/1.153.2.3/Wed Jul 10 06:27:15 2002//TBUGZILLA-2_16_2
-/README/1.50/Sat Aug 11 19:56:40 2001//TBUGZILLA-2_16_2
-/RelationSet.pm/1.7/Sat Nov 3 02:05:43 2001//TBUGZILLA-2_16_2
-/Token.pm/1.12.2.1/Tue Jul 9 02:17:28 2002//TBUGZILLA-2_16_2
-/UPGRADING/1.1/Fri Aug 10 22:35:21 2001//TBUGZILLA-2_16_2
-/UPGRADING-pre-2.8/1.2/Sun Dec 23 23:23:22 2001//TBUGZILLA-2_16_2
-/ant.jpg/1.2/Wed Aug 26 22:36:05 1998/-kb/TBUGZILLA-2_16_2
-/attachment.cgi/1.14/Wed Apr 24 07:24:43 2002//TBUGZILLA-2_16_2
-/bug_form.pl/1.93.2.3/Wed Jul 10 00:05:51 2002//TBUGZILLA-2_16_2
-/bug_status.html/1.13/Mon Apr 15 02:47:52 2002//TBUGZILLA-2_16_2
-/buglist.cgi/1.169.2.10/Wed Jun 19 22:53:25 2002//TBUGZILLA-2_16_2
-/bugwritinghelp.html/1.3/Mon Apr 15 02:47:53 2002//TBUGZILLA-2_16_2
-/bugzilla.dtd/1.5/Thu Apr 4 04:19:58 2002//TBUGZILLA-2_16_2
-/changepassword.cgi/1.21/Sun Jan 20 01:44:37 2002//TBUGZILLA-2_16_2
-/checksetup.pl/1.149.2.14/Mon Dec 23 01:54:23 2002//TBUGZILLA-2_16_2
-/colchange.cgi/1.24.2.2/Mon Jun 17 09:39:35 2002//TBUGZILLA-2_16_2
-/collectstats.pl/1.20.12.1/Fri Dec 13 11:02:26 2002//TBUGZILLA-2_16_2
-/confirmhelp.html/1.3/Mon Apr 15 02:47:53 2002//TBUGZILLA-2_16_2
-/createaccount.cgi/1.21.2.3/Fri Aug 30 15:29:24 2002//TBUGZILLA-2_16_2
-/defparams.pl/1.73.2.2/Wed Jul 10 00:05:52 2002//TBUGZILLA-2_16_2
-/describecomponents.cgi/1.11.2.2/Mon Jun 17 09:39:40 2002//TBUGZILLA-2_16_2
-/describekeywords.cgi/1.8/Wed Apr 24 07:24:45 2002//TBUGZILLA-2_16_2
-/doeditparams.cgi/1.17.2.1/Mon Jun 17 09:39:40 2002//TBUGZILLA-2_16_2
-/duplicates.cgi/1.19/Fri Apr 26 23:18:57 2002//TBUGZILLA-2_16_2
-/editattachstatuses.cgi/1.7/Mon Apr 29 19:32:27 2002//TBUGZILLA-2_16_2
-/editcomponents.cgi/1.22.2.2/Mon Jun 17 09:39:41 2002//TBUGZILLA-2_16_2
-/editgroups.cgi/1.16.2.1/Mon Jun 17 09:39:41 2002//TBUGZILLA-2_16_2
-/editkeywords.cgi/1.9.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_2
-/editmilestones.cgi/1.8.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_2
-/editparams.cgi/1.14.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_2
-/editproducts.cgi/1.24.2.2/Sun Sep 22 17:47:12 2002//TBUGZILLA-2_16_2
-/editusers.cgi/1.35.2.2/Mon Jun 17 09:39:44 2002//TBUGZILLA-2_16_2
-/editversions.cgi/1.11.2.1/Mon Jun 17 09:39:44 2002//TBUGZILLA-2_16_2
-/enter_bug.cgi/1.66.2.3/Tue Jun 11 13:33:45 2002//TBUGZILLA-2_16_2
-/globals.pl/1.169.2.13/Fri Dec 13 11:30:38 2002//TBUGZILLA-2_16_2
-/help.html/1.5/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/helpemailquery.html/1.2/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/how_to_mail.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/importxml.pl/1.23.2.1/Sun Aug 25 16:50:08 2002//TBUGZILLA-2_16_2
-/index.cgi/1.4.2.1/Sun Jun 23 17:36:00 2002//TBUGZILLA-2_16_2
-/localconfig.js/1.1/Wed Feb 28 23:07:25 2001//TBUGZILLA-2_16_2
-/long_list.cgi/1.26/Wed Apr 24 07:24:46 2002//TBUGZILLA-2_16_2
-/move.pl/1.11.2.1/Mon Jun 17 09:39:48 2002//TBUGZILLA-2_16_2
-/notargetmilestone.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/post_bug.cgi/1.52.2.6/Thu Aug 1 09:59:32 2002//TBUGZILLA-2_16_2
-/process_bug.cgi/1.125.2.6/Tue Sep 3 07:24:54 2002//TBUGZILLA-2_16_2
-/processmail/1.81/Sun Apr 14 04:43:55 2002//TBUGZILLA-2_16_2
-/query.cgi/1.98.2.1/Mon Jun 3 01:42:15 2002//TBUGZILLA-2_16_2
-/queryhelp.cgi/1.11.2.2/Mon Jun 17 09:39:45 2002//TBUGZILLA-2_16_2
-/quicksearch.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/quicksearch.js/1.9/Mon Dec 24 22:24:35 2001//TBUGZILLA-2_16_2
-/quicksearchhack.html/1.4/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_2
-/quips.cgi/1.6.2.1/Mon Jun 17 09:39:46 2002//TBUGZILLA-2_16_2
-/relogin.cgi/1.18/Wed May 8 04:40:35 2002//TBUGZILLA-2_16_2
-/reports.cgi/1.54/Fri Apr 26 21:09:50 2002//TBUGZILLA-2_16_2
-/robots.txt/1.2/Wed Apr 24 18:11:00 2002//TBUGZILLA-2_16_2
-/runtests.sh/1.5/Fri Apr 12 21:15:45 2002//TBUGZILLA-2_16_2
-/sanitycheck.cgi/1.42/Thu Apr 4 04:19:58 2002//TBUGZILLA-2_16_2
-/show_activity.cgi/1.9/Wed Apr 24 07:24:49 2002//TBUGZILLA-2_16_2
-/show_bug.cgi/1.18/Sat Mar 23 17:58:36 2002//TBUGZILLA-2_16_2
-/showattachment.cgi/1.10/Wed Jan 30 14:14:12 2002//TBUGZILLA-2_16_2
-/showdependencygraph.cgi/1.18.2.1/Tue Jul 9 23:40:41 2002//TBUGZILLA-2_16_2
-/showdependencytree.cgi/1.17.2.1/Tue May 21 14:18:00 2002//TBUGZILLA-2_16_2
-/sidebar.cgi/1.4.2.2/Wed Jul 10 00:05:54 2002//TBUGZILLA-2_16_2
-/syncshadowdb/1.14/Sun Dec 23 23:23:22 2001//TBUGZILLA-2_16_2
-/token.cgi/1.7.2.1/Mon Jun 17 09:39:46 2002//TBUGZILLA-2_16_2
-/userprefs.cgi/1.35.2.3/Tue Aug 13 06:57:00 2002//TBUGZILLA-2_16_2
-/votehelp.html/1.10/Mon Apr 15 02:47:56 2002//TBUGZILLA-2_16_2
-/votes.cgi/1.3/Tue May 7 21:28:41 2002//TBUGZILLA-2_16_2
-/whineatnews.pl/1.7/Sun Feb 17 08:22:31 2002//TBUGZILLA-2_16_2
-/xml.cgi/1.6.2.1/Mon Jun 17 09:39:48 2002//TBUGZILLA-2_16_2
+/.cvsignore/1.5.2.1/Mon May 13 22:31:47 2002//TBUGZILLA-2_16_3
+/1x1.gif/1.1/Wed Aug 26 06:14:15 1998/-kb/TBUGZILLA-2_16_3
+/Attachment.pm/1.8/Sat Mar 23 17:58:36 2002//TBUGZILLA-2_16_3
+/Bug.pm/1.12/Sat Apr 27 06:25:41 2002//TBUGZILLA-2_16_3
+/CGI.pl/1.153.2.4/Mon Apr 14 11:50:52 2003//TBUGZILLA-2_16_3
+/README/1.50/Sat Aug 11 19:56:40 2001//TBUGZILLA-2_16_3
+/RelationSet.pm/1.7/Sat Nov 3 02:05:43 2001//TBUGZILLA-2_16_3
+/Token.pm/1.12.2.1/Tue Jul 9 02:17:28 2002//TBUGZILLA-2_16_3
+/UPGRADING/1.1/Fri Aug 10 22:35:21 2001//TBUGZILLA-2_16_3
+/UPGRADING-pre-2.8/1.2/Sun Dec 23 23:23:22 2001//TBUGZILLA-2_16_3
+/ant.jpg/1.2/Wed Aug 26 22:36:05 1998/-kb/TBUGZILLA-2_16_3
+/attachment.cgi/1.14/Wed Apr 24 07:24:43 2002//TBUGZILLA-2_16_3
+/bug_form.pl/1.93.2.3/Wed Jul 10 00:05:51 2002//TBUGZILLA-2_16_3
+/bug_status.html/1.13/Mon Apr 15 02:47:52 2002//TBUGZILLA-2_16_3
+/buglist.cgi/1.169.2.10/Wed Jun 19 22:53:25 2002//TBUGZILLA-2_16_3
+/bugwritinghelp.html/1.3/Mon Apr 15 02:47:53 2002//TBUGZILLA-2_16_3
+/bugzilla.dtd/1.5/Thu Apr 4 04:19:58 2002//TBUGZILLA-2_16_3
+/changepassword.cgi/1.21/Sun Jan 20 01:44:37 2002//TBUGZILLA-2_16_3
+/checksetup.pl/1.149.2.16/Thu Apr 24 21:15:44 2003//TBUGZILLA-2_16_3
+/colchange.cgi/1.24.2.2/Mon Jun 17 09:39:35 2002//TBUGZILLA-2_16_3
+/collectstats.pl/1.20.12.1/Fri Dec 13 11:02:26 2002//TBUGZILLA-2_16_3
+/confirmhelp.html/1.3/Mon Apr 15 02:47:53 2002//TBUGZILLA-2_16_3
+/createaccount.cgi/1.21.2.3/Fri Aug 30 15:29:24 2002//TBUGZILLA-2_16_3
+/defparams.pl/1.73.2.5/Thu Apr 24 22:36:37 2003//TBUGZILLA-2_16_3
+/describecomponents.cgi/1.11.2.2/Mon Jun 17 09:39:40 2002//TBUGZILLA-2_16_3
+/describekeywords.cgi/1.8/Wed Apr 24 07:24:45 2002//TBUGZILLA-2_16_3
+/doeditparams.cgi/1.17.2.1/Mon Jun 17 09:39:40 2002//TBUGZILLA-2_16_3
+/duplicates.cgi/1.19.2.1/Thu Apr 24 20:45:08 2003//TBUGZILLA-2_16_3
+/editattachstatuses.cgi/1.7/Mon Apr 29 19:32:27 2002//TBUGZILLA-2_16_3
+/editcomponents.cgi/1.22.2.3/Sun Mar 16 06:19:34 2003//TBUGZILLA-2_16_3
+/editgroups.cgi/1.16.2.1/Mon Jun 17 09:39:41 2002//TBUGZILLA-2_16_3
+/editkeywords.cgi/1.9.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_3
+/editmilestones.cgi/1.8.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_3
+/editparams.cgi/1.14.2.1/Mon Jun 17 09:39:42 2002//TBUGZILLA-2_16_3
+/editproducts.cgi/1.24.2.3/Wed Feb 12 05:05:57 2003//TBUGZILLA-2_16_3
+/editusers.cgi/1.35.2.2/Mon Jun 17 09:39:44 2002//TBUGZILLA-2_16_3
+/editversions.cgi/1.11.2.1/Mon Jun 17 09:39:44 2002//TBUGZILLA-2_16_3
+/enter_bug.cgi/1.66.2.3/Tue Jun 11 13:33:45 2002//TBUGZILLA-2_16_3
+/globals.pl/1.169.2.15/Thu Apr 24 22:03:41 2003//TBUGZILLA-2_16_3
+/help.html/1.5/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/helpemailquery.html/1.2/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/how_to_mail.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/importxml.pl/1.23.2.2/Fri Apr 25 04:18:13 2003//TBUGZILLA-2_16_3
+/index.cgi/1.4.2.1/Sun Jun 23 17:36:00 2002//TBUGZILLA-2_16_3
+/localconfig.js/1.1/Wed Feb 28 23:07:25 2001//TBUGZILLA-2_16_3
+/long_list.cgi/1.26/Wed Apr 24 07:24:46 2002//TBUGZILLA-2_16_3
+/move.pl/1.11.2.1/Mon Jun 17 09:39:48 2002//TBUGZILLA-2_16_3
+/notargetmilestone.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/post_bug.cgi/1.52.2.6/Thu Aug 1 09:59:32 2002//TBUGZILLA-2_16_3
+/process_bug.cgi/1.125.2.7/Thu Apr 24 21:01:52 2003//TBUGZILLA-2_16_3
+/processmail/1.81/Sun Apr 14 04:43:55 2002//TBUGZILLA-2_16_3
+/query.cgi/1.98.2.1/Mon Jun 3 01:42:15 2002//TBUGZILLA-2_16_3
+/queryhelp.cgi/1.11.2.2/Mon Jun 17 09:39:45 2002//TBUGZILLA-2_16_3
+/quicksearch.html/1.3/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/quicksearch.js/1.9/Mon Dec 24 22:24:35 2001//TBUGZILLA-2_16_3
+/quicksearchhack.html/1.4/Mon Apr 15 02:47:55 2002//TBUGZILLA-2_16_3
+/quips.cgi/1.6.2.1/Mon Jun 17 09:39:46 2002//TBUGZILLA-2_16_3
+/relogin.cgi/1.18/Wed May 8 04:40:35 2002//TBUGZILLA-2_16_3
+/reports.cgi/1.54/Fri Apr 26 21:09:50 2002//TBUGZILLA-2_16_3
+/robots.txt/1.2/Wed Apr 24 18:11:00 2002//TBUGZILLA-2_16_3
+/runtests.pl/1.1.4.2/Mon Feb 17 02:33:31 2003//TBUGZILLA-2_16_3
+/runtests.sh/1.5/Fri Apr 12 21:15:45 2002//TBUGZILLA-2_16_3
+/sanitycheck.cgi/1.42/Thu Apr 4 04:19:58 2002//TBUGZILLA-2_16_3
+/show_activity.cgi/1.9/Wed Apr 24 07:24:49 2002//TBUGZILLA-2_16_3
+/show_bug.cgi/1.18/Sat Mar 23 17:58:36 2002//TBUGZILLA-2_16_3
+/showattachment.cgi/1.10/Wed Jan 30 14:14:12 2002//TBUGZILLA-2_16_3
+/showdependencygraph.cgi/1.18.2.3/Thu Apr 24 21:15:48 2003//TBUGZILLA-2_16_3
+/showdependencytree.cgi/1.17.2.1/Tue May 21 14:18:00 2002//TBUGZILLA-2_16_3
+/sidebar.cgi/1.4.2.2/Wed Jul 10 00:05:54 2002//TBUGZILLA-2_16_3
+/syncshadowdb/1.14/Sun Dec 23 23:23:22 2001//TBUGZILLA-2_16_3
+/token.cgi/1.7.2.1/Mon Jun 17 09:39:46 2002//TBUGZILLA-2_16_3
+/userprefs.cgi/1.35.2.3/Tue Aug 13 06:57:00 2002//TBUGZILLA-2_16_3
+/votehelp.html/1.10/Mon Apr 15 02:47:56 2002//TBUGZILLA-2_16_3
+/votes.cgi/1.3/Tue May 7 21:28:41 2002//TBUGZILLA-2_16_3
+/whineatnews.pl/1.7/Sun Feb 17 08:22:31 2002//TBUGZILLA-2_16_3
+/xml.cgi/1.6.2.1/Mon Jun 17 09:39:48 2002//TBUGZILLA-2_16_3
D/contrib////
D/css////
D/docs////
diff --git a/CVS/Entries.Log b/CVS/Entries.Log
index e678de311cbb10c1d63d72acab1181c5511dae90..ceff3f4a92da366a0b408067912d08057a99b4b2 100644
--- a/CVS/Entries.Log
+++ b/CVS/Entries.Log
@@ -1,12 +1,8 @@
A D/Bugzilla////
A D/Conf////
-A D/DiffPrinter////
-A D/PatchIterator////
A D/js////
A D/oracle////
R D/oracle////
R D/js////
-R D/PatchIterator////
-R D/DiffPrinter////
R D/Conf////
R D/Bugzilla////
diff --git a/CVS/Tag b/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/CVS/Tag
+++ b/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/checksetup.pl b/checksetup.pl
index fd2ffa33705d9a6e7e9348f25f9d44d32e0d64a9..b23ca76a6bb813bb73d0bf7c17cdbc8629560e0f 100755
--- a/checksetup.pl
+++ b/checksetup.pl
@@ -203,6 +203,10 @@ my $modules = [
name => 'File::Spec',
version => '0.82'
},
+ {
+ name => 'File::Temp',
+ version => '0'
+ },
{
name => 'Template',
version => '2.07'
@@ -813,14 +817,13 @@ END
# Restrict access to .dot files to the public webdot server at research.att.com
# if research.att.com ever changed their IP, or if you use a different
# webdot server, you'll need to edit this
-<FilesMatch ^[0-9]+\.dot$>
+<FilesMatch \.dot$>
Allow from 192.20.225.10
Deny from all
</FilesMatch>
-# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
-# .map files
-<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$>
+# Allow access to .png files created by a local copy of 'dot'
+<FilesMatch \.png$>
Allow from all
</FilesMatch>
@@ -1112,6 +1115,7 @@ if ($my_webservergroup) {
fixPerms('data/webdot', $<, $webservergid, 007, 1);
fixPerms('data/webdot/.htaccess', $<, $webservergid, 027);
fixPerms('data/params', $<, $webservergid, 017);
+ fixPerms('data/comments', $<, $webservergid, 017);
fixPerms('*', $<, $webservergid, 027);
fixPerms('template', $<, $webservergid, 027, 1);
fixPerms('css', $<, $webservergid, 027, 1);
diff --git a/contrib/CVS/Entries b/contrib/CVS/Entries
index b9ee68a43c72f40cfec6090430fe59515e3b603e..5b37e06f1e25fba7ec99730b12be4851db249b5e 100644
--- a/contrib/CVS/Entries
+++ b/contrib/CVS/Entries
@@ -1,13 +1,13 @@
-/BugzillaEmail.pm/1.1/Wed Mar 15 22:29:44 2000//TBUGZILLA-2_16_2
-/README/1.4/Sun Apr 22 18:13:40 2001//TBUGZILLA-2_16_2
-/README.Mailif/1.3/Wed Mar 15 23:39:03 2000//TBUGZILLA-2_16_2
-/bug_email.pl/1.9.12.2/Sat Aug 17 14:24:09 2002//TBUGZILLA-2_16_2
-/bugmail_help.html/1.1/Tue Mar 7 17:36:48 2000//TBUGZILLA-2_16_2
-/bugzilla.procmailrc/1.1/Wed Mar 15 23:39:09 2000//TBUGZILLA-2_16_2
-/bugzilla_email_append.pl/1.2.14.2/Tue Sep 3 06:39:06 2002//TBUGZILLA-2_16_2
-/cvs-update.sh/1.1/Wed Apr 18 18:01:28 2001//TBUGZILLA-2_16_2
-/gnats2bz.pl/1.6/Thu Jan 31 14:29:21 2002//TBUGZILLA-2_16_2
-/jb2bz.py/1.1/Wed Feb 13 14:59:30 2002//TBUGZILLA-2_16_2
-/mysqld-watcher.pl/1.2/Fri Jun 1 08:34:45 2001//TBUGZILLA-2_16_2
-/yp_nomail.sh/1.1/Tue Sep 12 23:50:31 2000//TBUGZILLA-2_16_2
+/BugzillaEmail.pm/1.1/Wed Mar 15 22:29:44 2000//TBUGZILLA-2_16_3
+/README/1.4/Sun Apr 22 18:13:40 2001//TBUGZILLA-2_16_3
+/README.Mailif/1.3/Wed Mar 15 23:39:03 2000//TBUGZILLA-2_16_3
+/bug_email.pl/1.9.12.2/Sat Aug 17 14:24:09 2002//TBUGZILLA-2_16_3
+/bugmail_help.html/1.1/Tue Mar 7 17:36:48 2000//TBUGZILLA-2_16_3
+/bugzilla.procmailrc/1.1/Wed Mar 15 23:39:09 2000//TBUGZILLA-2_16_3
+/bugzilla_email_append.pl/1.2.14.2/Tue Sep 3 06:39:06 2002//TBUGZILLA-2_16_3
+/cvs-update.sh/1.1/Wed Apr 18 18:01:28 2001//TBUGZILLA-2_16_3
+/gnats2bz.pl/1.6/Thu Jan 31 14:29:21 2002//TBUGZILLA-2_16_3
+/jb2bz.py/1.1/Wed Feb 13 14:59:30 2002//TBUGZILLA-2_16_3
+/mysqld-watcher.pl/1.2/Fri Jun 1 08:34:45 2001//TBUGZILLA-2_16_3
+/yp_nomail.sh/1.1/Tue Sep 12 23:50:31 2000//TBUGZILLA-2_16_3
D/cmdline////
diff --git a/contrib/CVS/Tag b/contrib/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/contrib/CVS/Tag
+++ b/contrib/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/contrib/cmdline/CVS/Entries b/contrib/cmdline/CVS/Entries
index 9340d151079dbba03967060e7bbcedbf13b12b5f..28ab2e7b3dcbf508ca462fb601a835800d699fbb 100644
--- a/contrib/cmdline/CVS/Entries
+++ b/contrib/cmdline/CVS/Entries
@@ -1,4 +1,4 @@
-/buglist/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_2
-/bugs/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_2
-/query.conf/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_2
+/buglist/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_3
+/bugs/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_3
+/query.conf/1.1/Thu Nov 15 17:04:58 2001//TBUGZILLA-2_16_3
D
diff --git a/contrib/cmdline/CVS/Tag b/contrib/cmdline/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/contrib/cmdline/CVS/Tag
+++ b/contrib/cmdline/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/css/CVS/Entries b/css/CVS/Entries
index abea81a0d159666e1e727effc89b4234a563ae43..94ef93799581a13474ad509820fdc753c79da582 100644
--- a/css/CVS/Entries
+++ b/css/CVS/Entries
@@ -1,3 +1,3 @@
-/buglist.css/1.1/Tue Mar 12 13:55:00 2002//TBUGZILLA-2_16_2
-/panel.css/1.1/Wed Dec 12 22:41:11 2001//TBUGZILLA-2_16_2
+/buglist.css/1.1/Tue Mar 12 13:55:00 2002//TBUGZILLA-2_16_3
+/panel.css/1.1/Wed Dec 12 22:41:11 2001//TBUGZILLA-2_16_3
D
diff --git a/css/CVS/Tag b/css/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/css/CVS/Tag
+++ b/css/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/defparams.pl b/defparams.pl
index d5c41dc601f820419d53424ef68c1cc9239fc3c0..5f2fc4472db1057aae59b150324ecd3b13b81b1b 100644
--- a/defparams.pl
+++ b/defparams.pl
@@ -55,15 +55,16 @@ sub WriteParams {
}
}
- my $tmpname = "data/params.$$";
- open(FID, ">$tmpname") || die "Can't create $tmpname";
+ require File::Temp;
+ my ($fh, $tmpname) = File::Temp::tempfile("params.XXXXX",
+ DIR=>'data');
my $v = $::param{'version'};
delete $::param{'version'}; # Don't write the version number out to
# the params file.
- print FID GenerateCode('%::param');
+ print $fh (GenerateCode('%::param'));
$::param{'version'} = $v;
- print FID "1;\n";
- close FID;
+ print $fh "1;\n";
+ close $fh;
rename $tmpname, "data/params" || die "Can't rename $tmpname to data/params";
ChmodDataFile('data/params', 0666);
}
@@ -439,8 +440,8 @@ sub check_webdotbase {
# Check .htaccess allows access to generated images
if(-e "data/webdot/.htaccess") {
open HTACCESS, "data/webdot/.htaccess";
- if(! grep(/png/,<HTACCESS>)) {
- print "Dependency graph images are not accessible.\nDelete data/webdot/.htaccess and re-run checksetup.pl to rectify.\n";
+ if(! grep(/ \\\.png\$/,<HTACCESS>)) {
+ print "Dependency graph images are not accessible.\nAssuming that you have not modified the file, delete data/webdot/.htaccess and re-run checksetup.pl to rectify.\n";
}
close HTACCESS;
}
diff --git a/docs/CVS/Entries b/docs/CVS/Entries
index 570a8e5e754f33e09e2ccb1b81ce9dd8c7cdcbd0..90416efff9bf640006e902a9af6fc4d7d74bcc57 100644
--- a/docs/CVS/Entries
+++ b/docs/CVS/Entries
@@ -1,6 +1,7 @@
-/README.docs/1.6/Wed May 1 09:24:40 2002//TBUGZILLA-2_16_2
-/rel_notes.txt/1.10.2.13/Thu Jan 2 17:10:56 2003//TBUGZILLA-2_16_2
+/README.docs/1.6.2.3/Wed Apr 23 03:22:20 2003//TBUGZILLA-2_16_3
+/makedocs.pl/1.2.2.2/Wed Apr 23 02:23:50 2003//TBUGZILLA-2_16_3
+/rel_notes.txt/1.10.2.14/Fri Apr 25 06:37:23 2003//TBUGZILLA-2_16_3
D/html////
D/images////
-D/sgml////
D/txt////
+D/xml////
diff --git a/docs/CVS/Tag b/docs/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/docs/CVS/Tag
+++ b/docs/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/docs/README.docs b/docs/README.docs
index 80349957f3a7218a96c7f3ba3a21d7a69dfd2794..8a172ecda1177e8832b70074e6321823a1b7749d 100644
--- a/docs/README.docs
+++ b/docs/README.docs
@@ -2,35 +2,33 @@ Welcome to the Bugzilla documentation project!
You'll find these directories and files here:
README.docs # This README file
-html/ # The compiled HTML docs from SGML sources (do not edit)
-sgml/ # The original SGML doc sources (edit these)
-txt/ # The compiled text docs from SGML sources
-ps/ # The compiled PostScript docs from SGML sources
-pdf/ # The compiled Adobe PDF docs from SGML sources
-
-A note about SGML:
- The documentation is written in DocBook 3.1/4.1 SGML, and attempts to adhere
-to the LinuxDoc standards everywhere applicable (http://www.linuxdoc.org).
-Please consult "The LDP Author Guide" at linuxdoc.org for details on how
-to set up your personal environment for compiling SGML files.
+html/ # The compiled HTML docs from XML sources (do not edit)
+txt/ # The compiled text docs from XML sources (do not edit)
+xml/ # The original XML doc sources (edit these)
+
+A note about the XML:
+ The documentation is written in DocBook 4.1.2, and attempts to adhere
+to the LinuxDoc standards everywhere applicable (http://www.tldp.org).
+Please consult "The LDP Author Guide" at tldp.org for details on how
+to set up your personal environment for compiling XML files.
If you need to make corrections to typographical errors, or other minor
-editing duties, feel free to use any text editor to make the changes. SGML
+editing duties, feel free to use any text editor to make the changes. XML
is not rocket science -- simply make sure your text appears between
appropriate tags (like <para>This is a paragraph</para>) and we'll be fine.
If you are making more extensive changes, please ensure you at least validate
-your SGML before checking it in with something like:
- nsgmls -s Bugzilla-Guide.sgml
+your XML before checking it in with something like:
+ nsgmls -s $JADE_PUB/xml.dcl Bugzilla-Guide.xml
- When you validate, please validate the master document (Bugzilla-Guide.sgml)
+ When you validate, please validate the master document (Bugzilla-Guide.xml)
as well as the document you edited to ensure there are no critical errors.
The following errors are considered "normal" when validating with nsgmls:
DTDDECL catalog entries are not supported
"DOCTYPE" declaration not allowed in instance
- The reason these occur is that free sgml validators do not yet support
+ The reason these occur is that free sgml/xml validators do not yet support
the DTDDECL catalog entries, and I've included DOCTYPE declarations in
-entities referenced from Bugzilla-Guide.sgml so these entities can compile
+entities referenced from Bugzilla-Guide.xml so these entities can compile
individually, if necessary. I suppose I ought to comment them out at some
point, but for now they are convenient and don't hurt anything.
@@ -39,13 +37,13 @@ documentation. Please address comments and questions to the newsgroup:
news://news.mozilla.org/netscape/public/mozilla/webtools .
==========
-HOW TO SET UP YOUR OWN SGML EDITING ENVIRONMENT:
+HOW TO SET UP YOUR OWN XML EDITING ENVIRONMENT:
==========
-Trying to set up an SGML/XML Docbook editing environment the
+Trying to set up an XML Docbook editing environment the
first time can be a daunting task.
I use Linux-Mandrake, in part, because it has a fully-functional
-SGML/XML Docbook editing environment included as part of the
+XML Docbook editing environment included as part of the
distribution CD's. If you have easier instructions for how to
do this for a particular Linux distribution or platform, please
let the team know at the mailing list: mozilla-webtools@mozilla.org.
@@ -74,9 +72,10 @@ sgml-common
If you're getting these from RedHat, make sure you get the ones in the
rawhide area. The ones in the 7.2 distribution are too old and don't
-include the XML stuff.
+include the XML stuff. The packages distrubuted with RedHat 8.0 and 9
+and known to work.
-Download "ldp.dsl" from the Resources page on linuxdoc.org. This is the
+Download "ldp.dsl" from the Resources page on tldp.org. This is the
stylesheet I use to get the HTML and text output. It works well, and has a
nice, consistent look with the rest of the linuxdoc documents. You'll have to
adjust the paths in ldp.dsl at the top of the file to reflect the actual
@@ -92,6 +91,8 @@ dsssl>
Note the difference is the top one points to the HTML docbook stylesheet,
and the next one points to the PRINT docbook stylesheet.
+Also note that modifying ldp.dsl doesn't seem to be needed on RedHat 9.
+
You know, this sure looks awful involved. Anyway, once you have this in
place, add to your .bashrc:
export SGML_CATALOG_FILES=/etc/sgml/catalog
@@ -111,13 +112,16 @@ for tcsh users.
folders are anywhere else on your system (for example, the openjade version
might change if you get a new version at some point).
- I suggest xemacs for editing your SGML/XML Docbook documents. The darn
+ I suggest xemacs for editing your XML Docbook documents. The darn
thing just works, and generally includes PSGML mode by default. Not to
mention you can validate the SGML from right within it without having to
remember the command-line syntax for nsgml (not that it's that hard
anyway). If not, you can download psgml at
http://www.sourceforge.net/projects/psgml.
+ Another good editor is the latest releases of vim and gvim. Vim will
+recognize DocBook tags and give them a different color than unreconized tags.
+
==========
NOTES:
==========
@@ -125,15 +129,17 @@ NOTES:
Here are the commands I use to maintain this documentation.
You MUST have DocBook 4.1.2 set up correctly in order for this to work.
+ These commands can be run all at once using the ./makedocs.pl script.
+
To create HTML documentation:
bash$ cd html
bash$ jade -t sgml -i html -d $LDP_HOME/ldp.dsl\#html \
-$JADE_PUB/xml.dcl ../sgml/Bugzilla-Guide.sgml
+$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml
To create HTML documentation as a single big HTML file:
bash$ cd html
bash$ jade -V nochunks -t sgml -i html -d $LDP_HOME/ldp.dsl\#html \
-$JADE_PUB/xml.dcl ../sgml/Bugzilla-Guide.sgml >Bugzilla-Guide.html
+$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml >Bugzilla-Guide.html
To create TXT documentation as a single big TXT file:
bash$ cd txt
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html
index 66bb333ec603c3e7651f71010592da0844f8638e..1e70196e65a819bb52c470cfa176f4fb279aebb5 100644
--- a/docs/html/Bugzilla-Guide.html
+++ b/docs/html/Bugzilla-Guide.html
@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
->The Bugzilla Guide</TITLE
+>The Bugzilla Guide - 2.16.3 Release</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
@@ -34,25 +34,38 @@ ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
-NAME="index"><DIV
+NAME="index"
+></A
+><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
-NAME="AEN2">The Bugzilla Guide</H1
+NAME="AEN2"
+></A
+>The Bugzilla Guide - 2.16.3 Release</H1
><H3
CLASS="author"
><A
-NAME="AEN5">Matthew P. Barnson</H3
+NAME="AEN5"
+></A
+>Matthew P. Barnson</H3
><H3
CLASS="author"
><A
-NAME="AEN9">The Bugzilla Team</H3
+NAME="AEN9"
+></A
+>The Bugzilla Team</H3
+><P
+CLASS="pubdate"
+>2003-04-23<BR></P
><DIV
><DIV
CLASS="abstract"
><A
-NAME="AEN13"><P
+NAME="AEN14"
+></A
+><P
></P
><P
> This is the documentation for Bugzilla, the mozilla.org
@@ -64,7 +77,7 @@ NAME="AEN13"><P
><P
>
This documentation is maintained in DocBook 4.1.2 XML format.
- Changes are best submitted as plain text or SGML diffs, attached
+ Changes are best submitted as plain text or XML diffs, attached
to a bug filed in
<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
@@ -307,7 +320,7 @@ HREF="#variants"
><DL
><DT
>D.1. <A
-HREF="#rhbugzilla"
+HREF="#variant-redhat"
>Red Hat Bugzilla</A
></DT
><DT
@@ -338,6 +351,75 @@ HREF="#variant-sourceforge"
></DL
></DD
><DT
+>E. <A
+HREF="#gfdl"
+>GNU Free Documentation License</A
+></DT
+><DD
+><DL
+><DT
+>0. <A
+HREF="#gfdl-0"
+>PREAMBLE</A
+></DT
+><DT
+>1. <A
+HREF="#gfdl-1"
+>APPLICABILITY AND DEFINITIONS</A
+></DT
+><DT
+>2. <A
+HREF="#gfdl-2"
+>VERBATIM COPYING</A
+></DT
+><DT
+>3. <A
+HREF="#gfdl-3"
+>COPYING IN QUANTITY</A
+></DT
+><DT
+>4. <A
+HREF="#gfdl-4"
+>MODIFICATIONS</A
+></DT
+><DT
+>5. <A
+HREF="#gfdl-5"
+>COMBINING DOCUMENTS</A
+></DT
+><DT
+>6. <A
+HREF="#gfdl-6"
+>COLLECTIONS OF DOCUMENTS</A
+></DT
+><DT
+>7. <A
+HREF="#gfdl-7"
+>AGGREGATION WITH INDEPENDENT WORKS</A
+></DT
+><DT
+>8. <A
+HREF="#gfdl-8"
+>TRANSLATION</A
+></DT
+><DT
+>9. <A
+HREF="#gfdl-9"
+>TERMINATION</A
+></DT
+><DT
+>10. <A
+HREF="#gfdl-10"
+>FUTURE REVISIONS OF THIS LICENSE</A
+></DT
+><DT
+><A
+HREF="#gfdl-howto"
+>How to use this License for your documents</A
+></DT
+></DL
+></DD
+><DT
><A
HREF="#glossary"
>Glossary</A
@@ -350,41 +432,82 @@ CLASS="LOT"
CLASS="LOT"
><DT
><B
+>List of Figures</B
+></DT
+><DT
+>4-1. <A
+HREF="#trouble-filetemp-errors"
+>Other File::Temp error messages</A
+></DT
+><DT
+>4-2. <A
+HREF="#trouble-filetemp-patch"
+>Patch for File::Temp in Perl 5.6.0</A
+></DT
+></DL
+></DIV
+><DIV
+CLASS="LOT"
+><DL
+CLASS="LOT"
+><DT
+><B
>List of Examples</B
></DT
><DT
>4-1. <A
-HREF="#AEN989"
+HREF="#AEN861"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
-HREF="#AEN1002"
+HREF="#AEN874"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
-HREF="#AEN1184"
+HREF="#AEN1056"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
></DT
+><DT
+>5-1. <A
+HREF="#upgrade-cvs"
+>Upgrading using CVS</A
+></DT
+><DT
+>5-2. <A
+HREF="#upgrade-tarball"
+>Upgrading using the tarball</A
+></DT
+><DT
+>5-3. <A
+HREF="#upgrade-patches"
+>Upgrading using patches</A
+></DT
></DL
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
-NAME="about">Chapter 1. About This Guide</H1
+NAME="about"
+></A
+>Chapter 1. About This Guide</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="copyright">1.1. Copyright Information</H1
+NAME="copyright"
+></A
+>1.1. Copyright Information</H1
><A
-NAME="AEN31"><TABLE
+NAME="AEN32"
+></A
+><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
@@ -404,7 +527,10 @@ VALIGN="TOP"
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included below.
+ the license is included in <A
+HREF="#gfdl"
+>Appendix E</A
+>.
</P
></TD
><TD
@@ -419,7 +545,7 @@ ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
->Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
+>Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN
></TD
><TD
WIDTH="10%"
@@ -431,730 +557,445 @@ WIDTH="10%"
copyright, or publishing this document in non-electronic form,
please contact The Bugzilla Team.
</P
+></DIV
><DIV
CLASS="section"
-><HR><H2
+><HR><H1
CLASS="section"
><A
-NAME="gfdl">1.1.1. GNU Free Documentation License</H2
+NAME="disclaimer"
+></A
+>1.2. Disclaimer</H1
><P
->Version 1.1, March 2000</P
-><A
-NAME="AEN38"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
+> No liability for the contents of this document can be accepted.
+ Use the concepts, examples, and other content at your own risk.
+ This document may contain errors
+ and inaccuracies that may damage your system, cause your partner
+ to leave you, your boss to fire you, your cats to
+ pee on your furniture and clothing, and global thermonuclear
+ war. Proceed with caution.
+ </P
><P
->Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
- distribute verbatim copies of this license document, but changing it is
- not allowed.</P
-></BLOCKQUOTE
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-0">0. PREAMBLE</H3
+> All copyrights are held by their respective owners, unless
+ specifically noted otherwise. Use of a term in this document
+ should not be regarded as affecting the validity of any
+ trademark or service mark.
+ </P
><P
->The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone the
- effective freedom to copy and redistribute it, with or without modifying
- it, either commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit for their
- work, while not being considered responsible for modifications made by
- others.</P
+> Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". We
+ wholeheartedly endorse the use of GNU/Linux in every situation
+ where it is appropriate. It is an extremely versatile, stable,
+ and robust operating system that offers an ideal operating
+ environment for Bugzilla.
+ </P
><P
->This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft license
- designed for free software.</P
+> You are strongly recommended to make a backup of your system
+ before installing Bugzilla and at regular intervals thereafter.
+ If you implement any suggestion in this Guide, implement this one!
+ </P
><P
->We have designed this License in order to use it for manuals for
- free software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or whether
- it is published as a printed book. We recommend this License principally
- for works whose purpose is instruction or reference.</P
+> Although the Bugzilla development team has taken great care to
+ ensure that all easily-exploitable bugs or options are
+ documented or fixed in the code, security holes surely exist.
+ 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. The Bugzilla development
+ team members, Netscape Communications, America Online Inc., and
+ any affiliated developers or sponsors assume no liability for
+ your use of this product. You have the source code to this
+ product, and are responsible for auditing it yourself to ensure
+ your security needs are met.
+ </P
></DIV
><DIV
CLASS="section"
-><HR><H3
+><HR><H1
CLASS="section"
><A
-NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H3
-><P
->This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed under
- the terms of this License. The "Document", below, refers to any such
- manual or work. Any member of the public is a licensee, and is addressed
- as "you".</P
-><P
->A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.</P
-><P
->A "Secondary Section" is a named appendix or a front-matter section
- of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall subject
- (or to related matters) and contains nothing that could fall directly
- within that overall subject. (For example, if the Document is in part a
- textbook of mathematics, a Secondary Section may not explain any
- mathematics.) The relationship could be a matter of historical connection
- with the subject or with related matters, or of legal, commercial,
- philosophical, ethical or political position regarding them.</P
+NAME="newversions"
+></A
+>1.3. New Versions</H1
><P
->The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in the
- notice that says that the Document is released under this License.</P
+> This is the 2.16.3 version of The Bugzilla Guide. It is so named
+ to match the version of Bugzilla it is disributed with. If you are
+ reading this from any source other than those below, please
+ check one of these mirrors to make sure you are reading an
+ up-to-date version of the Guide.
+ </P
><P
->The "Cover Texts" are certain short passages of text that are
- listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
- that the Document is released under this License.</P
+> The newest version of this guide can always be found at <A
+HREF="http://www.bugzilla.org"
+TARGET="_top"
+>bugzilla.org</A
+>; including
+ documentation for past releases and the current development version.
+ </P
><P
->A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the general
- public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or for
- automatic translation to a variety of formats suitable for input to text
- formatters. A copy made in an otherwise Transparent file format whose
- markup has been designed to thwart or discourage subsequent modification
- by readers is not Transparent. A copy that is not "Transparent" is called
- "Opaque".</P
+> The documentation for the most recent stable release of Bugzilla can also
+ be found at
+ <A
+HREF="http://www.tldp.org"
+TARGET="_top"
+>The Linux Documentation Project</A
+>.
+ </P
><P
->Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML or
- XML using a publicly available DTD, and standard-conforming simple HTML
- designed for human modification. Opaque formats include PostScript, PDF,
- proprietary formats that can be read and edited only by proprietary word
- processors, SGML or XML for which the DTD and/or processing tools are not
- generally available, and the machine-generated HTML produced by some word
- processors for output purposes only.</P
+> The latest version of this document can always be checked out via CVS.
+ Please follow the instructions available at
+ <A
+HREF="http://www.mozilla.org/cvs.html"
+TARGET="_top"
+>the Mozilla CVS page</A
+>,
+ and check out the <TT
+CLASS="filename"
+>mozilla/webtools/bugzilla/docs/</TT
+>
+ subtree.
+ </P
><P
->The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in formats
- which do not have any title page as such, "Title Page" means the text
- near the most prominent appearance of the work's title, preceding the
- beginning of the body of the text.</P
+> The Bugzilla Guide is currently only available in English.
+ If you would like to volunteer to translate it, please contact
+ <A
+HREF="mailto:justdave@syndicomm.com"
+TARGET="_top"
+>Dave Miller</A
+>.
+ </P
></DIV
><DIV
CLASS="section"
-><HR><H3
+><HR><H1
CLASS="section"
><A
-NAME="gfdl-2">2. VERBATIM COPYING</H3
+NAME="credits"
+></A
+>1.4. Credits</H1
><P
->You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies to
- the Document are reproduced in all copies, and that you add no other
- conditions whatsoever to those of this License. You may not use technical
- measures to obstruct or control the reading or further copying of the
- copies you make or distribute. However, you may accept compensation in
- exchange for copies. If you distribute a large enough number of copies
- you must also follow the conditions in section 3.</P
+> The people listed below have made enormous contributions to the
+ creation of this Guide, through their writing, dedicated hacking efforts,
+ numerous e-mail and IRC support sessions, and overall excellent
+ contribution to the Bugzilla community:
+ </P
><P
->You may also lend copies, under the same conditions stated above,
- and you may publicly display copies.</P
-></DIV
+></P
><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-3">3. COPYING IN QUANTITY</H3
-><P
->If you publish printed copies of the Document numbering more than
- 100, and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all these
- Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
- on the back cover. Both covers must also clearly and legibly identify you
- as the publisher of these copies. The front cover must present the full
- title with all words of the title equally prominent and visible. You may
- add other material on the covers in addition. Copying with changes
- limited to the covers, as long as they preserve the title of the Document
- and satisfy these conditions, can be treated as verbatim copying in other
- respects.</P
-><P
->If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit reasonably)
- on the actual cover, and continue the rest onto adjacent pages.</P
-><P
->If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with each
- Opaque copy a publicly-accessible computer-network location containing a
- complete Transparent copy of the Document, free of added material, which
- the general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location until
- at least one year after the last time you distribute an Opaque copy
- (directly or through your agents or retailers) of that edition to the
- public.</P
-><P
->It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-4">4. MODIFICATIONS</H3
-><P
->You may copy and distribute a Modified Version of the Document
- under the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution and
- modification of the Modified Version to whoever possesses a copy of it.
- In addition, you must do these things in the Modified Version:</P
-><P
-></P
-><OL
-TYPE="A"
-><LI
-><P
->Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the History
- section of the Document). You may use the same title as a previous
- version if the original publisher of that version gives
- permission.</P
-></LI
-><LI
-><P
->List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has less
- than five).</P
-></LI
-><LI
-><P
->State on the Title page the name of the publisher of the
- Modified Version, as the publisher.</P
-></LI
-><LI
-><P
->Preserve all the copyright notices of the Document.</P
-></LI
-><LI
-><P
->Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.</P
-></LI
-><LI
-><P
->Include, immediately after the copyright notices, a license
- notice giving the public permission to use the Modified Version under
- the terms of this License, in the form shown in the Addendum
- below.</P
-></LI
-><LI
-><P
->Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.</P
-></LI
-><LI
-><P
->Include an unaltered copy of this License.</P
-></LI
-><LI
-><P
->Preserve the section entitled "History", and its title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.</P
-></LI
-><LI
-><P
->Preserve the network location, if any, given in the Document
- for public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions it
- was based on. These may be placed in the "History" section. You may
- omit a network location for a work that was published at least four
- years before the Document itself, or if the original publisher of the
- version it refers to gives permission.</P
-></LI
-><LI
-><P
->In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements and/or
- dedications given therein.</P
-></LI
-><LI
-><P
->Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.</P
-></LI
-><LI
+CLASS="variablelist"
+><DL
+><DT
+>Matthew P. Barnson <TT
+CLASS="email"
+><<A
+HREF="mailto:mbarnson@sisna.com"
+>mbarnson@sisna.com</A
+>></TT
+></DT
+><DD
><P
->Delete any section entitled "Endorsements". Such a section may
- not be included in the Modified Version.</P
-></LI
-><LI
+>for the Herculaean task of pulling together the Bugzilla Guide
+ and shepherding it to 2.14.
+ </P
+></DD
+><DT
+>Terry Weissman <TT
+CLASS="email"
+><<A
+HREF="mailto:terry@mozilla.org"
+>terry@mozilla.org</A
+>></TT
+></DT
+><DD
><P
->Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.</P
-></LI
-></OL
+>for initially writing Bugzilla and creating the README upon
+ which the UNIX installation documentation is largely based.
+ </P
+></DD
+><DT
+>Tara Hernandez <TT
+CLASS="email"
+><<A
+HREF="mailto:tara@tequilarists.org"
+>tara@tequilarists.org</A
+>></TT
+></DT
+><DD
><P
->If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all of
- these sections as invariant. To do this, add their titles to the list of
- Invariant Sections in the Modified Version's license notice. These titles
- must be distinct from any other section titles.</P
+>for keeping Bugzilla development going strong after Terry left
+ mozilla.org and for running landfill.
+ </P
+></DD
+><DT
+>Dave Lawrence <TT
+CLASS="email"
+><<A
+HREF="mailto:dkl@redhat.com"
+>dkl@redhat.com</A
+>></TT
+></DT
+><DD
><P
->You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various parties--for
- example, statements of peer review or that the text has been approved by
- an organization as the authoritative definition of a standard.</P
+>for providing insight into the key differences between Red
+ Hat's customized Bugzilla, and being largely responsible for
+ <A
+HREF="#variant-redhat"
+>Section D.1</A
+>.
+ </P
+></DD
+><DT
+>Dawn Endico <TT
+CLASS="email"
+><<A
+HREF="mailto:endico@mozilla.org"
+>endico@mozilla.org</A
+>></TT
+></DT
+><DD
><P
->You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of the
- list of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or through
- arrangements made by) any one entity. If the Document already includes a
- cover text for the same cover, previously added by you or by arrangement
- made by the same entity you are acting on behalf of, you may not add
- another; but you may replace the old one, on explicit permission from the
- previous publisher that added the old one.</P
+>for being a hacker extraordinaire and putting up with Matthew's
+ incessant questions and arguments on irc.mozilla.org in #mozwebtools
+ </P
+></DD
+><DT
+>Jacob Steenhagen <TT
+CLASS="email"
+><<A
+HREF="mailto:jake@bugzilla.org"
+>jake@bugzilla.org</A
+>></TT
+></DT
+><DD
><P
->The author(s) and publisher(s) of the Document do not by this
- License give permission to use their names for publicity for or to assert
- or imply endorsement of any Modified Version.</P
+>for taking over documentation during the 2.17 development
+ period and backporting relevent docs changes to this 2.16 branch.
+ </P
+></DD
+></DL
></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-5">5. COMBINING DOCUMENTS</H3
-><P
->You may combine the Document with other documents released under
- this License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and list
- them all as Invariant Sections of your combined work in its license
- notice.</P
><P
->The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single copy.
- If there are multiple Invariant Sections with the same name but different
- contents, make the title of each such section unique by adding at the end
- of it, in parentheses, the name of the original author or publisher of
- that section if known, or else a unique number. Make the same adjustment
- to the section titles in the list of Invariant Sections in the license
- notice of the combined work.</P
+> Last but not least, all the members of the
+ <A
+HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
+TARGET="_top"
+>news://news.mozilla.org/netscape/public/mozilla/webtools</A
+>
+ newsgroup. Without your discussions, insight, suggestions, and patches,
+ this could never have happened.
+ </P
><P
->In the combination, you must combine any sections entitled
- "History" in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements", and
- any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."</P
+> Thanks also go to the following people for significant contributions
+ to this documentation (in alphabetical order):
+ Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
+ .
+ </P
></DIV
><DIV
CLASS="section"
-><HR><H3
+><HR><H1
CLASS="section"
><A
-NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H3
-><P
->You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual copies
- of this License in the various documents with a single copy that is
- included in the collection, provided that you follow the rules of this
- License for verbatim copying of each of the documents in all other
- respects.</P
+NAME="conventions"
+></A
+>1.5. Document Conventions</H1
><P
->You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a copy
- of this License into the extracted document, and follow this License in
- all other respects regarding verbatim copying of that document.</P
-></DIV
+>This document uses the following conventions:</P
><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
+CLASS="informaltable"
><A
-NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H3
+NAME="AEN109"
+></A
><P
->A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of a
- storage or distribution medium, does not as a whole count as a Modified
- Version of the Document, provided no compilation copyright is claimed for
- the compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they are
- not themselves derivative works of the Document.</P
-><P
->If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter of
- the entire aggregate, the Document's Cover Texts may be placed on covers
- that surround only the Document within the aggregate. Otherwise they must
- appear on covers around the whole aggregate.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-8">8. TRANSLATION</H3
+></P
+><TABLE
+BORDER="0"
+CLASS="CALSTABLE"
+><THEAD
+><TR
+><TH
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Descriptions</TH
+><TH
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Appearance</TH
+></TR
+></THEAD
+><TBODY
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Use caution</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <DIV
+CLASS="caution"
><P
->Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include translations
- of some or all Invariant Sections in addition to the original versions of
- these Invariant Sections. You may include a translation of this License
- provided that you also include the original English version of this
- License. In case of a disagreement between the translation and the
- original English version of this License, the original English version
- will prevail.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-9">9. TERMINATION</H3
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
->You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt to
- copy, modify, sublicense or distribute the Document is void, and will
- automatically terminate your rights under this License. However, parties
- who have received copies, or rights, from you under this License will not
- have their licenses terminated so long as such parties remain in full
- compliance.</P
+>Don't run with scissors!</P
+></TD
+></TR
+></TABLE
></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H3
-><P
->The Free Software Foundation may publish new, revised versions of
- the GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- <A
-HREF="http://www.gnu.org/copyleft/"
-TARGET="_top"
-> http://www.gnu.org/copyleft/</A
>
-
- .</P
-><P
->Each version of the License is given a distinguishing version
- number. If the Document specifies that a particular numbered version of
- this License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or of
- any later version that has been published (not as a draft) by the Free
- Software Foundation. If the Document does not specify a version number of
- this License, you may choose any version ever published (not as a draft)
- by the Free Software Foundation.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H3
-CLASS="section"
-><A
-NAME="gfdl-howto">How to use this License for your documents</H3
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Hint</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <DIV
+CLASS="tip"
><P
->To use this License in a document you have written, include a copy
- of the License in the document and put the following copyright and
- license notices just after the title page:</P
-><A
-NAME="AEN128"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
+></P
+><TABLE
+CLASS="tip"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
->Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU Free
- Documentation License, Version 1.1 or any later version published by
- the Free Software Foundation; with the Invariant Sections being LIST
- THEIR TITLES, with the Front-Cover Texts being LIST, and with the
- Back-Cover Texts being LIST. A copy of the license is included in the
- section entitled "GNU Free Documentation License".</P
-></BLOCKQUOTE
+>Would you like a breath mint?</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Notes</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <DIV
+CLASS="note"
><P
->If you have no Invariant Sections, write "with no Invariant
- Sections" instead of saying which ones are invariant. If you have no
- Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
- Texts being LIST"; likewise for Back-Cover Texts.</P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
->If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of free
- software license, such as the GNU General Public License, to permit their
- use in free software.</P
-></DIV
-></DIV
+>Dear John...</P
+></TD
+></TR
+></TABLE
></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="disclaimer">1.2. Disclaimer</H1
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Warnings</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <DIV
+CLASS="warning"
><P
-> No liability for the contents of this document can be accepted.
- Use the concepts, examples, and other content at your own risk.
- This document may contain errors
- and inaccuracies that may damage your system, cause your partner
- to leave you, your boss to fire you, your cats to
- pee on your furniture and clothing, and global thermonuclear
- war. Proceed with caution.
- </P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
-> All copyrights are held by their respective owners, unless
- specifically noted otherwise. Use of a term in this document
- should not be regarded as affecting the validity of any
- trademark or service mark.
- </P
-><P
-> Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". We
- wholeheartedly endorse the use of GNU/Linux in every situation
- where it is appropriate. It is an extremely versatile, stable,
- and robust operating system that offers an ideal operating
- environment for Bugzilla.
- </P
-><P
-> You are strongly recommended to make a backup of your system
- before installing Bugzilla and at regular intervals thereafter.
- If you implement any suggestion in this Guide, implement this one!
- </P
-><P
-> Although the Bugzilla development team has taken great care to
- ensure that all easily-exploitable bugs or options are
- documented or fixed in the code, security holes surely exist.
- 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. The Bugzilla development
- team members, Netscape Communications, America Online Inc., and
- any affiliated developers or sponsors assume no liability for
- your use of this product. You have the source code to this
- product, and are responsible for auditing it yourself to ensure
- your security needs are met.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="newversions">1.3. New Versions</H1
-><P
-> This is the 2.16 version of The Bugzilla Guide. It is so named
- to match the current version of Bugzilla. If you are
- reading this from any source other than those below, please
- check one of these mirrors to make sure you are reading an
- up-to-date version of the Guide.
- </P
-><P
-> This document can be found in the following places:
- </P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
->bugzilla.org</A
->
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.linuxdoc.org/"
-TARGET="_top"
->The Linux
- Documentation Project</A
->
- </P
-></LI
-></UL
->
- </P
-><P
-> The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at
- <A
-HREF="http://www.mozilla.org/cvs.html"
-TARGET="_top"
->the Mozilla CVS page</A
->,
- and check out the <TT
-CLASS="filename"
->mozilla/webtools/bugzilla/docs/</TT
->
- subtree.
- </P
-><P
-> The Bugzilla Guide is currently only available in English.
- If you would like to volunteer to translate it, please contact
- <A
-HREF="mailto:justdave@syndicomm.com"
-TARGET="_top"
->Dave Miller</A
->.
- </P
+>Read this or the cat gets it.</P
+></TD
+></TR
+></TABLE
></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="credits">1.4. Credits</H1
-><P
-> The people listed below have made enormous contributions to the
- creation of this Guide, through their writing, dedicated hacking efforts,
- numerous e-mail and IRC support sessions, and overall excellent
- contribution to the Bugzilla community:
- </P
-><P
-> <A
-HREF="mailto://mbarnson@sisna.com"
-TARGET="_top"
->Matthew P. Barnson</A
->
- for the Herculaean task of pulling together the Bugzilla Guide and
- shepherding it to 2.14.
- </P
-><P
-> <A
-HREF="mailto://terry@mozilla.org"
-TARGET="_top"
->Terry Weissman</A
>
- for initially writing Bugzilla and creating the
- README upon which the UNIX installation documentation is largely based.
- </P
-><P
-> <A
-HREF="mailto://tara@tequilarista.org"
-TARGET="_top"
->Tara Hernandez</A
->
- for keeping Bugzilla development going
- strong after Terry left mozilla.org
- </P
-><P
-> <A
-HREF="mailto://dkl@redhat.com"
-TARGET="_top"
->Dave Lawrence</A
->
- for providing insight into the key differences between Red Hat's
- customized Bugzilla, and being largely responsible for the "Red
- Hat Bugzilla" appendix
- </P
-><P
-> <A
-HREF="mailto://endico@mozilla.org"
-TARGET="_top"
->Dawn Endico</A
-> for
- being a hacker extraordinaire and putting up with my incessant
- questions and arguments on irc.mozilla.org in #mozwebtools
- </P
-><P
-> Last but not least, all the members of the
- <A
-HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
-TARGET="_top"
-> netscape.public.mozilla.webtools</A
-> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
- </P
-><P
-> Thanks also go to the following people for significant contributions
- to this documentation (in no particular order):
- </P
-><P
-> Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
- Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="conventions">1.5. Document Conventions</H1
-><P
->This document uses the following conventions:</P
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN178"><P
-></P
-><TABLE
-BORDER="0"
-CLASS="CALSTABLE"
-><THEAD
+ </TD
+></TR
><TR
-><TH
+><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Descriptions</TH
-><TH
+>File Names</TD
+><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Appearance</TH
+> <TT
+CLASS="filename"
+>filename</TT
+>
+ </TD
></TR
-></THEAD
-><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Warnings</TD
+>Directory Names</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
-> <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't run with scissors!</P
-></TD
-></TR
-></TABLE
-></DIV
+> <TT
+CLASS="filename"
+>directory</TT
>
</TD
></TR
@@ -1162,36 +1003,27 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Hint</TD
+>Commands to be typed</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
-> <DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
+> <B
+CLASS="command"
+>command</B
+>
+ </TD
+></TR
><TR
><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+>Applications Names</TD
><TD
ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Would you like a breath mint?</P
-></TD
-></TR
-></TABLE
-></DIV
+VALIGN="MIDDLE"
+> <SPAN
+CLASS="application"
+>application</SPAN
>
</TD
></TR
@@ -1199,147 +1031,17 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Notes</TD
+> <I
+CLASS="foreignphrase"
+>Prompt</I
+>
+
+ of users command under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
-> <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Dear John...</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Information requiring special attention</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Read this or the cat gets it.</P
-></TD
-></TR
-></TABLE
-></DIV
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->File Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->filename</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Directory Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <TT
-CLASS="filename"
->directory</TT
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Commands to be typed</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <B
-CLASS="command"
->command</B
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Applications Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <SPAN
-CLASS="application"
->application</SPAN
->
- </TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-> <I
-CLASS="foreignphrase"
->Prompt</I
->
-
- of users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash$</TD
-></TR
+>bash$</TD
+></TR
><TR
><TD
ALIGN="LEFT"
@@ -1401,6 +1103,23 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
+>Term found in the glossary</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <A
+HREF="#gloss-bugzilla"
+><I
+CLASS="glossterm"
+>Bugzilla</I
+></A
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
@@ -1442,19 +1161,29 @@ CLASS="sgmltag"
CLASS="chapter"
><HR><H1
><A
-NAME="introduction">Chapter 2. Introduction</H1
+NAME="introduction"
+></A
+>Chapter 2. Introduction</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="whatis">2.1. What is Bugzilla?</H1
+NAME="whatis"
+></A
+>2.1. What is Bugzilla?</H1
><P
> Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
of outstanding problems with their product.
- Bugzilla was originally
- written by Terry Weissman in a programming language called TCL, to
+ Bugzilla was originally written by Terry Weissman in a programming language
+ called <A
+HREF="#gloss-tcl"
+><I
+CLASS="glossterm"
+>TCL</I
+></A
+>, to
replace a rudimentary bug-tracking database used internally by Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
it remains to this day. Most commercial defect-tracking software vendors
@@ -1526,7 +1255,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="why">2.2. Why Should We Use Bugzilla?</H1
+NAME="why"
+></A
+>2.2. Why Should We Use Bugzilla?</H1
><P
>For many years, defect-tracking software has remained principally
the domain of large software development houses. Even then, most shops
@@ -1598,13 +1329,17 @@ TARGET="_top"
CLASS="chapter"
><HR><H1
><A
-NAME="using">Chapter 3. Using Bugzilla</H1
+NAME="using"
+></A
+>Chapter 3. Using Bugzilla</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="how">3.1. How do I use Bugzilla?</H1
+NAME="how"
+></A
+>3.1. How do I use Bugzilla?</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
@@ -1623,7 +1358,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount"
+></A
+>3.1.1. Create a Bugzilla Account</H2
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
@@ -1691,7 +1428,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="bug_page">3.1.2. Anatomy of a Bug</H2
+NAME="bug_page"
+></A
+>3.1.2. Anatomy of a Bug</H2
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
@@ -1956,7 +1695,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="query">3.1.3. Searching for Bugs</H2
+NAME="query"
+></A
+>3.1.3. Searching for Bugs</H2
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
@@ -1989,7 +1730,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="list">3.1.4. Bug Lists</H2
+NAME="list"
+></A
+>3.1.4. Bug Lists</H2
><P
>If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system - don't try
@@ -2061,7 +1804,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="bugreports">3.1.5. Filing Bugs</H2
+NAME="bugreports"
+></A
+>3.1.5. Filing Bugs</H2
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
@@ -2120,7 +1865,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="hintsandtips">3.2. Hints and Tips</H1
+NAME="hintsandtips"
+></A
+>3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
@@ -2129,7 +1876,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN434">3.2.1. Autolinkification</H2
+NAME="AEN370"
+></A
+>3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
@@ -2192,7 +1941,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="quicksearch">3.2.2. Quicksearch</H2
+NAME="quicksearch"
+></A
+>3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
@@ -2223,7 +1974,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="commenting">3.2.3. Comments</H2
+NAME="commenting"
+></A
+>3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
@@ -2245,7 +1998,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="attachments">3.2.4. Attachments</H2
+NAME="attachments"
+></A
+>3.2.4. Attachments</H2
><P
> Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
@@ -2269,7 +2024,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN463">3.2.5. Filing Bugs</H2
+NAME="AEN399"
+></A
+>3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
@@ -2293,7 +2050,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="userpreferences">3.3. User Preferences</H1
+NAME="userpreferences"
+></A
+>3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
@@ -2303,7 +2062,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="accountsettings">3.3.1. Account Settings</H2
+NAME="accountsettings"
+></A
+>3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
@@ -2326,7 +2087,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="emailsettings">3.3.2. Email Settings</H2
+NAME="emailsettings"
+></A
+>3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
@@ -2373,7 +2136,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="footersettings">3.3.3. Page Footer</H2
+NAME="footersettings"
+></A
+>3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
@@ -2385,7 +2150,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="permissionsettings">3.3.4. Permissions</H2
+NAME="permissionsettings"
+></A
+>3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
@@ -2398,19 +2165,25 @@ NAME="permissionsettings">3.3.4. Permissions</H2
CLASS="chapter"
><HR><H1
><A
-NAME="installation">Chapter 4. Installation</H1
+NAME="installation"
+></A
+>Chapter 4. Installation</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="stepbystep">4.1. Step-by-step Install</H1
+NAME="stepbystep"
+></A
+>4.1. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN492">4.1.1. Introduction</H2
+NAME="AEN428"
+></A
+>4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
@@ -2428,7 +2201,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN496">4.1.2. Package List</H2
+NAME="AEN432"
+></A
+>4.1.2. Package List</H2
><DIV
CLASS="note"
><P
@@ -2806,7 +2581,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="install-mysql">4.1.3. MySQL</H2
+NAME="install-mysql"
+></A
+>4.1.3. MySQL</H2
><P
>Visit the MySQL homepage at
<A
@@ -2908,7 +2685,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="install-perl">4.1.4. Perl</H2
+NAME="install-perl"
+></A
+>4.1.4. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
@@ -2925,7 +2704,9 @@ TARGET="_top"
><DIV
CLASS="tip"
><A
-NAME="bundlebugzilla"><P
+NAME="bundlebugzilla"
+></A
+><P
></P
><TABLE
CLASS="tip"
@@ -2990,7 +2771,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="perl-modules">4.1.5. Perl Modules</H2
+NAME="perl-modules"
+></A
+>4.1.5. Perl Modules</H2
><P
>
All Perl modules can be found on the
@@ -3153,7 +2936,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN642">4.1.5.1. DBI</H3
+NAME="AEN578"
+></A
+>4.1.5.1. DBI</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
@@ -3166,7 +2951,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN645">4.1.5.2. Data::Dumper</H3
+NAME="AEN581"
+></A
+>4.1.5.2. Data::Dumper</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
@@ -3178,7 +2965,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN648">4.1.5.3. MySQL-related modules</H3
+NAME="AEN584"
+></A
+>4.1.5.3. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
@@ -3202,7 +2991,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN653">4.1.5.4. TimeDate modules</H3
+NAME="AEN589"
+></A
+>4.1.5.4. TimeDate modules</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
@@ -3216,7 +3007,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN656">4.1.5.5. GD (optional)</H3
+NAME="AEN592"
+></A
+>4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
@@ -3269,7 +3062,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN663">4.1.5.6. Chart::Base (optional)</H3
+NAME="AEN599"
+></A
+>4.1.5.6. Chart::Base (optional)</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
@@ -3282,7 +3077,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="AEN666">4.1.5.7. Template Toolkit</H3
+NAME="AEN602"
+></A
+>4.1.5.7. Template Toolkit</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
@@ -3298,7 +3095,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN669">4.1.6. HTTP Server</H2
+NAME="AEN605"
+></A
+>4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
@@ -3374,7 +3173,9 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
->Options ExecCGI AllowOverride Limit</PRE
+> Options ExecCGI
+AllowOverride Limit
+ </PRE
></FONT
></TD
></TR
@@ -3472,7 +3273,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN688">4.1.7. Bugzilla</H2
+NAME="AEN624"
+></A
+>4.1.7. Bugzilla</H2
><P
>You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
@@ -3583,7 +3386,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN705">4.1.8. Setting Up the MySQL Database</H2
+NAME="AEN641"
+></A
+>4.1.8. Setting Up the MySQL Database</H2
><P
>After you've gotten all the software installed and working you're
ready to start preparing the database for its life as the back end to
@@ -3748,13 +3553,43 @@ CLASS="command"
></P
>
</P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you are using MySQL 4, the bugs user also needs to be granted
+ the LOCK TABLES and CREATE TEMPORARY TABLES permissions.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN741">4.1.9. <TT
+NAME="AEN679"
+></A
+>4.1.9. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
@@ -3905,313 +3740,43 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN773">4.1.10. Securing MySQL</H2
+NAME="AEN711"
+></A
+>4.1.10. Configuring Bugzilla</H2
><P
->If you followed the installation instructions for setting up your
- "bugs" and "root" user in MySQL, much of this should not apply to you.
- If you are upgrading an existing installation of Bugzilla, you should
- pay close attention to this section.</P
+> You should run through the parameters on the Edit Parameters page
+ (link in the footer) and set them all to appropriate values.
+ They key parameters are documented in <A
+HREF="#parameters"
+>Section 5.1</A
+>.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="extraconfig"
+></A
+>4.2. Optional Additional Configuration</H1
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="AEN717"
+></A
+>4.2.1. Dependency Charts</H2
><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
+>As well as the text-based dependency graphs, Bugzilla also
+ supports dependency graphing, using a package called 'dot'.
+ Exactly how this works is controlled by the 'webdotbase' parameter,
+ which can have one of three values:
+ </P
><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></TT
->
-
- <B
-CLASS="command"
->use mysql;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->show tables;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->select * from user;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></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->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
->running MySQL in a chroot jail</P
-></LI
-><LI
-><P
->running the httpd in a chroot 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"
-><HR><H2
-CLASS="section"
-><A
-NAME="AEN839">4.1.11. Configuring Bugzilla</H2
-><P
-> You should run through the parameters on the Edit Parameters page
- (link in the footer) and set them all to appropriate values.
- They key parameters are documented in <A
-HREF="#parameters"
->Section 5.1</A
->.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="extraconfig">4.2. Optional Additional Configuration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN845">4.2.1. Dependency Charts</H2
-><P
->As well as the text-based dependency graphs, Bugzilla also
- supports dependency graphing, using a package called 'dot'.
- Exactly how this works is controlled by the 'webdotbase' parameter,
- which can have one of three values:
- </P
-><P
-> <P
+> <P
></P
><OL
TYPE="1"
@@ -4265,7 +3830,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN860">4.2.2. Bug Graphs</H2
+NAME="AEN732"
+></A
+>4.2.2. Bug Graphs</H2
><P
>As long as you installed the GD and Graph::Base Perl modules you
might as well turn on the nifty Bugzilla bug reporting graphs.</P
@@ -4322,7 +3889,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN873">4.2.3. The Whining Cron</H2
+NAME="AEN745"
+></A
+>4.2.3. The Whining Cron</H2
><P
>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
@@ -4408,7 +3977,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="bzldap">4.2.4. LDAP Authentication</H2
+NAME="bzldap"
+></A
+>4.2.4. LDAP Authentication</H2
><P
> <DIV
CLASS="warning"
@@ -4499,7 +4070,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
+NAME="content-type"
+></A
+>4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
@@ -4569,7 +4142,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="htaccess">4.2.6. <TT
+NAME="htaccess"
+></A
+>4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
@@ -4739,7 +4314,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="mod-throttle">4.2.7. <TT
+NAME="mod-throttle"
+></A
+>4.2.7. <TT
CLASS="filename"
>mod_throttle</TT
>
@@ -4788,7 +4365,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="win32">4.3. Win32 Installation Notes</H1
+NAME="win32"
+></A
+>4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
@@ -4865,7 +4444,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2
+NAME="wininstall"
+></A
+>4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
@@ -5100,7 +4681,9 @@ CLASS="command"
><DIV
CLASS="example"
><A
-NAME="AEN989"><P
+NAME="AEN861"
+></A
+><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
@@ -5158,7 +4741,9 @@ TARGET="_top"
<DIV
CLASS="example"
><A
-NAME="AEN1002"><P
+NAME="AEN874"
+></A
+><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
@@ -6272,7 +5857,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="addlwintips">4.3.2. Additional Windows Tips</H2
+NAME="addlwintips"
+></A
+>4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
@@ -6296,7 +5883,9 @@ VALIGN="TOP"
><P
>From Andrew Pearson:
<A
-NAME="AEN1172"><BLOCKQUOTE
+NAME="AEN1044"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
@@ -6375,11 +5964,13 @@ VALIGN="TOP"
>
for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla &bz-ver;.
+ Bugzilla 2.16.3.
<DIV
CLASS="example"
><A
-NAME="AEN1184"><P
+NAME="AEN1056"
+></A
+><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
@@ -6438,7 +6029,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="osx">4.4. Mac OS X Installation Notes</H1
+NAME="osx"
+></A
+>4.4. Mac OS X Installation Notes</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
@@ -6488,7 +6081,7 @@ CLASS="command"
This should go through the motions of downloading the latest version of
the GD module, then it will open a shell and drop you into the build
directory. Apply <A
-HREF="../sgml/gd-makefile.patch"
+HREF="../xml/gd-makefile.patch"
TARGET="_top"
>this patch</A
>
@@ -6561,7 +6154,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="troubleshooting">4.5. Troubleshooting</H1
+NAME="troubleshooting"
+></A
+>4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
@@ -6571,7 +6166,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1218">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+NAME="AEN1090"
+></A
+>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
> Try executing <B
CLASS="command"
@@ -6594,7 +6191,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1223">4.5.2. DBD::Sponge::db prepare failed</H2
+NAME="AEN1095"
+></A
+>4.5.2. DBD::Sponge::db prepare failed</H2
><P
> The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
@@ -6678,7 +6277,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
+NAME="paranoid-security"
+></A
+>4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
distributions with
@@ -6729,19 +6330,133 @@ CLASS="filename"
as root to fix this problem.
</P
></DIV
-></DIV
-></DIV
-><DIV
-CLASS="chapter"
-><HR><H1
-><A
-NAME="administration">Chapter 5. Administering Bugzilla</H1
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="trouble-filetemp"
+></A
+>4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
+><P
+>This is caused by a bug in the version of
+ <SPAN
+CLASS="productname"
+>File::Temp</SPAN
+> that is distributed with perl
+ 5.6.0. Many minor variations of this error have been reported. Examples
+ can be found in <A
+HREF="#trouble-filetemp-errors"
+>Figure 4-1</A
+>.
+ </P
+><DIV
+CLASS="figure"
+><A
+NAME="trouble-filetemp-errors"
+></A
+><P
+><B
+>Figure 4-1. Other File::Temp error messages</B
+></P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> Your vendor has not defined Fcntl macro O_NOINHERIT, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
+
+Your vendor has not defined Fcntl macro O_EXLOCK, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
+
+Your vendor has not defined Fcntl macro O_TEMPORARY, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Numerous people have reported that upgrading to version 5.6.1
+ or higher solved the problem for them. A less involved fix is to apply
+ the patch in <A
+HREF="#trouble-filetemp-patch"
+>Figure 4-2</A
+>. The patch is also
+ available as a <A
+HREF="../xml/filetemp.patch"
+TARGET="_top"
+>patch file</A
+>.
+ </P
+><DIV
+CLASS="figure"
+><A
+NAME="trouble-filetemp-patch"
+></A
+><P
+><B
+>Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
+></P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
++++ File/Temp.pm Thu Feb 6 16:26:23 2003
+@@ -205,6 +205,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+@@ -226,6 +227,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="chapter"
+><HR><H1
+><A
+NAME="administration"
+></A
+>Chapter 5. Administering Bugzilla</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="parameters">5.1. Bugzilla Configuration</H1
+NAME="parameters"
+></A
+>5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
@@ -7041,13 +6756,17 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="useradmin">5.2. User Administration</H1
+NAME="useradmin"
+></A
+>5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="defaultuser">5.2.1. Creating the Default User</H2
+NAME="defaultuser"
+></A
+>5.2.1. Creating the Default User</H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
@@ -7139,13 +6858,17 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="manageusers">5.2.2. Managing Other Users</H2
+NAME="manageusers"
+></A
+>5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
-NAME="createnewusers">5.2.2.1. Creating new users</H3
+NAME="createnewusers"
+></A
+>5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
@@ -7216,7 +6939,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
-NAME="modifyusers">5.2.2.2. Modifying Users</H3
+NAME="modifyusers"
+></A
+>5.2.2.2. Modifying Users</H3
><P
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
@@ -7445,13 +7170,17 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
+NAME="programadmin"
+></A
+>5.3. Product, Component, Milestone, and Version Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="products">5.3.1. Products</H2
+NAME="products"
+></A
+>5.3.1. Products</H2
><P
> <A
HREF="#gloss-product"
@@ -7505,7 +7234,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="components">5.3.2. Components</H2
+NAME="components"
+></A
+>5.3.2. Components</H2
><P
>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
@@ -7558,7 +7289,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="versions">5.3.3. Versions</H2
+NAME="versions"
+></A
+>5.3.3. Versions</H2
><P
>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
@@ -7592,7 +7325,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="milestones">5.3.4. Milestones</H2
+NAME="milestones"
+></A
+>5.3.4. Milestones</H2
><P
>Milestones are "targets" that you plan to get a bug fixed by. For
example, you have a bug that you plan to fix for your 3.0 release, it
@@ -7693,7 +7428,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="voting">5.4. Voting</H1
+NAME="voting"
+></A
+>5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
@@ -7753,7 +7490,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="groups">5.5. Groups and Group Security</H1
+NAME="groups"
+></A
+>5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
@@ -7894,7 +7633,9 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="security">5.6. Bugzilla Security</H1
+NAME="security"
+></A
+>5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
@@ -7948,63 +7689,233 @@ VALIGN="TOP"
><P
>These instructions must, of necessity, be somewhat vague since
Bugzilla runs on so many different platforms. If you have refinements
- of these directions for specific platforms, please submit them to
- <A
-HREF="mailto://mozilla-webtools@mozilla.org"
+ of these directions, please submit a bug to <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
-> mozilla-webtools@mozilla.org</A
->
+>Bugzilla</A
+>.
</P
></TD
></TR
></TABLE
></DIV
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>This is not meant to be a comprehensive list of every possible
+ security issue regarding the tools mentioned in this section. There is
+ no subsitute for reading the information written by the authors of any
+ software running on your system.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="security-networking"
+></A
+>5.6.1. TCP/IP Ports</H2
+><P
+>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
+ only needs 1... 2 if you need to use features that require e-mail such
+ as bug moving or the e-mail interface from contrib. You should audit
+ your server and make sure that you aren't listening on any ports you
+ don't need to be. You may also wish to use some kind of firewall
+ software to be sure that trafic can only be recieved on ports you
+ specify.
+ </P
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="security-mysql"
+></A
+>5.6.2. MySQL</H2
+><P
+>MySQL ships by default with many settings that should be changed.
+ By defaults it allows anybody to connect from localhost without a
+ password and have full administrative capabilities. It also defaults to
+ not have a root password (this is <EM
+>not</EM
+> the same as
+ the system root). Also, many installations default to running
+ <SPAN
+CLASS="application"
+>mysqld</SPAN
+> as the system root.
+ </P
><P
->To secure your installation:
-
- <P
></P
><OL
TYPE="1"
><LI
><P
->Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and (from a security
- point of view) poor default configuration choices.</P
+>Make sure you are running at least version 3.22.32 of MySQL
+ as earlier versions had notable security holes.
+ </P
></LI
><LI
><P
-> <EM
->There is no substitute for understanding the tools on your
- system!</EM
->
-
- Read
- <A
-HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
-TARGET="_top"
-> The MySQL Privilege System</A
->
- until you can recite it from memory!</P
+>Consult the documentation that came with your system for
+ information on making <SPAN
+CLASS="application"
+>mysqld</SPAN
+> run as an
+ unprivleged user.
+ </P
></LI
><LI
><P
->Lock down /etc/inetd.conf. Heck, disable inet entirely on this
- box. It should only listen to port 25 for Sendmail and port 80 for
- Apache.</P
+>You should also be sure to disable the anonymous user account
+ and set a password for the root user. This is accomplished using the
+ following commands:
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> <TT
+CLASS="prompt"
+>bash$</TT
+> mysql mysql
+<TT
+CLASS="prompt"
+>mysql></TT
+> DELETE FROM user WHERE user = '';
+<TT
+CLASS="prompt"
+>mysql></TT
+> UPDATE user SET password = password('<TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+>') WHERE user = 'root';
+<TT
+CLASS="prompt"
+>mysql></TT
+> FLUSH PRIVILEGES;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>From this point forward you will need to use
+ <B
+CLASS="command"
+>mysql -u root -p</B
+> and enter
+ <TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+> when prompted when using the
+ mysql client.
+ </P
></LI
><LI
><P
->Do not run Apache as
- <SPAN
+>If you run MySQL on the same machine as your httpd server, you
+ should consider disabling networking from within MySQL by adding
+ the following to your <TT
+CLASS="filename"
+>/etc/my.conf</TT
+>:
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> [myslqd]
+# Prevent network access to MySQL.
+skip-networking
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></LI
+><LI
+><P
+>You may also consider running MySQL, or even all of Bugzilla
+ in a chroot jail; however, instructions for doing that are beyond
+ the scope of this document.
+ </P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="security-daemon"
+></A
+>5.6.3. Daemon Accounts</H2
+><P
+>Many daemons, such as Apache's httpd and MySQL's mysqld default to
+ running as either <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> or <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
->
-
- . 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.
- <DIV
+>. Running
+ as <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> introduces obvious security problems, but the
+ problems introduced by running everything as <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> may
+ not be so obvious. Basically, if you're running every daemon as
+ <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> and one of them gets comprimised, they all get
+ comprimised. For this reason it is recommended that you create a user
+ account for each daemon.
+ </P
+><DIV
CLASS="note"
><P
></P
@@ -8025,83 +7936,238 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->
-
- is a real user on UNIX systems. Having a process run as user id
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->
-
- is absolutely no protection against system crackers versus using
- any other user account. As a general security measure, I recommend
- you create unique user ID's for each daemon running on your system
- and, if possible, use "chroot" to jail that process away from the
- rest of your system.</P
+>You will need to set the <TT
+CLASS="varname"
+>webservergroup</TT
+> to
+ the group you created for your webserver to run as in
+ <TT
+CLASS="filename"
+>localconfig</TT
+>. This will allow
+ <B
+CLASS="command"
+>./checksetup.pl</B
+> to better adjust the file
+ permissions on your Bugzilla install so as to not require making
+ anything world-writable.
+ </P
></TD
></TR
></TABLE
></DIV
->
- </P
-></LI
-><LI
-><P
->Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ directory, as well as the
- $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" database account password.
- In addition, some
- files under $BUGZILLA_HOME/data/ store sensitive information.
- </P
-><P
->Bugzilla provides default .htaccess files to protect the most
- common Apache installations. However, you should verify these are
- adequate according to the site-wide security policy of your web
- server, and ensure that the .htaccess files are allowed to
- "override" default permissions set in your Apache configuration
- files. Covering Apache security is beyond the scope of this Guide;
- please consult the Apache documentation for details.</P
-><P
->If you are using a web server that does not support the
- .htaccess control method,
- <EM
->you are at risk!</EM
->
-
- After installing, check to see if you can view the file
- "localconfig" in your web browser (e.g.:
- <A
-HREF="http://bugzilla.mozilla.org/localconfig"
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="security-access"
+></A
+>5.6.4. Web Server Access Controls</H2
+><P
+>There are many files that are placed in the Bugzilla directory
+ area that should not be accessable from the web. Because of the way
+ Bugzilla is currently layed out, the list of what should and should
+ not be accessible is rather complicated. A new installation method
+ is currently in the works which should solve this by allowing files
+ that shouldn't be accessible from the web to be placed in directory
+ outside the webroot. See
+ <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
TARGET="_top"
-> http://bugzilla.mozilla.org/localconfig</A
+>bug
+ 44659</A
+> for more information.
+ </P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>In the main Bugzilla directory, you should:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block:
+ <TT
+CLASS="filename"
+>*.pl</TT
+>, <TT
+CLASS="filename"
+>*localconfig*</TT
+>, <TT
+CLASS="filename"
+>runtests.sh</TT
+>, <TT
+CLASS="filename"
+>processmail</TT
+>, <TT
+CLASS="filename"
+>syncshadowdb</TT
>
-
- ). If you can read the contents of this file, your web server has
- not secured your bugzilla directory properly and you must fix this
- problem before deploying Bugzilla. If, however, it gives you a
- "Forbidden" error, then it probably respects the .htaccess
- conventions and you are good to go.</P
+ </P
+></LI
+><LI
><P
->When you run checksetup.pl, the script will attempt to modify
- various permissions on files which Bugzilla uses. If you do not have
- a webservergroup set in the localconfig file, then Bugzilla will have
- to make certain files world readable and/or writable.
- <EM
->THIS IS INSECURE!</EM
+>But allow:
+ <TT
+CLASS="filename"
+>localconfig.js</TT
+>, <TT
+CLASS="filename"
+>localconfig.rdf</TT
>
-
- . This means that anyone who can get access to your system can do
- whatever they want to your Bugzilla installation.</P
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>data</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow:
+ <TT
+CLASS="filename"
+>duplicates.rdf</TT
+>
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>data/webdot</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>If you use a remote webdot server:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow
+ <TT
+CLASS="filename"
+>*.dot</TT
+>
+ only for the remote webdot server</P
+></LI
+></UL
+></LI
+><LI
+><P
+>Otherwise, if you use a local GraphViz:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow:
+ <TT
+CLASS="filename"
+>*.png</TT
+>, <TT
+CLASS="filename"
+>*.gif</TT
+>, <TT
+CLASS="filename"
+>*.jpg</TT
+>, <TT
+CLASS="filename"
+>*.map</TT
+>
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>And if you don't use any dot:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>Bugzilla</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>template</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
><DIV
-CLASS="note"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="note"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@@ -8110,74 +8176,86 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
-SRC="../images/note.gif"
+SRC="../images/tip.gif"
HSPACE="5"
-ALT="Note"></TD
+ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
->This also means that if your webserver runs all cgi scripts
- as the same user/group, anyone on the system who can run cgi
- scripts will be able to take control of your Bugzilla
- installation.</P
+>Bugzilla ships with the ability to generate
+ <TT
+CLASS="filename"
+>.htaccess</TT
+> files instructing Apache which files
+ should and should not be accessible.
+ </P
></TD
></TR
></TABLE
></DIV
><P
->On Apache, you can use .htaccess files to protect access to
- these directories, as outlined in
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
-TARGET="_top"
->Bug
- 57161</A
->
-
- for the localconfig file, and
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
+>You should test to make sure that the files mentioned above are
+ not accessible from the Internet, especially your
+ <TT
+CLASS="filename"
+>localconfig</TT
+> file which contains your database
+ password. To test, simply point your web browser at the file; for
+ example, to test mozilla.org's installation, we'd try to access
+ <A
+HREF="http://bugzilla.mozilla.org/localconfig"
TARGET="_top"
->Bug
- 65572</A
+>http://bugzilla.mozilla.org/localconfig</A
+>. You should
+ get a <SPAN
+CLASS="errorcode"
+>403</SPAN
+> <SPAN
+CLASS="errorname"
+>Forbidden</SPAN
>
-
- for adequate protection in your data/ directory.</P
-><P
->Note the instructions which follow are Apache-specific. If you
- use IIS, Netscape, or other non-Apache web servers, please consult
- your system documentation for how to secure these files from being
- transmitted to curious users.</P
+ error.
+ </P
+><DIV
+CLASS="caution"
><P
->Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/data directory.
- <P
-CLASS="literallayout"
-><Files comments> allow from all </Files><br>
- deny from all</P
->
- </P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
->Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/ directory.
- <P
-CLASS="literallayout"
-><Files localconfig> deny from all </Files><br>
- allow from all</P
->
+>Not following the instructions in this section, including
+ testing, may result in sensitive information being globally
+ accessible.
</P
-></LI
-></OL
->
- </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="cust-templates">5.7. Template Customisation</H1
+NAME="cust-templates"
+></A
+>5.7. Template Customisation</H1
><P
> One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
@@ -8201,7 +8279,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1539">5.7.1. What to Edit</H2
+NAME="AEN1532"
+></A
+>5.7.1. What to Edit</H2
><P
> There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
@@ -8314,7 +8394,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1558">5.7.2. How To Edit Templates</H2
+NAME="AEN1551"
+></A
+>5.7.2. How To Edit Templates</H2
><P
> The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
@@ -8394,7 +8476,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1568">5.7.3. Template Formats</H2
+NAME="AEN1561"
+></A
+>5.7.3. Template Formats</H2
><P
> Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
@@ -8454,7 +8538,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1581">5.7.4. Particular Templates</H2
+NAME="AEN1574"
+></A
+>5.7.4. Particular Templates</H2
><P
> There are a few templates you may be particularly interested in
customising for your installation.
@@ -8627,238 +8713,718 @@ CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="upgrading">5.8. Upgrading to New Releases</H1
+NAME="upgrading"
+></A
+>5.8. Upgrading to New Releases</H1
><P
->A plain Bugzilla is fairly easy to upgrade from one version to a
- newer one. Always read the release notes to see if there are any issues
- that you might need to take note of. It is recommended that you take a
- backup of your database and your entire Bugzilla installation before attempting an
- upgrade. You can upgrade a 'clean' installation by untarring a new
- tarball over the old installation. If you are upgrading from 2.12 or
- later, and have cvs installed, you can type <TT
-CLASS="filename"
->cvs -z3 update</TT
->,
- and resolve conflicts if there are any.
+>Upgrading Bugzilla is something we all want to do from time to time,
+ be it to get new features or pick up the latest security fix. How easy
+ it is to update depends on a few factors.
</P
><P
->However, things get a bit more complicated if you've made
- changes to Bugzilla's code. In this case, you may have to re-make or
- reapply those changes. One good method is to take a diff of your customised
- version against the original, so you can survey all that you've changed.
- Hopefully, templatisation will reduce the need for
- this in the future.</P
-><P
->From version 2.8 onwards, Bugzilla databases can be automatically
- carried forward during an upgrade. However, because the developers of
- Bugzilla are constantly adding new
- tables, columns and fields, you'll probably get SQL errors if you just
- update the code and attempt to use Bugzilla. Always run the
- <TT
-CLASS="filename"
->checksetup.pl</TT
->
- script whenever you upgrade your installation.</P
+></P
+><UL
+><LI
><P
->If you are running Bugzilla version 2.8 or lower, and wish to
- upgrade to the latest version, please consult the file,
- "UPGRADING-pre-2.8" in the Bugzilla root directory after untarring the
- archive.</P
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bonsai">5.9.1. Bonsai</H2
+>If the new version is a revision or a new point release</P
+></LI
+><LI
><P
->Bonsai is a web-based tool for managing
- <A
-HREF="#cvs"
->CVS, the Concurrent Versioning System</A
->
-
- . Using Bonsai, administrators can control open/closed status of trees,
- query a fast relational database back-end for change, branch, and comment
- information, and view changes made since the last time the tree was
- closed. Bonsai
- also integrates with
- <A
-HREF="#tinderbox"
->Tinderbox, the Mozilla automated build management system</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="cvs">5.9.2. CVS</H2
+>How many, if any, local changes have been made</P
+></LI
+></UL
><P
->CVS integration is best accomplished, at this point, using the
- Bugzilla Email Gateway.</P
+>There are also three different methods to upgrade your installation.
+ </P
><P
->Follow the instructions in this Guide for enabling Bugzilla e-mail
- integration. Ensure that your check-in script sends an email to your
- Bugzilla e-mail gateway with the subject of
- <SPAN
-CLASS="QUOTE"
->"[Bug XXXX]"</SPAN
->,
- and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+></P
+><OL
+TYPE="1"
+><LI
><P
->There is also a CVSZilla project, based upon somewhat dated
- Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
- email. Check it out at:
- <A
-HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
-TARGET="_top"
-> http://homepages.kcbbs.gen.nz/~tonyg/</A
->.
+>Using CVS (<A
+HREF="#upgrade-cvs"
+>Example 5-1</A
+>)</P
+></LI
+><LI
+><P
+>Downloading a new tarball (<A
+HREF="#upgrade-tarball"
+>Example 5-2</A
+>)</P
+></LI
+><LI
+><P
+>Applying the relevant patches (<A
+HREF="#upgrade-patches"
+>Example 5-3</A
+>)</P
+></LI
+></OL
+><P
+>Which options are available to you may depend on how large a jump
+ you are making and/or your network configuration.
+ </P
+><P
+>Revisions are normally released to fix security vulnerabilities
+ and are distinguished by an increase in the third number. For example,
+ when 2.16.2 was released, it was a revision to 2.16.1.
+ </P
+><P
+>Point releases are normally released when the Bugzilla team feels
+ that there has been a significant amount of progress made between the
+ last point release and the current time. These are often proceeded by a
+ stabilization period and release candidates, however the use of
+ development versions or release candidates is beyond the scope of this
+ document. Point releases can be distinguished by an increase in the
+ second number, or minor version. For example, 2.16.2 is a newer point
+ release than 2.14.5.
+ </P
+><P
+>The examples in this section are written as if you were updating
+ to version 2.16.2. The procedures are the same regardless if you are
+ updating to a new point release or a new revision. However, the chance
+ of running into trouble increases when upgrading to a new point release,
+ escpecially if you've made local changes.
+ </P
+><P
+>These examples also assume that your Bugzilla installation is at
+ <TT
+CLASS="filename"
+>/var/www/html/bugzilla</TT
+>. If that is not the case,
+ simply substitute the proper paths where appropriate.
</P
-></DIV
><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
+CLASS="example"
><A
-NAME="scm">5.9.3. Perforce SCM</H2
+NAME="upgrade-cvs"
+></A
><P
->You can find the project page for Bugzilla and Teamtrack Perforce
- integration (p4dti) at:
- <A
-HREF="http://www.ravenbrook.com/project/p4dti/"
-TARGET="_top"
-> http://www.ravenbrook.com/project/p4dti</A
->
+><B
+>Example 5-1. Upgrading using CVS</B
+></P
+><P
+>Every release of Bugzilla, whether it is a revision or a point
+ release, is tagged in CVS. Also, every tarball we have distributed
+ since version 2.12 has been primed for using CVS. This does, however,
+ require that you are able to access cvs-mirror.mozilla.org on port
+ 2401.
- .
- <SPAN
-CLASS="QUOTE"
->"p4dti"</SPAN
+ <DIV
+CLASS="tip"
+><P
+></P
+><TABLE
+CLASS="tip"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you can do this, updating using CVS is probably the most
+ painless method, especially if you have a lot of local changes.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
>
-
- 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
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html/bugzilla</B
>
-
- .</P
+bash$ <B
+CLASS="command"
+>cvs login</B
+>
+Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
+CVS password: <B
+CLASS="command"
+>anonymous</B
+>
+bash$ <B
+CLASS="command"
+>cvs -q update -r BUGZILLA-2_16_2 -dP</B
+>
+P checksetup.pl
+P collectstats.pl
+P globals.pl
+P docs/rel_notes.txt
+P template/en/default/list/quips.html.tmpl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
><P
->Integration of Perforce with Bugzilla, once patches are applied, is
- seamless. Perforce replication information will appear below the comments
- of each bug. Be certain you have a matching set of patches for the
- Bugzilla version you are installing. 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
-></DIV
-><DIV
-CLASS="section"
-><HR><H2
-CLASS="section"
-><A
-NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
+> <DIV
+CLASS="caution"
><P
->We need Tinderbox integration information.</P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If a line in the output from <B
+CLASS="command"
+>cvs update</B
+>
+ begins with a <TT
+CLASS="computeroutput"
+>C</TT
+> that represents a
+ file with local changes that CVS was unable to properly merge. You
+ need to resolve these conflicts manually before Bugzilla (or at
+ least the portion using that file) will be usable.
+ </P
+></TD
+></TR
+></TABLE
></DIV
+>
+
+ <DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You also need to run <B
+CLASS="command"
+>./checksetup.pl</B
+>
+ before your Bugzilla upgrade will be complete.
+ </P
+></TD
+></TR
+></TABLE
></DIV
+>
+ </P
></DIV
><DIV
-CLASS="appendix"
-><HR><H1
+CLASS="example"
><A
-NAME="faq">Appendix A. The Bugzilla FAQ</H1
+NAME="upgrade-tarball"
+></A
><P
-> This FAQ includes questions not covered elsewhere in the Guide.
- </P
-><DIV
-CLASS="qandaset"
-><DL
-><DT
->1. <A
-HREF="#faq-general"
->General Questions</A
-></DT
-><DD
-><DL
-><DT
->A.1.1. <A
-HREF="#AEN1649"
-> Where can I find information about Bugzilla?</A
-></DT
-><DT
->A.1.2. <A
-HREF="#AEN1655"
-> What license is Bugzilla distributed under?
- </A
-></DT
-><DT
->A.1.3. <A
-HREF="#AEN1661"
-> How do I get commercial support for Bugzilla?
- </A
-></DT
-><DT
->A.1.4. <A
-HREF="#AEN1668"
-> What major companies or projects are currently using Bugzilla
- for bug-tracking?
- </A
-></DT
-><DT
->A.1.5. <A
-HREF="#AEN1693"
-> Who maintains Bugzilla?
- </A
-></DT
-><DT
->A.1.6. <A
-HREF="#AEN1699"
-> How does Bugzilla stack up against other bug-tracking databases?
- </A
-></DT
-><DT
->A.1.7. <A
-HREF="#AEN1705"
-> Why doesn't Bugzilla offer this or that feature or compatability
- with this other tracking software?
- </A
-></DT
-><DT
->A.1.8. <A
-HREF="#AEN1712"
-> Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- </A
-></DT
-><DT
->A.1.9. <A
-HREF="#AEN1717"
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
- </A
-></DT
-><DT
->A.1.10. <A
-HREF="#AEN1723"
-> Is there an easy way to change the Bugzilla cookie name?
- </A
-></DT
-></DL
-></DD
-><DT
+><B
+>Example 5-2. Upgrading using the tarball</B
+></P
+><P
+>If you are unable or unwilling to use CVS, another option that's
+ always available is to download the latest tarball. This is the most
+ difficult option to use, especially if you have local changes.
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html</B
+>
+bash$ <B
+CLASS="command"
+>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B
+>
+<EM
+>Output omitted</EM
+>
+bash$ <B
+CLASS="command"
+>tar xzvf bugzilla-2.16.2.tar.gz</B
+>
+bugzilla-2.16.2/
+bugzilla-2.16.2/.cvsignore
+bugzilla-2.16.2/1x1.gif
+<EM
+>Output truncated</EM
+>
+bash$ <B
+CLASS="command"
+>cd bugzilla-2.16.2</B
+>
+bash$ <B
+CLASS="command"
+>cp ../bugzilla/localconfig* .</B
+>
+bash$ <B
+CLASS="command"
+>cp -r ../bugzilla/data .</B
+>
+bash$ <B
+CLASS="command"
+>cd ..</B
+>
+bash$ <B
+CLASS="command"
+>mv bugzilla bugzilla.old</B
+>
+bash$ <B
+CLASS="command"
+>mv bugzilla-2.16.2 bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>cd bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>./checksetup.pl</B
+>
+<EM
+>Output omitted</EM
+>
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+> <DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The <B
+CLASS="command"
+>cp</B
+> commands both end with periods which
+ is a very important detail, it tells the shell that the destination
+ directory is the current working directory. Also, the period at the
+ beginning of the <B
+CLASS="command"
+>./checksetup.pl</B
+> is important and
+ can not be omitted.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ <DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You will now have to reapply any changes you have made to your
+ local installation manually.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="example"
+><A
+NAME="upgrade-patches"
+></A
+><P
+><B
+>Example 5-3. Upgrading using patches</B
+></P
+><P
+>The Bugzilla team will normally make a patch file available for
+ revisions to go from the most recent revision to the new one. You could
+ also read the release notes and grab the patches attached to the
+ mentioned bug, but it is safer to use the released patch file as
+ sometimes patches get changed before they get checked in (for minor
+ spelling fixes and the like). It is also theorectically possible to
+ scour the fixed bug list and pick and choose which patches to apply
+ from a point release, but this is not recommended either as what you'll
+ end up with is a hodge podge Bugzilla that isn't really any version.
+ This would also make it more difficult to upgrade in the future.
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html/bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B
+>
+<EM
+>Output omitted</EM
+>
+bash$ <B
+CLASS="command"
+>gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B
+>
+bash$ <B
+CLASS="command"
+>patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B
+>
+patching file checksetup.pl
+patching file collectstats.pl
+patching file globals.pl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+> <DIV
+CLASS="caution"
+><P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you do this, beware that this doesn't change the entires in
+ your <TT
+CLASS="filename"
+>CVS</TT
+> directory so it may make
+ updates using CVS (<A
+HREF="#upgrade-cvs"
+>Example 5-1</A
+>) more difficult in the
+ future.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="integration"
+></A
+>5.9. Integrating Bugzilla with Third-Party Tools</H1
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="bonsai"
+></A
+>5.9.1. Bonsai</H2
+><P
+>Bonsai is a web-based tool for managing
+ <A
+HREF="#cvs"
+>CVS, the Concurrent Versioning System</A
+>
+
+ . Using Bonsai, administrators can control open/closed status of trees,
+ query a fast relational database back-end for change, branch, and comment
+ information, and view changes made since the last time the tree was
+ closed. Bonsai
+ also integrates with
+ <A
+HREF="#tinderbox"
+>Tinderbox, the Mozilla automated build management system</A
+>.
+ </P
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="cvs"
+></A
+>5.9.2. CVS</H2
+><P
+>CVS integration is best accomplished, at this point, using the
+ Bugzilla Email Gateway.</P
+><P
+>Follow the instructions in this Guide for enabling Bugzilla e-mail
+ integration. Ensure that your check-in script sends an email to your
+ Bugzilla e-mail gateway with the subject of
+ <SPAN
+CLASS="QUOTE"
+>"[Bug XXXX]"</SPAN
+>,
+ and you can have CVS check-in comments append to your Bugzilla bug. If
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
+><P
+>There is also a CVSZilla project, based upon somewhat dated
+ Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
+ email. Check it out at:
+ <A
+HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
+TARGET="_top"
+> http://homepages.kcbbs.gen.nz/~tonyg/</A
+>.
+ </P
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="scm"
+></A
+>5.9.3. Perforce SCM</H2
+><P
+>You can find the project page for Bugzilla and Teamtrack Perforce
+ integration (p4dti) at:
+ <A
+HREF="http://www.ravenbrook.com/project/p4dti/"
+TARGET="_top"
+> http://www.ravenbrook.com/project/p4dti</A
+>
+
+ .
+ <SPAN
+CLASS="QUOTE"
+>"p4dti"</SPAN
+>
+
+ 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
+ seamless. Perforce replication information will appear below the comments
+ of each bug. Be certain you have a matching set of patches for the
+ Bugzilla version you are installing. 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
+></DIV
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
+><A
+NAME="tinderbox"
+></A
+>5.9.4. Tinderbox/Tinderbox2</H2
+><P
+>We need Tinderbox integration information.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="appendix"
+><HR><H1
+><A
+NAME="faq"
+></A
+>Appendix A. The Bugzilla FAQ</H1
+><P
+> This FAQ includes questions not covered elsewhere in the Guide.
+ </P
+><DIV
+CLASS="qandaset"
+><DL
+><DT
+>1. <A
+HREF="#faq-general"
+>General Questions</A
+></DT
+><DD
+><DL
+><DT
+>A.1.1. <A
+HREF="#faq-general-information"
+> Where can I find information about Bugzilla?</A
+></DT
+><DT
+>A.1.2. <A
+HREF="#faq-general-license"
+> What license is Bugzilla distributed under?
+ </A
+></DT
+><DT
+>A.1.3. <A
+HREF="#faq-general-support"
+> How do I get commercial support for Bugzilla?
+ </A
+></DT
+><DT
+>A.1.4. <A
+HREF="#faq-general-companies"
+> What major companies or projects are currently using Bugzilla
+ for bug-tracking?
+ </A
+></DT
+><DT
+>A.1.5. <A
+HREF="#faq-general-maintainers"
+> Who maintains Bugzilla?
+ </A
+></DT
+><DT
+>A.1.6. <A
+HREF="#faq-general-compare"
+> How does Bugzilla stack up against other bug-tracking databases?
+ </A
+></DT
+><DT
+>A.1.7. <A
+HREF="#faq-general-bzmissing"
+> Why doesn't Bugzilla offer this or that feature or compatibility
+ with this other tracking software?
+ </A
+></DT
+><DT
+>A.1.8. <A
+HREF="#faq-general-mysql"
+> Why MySQL? I'm interested in seeing Bugzilla run on
+ Oracle/Sybase/Msql/PostgreSQL/MSSQL.
+ </A
+></DT
+><DT
+>A.1.9. <A
+HREF="#faq-general-bonsaitools"
+> Why do the scripts say
+ <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+> instead of
+ <TT
+CLASS="filename"
+>/usr/bin/perl</TT
+> or something else?
+ </A
+></DT
+><DT
+>A.1.10. <A
+HREF="#faq-general-cookie"
+> Is there an easy way to change the Bugzilla cookie name?
+ </A
+></DT
+></DL
+></DD
+><DT
>2. <A
HREF="#faq-phb"
>Managerial Questions</A
@@ -8867,41 +9433,41 @@ HREF="#faq-phb"
><DL
><DT
>A.2.1. <A
-HREF="#AEN1733"
+HREF="#faq-phb-client"
> Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
-HREF="#AEN1738"
+HREF="#faq-phb-integration"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="#AEN1743"
+HREF="#faq-phb-projects"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="#AEN1748"
+HREF="#faq-phb-sorting"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="#AEN1753"
+HREF="#faq-phb-attachments"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="#AEN1758"
+HREF="#faq-phb-priorities"
> 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?
@@ -8909,35 +9475,35 @@ HREF="#AEN1758"
></DT
><DT
>A.2.7. <A
-HREF="#AEN1765"
+HREF="#faq-phb-reporting"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="#AEN1772"
+HREF="#faq-phb-email"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="#AEN1777"
+HREF="#faq-phb-cclist"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="#AEN1782"
+HREF="#faq-phb-emailapp"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="#AEN1789"
+HREF="#faq-phb-data"
> 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
@@ -8946,28 +9512,28 @@ HREF="#AEN1789"
></DT
><DT
>A.2.12. <A
-HREF="#AEN1797"
+HREF="#faq-phb-l10n"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="#AEN1802"
+HREF="#faq-phb-reports"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="#AEN1807"
+HREF="#faq-phb-searching"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="#AEN1812"
+HREF="#faq-phb-midair"
> 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?
@@ -8975,19 +9541,19 @@ HREF="#AEN1812"
></DT
><DT
>A.2.16. <A
-HREF="#AEN1817"
+HREF="#faq-phb-backup"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="#AEN1823"
+HREF="#faq-phb-livebackup"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="#AEN1828"
+HREF="#faq-phb-maintenance"
> 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
@@ -8997,7 +9563,7 @@ HREF="#AEN1828"
></DT
><DT
>A.2.19. <A
-HREF="#AEN1834"
+HREF="#faq-phb-installtime"
> 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
@@ -9007,7 +9573,7 @@ HREF="#AEN1834"
></DT
><DT
>A.2.20. <A
-HREF="#AEN1839"
+HREF="#faq-phb-cost"
> 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
@@ -9023,20 +9589,20 @@ HREF="#faq-security"
><DL
><DT
>A.3.1. <A
-HREF="#AEN1846"
+HREF="#faq-security-mysql"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide)?
</A
></DT
><DT
>A.3.2. <A
-HREF="#AEN1852"
+HREF="#faq-security-knownproblems"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="#AEN1857"
+HREF="#faq-security-mysqluser"
> 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.
@@ -9053,48 +9619,48 @@ HREF="#faq-email"
><DL
><DT
>A.4.1. <A
-HREF="#AEN1864"
+HREF="#faq-email-nomail"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.4.2. <A
-HREF="#AEN1869"
+HREF="#faq-email-testing"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.4.3. <A
-HREF="#AEN1874"
+HREF="#faq-email-whine"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="#AEN1880"
+HREF="#faq-email-procmail"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="#AEN1887"
+HREF="#faq-email-mailif"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="#AEN1892"
+HREF="#faq-email-sendmailnow"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="#AEN1899"
+HREF="#faq-email-nonreceived"
> How come email from Bugzilla changes never reaches me?
</A
></DT
@@ -9109,39 +9675,33 @@ HREF="#faq-db"
><DL
><DT
>A.5.1. <A
-HREF="#AEN1907"
+HREF="#faq-db-oracle"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="#AEN1912"
+HREF="#faq-db-corrupted"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="#AEN1920"
+HREF="#faq-db-manualedit"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="#AEN1925"
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
- </A
-></DT
-><DT
->A.5.5. <A
-HREF="#AEN1930"
+HREF="#faq-db-permissions"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
->A.5.6. <A
-HREF="#AEN1935"
+>A.5.5. <A
+HREF="#faq-db-synchronize"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
@@ -9157,26 +9717,26 @@ HREF="#faq-nt"
><DL
><DT
>A.6.1. <A
-HREF="#AEN1944"
+HREF="#faq-nt-easiest"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="#AEN1949"
+HREF="#faq-nt-bundle"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="#AEN1954"
+HREF="#faq-nt-mappings"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="#AEN1962"
+HREF="#faq-nt-dbi"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
@@ -9192,40 +9752,33 @@ HREF="#faq-use"
><DL
><DT
>A.7.1. <A
-HREF="#AEN1983"
+HREF="#faq-use-changeaddress"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="#AEN1988"
+HREF="#faq-use-query"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="#AEN1993"
+HREF="#faq-use-accept"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.7.4. <A
-HREF="#AEN2003"
+HREF="#faq-use-attachment"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="#AEN2008"
-> Email submissions to Bugzilla that have attachments end up asking me to
- save it as a "cgi" file.
- </A
-></DT
-><DT
->A.7.6. <A
-HREF="#AEN2013"
+HREF="#faq-use-keyword"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
@@ -9240,20 +9793,20 @@ HREF="#faq-hacking"
><DL
><DT
>A.8.1. <A
-HREF="#AEN2020"
+HREF="#faq-hacking-bugzillabugs"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.2. <A
-HREF="#AEN2029"
+HREF="#faq-hacking-priority"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.8.3. <A
-HREF="#AEN2035"
+HREF="#faq-hacking-patches"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
@@ -9261,20 +9814,303 @@ HREF="#AEN2035"
></DD
></DL
><DIV
-CLASS="qandadiv"
-><H3
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-general"
+></A
+>1. General Questions</H3
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-information"
+></A
+><B
+>A.1.1. </B
+>
+ Where can I find information about Bugzilla?</P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ You can stay up-to-date with the latest Bugzilla
+ information at <A
+HREF="http://www.bugzilla.org/"
+TARGET="_top"
+> http://www.bugzilla.org/</A
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-license"
+></A
+><B
+>A.1.2. </B
+>
+ What license is Bugzilla distributed under?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ Bugzilla is covered by the Mozilla Public License.
+ See details at <A
+HREF="http://www.mozilla.org/MPL/"
+TARGET="_top"
+> http://www.mozilla.org/MPL/</A
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-support"
+></A
+><B
+>A.1.3. </B
+>
+ How do I get commercial support for Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ <A
+HREF="http://bugzilla.org/consulting.html"
+TARGET="_top"
+>http://bugzilla.org/consulting.html</A
+>
+ is a list of people and companies who have asked us to list them
+ as consultants for Bugzilla.
+ </P
+><P
+> <A
+HREF="http://www.collab.net/"
+TARGET="_top"
+>www.collab.net</A
+> offers
+ Bugzilla as part of their standard offering to large projects.
+ They do have some minimum fees that are pretty hefty, and generally
+ aren't interested in small projects.
+ </P
+><P
+> There are several experienced
+ Bugzilla hackers on the mailing list/newsgroup who are willing
+ to make themselves available for generous compensation.
+ Try sending a message to the mailing list asking for a volunteer.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-companies"
+></A
+><B
+>A.1.4. </B
+>
+ What major companies or projects are currently using Bugzilla
+ for bug-tracking?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ There are <EM
+>dozens</EM
+> of major companies with public
+ Bugzilla sites to track bugs in their products. A few include:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Netscape/AOL</TD
+></TR
+><TR
+><TD
+>Mozilla.org</TD
+></TR
+><TR
+><TD
+>NASA</TD
+></TR
+><TR
+><TD
+>Red Hat Software</TD
+></TR
+><TR
+><TD
+>SuSe Corp</TD
+></TR
+><TR
+><TD
+>The Horde Project</TD
+></TR
+><TR
+><TD
+>AbiSource</TD
+></TR
+><TR
+><TD
+>Real Time Enterprises, Inc</TD
+></TR
+><TR
+><TD
+>Eggheads.org</TD
+></TR
+><TR
+><TD
+>Strata Software</TD
+></TR
+><TR
+><TD
+>RockLinux</TD
+></TR
+><TR
+><TD
+>Creative Labs (makers of SoundBlaster)</TD
+></TR
+><TR
+><TD
+>The Apache Foundation</TD
+></TR
+><TR
+><TD
+>The Gnome Foundation</TD
+></TR
+><TR
+><TD
+>Ximian</TD
+></TR
+><TR
+><TD
+>Linux-Mandrake</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> Suffice to say, there are more than enough huge projects using Bugzilla
+ that we can safely say it's extremely popular.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-maintainers"
+></A
+><B
+>A.1.5. </B
+>
+ Who maintains Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ A
+ <A
+HREF="http://www.bugzilla.org/who_we_are.html"
+TARGET="_top"
+>core team</A
+>,
+ led by Dave Miller (justdave@netscape.com).
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
><A
-NAME="faq-general">1. General Questions</H3
+NAME="faq-general-compare"
+></A
+><B
+>A.1.6. </B
+>
+ How does Bugzilla stack up against other bug-tracking databases?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ We can't find any head-to-head comparisons of Bugzilla against
+ other defect-tracking software. If you know of one, please
+ get in touch. However, from the author's personal
+ experience with other bug-trackers, Bugzilla offers
+ superior performance on commodity hardware, better price
+ (free!), more developer- friendly features (such as stored
+ queries, email integration, and platform independence),
+ improved scalability, open source code, greater
+ flexibility, and superior ease-of-use.
+ </P
+><P
+> If you happen to be a commercial bug-tracker vendor, please
+ step forward with a list of advantages your product has over
+ Bugzilla. We'd be happy to include it in the "Competitors"
+ section.
+ </P
+></DIV
+></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1649"><B
->A.1.1. </B
+NAME="faq-general-bzmissing"
+></A
+><B
+>A.1.7. </B
>
- Where can I find information about Bugzilla?</P
+ Why doesn't Bugzilla offer this or that feature or compatibility
+ with this other tracking software?
+ </P
></DIV
><DIV
CLASS="answer"
@@ -9282,12 +10118,22 @@ CLASS="answer"
><B
> </B
>
- You can stay up-to-date with the latest Bugzilla
- information at <A
-HREF="http://www.bugzilla.org/"
+ It may be that the support has not been built yet, or that you
+ have not yet found it. Bugzilla is making tremendous strides in
+ usability, customizability, scalability, and user interface. It
+ is widely considered the most complete and popular open-source
+ bug-tracking software in existence.
+ </P
+><P
+> That doesn't mean it can't use improvement!
+ You can help the project along by either hacking a patch yourself
+ that supports the functionality you require, or else submitting a
+ "Request for Enhancement" (RFE) using the bug submission interface
+ at <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
TARGET="_top"
-> http://www.bugzilla.org/</A
->
+>bugzilla.mozilla.org</A
+>.
</P
></DIV
></DIV
@@ -9297,10 +10143,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1655"><B
->A.1.2. </B
+NAME="faq-general-mysql"
+></A
+><B
+>A.1.8. </B
>
- What license is Bugzilla distributed under?
+ Why MySQL? I'm interested in seeing Bugzilla run on
+ Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</P
></DIV
><DIV
@@ -9309,14 +10158,94 @@ CLASS="answer"
><B
> </B
>
- Bugzilla is covered by the Mozilla Public License.
- See details at <A
-HREF="http://www.mozilla.org/MPL/"
+ MySQL was originally chosen because it is free, easy to install,
+ and was available for the hardware Netscape intended to run it on.
+ </P
+><P
+> There is currently work in progress to make Bugzilla work on
+ PostgreSQL and Sybase in the default distribution. You can track
+ the progress of these initiatives in bugs <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
TARGET="_top"
-> http://www.mozilla.org/MPL/</A
+>98304</A
+>
+ and <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
+TARGET="_top"
+>173130</A
+>
+ respectively.
+ </P
+><P
+> Once both of these are done, adding support for additional
+ database servers should be trivial.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-general-bonsaitools"
+></A
+><B
+>A.1.9. </B
>
+ Why do the scripts say
+ <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+> instead of
+ <TT
+CLASS="filename"
+>/usr/bin/perl</TT
+> or something else?
</P
></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ Mozilla.org used <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+>,
+ because originally Terry wanted a place to put a version of Perl
+ and other tools that was strictly under his control.
+ </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This convention was abonded during the 2.17 development cycle so
+ it will no longer be an issue when 2.18 comes out.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
></DIV
><DIV
CLASS="qandaentry"
@@ -9324,10 +10253,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1661"><B
->A.1.3. </B
+NAME="faq-general-cookie"
+></A
+><B
+>A.1.10. </B
>
- How do I get commercial support for Bugzilla?
+ Is there an easy way to change the Bugzilla cookie name?
</P
></DIV
><DIV
@@ -9336,20 +10267,71 @@ CLASS="answer"
><B
> </B
>
- <A
-HREF="http://www.collab.net/"
-TARGET="_top"
->www.collab.net</A
-> offers
- Bugzilla as part of their standard offering to large projects.
- They do have some minimum fees that are pretty hefty, and generally
- aren't interested in small projects.
+ At present, no.
</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-phb"
+></A
+>2. Managerial Questions</H3
><P
-> There are several experienced
- Bugzilla hackers on the mailing list/newsgroup who are willing
- to make themselves available for generous compensation.
- Try sending a message to the mailing list asking for a volunteer.
+> <DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Questions likely to be asked by managers. :-)
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-phb-client"
+></A
+><B
+>A.2.1. </B
+>
+ Is Bugzilla web-based, or do you have to have specific software or
+ a specific operating system on your machine?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ It is web and e-mail based. You can edit bugs by sending specially
+ formatted email to a properly configured Bugzilla, or control via the web.
</P
></DIV
></DIV
@@ -9359,11 +10341,38 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1668"><B
->A.1.4. </B
+NAME="faq-phb-integration"
+></A
+><B
+>A.2.2. </B
>
- What major companies or projects are currently using Bugzilla
- for bug-tracking?
+ Can Bugzilla integrate with
+ Perforce (SCM software)?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ Yes! You can find more information elsewhere in "The Bugzilla
+ Guide" in the "Integration with Third-Party Products" section.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-phb-projects"
+></A
+><B
+>A.2.3. </B
+>
+ Does Bugzilla allow the user to track multiple projects?
</P
></DIV
><DIV
@@ -9372,93 +10381,39 @@ CLASS="answer"
><B
> </B
>
- There are <EM
->dozens</EM
-> of major comapanies with public
- Bugzilla sites to track bugs in their products. A few include:
- <P
+ Absolutely! You can track any number of Products that can each be
+ composed of any number of Components.
+ </P
+><DIV
+CLASS="note"
+><P
></P
><TABLE
+CLASS="note"
+WIDTH="100%"
BORDER="0"
-><TBODY
-><TR
-><TD
->Netscape/AOL</TD
-></TR
-><TR
-><TD
->Mozilla.org</TD
-></TR
-><TR
-><TD
->NASA</TD
-></TR
-><TR
-><TD
->AtHome Corporation</TD
-></TR
-><TR
-><TD
->Red Hat Software</TD
-></TR
-><TR
-><TD
->SuSe Corp</TD
-></TR
-><TR
-><TD
->The Horde Project</TD
-></TR
-><TR
-><TD
->AbiSource</TD
-></TR
-><TR
-><TD
->Real Time Enterprises, Inc</TD
-></TR
-><TR
-><TD
->Eggheads.org</TD
-></TR
-><TR
-><TD
->Strata Software</TD
-></TR
-><TR
-><TD
->RockLinux</TD
-></TR
-><TR
-><TD
->Creative Labs (makers of SoundBlaster)</TD
-></TR
><TR
><TD
->The Apache Foundation</TD
-></TR
-><TR
-><TD
->The Gnome Foundation</TD
-></TR
-><TR
-><TD
->Ximian</TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
->Linux-Mandrake</TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>There are only 55 groups available in version 2.16 of
+ Bugzilla. If you are using product groups, this will also limit
+ the number of products you can have. This limit does not exist in
+ the current 2.17 development releases and will not exist in 2.18.
+ </P
+></TD
></TR
-></TBODY
></TABLE
-><P
-></P
->
- </P
-><P
-> Suffice to say, there are more than enough huge projects using Bugzilla
- that we can safely say it's extremely popular.
- </P
+></DIV
></DIV
></DIV
><DIV
@@ -9467,10 +10422,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1693"><B
->A.1.5. </B
+NAME="faq-phb-sorting"
+></A
+><B
+>A.2.4. </B
>
- Who maintains Bugzilla?
+ 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?
</P
></DIV
><DIV
@@ -9479,13 +10437,7 @@ CLASS="answer"
><B
> </B
>
- A
- <A
-HREF="http://www.bugzilla.org/who_we_are.html"
-TARGET="_top"
->core team</A
->,
- led by Dave Miller (justdave@syndicomm.com).
+ Yes.
</P
></DIV
></DIV
@@ -9495,10 +10447,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1699"><B
->A.1.6. </B
+NAME="faq-phb-attachments"
+></A
+><B
+>A.2.5. </B
>
- How does Bugzilla stack up against other bug-tracking databases?
+ Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
+ are there any that are NOT allowed?
</P
></DIV
><DIV
@@ -9507,21 +10462,11 @@ CLASS="answer"
><B
> </B
>
- We can't find any head-to-head comparisons of Bugzilla against
- other defect-tracking software. If you know of one, please
- get in touch. However, from the author's personal
- experience with other bug-trackers, Bugzilla offers
- superior performance on commodity hardware, better price
- (free!), more developer- friendly features (such as stored
- queries, email integration, and platform independence),
- improved scalability, open source code, greater
- flexibility, and superior ease-of-use.
- </P
-><P
-> If you happen to be a commercial bug-tracker vendor, please
- step forward with a list of advantages your product has over
- Bugzilla. We'd be happy to include it in the "Competitors"
- section.
+ Yes - any sort of attachment is allowed, although administrators can
+ configure a maximum size.
+ Bugzilla gives the user the option of either using the MIME-type
+ supplied by the browser, choosing from a pre-defined list or
+ manually typing any arbitrary MIME-type.
</P
></DIV
></DIV
@@ -9531,11 +10476,14 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1705"><B
->A.1.7. </B
+NAME="faq-phb-priorities"
+></A
+><B
+>A.2.6. </B
>
- Why doesn't Bugzilla offer this or that feature or compatability
- with this other tracking software?
+ 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?
</P
></DIV
><DIV
@@ -9544,21 +10492,17 @@ CLASS="answer"
><B
> </B
>
- It may be that the support has not been built yet, or that you
- have not yet found it. Bugzilla is making tremendous strides in
- usability, customizability, scalability, and user interface. It
- is widely considered the most complete and popular open-source
- bug-tracking software in existence.
+ Yes. However, modifying some fields, notably those related to bug
+ progression states, also require adjusting the program logic to
+ compensate for the change.
</P
><P
-> That doesn't mean it can't use improvement!
- You can help the project along by either hacking a patch yourself
- that supports the functionality you require, or else submitting a
- "Request for Enhancement" (RFE) using the bug submission interface
- at <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
+> There is no GUI for adding fields to Bugzilla at this
+ time. You can follow development of this feature at
+ <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
TARGET="_top"
->bugzilla.mozilla.org</A
+>http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
>.
</P
></DIV
@@ -9569,11 +10513,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1712"><B
->A.1.8. </B
+NAME="faq-phb-reporting"
+></A
+><B
+>A.2.7. </B
>
- Why MySQL? I'm interested in seeing Bugzilla run on
- Oracle/Sybase/Msql/PostgreSQL/MSSQL.
+ Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+ know, the type of stuff that management likes to see. :)
</P
></DIV
><DIV
@@ -9582,9 +10528,54 @@ CLASS="answer"
><B
> </B
>
- There is DB-independence work afoot. PostgreSQL support is planned
- for 2.18, and full DB-independence can't be far further on.
+ Yes. Look at <A
+HREF="http://bugzilla.mozilla.org/reports.cgi"
+TARGET="_top"
+>http://bugzilla.mozilla.org/reports.cgi</A
+>
+ for samples of what Bugzilla can do in reporting and graphing.
</P
+><P
+> If you can not get the reports you want from the included reporting
+ scripts, it is possible to hook up a professional reporting package
+ such as Crystal Reports using ODBC. If you choose to do this,
+ beware that giving direct access to the database does contain some
+ security implications. Even if you give read-only access to the
+ bugs database it will bypass the secure bugs features of Bugzilla.
+ </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Bugzilla's current development versions can do a lot more in the
+ way of reporting. To see examples, check out
+ <A
+HREF="http://bugzilla.mozilla.org/report.cgi"
+TARGET="_top"
+>http://bugzilla.mozilla.org/report.cgi</A
+>.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -9593,11 +10584,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1717"><B
->A.1.9. </B
+NAME="faq-phb-email"
+></A
+><B
+>A.2.8. </B
>
- Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
+ Is there email notification and if so, what do you see when you get an
+ email?
</P
></DIV
><DIV
@@ -9606,16 +10599,10 @@ CLASS="answer"
><B
> </B
>
- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally
- Terry wanted a place to put a version of Perl and other tools
- that was strictly under his control.
- </P
-><P
-> We always recommend that, if possible, you keep the path
- as /usr/bonsaitools/bin/perl, and simply add symlink.
- This will make upgrading
- your Bugzilla much easier in the future.
- </P
+ Email notification is user-configurable. By default, the bug id and
+ Summary of the bug report accompany each email notification, along with
+ a list of the changes made.
+ </P
></DIV
></DIV
><DIV
@@ -9624,10 +10611,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1723"><B
->A.1.10. </B
+NAME="faq-phb-cclist"
+></A
+><B
+>A.2.9. </B
>
- Is there an easy way to change the Bugzilla cookie name?
+ Can email notification be set up to send to multiple
+ people, some on the To List, CC List, BCC List etc?
</P
></DIV
><DIV
@@ -9636,18 +10626,34 @@ CLASS="answer"
><B
> </B
>
- At present, no.
+ Yes.
</P
></DIV
></DIV
-></DIV
><DIV
-CLASS="qandadiv"
-><H3
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
><A
-NAME="faq-phb">2. Managerial Questions</H3
+NAME="faq-phb-emailapp"
+></A
+><B
+>A.2.10. </B
+>
+ Do users have to have any particular
+ type of email application?
+ </P
+></DIV
+><DIV
+CLASS="answer"
><P
-> <DIV
+><B
+> </B
+>
+ Bugzilla email is sent in plain text, the most compatible mail format
+ on the planet.
+ <DIV
CLASS="note"
><P
></P
@@ -9667,26 +10673,37 @@ ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
-><P
-> Questions likely to be asked by managers. :-)
- </P
+><P
+> If you decide to use the bugzilla_email integration features
+ to allow Bugzilla to record responses to mail with the associated bug,
+ you may need to caution your users to set their mailer to "respond
+ to messages in the format in which they were sent". For security reasons
+ Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
+ email into Bugzilla the resulting comment looks downright awful.
+ </P
></TD
></TR
></TABLE
></DIV
>
- </P
+ </P
+></DIV
+></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1733"><B
->A.2.1. </B
+NAME="faq-phb-data"
+></A
+><B
+>A.2.11. </B
>
- Is Bugzilla web-based, or do you have to have specific software or
- a specific operating system on your machine?
+ 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
+ and export that data to MS Excel, could I do that?
</P
></DIV
><DIV
@@ -9695,9 +10712,39 @@ CLASS="answer"
><B
> </B
>
- It is web and e-mail based. You can edit bugs by sending specially
- formatted email to a properly configured Bugzilla, or control via the web.
- </P
+ Bugzilla can only output buglists as HTML in version 2.16. There
+ are other formats available (CSV and RDF) in the newer development
+ versions.
+ </P
+><P
+> Bugzilla can export bugs using <TT
+CLASS="filename"
+>xml.cgi</TT
+> with
+ either a bug number or list of bug numbers.
+ </P
+><P
+> Currently the only script included with Bugzilla that can import
+ data is <TT
+CLASS="filename"
+>importxml.pl</TT
+> which is intended to be
+ used for importing the data generated by <TT
+CLASS="filename"
+>xml.cgi</TT
+>
+ in association with bug moving. Any other use is left as an
+ exercise for the user.
+ </P
+><P
+> There are also scripts included in the <TT
+CLASS="filename"
+>contrib/</TT
+>
+ directory for using e-mail to import information into Bugzilla,
+ but these scripts are not currently supported and included for
+ educational purposes.
+ </P
></DIV
></DIV
><DIV
@@ -9706,11 +10753,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1738"><B
->A.2.2. </B
+NAME="faq-phb-l10n"
+></A
+><B
+>A.2.12. </B
>
- Can Bugzilla integrate with
- Perforce (SCM software)?
+ Has anyone converted Bugzilla to another language to be used in other
+ countries? Is it localizable?
</P
></DIV
><DIV
@@ -9719,8 +10768,20 @@ CLASS="answer"
><B
> </B
>
- Yes! You can find more information elsewhere in "The Bugzilla
- Guide" in the "Integration with Third-Party Products" section.
+ Yes. For more information including available translated templates,
+ see <A
+HREF="http://www.bugzilla.org/download.html#localizations"
+TARGET="_top"
+>http://www.bugzilla.org/download.html#localizations</A
+>.
+ The admin interfaces are still not included in these translated
+ templates and is therefore still English only. Also, there may be
+ issues with the charset not being declared. See <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug 126226</A
+>
+ for more information.
</P
></DIV
></DIV
@@ -9730,10 +10791,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1743"><B
->A.2.3. </B
+NAME="faq-phb-reports"
+></A
+><B
+>A.2.13. </B
>
- Does Bugzilla allow the user to track multiple projects?
+ Can a user create and save reports? Can they do this in Word format?
+ Excel format?
</P
></DIV
><DIV
@@ -9742,10 +10806,7 @@ CLASS="answer"
><B
> </B
>
- Absolutely! You can track any number of Products (although you
- are limited to about 55 or so if
- you are using Product-Based Groups), that can each be composed of any
- number of Components.
+ Yes. No. Not in 2.16.
</P
></DIV
></DIV
@@ -9755,11 +10816,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1748"><B
->A.2.4. </B
+NAME="faq-phb-searching"
+></A
+><B
+>A.2.14. </B
>
- 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?
+ Does Bugzilla have the ability to search by word, phrase, compound
+ search?
</P
></DIV
><DIV
@@ -9768,7 +10831,8 @@ CLASS="answer"
><B
> </B
>
- Yes.
+ You have no idea. Bugzilla's query interface, particularly with the
+ advanced Boolean operators, is incredibly versatile.
</P
></DIV
></DIV
@@ -9778,11 +10842,14 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1753"><B
->A.2.5. </B
+NAME="faq-phb-midair"
+></A
+><B
+>A.2.15. </B
>
- Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
- are there any that are NOT allowed?
+ 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?
</P
></DIV
><DIV
@@ -9791,11 +10858,8 @@ CLASS="answer"
><B
> </B
>
- Yes - any sort of attachment is allowed, although administrators can
- configure a maximum size.
- There are many specific MIME-types that are pre-defined by Bugzilla,
- but you may specify any arbitrary MIME-type you need when you
- upload the file.
+ Bugzilla does not lock records. It provides mid-air collision detection,
+ and offers the offending user a choice of options to deal with the conflict.
</P
></DIV
></DIV
@@ -9805,12 +10869,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1758"><B
->A.2.6. </B
+NAME="faq-phb-backup"
+></A
+><B
+>A.2.16. </B
>
- 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?
+ Are there any backup features provided?
</P
></DIV
><DIV
@@ -9819,17 +10883,12 @@ CLASS="answer"
><B
> </B
>
- Yes. However, modifying some fields, notably those related to bug
- progression states, also require adjusting the program logic to
- compensate for the change.
- </P
-><P
-> There is no GUI for adding fields to Bugzilla at this
- time. You can follow development of this feature at
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
+ MySQL, the database back-end for Bugzilla, allows hot-backup of data.
+ You can find strategies for dealing with backup considerations
+ at <A
+HREF="http://www.mysql.com/doc/B/a/Backup.html"
TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
+> http://www.mysql.com/doc/B/a/Backup.html</A
>
</P
></DIV
@@ -9840,11 +10899,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1765"><B
->A.2.7. </B
+NAME="faq-phb-livebackup"
+></A
+><B
+>A.2.17. </B
>
- Does Bugzilla provide any reporting features, metrics, graphs, etc? You
- know, the type of stuff that management likes to see. :)
+ Can users be on the system while a backup is in progress?
</P
></DIV
><DIV
@@ -9853,20 +10913,9 @@ CLASS="answer"
><B
> </B
>
- Yes. Look at <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
-TARGET="_top"
-> http://bugzilla.mozilla.org/reports.cgi</A
-> for basic reporting
- and graphing facilities.
- </P
-><P
-> For more advanced reporting, I recommend hooking up a professional
- reporting package, such as Crystal Reports, and use ODBC to access
- the MySQL database. You can do a lot through the Query page of
- Bugzilla as well, but right now Advanced Reporting is much
- better accomplished through third-party utilities that can
- interface with the database directly.
+ Yes. However, commits to the database must wait
+ until the tables are unlocked. Bugzilla databases are typically
+ very small, and backups routinely take less than a minute.
</P
></DIV
></DIV
@@ -9876,11 +10925,16 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1772"><B
->A.2.8. </B
+NAME="faq-phb-maintenance"
+></A
+><B
+>A.2.18. </B
>
- Is there email notification and if so, what do you see when you get an
- email?
+ 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
+ individuals would we need to hire and how much would that cost vs buying an
+ "Out-of-the-Box" solution.
</P
></DIV
><DIV
@@ -9889,9 +10943,14 @@ CLASS="answer"
><B
> </B
>
- Email notification is user-configurable. By default, the bug id and
- Summary of the bug report accompany each email notification, along with
- a list of the changes made.
+ If Bugzilla is set up correctly from the start, continuing maintenance
+ needs are minimal and can be done easily using the web interface.
+ </P
+><P
+> Commercial Bug-tracking software typically costs somewhere upwards
+ of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
+ is available from skilled members of the newsgroup. Simple questions
+ are answered there and then.
</P
></DIV
></DIV
@@ -9901,11 +10960,16 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1777"><B
->A.2.9. </B
+NAME="faq-phb-installtime"
+></A
+><B
+>A.2.19. </B
>
- Can email notification be set up to send to multiple
- people, some on the To List, CC List, BCC List etc?
+ 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
+ a multi-week install process, plus a full time job for 1 person, 2 people,
+ etc?
</P
></DIV
><DIV
@@ -9914,7 +10978,12 @@ CLASS="answer"
><B
> </B
>
- Yes.
+ It all depends on your level of commitment. Someone with much Bugzilla
+ experience can get you up and running in less than a day, and
+ your Bugzilla install can run untended for years. If your
+ Bugzilla strategy is critical to your business workflow, hire somebody
+ with reasonable UNIX or Perl skills to handle your process management and
+ bug-tracking maintenance & customization.
</P
></DIV
></DIV
@@ -9924,11 +10993,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1782"><B
->A.2.10. </B
+NAME="faq-phb-cost"
+></A
+><B
+>A.2.20. </B
>
- Do users have to have any particular
- type of email application?
+ Is there any licensing fee or other fees for using Bugzilla? Any
+ out-of-pocket cost other than the bodies needed as identified above?
</P
></DIV
><DIV
@@ -9937,57 +11008,32 @@ CLASS="answer"
><B
> </B
>
- Bugzilla email is sent in plain text, the most compatible mail format
- on the planet.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you decide to use the bugzilla_email integration features
- to allow Bugzilla to record responses to mail with the associated bug,
- you may need to caution your users to set their mailer to "respond
- to messages in the format in which they were sent". For security reasons
- Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
- email into Bugzilla the resulting comment looks downright awful.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
+ No. MySQL asks, if you find their product valuable, that you purchase
+ a support contract from them that suits your needs.
</P
></DIV
></DIV
+></DIV
+><DIV
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-security"
+></A
+>3. Bugzilla Security</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1789"><B
->A.2.11. </B
+NAME="faq-security-mysql"
+></A
+><B
+>A.3.1. </B
>
- 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
- and export that data to MS Excel, could I do that?
+ How do I completely disable MySQL security if it's giving me problems
+ (I've followed the instructions in the installation section of this guide)?
</P
></DIV
><DIV
@@ -9996,27 +11042,11 @@ CLASS="answer"
><B
> </B
>
- Mozilla allows data export through a custom DTD in XML format.
- It does not, however, export to specific formats other than the
- XML Mozilla DTD. Importing the data into Excel or any other application
- is left as an exercise for the reader.
- </P
-><P
-> If you create import filters to other applications from Mozilla's XML,
- please submit your modifications for inclusion in future Bugzilla
- distributions.
- </P
-><P
-> As for data import, any application can send data to Bugzilla through
- the HTTP protocol, or through Mozilla's XML API. However, it seems
- kind of silly to put another front-end in front of Bugzilla;
- it makes more sense to create a simplified bug submission form in
- HTML. You can find an excellent example at
- <A
-HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
-TARGET="_top"
-> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
->
+ Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
+>this
+ makes MySQL as secure as taping a $100 to the floor of a football stadium
+ bathroom for safekeeping.</EM
+>
</P
></DIV
></DIV
@@ -10026,11 +11056,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1797"><B
->A.2.12. </B
+NAME="faq-security-knownproblems"
+></A
+><B
+>A.3.2. </B
>
- Has anyone converted Bugzilla to another language to be used in other
- countries? Is it localizable?
+ Are there any security problems with Bugzilla?
</P
></DIV
><DIV
@@ -10039,10 +11070,11 @@ CLASS="answer"
><B
> </B
>
- To a certain extent, yes. 2.16's templates mean that you can localise
- the user-facing UI (and several projects are doing exactly that.) However,
- error messages and the admin interface are currently not localisable.
- This should be achieved by 2.18.
+ The Bugzilla code has undergone a reasonably complete security audit,
+ and user-facing CGIs run under Perl's taint mode. However,
+ it is recommended that you closely examine permissions on your Bugzilla
+ installation, and follow the recommended security guidelines found
+ in The Bugzilla Guide.
</P
></DIV
></DIV
@@ -10052,11 +11084,14 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1802"><B
->A.2.13. </B
+NAME="faq-security-mysqluser"
+></A
+><B
+>A.3.3. </B
>
- Can a user create and save reports? Can they do this in Word format?
- Excel format?
+ 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.
</P
></DIV
><DIV
@@ -10065,21 +11100,33 @@ CLASS="answer"
><B
> </B
>
- Yes. No. No.
+ This is a common problem, related to running out of file descriptors.
+ Simply add "ulimit -n unlimited" to the script which starts
+ mysqld.
</P
></DIV
></DIV
+></DIV
+><DIV
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-email"
+></A
+>4. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1807"><B
->A.2.14. </B
+NAME="faq-email-nomail"
+></A
+><B
+>A.4.1. </B
>
- Does Bugzilla have the ability to search by word, phrase, compound
- search?
+ I have a user who doesn't want to receive any more email from Bugzilla.
+ How do I stop it entirely for this user?
</P
></DIV
><DIV
@@ -10088,8 +11135,12 @@ CLASS="answer"
><B
> </B
>
- You have no idea. Bugzilla's query interface, particularly with the
- advanced Boolean operators, is incredibly versatile.
+ The user should be able to set
+ this in user email preferences (uncheck all boxes) or you can add
+ their email address to the <TT
+CLASS="filename"
+>data/nomail</TT
+> file.
</P
></DIV
></DIV
@@ -10099,12 +11150,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1812"><B
->A.2.15. </B
+NAME="faq-email-testing"
+></A
+><B
+>A.4.2. </B
>
- 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?
+ I'm evaluating/testing Bugzilla, and don't want it to send email to
+ anyone but me. How do I do it?
</P
></DIV
><DIV
@@ -10113,8 +11165,8 @@ CLASS="answer"
><B
> </B
>
- Bugzilla does not lock records. It provides mid-air collision detection,
- and offers the offending user a choice of options to deal with the conflict.
+ Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
+ replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
</P
></DIV
></DIV
@@ -10124,10 +11176,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1817"><B
->A.2.16. </B
+NAME="faq-email-whine"
+></A
+><B
+>A.4.3. </B
>
- Are there any backup features provided?
+ I want whineatnews.pl to whine at something more, or other than, only new
+ bugs. How do I do it?
</P
></DIV
><DIV
@@ -10136,13 +11191,14 @@ CLASS="answer"
><B
> </B
>
- MySQL, the database back-end for Bugzilla, allows hot-backup of data.
- You can find strategies for dealing with backup considerations
- at <A
-HREF="http://www.mysql.com/doc/B/a/Backup.html"
+ Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+ You can find it at <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
TARGET="_top"
-> http://www.mysql.com/doc/B/a/Backup.html</A
->
+>http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
+>. This
+ patch is against an older version of Bugzilla, so you must apply
+ the diffs manually.
</P
></DIV
></DIV
@@ -10152,10 +11208,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1823"><B
->A.2.17. </B
+NAME="faq-email-procmail"
+></A
+><B
+>A.4.4. </B
>
- Can users be on the system while a backup is in progress?
+ I don't like/want to use Procmail to hand mail off to bug_email.pl.
+ What alternatives do I have?
</P
></DIV
><DIV
@@ -10164,9 +11223,21 @@ CLASS="answer"
><B
> </B
>
- Yes. However, commits to the database must wait
- until the tables are unlocked. Bugzilla databases are typically
- very small, and backups routinely take less than a minute.
+ You can call bug_email.pl directly from your aliases file, with
+ an entry like this:
+ <A
+NAME="AEN1973"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
+ </P
+></BLOCKQUOTE
+>
+ However, this is fairly nasty and subject to problems; you also
+ need to set up your smrsh (sendmail restricted shell) to allow
+ it. In a pinch, though, it can work.
</P
></DIV
></DIV
@@ -10176,14 +11247,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1828"><B
->A.2.18. </B
+NAME="faq-email-mailif"
+></A
+><B
+>A.4.5. </B
>
- 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
- individuals would we need to hire and how much would that cost vs buying an
- "Out-of-the-Box" solution.
+ How do I set up the email interface to submit/change bugs via email?
</P
></DIV
><DIV
@@ -10192,14 +11261,8 @@ CLASS="answer"
><B
> </B
>
- If Bugzilla is set up correctly from the start, continuing maintenance
- needs are minimal and can be done easily using the web interface.
- </P
-><P
-> Commercial Bug-tracking software typically costs somewhere upwards
- of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
- is available from skilled members of the newsgroup. Simple questions
- are answered there and then.
+ You can find an updated README.mailif file in the contrib/ directory
+ of your Bugzilla distribution that walks you through the setup.
</P
></DIV
></DIV
@@ -10209,14 +11272,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1834"><B
->A.2.19. </B
+NAME="faq-email-sendmailnow"
+></A
+><B
+>A.4.6. </B
>
- 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
- a multi-week install process, plus a full time job for 1 person, 2 people,
- etc?
+ Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
+ What gives?
</P
></DIV
><DIV
@@ -10225,12 +11287,17 @@ CLASS="answer"
><B
> </B
>
- It all depends on your level of commitment. Someone with much Bugzilla
- experience can get you up and running in less than a day, and
- your Bugzilla install can run untended for years. If your
- Bugzilla strategy is critical to your business workflow, hire somebody
- with reasonable UNIX or Perl skills to handle your process management and
- bug-tracking maintenance & customization.
+ If you are using an alternate Mail Transport Agent (MTA other than
+ sendmail), make sure the options given in the "processmail" and other
+ scripts for all
+ instances of "sendmail" are correct for your MTA.
+ </P
+><P
+> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
+ If you are using Postfix, you will also need to enable <SPAN
+CLASS="QUOTE"
+>"sendmailnow"</SPAN
+>.
</P
></DIV
></DIV
@@ -10240,11 +11307,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1839"><B
->A.2.20. </B
+NAME="faq-email-nonreceived"
+></A
+><B
+>A.4.7. </B
>
- Is there any licensing fee or other fees for using Bugzilla? Any
- out-of-pocket cost other than the bodies needed as identified above?
+ How come email from Bugzilla changes never reaches me?
</P
></DIV
><DIV
@@ -10253,8 +11321,15 @@ CLASS="answer"
><B
> </B
>
- No. MySQL asks, if you find their product valuable, that you purchase
- a support contract from them that suits your needs.
+ Double-check that you have not turned off email in your user preferences.
+ Confirm that Bugzilla is able to send email by visiting the "Log In"
+ link of your Bugzilla installation and clicking the "Email me a password"
+ button after entering your email address.
+ </P
+><P
+> If you never receive mail from Bugzilla, chances you do not have
+ sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
+ to, "/usr/lib/sendmail".
</P
></DIV
></DIV
@@ -10263,18 +11338,21 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-security">3. Bugzilla Security</H3
+NAME="faq-db"
+></A
+>5. Bugzilla Database</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1846"><B
->A.3.1. </B
+NAME="faq-db-oracle"
+></A
+><B
+>A.5.1. </B
>
- How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the installation section of this guide)?
+ I've heard Bugzilla can be used with Oracle?
</P
></DIV
><DIV
@@ -10283,11 +11361,11 @@ CLASS="answer"
><B
> </B
>
- Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
->this
- makes MySQL as secure as taping a $100 to the floor of a football stadium
- bathroom for safekeeping.</EM
->
+ Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
+ Red Hat's newer version (based on 2.17.1 and soon to be merged into
+ the main distribution) runs on PostgreSQL. At this time we know of
+ no recent ports of Bugzilla to Oracle but do intend to support it
+ in the future (possibly the 2.20 time-frame).
</P
></DIV
></DIV
@@ -10297,10 +11375,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1852"><B
->A.3.2. </B
+NAME="faq-db-corrupted"
+></A
+><B
+>A.5.2. </B
>
- Are there any security problems with Bugzilla?
+ I think my database might be corrupted, or contain invalid entries. What
+ do I do?
</P
></DIV
><DIV
@@ -10309,11 +11390,29 @@ CLASS="answer"
><B
> </B
>
- The Bugzilla code has undergone a reasonably complete security audit,
- and user-facing CGIs run under Perl's taint mode. However,
- it is recommended that you closely examine permissions on your Bugzilla
- installation, and follow the recommended security guidelines found
- in The Bugzilla Guide.
+ Run the <SPAN
+CLASS="QUOTE"
+>"sanity check"</SPAN
+> utility
+ (<TT
+CLASS="filename"
+>./sanitycheck.cgi</TT
+> in the
+ Bugzilla_home directory) from your web browser to see! If
+ it finishes without errors, you're
+ <EM
+>probably</EM
+> OK. If it doesn't come back
+ OK (i.e. any red letters), there are certain things
+ Bugzilla can recover from and certain things it can't. If
+ it can't auto-recover, I hope you're familiar with
+ mysqladmin commands or have installed another way to
+ manage your database. Sanity Check, although it is a good
+ basic check on your database integrity, by no means is a
+ substitute for competent database administration and
+ avoiding deletion of data. It is not exhaustive, and was
+ created to do a basic check for the most common problems
+ in Bugzilla databases.
</P
></DIV
></DIV
@@ -10323,12 +11422,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1857"><B
->A.3.3. </B
+NAME="faq-db-manualedit"
+></A
+><B
+>A.5.3. </B
>
- 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.
+ I want to manually edit some entries in my database. How?
</P
></DIV
><DIV
@@ -10337,29 +11436,40 @@ CLASS="answer"
><B
> </B
>
- This is a common problem, related to running out of file descriptors.
- Simply add "ulimit -n unlimited" to the script which starts
- mysqld.
+ There is no facility in Bugzilla itself to do this. It's also generally
+ not a smart thing to do if you don't know exactly what you're doing.
+ However, if you understand SQL you can use the <B
+CLASS="command"
+>mysql</B
+>
+ command line utility to manually insert, delete and modify table
+ information. There are also more intuitive GUI clients available.
+ Personal favorites of the Bugzilla team are <A
+HREF="http://www.phpmyadmin.net/"
+TARGET="_top"
+>phpMyAdmin</A
+> and <A
+HREF="http://www.mysql.com/downloads/gui-mycc.html"
+TARGET="_top"
+>MySQL Control
+ Center</A
+>.
</P
></DIV
></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-email">4. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1864"><B
->A.4.1. </B
+NAME="faq-db-permissions"
+></A
+><B
+>A.5.4. </B
>
- I have a user who doesn't want to receive any more email from Bugzilla.
- How do I stop it entirely for this user?
+ I think I've set up MySQL permissions correctly, but Bugzilla still can't
+ connect.
</P
></DIV
><DIV
@@ -10368,33 +11478,44 @@ CLASS="answer"
><B
> </B
>
- The user should be able to set
- this in user email preferences (uncheck all boxes.)
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
+ Try running MySQL from its binary: "mysqld --skip-grant-tables". This
+ will allow you to completely rule out grant tables as the cause of your
+ frustration. If this Bugzilla is able to connect at this point then
+ you need to check that you have granted proper permission to the user
+ password combo defined in <TT
+CLASS="filename"
+>localconfig</TT
+>.
+ </P
><DIV
-CLASS="question"
+CLASS="warning"
><P
-><A
-NAME="AEN1869"><B
->A.4.2. </B
->
- I'm evaluating/testing Bugzilla, and don't want it to send email to
- anyone but me. How do I do it?
- </P
-></DIV
-><DIV
-CLASS="answer"
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
-><B
-> </B
->
- Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
- replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
- </P
+> Running MySQL with this command line option is very insecure and
+ should only be done when not connected to the external network
+ as a troubleshooting step.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -10403,11 +11524,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1874"><B
->A.4.3. </B
+NAME="faq-db-synchronize"
+></A
+><B
+>A.5.5. </B
>
- I want whineatnews.pl to whine at something more, or other than, only new
- bugs. How do I do it?
+ How do I synchronize bug information among multiple different Bugzilla
+ databases?
</P
></DIV
><DIV
@@ -10416,28 +11539,43 @@ CLASS="answer"
><B
> </B
>
- Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
- You can find it at<A
-HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
-TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
->. This
- patch is against an older version of Bugzilla, so you must apply
- the diffs manually.
+ Well, you can synchronize or you can move bugs. Synchronization will
+ only work one way -- you can create a read-only copy of the database
+ at one site, and have it regularly updated at intervals from the main
+ database.
+ </P
+><P
+> MySQL has some synchronization features builtin to the latest releases.
+ It would be great if someone looked into the possibilities there
+ and provided a report to the newsgroup on how to effectively
+ synchronize two Bugzilla installations.
+ </P
+><P
+> If you simply need to transfer bugs from one Bugzilla to another,
+ checkout the "move.pl" script in the Bugzilla distribution.
</P
></DIV
></DIV
+></DIV
+><DIV
+CLASS="qandadiv"
+><H3
+><A
+NAME="faq-nt"
+></A
+>6. Bugzilla and Win32</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1880"><B
->A.4.4. </B
+NAME="faq-nt-easiest"
+></A
+><B
+>A.6.1. </B
>
- I don't like/want to use Procmail to hand mail off to bug_email.pl.
- What alternatives do I have?
+ What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</P
></DIV
><DIV
@@ -10446,19 +11584,8 @@ CLASS="answer"
><B
> </B
>
- You can call bug_email.pl directly from your aliases file, with
- an entry like this:
- <A
-NAME="AEN1884"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
- </P
-></BLOCKQUOTE
->
- However, this is fairly nasty and subject to problems; you also
- need to set up your smrsh (sendmail restricted shell) to allow
- it. In a pinch, though, it can work.
+ Remove Windows. Install Linux. Install Bugzilla.
+ The boss will never know the difference.
</P
></DIV
></DIV
@@ -10468,10 +11595,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1887"><B
->A.4.5. </B
+NAME="faq-nt-bundle"
+></A
+><B
+>A.6.2. </B
>
- How do I set up the email interface to submit/change bugs via email?
+ Is there a "Bundle::Bugzilla" equivalent for Win32?
</P
></DIV
><DIV
@@ -10480,8 +11609,9 @@ CLASS="answer"
><B
> </B
>
- You can find an updated README.mailif file in the contrib/ directory
- of your Bugzilla distribution that walks you through the setup.
+ Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
+ installation on UNIX systems. If someone can volunteer to
+ create a suitable PPM bundle for Win32, it would be appreciated.
</P
></DIV
></DIV
@@ -10491,11 +11621,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1892"><B
->A.4.6. </B
+NAME="faq-nt-mappings"
+></A
+><B
+>A.6.3. </B
>
- Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
- What gives?
+ CGI's are failing with a "something.cgi is not a valid Windows NT
+ application" error. Why?
</P
></DIV
><DIV
@@ -10504,17 +11636,30 @@ CLASS="answer"
><B
> </B
>
- If you are using an alternate Mail Transport Agent (MTA other than
- sendmail), make sure the options given in the "processmail" and other
- scripts for all
- instances of "sendmail" are correct for your MTA.
+ Depending on what Web server you are using, you will have to configure
+ the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
+ adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the
+ executable.
</P
><P
-> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
- If you are using Postfix, you will also need to enable <SPAN
-CLASS="QUOTE"
->"sendmailnow"</SPAN
->.
+> Microsoft has some advice on this matter, as well:
+ <A
+NAME="AEN2049"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> "Set application mappings. In the ISM, map the extension for the script
+ file(s) to the executable for the script interpreter. For example, you might
+ map the extension .py to Python.exe, the executable for the Python script
+ interpreter. Note For the ActiveState Perl script interpreter, the extension
+ .pl is associated with PerlIS.dll by default. If you want to change the
+ association of .pl to perl.exe, you need to change the application mapping.
+ In the mapping, you must add two percent (%) characters to the end of the
+ pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s"
+ </P
+></BLOCKQUOTE
+>
</P
></DIV
></DIV
@@ -10524,10 +11669,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1899"><B
->A.4.7. </B
+NAME="faq-nt-dbi"
+></A
+><B
+>A.6.4. </B
>
- How come email from Bugzilla changes never reaches me?
+ I'm having trouble with the perl modules for NT not being able to talk to
+ to the database.
</P
></DIV
><DIV
@@ -10536,15 +11684,51 @@ CLASS="answer"
><B
> </B
>
- Double-check that you have not turned off email in your user preferences.
- Confirm that Bugzilla is able to send email by visiting the "Log In"
- link of your Bugzilla installation and clicking the "Email me a password"
- button after entering your email address.
- </P
+ Your modules may be outdated or inaccurate. Try:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
><P
-> If you never receive mail from Bugzilla, chances you do not have
- sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
- to, "/usr/lib/sendmail".
+> Hitting http://www.activestate.com/ActivePerl
+ </P
+></LI
+><LI
+><P
+> Download ActivePerl
+ </P
+></LI
+><LI
+><P
+> Go to your prompt
+ </P
+></LI
+><LI
+><P
+> Type 'ppm'
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="prompt"
+>PPM></TT
+> <B
+CLASS="command"
+>install DBI DBD-mysql GD</B
+>
+ </P
+></LI
+></OL
+>
+ I reckon TimeDate and Data::Dumper come with the activeperl. You can check
+ the ActiveState site for packages for installation through PPM.
+ <A
+HREF=" http://www.activestate.com/Packages/"
+TARGET="_top"
+> http://www.activestate.com/Packages/</A
+>
</P
></DIV
></DIV
@@ -10553,17 +11737,21 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-db">5. Bugzilla Database</H3
+NAME="faq-use"
+></A
+>7. Bugzilla Usage</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1907"><B
->A.5.1. </B
+NAME="faq-use-changeaddress"
+></A
+><B
+>A.7.1. </B
>
- I've heard Bugzilla can be used with Oracle?
+ How do I change my user name (email address) in Bugzilla?
</P
></DIV
><DIV
@@ -10572,10 +11760,8 @@ CLASS="answer"
><B
> </B
>
- Red Hat Bugzilla works with Oracle. The current version
- from Mozilla.org does not have this capability. Unfortunately, though
- you will sacrifice a lot of the really great features available in
- Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+ New in 2.16 - go to the Account section of the Preferences. You will
+ be emailed at both addresses for confirmation.
</P
></DIV
></DIV
@@ -10585,11 +11771,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1912"><B
->A.5.2. </B
+NAME="faq-use-query"
+></A
+><B
+>A.7.2. </B
>
- I think my database might be corrupted, or contain invalid entries. What
- do I do?
+ The query page is very confusing. Isn't there a simpler way to query?
</P
></DIV
><DIV
@@ -10598,29 +11785,9 @@ CLASS="answer"
><B
> </B
>
- Run the <SPAN
-CLASS="QUOTE"
->"sanity check"</SPAN
-> utility
- (<TT
-CLASS="filename"
->./sanitycheck.cgi</TT
-> in the
- Bugzilla_home directory) from your web browser to see! If
- it finishes without errors, you're
- <EM
->probably</EM
-> OK. If it doesn't come back
- OK (i.e. any red letters), there are certain things
- Bugzilla can recover from and certain things it can't. If
- it can't auto-recover, I hope you're familiar with
- mysqladmin commands or have installed another way to
- manage your database. Sanity Check, although it is a good
- basic check on your database integrity, by no means is a
- substitute for competent database administration and
- avoiding deletion of data. It is not exhaustive, and was
- created to do a basic check for the most common problems
- in Bugzilla databases.
+ The interface was simplified by a UI designer for 2.16. Further
+ suggestions for improvement are welcome, but we won't sacrifice power for
+ simplicity.
</P
></DIV
></DIV
@@ -10630,10 +11797,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1920"><B
->A.5.3. </B
+NAME="faq-use-accept"
+></A
+><B
+>A.7.3. </B
>
- I want to manually edit some entries in my database. How?
+ 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?
</P
></DIV
><DIV
@@ -10642,36 +11812,37 @@ CLASS="answer"
><B
> </B
>
- There is no facility in Bugzilla itself to do this. It's also generally
- not a smart thing to do if you don't know exactly what you're doing.
- However, if you understand SQL you can use the mysqladmin utility to
- manually insert, delete, and modify table information. Personally, I
- use "phpMyAdmin". You have to compile a PHP module with MySQL
- support to make it work, but it's very clean and easy to use.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
+ The current behavior is acceptable to bugzilla.mozilla.org and most
+ users. You have your choice of patches
+ to change this behavior, however.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
><A
-NAME="AEN1925"><B
->A.5.4. </B
->
- I try to add myself as a user, but Bugzilla always tells me my password is wrong.
- </P
-></DIV
-><DIV
-CLASS="answer"
+HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
+TARGET="_top"
+> Add a "and accept bug" radio button</A
+></TD
+></TR
+><TR
+><TD
+><A
+HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
+TARGET="_top"
+> "Accept" button automatically assigns to you</A
+></TD
+></TR
+></TBODY
+></TABLE
><P
-><B
-> </B
+></P
>
- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
- the "crypt()" function. This prevented MySQL from storing encrypted passwords.
- Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+ Note that these patches are somewhat dated. You will need to apply
+ them manually.
</P
></DIV
></DIV
@@ -10681,11 +11852,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1930"><B
->A.5.5. </B
+NAME="faq-use-attachment"
+></A
+><B
+>A.7.4. </B
>
- I think I've set up MySQL permissions correctly, but Bugzilla still can't
- connect.
+ I can't upload anything into the database via the "Create Attachment"
+ link. What am I doing wrong?
</P
></DIV
><DIV
@@ -10694,11 +11867,9 @@ CLASS="answer"
><B
> </B
>
- Try running MySQL from its binary: "mysqld --skip-grant-tables". This
- will allow you to completely rule out grant tables as the cause of your
- frustration. However, I do not recommend you run it this way on a regular
- basis, unless you really want your web site defaced and your machine
- cracked.
+ The most likely cause is a very old browser or a browser that is
+ incompatible with file upload via POST. Download the latest Netscape,
+ Microsoft, or Mozilla browser to handle uploads correctly.
</P
></DIV
></DIV
@@ -10708,11 +11879,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1935"><B
->A.5.6. </B
+NAME="faq-use-keyword"
+></A
+><B
+>A.7.5. </B
>
- How do I synchronize bug information among multiple different Bugzilla
- databases?
+ How do I change a keyword in Bugzilla, once some bugs are using it?
</P
></DIV
><DIV
@@ -10721,20 +11893,9 @@ CLASS="answer"
><B
> </B
>
- Well, you can synchronize or you can move bugs. Synchronization will
- only work one way -- you can create a read-only copy of the database
- at one site, and have it regularly updated at intervals from the main
- database.
- </P
-><P
-> MySQL has some synchronization features builtin to the latest releases.
- It would be great if someone looked into the possibilities there
- and provided a report to the newsgroup on how to effectively
- synchronize two Bugzilla installations.
- </P
-><P
-> If you simply need to transfer bugs from one Bugzilla to another,
- checkout the "move.pl" script in the Bugzilla distribution.
+ In the Bugzilla administrator UI, edit the keyword and it will let you
+ replace the old keyword name with a new one. This will cause a problem
+ with the keyword cache. Run sanitycheck.cgi to fix it.
</P
></DIV
></DIV
@@ -10743,17 +11904,21 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-nt">6. Bugzilla and Win32</H3
+NAME="faq-hacking"
+></A
+>8. Bugzilla Hacking</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1944"><B
->A.6.1. </B
+NAME="faq-hacking-bugzillabugs"
+></A
+><B
+>A.8.1. </B
>
- What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+ What bugs are in Bugzilla right now?
</P
></DIV
><DIV
@@ -10762,32 +11927,29 @@ CLASS="answer"
><B
> </B
>
- Remove Windows. Install Linux. Install Bugzilla.
- The boss will never know the difference.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1949"><B
->A.6.2. </B
->
- Is there a "Bundle::Bugzilla" equivalent for Win32?
+ Try <A
+HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"
+TARGET="_top"
+> this link</A
+> to view current bugs or requests for
+ enhancement for Bugzilla.
</P
-></DIV
-><DIV
-CLASS="answer"
><P
-><B
-> </B
->
- Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
- installation on UNIX systems. If someone can volunteer to
- create a suitable PPM bundle for Win32, it would be appreciated.
+> You can view bugs marked for 2.18 release
+ <A
+HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"
+TARGET="_top"
+>here</A
+>.
+ This list includes bugs for the 2.18 release that have already
+ been fixed and checked into CVS. Please consult the
+ <A
+HREF="http://www.bugzilla.org/"
+TARGET="_top"
+> Bugzilla Project Page</A
+> for details on how to
+ check current sources out of CVS so you can have these
+ bug fixes early!
</P
></DIV
></DIV
@@ -10797,11 +11959,13 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1954"><B
->A.6.3. </B
+NAME="faq-hacking-priority"
+></A
+><B
+>A.8.2. </B
>
- CGI's are failing with a "something.cgi is not a valid Windows NT
- application" error. Why?
+ How can I change the default priority to a null value? For instance, have the default
+ priority be "---" instead of "P2"?
</P
></DIV
><DIV
@@ -10810,28 +11974,14 @@ CLASS="answer"
><B
> </B
>
- Depending on what Web server you are using, you will have to configure
- the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
- adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the
- executable.
- </P
-><P
-> Microsoft has some advice on this matter, as well:
- <A
-NAME="AEN1959"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> "Set application mappings. In the ISM, map the extension for the script
- file(s) to the executable for the script interpreter. For example, you might
- map the extension .py to Python.exe, the executable for the Python script
- interpreter. Note For the ActiveState Perl script interpreter, the extension
- .pl is associated with PerlIS.dll by default. If you want to change the
- association of .pl to perl.exe, you need to change the application mapping.
- In the mapping, you must add two percent (%) characters to the end of the
- pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s"
- </P
-></BLOCKQUOTE
->
+ 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".
</P
></DIV
></DIV
@@ -10841,11 +11991,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1962"><B
->A.6.4. </B
+NAME="faq-hacking-patches"
+></A
+><B
+>A.8.3. </B
>
- I'm having trouble with the perl modules for NT not being able to talk to
- to the database.
+ What's the best way to submit patches? What guidelines should I follow?
</P
></DIV
><DIV
@@ -10853,1156 +12004,1385 @@ CLASS="answer"
><P
><B
> </B
->
- Your modules may be outdated or inaccurate. Try:
- <P
+><P
></P
><OL
TYPE="1"
><LI
><P
-> Hitting http://www.activestate.com/ActivePerl
+> Enter a bug into bugzilla.mozilla.org for the <SPAN
+CLASS="QUOTE"
+>"<A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
+TARGET="_top"
+>Bugzilla</A
+>"</SPAN
+>
+ product.
</P
></LI
><LI
><P
-> Download ActivePerl
+> Upload your patch as a unified diff (having used "diff -u" against
+ the <EM
+>current sources</EM
+> checked out of CVS),
+ or new source file by clicking
+ "Create a new attachment" link on the bug page you've just created, and
+ include any descriptions of database changes you may make, into the bug
+ ID you submitted in step #1. Be sure and click the "Patch" checkbox
+ to indicate the text you are sending is a patch!
</P
></LI
><LI
><P
-> Go to your prompt
+> Announce your patch and the associated URL
+ (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
+ the newsgroup (netscape.public.mozilla.webtools). You'll get a really
+ good, fairly immediate reaction to the implications of your patch,
+ which will also give us an idea how well-received the change would
+ be.
</P
></LI
><LI
><P
-> Type 'ppm'
+> If it passes muster with minimal modification, the person to whom
+ the bug is assigned in Bugzilla is responsible for seeing the patch
+ is checked into CVS.
</P
></LI
><LI
><P
-> <TT
-CLASS="prompt"
->PPM></TT
-> <B
-CLASS="command"
->install DBI DBD-mysql GD</B
->
+> Bask in the glory of the fact that you helped write the most successful
+ open-source bug-tracking software on the planet :)
</P
></LI
></OL
->
- I reckon TimeDate and Data::Dumper come with the activeperl. You can check
- the ActiveState site for packages for installation through PPM.
- <A
-HREF=" http://www.activestate.com/Packages/"
-TARGET="_top"
-> http://www.activestate.com/Packages/</A
->
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-use">7. Bugzilla Usage</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1983"><B
->A.7.1. </B
->
- How do I change my user name (email address) in Bugzilla?
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- New in 2.16 - go to the Account section of the Preferences. You will
- be emailed at both addresses for confirmation.
- </P
-></DIV
+></P
></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1988"><B
->A.7.2. </B
->
- The query page is very confusing. Isn't there a simpler way to query?
- </P
></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- The interface was simplified by a UI designer for 2.16. Further
- suggestions for improvement are welcome, but we won't sacrifice power for
- simplicity.
- </P
></DIV
></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1993"><B
->A.7.3. </B
->
- 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?
- </P
></DIV
><DIV
-CLASS="answer"
+CLASS="appendix"
+><HR><H1
+><A
+NAME="database"
+></A
+>Appendix B. The Bugzilla Database</H1
+><DIV
+CLASS="note"
><P
-><B
-> </B
->
- The current behavior is acceptable to bugzilla.mozilla.org and most
- users. You have your choice of patches
- to change this behavior, however.
- <P
></P
><TABLE
+CLASS="note"
+WIDTH="100%"
BORDER="0"
-><TBODY
><TR
><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
-TARGET="_top"
-> Add a "and accept bug" radio button</A
-></TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-><A
-HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
-TARGET="_top"
-> "Accept" button automatically assigns to you</A
+ALIGN="LEFT"
+VALIGN="TOP"
+><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
></TD
></TR
-></TBODY
></TABLE
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="dbschema"
+></A
+>B.1. Database Schema Chart</H1
+><P
+> <DIV
+CLASS="mediaobject"
+><P
+><IMG
+SRC="../images/dbschema.jpg"><DIV
+CLASS="caption"
><P
+>Bugzilla database relationships chart</P
+></DIV
></P
->
- Note that these patches are somewhat dated. You will need to apply
- them manually.
- </P
></DIV
+>
+ </P
></DIV
><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="dbdoc"
+></A
+>B.2. MySQL Bugzilla Database Introduction</H1
+><P
+>This information comes straight from my life. I was forced to learn
+ how Bugzilla organizes database because of nitpicky requests from users
+ for tiny changes in wording, rather than having people re-educate
+ themselves or figure out how to work our procedures around the tool. It
+ sucks, but it can and will happen to you, so learn how the schema works
+ and deal with it when it comes.</P
+><P
+>So, here you are with your brand-new installation of Bugzilla.
+ You've got MySQL set up, Apache working right, Perl DBI and DBD talking
+ to the database flawlessly. Maybe you've even entered a few test bugs to
+ make sure email's working; people seem to be notified of new bugs and
+ changes, and you can enter and edit bugs to your heart's content. Perhaps
+ you've gone through the trouble of setting up a gateway for people to
+ submit bugs to your database via email, have had a few people test it,
+ and received rave reviews from your beta testers.</P
+><P
+>What's the next thing you do? Outline a training strategy for your
+ development team, of course, and bring them up to speed on the new tool
+ you've labored over for hours.</P
+><P
+>Your first training session starts off very well! You have a
+ captive audience which seems enraptured by the efficiency embodied in
+ this thing called "Bugzilla". You are caught up describing the nifty
+ features, how people can save favorite queries in the database, set them
+ up as headers and footers on their pages, customize their layouts,
+ generate reports, track status with greater efficiency than ever before,
+ leap tall buildings with a single bound and rescue Jane from the clutches
+ of Certain Death!</P
+><P
+>But Certain Death speaks up -- a tiny voice, from the dark corners
+ of the conference room. "I have a concern," the voice hisses from the
+ darkness, "about the use of the word 'verified'.</P
+><P
+>The room, previously filled with happy chatter, lapses into
+ reverential silence as Certain Death (better known as the Vice President
+ of Software Engineering) continues. "You see, for two years we've used
+ the word 'verified' to indicate that a developer or quality assurance
+ engineer has confirmed that, in fact, a bug is valid. I don't want to
+ lose two years of training to a new software product. You need to change
+ the bug status of 'verified' to 'approved' as soon as possible. To avoid
+ confusion, of course."</P
+><P
+>Oh no! Terror strikes your heart, as you find yourself mumbling
+ "yes, yes, I don't think that would be a problem," You review the changes
+ with Certain Death, and continue to jabber on, "no, it's not too big a
+ change. I mean, we have the source code, right? You know, 'Use the
+ Source, Luke' and all that... no problem," All the while you quiver
+ inside like a beached jellyfish bubbling, burbling, and boiling on a hot
+ Jamaican sand dune...</P
><P
+>Thus begins your adventure into the heart of Bugzilla. You've been
+ forced to learn about non-portable enum() fields, varchar columns, and
+ tinyint definitions. The Adventure Awaits You!</P
+><DIV
+CLASS="section"
+><HR><H2
+CLASS="section"
><A
-NAME="AEN2003"><B
->A.7.4. </B
+NAME="AEN2162"
+></A
+>B.2.1. Bugzilla Database Basics</H2
+><P
+>If you were like me, at this point you're totally clueless about
+ the internals of MySQL, and if it weren't for this executive order from
+ the Vice President you couldn't care less about the difference between
+ a
+ <SPAN
+CLASS="QUOTE"
+>"bigint"</SPAN
>
- I can't upload anything into the database via the "Create Attachment"
- link. What am I doing wrong?
- </P
-></DIV
-><DIV
-CLASS="answer"
+
+ and a
+ <SPAN
+CLASS="QUOTE"
+>"tinyint"</SPAN
+>
+
+ entry in MySQL. I recommend you refer to the MySQL documentation,
+ available at
+ <A
+HREF="http://www.mysql.com/doc.html"
+TARGET="_top"
+>MySQL.com</A
+>
+
+ . Below are the basics you need to know about the Bugzilla database.
+ Check the chart above for more details.</P
><P
-><B
-> </B
+> <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>To connect to your database:</P
+><P
+> <TT
+CLASS="prompt"
+>bash#</TT
>
- The most likely cause is a very old browser or a browser that is
- incompatible with file upload via POST. Download the latest Netscape,
- Microsoft, or Mozilla browser to handle uploads correctly.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
+
+ <B
+CLASS="command"
+>mysql</B
+>
+
+ <TT
+CLASS="parameter"
+><I
+>-u root</I
+></TT
+>
+ </P
><P
-><A
-NAME="AEN2008"><B
->A.7.5. </B
+>If this works without asking you for a password,
+ <EM
+>shame on you</EM
>
- Email submissions to Bugzilla that have attachments end up asking me to
- save it as a "cgi" file.
- </P
-></DIV
-><DIV
-CLASS="answer"
+
+ ! You should have locked your security down like the installation
+ instructions told you to. You can find details on locking down
+ your database in the Bugzilla FAQ in this directory (under
+ "Security"), or more robust security generalities in the
+ <A
+HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
+TARGET="_top"
+>MySQL
+ searchable documentation</A
+>.
+ </P
+></LI
+><LI
><P
-><B
-> </B
+>You should now be at a prompt that looks like this:</P
+><P
+> <TT
+CLASS="prompt"
+>mysql></TT
+>
+ </P
+><P
+>At the prompt, if
+ <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+>
+
+ is the name you chose in the
+ <TT
+CLASS="filename"
+>localconfig</TT
+>
+
+ file for your Bugzilla database, type:</P
+><P
+> <TT
+CLASS="prompt"
+>mysql</TT
+>
+
+ <B
+CLASS="command"
+>use bugs;</B
+>
+ </P
+></LI
+></OL
>
- Yup. Just rename it once you download it, or save it under a different
- filename. This will not be fixed anytime soon, because it would
- cripple some other functionality.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
+ </P
><DIV
-CLASS="question"
-><P
+CLASS="section"
+><HR><H3
+CLASS="section"
><A
-NAME="AEN2013"><B
->A.7.6. </B
+NAME="AEN2189"
+></A
+>B.2.1.1. Bugzilla Database Tables</H3
+><P
+>Imagine your MySQL database as a series of spreadsheets, and
+ you won't be too far off. If you use this command:</P
+><P
+> <TT
+CLASS="prompt"
+>mysql></TT
>
- How do I change a keyword in Bugzilla, once some bugs are using it?
- </P
-></DIV
-><DIV
-CLASS="answer"
+ <B
+CLASS="command"
+>show tables from bugs;</B
+>
+ </P
><P
-><B
-> </B
+>you'll be able to see the names of all the
+ <SPAN
+CLASS="QUOTE"
+>"spreadsheets"</SPAN
>
- In the Bugzilla administrator UI, edit the keyword and it will let you
- replace the old keyword name with a new one. This will cause a problem
- with the keyword cache. Run sanitycheck.cgi to fix it.
- </P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="qandadiv"
-><H3
-><A
-NAME="faq-hacking">8. Bugzilla Hacking</H3
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
+ (tables) in your database.</P
><P
-><A
-NAME="AEN2020"><B
->A.8.1. </B
+>From the command issued above, ou should have some
+ output that looks like this:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> +-------------------+
+| Tables in bugs |
++-------------------+
+| attachments |
+| bugs |
+| bugs_activity |
+| cc |
+| components |
+| dependencies |
+| fielddefs |
+| groups |
+| keyworddefs |
+| keywords |
+| logincookies |
+| longdescs |
+| milestones |
+| namedqueries |
+| products |
+| profiles |
+| profiles_activity |
+| shadowlog |
+| tokens |
+| versions |
+| votes |
+| watch |
++-------------------+
+</PRE
+></FONT
+></TD
+></TR
+></TABLE
>
- What bugs are in Bugzilla right now?
- </P
+</P
+><P
+CLASS="literallayout"
+><br>
+ Here's an overview of what each table does. Most columns in each table have<br>
+descriptive names that make it fairly trivial to figure out their jobs.<br>
+<br>
+attachments: This table stores all attachments to bugs. It tends to be your<br>
+largest table, yet also generally has the fewest entries because file<br>
+attachments are so (relatively) large.<br>
+<br>
+bugs: This is the core of your system. The bugs table stores most of the<br>
+current information about a bug, with the exception of the info stored in the<br>
+other tables.<br>
+<br>
+bugs_activity: This stores information regarding what changes are made to bugs<br>
+when -- a history file.<br>
+<br>
+cc: This tiny table simply stores all the CC information for any bug which has<br>
+any entries in the CC field of the bug. Note that, like most other tables in<br>
+Bugzilla, it does not refer to users by their user names, but by their unique<br>
+userid, stored as a primary key in the profiles table.<br>
+<br>
+components: This stores the programs and components (or products and<br>
+components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
+(product) field is the full name of the product, rather than some other unique<br>
+identifier, like bug_id and user_id are elsewhere in the database.<br>
+<br>
+dependencies: Stores data about those cool dependency trees.<br>
+<br>
+fielddefs: A nifty table that defines other tables. For instance, when you<br>
+submit a form that changes the value of "AssignedTo" this table allows<br>
+translation to the actual field name "assigned_to" for entry into MySQL.<br>
+<br>
+groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
+identify group memberships. For instance, say the group that is allowed to<br>
+tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
+users is assigned a "2", and the group that is allowed to create new groups is<br>
+assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
+like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
+parameters and create groups, but not edit users, by giving him a bitmask of<br>
+"5", or a user allowed to edit users and create groups, but not tweak<br>
+parameters, by giving him a bitmask of "6" Simple, huh?<br>
+ If this makes no sense to you, try this at the mysql prompt:<br>
+mysql> select * from groups;<br>
+ You'll see the list, it makes much more sense that way.<br>
+<br>
+keyworddefs: Definitions of keywords to be used<br>
+<br>
+keywords: Unlike what you'd think, this table holds which keywords are<br>
+associated with which bug id's.<br>
+<br>
+logincookies: This stores every login cookie ever assigned to you for every<br>
+machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
+housecleaning -- I see cookies in this file I've not used for months. However,<br>
+since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
+sense.<br>
+<br>
+longdescs: The meat of bugzilla -- here is where all user comments are stored!<br>
+You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
+sparingly -- that's only the amount of space the Old Testament from the Bible<br>
+would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
+bug_id to which it's attached, so the order is necessarily chronological, for<br>
+comments are played back in the order in which they are received.<br>
+<br>
+milestones: Interesting that milestones are associated with a specific product<br>
+in this table, but Bugzilla does not yet support differing milestones by<br>
+product through the standard configuration interfaces.<br>
+<br>
+namedqueries: This is where everybody stores their "custom queries". Very<br>
+cool feature; it beats the tar out of having to bookmark each cool query you<br>
+construct.<br>
+<br>
+products: What products you have, whether new bug entries are allowed for the<br>
+product, what milestone you're working toward on that product, votes, etc. It<br>
+will be nice when the components table supports these same features, so you<br>
+could close a particular component for bug entry without having to close an<br>
+entire product...<br>
+<br>
+profiles: Ahh, so you were wondering where your precious user information was<br>
+stored? Here it is! With the passwords in plain text for all to see! (but<br>
+sshh... don't tell your users!)<br>
+<br>
+profiles_activity: Need to know who did what when to who's profile? This'll<br>
+tell you, it's a pretty complete history.<br>
+<br>
+shadowlog: I could be mistaken here, but I believe this table tells you when<br>
+your shadow database is updated and what commands were used to update it. We<br>
+don't use a shadow database at our site yet, so it's pretty empty for us.<br>
+<br>
+versions: Version information for every product<br>
+<br>
+votes: Who voted for what when<br>
+<br>
+watch: Who (according to userid) is watching who's bugs (according to their<br>
+userid).<br>
+<br>
+<br>
+===<br>
+THE DETAILS<br>
+===<br>
+<br>
+ Ahh, so you're wondering just what to do with the information above? At the<br>
+mysql prompt, you can view any information about the columns in a table with<br>
+this command (where "table" is the name of the table you wish to view):<br>
+<br>
+mysql> show columns from table;<br>
+<br>
+ You can also view all the data in a table with this command:<br>
+<br>
+mysql> select * from table;<br>
+<br>
+ -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
+you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
+50,000 bugs play across your screen.<br>
+<br>
+ You can limit the display from above a little with the command, where<br>
+"column" is the name of the column for which you wish to restrict information:<br>
+<br>
+mysql> select * from table where (column = "some info");<br>
+<br>
+ -- or the reverse of this<br>
+<br>
+mysql> select * from table where (column != "some info");<br>
+<br>
+ Let's take our example from the introduction, and assume you need to change<br>
+the word "verified" to "approved" in the resolution field. We know from the<br>
+above information that the resolution is likely to be stored in the "bugs"<br>
+table. Note we'll need to change a little perl code as well as this database<br>
+change, but I won't plunge into that in this document. Let's verify the<br>
+information is stored in the "bugs" table:<br>
+<br>
+mysql> show columns from bugs<br>
+<br>
+ (exceedingly long output truncated here)<br>
+| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br>
+<br>
+ Sorry about that long line. We see from this that the "bug status" column is<br>
+an "enum field", which is a MySQL peculiarity where a string type field can<br>
+only have certain types of entries. While I think this is very cool, it's not<br>
+standard SQL. Anyway, we need to add the possible enum field entry<br>
+'APPROVED' by altering the "bugs" table.<br>
+<br>
+mysql> ALTER table bugs CHANGE bug_status bug_status<br>
+ -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br>
+ -> "VERIFIED", "APPROVED", "CLOSED") not null;<br>
+<br>
+ (note we can take three lines or more -- whatever you put in before the<br>
+semicolon is evaluated as a single expression)<br>
+<br>
+Now if you do this:<br>
+<br>
+mysql> show columns from bugs;<br>
+<br>
+ you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
+available! Cool thing, too, is that this is reflected on your query page as<br>
+well -- you can query by the new status. But how's it fit into the existing<br>
+scheme of things?<br>
+ Looks like you need to go back and look for instances of the word "verified"<br>
+in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
+"approved" and you're in business (make sure that's a case-insensitive search).<br>
+Although you can query by the enum field, you can't give something a status<br>
+of "APPROVED" until you make the perl changes. Note that this change I<br>
+mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
+this. But you need to know this stuff anyway, right?<br>
+ </P
></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
- Try <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"
-TARGET="_top"
-> this link</A
-> to view current bugs or requests for
- enhancement for Bugzilla.
- </P
-><P
-> You can view bugs marked for 2.18 release
- <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"
-TARGET="_top"
->here</A
->.
- This list includes bugs for the 2.18 release that have already
- been fixed and checked into CVS. Please consult the
- <A
-HREF="http://www.mozilla.org/projects/bugzilla/"
-TARGET="_top"
-> Bugzilla Project Page</A
-> for details on how to
- check current sources out of CVS so you can have these
- bug fixes early!
- </P
></DIV
></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN2029"><B
->A.8.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"
+CLASS="appendix"
+><HR><H1
+><A
+NAME="patches"
+></A
+>Appendix C. Useful Patches and Utilities for Bugzilla</H1
><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".
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
+>Are you looking for a way to put your Bugzilla into overdrive? Catch
+ some of the niftiest tricks here in this section.</P
><DIV
-CLASS="question"
-><P
+CLASS="section"
+><HR><H1
+CLASS="section"
><A
-NAME="AEN2035"><B
->A.8.3. </B
+NAME="rewrite"
+></A
+>C.1. Apache
+ <TT
+CLASS="filename"
+>mod_rewrite</TT
>
- What's the best way to submit patches? What guidelines should I follow?
- </P
-></DIV
-><DIV
-CLASS="answer"
+
+ magic</H1
><P
-><B
-> </B
+>Apache's
+ <TT
+CLASS="filename"
+>mod_rewrite</TT
+>
+
+ module lets you do some truly amazing things with URL rewriting. Here are
+ a couple of examples of what you can do.</P
><P
></P
><OL
TYPE="1"
><LI
><P
-> Enter a bug into bugzilla.mozilla.org for the <SPAN
-CLASS="QUOTE"
->"<A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
-TARGET="_top"
->Bugzilla</A
->"</SPAN
+>Make it so if someone types
+ <TT
+CLASS="computeroutput"
+>http://www.foo.com/12345</TT
>
- product.
- </P
+
+ , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
+ setting up your VirtualHost section for Bugzilla with a rule like
+ this:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> <VirtualHost 12.34.56.78>
+RewriteEngine On
+RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+</VirtualHost>
+</PRE
+></FONT
+></TD
+></TR
+></TABLE
></LI
><LI
><P
-> Upload your patch as a unified diff (having used "diff -u" against
- the <EM
->current sources</EM
-> checked out of CVS),
- or new source file by clicking
- "Create a new attachment" link on the bug page you've just created, and
- include any descriptions of database changes you may make, into the bug
- ID you submitted in step #1. Be sure and click the "Patch" checkbox
- to indicate the text you are sending is a patch!
- </P
+>There are many, many more things you can do with mod_rewrite.
+ Please refer to the mod_rewrite documentation at
+ <A
+HREF="http://www.apache.org"
+TARGET="_top"
+>http://www.apache.org</A
+>.
+ </P
></LI
-><LI
+></OL
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="cmdline"
+></A
+>C.2. Command-line Bugzilla Queries</H1
><P
-> Announce your patch and the associated URL
- (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
- the newsgroup (netscape.public.mozilla.webtools). You'll get a really
- good, fairly immediate reaction to the implications of your patch,
- which will also give us an idea how well-received the change would
- be.
- </P
-></LI
-><LI
+>There are a suite of Unix utilities for querying Bugzilla from the
+ command line. They live in the
+ <TT
+CLASS="filename"
+>contrib/cmdline</TT
+>
+ directory. However, they
+ have not yet been updated to work with 2.16 (post-templatisation.).
+ There are three files - <TT
+CLASS="filename"
+>query.conf</TT
+>,
+ <TT
+CLASS="filename"
+>buglist</TT
+> and <TT
+CLASS="filename"
+>bugs</TT
+>.</P
><P
-> If it passes muster with minimal modification, the person to whom
- the bug is assigned in Bugzilla is responsible for seeing the patch
- is checked into CVS.
- </P
-></LI
-><LI
+><TT
+CLASS="filename"
+>query.conf</TT
+>
+ contains the mapping from options to field
+ names and comparison types. Quoted option names are "grepped" for, so it
+ should be easy to edit this file. Comments (#) have no effect; you must
+ make sure these lines do not contain any quoted "option".</P
><P
-> Bask in the glory of the fact that you helped write the most successful
- open-source bug-tracking software on the planet :)
- </P
-></LI
-></OL
-></P
-></DIV
-></DIV
-></DIV
+><TT
+CLASS="filename"
+>buglist</TT
+>
+ is a shell script which submits a Bugzilla query and writes
+ the resulting HTML page to stdout. It supports both short options, (such
+ as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
+ "--reporter=bar"). If the first character of an option is not "-", it is
+ treated as if it were prefixed with "--default=".</P
+><P
+>The column list is taken from the COLUMNLIST environment variable.
+ This is equivalent to the "Change Columns" option when you list bugs in
+ buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
+ in your cookies file to see your current COLUMNLIST setting.</P
+><P
+><TT
+CLASS="filename"
+>bugs</TT
+> is a simple shell script which calls
+ <TT
+CLASS="filename"
+>buglist</TT
+> and extracts the
+ bug numbers from the output. Adding the prefix
+ "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
+ a working link if any bugs are found. Counting bugs is easy. Pipe the
+ results through
+ <B
+CLASS="command"
+>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
+>
+ </P
+><P
+>Akkana Peck says she has good results piping
+ <TT
+CLASS="filename"
+>buglist</TT
+> output through
+ <B
+CLASS="command"
+>w3m -T text/html -dump</B
+>
+ </P
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
-NAME="database">Appendix B. The Bugzilla Database</H1
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
+NAME="variants"
+></A
+>Appendix D. Bugzilla Variants and Competitors</H1
><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
-></TD
-></TR
-></TABLE
-></DIV
+>I created this section to answer questions about Bugzilla competitors
+ and variants, then found a wonderful site which covers an awful lot of what
+ I wanted to discuss. Rather than quote it in its entirety, I'll simply
+ refer you here:
+ <A
+HREF="http://linas.org/linux/pm.html"
+TARGET="_top"
+> http://linas.org/linux/pm.html</A
+>
+ </P
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="dbschema">B.1. Database Schema Chart</H1
-><P
-> <DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="../images/dbschema.jpg"><DIV
-CLASS="caption"
+NAME="variant-redhat"
+></A
+>D.1. Red Hat Bugzilla</H1
+><P
+>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+ obsolete. The newest version in use is based on version 2.17.1 and is in
+ the process of being integrated into the main Bugzilla source tree. The
+ back-end is modified to work with PostgreSQL instead of MySQL and they have
+ custom templates to get their desired look and feel, but other than that it
+ is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
+ effort to make sure that the changes he made could be integrated back into
+ the main tree.
+ <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>Bug
+ 98304</A
+> exists to track this integration.
+ </P
><P
->Bugzilla database relationships chart</P
-></DIV
-></P
-></DIV
+>URL:
+ <A
+HREF="http://bugzilla.redhat.com/bugzilla/"
+TARGET="_top"
+> http://bugzilla.redhat.com/bugzilla/</A
>
</P
+><P
+>This section last updated 24 Dec 2002</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
-><P
->This information comes straight from my life. I was forced to learn
- how Bugzilla organizes database because of nitpicky requests from users
- for tiny changes in wording, rather than having people re-educate
- themselves or figure out how to work our procedures around the tool. It
- sucks, but it can and will happen to you, so learn how the schema works
- and deal with it when it comes.</P
-><P
->So, here you are with your brand-new installation of Bugzilla.
- You've got MySQL set up, Apache working right, Perl DBI and DBD talking
- to the database flawlessly. Maybe you've even entered a few test bugs to
- make sure email's working; people seem to be notified of new bugs and
- changes, and you can enter and edit bugs to your heart's content. Perhaps
- you've gone through the trouble of setting up a gateway for people to
- submit bugs to your database via email, have had a few people test it,
- and received rave reviews from your beta testers.</P
-><P
->What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new tool
- you've labored over for hours.</P
-><P
->Your first training session starts off very well! You have a
- captive audience which seems enraptured by the efficiency embodied in
- this thing called "Bugzilla". You are caught up describing the nifty
- features, how people can save favorite queries in the database, set them
- up as headers and footers on their pages, customize their layouts,
- generate reports, track status with greater efficiency than ever before,
- leap tall buildings with a single bound and rescue Jane from the clutches
- of Certain Death!</P
+NAME="variant-fenris"
+></A
+>D.2. Loki Bugzilla (Fenris)</H1
><P
->But Certain Death speaks up -- a tiny voice, from the dark corners
- of the conference room. "I have a concern," the voice hisses from the
- darkness, "about the use of the word 'verified'.</P
+>Fenris was a fork from Bugzilla made by Loki Games; when
+ Loki went into receivership, it died. While Loki's other code lives on,
+ its custodians recommend Bugzilla for future bug-tracker deployments.
+ </P
><P
->The room, previously filled with happy chatter, lapses into
- reverential silence as Certain Death (better known as the Vice President
- of Software Engineering) continues. "You see, for two years we've used
- the word 'verified' to indicate that a developer or quality assurance
- engineer has confirmed that, in fact, a bug is valid. I don't want to
- lose two years of training to a new software product. You need to change
- the bug status of 'verified' to 'approved' as soon as possible. To avoid
- confusion, of course."</P
+>This section last updated 27 Jul 2002</P
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="variant-issuezilla"
+></A
+>D.3. Issuezilla</H1
><P
->Oh no! Terror strikes your heart, as you find yourself mumbling
- "yes, yes, I don't think that would be a problem," You review the changes
- with Certain Death, and continue to jabber on, "no, it's not too big a
- change. I mean, we have the source code, right? You know, 'Use the
- Source, Luke' and all that... no problem," All the while you quiver
- inside like a beached jellyfish bubbling, burbling, and boiling on a hot
- Jamaican sand dune...</P
+>Issuezilla was another fork from Bugzilla, made by collab.net and
+ hosted at tigris.org. It is also dead; the primary focus of bug-tracking
+ at tigris.org is their Java-based bug-tracker,
+ <A
+HREF="#variant-scarab"
+>Section D.4</A
+>.</P
><P
->Thus begins your adventure into the heart of Bugzilla. You've been
- forced to learn about non-portable enum() fields, varchar columns, and
- tinyint definitions. The Adventure Awaits You!</P
+>This section last updated 27 Jul 2002</P
+></DIV
><DIV
CLASS="section"
-><HR><H2
+><HR><H1
CLASS="section"
><A
-NAME="AEN2077">B.2.1. Bugzilla Database Basics</H2
+NAME="variant-scarab"
+></A
+>D.4. Scarab</H1
><P
->If you were like me, at this point you're totally clueless about
- the internals of MySQL, and if it weren't for this executive order from
- the Vice President you couldn't care less about the difference between
- a
- <SPAN
-CLASS="QUOTE"
->"bigint"</SPAN
->
-
- and a
- <SPAN
-CLASS="QUOTE"
->"tinyint"</SPAN
->
-
- entry in MySQL. I recommend you refer to the MySQL documentation,
- available at
- <A
-HREF="http://www.mysql.com/doc.html"
+>Scarab is a new open source bug-tracking system built using Java
+ Servlet technology. It is currently at version 1.0 beta 13.</P
+><P
+>URL:
+ <A
+HREF="http://scarab.tigris.org/"
TARGET="_top"
->MySQL.com</A
+>http://scarab.tigris.org</A
>
-
- . Below are the basics you need to know about the Bugzilla database.
- Check the chart above for more details.</P
-><P
-> <P
-></P
-><OL
-TYPE="1"
-><LI
+ </P
><P
->To connect to your database:</P
+>This section last updated 18 Jan 2003</P
+></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="variant-perforce"
+></A
+>D.5. Perforce SCM</H1
><P
-> <TT
-CLASS="prompt"
->bash#</TT
->
-
- <B
-CLASS="command"
->mysql</B
->
-
- <TT
-CLASS="parameter"
-><I
->-u root</I
-></TT
+>Although Perforce isn't really a bug tracker, it can be used as
+ such through the <SPAN
+CLASS="QUOTE"
+>"jobs"</SPAN
>
- </P
+ functionality.</P
><P
->If this works without asking you for a password,
- <EM
->shame on you</EM
->
-
- ! You should have locked your security down like the installation
- instructions told you to. You can find details on locking down
- your database in the Bugzilla FAQ in this directory (under
- "Security"), or more robust security generalities in the
- <A
-HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
+>URL:
+ <A
+HREF="http://www.perforce.com/perforce/technotes/note052.html"
TARGET="_top"
->MySQL
- searchable documentation</A
->.
- </P
-></LI
-><LI
-><P
->You should now be at a prompt that looks like this:</P
-><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- </P
-><P
->At the prompt, if
- <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
->
-
- is the name you chose in the
- <TT
-CLASS="filename"
->localconfig</TT
+> http://www.perforce.com/perforce/technotes/note052.html
+ </A
>
-
- file for your Bugzilla database, type:</P
+ </P
><P
-> <TT
-CLASS="prompt"
->mysql</TT
->
-
- <B
-CLASS="command"
->use bugs;</B
->
- </P
-></LI
-></OL
->
- </P
+>This section last updated 27 Jul 2002</P
+></DIV
><DIV
CLASS="section"
-><HR><H3
+><HR><H1
CLASS="section"
><A
-NAME="AEN2104">B.2.1.1. Bugzilla Database Tables</H3
+NAME="variant-sourceforge"
+></A
+>D.6. SourceForge</H1
><P
->Imagine your MySQL database as a series of spreadsheets, and
- you won't be too far off. If you use this command:</P
+>SourceForge is a way of coordinating geographically
+ distributed free software and open source projects over the Internet.
+ It has a built-in bug tracker, but it's not highly thought of.</P
><P
-> <TT
-CLASS="prompt"
->mysql></TT
->
- <B
-CLASS="command"
->show tables from bugs;</B
+>URL:
+ <A
+HREF="http://www.sourceforge.net"
+TARGET="_top"
+> http://www.sourceforge.net</A
>
- </P
+ </P
><P
->you'll be able to see the names of all the
- <SPAN
-CLASS="QUOTE"
->"spreadsheets"</SPAN
->
- (tables) in your database.</P
+>This section last updated 27 Jul 2002</P
+></DIV
+></DIV
+><DIV
+CLASS="appendix"
+><HR><H1
+><A
+NAME="gfdl"
+></A
+>Appendix E. GNU Free Documentation License</H1
><P
->From the command issued above, ou should have some
- output that looks like this:
-<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> +-------------------+
-| Tables in bugs |
-+-------------------+
-| attachments |
-| bugs |
-| bugs_activity |
-| cc |
-| components |
-| dependencies |
-| fielddefs |
-| groups |
-| keyworddefs |
-| keywords |
-| logincookies |
-| longdescs |
-| milestones |
-| namedqueries |
-| products |
-| profiles |
-| profiles_activity |
-| shadowlog |
-| tokens |
-| versions |
-| votes |
-| watch |
-+-------------------+
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-</P
+>Version 1.1, March 2000</P
+><A
+NAME="AEN2277"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
><P
-CLASS="literallayout"
-><br>
- Here's an overview of what each table does. Most columns in each table have<br>
-descriptive names that make it fairly trivial to figure out their jobs.<br>
-<br>
-attachments: This table stores all attachments to bugs. It tends to be your<br>
-largest table, yet also generally has the fewest entries because file<br>
-attachments are so (relatively) large.<br>
-<br>
-bugs: This is the core of your system. The bugs table stores most of the<br>
-current information about a bug, with the exception of the info stored in the<br>
-other tables.<br>
-<br>
-bugs_activity: This stores information regarding what changes are made to bugs<br>
-when -- a history file.<br>
-<br>
-cc: This tiny table simply stores all the CC information for any bug which has<br>
-any entries in the CC field of the bug. Note that, like most other tables in<br>
-Bugzilla, it does not refer to users by their user names, but by their unique<br>
-userid, stored as a primary key in the profiles table.<br>
-<br>
-components: This stores the programs and components (or products and<br>
-components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
-(product) field is the full name of the product, rather than some other unique<br>
-identifier, like bug_id and user_id are elsewhere in the database.<br>
-<br>
-dependencies: Stores data about those cool dependency trees.<br>
-<br>
-fielddefs: A nifty table that defines other tables. For instance, when you<br>
-submit a form that changes the value of "AssignedTo" this table allows<br>
-translation to the actual field name "assigned_to" for entry into MySQL.<br>
-<br>
-groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
-identify group memberships. For instance, say the group that is allowed to<br>
-tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
-users is assigned a "2", and the group that is allowed to create new groups is<br>
-assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
-like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
-parameters and create groups, but not edit users, by giving him a bitmask of<br>
-"5", or a user allowed to edit users and create groups, but not tweak<br>
-parameters, by giving him a bitmask of "6" Simple, huh?<br>
- If this makes no sense to you, try this at the mysql prompt:<br>
-mysql> select * from groups;<br>
- You'll see the list, it makes much more sense that way.<br>
-<br>
-keyworddefs: Definitions of keywords to be used<br>
-<br>
-keywords: Unlike what you'd think, this table holds which keywords are<br>
-associated with which bug id's.<br>
-<br>
-logincookies: This stores every login cookie ever assigned to you for every<br>
-machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
-housecleaning -- I see cookies in this file I've not used for months. However,<br>
-since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
-sense.<br>
-<br>
-longdescs: The meat of bugzilla -- here is where all user comments are stored!<br>
-You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
-sparingly -- that's only the amount of space the Old Testament from the Bible<br>
-would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
-bug_id to which it's attached, so the order is necessarily chronological, for<br>
-comments are played back in the order in which they are received.<br>
-<br>
-milestones: Interesting that milestones are associated with a specific product<br>
-in this table, but Bugzilla does not yet support differing milestones by<br>
-product through the standard configuration interfaces.<br>
-<br>
-namedqueries: This is where everybody stores their "custom queries". Very<br>
-cool feature; it beats the tar out of having to bookmark each cool query you<br>
-construct.<br>
-<br>
-products: What products you have, whether new bug entries are allowed for the<br>
-product, what milestone you're working toward on that product, votes, etc. It<br>
-will be nice when the components table supports these same features, so you<br>
-could close a particular component for bug entry without having to close an<br>
-entire product...<br>
-<br>
-profiles: Ahh, so you were wondering where your precious user information was<br>
-stored? Here it is! With the passwords in plain text for all to see! (but<br>
-sshh... don't tell your users!)<br>
-<br>
-profiles_activity: Need to know who did what when to who's profile? This'll<br>
-tell you, it's a pretty complete history.<br>
-<br>
-shadowlog: I could be mistaken here, but I believe this table tells you when<br>
-your shadow database is updated and what commands were used to update it. We<br>
-don't use a shadow database at our site yet, so it's pretty empty for us.<br>
-<br>
-versions: Version information for every product<br>
-<br>
-votes: Who voted for what when<br>
-<br>
-watch: Who (according to userid) is watching who's bugs (according to their<br>
-userid).<br>
-<br>
-<br>
-===<br>
-THE DETAILS<br>
-===<br>
-<br>
- Ahh, so you're wondering just what to do with the information above? At the<br>
-mysql prompt, you can view any information about the columns in a table with<br>
-this command (where "table" is the name of the table you wish to view):<br>
-<br>
-mysql> show columns from table;<br>
-<br>
- You can also view all the data in a table with this command:<br>
-<br>
-mysql> select * from table;<br>
-<br>
- -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
-you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
-50,000 bugs play across your screen.<br>
-<br>
- You can limit the display from above a little with the command, where<br>
-"column" is the name of the column for which you wish to restrict information:<br>
-<br>
-mysql> select * from table where (column = "some info");<br>
-<br>
- -- or the reverse of this<br>
-<br>
-mysql> select * from table where (column != "some info");<br>
-<br>
- Let's take our example from the introduction, and assume you need to change<br>
-the word "verified" to "approved" in the resolution field. We know from the<br>
-above information that the resolution is likely to be stored in the "bugs"<br>
-table. Note we'll need to change a little perl code as well as this database<br>
-change, but I won't plunge into that in this document. Let's verify the<br>
-information is stored in the "bugs" table:<br>
-<br>
-mysql> show columns from bugs<br>
-<br>
- (exceedingly long output truncated here)<br>
-| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br>
-<br>
- Sorry about that long line. We see from this that the "bug status" column is<br>
-an "enum field", which is a MySQL peculiarity where a string type field can<br>
-only have certain types of entries. While I think this is very cool, it's not<br>
-standard SQL. Anyway, we need to add the possible enum field entry<br>
-'APPROVED' by altering the "bugs" table.<br>
-<br>
-mysql> ALTER table bugs CHANGE bug_status bug_status<br>
- -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br>
- -> "VERIFIED", "APPROVED", "CLOSED") not null;<br>
-<br>
- (note we can take three lines or more -- whatever you put in before the<br>
-semicolon is evaluated as a single expression)<br>
-<br>
-Now if you do this:<br>
-<br>
-mysql> show columns from bugs;<br>
-<br>
- you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
-available! Cool thing, too, is that this is reflected on your query page as<br>
-well -- you can query by the new status. But how's it fit into the existing<br>
-scheme of things?<br>
- Looks like you need to go back and look for instances of the word "verified"<br>
-in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
-"approved" and you're in business (make sure that's a case-insensitive search).<br>
-Although you can query by the enum field, you can't give something a status<br>
-of "APPROVED" until you make the perl changes. Note that this change I<br>
-mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
-this. But you need to know this stuff anyway, right?<br>
- </P
-></DIV
+>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
+ Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
+ distribute verbatim copies of this license document, but changing it is
+ not allowed.</P
+></BLOCKQUOTE
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="gfdl-0"
+></A
+>0. PREAMBLE</H1
+><P
+>The purpose of this License is to make a manual, textbook, or other
+ written document "free" in the sense of freedom: to assure everyone the
+ effective freedom to copy and redistribute it, with or without modifying
+ it, either commercially or noncommercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for their
+ work, while not being considered responsible for modifications made by
+ others.</P
+><P
+>This License is a kind of "copyleft", which means that derivative
+ works of the document must themselves be free in the same sense. It
+ complements the GNU General Public License, which is a copyleft license
+ designed for free software.</P
+><P
+>We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a free
+ program should come with manuals providing the same freedoms that the
+ software does. But this License is not limited to software manuals; it
+ can be used for any textual work, regardless of subject matter or whether
+ it is published as a printed book. We recommend this License principally
+ for works whose purpose is instruction or reference.</P
></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="gfdl-1"
+></A
+>1. APPLICABILITY AND DEFINITIONS</H1
+><P
+>This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be distributed under
+ the terms of this License. The "Document", below, refers to any such
+ manual or work. Any member of the public is a licensee, and is addressed
+ as "you".</P
+><P
+>A "Modified Version" of the Document means any work containing the
+ Document or a portion of it, either copied verbatim, or with
+ modifications and/or translated into another language.</P
+><P
+>A "Secondary Section" is a named appendix or a front-matter section
+ of the Document that deals exclusively with the relationship of the
+ publishers or authors of the Document to the Document's overall subject
+ (or to related matters) and contains nothing that could fall directly
+ within that overall subject. (For example, if the Document is in part a
+ textbook of mathematics, a Secondary Section may not explain any
+ mathematics.) The relationship could be a matter of historical connection
+ with the subject or with related matters, or of legal, commercial,
+ philosophical, ethical or political position regarding them.</P
+><P
+>The "Invariant Sections" are certain Secondary Sections whose
+ titles are designated, as being those of Invariant Sections, in the
+ notice that says that the Document is released under this License.</P
+><P
+>The "Cover Texts" are certain short passages of text that are
+ listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
+ that the Document is released under this License.</P
+><P
+>A "Transparent" copy of the Document means a machine-readable copy,
+ represented in a format whose specification is available to the general
+ public, whose contents can be viewed and edited directly and
+ straightforwardly with generic text editors or (for images composed of
+ pixels) generic paint programs or (for drawings) some widely available
+ drawing editor, and that is suitable for input to text formatters or for
+ automatic translation to a variety of formats suitable for input to text
+ formatters. A copy made in an otherwise Transparent file format whose
+ markup has been designed to thwart or discourage subsequent modification
+ by readers is not Transparent. A copy that is not "Transparent" is called
+ "Opaque".</P
+><P
+>Examples of suitable formats for Transparent copies include plain
+ ASCII without markup, Texinfo input format, LaTeX input format, SGML or
+ XML using a publicly available DTD, and standard-conforming simple HTML
+ designed for human modification. Opaque formats include PostScript, PDF,
+ proprietary formats that can be read and edited only by proprietary word
+ processors, SGML or XML for which the DTD and/or processing tools are not
+ generally available, and the machine-generated HTML produced by some word
+ processors for output purposes only.</P
+><P
+>The "Title Page" means, for a printed book, the title page itself,
+ plus such following pages as are needed to hold, legibly, the material
+ this License requires to appear in the title page. For works in formats
+ which do not have any title page as such, "Title Page" means the text
+ near the most prominent appearance of the work's title, preceding the
+ beginning of the body of the text.</P
></DIV
+><DIV
+CLASS="section"
+><HR><H1
+CLASS="section"
+><A
+NAME="gfdl-2"
+></A
+>2. VERBATIM COPYING</H1
+><P
+>You may copy and distribute the Document in any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License applies to
+ the Document are reproduced in all copies, and that you add no other
+ conditions whatsoever to those of this License. You may not use technical
+ measures to obstruct or control the reading or further copying of the
+ copies you make or distribute. However, you may accept compensation in
+ exchange for copies. If you distribute a large enough number of copies
+ you must also follow the conditions in section 3.</P
+><P
+>You may also lend copies, under the same conditions stated above,
+ and you may publicly display copies.</P
></DIV
><DIV
-CLASS="appendix"
+CLASS="section"
><HR><H1
+CLASS="section"
><A
-NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
+NAME="gfdl-3"
+></A
+>3. COPYING IN QUANTITY</H1
><P
->Are you looking for a way to put your Bugzilla into overdrive? Catch
- some of the niftiest tricks here in this section.</P
+>If you publish printed copies of the Document numbering more than
+ 100, and the Document's license notice requires Cover Texts, you must
+ enclose the copies in covers that carry, clearly and legibly, all these
+ Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
+ on the back cover. Both covers must also clearly and legibly identify you
+ as the publisher of these copies. The front cover must present the full
+ title with all words of the title equally prominent and visible. You may
+ add other material on the covers in addition. Copying with changes
+ limited to the covers, as long as they preserve the title of the Document
+ and satisfy these conditions, can be treated as verbatim copying in other
+ respects.</P
+><P
+>If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit reasonably)
+ on the actual cover, and continue the rest onto adjacent pages.</P
+><P
+>If you publish or distribute Opaque copies of the Document
+ numbering more than 100, you must either include a machine-readable
+ Transparent copy along with each Opaque copy, or state in or with each
+ Opaque copy a publicly-accessible computer-network location containing a
+ complete Transparent copy of the Document, free of added material, which
+ the general network-using public has access to download anonymously at no
+ charge using public-standard network protocols. If you use the latter
+ option, you must take reasonably prudent steps, when you begin
+ distribution of Opaque copies in quantity, to ensure that this
+ Transparent copy will remain thus accessible at the stated location until
+ at least one year after the last time you distribute an Opaque copy
+ (directly or through your agents or retailers) of that edition to the
+ public.</P
+><P
+>It is requested, but not required, that you contact the authors of
+ the Document well before redistributing any large number of copies, to
+ give them a chance to provide you with an updated version of the
+ Document.</P
+></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="rewrite">C.1. Apache
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- magic</H1
+NAME="gfdl-4"
+></A
+>4. MODIFICATIONS</H1
><P
->Apache's
- <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
- module lets you do some truly amazing things with URL rewriting. Here are
- a couple of examples of what you can do.</P
+>You may copy and distribute a Modified Version of the Document
+ under the conditions of sections 2 and 3 above, provided that you release
+ the Modified Version under precisely this License, with the Modified
+ Version filling the role of the Document, thus licensing distribution and
+ modification of the Modified Version to whoever possesses a copy of it.
+ In addition, you must do these things in the Modified Version:</P
><P
></P
><OL
-TYPE="1"
+TYPE="A"
><LI
><P
->Make it so if someone types
- <TT
-CLASS="computeroutput"
->http://www.foo.com/12345</TT
->
-
- , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
- setting up your VirtualHost section for Bugzilla with a rule like
- this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-> <VirtualHost 12.34.56.78>
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-</VirtualHost>
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
+>Use in the Title Page (and on the covers, if any) a title
+ distinct from that of the Document, and from those of previous
+ versions (which should, if there were any, be listed in the History
+ section of the Document). You may use the same title as a previous
+ version if the original publisher of that version gives
+ permission.</P
+></LI
+><LI
+><P
+>List on the Title Page, as authors, one or more persons or
+ entities responsible for authorship of the modifications in the
+ Modified Version, together with at least five of the principal
+ authors of the Document (all of its principal authors, if it has less
+ than five).</P
+></LI
+><LI
+><P
+>State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.</P
+></LI
+><LI
+><P
+>Preserve all the copyright notices of the Document.</P
+></LI
+><LI
+><P
+>Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.</P
+></LI
+><LI
+><P
+>Include, immediately after the copyright notices, a license
+ notice giving the public permission to use the Modified Version under
+ the terms of this License, in the form shown in the Addendum
+ below.</P
+></LI
+><LI
+><P
+>Preserve in that license notice the full lists of Invariant
+ Sections and required Cover Texts given in the Document's license
+ notice.</P
+></LI
+><LI
+><P
+>Include an unaltered copy of this License.</P
+></LI
+><LI
+><P
+>Preserve the section entitled "History", and its title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.</P
+></LI
+><LI
+><P
+>Preserve the network location, if any, given in the Document
+ for public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions it
+ was based on. These may be placed in the "History" section. You may
+ omit a network location for a work that was published at least four
+ years before the Document itself, or if the original publisher of the
+ version it refers to gives permission.</P
></LI
><LI
><P
->There are many, many more things you can do with mod_rewrite.
- Please refer to the mod_rewrite documentation at
- <A
-HREF="http://www.apache.org"
-TARGET="_top"
->http://www.apache.org</A
->.
- </P
+>In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements and/or
+ dedications given therein.</P
></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><HR><H1
-CLASS="section"
-><A
-NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
+><LI
><P
->There are a suite of Unix utilities for querying Bugzilla from the
- command line. They live in the
- <TT
-CLASS="filename"
->contrib/cmdline</TT
->
- directory. However, they
- have not yet been updated to work with 2.16 (post-templatisation.).
- There are three files - <TT
-CLASS="filename"
->query.conf</TT
->,
- <TT
-CLASS="filename"
->buglist</TT
-> and <TT
-CLASS="filename"
->bugs</TT
->.</P
+>Preserve all the Invariant Sections of the Document, unaltered
+ in their text and in their titles. Section numbers or the equivalent
+ are not considered part of the section titles.</P
+></LI
+><LI
><P
-><TT
-CLASS="filename"
->query.conf</TT
->
- contains the mapping from options to field
- names and comparison types. Quoted option names are "grepped" for, so it
- should be easy to edit this file. Comments (#) have no effect; you must
- make sure these lines do not contain any quoted "option".</P
+>Delete any section entitled "Endorsements". Such a section may
+ not be included in the Modified Version.</P
+></LI
+><LI
><P
-><TT
-CLASS="filename"
->buglist</TT
->
- is a shell script which submits a Bugzilla query and writes
- the resulting HTML page to stdout. It supports both short options, (such
- as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
- "--reporter=bar"). If the first character of an option is not "-", it is
- treated as if it were prefixed with "--default=".</P
+>Do not retitle any existing section as "Endorsements" or to
+ conflict in title with any Invariant Section.</P
+></LI
+></OL
><P
->The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the "Change Columns" option when you list bugs in
- buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
- in your cookies file to see your current COLUMNLIST setting.</P
+>If the Modified Version includes new front-matter sections or
+ appendices that qualify as Secondary Sections and contain no material
+ copied from the Document, you may at your option designate some or all of
+ these sections as invariant. To do this, add their titles to the list of
+ Invariant Sections in the Modified Version's license notice. These titles
+ must be distinct from any other section titles.</P
><P
-><TT
-CLASS="filename"
->bugs</TT
-> is a simple shell script which calls
- <TT
-CLASS="filename"
->buglist</TT
-> and extracts the
- bug numbers from the output. Adding the prefix
- "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
- a working link if any bugs are found. Counting bugs is easy. Pipe the
- results through
- <B
-CLASS="command"
->sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
->
- </P
+>You may add a section entitled "Endorsements", provided it contains
+ nothing but endorsements of your Modified Version by various parties--for
+ example, statements of peer review or that the text has been approved by
+ an organization as the authoritative definition of a standard.</P
><P
->Akkana Peck says she has good results piping
- <TT
-CLASS="filename"
->buglist</TT
-> output through
- <B
-CLASS="command"
->w3m -T text/html -dump</B
->
- </P
-></DIV
+>You may add a passage of up to five words as a Front-Cover Text,
+ and a passage of up to 25 words as a Back-Cover Text, to the end of the
+ list of Cover Texts in the Modified Version. Only one passage of
+ Front-Cover Text and one of Back-Cover Text may be added by (or through
+ arrangements made by) any one entity. If the Document already includes a
+ cover text for the same cover, previously added by you or by arrangement
+ made by the same entity you are acting on behalf of, you may not add
+ another; but you may replace the old one, on explicit permission from the
+ previous publisher that added the old one.</P
+><P
+>The author(s) and publisher(s) of the Document do not by this
+ License give permission to use their names for publicity for or to assert
+ or imply endorsement of any Modified Version.</P
></DIV
><DIV
-CLASS="appendix"
+CLASS="section"
><HR><H1
+CLASS="section"
><A
-NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
+NAME="gfdl-5"
+></A
+>5. COMBINING DOCUMENTS</H1
><P
->I created this section to answer questions about Bugzilla competitors
- and variants, then found a wonderful site which covers an awful lot of what
- I wanted to discuss. Rather than quote it in its entirety, I'll simply
- refer you here:
- <A
-HREF="http://linas.org/linux/pm.html"
-TARGET="_top"
-> http://linas.org/linux/pm.html</A
->
- </P
+>You may combine the Document with other documents released under
+ this License, under the terms defined in section 4 above for modified
+ versions, provided that you include in the combination all of the
+ Invariant Sections of all of the original documents, unmodified, and list
+ them all as Invariant Sections of your combined work in its license
+ notice.</P
+><P
+>The combined work need only contain one copy of this License, and
+ multiple identical Invariant Sections may be replaced with a single copy.
+ If there are multiple Invariant Sections with the same name but different
+ contents, make the title of each such section unique by adding at the end
+ of it, in parentheses, the name of the original author or publisher of
+ that section if known, or else a unique number. Make the same adjustment
+ to the section titles in the list of Invariant Sections in the license
+ notice of the combined work.</P
+><P
+>In the combination, you must combine any sections entitled
+ "History" in the various original documents, forming one section entitled
+ "History"; likewise combine any sections entitled "Acknowledgements", and
+ any sections entitled "Dedications". You must delete all sections
+ entitled "Endorsements."</P
+></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="rhbugzilla">D.1. Red Hat Bugzilla</H1
+NAME="gfdl-6"
+></A
+>6. COLLECTIONS OF DOCUMENTS</H1
><P
->Red Hat Bugzilla is a fork of Bugzilla 2.8.
- One of its major benefits is the ability
- to work with Oracle, MySQL, and PostGreSQL databases serving as the
- back-end, instead of just MySQL. Dave Lawrence of Red Hat is
- active in the Bugzilla community, and we hope to see a reunification
- of the fork before too long.</P
+>You may make a collection consisting of the Document and other
+ documents released under this License, and replace the individual copies
+ of this License in the various documents with a single copy that is
+ included in the collection, provided that you follow the rules of this
+ License for verbatim copying of each of the documents in all other
+ respects.</P
><P
->URL:
- <A
-HREF="http://bugzilla.redhat.com/bugzilla/"
-TARGET="_top"
-> http://bugzilla.redhat.com/bugzilla/</A
->
- </P
+>You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you insert a copy
+ of this License into the extracted document, and follow this License in
+ all other respects regarding verbatim copying of that document.</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
+NAME="gfdl-7"
+></A
+>7. AGGREGATION WITH INDEPENDENT WORKS</H1
><P
->Fenris was a fork from Bugzilla made by Loki Games; when
- Loki went into receivership, it died. While Loki's other code lives on,
- its custodians recommend Bugzilla for future bug-tracker deployments.
- </P
+>A compilation of the Document or its derivatives with other
+ separate and independent documents or works, in or on a volume of a
+ storage or distribution medium, does not as a whole count as a Modified
+ Version of the Document, provided no compilation copyright is claimed for
+ the compilation. Such a compilation is called an "aggregate", and this
+ License does not apply to the other self-contained works thus compiled
+ with the Document, on account of their being thus compiled, if they are
+ not themselves derivative works of the Document.</P
+><P
+>If the Cover Text requirement of section 3 is applicable to these
+ copies of the Document, then if the Document is less than one quarter of
+ the entire aggregate, the Document's Cover Texts may be placed on covers
+ that surround only the Document within the aggregate. Otherwise they must
+ appear on covers around the whole aggregate.</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="variant-issuezilla">D.3. Issuezilla</H1
+NAME="gfdl-8"
+></A
+>8. TRANSLATION</H1
><P
->Issuezilla was another fork from Bugzilla, made by collab.net and
- hosted at tigris.org. It is also dead; the primary focus of bug-tracking
- at tigris.org is their Java-based bug-tracker,
- <A
-HREF="#variant-scarab"
->Scarab</A
->.</P
+>Translation is considered a kind of modification, so you may
+ distribute translations of the Document under the terms of section 4.
+ Replacing Invariant Sections with translations requires special
+ permission from their copyright holders, but you may include translations
+ of some or all Invariant Sections in addition to the original versions of
+ these Invariant Sections. You may include a translation of this License
+ provided that you also include the original English version of this
+ License. In case of a disagreement between the translation and the
+ original English version of this License, the original English version
+ will prevail.</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="variant-scarab">D.4. Scarab</H1
-><P
->Scarab is a new open source bug-tracking system built using Java
- Serlet technology. It is currently at version 1.0 beta 8.</P
+NAME="gfdl-9"
+></A
+>9. TERMINATION</H1
><P
->URL:
- <A
-HREF="http://scarab.tigris.org/"
-TARGET="_top"
->http://scarab.tigris.org</A
->
- </P
+>You may not copy, modify, sublicense, or distribute the Document
+ except as expressly provided for under this License. Any other attempt to
+ copy, modify, sublicense or distribute the Document is void, and will
+ automatically terminate your rights under this License. However, parties
+ who have received copies, or rights, from you under this License will not
+ have their licenses terminated so long as such parties remain in full
+ compliance.</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="variant-perforce">D.5. Perforce SCM</H1
-><P
->Although Perforce isn't really a bug tracker, it can be used as
- such through the <SPAN
-CLASS="QUOTE"
->"jobs"</SPAN
->
- functionality.</P
+NAME="gfdl-10"
+></A
+>10. FUTURE REVISIONS OF THIS LICENSE</H1
><P
->URL:
+>The Free Software Foundation may publish new, revised versions of
+ the GNU Free Documentation License from time to time. Such new versions
+ will be similar in spirit to the present version, but may differ in
+ detail to address new problems or concerns. See
<A
-HREF="http://www.perforce.com/perforce/technotes/note052.html"
+HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
-> http://www.perforce.com/perforce/technotes/note052.html
- </A
+> http://www.gnu.org/copyleft/</A
>
- </P
+
+ .</P
+><P
+>Each version of the License is given a distinguishing version
+ number. If the Document specifies that a particular numbered version of
+ this License "or any later version" applies to it, you have the option of
+ following the terms and conditions either of that specified version or of
+ any later version that has been published (not as a draft) by the Free
+ Software Foundation. If the Document does not specify a version number of
+ this License, you may choose any version ever published (not as a draft)
+ by the Free Software Foundation.</P
></DIV
><DIV
CLASS="section"
><HR><H1
CLASS="section"
><A
-NAME="variant-sourceforge">D.6. SourceForge</H1
+NAME="gfdl-howto"
+></A
+>How to use this License for your documents</H1
><P
->SourceForge is a way of coordinating geographically
- distributed free software and open source projects over the Internet.
- It has a built-in bug tracker, but it's not highly thought of.</P
+>To use this License in a document you have written, include a copy
+ of the License in the document and put the following copyright and
+ license notices just after the title page:</P
+><A
+NAME="AEN2367"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
><P
->URL:
- <A
-HREF="http://www.sourceforge.net"
-TARGET="_top"
-> http://www.sourceforge.net</A
->
- </P
+>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
+ distribute and/or modify this document under the terms of the GNU Free
+ Documentation License, Version 1.1 or any later version published by
+ the Free Software Foundation; with the Invariant Sections being LIST
+ THEIR TITLES, with the Front-Cover Texts being LIST, and with the
+ Back-Cover Texts being LIST. A copy of the license is included in the
+ section entitled "GNU Free Documentation License".</P
+></BLOCKQUOTE
+><P
+>If you have no Invariant Sections, write "with no Invariant
+ Sections" instead of saying which ones are invariant. If you have no
+ Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
+ Texts being LIST"; likewise for Back-Cover Texts.</P
+><P
+>If your document contains nontrivial examples of program code, we
+ recommend releasing these examples in parallel under your choice of free
+ software license, such as the GNU General Public License, to permit their
+ use in free software.</P
></DIV
></DIV
><DIV
CLASS="GLOSSARY"
><H1
><A
-NAME="glossary">Glossary</H1
+NAME="glossary"
+></A
+>Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2183">0-9, high ascii</H1
+NAME="AEN2372"
+></A
+>0-9, high ascii</H1
><DL
><DT
><B
@@ -12034,7 +13414,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-a">A</H1
+NAME="gloss-a"
+></A
+>A</H1
><DL
><DT
><B
@@ -12064,6 +13446,110 @@ CLASS="acronym"
>
world-wide-web server.</P
+><P
+></P
+><DIV
+CLASS="variablelist"
+><P
+><B
+>Useful Directives when configuring Bugzilla</B
+></P
+><DL
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
+TARGET="_top"
+>AddHandler</A
+></TT
+></DT
+><DD
+><P
+>Tell Apache that it's OK to run CGI scripts.</P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
+TARGET="_top"
+>AllowOverride</A
+></TT
+>, <TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
+TARGET="_top"
+>Options</A
+></TT
+></DT
+><DD
+><P
+>These directives are used to tell Apache many things about
+ the directory they apply to. For Bugzilla's purposes, we need
+ them to allow script execution and <TT
+CLASS="filename"
+>.htaccess</TT
+>
+ overrides.
+ </P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
+TARGET="_top"
+>DirectoryIndex</A
+></TT
+></DT
+><DD
+><P
+>Used to tell Apache what files are indexes. If you can
+ not add <TT
+CLASS="filename"
+>index.cgi</TT
+> to the list of valid files,
+ you'll need to set <TT
+CLASS="computeroutput"
+>$index_html</TT
+> to
+ 1 in <TT
+CLASS="filename"
+>localconfig</TT
+> so
+ <B
+CLASS="command"
+>./checksetup.pl</B
+> will create an
+ <TT
+CLASS="filename"
+>index.html</TT
+> that redirects to
+ <TT
+CLASS="filename"
+>index.cgi</TT
+>.
+ </P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
+TARGET="_top"
+>ScriptInterpreterSource</A
+></TT
+></DT
+><DD
+><P
+>Used when running Apache on windows so the shebang line
+ doesn't have to be changed in every Bugzilla script.
+ </P
+></DD
+></DL
+></DIV
></DD
></DL
></DIV
@@ -12072,7 +13558,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-b">B</H1
+NAME="gloss-b"
+></A
+>B</H1
><DL
><DT
><B
@@ -12111,6 +13599,9 @@ CLASS="QUOTE"
"Find" box.</P
></DD
><DT
+><A
+NAME="gloss-bugzilla"
+></A
><B
>Bugzilla</B
></DT
@@ -12126,11 +13617,35 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-c"></H1
+NAME="gloss-c"
+></A
+>C</H1
><DL
><DT
><A
-NAME="gloss-component"><B
+NAME="gloss-cgi"
+></A
+><B
+>Common Gateway Interface</B
+></DT
+> (CGI)<DD
+><P
+><SPAN
+CLASS="acronym"
+>CGI</SPAN
+> is an acronym for Common Gateway Interface.
+ This is a standard for interfacing an external application with a web
+ server. Bugzilla is an example of a <SPAN
+CLASS="acronym"
+>CGI</SPAN
+> application.
+ </P
+></DD
+><DT
+><A
+NAME="gloss-component"
+></A
+><B
>Component</B
></DT
><DD
@@ -12142,7 +13657,9 @@ NAME="gloss-component"><B
></DD
><DT
><A
-NAME="gloss-cpan"><B
+NAME="gloss-cpan"
+></A
+><B
> <SPAN
CLASS="acronym"
>CPAN</SPAN
@@ -12176,7 +13693,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-d">D</H1
+NAME="gloss-d"
+></A
+>D</H1
><DL
><DT
><B
@@ -12205,7 +13724,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-g"></H1
+NAME="gloss-g"
+></A
+>G</H1
><DL
><DT
><B
@@ -12240,24 +13761,83 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-m">M</H1
+NAME="gloss-m"
+></A
+>M</H1
><DL
><DT
+><A
+NAME="gloss-mta"
+></A
+><B
+>Message Transport Agent</B
+></DT
+> (MTA)<DD
+><P
+>A Message Transport Agent is used to control the flow of email
+ on a system. Many unix based systems use
+ <A
+HREF="http://www.sendmail.org"
+TARGET="_top"
+>sendmail</A
+> which is what
+ Bugzilla expects to find by default at <TT
+CLASS="filename"
+>/usr/sbin/sendmail</TT
+>.
+ Many other MTA's will work, but they all require that the
+ <TT
+CLASS="option"
+>sendmailnow</TT
+> param be set to <TT
+CLASS="literal"
+>on</TT
+>.
+ </P
+></DD
+><DT
+><A
+NAME="gloss-mysql"
+></A
><B
->mysqld</B
+>MySQL</B
></DT
><DD
><P
->mysqld is the name of the
- <I
+>MySQL is currently the required
+ <A
+HREF="#gloss-rdbms"
+><I
CLASS="glossterm"
->daemon</I
->
-
- for the MySQL database. In general, it is invoked automatically
- through the use of the System V init scripts on GNU/Linux and
- AT&T System V-based systems, such as Solaris and HP/UX, or
- through the RC scripts on BSD-based systems.</P
+>RDBMS</I
+></A
+> for Bugzilla. MySQL
+ can be downloaded from <A
+HREF="http://www.mysql.com"
+TARGET="_top"
+>http://www.mysql.com</A
+>. While you
+ should familiarize yourself with all of the documentation, some high
+ points are:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
+TARGET="_top"
+>MySQL
+ Privilege System</A
+> - Much more detailed information about
+ the suggestions in <A
+HREF="#security-mysql"
+>Section 5.6.2</A
+>.
+ </P
+></LI
+></UL
></DD
></DL
></DIV
@@ -12266,7 +13846,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-p">P</H1
+NAME="gloss-p"
+></A
+>P</H1
><DL
><DT
><B
@@ -12304,7 +13886,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-q">Q</H1
+NAME="gloss-q"
+></A
+>Q</H1
><DL
><DT
><B
@@ -12347,7 +13931,33 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-s">S</H1
+NAME="gloss-r"
+></A
+>R</H1
+><DL
+><DT
+><A
+NAME="gloss-rdbms"
+></A
+><B
+>Relational DataBase Managment System</B
+></DT
+> (RDBMS)<DD
+><P
+>A relational database management system is a database system
+ that stores information in tables that are related to each other.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="glossdiv"
+><H1
+CLASS="glossdiv"
+><A
+NAME="gloss-s"
+></A
+>S</H1
><DL
><DT
><B
@@ -12424,11 +14034,15 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-t">T</H1
+NAME="gloss-t"
+></A
+>T</H1
><DL
><DT
><A
-NAME="gloss-target-milestone"><B
+NAME="gloss-target-milestone"
+></A
+><B
>Target Milestone</B
></DT
><DD
@@ -12446,6 +14060,21 @@ CLASS="QUOTE"
giving you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.</P
></DD
+><DT
+><A
+NAME="gloss-tcl"
+></A
+><B
+>Tool Command Language</B
+></DT
+> (TCL)<DD
+><P
+>TCL is an open source scripting language available for Windows,
+ Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
+ never released. The first release of Bugzilla was 2.0, which was when
+ it was ported to perl.
+ </P
+></DD
></DL
></DIV
><DIV
@@ -12453,18 +14082,76 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-z">Z</H1
+NAME="gloss-z"
+></A
+>Z</H1
><DL
><DT
><A
-NAME="zarro-boogs-found"><B
+NAME="gloss-zarro"
+></A
+><B
>Zarro Boogs Found</B
></DT
><DD
><P
->This is the cryptic response sent by Bugzilla when a query
- returned no results. It is just a goofy way of saying "Zero Bugs
- Found".</P
+>This is just a goofy way of saying that there were no bugs
+ found matching your query. When asked to explain this message,
+ Terry had the following to say:
+ </P
+><A
+NAME="AEN2566"
+></A
+><TABLE
+BORDER="0"
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="BLOCKQUOTE"
+><TR
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+> </TD
+><TD
+WIDTH="80%"
+VALIGN="TOP"
+><P
+>I've been asked to explain this ... way back when, when
+ Netscape released version 4.0 of its browser, we had a release
+ party. Naturally, there had been a big push to try and fix every
+ known bug before the release. Naturally, that hadn't actually
+ happened. (This is not unique to Netscape or to 4.0; the same thing
+ has happened with every software project I've ever seen.) Anyway,
+ at the release party, T-shirts were handed out that said something
+ like "Netscape 4.0: Zarro Boogs". Just like the software, the
+ T-shirt had no known bugs. Uh-huh.
+ </P
+><P
+>So, when you query for a list of bugs, and it gets no results,
+ you can think of this as a friendly reminder. Of *course* there are
+ bugs matching your query, they just aren't in the bugsystem yet...
+ </P
+></TD
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+> </TD
+></TR
+><TR
+><TD
+COLSPAN="2"
+ALIGN="RIGHT"
+VALIGN="TOP"
+>--<SPAN
+CLASS="attribution"
+>Terry Weissman</SPAN
+></TD
+><TD
+WIDTH="10%"
+> </TD
+></TR
+></TABLE
></DD
></DL
></DIV
diff --git a/docs/html/CVS/Entries b/docs/html/CVS/Entries
index 179e28393998737f981bb58595640eb55e3b2a0d..02dae14ae274c65189c796644440a493ac8740c3 100644
--- a/docs/html/CVS/Entries
+++ b/docs/html/CVS/Entries
@@ -1,48 +1,61 @@
-/Bugzilla-Guide.html/1.15.2.1/Thu Jul 25 21:03:10 2002//TBUGZILLA-2_16_2
-/about.html/1.7.2.1/Sat May 11 17:59:49 2002//TBUGZILLA-2_16_2
-/aboutthisguide.html/1.9/Wed May 8 21:16:36 2002//TBUGZILLA-2_16_2
-/administration.html/1.7.2.5/Thu Jul 25 20:48:28 2002//TBUGZILLA-2_16_2
-/cmdline.html/1.7.2.3/Sat May 25 15:36:47 2002//TBUGZILLA-2_16_2
-/conventions.html/1.8.2.4/Thu Jul 25 20:48:29 2002//TBUGZILLA-2_16_2
-/copyright.html/1.9.2.3/Thu Jul 25 20:48:29 2002//TBUGZILLA-2_16_2
-/credits.html/1.8.2.1/Sat May 11 17:59:52 2002//TBUGZILLA-2_16_2
-/cust-templates.html/1.1.2.5/Thu Jul 25 21:03:13 2002//TBUGZILLA-2_16_2
-/database.html/1.6.2.3/Sat May 25 15:36:47 2002//TBUGZILLA-2_16_2
-/dbdoc.html/1.9.2.5/Thu Jul 25 20:48:30 2002//TBUGZILLA-2_16_2
-/dbschema.html/1.7.2.1/Sun May 12 16:15:16 2002//TBUGZILLA-2_16_2
-/disclaimer.html/1.7.2.1/Sat May 11 17:59:54 2002//TBUGZILLA-2_16_2
-/extraconfig.html/1.1.2.4/Thu Jul 25 20:48:30 2002//TBUGZILLA-2_16_2
-/faq.html/1.10.2.5/Thu Jul 25 20:48:30 2002//TBUGZILLA-2_16_2
-/glossary.html/1.11.2.5/Thu Jul 25 20:48:32 2002//TBUGZILLA-2_16_2
-/groups.html/1.1.2.2/Sat May 25 15:36:51 2002//TBUGZILLA-2_16_2
-/hintsandtips.html/1.1.2.3/Sat Jul 13 07:54:03 2002//TBUGZILLA-2_16_2
-/how.html/1.10.2.4/Thu Jul 25 20:48:33 2002//TBUGZILLA-2_16_2
-/index.html/1.11.2.5/Thu Jul 25 20:48:33 2002//TBUGZILLA-2_16_2
-/installation.html/1.10.2.5/Thu Jul 25 20:48:33 2002//TBUGZILLA-2_16_2
-/integration.html/1.7.2.3/Sat May 25 15:36:54 2002//TBUGZILLA-2_16_2
-/introduction.html/1.1.2.1/Sun May 12 16:17:40 2002//TBUGZILLA-2_16_2
-/newversions.html/1.8.2.1/Sat May 11 18:00:00 2002//TBUGZILLA-2_16_2
-/osx.html/1.3.2.3/Sat May 25 15:36:54 2002//TBUGZILLA-2_16_2
-/parameters.html/1.1.2.1/Sat May 25 15:39:13 2002//TBUGZILLA-2_16_2
-/patches.html/1.10.2.3/Sat May 25 15:36:54 2002//TBUGZILLA-2_16_2
-/programadmin.html/1.10.2.3/Sat May 25 15:36:55 2002//TBUGZILLA-2_16_2
-/rewrite.html/1.3.2.2/Sun May 12 16:15:22 2002//TBUGZILLA-2_16_2
-/rhbugzilla.html/1.8.2.3/Thu Jul 25 20:48:34 2002//TBUGZILLA-2_16_2
-/security.html/1.9.2.3/Sat May 25 15:36:55 2002//TBUGZILLA-2_16_2
-/stepbystep.html/1.8.2.5/Sat Jul 13 07:54:05 2002//TBUGZILLA-2_16_2
-/troubleshooting.html/1.1.2.4/Thu Jul 25 20:48:35 2002//TBUGZILLA-2_16_2
-/upgrading.html/1.1.2.2/Sat Jul 13 07:54:06 2002//TBUGZILLA-2_16_2
-/useradmin.html/1.8.2.2/Sat May 25 15:36:57 2002//TBUGZILLA-2_16_2
-/userpreferences.html/1.1.2.2/Sat May 25 15:36:57 2002//TBUGZILLA-2_16_2
-/using.html/1.8.2.4/Sat Jul 13 07:54:06 2002//TBUGZILLA-2_16_2
-/variant-fenris.html/1.3.2.2/Sun May 12 16:15:24 2002//TBUGZILLA-2_16_2
-/variant-issuezilla.html/1.3.2.2/Sun May 12 16:15:24 2002//TBUGZILLA-2_16_2
-/variant-perforce.html/1.3.2.3/Sat May 25 15:36:58 2002//TBUGZILLA-2_16_2
-/variant-scarab.html/1.3.2.3/Thu Jul 25 20:48:35 2002//TBUGZILLA-2_16_2
-/variant-sourceforge.html/1.3.2.2/Sun May 12 16:15:25 2002//TBUGZILLA-2_16_2
-/variants.html/1.8.2.2/Sun May 12 16:15:25 2002//TBUGZILLA-2_16_2
-/voting.html/1.1.2.2/Sat May 25 15:36:58 2002//TBUGZILLA-2_16_2
-/whatis.html/1.8.2.1/Sat May 11 18:00:07 2002//TBUGZILLA-2_16_2
-/why.html/1.7.2.2/Thu Jul 25 20:48:35 2002//TBUGZILLA-2_16_2
-/win32.html/1.7.2.5/Thu Jul 25 20:48:36 2002//TBUGZILLA-2_16_2
+/Bugzilla-Guide.html/1.15.2.6/Wed Apr 23 02:34:09 2003//TBUGZILLA-2_16_3
+/about.html/1.7.2.3/Sun Feb 16 15:41:20 2003//TBUGZILLA-2_16_3
+/aboutthisguide.html/1.9/Wed May 8 21:16:36 2002//TBUGZILLA-2_16_3
+/administration.html/1.7.2.8/Wed Apr 23 02:34:19 2003//TBUGZILLA-2_16_3
+/cmdline.html/1.7.2.5/Sun Feb 16 15:41:20 2003//TBUGZILLA-2_16_3
+/conventions.html/1.8.2.7/Wed Apr 23 02:34:19 2003//TBUGZILLA-2_16_3
+/copyright.html/1.9.2.6/Wed Apr 23 02:34:20 2003//TBUGZILLA-2_16_3
+/credits.html/1.8.2.4/Wed Apr 23 02:34:20 2003//TBUGZILLA-2_16_3
+/cust-templates.html/1.1.2.8/Wed Apr 23 02:34:20 2003//TBUGZILLA-2_16_3
+/database.html/1.6.2.5/Sun Feb 16 15:41:25 2003//TBUGZILLA-2_16_3
+/dbdoc.html/1.9.2.8/Wed Apr 23 02:34:21 2003//TBUGZILLA-2_16_3
+/dbschema.html/1.7.2.3/Sun Feb 16 15:41:26 2003//TBUGZILLA-2_16_3
+/disclaimer.html/1.7.2.3/Sun Feb 16 15:41:29 2003//TBUGZILLA-2_16_3
+/extraconfig.html/1.1.2.7/Wed Apr 23 02:34:21 2003//TBUGZILLA-2_16_3
+/faq.html/1.10.2.8/Wed Apr 23 02:34:21 2003//TBUGZILLA-2_16_3
+/gfdl-0.html/1.2.2.4/Wed Apr 23 02:34:22 2003//TBUGZILLA-2_16_3
+/gfdl-1.html/1.2.2.4/Wed Apr 23 02:34:22 2003//TBUGZILLA-2_16_3
+/gfdl-10.html/1.2.2.4/Wed Apr 23 02:34:22 2003//TBUGZILLA-2_16_3
+/gfdl-2.html/1.2.2.4/Wed Apr 23 02:34:23 2003//TBUGZILLA-2_16_3
+/gfdl-3.html/1.2.2.4/Wed Apr 23 02:34:23 2003//TBUGZILLA-2_16_3
+/gfdl-4.html/1.2.2.4/Wed Apr 23 02:34:23 2003//TBUGZILLA-2_16_3
+/gfdl-5.html/1.2.2.4/Wed Apr 23 02:34:23 2003//TBUGZILLA-2_16_3
+/gfdl-6.html/1.2.2.4/Wed Apr 23 02:34:23 2003//TBUGZILLA-2_16_3
+/gfdl-7.html/1.2.2.4/Wed Apr 23 02:34:24 2003//TBUGZILLA-2_16_3
+/gfdl-8.html/1.2.2.4/Wed Apr 23 02:34:25 2003//TBUGZILLA-2_16_3
+/gfdl-9.html/1.2.2.4/Wed Apr 23 02:34:25 2003//TBUGZILLA-2_16_3
+/gfdl-howto.html/1.3.2.4/Wed Apr 23 02:34:26 2003//TBUGZILLA-2_16_3
+/gfdl.html/1.11.2.4/Wed Apr 23 02:34:27 2003//TBUGZILLA-2_16_3
+/glossary.html/1.11.2.8/Wed Apr 23 02:34:27 2003//TBUGZILLA-2_16_3
+/groups.html/1.1.2.4/Sun Feb 16 15:41:37 2003//TBUGZILLA-2_16_3
+/hintsandtips.html/1.1.2.6/Wed Apr 23 02:34:27 2003//TBUGZILLA-2_16_3
+/how.html/1.10.2.6/Sun Feb 16 15:41:39 2003//TBUGZILLA-2_16_3
+/index.html/1.11.2.8/Wed Apr 23 02:34:27 2003//TBUGZILLA-2_16_3
+/installation.html/1.10.2.8/Wed Apr 23 02:34:28 2003//TBUGZILLA-2_16_3
+/integration.html/1.7.2.5/Sun Feb 16 15:41:41 2003//TBUGZILLA-2_16_3
+/introduction.html/1.1.2.3/Sun Feb 16 15:41:45 2003//TBUGZILLA-2_16_3
+/newversions.html/1.8.2.4/Wed Apr 23 02:34:28 2003//TBUGZILLA-2_16_3
+/osx.html/1.3.2.6/Wed Apr 23 02:34:28 2003//TBUGZILLA-2_16_3
+/parameters.html/1.1.2.3/Sun Feb 16 15:41:47 2003//TBUGZILLA-2_16_3
+/patches.html/1.10.2.5/Sun Feb 16 15:41:48 2003//TBUGZILLA-2_16_3
+/programadmin.html/1.10.2.5/Sun Feb 16 15:41:48 2003//TBUGZILLA-2_16_3
+/rewrite.html/1.3.2.4/Sun Feb 16 15:41:49 2003//TBUGZILLA-2_16_3
+/security.html/1.9.2.5/Sun Feb 16 15:41:52 2003//TBUGZILLA-2_16_3
+/stepbystep.html/1.8.2.9/Wed Apr 23 02:34:29 2003//TBUGZILLA-2_16_3
+/troubleshooting.html/1.1.2.7/Wed Apr 23 02:34:30 2003//TBUGZILLA-2_16_3
+/upgrading.html/1.1.2.4/Sun Feb 16 15:41:55 2003//TBUGZILLA-2_16_3
+/useradmin.html/1.8.2.4/Sun Feb 16 15:41:57 2003//TBUGZILLA-2_16_3
+/userpreferences.html/1.1.2.4/Sun Feb 16 15:41:59 2003//TBUGZILLA-2_16_3
+/using.html/1.8.2.7/Wed Apr 23 02:34:30 2003//TBUGZILLA-2_16_3
+/variant-fenris.html/1.3.2.5/Wed Apr 23 02:34:30 2003//TBUGZILLA-2_16_3
+/variant-issuezilla.html/1.3.2.5/Wed Apr 23 02:34:31 2003//TBUGZILLA-2_16_3
+/variant-perforce.html/1.3.2.6/Wed Apr 23 02:34:31 2003//TBUGZILLA-2_16_3
+/variant-redhat.html/1.1.2.1/Wed Apr 23 02:34:31 2003//TBUGZILLA-2_16_3
+/variant-scarab.html/1.3.2.6/Wed Apr 23 02:34:31 2003//TBUGZILLA-2_16_3
+/variant-sourceforge.html/1.3.2.5/Wed Apr 23 02:34:32 2003//TBUGZILLA-2_16_3
+/variants.html/1.8.2.5/Wed Apr 23 02:34:32 2003//TBUGZILLA-2_16_3
+/voting.html/1.1.2.4/Sun Feb 16 15:42:01 2003//TBUGZILLA-2_16_3
+/whatis.html/1.8.2.4/Wed Apr 23 02:34:32 2003//TBUGZILLA-2_16_3
+/why.html/1.7.2.4/Sun Feb 16 15:42:02 2003//TBUGZILLA-2_16_3
+/win32.html/1.7.2.8/Wed Apr 23 02:34:32 2003//TBUGZILLA-2_16_3
D
diff --git a/docs/html/CVS/Tag b/docs/html/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/docs/html/CVS/Tag
+++ b/docs/html/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/docs/html/about.html b/docs/html/about.html
index 7f1f7846759e3db4e5f236018cd07e1234db4288..1c1d0257fd5975c1ad2d9553fafc655524192653 100644
--- a/docs/html/about.html
+++ b/docs/html/about.html
@@ -7,10 +7,10 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Copyright Information"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
-NAME="about">Chapter 1. About This Guide</H1
+NAME="about"
+></A
+>Chapter 1. About This Guide</H1
><DIV
CLASS="TOC"
><DL
@@ -149,7 +151,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->The Bugzilla Guide</TD
+>The Bugzilla Guide - 2.16.3 Release</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/administration.html b/docs/html/administration.html
index c85d9acdda808b599ee564d118294de1acbcc005..06f61547b27f35b5526a90aeefdbbe1caac6733f 100644
--- a/docs/html/administration.html
+++ b/docs/html/administration.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Troubleshooting"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
-NAME="administration">Chapter 5. Administering Bugzilla</H1
+NAME="administration"
+></A
+>Chapter 5. Administering Bugzilla</H1
><DIV
CLASS="TOC"
><DL
@@ -145,6 +147,30 @@ HREF="groups.html"
HREF="security.html"
>Bugzilla Security</A
></DT
+><DD
+><DL
+><DT
+>5.6.1. <A
+HREF="security.html#security-networking"
+>TCP/IP Ports</A
+></DT
+><DT
+>5.6.2. <A
+HREF="security.html#security-mysql"
+>MySQL</A
+></DT
+><DT
+>5.6.3. <A
+HREF="security.html#security-daemon"
+>Daemon Accounts</A
+></DT
+><DT
+>5.6.4. <A
+HREF="security.html#security-access"
+>Web Server Access Controls</A
+></DT
+></DL
+></DD
><DT
>5.7. <A
HREF="cust-templates.html"
@@ -154,22 +180,22 @@ HREF="cust-templates.html"
><DL
><DT
>5.7.1. <A
-HREF="cust-templates.html#AEN1539"
+HREF="cust-templates.html#AEN1532"
>What to Edit</A
></DT
><DT
>5.7.2. <A
-HREF="cust-templates.html#AEN1558"
+HREF="cust-templates.html#AEN1551"
>How To Edit Templates</A
></DT
><DT
>5.7.3. <A
-HREF="cust-templates.html#AEN1568"
+HREF="cust-templates.html#AEN1561"
>Template Formats</A
></DT
><DT
>5.7.4. <A
-HREF="cust-templates.html#AEN1581"
+HREF="cust-templates.html#AEN1574"
>Particular Templates</A
></DT
></DL
diff --git a/docs/html/cmdline.html b/docs/html/cmdline.html
index a3825c25aacaddf30c98a16b6ca59a979a2f2b55..6705ac766c80e4a1c395f7d7c4fae2409f2c4c7f 100644
--- a/docs/html/cmdline.html
+++ b/docs/html/cmdline.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
@@ -40,7 +40,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -76,7 +76,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
+NAME="cmdline"
+></A
+>C.2. Command-line Bugzilla Queries</H1
><P
>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
diff --git a/docs/html/conventions.html b/docs/html/conventions.html
index 40ce3f8c42bb6723a84f6b2998bfcef45c3b9841..8c0d24699b991550cd49644af8acab035025b859 100644
--- a/docs/html/conventions.html
+++ b/docs/html/conventions.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="conventions">1.5. Document Conventions</H1
+NAME="conventions"
+></A
+>1.5. Document Conventions</H1
><P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><A
-NAME="AEN178"><P
+NAME="AEN109"
+></A
+><P
></P
><TABLE
BORDER="0"
@@ -101,7 +105,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Warnings</TD
+>Use caution</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
@@ -212,7 +216,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
->Information requiring special attention</TD
+>Warnings</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
@@ -377,6 +381,23 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
+>Term found in the glossary</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <A
+HREF="glossary.html#gloss-bugzilla"
+><I
+CLASS="glossterm"
+>Bugzilla</I
+></A
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
diff --git a/docs/html/copyright.html b/docs/html/copyright.html
index 8501809e61deca6c9e4bff1fbf3addf9806c6b88..f394b719f882fbaf05a3aef6b32495192bdd7430 100644
--- a/docs/html/copyright.html
+++ b/docs/html/copyright.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,9 +73,13 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="copyright">1.1. Copyright Information</H1
+NAME="copyright"
+></A
+>1.1. Copyright Information</H1
><A
-NAME="AEN31"><TABLE
+NAME="AEN32"
+></A
+><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
@@ -95,7 +99,10 @@ VALIGN="TOP"
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included below.
+ the license is included in <A
+HREF="gfdl.html"
+>Appendix E</A
+>.
</P
></TD
><TD
@@ -110,7 +117,7 @@ ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
->Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
+>Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN
></TD
><TD
WIDTH="10%"
@@ -122,477 +129,6 @@ WIDTH="10%"
copyright, or publishing this document in non-electronic form,
please contact The Bugzilla Team.
</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="gfdl">1.1.1. GNU Free Documentation License</H2
-><P
->Version 1.1, March 2000</P
-><A
-NAME="AEN38"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
- distribute verbatim copies of this license document, but changing it is
- not allowed.</P
-></BLOCKQUOTE
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-0">0. PREAMBLE</H3
-><P
->The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone the
- effective freedom to copy and redistribute it, with or without modifying
- it, either commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit for their
- work, while not being considered responsible for modifications made by
- others.</P
-><P
->This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft license
- designed for free software.</P
-><P
->We have designed this License in order to use it for manuals for
- free software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or whether
- it is published as a printed book. We recommend this License principally
- for works whose purpose is instruction or reference.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H3
-><P
->This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed under
- the terms of this License. The "Document", below, refers to any such
- manual or work. Any member of the public is a licensee, and is addressed
- as "you".</P
-><P
->A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.</P
-><P
->A "Secondary Section" is a named appendix or a front-matter section
- of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall subject
- (or to related matters) and contains nothing that could fall directly
- within that overall subject. (For example, if the Document is in part a
- textbook of mathematics, a Secondary Section may not explain any
- mathematics.) The relationship could be a matter of historical connection
- with the subject or with related matters, or of legal, commercial,
- philosophical, ethical or political position regarding them.</P
-><P
->The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in the
- notice that says that the Document is released under this License.</P
-><P
->The "Cover Texts" are certain short passages of text that are
- listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
- that the Document is released under this License.</P
-><P
->A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the general
- public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or for
- automatic translation to a variety of formats suitable for input to text
- formatters. A copy made in an otherwise Transparent file format whose
- markup has been designed to thwart or discourage subsequent modification
- by readers is not Transparent. A copy that is not "Transparent" is called
- "Opaque".</P
-><P
->Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML or
- XML using a publicly available DTD, and standard-conforming simple HTML
- designed for human modification. Opaque formats include PostScript, PDF,
- proprietary formats that can be read and edited only by proprietary word
- processors, SGML or XML for which the DTD and/or processing tools are not
- generally available, and the machine-generated HTML produced by some word
- processors for output purposes only.</P
-><P
->The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in formats
- which do not have any title page as such, "Title Page" means the text
- near the most prominent appearance of the work's title, preceding the
- beginning of the body of the text.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-2">2. VERBATIM COPYING</H3
-><P
->You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies to
- the Document are reproduced in all copies, and that you add no other
- conditions whatsoever to those of this License. You may not use technical
- measures to obstruct or control the reading or further copying of the
- copies you make or distribute. However, you may accept compensation in
- exchange for copies. If you distribute a large enough number of copies
- you must also follow the conditions in section 3.</P
-><P
->You may also lend copies, under the same conditions stated above,
- and you may publicly display copies.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-3">3. COPYING IN QUANTITY</H3
-><P
->If you publish printed copies of the Document numbering more than
- 100, and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all these
- Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
- on the back cover. Both covers must also clearly and legibly identify you
- as the publisher of these copies. The front cover must present the full
- title with all words of the title equally prominent and visible. You may
- add other material on the covers in addition. Copying with changes
- limited to the covers, as long as they preserve the title of the Document
- and satisfy these conditions, can be treated as verbatim copying in other
- respects.</P
-><P
->If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit reasonably)
- on the actual cover, and continue the rest onto adjacent pages.</P
-><P
->If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a machine-readable
- Transparent copy along with each Opaque copy, or state in or with each
- Opaque copy a publicly-accessible computer-network location containing a
- complete Transparent copy of the Document, free of added material, which
- the general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location until
- at least one year after the last time you distribute an Opaque copy
- (directly or through your agents or retailers) of that edition to the
- public.</P
-><P
->It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-4">4. MODIFICATIONS</H3
-><P
->You may copy and distribute a Modified Version of the Document
- under the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution and
- modification of the Modified Version to whoever possesses a copy of it.
- In addition, you must do these things in the Modified Version:</P
-><P
-></P
-><OL
-TYPE="A"
-><LI
-><P
->Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of previous
- versions (which should, if there were any, be listed in the History
- section of the Document). You may use the same title as a previous
- version if the original publisher of that version gives
- permission.</P
-></LI
-><LI
-><P
->List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has less
- than five).</P
-></LI
-><LI
-><P
->State on the Title page the name of the publisher of the
- Modified Version, as the publisher.</P
-></LI
-><LI
-><P
->Preserve all the copyright notices of the Document.</P
-></LI
-><LI
-><P
->Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.</P
-></LI
-><LI
-><P
->Include, immediately after the copyright notices, a license
- notice giving the public permission to use the Modified Version under
- the terms of this License, in the form shown in the Addendum
- below.</P
-></LI
-><LI
-><P
->Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.</P
-></LI
-><LI
-><P
->Include an unaltered copy of this License.</P
-></LI
-><LI
-><P
->Preserve the section entitled "History", and its title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.</P
-></LI
-><LI
-><P
->Preserve the network location, if any, given in the Document
- for public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions it
- was based on. These may be placed in the "History" section. You may
- omit a network location for a work that was published at least four
- years before the Document itself, or if the original publisher of the
- version it refers to gives permission.</P
-></LI
-><LI
-><P
->In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements and/or
- dedications given therein.</P
-></LI
-><LI
-><P
->Preserve all the Invariant Sections of the Document, unaltered
- in their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.</P
-></LI
-><LI
-><P
->Delete any section entitled "Endorsements". Such a section may
- not be included in the Modified Version.</P
-></LI
-><LI
-><P
->Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.</P
-></LI
-></OL
-><P
->If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all of
- these sections as invariant. To do this, add their titles to the list of
- Invariant Sections in the Modified Version's license notice. These titles
- must be distinct from any other section titles.</P
-><P
->You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various parties--for
- example, statements of peer review or that the text has been approved by
- an organization as the authoritative definition of a standard.</P
-><P
->You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end of the
- list of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or through
- arrangements made by) any one entity. If the Document already includes a
- cover text for the same cover, previously added by you or by arrangement
- made by the same entity you are acting on behalf of, you may not add
- another; but you may replace the old one, on explicit permission from the
- previous publisher that added the old one.</P
-><P
->The author(s) and publisher(s) of the Document do not by this
- License give permission to use their names for publicity for or to assert
- or imply endorsement of any Modified Version.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-5">5. COMBINING DOCUMENTS</H3
-><P
->You may combine the Document with other documents released under
- this License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and list
- them all as Invariant Sections of your combined work in its license
- notice.</P
-><P
->The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single copy.
- If there are multiple Invariant Sections with the same name but different
- contents, make the title of each such section unique by adding at the end
- of it, in parentheses, the name of the original author or publisher of
- that section if known, or else a unique number. Make the same adjustment
- to the section titles in the list of Invariant Sections in the license
- notice of the combined work.</P
-><P
->In the combination, you must combine any sections entitled
- "History" in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements", and
- any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H3
-><P
->You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual copies
- of this License in the various documents with a single copy that is
- included in the collection, provided that you follow the rules of this
- License for verbatim copying of each of the documents in all other
- respects.</P
-><P
->You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a copy
- of this License into the extracted document, and follow this License in
- all other respects regarding verbatim copying of that document.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H3
-><P
->A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of a
- storage or distribution medium, does not as a whole count as a Modified
- Version of the Document, provided no compilation copyright is claimed for
- the compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they are
- not themselves derivative works of the Document.</P
-><P
->If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter of
- the entire aggregate, the Document's Cover Texts may be placed on covers
- that surround only the Document within the aggregate. Otherwise they must
- appear on covers around the whole aggregate.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-8">8. TRANSLATION</H3
-><P
->Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include translations
- of some or all Invariant Sections in addition to the original versions of
- these Invariant Sections. You may include a translation of this License
- provided that you also include the original English version of this
- License. In case of a disagreement between the translation and the
- original English version of this License, the original English version
- will prevail.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-9">9. TERMINATION</H3
-><P
->You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt to
- copy, modify, sublicense or distribute the Document is void, and will
- automatically terminate your rights under this License. However, parties
- who have received copies, or rights, from you under this License will not
- have their licenses terminated so long as such parties remain in full
- compliance.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H3
-><P
->The Free Software Foundation may publish new, revised versions of
- the GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- <A
-HREF="http://www.gnu.org/copyleft/"
-TARGET="_top"
-> http://www.gnu.org/copyleft/</A
->
-
- .</P
-><P
->Each version of the License is given a distinguishing version
- number. If the Document specifies that a particular numbered version of
- this License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or of
- any later version that has been published (not as a draft) by the Free
- Software Foundation. If the Document does not specify a version number of
- this License, you may choose any version ever published (not as a draft)
- by the Free Software Foundation.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="gfdl-howto">How to use this License for your documents</H3
-><P
->To use this License in a document you have written, include a copy
- of the License in the document and put the following copyright and
- license notices just after the title page:</P
-><A
-NAME="AEN128"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU Free
- Documentation License, Version 1.1 or any later version published by
- the Free Software Foundation; with the Invariant Sections being LIST
- THEIR TITLES, with the Front-Cover Texts being LIST, and with the
- Back-Cover Texts being LIST. A copy of the license is included in the
- section entitled "GNU Free Documentation License".</P
-></BLOCKQUOTE
-><P
->If you have no Invariant Sections, write "with no Invariant
- Sections" instead of saying which ones are invariant. If you have no
- Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
- Texts being LIST"; likewise for Back-Cover Texts.</P
-><P
->If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of free
- software license, such as the GNU General Public License, to permit their
- use in free software.</P
-></DIV
-></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/credits.html b/docs/html/credits.html
index a15f56fb7dd665802453a544800aab9a2a380311..a85ab6cbc8a90ebb9719ee19dec30b0761587931 100644
--- a/docs/html/credits.html
+++ b/docs/html/credits.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="credits">1.4. Credits</H1
+NAME="credits"
+></A
+>1.4. Credits</H1
><P
> The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
@@ -81,66 +83,115 @@ NAME="credits">1.4. Credits</H1
contribution to the Bugzilla community:
</P
><P
-> <A
-HREF="mailto://mbarnson@sisna.com"
-TARGET="_top"
->Matthew P. Barnson</A
->
- for the Herculaean task of pulling together the Bugzilla Guide and
- shepherding it to 2.14.
- </P
+></P
+><DIV
+CLASS="variablelist"
+><DL
+><DT
+>Matthew P. Barnson <TT
+CLASS="email"
+><<A
+HREF="mailto:mbarnson@sisna.com"
+>mbarnson@sisna.com</A
+>></TT
+></DT
+><DD
><P
-> <A
-HREF="mailto://terry@mozilla.org"
-TARGET="_top"
->Terry Weissman</A
->
- for initially writing Bugzilla and creating the
- README upon which the UNIX installation documentation is largely based.
- </P
+>for the Herculaean task of pulling together the Bugzilla Guide
+ and shepherding it to 2.14.
+ </P
+></DD
+><DT
+>Terry Weissman <TT
+CLASS="email"
+><<A
+HREF="mailto:terry@mozilla.org"
+>terry@mozilla.org</A
+>></TT
+></DT
+><DD
><P
-> <A
-HREF="mailto://tara@tequilarista.org"
-TARGET="_top"
->Tara Hernandez</A
->
- for keeping Bugzilla development going
- strong after Terry left mozilla.org
- </P
+>for initially writing Bugzilla and creating the README upon
+ which the UNIX installation documentation is largely based.
+ </P
+></DD
+><DT
+>Tara Hernandez <TT
+CLASS="email"
+><<A
+HREF="mailto:tara@tequilarists.org"
+>tara@tequilarists.org</A
+>></TT
+></DT
+><DD
><P
-> <A
-HREF="mailto://dkl@redhat.com"
-TARGET="_top"
->Dave Lawrence</A
->
- for providing insight into the key differences between Red Hat's
- customized Bugzilla, and being largely responsible for the "Red
- Hat Bugzilla" appendix
- </P
+>for keeping Bugzilla development going strong after Terry left
+ mozilla.org and for running landfill.
+ </P
+></DD
+><DT
+>Dave Lawrence <TT
+CLASS="email"
+><<A
+HREF="mailto:dkl@redhat.com"
+>dkl@redhat.com</A
+>></TT
+></DT
+><DD
><P
-> <A
-HREF="mailto://endico@mozilla.org"
-TARGET="_top"
->Dawn Endico</A
-> for
- being a hacker extraordinaire and putting up with my incessant
- questions and arguments on irc.mozilla.org in #mozwebtools
- </P
+>for providing insight into the key differences between Red
+ Hat's customized Bugzilla, and being largely responsible for
+ <A
+HREF="variant-redhat.html"
+>Section D.1</A
+>.
+ </P
+></DD
+><DT
+>Dawn Endico <TT
+CLASS="email"
+><<A
+HREF="mailto:endico@mozilla.org"
+>endico@mozilla.org</A
+>></TT
+></DT
+><DD
+><P
+>for being a hacker extraordinaire and putting up with Matthew's
+ incessant questions and arguments on irc.mozilla.org in #mozwebtools
+ </P
+></DD
+><DT
+>Jacob Steenhagen <TT
+CLASS="email"
+><<A
+HREF="mailto:jake@bugzilla.org"
+>jake@bugzilla.org</A
+>></TT
+></DT
+><DD
+><P
+>for taking over documentation during the 2.17 development
+ period and backporting relevent docs changes to this 2.16 branch.
+ </P
+></DD
+></DL
+></DIV
><P
> Last but not least, all the members of the
<A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
TARGET="_top"
-> netscape.public.mozilla.webtools</A
-> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
+>news://news.mozilla.org/netscape/public/mozilla/webtools</A
+>
+ newsgroup. Without your discussions, insight, suggestions, and patches,
+ this could never have happened.
</P
><P
> Thanks also go to the following people for significant contributions
- to this documentation (in no particular order):
- </P
-><P
-> Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
- Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
+ to this documentation (in alphabetical order):
+ Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
+ .
</P
></DIV
><DIV
diff --git a/docs/html/cust-templates.html b/docs/html/cust-templates.html
index 7987f2aba8ab6d9d5e76468a96ab94311f559ac1..b27a3d725d6bebbc8a6caaf366e7fcccdfecaa44 100644
--- a/docs/html/cust-templates.html
+++ b/docs/html/cust-templates.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="cust-templates">5.7. Template Customisation</H1
+NAME="cust-templates"
+></A
+>5.7. Template Customisation</H1
><P
> One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
@@ -97,7 +99,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1539">5.7.1. What to Edit</H2
+NAME="AEN1532"
+></A
+>5.7.1. What to Edit</H2
><P
> There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
@@ -210,7 +214,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1558">5.7.2. How To Edit Templates</H2
+NAME="AEN1551"
+></A
+>5.7.2. How To Edit Templates</H2
><P
> The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
@@ -290,7 +296,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1568">5.7.3. Template Formats</H2
+NAME="AEN1561"
+></A
+>5.7.3. Template Formats</H2
><P
> Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
@@ -350,7 +358,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1581">5.7.4. Particular Templates</H2
+NAME="AEN1574"
+></A
+>5.7.4. Particular Templates</H2
><P
> There are a few templates you may be particularly interested in
customising for your installation.
diff --git a/docs/html/database.html b/docs/html/database.html
index 95bce503ea222446cf633bacb2f69ca7ec2f0acf..c775d37f360d4f959ea1ce8303a85112fc59ef76 100644
--- a/docs/html/database.html
+++ b/docs/html/database.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
-NAME="database">Appendix B. The Bugzilla Database</H1
+NAME="database"
+></A
+>Appendix B. The Bugzilla Database</H1
><DIV
CLASS="TOC"
><DL
diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html
index 49e9b6526f61ce9723fea92279c6ff8bdc9411bf..981a819d86eaa7c9f5f5e53028ae2be0eb228088 100644
--- a/docs/html/dbdoc.html
+++ b/docs/html/dbdoc.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="The Bugzilla Database"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
+NAME="dbdoc"
+></A
+>B.2. MySQL Bugzilla Database Introduction</H1
><P
>This information comes straight from my life. I was forced to learn
how Bugzilla organizes database because of nitpicky requests from users
@@ -133,7 +135,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN2077">B.2.1. Bugzilla Database Basics</H2
+NAME="AEN2162"
+></A
+>B.2.1. Bugzilla Database Basics</H2
><P
>If you were like me, at this point you're totally clueless about
the internals of MySQL, and if it weren't for this executive order from
@@ -247,7 +251,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN2104">B.2.1.1. Bugzilla Database Tables</H3
+NAME="AEN2189"
+></A
+>B.2.1.1. Bugzilla Database Tables</H3
><P
>Imagine your MySQL database as a series of spreadsheets, and
you won't be too far off. If you use this command:</P
diff --git a/docs/html/dbschema.html b/docs/html/dbschema.html
index f4b0ef7146d69df1a1f2da598aa6378c01032a45..efa8fbf0666d2b91b310c2b0b14e5cc955cf67ee 100644
--- a/docs/html/dbschema.html
+++ b/docs/html/dbschema.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="The Bugzilla Database"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="dbschema">B.1. Database Schema Chart</H1
+NAME="dbschema"
+></A
+>B.1. Database Schema Chart</H1
><P
> <DIV
CLASS="mediaobject"
diff --git a/docs/html/disclaimer.html b/docs/html/disclaimer.html
index dfec8aaab3e83a5c948aaff9aa9079237172b47c..71213504ed033f0f336e4aaf12a998568b96ba9c 100644
--- a/docs/html/disclaimer.html
+++ b/docs/html/disclaimer.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="disclaimer">1.2. Disclaimer</H1
+NAME="disclaimer"
+></A
+>1.2. Disclaimer</H1
><P
> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
diff --git a/docs/html/extraconfig.html b/docs/html/extraconfig.html
index fb8ceb4459f6ff80026054ef2f0ba14c0fa79a63..64d78bf4c5ec381b5bdb83629f97de3e325b1171 100644
--- a/docs/html/extraconfig.html
+++ b/docs/html/extraconfig.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="extraconfig">4.2. Optional Additional Configuration</H1
+NAME="extraconfig"
+></A
+>4.2. Optional Additional Configuration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN845">4.2.1. Dependency Charts</H2
+NAME="AEN717"
+></A
+>4.2.1. Dependency Charts</H2
><P
>As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
@@ -141,7 +145,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN860">4.2.2. Bug Graphs</H2
+NAME="AEN732"
+></A
+>4.2.2. Bug Graphs</H2
><P
>As long as you installed the GD and Graph::Base Perl modules you
might as well turn on the nifty Bugzilla bug reporting graphs.</P
@@ -198,7 +204,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN873">4.2.3. The Whining Cron</H2
+NAME="AEN745"
+></A
+>4.2.3. The Whining Cron</H2
><P
>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
@@ -284,7 +292,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="bzldap">4.2.4. LDAP Authentication</H2
+NAME="bzldap"
+></A
+>4.2.4. LDAP Authentication</H2
><P
> <DIV
CLASS="warning"
@@ -375,7 +385,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
+NAME="content-type"
+></A
+>4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
@@ -445,7 +457,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="htaccess">4.2.6. <TT
+NAME="htaccess"
+></A
+>4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
@@ -615,7 +629,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="mod-throttle">4.2.7. <TT
+NAME="mod-throttle"
+></A
+>4.2.7. <TT
CLASS="filename"
>mod_throttle</TT
>
diff --git a/docs/html/faq.html b/docs/html/faq.html
index 0b0dfcca5c078bc1738778dd611a176c110ec5ba..2d6206712d2dc9a02ee0bdfaecf54caa6c00acf6 100644
--- a/docs/html/faq.html
+++ b/docs/html/faq.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Integrating Bugzilla with Third-Party Tools"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
-NAME="faq">Appendix A. The Bugzilla FAQ</H1
+NAME="faq"
+></A
+>Appendix A. The Bugzilla FAQ</H1
><P
> This FAQ includes questions not covered elsewhere in the Guide.
</P
@@ -85,64 +87,71 @@ HREF="faq.html#faq-general"
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1649"
+HREF="faq.html#faq-general-information"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1655"
+HREF="faq.html#faq-general-license"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1661"
+HREF="faq.html#faq-general-support"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1668"
+HREF="faq.html#faq-general-companies"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1693"
+HREF="faq.html#faq-general-maintainers"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1699"
+HREF="faq.html#faq-general-compare"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1705"
-> Why doesn't Bugzilla offer this or that feature or compatability
+HREF="faq.html#faq-general-bzmissing"
+> Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1712"
+HREF="faq.html#faq-general-mysql"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1717"
-> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
+HREF="faq.html#faq-general-bonsaitools"
+> Why do the scripts say
+ <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+> instead of
+ <TT
+CLASS="filename"
+>/usr/bin/perl</TT
+> or something else?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1723"
+HREF="faq.html#faq-general-cookie"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
@@ -157,41 +166,41 @@ HREF="faq.html#faq-phb"
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1733"
+HREF="faq.html#faq-phb-client"
> Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
-HREF="faq.html#AEN1738"
+HREF="faq.html#faq-phb-integration"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1743"
+HREF="faq.html#faq-phb-projects"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="faq.html#AEN1748"
+HREF="faq.html#faq-phb-sorting"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="faq.html#AEN1753"
+HREF="faq.html#faq-phb-attachments"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="faq.html#AEN1758"
+HREF="faq.html#faq-phb-priorities"
> 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?
@@ -199,35 +208,35 @@ HREF="faq.html#AEN1758"
></DT
><DT
>A.2.7. <A
-HREF="faq.html#AEN1765"
+HREF="faq.html#faq-phb-reporting"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="faq.html#AEN1772"
+HREF="faq.html#faq-phb-email"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="faq.html#AEN1777"
+HREF="faq.html#faq-phb-cclist"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="faq.html#AEN1782"
+HREF="faq.html#faq-phb-emailapp"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="faq.html#AEN1789"
+HREF="faq.html#faq-phb-data"
> 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
@@ -236,28 +245,28 @@ HREF="faq.html#AEN1789"
></DT
><DT
>A.2.12. <A
-HREF="faq.html#AEN1797"
+HREF="faq.html#faq-phb-l10n"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="faq.html#AEN1802"
+HREF="faq.html#faq-phb-reports"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="faq.html#AEN1807"
+HREF="faq.html#faq-phb-searching"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="faq.html#AEN1812"
+HREF="faq.html#faq-phb-midair"
> 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?
@@ -265,19 +274,19 @@ HREF="faq.html#AEN1812"
></DT
><DT
>A.2.16. <A
-HREF="faq.html#AEN1817"
+HREF="faq.html#faq-phb-backup"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="faq.html#AEN1823"
+HREF="faq.html#faq-phb-livebackup"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="faq.html#AEN1828"
+HREF="faq.html#faq-phb-maintenance"
> 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
@@ -287,7 +296,7 @@ HREF="faq.html#AEN1828"
></DT
><DT
>A.2.19. <A
-HREF="faq.html#AEN1834"
+HREF="faq.html#faq-phb-installtime"
> 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
@@ -297,7 +306,7 @@ HREF="faq.html#AEN1834"
></DT
><DT
>A.2.20. <A
-HREF="faq.html#AEN1839"
+HREF="faq.html#faq-phb-cost"
> 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
@@ -313,20 +322,20 @@ HREF="faq.html#faq-security"
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1846"
+HREF="faq.html#faq-security-mysql"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide)?
</A
></DT
><DT
>A.3.2. <A
-HREF="faq.html#AEN1852"
+HREF="faq.html#faq-security-knownproblems"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="faq.html#AEN1857"
+HREF="faq.html#faq-security-mysqluser"
> 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.
@@ -343,48 +352,48 @@ HREF="faq.html#faq-email"
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1864"
+HREF="faq.html#faq-email-nomail"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.4.2. <A
-HREF="faq.html#AEN1869"
+HREF="faq.html#faq-email-testing"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.4.3. <A
-HREF="faq.html#AEN1874"
+HREF="faq.html#faq-email-whine"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1880"
+HREF="faq.html#faq-email-procmail"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="faq.html#AEN1887"
+HREF="faq.html#faq-email-mailif"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1892"
+HREF="faq.html#faq-email-sendmailnow"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="faq.html#AEN1899"
+HREF="faq.html#faq-email-nonreceived"
> How come email from Bugzilla changes never reaches me?
</A
></DT
@@ -399,39 +408,33 @@ HREF="faq.html#faq-db"
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN1907"
+HREF="faq.html#faq-db-oracle"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN1912"
+HREF="faq.html#faq-db-corrupted"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN1920"
+HREF="faq.html#faq-db-manualedit"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="faq.html#AEN1925"
-> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
- </A
-></DT
-><DT
->A.5.5. <A
-HREF="faq.html#AEN1930"
+HREF="faq.html#faq-db-permissions"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
->A.5.6. <A
-HREF="faq.html#AEN1935"
+>A.5.5. <A
+HREF="faq.html#faq-db-synchronize"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
@@ -447,26 +450,26 @@ HREF="faq.html#faq-nt"
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN1944"
+HREF="faq.html#faq-nt-easiest"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="faq.html#AEN1949"
+HREF="faq.html#faq-nt-bundle"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN1954"
+HREF="faq.html#faq-nt-mappings"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="faq.html#AEN1962"
+HREF="faq.html#faq-nt-dbi"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
@@ -482,40 +485,33 @@ HREF="faq.html#faq-use"
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN1983"
+HREF="faq.html#faq-use-changeaddress"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="faq.html#AEN1988"
+HREF="faq.html#faq-use-query"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="faq.html#AEN1993"
+HREF="faq.html#faq-use-accept"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.7.4. <A
-HREF="faq.html#AEN2003"
+HREF="faq.html#faq-use-attachment"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="faq.html#AEN2008"
-> Email submissions to Bugzilla that have attachments end up asking me to
- save it as a "cgi" file.
- </A
-></DT
-><DT
->A.7.6. <A
-HREF="faq.html#AEN2013"
+HREF="faq.html#faq-use-keyword"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
@@ -530,20 +526,20 @@ HREF="faq.html#faq-hacking"
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN2020"
+HREF="faq.html#faq-hacking-bugzillabugs"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN2029"
+HREF="faq.html#faq-hacking-priority"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN2035"
+HREF="faq.html#faq-hacking-patches"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
@@ -554,14 +550,18 @@ HREF="faq.html#AEN2035"
CLASS="qandadiv"
><H3
><A
-NAME="faq-general">1. General Questions</H3
+NAME="faq-general"
+></A
+>1. General Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1649"><B
+NAME="faq-general-information"
+></A
+><B
>A.1.1. </B
>
Where can I find information about Bugzilla?</P
@@ -587,7 +587,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1655"><B
+NAME="faq-general-license"
+></A
+><B
>A.1.2. </B
>
What license is Bugzilla distributed under?
@@ -614,7 +616,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1661"><B
+NAME="faq-general-support"
+></A
+><B
>A.1.3. </B
>
How do I get commercial support for Bugzilla?
@@ -626,7 +630,16 @@ CLASS="answer"
><B
> </B
>
- <A
+ <A
+HREF="http://bugzilla.org/consulting.html"
+TARGET="_top"
+>http://bugzilla.org/consulting.html</A
+>
+ is a list of people and companies who have asked us to list them
+ as consultants for Bugzilla.
+ </P
+><P
+> <A
HREF="http://www.collab.net/"
TARGET="_top"
>www.collab.net</A
@@ -649,7 +662,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1668"><B
+NAME="faq-general-companies"
+></A
+><B
>A.1.4. </B
>
What major companies or projects are currently using Bugzilla
@@ -664,7 +679,7 @@ CLASS="answer"
>
There are <EM
>dozens</EM
-> of major comapanies with public
+> of major companies with public
Bugzilla sites to track bugs in their products. A few include:
<P
></P
@@ -685,10 +700,6 @@ BORDER="0"
></TR
><TR
><TD
->AtHome Corporation</TD
-></TR
-><TR
-><TD
>Red Hat Software</TD
></TR
><TR
@@ -757,7 +768,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1693"><B
+NAME="faq-general-maintainers"
+></A
+><B
>A.1.5. </B
>
Who maintains Bugzilla?
@@ -775,7 +788,7 @@ HREF="http://www.bugzilla.org/who_we_are.html"
TARGET="_top"
>core team</A
>,
- led by Dave Miller (justdave@syndicomm.com).
+ led by Dave Miller (justdave@netscape.com).
</P
></DIV
></DIV
@@ -785,7 +798,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1699"><B
+NAME="faq-general-compare"
+></A
+><B
>A.1.6. </B
>
How does Bugzilla stack up against other bug-tracking databases?
@@ -821,10 +836,12 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1705"><B
+NAME="faq-general-bzmissing"
+></A
+><B
>A.1.7. </B
>
- Why doesn't Bugzilla offer this or that feature or compatability
+ Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</P
></DIV
@@ -859,7 +876,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1712"><B
+NAME="faq-general-mysql"
+></A
+><B
>A.1.8. </B
>
Why MySQL? I'm interested in seeing Bugzilla run on
@@ -872,9 +891,28 @@ CLASS="answer"
><B
> </B
>
- There is DB-independence work afoot. PostgreSQL support is planned
- for 2.18, and full DB-independence can't be far further on.
+ MySQL was originally chosen because it is free, easy to install,
+ and was available for the hardware Netscape intended to run it on.
</P
+><P
+> There is currently work in progress to make Bugzilla work on
+ PostgreSQL and Sybase in the default distribution. You can track
+ the progress of these initiatives in bugs <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>98304</A
+>
+ and <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
+TARGET="_top"
+>173130</A
+>
+ respectively.
+ </P
+><P
+> Once both of these are done, adding support for additional
+ database servers should be trivial.
+ </P
></DIV
></DIV
><DIV
@@ -883,11 +921,20 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1717"><B
+NAME="faq-general-bonsaitools"
+></A
+><B
>A.1.9. </B
>
- Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
+ Why do the scripts say
+ <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+> instead of
+ <TT
+CLASS="filename"
+>/usr/bin/perl</TT
+> or something else?
</P
></DIV
><DIV
@@ -896,16 +943,41 @@ CLASS="answer"
><B
> </B
>
- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally
- Terry wanted a place to put a version of Perl and other tools
- that was strictly under his control.
- </P
+ Mozilla.org used <TT
+CLASS="filename"
+>/usr/bonsaitools/bin/perl</TT
+>,
+ because originally Terry wanted a place to put a version of Perl
+ and other tools that was strictly under his control.
+ </P
+><DIV
+CLASS="note"
><P
-> We always recommend that, if possible, you keep the path
- as /usr/bonsaitools/bin/perl, and simply add symlink.
- This will make upgrading
- your Bugzilla much easier in the future.
- </P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This convention was abonded during the 2.17 development cycle so
+ it will no longer be an issue when 2.18 comes out.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -914,7 +986,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1723"><B
+NAME="faq-general-cookie"
+></A
+><B
>A.1.10. </B
>
Is there an easy way to change the Bugzilla cookie name?
@@ -935,7 +1009,9 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-phb">2. Managerial Questions</H3
+NAME="faq-phb"
+></A
+>2. Managerial Questions</H3
><P
> <DIV
CLASS="note"
@@ -972,7 +1048,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1733"><B
+NAME="faq-phb-client"
+></A
+><B
>A.2.1. </B
>
Is Bugzilla web-based, or do you have to have specific software or
@@ -996,7 +1074,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1738"><B
+NAME="faq-phb-integration"
+></A
+><B
>A.2.2. </B
>
Can Bugzilla integrate with
@@ -1020,7 +1100,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1743"><B
+NAME="faq-phb-projects"
+></A
+><B
>A.2.3. </B
>
Does Bugzilla allow the user to track multiple projects?
@@ -1032,11 +1114,39 @@ CLASS="answer"
><B
> </B
>
- Absolutely! You can track any number of Products (although you
- are limited to about 55 or so if
- you are using Product-Based Groups), that can each be composed of any
- number of Components.
+ Absolutely! You can track any number of Products that can each be
+ composed of any number of Components.
</P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>There are only 55 groups available in version 2.16 of
+ Bugzilla. If you are using product groups, this will also limit
+ the number of products you can have. This limit does not exist in
+ the current 2.17 development releases and will not exist in 2.18.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -1045,7 +1155,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1748"><B
+NAME="faq-phb-sorting"
+></A
+><B
>A.2.4. </B
>
If I am on many projects, and search for all bugs assigned to me, will
@@ -1068,7 +1180,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1753"><B
+NAME="faq-phb-attachments"
+></A
+><B
>A.2.5. </B
>
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
@@ -1083,9 +1197,9 @@ CLASS="answer"
>
Yes - any sort of attachment is allowed, although administrators can
configure a maximum size.
- There are many specific MIME-types that are pre-defined by Bugzilla,
- but you may specify any arbitrary MIME-type you need when you
- upload the file.
+ Bugzilla gives the user the option of either using the MIME-type
+ supplied by the browser, choosing from a pre-defined list or
+ manually typing any arbitrary MIME-type.
</P
></DIV
></DIV
@@ -1095,7 +1209,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1758"><B
+NAME="faq-phb-priorities"
+></A
+><B
>A.2.6. </B
>
Does Bugzilla allow us to define our own priorities and levels? Do we
@@ -1120,7 +1236,7 @@ CLASS="answer"
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
TARGET="_top"
>http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
->
+>.
</P
></DIV
></DIV
@@ -1130,7 +1246,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1765"><B
+NAME="faq-phb-reporting"
+></A
+><B
>A.2.7. </B
>
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
@@ -1146,18 +1264,51 @@ CLASS="answer"
Yes. Look at <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top"
-> http://bugzilla.mozilla.org/reports.cgi</A
-> for basic reporting
- and graphing facilities.
+>http://bugzilla.mozilla.org/reports.cgi</A
+>
+ for samples of what Bugzilla can do in reporting and graphing.
</P
><P
-> For more advanced reporting, I recommend hooking up a professional
- reporting package, such as Crystal Reports, and use ODBC to access
- the MySQL database. You can do a lot through the Query page of
- Bugzilla as well, but right now Advanced Reporting is much
- better accomplished through third-party utilities that can
- interface with the database directly.
+> If you can not get the reports you want from the included reporting
+ scripts, it is possible to hook up a professional reporting package
+ such as Crystal Reports using ODBC. If you choose to do this,
+ beware that giving direct access to the database does contain some
+ security implications. Even if you give read-only access to the
+ bugs database it will bypass the secure bugs features of Bugzilla.
</P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Bugzilla's current development versions can do a lot more in the
+ way of reporting. To see examples, check out
+ <A
+HREF="http://bugzilla.mozilla.org/report.cgi"
+TARGET="_top"
+>http://bugzilla.mozilla.org/report.cgi</A
+>.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -1166,7 +1317,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1772"><B
+NAME="faq-phb-email"
+></A
+><B
>A.2.8. </B
>
Is there email notification and if so, what do you see when you get an
@@ -1191,7 +1344,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1777"><B
+NAME="faq-phb-cclist"
+></A
+><B
>A.2.9. </B
>
Can email notification be set up to send to multiple
@@ -1214,7 +1369,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1782"><B
+NAME="faq-phb-emailapp"
+></A
+><B
>A.2.10. </B
>
Do users have to have any particular
@@ -1271,7 +1428,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1789"><B
+NAME="faq-phb-data"
+></A
+><B
>A.2.11. </B
>
Does Bugzilla allow data to be imported and exported? If I had outsiders
@@ -1286,28 +1445,39 @@ CLASS="answer"
><B
> </B
>
- Mozilla allows data export through a custom DTD in XML format.
- It does not, however, export to specific formats other than the
- XML Mozilla DTD. Importing the data into Excel or any other application
- is left as an exercise for the reader.
- </P
+ Bugzilla can only output buglists as HTML in version 2.16. There
+ are other formats available (CSV and RDF) in the newer development
+ versions.
+ </P
><P
-> If you create import filters to other applications from Mozilla's XML,
- please submit your modifications for inclusion in future Bugzilla
- distributions.
- </P
+> Bugzilla can export bugs using <TT
+CLASS="filename"
+>xml.cgi</TT
+> with
+ either a bug number or list of bug numbers.
+ </P
><P
-> As for data import, any application can send data to Bugzilla through
- the HTTP protocol, or through Mozilla's XML API. However, it seems
- kind of silly to put another front-end in front of Bugzilla;
- it makes more sense to create a simplified bug submission form in
- HTML. You can find an excellent example at
- <A
-HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
-TARGET="_top"
-> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+> Currently the only script included with Bugzilla that can import
+ data is <TT
+CLASS="filename"
+>importxml.pl</TT
+> which is intended to be
+ used for importing the data generated by <TT
+CLASS="filename"
+>xml.cgi</TT
>
- </P
+ in association with bug moving. Any other use is left as an
+ exercise for the user.
+ </P
+><P
+> There are also scripts included in the <TT
+CLASS="filename"
+>contrib/</TT
+>
+ directory for using e-mail to import information into Bugzilla,
+ but these scripts are not currently supported and included for
+ educational purposes.
+ </P
></DIV
></DIV
><DIV
@@ -1316,7 +1486,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1797"><B
+NAME="faq-phb-l10n"
+></A
+><B
>A.2.12. </B
>
Has anyone converted Bugzilla to another language to be used in other
@@ -1329,10 +1501,20 @@ CLASS="answer"
><B
> </B
>
- To a certain extent, yes. 2.16's templates mean that you can localise
- the user-facing UI (and several projects are doing exactly that.) However,
- error messages and the admin interface are currently not localisable.
- This should be achieved by 2.18.
+ Yes. For more information including available translated templates,
+ see <A
+HREF="http://www.bugzilla.org/download.html#localizations"
+TARGET="_top"
+>http://www.bugzilla.org/download.html#localizations</A
+>.
+ The admin interfaces are still not included in these translated
+ templates and is therefore still English only. Also, there may be
+ issues with the charset not being declared. See <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug 126226</A
+>
+ for more information.
</P
></DIV
></DIV
@@ -1342,7 +1524,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1802"><B
+NAME="faq-phb-reports"
+></A
+><B
>A.2.13. </B
>
Can a user create and save reports? Can they do this in Word format?
@@ -1355,7 +1539,7 @@ CLASS="answer"
><B
> </B
>
- Yes. No. No.
+ Yes. No. Not in 2.16.
</P
></DIV
></DIV
@@ -1365,7 +1549,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1807"><B
+NAME="faq-phb-searching"
+></A
+><B
>A.2.14. </B
>
Does Bugzilla have the ability to search by word, phrase, compound
@@ -1389,7 +1575,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1812"><B
+NAME="faq-phb-midair"
+></A
+><B
>A.2.15. </B
>
Does Bugzilla provide record locking when there is simultaneous access
@@ -1414,7 +1602,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1817"><B
+NAME="faq-phb-backup"
+></A
+><B
>A.2.16. </B
>
Are there any backup features provided?
@@ -1442,7 +1632,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1823"><B
+NAME="faq-phb-livebackup"
+></A
+><B
>A.2.17. </B
>
Can users be on the system while a backup is in progress?
@@ -1466,7 +1658,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1828"><B
+NAME="faq-phb-maintenance"
+></A
+><B
>A.2.18. </B
>
What type of human resources are needed to be on staff to install and
@@ -1499,7 +1693,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1834"><B
+NAME="faq-phb-installtime"
+></A
+><B
>A.2.19. </B
>
What time frame are we looking at if we decide to hire people to install
@@ -1530,7 +1726,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1839"><B
+NAME="faq-phb-cost"
+></A
+><B
>A.2.20. </B
>
Is there any licensing fee or other fees for using Bugzilla? Any
@@ -1553,14 +1751,18 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-security">3. Bugzilla Security</H3
+NAME="faq-security"
+></A
+>3. Bugzilla Security</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1846"><B
+NAME="faq-security-mysql"
+></A
+><B
>A.3.1. </B
>
How do I completely disable MySQL security if it's giving me problems
@@ -1587,7 +1789,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1852"><B
+NAME="faq-security-knownproblems"
+></A
+><B
>A.3.2. </B
>
Are there any security problems with Bugzilla?
@@ -1613,7 +1817,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1857"><B
+NAME="faq-security-mysqluser"
+></A
+><B
>A.3.3. </B
>
I've implemented the security fixes mentioned in Chris Yeh's security
@@ -1638,14 +1844,18 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-email">4. Bugzilla Email</H3
+NAME="faq-email"
+></A
+>4. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1864"><B
+NAME="faq-email-nomail"
+></A
+><B
>A.4.1. </B
>
I have a user who doesn't want to receive any more email from Bugzilla.
@@ -1659,7 +1869,11 @@ CLASS="answer"
> </B
>
The user should be able to set
- this in user email preferences (uncheck all boxes.)
+ this in user email preferences (uncheck all boxes) or you can add
+ their email address to the <TT
+CLASS="filename"
+>data/nomail</TT
+> file.
</P
></DIV
></DIV
@@ -1669,7 +1883,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1869"><B
+NAME="faq-email-testing"
+></A
+><B
>A.4.2. </B
>
I'm evaluating/testing Bugzilla, and don't want it to send email to
@@ -1682,7 +1898,7 @@ CLASS="answer"
><B
> </B
>
- Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
+ Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
</P
></DIV
@@ -1693,7 +1909,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1874"><B
+NAME="faq-email-whine"
+></A
+><B
>A.4.3. </B
>
I want whineatnews.pl to whine at something more, or other than, only new
@@ -1707,10 +1925,10 @@ CLASS="answer"
> </B
>
Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
- You can find it at<A
-HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
+ You can find it at <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
TARGET="_top"
-> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
+>http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
>. This
patch is against an older version of Bugzilla, so you must apply
the diffs manually.
@@ -1723,7 +1941,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1880"><B
+NAME="faq-email-procmail"
+></A
+><B
>A.4.4. </B
>
I don't like/want to use Procmail to hand mail off to bug_email.pl.
@@ -1739,7 +1959,9 @@ CLASS="answer"
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1884"><BLOCKQUOTE
+NAME="AEN1973"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
@@ -1758,7 +1980,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1887"><B
+NAME="faq-email-mailif"
+></A
+><B
>A.4.5. </B
>
How do I set up the email interface to submit/change bugs via email?
@@ -1781,7 +2005,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1892"><B
+NAME="faq-email-sendmailnow"
+></A
+><B
>A.4.6. </B
>
Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
@@ -1814,7 +2040,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1899"><B
+NAME="faq-email-nonreceived"
+></A
+><B
>A.4.7. </B
>
How come email from Bugzilla changes never reaches me?
@@ -1843,14 +2071,18 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-db">5. Bugzilla Database</H3
+NAME="faq-db"
+></A
+>5. Bugzilla Database</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1907"><B
+NAME="faq-db-oracle"
+></A
+><B
>A.5.1. </B
>
I've heard Bugzilla can be used with Oracle?
@@ -1862,10 +2094,11 @@ CLASS="answer"
><B
> </B
>
- Red Hat Bugzilla works with Oracle. The current version
- from Mozilla.org does not have this capability. Unfortunately, though
- you will sacrifice a lot of the really great features available in
- Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+ Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
+ Red Hat's newer version (based on 2.17.1 and soon to be merged into
+ the main distribution) runs on PostgreSQL. At this time we know of
+ no recent ports of Bugzilla to Oracle but do intend to support it
+ in the future (possibly the 2.20 time-frame).
</P
></DIV
></DIV
@@ -1875,7 +2108,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1912"><B
+NAME="faq-db-corrupted"
+></A
+><B
>A.5.2. </B
>
I think my database might be corrupted, or contain invalid entries. What
@@ -1920,7 +2155,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1920"><B
+NAME="faq-db-manualedit"
+></A
+><B
>A.5.3. </B
>
I want to manually edit some entries in my database. How?
@@ -1934,34 +2171,22 @@ CLASS="answer"
>
There is no facility in Bugzilla itself to do this. It's also generally
not a smart thing to do if you don't know exactly what you're doing.
- However, if you understand SQL you can use the mysqladmin utility to
- manually insert, delete, and modify table information. Personally, I
- use "phpMyAdmin". You have to compile a PHP module with MySQL
- support to make it work, but it's very clean and easy to use.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1925"><B
->A.5.4. </B
->
- I try to add myself as a user, but Bugzilla always tells me my password is wrong.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
+ However, if you understand SQL you can use the <B
+CLASS="command"
+>mysql</B
>
- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
- the "crypt()" function. This prevented MySQL from storing encrypted passwords.
- Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+ command line utility to manually insert, delete and modify table
+ information. There are also more intuitive GUI clients available.
+ Personal favorites of the Bugzilla team are <A
+HREF="http://www.phpmyadmin.net/"
+TARGET="_top"
+>phpMyAdmin</A
+> and <A
+HREF="http://www.mysql.com/downloads/gui-mycc.html"
+TARGET="_top"
+>MySQL Control
+ Center</A
+>.
</P
></DIV
></DIV
@@ -1971,8 +2196,10 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1930"><B
->A.5.5. </B
+NAME="faq-db-permissions"
+></A
+><B
+>A.5.4. </B
>
I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
@@ -1986,10 +2213,42 @@ CLASS="answer"
>
Try running MySQL from its binary: "mysqld --skip-grant-tables". This
will allow you to completely rule out grant tables as the cause of your
- frustration. However, I do not recommend you run it this way on a regular
- basis, unless you really want your web site defaced and your machine
- cracked.
- </P
+ frustration. If this Bugzilla is able to connect at this point then
+ you need to check that you have granted proper permission to the user
+ password combo defined in <TT
+CLASS="filename"
+>localconfig</TT
+>.
+ </P
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Running MySQL with this command line option is very insecure and
+ should only be done when not connected to the external network
+ as a troubleshooting step.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
></DIV
><DIV
@@ -1998,8 +2257,10 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1935"><B
->A.5.6. </B
+NAME="faq-db-synchronize"
+></A
+><B
+>A.5.5. </B
>
How do I synchronize bug information among multiple different Bugzilla
databases?
@@ -2033,14 +2294,18 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-nt">6. Bugzilla and Win32</H3
+NAME="faq-nt"
+></A
+>6. Bugzilla and Win32</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1944"><B
+NAME="faq-nt-easiest"
+></A
+><B
>A.6.1. </B
>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
@@ -2063,7 +2328,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1949"><B
+NAME="faq-nt-bundle"
+></A
+><B
>A.6.2. </B
>
Is there a "Bundle::Bugzilla" equivalent for Win32?
@@ -2087,7 +2354,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1954"><B
+NAME="faq-nt-mappings"
+></A
+><B
>A.6.3. </B
>
CGI's are failing with a "something.cgi is not a valid Windows NT
@@ -2108,7 +2377,9 @@ CLASS="answer"
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1959"><BLOCKQUOTE
+NAME="AEN2049"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> "Set application mappings. In the ISM, map the extension for the script
@@ -2131,7 +2402,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1962"><B
+NAME="faq-nt-dbi"
+></A
+><B
>A.6.4. </B
>
I'm having trouble with the perl modules for NT not being able to talk to
@@ -2197,14 +2470,18 @@ TARGET="_top"
CLASS="qandadiv"
><H3
><A
-NAME="faq-use">7. Bugzilla Usage</H3
+NAME="faq-use"
+></A
+>7. Bugzilla Usage</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN1983"><B
+NAME="faq-use-changeaddress"
+></A
+><B
>A.7.1. </B
>
How do I change my user name (email address) in Bugzilla?
@@ -2227,7 +2504,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1988"><B
+NAME="faq-use-query"
+></A
+><B
>A.7.2. </B
>
The query page is very confusing. Isn't there a simpler way to query?
@@ -2251,7 +2530,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN1993"><B
+NAME="faq-use-accept"
+></A
+><B
>A.7.3. </B
>
I'm confused by the behavior of the "accept" button in the Show Bug form.
@@ -2304,7 +2585,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN2003"><B
+NAME="faq-use-attachment"
+></A
+><B
>A.7.4. </B
>
I can't upload anything into the database via the "Create Attachment"
@@ -2329,33 +2612,10 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN2008"><B
->A.7.5. </B
->
- Email submissions to Bugzilla that have attachments end up asking me to
- save it as a "cgi" file.
- </P
-></DIV
-><DIV
-CLASS="answer"
-><P
+NAME="faq-use-keyword"
+></A
><B
-> </B
->
- Yup. Just rename it once you download it, or save it under a different
- filename. This will not be fixed anytime soon, because it would
- cripple some other functionality.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN2013"><B
->A.7.6. </B
+>A.7.5. </B
>
How do I change a keyword in Bugzilla, once some bugs are using it?
</P
@@ -2377,14 +2637,18 @@ CLASS="answer"
CLASS="qandadiv"
><H3
><A
-NAME="faq-hacking">8. Bugzilla Hacking</H3
+NAME="faq-hacking"
+></A
+>8. Bugzilla Hacking</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="AEN2020"><B
+NAME="faq-hacking-bugzillabugs"
+></A
+><B
>A.8.1. </B
>
What bugs are in Bugzilla right now?
@@ -2413,7 +2677,7 @@ TARGET="_top"
This list includes bugs for the 2.18 release that have already
been fixed and checked into CVS. Please consult the
<A
-HREF="http://www.mozilla.org/projects/bugzilla/"
+HREF="http://www.bugzilla.org/"
TARGET="_top"
> Bugzilla Project Page</A
> for details on how to
@@ -2428,7 +2692,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN2029"><B
+NAME="faq-hacking-priority"
+></A
+><B
>A.8.2. </B
>
How can I change the default priority to a null value? For instance, have the default
@@ -2458,7 +2724,9 @@ CLASS="qandaentry"
CLASS="question"
><P
><A
-NAME="AEN2035"><B
+NAME="faq-hacking-patches"
+></A
+><B
>A.8.3. </B
>
What's the best way to submit patches? What guidelines should I follow?
diff --git a/docs/html/gfdl-0.html b/docs/html/gfdl-0.html
new file mode 100644
index 0000000000000000000000000000000000000000..9df3f52b6e85772629b1871e9f98e35f0275db1a
--- /dev/null
+++ b/docs/html/gfdl-0.html
@@ -0,0 +1,165 @@
+<HTML
+><HEAD
+><TITLE
+>PREAMBLE</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="NEXT"
+TITLE="APPLICABILITY AND DEFINITIONS"
+HREF="gfdl-1.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-1.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-0"
+></A
+>0. PREAMBLE</H1
+><P
+>The purpose of this License is to make a manual, textbook, or other
+ written document "free" in the sense of freedom: to assure everyone the
+ effective freedom to copy and redistribute it, with or without modifying
+ it, either commercially or noncommercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for their
+ work, while not being considered responsible for modifications made by
+ others.</P
+><P
+>This License is a kind of "copyleft", which means that derivative
+ works of the document must themselves be free in the same sense. It
+ complements the GNU General Public License, which is a copyleft license
+ designed for free software.</P
+><P
+>We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a free
+ program should come with manuals providing the same freedoms that the
+ software does. But this License is not limited to software manuals; it
+ can be used for any textual work, regardless of subject matter or whether
+ it is published as a printed book. We recommend this License principally
+ for works whose purpose is instruction or reference.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-1.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>GNU Free Documentation License</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>APPLICABILITY AND DEFINITIONS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-1.html b/docs/html/gfdl-1.html
new file mode 100644
index 0000000000000000000000000000000000000000..8c611d6dfd30100bc881f7f361960022bb71762a
--- /dev/null
+++ b/docs/html/gfdl-1.html
@@ -0,0 +1,200 @@
+<HTML
+><HEAD
+><TITLE
+>APPLICABILITY AND DEFINITIONS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="PREAMBLE"
+HREF="gfdl-0.html"><LINK
+REL="NEXT"
+TITLE="VERBATIM COPYING"
+HREF="gfdl-2.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-0.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-2.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-1"
+></A
+>1. APPLICABILITY AND DEFINITIONS</H1
+><P
+>This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be distributed under
+ the terms of this License. The "Document", below, refers to any such
+ manual or work. Any member of the public is a licensee, and is addressed
+ as "you".</P
+><P
+>A "Modified Version" of the Document means any work containing the
+ Document or a portion of it, either copied verbatim, or with
+ modifications and/or translated into another language.</P
+><P
+>A "Secondary Section" is a named appendix or a front-matter section
+ of the Document that deals exclusively with the relationship of the
+ publishers or authors of the Document to the Document's overall subject
+ (or to related matters) and contains nothing that could fall directly
+ within that overall subject. (For example, if the Document is in part a
+ textbook of mathematics, a Secondary Section may not explain any
+ mathematics.) The relationship could be a matter of historical connection
+ with the subject or with related matters, or of legal, commercial,
+ philosophical, ethical or political position regarding them.</P
+><P
+>The "Invariant Sections" are certain Secondary Sections whose
+ titles are designated, as being those of Invariant Sections, in the
+ notice that says that the Document is released under this License.</P
+><P
+>The "Cover Texts" are certain short passages of text that are
+ listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
+ that the Document is released under this License.</P
+><P
+>A "Transparent" copy of the Document means a machine-readable copy,
+ represented in a format whose specification is available to the general
+ public, whose contents can be viewed and edited directly and
+ straightforwardly with generic text editors or (for images composed of
+ pixels) generic paint programs or (for drawings) some widely available
+ drawing editor, and that is suitable for input to text formatters or for
+ automatic translation to a variety of formats suitable for input to text
+ formatters. A copy made in an otherwise Transparent file format whose
+ markup has been designed to thwart or discourage subsequent modification
+ by readers is not Transparent. A copy that is not "Transparent" is called
+ "Opaque".</P
+><P
+>Examples of suitable formats for Transparent copies include plain
+ ASCII without markup, Texinfo input format, LaTeX input format, SGML or
+ XML using a publicly available DTD, and standard-conforming simple HTML
+ designed for human modification. Opaque formats include PostScript, PDF,
+ proprietary formats that can be read and edited only by proprietary word
+ processors, SGML or XML for which the DTD and/or processing tools are not
+ generally available, and the machine-generated HTML produced by some word
+ processors for output purposes only.</P
+><P
+>The "Title Page" means, for a printed book, the title page itself,
+ plus such following pages as are needed to hold, legibly, the material
+ this License requires to appear in the title page. For works in formats
+ which do not have any title page as such, "Title Page" means the text
+ near the most prominent appearance of the work's title, preceding the
+ beginning of the body of the text.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-0.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-2.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>PREAMBLE</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>VERBATIM COPYING</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-10.html b/docs/html/gfdl-10.html
new file mode 100644
index 0000000000000000000000000000000000000000..9ab07bdb1adf8b4508b9eacbce41da08e7b8ca7c
--- /dev/null
+++ b/docs/html/gfdl-10.html
@@ -0,0 +1,165 @@
+<HTML
+><HEAD
+><TITLE
+>FUTURE REVISIONS OF THIS LICENSE</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="TERMINATION"
+HREF="gfdl-9.html"><LINK
+REL="NEXT"
+TITLE="How to use this License for your documents"
+HREF="gfdl-howto.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-9.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-howto.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-10"
+></A
+>10. FUTURE REVISIONS OF THIS LICENSE</H1
+><P
+>The Free Software Foundation may publish new, revised versions of
+ the GNU Free Documentation License from time to time. Such new versions
+ will be similar in spirit to the present version, but may differ in
+ detail to address new problems or concerns. See
+ <A
+HREF="http://www.gnu.org/copyleft/"
+TARGET="_top"
+> http://www.gnu.org/copyleft/</A
+>
+
+ .</P
+><P
+>Each version of the License is given a distinguishing version
+ number. If the Document specifies that a particular numbered version of
+ this License "or any later version" applies to it, you have the option of
+ following the terms and conditions either of that specified version or of
+ any later version that has been published (not as a draft) by the Free
+ Software Foundation. If the Document does not specify a version number of
+ this License, you may choose any version ever published (not as a draft)
+ by the Free Software Foundation.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-9.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-howto.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>TERMINATION</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to use this License for your documents</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-2.html b/docs/html/gfdl-2.html
new file mode 100644
index 0000000000000000000000000000000000000000..0e7b592832476c6e6fa4ee5013ba742e49155869
--- /dev/null
+++ b/docs/html/gfdl-2.html
@@ -0,0 +1,157 @@
+<HTML
+><HEAD
+><TITLE
+>VERBATIM COPYING</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="APPLICABILITY AND DEFINITIONS"
+HREF="gfdl-1.html"><LINK
+REL="NEXT"
+TITLE="COPYING IN QUANTITY"
+HREF="gfdl-3.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-1.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-3.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-2"
+></A
+>2. VERBATIM COPYING</H1
+><P
+>You may copy and distribute the Document in any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License applies to
+ the Document are reproduced in all copies, and that you add no other
+ conditions whatsoever to those of this License. You may not use technical
+ measures to obstruct or control the reading or further copying of the
+ copies you make or distribute. However, you may accept compensation in
+ exchange for copies. If you distribute a large enough number of copies
+ you must also follow the conditions in section 3.</P
+><P
+>You may also lend copies, under the same conditions stated above,
+ and you may publicly display copies.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-1.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-3.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>APPLICABILITY AND DEFINITIONS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>COPYING IN QUANTITY</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-3.html b/docs/html/gfdl-3.html
new file mode 100644
index 0000000000000000000000000000000000000000..eb6f8bef89bf2c8920646d877e543ae87b7a4159
--- /dev/null
+++ b/docs/html/gfdl-3.html
@@ -0,0 +1,179 @@
+<HTML
+><HEAD
+><TITLE
+>COPYING IN QUANTITY</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="VERBATIM COPYING"
+HREF="gfdl-2.html"><LINK
+REL="NEXT"
+TITLE="MODIFICATIONS"
+HREF="gfdl-4.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-2.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-4.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-3"
+></A
+>3. COPYING IN QUANTITY</H1
+><P
+>If you publish printed copies of the Document numbering more than
+ 100, and the Document's license notice requires Cover Texts, you must
+ enclose the copies in covers that carry, clearly and legibly, all these
+ Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
+ on the back cover. Both covers must also clearly and legibly identify you
+ as the publisher of these copies. The front cover must present the full
+ title with all words of the title equally prominent and visible. You may
+ add other material on the covers in addition. Copying with changes
+ limited to the covers, as long as they preserve the title of the Document
+ and satisfy these conditions, can be treated as verbatim copying in other
+ respects.</P
+><P
+>If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit reasonably)
+ on the actual cover, and continue the rest onto adjacent pages.</P
+><P
+>If you publish or distribute Opaque copies of the Document
+ numbering more than 100, you must either include a machine-readable
+ Transparent copy along with each Opaque copy, or state in or with each
+ Opaque copy a publicly-accessible computer-network location containing a
+ complete Transparent copy of the Document, free of added material, which
+ the general network-using public has access to download anonymously at no
+ charge using public-standard network protocols. If you use the latter
+ option, you must take reasonably prudent steps, when you begin
+ distribution of Opaque copies in quantity, to ensure that this
+ Transparent copy will remain thus accessible at the stated location until
+ at least one year after the last time you distribute an Opaque copy
+ (directly or through your agents or retailers) of that edition to the
+ public.</P
+><P
+>It is requested, but not required, that you contact the authors of
+ the Document well before redistributing any large number of copies, to
+ give them a chance to provide you with an updated version of the
+ Document.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-2.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-4.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>VERBATIM COPYING</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>MODIFICATIONS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-4.html b/docs/html/gfdl-4.html
new file mode 100644
index 0000000000000000000000000000000000000000..282817958e18259159b93eb2bd75bbe369c9c844
--- /dev/null
+++ b/docs/html/gfdl-4.html
@@ -0,0 +1,273 @@
+<HTML
+><HEAD
+><TITLE
+>MODIFICATIONS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="COPYING IN QUANTITY"
+HREF="gfdl-3.html"><LINK
+REL="NEXT"
+TITLE="COMBINING DOCUMENTS"
+HREF="gfdl-5.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-3.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-5.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-4"
+></A
+>4. MODIFICATIONS</H1
+><P
+>You may copy and distribute a Modified Version of the Document
+ under the conditions of sections 2 and 3 above, provided that you release
+ the Modified Version under precisely this License, with the Modified
+ Version filling the role of the Document, thus licensing distribution and
+ modification of the Modified Version to whoever possesses a copy of it.
+ In addition, you must do these things in the Modified Version:</P
+><P
+></P
+><OL
+TYPE="A"
+><LI
+><P
+>Use in the Title Page (and on the covers, if any) a title
+ distinct from that of the Document, and from those of previous
+ versions (which should, if there were any, be listed in the History
+ section of the Document). You may use the same title as a previous
+ version if the original publisher of that version gives
+ permission.</P
+></LI
+><LI
+><P
+>List on the Title Page, as authors, one or more persons or
+ entities responsible for authorship of the modifications in the
+ Modified Version, together with at least five of the principal
+ authors of the Document (all of its principal authors, if it has less
+ than five).</P
+></LI
+><LI
+><P
+>State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.</P
+></LI
+><LI
+><P
+>Preserve all the copyright notices of the Document.</P
+></LI
+><LI
+><P
+>Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.</P
+></LI
+><LI
+><P
+>Include, immediately after the copyright notices, a license
+ notice giving the public permission to use the Modified Version under
+ the terms of this License, in the form shown in the Addendum
+ below.</P
+></LI
+><LI
+><P
+>Preserve in that license notice the full lists of Invariant
+ Sections and required Cover Texts given in the Document's license
+ notice.</P
+></LI
+><LI
+><P
+>Include an unaltered copy of this License.</P
+></LI
+><LI
+><P
+>Preserve the section entitled "History", and its title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.</P
+></LI
+><LI
+><P
+>Preserve the network location, if any, given in the Document
+ for public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions it
+ was based on. These may be placed in the "History" section. You may
+ omit a network location for a work that was published at least four
+ years before the Document itself, or if the original publisher of the
+ version it refers to gives permission.</P
+></LI
+><LI
+><P
+>In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements and/or
+ dedications given therein.</P
+></LI
+><LI
+><P
+>Preserve all the Invariant Sections of the Document, unaltered
+ in their text and in their titles. Section numbers or the equivalent
+ are not considered part of the section titles.</P
+></LI
+><LI
+><P
+>Delete any section entitled "Endorsements". Such a section may
+ not be included in the Modified Version.</P
+></LI
+><LI
+><P
+>Do not retitle any existing section as "Endorsements" or to
+ conflict in title with any Invariant Section.</P
+></LI
+></OL
+><P
+>If the Modified Version includes new front-matter sections or
+ appendices that qualify as Secondary Sections and contain no material
+ copied from the Document, you may at your option designate some or all of
+ these sections as invariant. To do this, add their titles to the list of
+ Invariant Sections in the Modified Version's license notice. These titles
+ must be distinct from any other section titles.</P
+><P
+>You may add a section entitled "Endorsements", provided it contains
+ nothing but endorsements of your Modified Version by various parties--for
+ example, statements of peer review or that the text has been approved by
+ an organization as the authoritative definition of a standard.</P
+><P
+>You may add a passage of up to five words as a Front-Cover Text,
+ and a passage of up to 25 words as a Back-Cover Text, to the end of the
+ list of Cover Texts in the Modified Version. Only one passage of
+ Front-Cover Text and one of Back-Cover Text may be added by (or through
+ arrangements made by) any one entity. If the Document already includes a
+ cover text for the same cover, previously added by you or by arrangement
+ made by the same entity you are acting on behalf of, you may not add
+ another; but you may replace the old one, on explicit permission from the
+ previous publisher that added the old one.</P
+><P
+>The author(s) and publisher(s) of the Document do not by this
+ License give permission to use their names for publicity for or to assert
+ or imply endorsement of any Modified Version.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-3.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-5.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>COPYING IN QUANTITY</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>COMBINING DOCUMENTS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-5.html b/docs/html/gfdl-5.html
new file mode 100644
index 0000000000000000000000000000000000000000..943cce21983b24ba4e39bd1bb4c0fa979ad14835
--- /dev/null
+++ b/docs/html/gfdl-5.html
@@ -0,0 +1,166 @@
+<HTML
+><HEAD
+><TITLE
+>COMBINING DOCUMENTS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="MODIFICATIONS"
+HREF="gfdl-4.html"><LINK
+REL="NEXT"
+TITLE="COLLECTIONS OF DOCUMENTS"
+HREF="gfdl-6.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-4.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-6.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-5"
+></A
+>5. COMBINING DOCUMENTS</H1
+><P
+>You may combine the Document with other documents released under
+ this License, under the terms defined in section 4 above for modified
+ versions, provided that you include in the combination all of the
+ Invariant Sections of all of the original documents, unmodified, and list
+ them all as Invariant Sections of your combined work in its license
+ notice.</P
+><P
+>The combined work need only contain one copy of this License, and
+ multiple identical Invariant Sections may be replaced with a single copy.
+ If there are multiple Invariant Sections with the same name but different
+ contents, make the title of each such section unique by adding at the end
+ of it, in parentheses, the name of the original author or publisher of
+ that section if known, or else a unique number. Make the same adjustment
+ to the section titles in the list of Invariant Sections in the license
+ notice of the combined work.</P
+><P
+>In the combination, you must combine any sections entitled
+ "History" in the various original documents, forming one section entitled
+ "History"; likewise combine any sections entitled "Acknowledgements", and
+ any sections entitled "Dedications". You must delete all sections
+ entitled "Endorsements."</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-4.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-6.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>MODIFICATIONS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>COLLECTIONS OF DOCUMENTS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-6.html b/docs/html/gfdl-6.html
new file mode 100644
index 0000000000000000000000000000000000000000..82219372d6b059ad571c3cdce6fe96ecc979406e
--- /dev/null
+++ b/docs/html/gfdl-6.html
@@ -0,0 +1,156 @@
+<HTML
+><HEAD
+><TITLE
+>COLLECTIONS OF DOCUMENTS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="COMBINING DOCUMENTS"
+HREF="gfdl-5.html"><LINK
+REL="NEXT"
+TITLE="AGGREGATION WITH INDEPENDENT WORKS"
+HREF="gfdl-7.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-5.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-7.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-6"
+></A
+>6. COLLECTIONS OF DOCUMENTS</H1
+><P
+>You may make a collection consisting of the Document and other
+ documents released under this License, and replace the individual copies
+ of this License in the various documents with a single copy that is
+ included in the collection, provided that you follow the rules of this
+ License for verbatim copying of each of the documents in all other
+ respects.</P
+><P
+>You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you insert a copy
+ of this License into the extracted document, and follow this License in
+ all other respects regarding verbatim copying of that document.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-5.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-7.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>COMBINING DOCUMENTS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>AGGREGATION WITH INDEPENDENT WORKS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-7.html b/docs/html/gfdl-7.html
new file mode 100644
index 0000000000000000000000000000000000000000..5fb7e44336f5f74caf380cdf6f481b54054518ef
--- /dev/null
+++ b/docs/html/gfdl-7.html
@@ -0,0 +1,159 @@
+<HTML
+><HEAD
+><TITLE
+>AGGREGATION WITH INDEPENDENT WORKS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="COLLECTIONS OF DOCUMENTS"
+HREF="gfdl-6.html"><LINK
+REL="NEXT"
+TITLE="TRANSLATION"
+HREF="gfdl-8.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-6.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-8.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-7"
+></A
+>7. AGGREGATION WITH INDEPENDENT WORKS</H1
+><P
+>A compilation of the Document or its derivatives with other
+ separate and independent documents or works, in or on a volume of a
+ storage or distribution medium, does not as a whole count as a Modified
+ Version of the Document, provided no compilation copyright is claimed for
+ the compilation. Such a compilation is called an "aggregate", and this
+ License does not apply to the other self-contained works thus compiled
+ with the Document, on account of their being thus compiled, if they are
+ not themselves derivative works of the Document.</P
+><P
+>If the Cover Text requirement of section 3 is applicable to these
+ copies of the Document, then if the Document is less than one quarter of
+ the entire aggregate, the Document's Cover Texts may be placed on covers
+ that surround only the Document within the aggregate. Otherwise they must
+ appear on covers around the whole aggregate.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-6.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-8.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>COLLECTIONS OF DOCUMENTS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>TRANSLATION</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-8.html b/docs/html/gfdl-8.html
new file mode 100644
index 0000000000000000000000000000000000000000..c2b9526faec899fd0b454d15ea723f072a1c4c97
--- /dev/null
+++ b/docs/html/gfdl-8.html
@@ -0,0 +1,155 @@
+<HTML
+><HEAD
+><TITLE
+>TRANSLATION</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="AGGREGATION WITH INDEPENDENT WORKS"
+HREF="gfdl-7.html"><LINK
+REL="NEXT"
+TITLE="TERMINATION"
+HREF="gfdl-9.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-7.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-9.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-8"
+></A
+>8. TRANSLATION</H1
+><P
+>Translation is considered a kind of modification, so you may
+ distribute translations of the Document under the terms of section 4.
+ Replacing Invariant Sections with translations requires special
+ permission from their copyright holders, but you may include translations
+ of some or all Invariant Sections in addition to the original versions of
+ these Invariant Sections. You may include a translation of this License
+ provided that you also include the original English version of this
+ License. In case of a disagreement between the translation and the
+ original English version of this License, the original English version
+ will prevail.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-7.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-9.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>AGGREGATION WITH INDEPENDENT WORKS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>TERMINATION</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-9.html b/docs/html/gfdl-9.html
new file mode 100644
index 0000000000000000000000000000000000000000..ca5f57153008c384a2aa549f88d2c53c446157be
--- /dev/null
+++ b/docs/html/gfdl-9.html
@@ -0,0 +1,152 @@
+<HTML
+><HEAD
+><TITLE
+>TERMINATION</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="TRANSLATION"
+HREF="gfdl-8.html"><LINK
+REL="NEXT"
+TITLE="FUTURE REVISIONS OF THIS LICENSE"
+HREF="gfdl-10.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-8.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-10.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-9"
+></A
+>9. TERMINATION</H1
+><P
+>You may not copy, modify, sublicense, or distribute the Document
+ except as expressly provided for under this License. Any other attempt to
+ copy, modify, sublicense or distribute the Document is void, and will
+ automatically terminate your rights under this License. However, parties
+ who have received copies, or rights, from you under this License will not
+ have their licenses terminated so long as such parties remain in full
+ compliance.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-8.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-10.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>TRANSLATION</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>FUTURE REVISIONS OF THIS LICENSE</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl-howto.html b/docs/html/gfdl-howto.html
new file mode 100644
index 0000000000000000000000000000000000000000..9e760fc5fc33ea0495765902793d039d98dc4e7f
--- /dev/null
+++ b/docs/html/gfdl-howto.html
@@ -0,0 +1,172 @@
+<HTML
+><HEAD
+><TITLE
+>How to use this License for your documents</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"><LINK
+REL="PREVIOUS"
+TITLE="FUTURE REVISIONS OF THIS LICENSE"
+HREF="gfdl-10.html"><LINK
+REL="NEXT"
+TITLE="Glossary"
+HREF="glossary.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="gfdl-10.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix E. GNU Free Documentation License</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="glossary.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="gfdl-howto"
+></A
+>How to use this License for your documents</H1
+><P
+>To use this License in a document you have written, include a copy
+ of the License in the document and put the following copyright and
+ license notices just after the title page:</P
+><A
+NAME="AEN2367"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
+ distribute and/or modify this document under the terms of the GNU Free
+ Documentation License, Version 1.1 or any later version published by
+ the Free Software Foundation; with the Invariant Sections being LIST
+ THEIR TITLES, with the Front-Cover Texts being LIST, and with the
+ Back-Cover Texts being LIST. A copy of the license is included in the
+ section entitled "GNU Free Documentation License".</P
+></BLOCKQUOTE
+><P
+>If you have no Invariant Sections, write "with no Invariant
+ Sections" instead of saying which ones are invariant. If you have no
+ Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
+ Texts being LIST"; likewise for Back-Cover Texts.</P
+><P
+>If your document contains nontrivial examples of program code, we
+ recommend releasing these examples in parallel under your choice of free
+ software license, such as the GNU General Public License, to permit their
+ use in free software.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="gfdl-10.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="glossary.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>FUTURE REVISIONS OF THIS LICENSE</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Glossary</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html
new file mode 100644
index 0000000000000000000000000000000000000000..d7a9ffe2c3a7d36179aa9285b59852a5ef5a5e6c
--- /dev/null
+++ b/docs/html/gfdl.html
@@ -0,0 +1,218 @@
+<HTML
+><HEAD
+><TITLE
+>GNU Free Documentation License</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
+HREF="index.html"><LINK
+REL="PREVIOUS"
+TITLE="SourceForge"
+HREF="variant-sourceforge.html"><LINK
+REL="NEXT"
+TITLE="PREAMBLE"
+HREF="gfdl-0.html"></HEAD
+><BODY
+CLASS="appendix"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.16.3 Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="variant-sourceforge.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl-0.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="appendix"
+><H1
+><A
+NAME="gfdl"
+></A
+>Appendix E. GNU Free Documentation License</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>0. <A
+HREF="gfdl-0.html"
+>PREAMBLE</A
+></DT
+><DT
+>1. <A
+HREF="gfdl-1.html"
+>APPLICABILITY AND DEFINITIONS</A
+></DT
+><DT
+>2. <A
+HREF="gfdl-2.html"
+>VERBATIM COPYING</A
+></DT
+><DT
+>3. <A
+HREF="gfdl-3.html"
+>COPYING IN QUANTITY</A
+></DT
+><DT
+>4. <A
+HREF="gfdl-4.html"
+>MODIFICATIONS</A
+></DT
+><DT
+>5. <A
+HREF="gfdl-5.html"
+>COMBINING DOCUMENTS</A
+></DT
+><DT
+>6. <A
+HREF="gfdl-6.html"
+>COLLECTIONS OF DOCUMENTS</A
+></DT
+><DT
+>7. <A
+HREF="gfdl-7.html"
+>AGGREGATION WITH INDEPENDENT WORKS</A
+></DT
+><DT
+>8. <A
+HREF="gfdl-8.html"
+>TRANSLATION</A
+></DT
+><DT
+>9. <A
+HREF="gfdl-9.html"
+>TERMINATION</A
+></DT
+><DT
+>10. <A
+HREF="gfdl-10.html"
+>FUTURE REVISIONS OF THIS LICENSE</A
+></DT
+><DT
+><A
+HREF="gfdl-howto.html"
+>How to use this License for your documents</A
+></DT
+></DL
+></DIV
+><P
+>Version 1.1, March 2000</P
+><A
+NAME="AEN2277"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
+ Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
+ distribute verbatim copies of this license document, but changing it is
+ not allowed.</P
+></BLOCKQUOTE
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant-sourceforge.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl-0.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>SourceForge</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>PREAMBLE</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/glossary.html b/docs/html/glossary.html
index c6251cb6097c696e8dc89170cded8f5814bc5e34..06257255b96d61d787b5cca7366a78c77a43e35b 100644
--- a/docs/html/glossary.html
+++ b/docs/html/glossary.html
@@ -7,11 +7,11 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="SourceForge"
-HREF="variant-sourceforge.html"></HEAD
+TITLE="How to use this License for your documents"
+HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="glossary"
BGCOLOR="#FFFFFF"
@@ -31,7 +31,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -39,7 +39,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="variant-sourceforge.html"
+HREF="gfdl-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -62,13 +62,17 @@ WIDTH="100%"></DIV
CLASS="GLOSSARY"
><H1
><A
-NAME="glossary">Glossary</H1
+NAME="glossary"
+></A
+>Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2183">0-9, high ascii</H1
+NAME="AEN2372"
+></A
+>0-9, high ascii</H1
><DL
><DT
><B
@@ -100,7 +104,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-a">A</H1
+NAME="gloss-a"
+></A
+>A</H1
><DL
><DT
><B
@@ -130,6 +136,110 @@ CLASS="acronym"
>
world-wide-web server.</P
+><P
+></P
+><DIV
+CLASS="variablelist"
+><P
+><B
+>Useful Directives when configuring Bugzilla</B
+></P
+><DL
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
+TARGET="_top"
+>AddHandler</A
+></TT
+></DT
+><DD
+><P
+>Tell Apache that it's OK to run CGI scripts.</P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
+TARGET="_top"
+>AllowOverride</A
+></TT
+>, <TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
+TARGET="_top"
+>Options</A
+></TT
+></DT
+><DD
+><P
+>These directives are used to tell Apache many things about
+ the directory they apply to. For Bugzilla's purposes, we need
+ them to allow script execution and <TT
+CLASS="filename"
+>.htaccess</TT
+>
+ overrides.
+ </P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
+TARGET="_top"
+>DirectoryIndex</A
+></TT
+></DT
+><DD
+><P
+>Used to tell Apache what files are indexes. If you can
+ not add <TT
+CLASS="filename"
+>index.cgi</TT
+> to the list of valid files,
+ you'll need to set <TT
+CLASS="computeroutput"
+>$index_html</TT
+> to
+ 1 in <TT
+CLASS="filename"
+>localconfig</TT
+> so
+ <B
+CLASS="command"
+>./checksetup.pl</B
+> will create an
+ <TT
+CLASS="filename"
+>index.html</TT
+> that redirects to
+ <TT
+CLASS="filename"
+>index.cgi</TT
+>.
+ </P
+></DD
+><DT
+><TT
+CLASS="computeroutput"
+><A
+HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
+TARGET="_top"
+>ScriptInterpreterSource</A
+></TT
+></DT
+><DD
+><P
+>Used when running Apache on windows so the shebang line
+ doesn't have to be changed in every Bugzilla script.
+ </P
+></DD
+></DL
+></DIV
></DD
></DL
></DIV
@@ -138,7 +248,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-b">B</H1
+NAME="gloss-b"
+></A
+>B</H1
><DL
><DT
><B
@@ -177,6 +289,9 @@ CLASS="QUOTE"
"Find" box.</P
></DD
><DT
+><A
+NAME="gloss-bugzilla"
+></A
><B
>Bugzilla</B
></DT
@@ -192,11 +307,35 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-c"></H1
+NAME="gloss-c"
+></A
+>C</H1
><DL
><DT
><A
-NAME="gloss-component"><B
+NAME="gloss-cgi"
+></A
+><B
+>Common Gateway Interface</B
+></DT
+> (CGI)<DD
+><P
+><SPAN
+CLASS="acronym"
+>CGI</SPAN
+> is an acronym for Common Gateway Interface.
+ This is a standard for interfacing an external application with a web
+ server. Bugzilla is an example of a <SPAN
+CLASS="acronym"
+>CGI</SPAN
+> application.
+ </P
+></DD
+><DT
+><A
+NAME="gloss-component"
+></A
+><B
>Component</B
></DT
><DD
@@ -208,7 +347,9 @@ NAME="gloss-component"><B
></DD
><DT
><A
-NAME="gloss-cpan"><B
+NAME="gloss-cpan"
+></A
+><B
> <SPAN
CLASS="acronym"
>CPAN</SPAN
@@ -242,7 +383,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-d">D</H1
+NAME="gloss-d"
+></A
+>D</H1
><DL
><DT
><B
@@ -271,7 +414,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-g"></H1
+NAME="gloss-g"
+></A
+>G</H1
><DL
><DT
><B
@@ -306,24 +451,83 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-m">M</H1
+NAME="gloss-m"
+></A
+>M</H1
><DL
><DT
+><A
+NAME="gloss-mta"
+></A
><B
->mysqld</B
+>Message Transport Agent</B
+></DT
+> (MTA)<DD
+><P
+>A Message Transport Agent is used to control the flow of email
+ on a system. Many unix based systems use
+ <A
+HREF="http://www.sendmail.org"
+TARGET="_top"
+>sendmail</A
+> which is what
+ Bugzilla expects to find by default at <TT
+CLASS="filename"
+>/usr/sbin/sendmail</TT
+>.
+ Many other MTA's will work, but they all require that the
+ <TT
+CLASS="option"
+>sendmailnow</TT
+> param be set to <TT
+CLASS="literal"
+>on</TT
+>.
+ </P
+></DD
+><DT
+><A
+NAME="gloss-mysql"
+></A
+><B
+>MySQL</B
></DT
><DD
><P
->mysqld is the name of the
- <I
+>MySQL is currently the required
+ <A
+HREF="glossary.html#gloss-rdbms"
+><I
CLASS="glossterm"
->daemon</I
->
-
- for the MySQL database. In general, it is invoked automatically
- through the use of the System V init scripts on GNU/Linux and
- AT&T System V-based systems, such as Solaris and HP/UX, or
- through the RC scripts on BSD-based systems.</P
+>RDBMS</I
+></A
+> for Bugzilla. MySQL
+ can be downloaded from <A
+HREF="http://www.mysql.com"
+TARGET="_top"
+>http://www.mysql.com</A
+>. While you
+ should familiarize yourself with all of the documentation, some high
+ points are:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
+TARGET="_top"
+>MySQL
+ Privilege System</A
+> - Much more detailed information about
+ the suggestions in <A
+HREF="security.html#security-mysql"
+>Section 5.6.2</A
+>.
+ </P
+></LI
+></UL
></DD
></DL
></DIV
@@ -332,7 +536,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-p">P</H1
+NAME="gloss-p"
+></A
+>P</H1
><DL
><DT
><B
@@ -370,7 +576,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-q">Q</H1
+NAME="gloss-q"
+></A
+>Q</H1
><DL
><DT
><B
@@ -413,7 +621,33 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-s">S</H1
+NAME="gloss-r"
+></A
+>R</H1
+><DL
+><DT
+><A
+NAME="gloss-rdbms"
+></A
+><B
+>Relational DataBase Managment System</B
+></DT
+> (RDBMS)<DD
+><P
+>A relational database management system is a database system
+ that stores information in tables that are related to each other.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="glossdiv"
+><H1
+CLASS="glossdiv"
+><A
+NAME="gloss-s"
+></A
+>S</H1
><DL
><DT
><B
@@ -490,11 +724,15 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-t">T</H1
+NAME="gloss-t"
+></A
+>T</H1
><DL
><DT
><A
-NAME="gloss-target-milestone"><B
+NAME="gloss-target-milestone"
+></A
+><B
>Target Milestone</B
></DT
><DD
@@ -512,6 +750,21 @@ CLASS="QUOTE"
giving you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.</P
></DD
+><DT
+><A
+NAME="gloss-tcl"
+></A
+><B
+>Tool Command Language</B
+></DT
+> (TCL)<DD
+><P
+>TCL is an open source scripting language available for Windows,
+ Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
+ never released. The first release of Bugzilla was 2.0, which was when
+ it was ported to perl.
+ </P
+></DD
></DL
></DIV
><DIV
@@ -519,18 +772,76 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="gloss-z">Z</H1
+NAME="gloss-z"
+></A
+>Z</H1
><DL
><DT
><A
-NAME="zarro-boogs-found"><B
+NAME="gloss-zarro"
+></A
+><B
>Zarro Boogs Found</B
></DT
><DD
><P
->This is the cryptic response sent by Bugzilla when a query
- returned no results. It is just a goofy way of saying "Zero Bugs
- Found".</P
+>This is just a goofy way of saying that there were no bugs
+ found matching your query. When asked to explain this message,
+ Terry had the following to say:
+ </P
+><A
+NAME="AEN2566"
+></A
+><TABLE
+BORDER="0"
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="BLOCKQUOTE"
+><TR
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+> </TD
+><TD
+WIDTH="80%"
+VALIGN="TOP"
+><P
+>I've been asked to explain this ... way back when, when
+ Netscape released version 4.0 of its browser, we had a release
+ party. Naturally, there had been a big push to try and fix every
+ known bug before the release. Naturally, that hadn't actually
+ happened. (This is not unique to Netscape or to 4.0; the same thing
+ has happened with every software project I've ever seen.) Anyway,
+ at the release party, T-shirts were handed out that said something
+ like "Netscape 4.0: Zarro Boogs". Just like the software, the
+ T-shirt had no known bugs. Uh-huh.
+ </P
+><P
+>So, when you query for a list of bugs, and it gets no results,
+ you can think of this as a friendly reminder. Of *course* there are
+ bugs matching your query, they just aren't in the bugsystem yet...
+ </P
+></TD
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+> </TD
+></TR
+><TR
+><TD
+COLSPAN="2"
+ALIGN="RIGHT"
+VALIGN="TOP"
+>--<SPAN
+CLASS="attribution"
+>Terry Weissman</SPAN
+></TD
+><TD
+WIDTH="10%"
+> </TD
+></TR
+></TABLE
></DD
></DL
></DIV
@@ -551,7 +862,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="variant-sourceforge.html"
+HREF="gfdl-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -575,7 +886,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->SourceForge</TD
+>How to use this License for your documents</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/groups.html b/docs/html/groups.html
index 37d58d046c19ccdc690bbdbc0f524f97ca6db93a..abd7d0d2553dc5039b2289e5664b9aafac5c6a19 100644
--- a/docs/html/groups.html
+++ b/docs/html/groups.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="groups">5.5. Groups and Group Security</H1
+NAME="groups"
+></A
+>5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
diff --git a/docs/html/hintsandtips.html b/docs/html/hintsandtips.html
index c20131bd4f9e56b4c3e1d4c124ba038dbe848041..f5115523321ad435c60d8ff37e1a14184d65fae0 100644
--- a/docs/html/hintsandtips.html
+++ b/docs/html/hintsandtips.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="hintsandtips">3.2. Hints and Tips</H1
+NAME="hintsandtips"
+></A
+>3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
@@ -82,7 +84,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN434">3.2.1. Autolinkification</H2
+NAME="AEN370"
+></A
+>3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
@@ -145,7 +149,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="quicksearch">3.2.2. Quicksearch</H2
+NAME="quicksearch"
+></A
+>3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
@@ -176,7 +182,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="commenting">3.2.3. Comments</H2
+NAME="commenting"
+></A
+>3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
@@ -198,7 +206,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="attachments">3.2.4. Attachments</H2
+NAME="attachments"
+></A
+>3.2.4. Attachments</H2
><P
> Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
@@ -222,7 +232,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN463">3.2.5. Filing Bugs</H2
+NAME="AEN399"
+></A
+>3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
diff --git a/docs/html/how.html b/docs/html/how.html
index 6d7018a0c09455ea140b8b0b37c6f2b6ca7e8ff9..d2a3e2ed4e1abe6df822e2e061aa1178a236ddd7 100644
--- a/docs/html/how.html
+++ b/docs/html/how.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="how">3.1. How do I use Bugzilla?</H1
+NAME="how"
+></A
+>3.1. How do I use Bugzilla?</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
@@ -92,7 +94,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount"
+></A
+>3.1.1. Create a Bugzilla Account</H2
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
@@ -160,7 +164,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="bug_page">3.1.2. Anatomy of a Bug</H2
+NAME="bug_page"
+></A
+>3.1.2. Anatomy of a Bug</H2
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
@@ -425,7 +431,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="query">3.1.3. Searching for Bugs</H2
+NAME="query"
+></A
+>3.1.3. Searching for Bugs</H2
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
@@ -458,7 +466,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="list">3.1.4. Bug Lists</H2
+NAME="list"
+></A
+>3.1.4. Bug Lists</H2
><P
>If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system - don't try
@@ -530,7 +540,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="bugreports">3.1.5. Filing Bugs</H2
+NAME="bugreports"
+></A
+>3.1.5. Filing Bugs</H2
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
diff --git a/docs/html/index.html b/docs/html/index.html
index 51024b628b1ea2fa489be3ed3b05abce588bf4d6..be41c717e519a0f6dd3478d1c450eb1ed4b14746 100644
--- a/docs/html/index.html
+++ b/docs/html/index.html
@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
->The Bugzilla Guide</TITLE
+>The Bugzilla Guide - 2.16.3 Release</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
@@ -37,25 +37,38 @@ ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
-NAME="index"><DIV
+NAME="index"
+></A
+><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
-NAME="AEN2">The Bugzilla Guide</H1
+NAME="AEN2"
+></A
+>The Bugzilla Guide - 2.16.3 Release</H1
><H3
CLASS="author"
><A
-NAME="AEN5">Matthew P. Barnson</H3
+NAME="AEN5"
+></A
+>Matthew P. Barnson</H3
><H3
CLASS="author"
><A
-NAME="AEN9">The Bugzilla Team</H3
+NAME="AEN9"
+></A
+>The Bugzilla Team</H3
+><P
+CLASS="pubdate"
+>2003-04-23<BR></P
><DIV
><DIV
CLASS="abstract"
><A
-NAME="AEN13"><P
+NAME="AEN14"
+></A
+><P
></P
><P
> This is the documentation for Bugzilla, the mozilla.org
@@ -67,7 +80,7 @@ NAME="AEN13"><P
><P
>
This documentation is maintained in DocBook 4.1.2 XML format.
- Changes are best submitted as plain text or SGML diffs, attached
+ Changes are best submitted as plain text or XML diffs, attached
to a bug filed in
<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
@@ -310,7 +323,7 @@ HREF="variants.html"
><DL
><DT
>D.1. <A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
>Red Hat Bugzilla</A
></DT
><DT
@@ -341,6 +354,75 @@ HREF="variant-sourceforge.html"
></DL
></DD
><DT
+>E. <A
+HREF="gfdl.html"
+>GNU Free Documentation License</A
+></DT
+><DD
+><DL
+><DT
+>0. <A
+HREF="gfdl-0.html"
+>PREAMBLE</A
+></DT
+><DT
+>1. <A
+HREF="gfdl-1.html"
+>APPLICABILITY AND DEFINITIONS</A
+></DT
+><DT
+>2. <A
+HREF="gfdl-2.html"
+>VERBATIM COPYING</A
+></DT
+><DT
+>3. <A
+HREF="gfdl-3.html"
+>COPYING IN QUANTITY</A
+></DT
+><DT
+>4. <A
+HREF="gfdl-4.html"
+>MODIFICATIONS</A
+></DT
+><DT
+>5. <A
+HREF="gfdl-5.html"
+>COMBINING DOCUMENTS</A
+></DT
+><DT
+>6. <A
+HREF="gfdl-6.html"
+>COLLECTIONS OF DOCUMENTS</A
+></DT
+><DT
+>7. <A
+HREF="gfdl-7.html"
+>AGGREGATION WITH INDEPENDENT WORKS</A
+></DT
+><DT
+>8. <A
+HREF="gfdl-8.html"
+>TRANSLATION</A
+></DT
+><DT
+>9. <A
+HREF="gfdl-9.html"
+>TERMINATION</A
+></DT
+><DT
+>10. <A
+HREF="gfdl-10.html"
+>FUTURE REVISIONS OF THIS LICENSE</A
+></DT
+><DT
+><A
+HREF="gfdl-howto.html"
+>How to use this License for your documents</A
+></DT
+></DL
+></DD
+><DT
><A
HREF="glossary.html"
>Glossary</A
@@ -353,26 +435,61 @@ CLASS="LOT"
CLASS="LOT"
><DT
><B
+>List of Figures</B
+></DT
+><DT
+>4-1. <A
+HREF="troubleshooting.html#trouble-filetemp-errors"
+>Other File::Temp error messages</A
+></DT
+><DT
+>4-2. <A
+HREF="troubleshooting.html#trouble-filetemp-patch"
+>Patch for File::Temp in Perl 5.6.0</A
+></DT
+></DL
+></DIV
+><DIV
+CLASS="LOT"
+><DL
+CLASS="LOT"
+><DT
+><B
>List of Examples</B
></DT
><DT
>4-1. <A
-HREF="win32.html#AEN989"
+HREF="win32.html#AEN861"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
-HREF="win32.html#AEN1002"
+HREF="win32.html#AEN874"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
-HREF="win32.html#AEN1184"
+HREF="win32.html#AEN1056"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
></DT
+><DT
+>5-1. <A
+HREF="upgrading.html#upgrade-cvs"
+>Upgrading using CVS</A
+></DT
+><DT
+>5-2. <A
+HREF="upgrading.html#upgrade-tarball"
+>Upgrading using the tarball</A
+></DT
+><DT
+>5-3. <A
+HREF="upgrading.html#upgrade-patches"
+>Upgrading using patches</A
+></DT
></DL
></DIV
></DIV
diff --git a/docs/html/installation.html b/docs/html/installation.html
index 2f27feedf790a9fd656a227f2f9479ef5d2fcd8e..a2a8d9fb6399f7be4b6d29ad9300f03d9b29bce0 100644
--- a/docs/html/installation.html
+++ b/docs/html/installation.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="User Preferences"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
-NAME="installation">Chapter 4. Installation</H1
+NAME="installation"
+></A
+>Chapter 4. Installation</H1
><DIV
CLASS="TOC"
><DL
@@ -86,12 +88,12 @@ HREF="stepbystep.html"
><DL
><DT
>4.1.1. <A
-HREF="stepbystep.html#AEN492"
+HREF="stepbystep.html#AEN428"
>Introduction</A
></DT
><DT
>4.1.2. <A
-HREF="stepbystep.html#AEN496"
+HREF="stepbystep.html#AEN432"
>Package List</A
></DT
><DT
@@ -111,22 +113,22 @@ HREF="stepbystep.html#perl-modules"
></DT
><DT
>4.1.6. <A
-HREF="stepbystep.html#AEN669"
+HREF="stepbystep.html#AEN605"
>HTTP Server</A
></DT
><DT
>4.1.7. <A
-HREF="stepbystep.html#AEN688"
+HREF="stepbystep.html#AEN624"
>Bugzilla</A
></DT
><DT
>4.1.8. <A
-HREF="stepbystep.html#AEN705"
+HREF="stepbystep.html#AEN641"
>Setting Up the MySQL Database</A
></DT
><DT
>4.1.9. <A
-HREF="stepbystep.html#AEN741"
+HREF="stepbystep.html#AEN679"
><TT
CLASS="filename"
>checksetup.pl</TT
@@ -134,12 +136,7 @@ CLASS="filename"
></DT
><DT
>4.1.10. <A
-HREF="stepbystep.html#AEN773"
->Securing MySQL</A
-></DT
-><DT
->4.1.11. <A
-HREF="stepbystep.html#AEN839"
+HREF="stepbystep.html#AEN711"
>Configuring Bugzilla</A
></DT
></DL
@@ -153,17 +150,17 @@ HREF="extraconfig.html"
><DL
><DT
>4.2.1. <A
-HREF="extraconfig.html#AEN845"
+HREF="extraconfig.html#AEN717"
>Dependency Charts</A
></DT
><DT
>4.2.2. <A
-HREF="extraconfig.html#AEN860"
+HREF="extraconfig.html#AEN732"
>Bug Graphs</A
></DT
><DT
>4.2.3. <A
-HREF="extraconfig.html#AEN873"
+HREF="extraconfig.html#AEN745"
>The Whining Cron</A
></DT
><DT
@@ -231,12 +228,12 @@ HREF="troubleshooting.html"
><DL
><DT
>4.5.1. <A
-HREF="troubleshooting.html#AEN1218"
+HREF="troubleshooting.html#AEN1090"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.5.2. <A
-HREF="troubleshooting.html#AEN1223"
+HREF="troubleshooting.html#AEN1095"
>DBD::Sponge::db prepare failed</A
></DT
><DT
@@ -244,6 +241,11 @@ HREF="troubleshooting.html#AEN1223"
HREF="troubleshooting.html#paranoid-security"
>cannot chdir(/var/spool/mqueue)</A
></DT
+><DT
+>4.5.4. <A
+HREF="troubleshooting.html#trouble-filetemp"
+>Your vendor has not defined Fcntl macro O_NOINHERIT</A
+></DT
></DL
></DD
></DL
diff --git a/docs/html/integration.html b/docs/html/integration.html
index 9a7c1c43292924b22161a407084c239aa31a7fb6..f71ac2e1456166da45a6296e852c8e173083efbe 100644
--- a/docs/html/integration.html
+++ b/docs/html/integration.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
+NAME="integration"
+></A
+>5.9. Integrating Bugzilla with Third-Party Tools</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="bonsai">5.9.1. Bonsai</H2
+NAME="bonsai"
+></A
+>5.9.1. Bonsai</H2
><P
>Bonsai is a web-based tool for managing
<A
@@ -103,7 +107,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="cvs">5.9.2. CVS</H2
+NAME="cvs"
+></A
+>5.9.2. CVS</H2
><P
>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.</P
@@ -116,8 +122,12 @@ CLASS="QUOTE"
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
><P
>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
@@ -134,7 +144,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="scm">5.9.3. Perforce SCM</H2
+NAME="scm"
+></A
+>5.9.3. Perforce SCM</H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
@@ -172,7 +184,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
+NAME="tinderbox"
+></A
+>5.9.4. Tinderbox/Tinderbox2</H2
><P
>We need Tinderbox integration information.</P
></DIV
diff --git a/docs/html/introduction.html b/docs/html/introduction.html
index 5240be0577cfacf38734c69c3a3a5314e5f4c018..da690e3a2e3eab03fb96230755e3a4ec5adfea4a 100644
--- a/docs/html/introduction.html
+++ b/docs/html/introduction.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Document Conventions"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
-NAME="introduction">Chapter 2. Introduction</H1
+NAME="introduction"
+></A
+>Chapter 2. Introduction</H1
><DIV
CLASS="TOC"
><DL
diff --git a/docs/html/newversions.html b/docs/html/newversions.html
index d9e4ba4bece7c07ff90b998b0858a833e88bdb46..513caf2ed67466019a154924682bec161553f3b4 100644
--- a/docs/html/newversions.html
+++ b/docs/html/newversions.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,42 +73,32 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="newversions">1.3. New Versions</H1
+NAME="newversions"
+></A
+>1.3. New Versions</H1
><P
-> This is the 2.16 version of The Bugzilla Guide. It is so named
- to match the current version of Bugzilla. If you are
+> This is the 2.16.3 version of The Bugzilla Guide. It is so named
+ to match the version of Bugzilla it is disributed with. If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
</P
><P
-> This document can be found in the following places:
- </P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> <A
-HREF="http://www.bugzilla.org/"
+> The newest version of this guide can always be found at <A
+HREF="http://www.bugzilla.org"
TARGET="_top"
>bugzilla.org</A
->
- </P
-></LI
-><LI
+>; including
+ documentation for past releases and the current development version.
+ </P
><P
-> <A
-HREF="http://www.linuxdoc.org/"
+> The documentation for the most recent stable release of Bugzilla can also
+ be found at
+ <A
+HREF="http://www.tldp.org"
TARGET="_top"
->The Linux
- Documentation Project</A
->
- </P
-></LI
-></UL
->
+>The Linux Documentation Project</A
+>.
</P
><P
> The latest version of this document can always be checked out via CVS.
diff --git a/docs/html/osx.html b/docs/html/osx.html
index 147cf3b6c374b037c22dce51cb445ff78994b793..62ed7445625946d8827690beba628509e9084447 100644
--- a/docs/html/osx.html
+++ b/docs/html/osx.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="osx">4.4. Mac OS X Installation Notes</H1
+NAME="osx"
+></A
+>4.4. Mac OS X Installation Notes</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
@@ -123,7 +125,7 @@ CLASS="command"
This should go through the motions of downloading the latest version of
the GD module, then it will open a shell and drop you into the build
directory. Apply <A
-HREF="../sgml/gd-makefile.patch"
+HREF="../xml/gd-makefile.patch"
TARGET="_top"
>this patch</A
>
diff --git a/docs/html/parameters.html b/docs/html/parameters.html
index 59455a0822353be044dcd55f62f4712830a70a66..ccfeca6cc4c48f09325ddab14c1bbcd28b49f9d2 100644
--- a/docs/html/parameters.html
+++ b/docs/html/parameters.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="parameters">5.1. Bugzilla Configuration</H1
+NAME="parameters"
+></A
+>5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
diff --git a/docs/html/patches.html b/docs/html/patches.html
index c2637937b97949d6d1a68ee9cc3a3298217daca2..8dc11972628fdc5722b3b3dff61a8f1c5a8e0ec6 100644
--- a/docs/html/patches.html
+++ b/docs/html/patches.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="MySQL Bugzilla Database Introduction"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -72,7 +72,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
-NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
+NAME="patches"
+></A
+>Appendix C. Useful Patches and Utilities for Bugzilla</H1
><DIV
CLASS="TOC"
><DL
diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html
index f047dbcaddeb8d166befc067a4fe017da89da30f..106d8a9a002045e9ae3af962ff1f260a11110076 100644
--- a/docs/html/programadmin.html
+++ b/docs/html/programadmin.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
+NAME="programadmin"
+></A
+>5.3. Product, Component, Milestone, and Version Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="products">5.3.1. Products</H2
+NAME="products"
+></A
+>5.3.1. Products</H2
><P
> <A
HREF="glossary.html#gloss-product"
@@ -133,7 +137,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="components">5.3.2. Components</H2
+NAME="components"
+></A
+>5.3.2. Components</H2
><P
>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
@@ -186,7 +192,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="versions">5.3.3. Versions</H2
+NAME="versions"
+></A
+>5.3.3. Versions</H2
><P
>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
@@ -220,7 +228,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="milestones">5.3.4. Milestones</H2
+NAME="milestones"
+></A
+>5.3.4. Milestones</H2
><P
>Milestones are "targets" that you plan to get a bug fixed by. For
example, you have a bug that you plan to fix for your 3.0 release, it
diff --git a/docs/html/rewrite.html b/docs/html/rewrite.html
index a64240d98f663dd0c57bbfdb2c5e6a0f80acebe2..3e7a64390b1ab71a6be690f61c397871f19a24e4 100644
--- a/docs/html/rewrite.html
+++ b/docs/html/rewrite.html
@@ -10,7 +10,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
@@ -40,7 +40,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -76,7 +76,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="rewrite">C.1. Apache
+NAME="rewrite"
+></A
+>C.1. Apache
<TT
CLASS="filename"
>mod_rewrite</TT
diff --git a/docs/html/security.html b/docs/html/security.html
index a7433f67c064aa8f9773067ba35ea5f267b43e32..14e93e6eb7fd786dfaf5d554e56cfdda4a3b901d 100644
--- a/docs/html/security.html
+++ b/docs/html/security.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="security">5.6. Bugzilla Security</H1
+NAME="security"
+></A
+>5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
@@ -127,63 +129,233 @@ VALIGN="TOP"
><P
>These instructions must, of necessity, be somewhat vague since
Bugzilla runs on so many different platforms. If you have refinements
- of these directions for specific platforms, please submit them to
- <A
-HREF="mailto://mozilla-webtools@mozilla.org"
+ of these directions, please submit a bug to <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
-> mozilla-webtools@mozilla.org</A
->
+>Bugzilla</A
+>.
</P
></TD
></TR
></TABLE
></DIV
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>This is not meant to be a comprehensive list of every possible
+ security issue regarding the tools mentioned in this section. There is
+ no subsitute for reading the information written by the authors of any
+ software running on your system.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-networking"
+></A
+>5.6.1. TCP/IP Ports</H2
+><P
+>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
+ only needs 1... 2 if you need to use features that require e-mail such
+ as bug moving or the e-mail interface from contrib. You should audit
+ your server and make sure that you aren't listening on any ports you
+ don't need to be. You may also wish to use some kind of firewall
+ software to be sure that trafic can only be recieved on ports you
+ specify.
+ </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-mysql"
+></A
+>5.6.2. MySQL</H2
+><P
+>MySQL ships by default with many settings that should be changed.
+ By defaults it allows anybody to connect from localhost without a
+ password and have full administrative capabilities. It also defaults to
+ not have a root password (this is <EM
+>not</EM
+> the same as
+ the system root). Also, many installations default to running
+ <SPAN
+CLASS="application"
+>mysqld</SPAN
+> as the system root.
+ </P
><P
->To secure your installation:
-
- <P
></P
><OL
TYPE="1"
><LI
><P
->Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and (from a security
- point of view) poor default configuration choices.</P
+>Make sure you are running at least version 3.22.32 of MySQL
+ as earlier versions had notable security holes.
+ </P
></LI
><LI
><P
-> <EM
->There is no substitute for understanding the tools on your
- system!</EM
->
-
- Read
- <A
-HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
-TARGET="_top"
-> The MySQL Privilege System</A
->
- until you can recite it from memory!</P
+>Consult the documentation that came with your system for
+ information on making <SPAN
+CLASS="application"
+>mysqld</SPAN
+> run as an
+ unprivleged user.
+ </P
></LI
><LI
><P
->Lock down /etc/inetd.conf. Heck, disable inet entirely on this
- box. It should only listen to port 25 for Sendmail and port 80 for
- Apache.</P
+>You should also be sure to disable the anonymous user account
+ and set a password for the root user. This is accomplished using the
+ following commands:
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> <TT
+CLASS="prompt"
+>bash$</TT
+> mysql mysql
+<TT
+CLASS="prompt"
+>mysql></TT
+> DELETE FROM user WHERE user = '';
+<TT
+CLASS="prompt"
+>mysql></TT
+> UPDATE user SET password = password('<TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+>') WHERE user = 'root';
+<TT
+CLASS="prompt"
+>mysql></TT
+> FLUSH PRIVILEGES;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>From this point forward you will need to use
+ <B
+CLASS="command"
+>mysql -u root -p</B
+> and enter
+ <TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+> when prompted when using the
+ mysql client.
+ </P
></LI
><LI
><P
->Do not run Apache as
- <SPAN
+>If you run MySQL on the same machine as your httpd server, you
+ should consider disabling networking from within MySQL by adding
+ the following to your <TT
+CLASS="filename"
+>/etc/my.conf</TT
+>:
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> [myslqd]
+# Prevent network access to MySQL.
+skip-networking
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></LI
+><LI
+><P
+>You may also consider running MySQL, or even all of Bugzilla
+ in a chroot jail; however, instructions for doing that are beyond
+ the scope of this document.
+ </P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-daemon"
+></A
+>5.6.3. Daemon Accounts</H2
+><P
+>Many daemons, such as Apache's httpd and MySQL's mysqld default to
+ running as either <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> or <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
->
-
- . 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.
- <DIV
+>. Running
+ as <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> introduces obvious security problems, but the
+ problems introduced by running everything as <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> may
+ not be so obvious. Basically, if you're running every daemon as
+ <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> and one of them gets comprimised, they all get
+ comprimised. For this reason it is recommended that you create a user
+ account for each daemon.
+ </P
+><DIV
CLASS="note"
><P
></P
@@ -204,83 +376,238 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
-> <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->
-
- is a real user on UNIX systems. Having a process run as user id
- <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->
-
- is absolutely no protection against system crackers versus using
- any other user account. As a general security measure, I recommend
- you create unique user ID's for each daemon running on your system
- and, if possible, use "chroot" to jail that process away from the
- rest of your system.</P
+>You will need to set the <TT
+CLASS="varname"
+>webservergroup</TT
+> to
+ the group you created for your webserver to run as in
+ <TT
+CLASS="filename"
+>localconfig</TT
+>. This will allow
+ <B
+CLASS="command"
+>./checksetup.pl</B
+> to better adjust the file
+ permissions on your Bugzilla install so as to not require making
+ anything world-writable.
+ </P
></TD
></TR
></TABLE
></DIV
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-access"
+></A
+>5.6.4. Web Server Access Controls</H2
+><P
+>There are many files that are placed in the Bugzilla directory
+ area that should not be accessable from the web. Because of the way
+ Bugzilla is currently layed out, the list of what should and should
+ not be accessible is rather complicated. A new installation method
+ is currently in the works which should solve this by allowing files
+ that shouldn't be accessible from the web to be placed in directory
+ outside the webroot. See
+ <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
+TARGET="_top"
+>bug
+ 44659</A
+> for more information.
+ </P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>In the main Bugzilla directory, you should:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block:
+ <TT
+CLASS="filename"
+>*.pl</TT
+>, <TT
+CLASS="filename"
+>*localconfig*</TT
+>, <TT
+CLASS="filename"
+>runtests.sh</TT
+>, <TT
+CLASS="filename"
+>processmail</TT
+>, <TT
+CLASS="filename"
+>syncshadowdb</TT
>
- </P
+ </P
></LI
><LI
><P
->Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ directory, as well as the
- $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" database account password.
- In addition, some
- files under $BUGZILLA_HOME/data/ store sensitive information.
- </P
+>But allow:
+ <TT
+CLASS="filename"
+>localconfig.js</TT
+>, <TT
+CLASS="filename"
+>localconfig.rdf</TT
+>
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>data</TT
+>:</P
><P
->Bugzilla provides default .htaccess files to protect the most
- common Apache installations. However, you should verify these are
- adequate according to the site-wide security policy of your web
- server, and ensure that the .htaccess files are allowed to
- "override" default permissions set in your Apache configuration
- files. Covering Apache security is beyond the scope of this Guide;
- please consult the Apache documentation for details.</P
-><P
->If you are using a web server that does not support the
- .htaccess control method,
- <EM
->you are at risk!</EM
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow:
+ <TT
+CLASS="filename"
+>duplicates.rdf</TT
>
-
- After installing, check to see if you can view the file
- "localconfig" in your web browser (e.g.:
- <A
-HREF="http://bugzilla.mozilla.org/localconfig"
-TARGET="_top"
-> http://bugzilla.mozilla.org/localconfig</A
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>data/webdot</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>If you use a remote webdot server:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow
+ <TT
+CLASS="filename"
+>*.dot</TT
>
-
- ). If you can read the contents of this file, your web server has
- not secured your bugzilla directory properly and you must fix this
- problem before deploying Bugzilla. If, however, it gives you a
- "Forbidden" error, then it probably respects the .htaccess
- conventions and you are good to go.</P
-><P
->When you run checksetup.pl, the script will attempt to modify
- various permissions on files which Bugzilla uses. If you do not have
- a webservergroup set in the localconfig file, then Bugzilla will have
- to make certain files world readable and/or writable.
- <EM
->THIS IS INSECURE!</EM
+ only for the remote webdot server</P
+></LI
+></UL
+></LI
+><LI
+><P
+>Otherwise, if you use a local GraphViz:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow:
+ <TT
+CLASS="filename"
+>*.png</TT
+>, <TT
+CLASS="filename"
+>*.gif</TT
+>, <TT
+CLASS="filename"
+>*.jpg</TT
+>, <TT
+CLASS="filename"
+>*.map</TT
>
-
- . This means that anyone who can get access to your system can do
- whatever they want to your Bugzilla installation.</P
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+>And if you don't use any dot:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>Bugzilla</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>template</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
><DIV
-CLASS="note"
+CLASS="tip"
><P
></P
><TABLE
-CLASS="note"
+CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@@ -289,67 +616,77 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
-SRC="../images/note.gif"
+SRC="../images/tip.gif"
HSPACE="5"
-ALT="Note"></TD
+ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
->This also means that if your webserver runs all cgi scripts
- as the same user/group, anyone on the system who can run cgi
- scripts will be able to take control of your Bugzilla
- installation.</P
+>Bugzilla ships with the ability to generate
+ <TT
+CLASS="filename"
+>.htaccess</TT
+> files instructing Apache which files
+ should and should not be accessible.
+ </P
></TD
></TR
></TABLE
></DIV
><P
->On Apache, you can use .htaccess files to protect access to
- these directories, as outlined in
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
-TARGET="_top"
->Bug
- 57161</A
->
-
- for the localconfig file, and
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
+>You should test to make sure that the files mentioned above are
+ not accessible from the Internet, especially your
+ <TT
+CLASS="filename"
+>localconfig</TT
+> file which contains your database
+ password. To test, simply point your web browser at the file; for
+ example, to test mozilla.org's installation, we'd try to access
+ <A
+HREF="http://bugzilla.mozilla.org/localconfig"
TARGET="_top"
->Bug
- 65572</A
->
-
- for adequate protection in your data/ directory.</P
-><P
->Note the instructions which follow are Apache-specific. If you
- use IIS, Netscape, or other non-Apache web servers, please consult
- your system documentation for how to secure these files from being
- transmitted to curious users.</P
-><P
->Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/data directory.
- <P
-CLASS="literallayout"
-><Files comments> allow from all </Files><br>
- deny from all</P
+>http://bugzilla.mozilla.org/localconfig</A
+>. You should
+ get a <SPAN
+CLASS="errorcode"
+>403</SPAN
+> <SPAN
+CLASS="errorname"
+>Forbidden</SPAN
>
- </P
+ error.
+ </P
+><DIV
+CLASS="caution"
><P
->Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/ directory.
- <P
-CLASS="literallayout"
-><Files localconfig> deny from all </Files><br>
- allow from all</P
->
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Not following the instructions in this section, including
+ testing, may result in sensitive information being globally
+ accessible.
</P
-></LI
-></OL
->
- </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html
index 6d4de5a218399f1d612f4ebdaef324750437baba..c3a9c01cf924986be81f484eeedeb9814f4eb846 100644
--- a/docs/html/stepbystep.html
+++ b/docs/html/stepbystep.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="stepbystep">4.1. Step-by-step Install</H1
+NAME="stepbystep"
+></A
+>4.1. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN492">4.1.1. Introduction</H2
+NAME="AEN428"
+></A
+>4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
@@ -97,7 +101,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN496">4.1.2. Package List</H2
+NAME="AEN432"
+></A
+>4.1.2. Package List</H2
><DIV
CLASS="note"
><P
@@ -475,7 +481,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="install-mysql">4.1.3. MySQL</H2
+NAME="install-mysql"
+></A
+>4.1.3. MySQL</H2
><P
>Visit the MySQL homepage at
<A
@@ -577,7 +585,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="install-perl">4.1.4. Perl</H2
+NAME="install-perl"
+></A
+>4.1.4. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
@@ -594,7 +604,9 @@ TARGET="_top"
><DIV
CLASS="tip"
><A
-NAME="bundlebugzilla"><P
+NAME="bundlebugzilla"
+></A
+><P
></P
><TABLE
CLASS="tip"
@@ -659,7 +671,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="perl-modules">4.1.5. Perl Modules</H2
+NAME="perl-modules"
+></A
+>4.1.5. Perl Modules</H2
><P
>
All Perl modules can be found on the
@@ -822,7 +836,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN642">4.1.5.1. DBI</H3
+NAME="AEN578"
+></A
+>4.1.5.1. DBI</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
@@ -835,7 +851,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN645">4.1.5.2. Data::Dumper</H3
+NAME="AEN581"
+></A
+>4.1.5.2. Data::Dumper</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
@@ -847,7 +865,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN648">4.1.5.3. MySQL-related modules</H3
+NAME="AEN584"
+></A
+>4.1.5.3. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
@@ -871,7 +891,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN653">4.1.5.4. TimeDate modules</H3
+NAME="AEN589"
+></A
+>4.1.5.4. TimeDate modules</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
@@ -885,7 +907,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN656">4.1.5.5. GD (optional)</H3
+NAME="AEN592"
+></A
+>4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
@@ -938,7 +962,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN663">4.1.5.6. Chart::Base (optional)</H3
+NAME="AEN599"
+></A
+>4.1.5.6. Chart::Base (optional)</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
@@ -951,7 +977,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="AEN666">4.1.5.7. Template Toolkit</H3
+NAME="AEN602"
+></A
+>4.1.5.7. Template Toolkit</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
@@ -967,7 +995,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN669">4.1.6. HTTP Server</H2
+NAME="AEN605"
+></A
+>4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
@@ -1043,7 +1073,9 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
->Options ExecCGI AllowOverride Limit</PRE
+> Options ExecCGI
+AllowOverride Limit
+ </PRE
></FONT
></TD
></TR
@@ -1141,7 +1173,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN688">4.1.7. Bugzilla</H2
+NAME="AEN624"
+></A
+>4.1.7. Bugzilla</H2
><P
>You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
@@ -1252,7 +1286,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN705">4.1.8. Setting Up the MySQL Database</H2
+NAME="AEN641"
+></A
+>4.1.8. Setting Up the MySQL Database</H2
><P
>After you've gotten all the software installed and working you're
ready to start preparing the database for its life as the back end to
@@ -1417,13 +1453,43 @@ CLASS="command"
></P
>
</P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you are using MySQL 4, the bugs user also needs to be granted
+ the LOCK TABLES and CREATE TEMPORARY TABLES permissions.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN741">4.1.9. <TT
+NAME="AEN679"
+></A
+>4.1.9. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
@@ -1574,283 +1640,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN773">4.1.10. Securing MySQL</H2
-><P
->If you followed the installation instructions for setting up your
- "bugs" and "root" user in MySQL, much of this should not apply to you.
- 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></TT
->
-
- <B
-CLASS="command"
->use mysql;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->show tables;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></TT
->
-
- <B
-CLASS="command"
->select * from user;</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->mysql></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->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
->running MySQL in a chroot jail</P
-></LI
-><LI
-><P
->running the httpd in a chroot 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"
-><H2
-CLASS="section"
-><A
-NAME="AEN839">4.1.11. Configuring Bugzilla</H2
+NAME="AEN711"
+></A
+>4.1.10. Configuring Bugzilla</H2
><P
> You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
diff --git a/docs/html/troubleshooting.html b/docs/html/troubleshooting.html
index 7a4a32d7de8fc8628bd8e91da829306c7df25cab..d712a4029eb62a895b7df0423ec1702b5af1b239 100644
--- a/docs/html/troubleshooting.html
+++ b/docs/html/troubleshooting.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="troubleshooting">4.5. Troubleshooting</H1
+NAME="troubleshooting"
+></A
+>4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
@@ -83,7 +85,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1218">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+NAME="AEN1090"
+></A
+>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
> Try executing <B
CLASS="command"
@@ -106,7 +110,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN1223">4.5.2. DBD::Sponge::db prepare failed</H2
+NAME="AEN1095"
+></A
+>4.5.2. DBD::Sponge::db prepare failed</H2
><P
> The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
@@ -190,7 +196,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
+NAME="paranoid-security"
+></A
+>4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
distributions with
@@ -241,6 +249,116 @@ CLASS="filename"
as root to fix this problem.
</P
></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="trouble-filetemp"
+></A
+>4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
+><P
+>This is caused by a bug in the version of
+ <SPAN
+CLASS="productname"
+>File::Temp</SPAN
+> that is distributed with perl
+ 5.6.0. Many minor variations of this error have been reported. Examples
+ can be found in <A
+HREF="troubleshooting.html#trouble-filetemp-errors"
+>Figure 4-1</A
+>.
+ </P
+><DIV
+CLASS="figure"
+><A
+NAME="trouble-filetemp-errors"
+></A
+><P
+><B
+>Figure 4-1. Other File::Temp error messages</B
+></P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> Your vendor has not defined Fcntl macro O_NOINHERIT, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
+
+Your vendor has not defined Fcntl macro O_EXLOCK, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
+
+Your vendor has not defined Fcntl macro O_TEMPORARY, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Numerous people have reported that upgrading to version 5.6.1
+ or higher solved the problem for them. A less involved fix is to apply
+ the patch in <A
+HREF="troubleshooting.html#trouble-filetemp-patch"
+>Figure 4-2</A
+>. The patch is also
+ available as a <A
+HREF="../xml/filetemp.patch"
+TARGET="_top"
+>patch file</A
+>.
+ </P
+><DIV
+CLASS="figure"
+><A
+NAME="trouble-filetemp-patch"
+></A
+><P
+><B
+>Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
+></P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> --- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
++++ File/Temp.pm Thu Feb 6 16:26:23 2003
+@@ -205,6 +205,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+@@ -226,6 +227,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/upgrading.html b/docs/html/upgrading.html
index 445154030eed17dc00a2b7e8003961d629c80264..f59abd2b58772a5558193a925df5858a27863250 100644
--- a/docs/html/upgrading.html
+++ b/docs/html/upgrading.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,43 +73,500 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="upgrading">5.8. Upgrading to New Releases</H1
-><P
->A plain Bugzilla is fairly easy to upgrade from one version to a
- newer one. Always read the release notes to see if there are any issues
- that you might need to take note of. It is recommended that you take a
- backup of your database and your entire Bugzilla installation before attempting an
- upgrade. You can upgrade a 'clean' installation by untarring a new
- tarball over the old installation. If you are upgrading from 2.12 or
- later, and have cvs installed, you can type <TT
-CLASS="filename"
->cvs -z3 update</TT
->,
- and resolve conflicts if there are any.
+NAME="upgrading"
+></A
+>5.8. Upgrading to New Releases</H1
+><P
+>Upgrading Bugzilla is something we all want to do from time to time,
+ be it to get new features or pick up the latest security fix. How easy
+ it is to update depends on a few factors.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>If the new version is a revision or a new point release</P
+></LI
+><LI
+><P
+>How many, if any, local changes have been made</P
+></LI
+></UL
+><P
+>There are also three different methods to upgrade your installation.
+ </P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Using CVS (<A
+HREF="upgrading.html#upgrade-cvs"
+>Example 5-1</A
+>)</P
+></LI
+><LI
+><P
+>Downloading a new tarball (<A
+HREF="upgrading.html#upgrade-tarball"
+>Example 5-2</A
+>)</P
+></LI
+><LI
+><P
+>Applying the relevant patches (<A
+HREF="upgrading.html#upgrade-patches"
+>Example 5-3</A
+>)</P
+></LI
+></OL
+><P
+>Which options are available to you may depend on how large a jump
+ you are making and/or your network configuration.
+ </P
+><P
+>Revisions are normally released to fix security vulnerabilities
+ and are distinguished by an increase in the third number. For example,
+ when 2.16.2 was released, it was a revision to 2.16.1.
+ </P
+><P
+>Point releases are normally released when the Bugzilla team feels
+ that there has been a significant amount of progress made between the
+ last point release and the current time. These are often proceeded by a
+ stabilization period and release candidates, however the use of
+ development versions or release candidates is beyond the scope of this
+ document. Point releases can be distinguished by an increase in the
+ second number, or minor version. For example, 2.16.2 is a newer point
+ release than 2.14.5.
+ </P
+><P
+>The examples in this section are written as if you were updating
+ to version 2.16.2. The procedures are the same regardless if you are
+ updating to a new point release or a new revision. However, the chance
+ of running into trouble increases when upgrading to a new point release,
+ escpecially if you've made local changes.
</P
><P
->However, things get a bit more complicated if you've made
- changes to Bugzilla's code. In this case, you may have to re-make or
- reapply those changes. One good method is to take a diff of your customised
- version against the original, so you can survey all that you've changed.
- Hopefully, templatisation will reduce the need for
- this in the future.</P
-><P
->From version 2.8 onwards, Bugzilla databases can be automatically
- carried forward during an upgrade. However, because the developers of
- Bugzilla are constantly adding new
- tables, columns and fields, you'll probably get SQL errors if you just
- update the code and attempt to use Bugzilla. Always run the
+>These examples also assume that your Bugzilla installation is at
<TT
CLASS="filename"
->checksetup.pl</TT
->
- script whenever you upgrade your installation.</P
-><P
->If you are running Bugzilla version 2.8 or lower, and wish to
- upgrade to the latest version, please consult the file,
- "UPGRADING-pre-2.8" in the Bugzilla root directory after untarring the
- archive.</P
+>/var/www/html/bugzilla</TT
+>. If that is not the case,
+ simply substitute the proper paths where appropriate.
+ </P
+><DIV
+CLASS="example"
+><A
+NAME="upgrade-cvs"
+></A
+><P
+><B
+>Example 5-1. Upgrading using CVS</B
+></P
+><P
+>Every release of Bugzilla, whether it is a revision or a point
+ release, is tagged in CVS. Also, every tarball we have distributed
+ since version 2.12 has been primed for using CVS. This does, however,
+ require that you are able to access cvs-mirror.mozilla.org on port
+ 2401.
+
+ <DIV
+CLASS="tip"
+><P
+></P
+><TABLE
+CLASS="tip"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you can do this, updating using CVS is probably the most
+ painless method, especially if you have a lot of local changes.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html/bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>cvs login</B
+>
+Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
+CVS password: <B
+CLASS="command"
+>anonymous</B
+>
+bash$ <B
+CLASS="command"
+>cvs -q update -r BUGZILLA-2_16_2 -dP</B
+>
+P checksetup.pl
+P collectstats.pl
+P globals.pl
+P docs/rel_notes.txt
+P template/en/default/list/quips.html.tmpl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+> <DIV
+CLASS="caution"
+><P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If a line in the output from <B
+CLASS="command"
+>cvs update</B
+>
+ begins with a <TT
+CLASS="computeroutput"
+>C</TT
+> that represents a
+ file with local changes that CVS was unable to properly merge. You
+ need to resolve these conflicts manually before Bugzilla (or at
+ least the portion using that file) will be usable.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ <DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You also need to run <B
+CLASS="command"
+>./checksetup.pl</B
+>
+ before your Bugzilla upgrade will be complete.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="example"
+><A
+NAME="upgrade-tarball"
+></A
+><P
+><B
+>Example 5-2. Upgrading using the tarball</B
+></P
+><P
+>If you are unable or unwilling to use CVS, another option that's
+ always available is to download the latest tarball. This is the most
+ difficult option to use, especially if you have local changes.
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html</B
+>
+bash$ <B
+CLASS="command"
+>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B
+>
+<EM
+>Output omitted</EM
+>
+bash$ <B
+CLASS="command"
+>tar xzvf bugzilla-2.16.2.tar.gz</B
+>
+bugzilla-2.16.2/
+bugzilla-2.16.2/.cvsignore
+bugzilla-2.16.2/1x1.gif
+<EM
+>Output truncated</EM
+>
+bash$ <B
+CLASS="command"
+>cd bugzilla-2.16.2</B
+>
+bash$ <B
+CLASS="command"
+>cp ../bugzilla/localconfig* .</B
+>
+bash$ <B
+CLASS="command"
+>cp -r ../bugzilla/data .</B
+>
+bash$ <B
+CLASS="command"
+>cd ..</B
+>
+bash$ <B
+CLASS="command"
+>mv bugzilla bugzilla.old</B
+>
+bash$ <B
+CLASS="command"
+>mv bugzilla-2.16.2 bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>cd bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>./checksetup.pl</B
+>
+<EM
+>Output omitted</EM
+>
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+> <DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The <B
+CLASS="command"
+>cp</B
+> commands both end with periods which
+ is a very important detail, it tells the shell that the destination
+ directory is the current working directory. Also, the period at the
+ beginning of the <B
+CLASS="command"
+>./checksetup.pl</B
+> is important and
+ can not be omitted.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ <DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You will now have to reapply any changes you have made to your
+ local installation manually.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="example"
+><A
+NAME="upgrade-patches"
+></A
+><P
+><B
+>Example 5-3. Upgrading using patches</B
+></P
+><P
+>The Bugzilla team will normally make a patch file available for
+ revisions to go from the most recent revision to the new one. You could
+ also read the release notes and grab the patches attached to the
+ mentioned bug, but it is safer to use the released patch file as
+ sometimes patches get changed before they get checked in (for minor
+ spelling fixes and the like). It is also theorectically possible to
+ scour the fixed bug list and pick and choose which patches to apply
+ from a point release, but this is not recommended either as what you'll
+ end up with is a hodge podge Bugzilla that isn't really any version.
+ This would also make it more difficult to upgrade in the future.
+ </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+> bash$ <B
+CLASS="command"
+>cd /var/www/html/bugzilla</B
+>
+bash$ <B
+CLASS="command"
+>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B
+>
+<EM
+>Output omitted</EM
+>
+bash$ <B
+CLASS="command"
+>gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B
+>
+bash$ <B
+CLASS="command"
+>patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B
+>
+patching file checksetup.pl
+patching file collectstats.pl
+patching file globals.pl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+> <DIV
+CLASS="caution"
+><P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you do this, beware that this doesn't change the entires in
+ your <TT
+CLASS="filename"
+>CVS</TT
+> directory so it may make
+ updates using CVS (<A
+HREF="upgrading.html#upgrade-cvs"
+>Example 5-1</A
+>) more difficult in the
+ future.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/useradmin.html b/docs/html/useradmin.html
index 00893687ea008e1a2727cde2c5d973fcc5fabe9a..9edb45892d22bfb17e9cb298e72a7236d856e76c 100644
--- a/docs/html/useradmin.html
+++ b/docs/html/useradmin.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="useradmin">5.2. User Administration</H1
+NAME="useradmin"
+></A
+>5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="defaultuser">5.2.1. Creating the Default User</H2
+NAME="defaultuser"
+></A
+>5.2.1. Creating the Default User</H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
@@ -171,13 +175,17 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="manageusers">5.2.2. Managing Other Users</H2
+NAME="manageusers"
+></A
+>5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
-NAME="createnewusers">5.2.2.1. Creating new users</H3
+NAME="createnewusers"
+></A
+>5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
@@ -248,7 +256,9 @@ CLASS="section"
><H3
CLASS="section"
><A
-NAME="modifyusers">5.2.2.2. Modifying Users</H3
+NAME="modifyusers"
+></A
+>5.2.2.2. Modifying Users</H3
><P
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
diff --git a/docs/html/userpreferences.html b/docs/html/userpreferences.html
index a782877f310277ab86661421b077644c36f80a8a..bdb7c42952fec4b718c05a713701e8c0c60666d8 100644
--- a/docs/html/userpreferences.html
+++ b/docs/html/userpreferences.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="userpreferences">3.3. User Preferences</H1
+NAME="userpreferences"
+></A
+>3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
@@ -83,7 +85,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="accountsettings">3.3.1. Account Settings</H2
+NAME="accountsettings"
+></A
+>3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
@@ -106,7 +110,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="emailsettings">3.3.2. Email Settings</H2
+NAME="emailsettings"
+></A
+>3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
@@ -153,7 +159,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="footersettings">3.3.3. Page Footer</H2
+NAME="footersettings"
+></A
+>3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
@@ -165,7 +173,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="permissionsettings">3.3.4. Permissions</H2
+NAME="permissionsettings"
+></A
+>3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
diff --git a/docs/html/using.html b/docs/html/using.html
index 0d1231589ebc12ebfa63d8722c3bffb2d80ba911..65a8f99c472a6031da8c8a968c52d818e3c8e7cb 100644
--- a/docs/html/using.html
+++ b/docs/html/using.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Why Should We Use Bugzilla?"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
-NAME="using">Chapter 3. Using Bugzilla</H1
+NAME="using"
+></A
+>Chapter 3. Using Bugzilla</H1
><DIV
CLASS="TOC"
><DL
@@ -120,7 +122,7 @@ HREF="hintsandtips.html"
><DL
><DT
>3.2.1. <A
-HREF="hintsandtips.html#AEN434"
+HREF="hintsandtips.html#AEN370"
>Autolinkification</A
></DT
><DT
@@ -140,7 +142,7 @@ HREF="hintsandtips.html#attachments"
></DT
><DT
>3.2.5. <A
-HREF="hintsandtips.html#AEN463"
+HREF="hintsandtips.html#AEN399"
>Filing Bugs</A
></DT
></DL
diff --git a/docs/html/variant-fenris.html b/docs/html/variant-fenris.html
index 69be49b6b09277cbd18dea9e326de4645cf87afa..2fa641e59f247eba4179af5e490e47739eccd02f 100644
--- a/docs/html/variant-fenris.html
+++ b/docs/html/variant-fenris.html
@@ -7,14 +7,14 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Red Hat Bugzilla"
-HREF="rhbugzilla.html"><LINK
+HREF="variant-redhat.html"><LINK
REL="NEXT"
TITLE="Issuezilla"
HREF="variant-issuezilla.html"></HEAD
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -73,12 +73,16 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
+NAME="variant-fenris"
+></A
+>D.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
its custodians recommend Bugzilla for future bug-tracker deployments.
</P
+><P
+>This section last updated 27 Jul 2002</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -96,7 +100,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
ACCESSKEY="P"
>Prev</A
></TD
diff --git a/docs/html/variant-issuezilla.html b/docs/html/variant-issuezilla.html
index e14cc0794673171a4408d31c4cc4c186b7b6c7c2..1c4d8215e9076428804c3f82af8ebd218c9fb325 100644
--- a/docs/html/variant-issuezilla.html
+++ b/docs/html/variant-issuezilla.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,15 +73,19 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="variant-issuezilla">D.3. Issuezilla</H1
+NAME="variant-issuezilla"
+></A
+>D.3. Issuezilla</H1
><P
>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
at tigris.org is their Java-based bug-tracker,
<A
HREF="variant-scarab.html"
->Scarab</A
+>Section D.4</A
>.</P
+><P
+>This section last updated 27 Jul 2002</P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/variant-perforce.html b/docs/html/variant-perforce.html
index 6bcfc5eed634a76eac950441859585ed098b294b..e912f0c3b0f13044464813a390943a12a5822031 100644
--- a/docs/html/variant-perforce.html
+++ b/docs/html/variant-perforce.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="variant-perforce">D.5. Perforce SCM</H1
+NAME="variant-perforce"
+></A
+>D.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used as
such through the <SPAN
@@ -90,6 +92,8 @@ TARGET="_top"
</A
>
</P
+><P
+>This section last updated 27 Jul 2002</P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/rhbugzilla.html b/docs/html/variant-redhat.html
similarity index 69%
rename from docs/html/rhbugzilla.html
rename to docs/html/variant-redhat.html
index fb1eb3c9a92d6eda253382bab6d6402b2a496705..bcc38f8b0403d5613b338d810d8bde364d903daa 100644
--- a/docs/html/rhbugzilla.html
+++ b/docs/html/variant-redhat.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,14 +73,25 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="rhbugzilla">D.1. Red Hat Bugzilla</H1
+NAME="variant-redhat"
+></A
+>D.1. Red Hat Bugzilla</H1
><P
->Red Hat Bugzilla is a fork of Bugzilla 2.8.
- One of its major benefits is the ability
- to work with Oracle, MySQL, and PostGreSQL databases serving as the
- back-end, instead of just MySQL. Dave Lawrence of Red Hat is
- active in the Bugzilla community, and we hope to see a reunification
- of the fork before too long.</P
+>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+ obsolete. The newest version in use is based on version 2.17.1 and is in
+ the process of being integrated into the main Bugzilla source tree. The
+ back-end is modified to work with PostgreSQL instead of MySQL and they have
+ custom templates to get their desired look and feel, but other than that it
+ is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
+ effort to make sure that the changes he made could be integrated back into
+ the main tree.
+ <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>Bug
+ 98304</A
+> exists to track this integration.
+ </P
><P
>URL:
<A
@@ -89,6 +100,8 @@ TARGET="_top"
> http://bugzilla.redhat.com/bugzilla/</A
>
</P
+><P
+>This section last updated 24 Dec 2002</P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/variant-scarab.html b/docs/html/variant-scarab.html
index 14cd54afa4892a2aeb1e383f512bb946cd66fd65..6b5ecb768e938c8e57c2bbef5577452608cc078c 100644
--- a/docs/html/variant-scarab.html
+++ b/docs/html/variant-scarab.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,10 +73,12 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="variant-scarab">D.4. Scarab</H1
+NAME="variant-scarab"
+></A
+>D.4. Scarab</H1
><P
>Scarab is a new open source bug-tracking system built using Java
- Serlet technology. It is currently at version 1.0 beta 8.</P
+ Servlet technology. It is currently at version 1.0 beta 13.</P
><P
>URL:
<A
@@ -85,6 +87,8 @@ TARGET="_top"
>http://scarab.tigris.org</A
>
</P
+><P
+>This section last updated 18 Jan 2003</P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/variant-sourceforge.html b/docs/html/variant-sourceforge.html
index 1e4891f4a9ae1f2c8314629b19a06a13372c6abf..ab418336d0891301ac64ed826cdba113d680dbb8 100644
--- a/docs/html/variant-sourceforge.html
+++ b/docs/html/variant-sourceforge.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant-perforce.html"><LINK
REL="NEXT"
-TITLE="Glossary"
-HREF="glossary.html"></HEAD
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="glossary.html"
+HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="variant-sourceforge">D.6. SourceForge</H1
+NAME="variant-sourceforge"
+></A
+>D.6. SourceForge</H1
><P
>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
@@ -86,6 +88,8 @@ TARGET="_top"
> http://www.sourceforge.net</A
>
</P
+><P
+>This section last updated 27 Jul 2002</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -121,7 +125,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="glossary.html"
+HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -145,7 +149,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Glossary</TD
+>GNU Free Documentation License</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/variants.html b/docs/html/variants.html
index f5bd22fdea6e7115c36ba0fcd4fc3d5b31bff04f..c7360971ebc2c772e647d98d38158a639e8ff1b0 100644
--- a/docs/html/variants.html
+++ b/docs/html/variants.html
@@ -7,14 +7,14 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
-HREF="rhbugzilla.html"></HEAD
+HREF="variant-redhat.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
@@ -34,7 +34,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
-NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
+NAME="variants"
+></A
+>Appendix D. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
@@ -79,7 +81,7 @@ CLASS="TOC"
></DT
><DT
>D.1. <A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
>Red Hat Bugzilla</A
></DT
><DT
@@ -155,7 +157,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="rhbugzilla.html"
+HREF="variant-redhat.html"
ACCESSKEY="N"
>Next</A
></TD
diff --git a/docs/html/voting.html b/docs/html/voting.html
index 47b05647f6c5c4991692b1a73a8c85dcf0235ed1..4e0d7ac8020a13d6cdfe3ed6a93484e9733ad483 100644
--- a/docs/html/voting.html
+++ b/docs/html/voting.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="voting">5.4. Voting</H1
+NAME="voting"
+></A
+>5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index 85ec722020adfb14d4d9d6c9168aca952ad7acb2..5de3cb2ef59d2bb082046a6b9cbd0be4bf5375f3 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,13 +73,21 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="whatis">2.1. What is Bugzilla?</H1
+NAME="whatis"
+></A
+>2.1. What is Bugzilla?</H1
><P
> Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
of outstanding problems with their product.
- Bugzilla was originally
- written by Terry Weissman in a programming language called TCL, to
+ Bugzilla was originally written by Terry Weissman in a programming language
+ called <A
+HREF="glossary.html#gloss-tcl"
+><I
+CLASS="glossterm"
+>TCL</I
+></A
+>, to
replace a rudimentary bug-tracking database used internally by Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
it remains to this day. Most commercial defect-tracking software vendors
diff --git a/docs/html/why.html b/docs/html/why.html
index 1baa4042e39b5b61b50e2c4a3895bd84ddd8c84f..dae636c3ef4af01d8cb8be4227642b2f00a8b450 100644
--- a/docs/html/why.html
+++ b/docs/html/why.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="why">2.2. Why Should We Use Bugzilla?</H1
+NAME="why"
+></A
+>2.2. Why Should We Use Bugzilla?</H1
><P
>For many years, defect-tracking software has remained principally
the domain of large software development houses. Even then, most shops
diff --git a/docs/html/win32.html b/docs/html/win32.html
index 575bf8f4be82dd8345273ade17a00cf843a3bc02..840a4303df5a72e7e6c94e47ffd16072b82bfef2 100644
--- a/docs/html/win32.html
+++ b/docs/html/win32.html
@@ -7,7 +7,7 @@ NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide"
+TITLE="The Bugzilla Guide - 2.16.3 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
@@ -37,7 +37,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide</TH
+>The Bugzilla Guide - 2.16.3 Release</TH
></TR
><TR
><TD
@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
-NAME="win32">4.3. Win32 Installation Notes</H1
+NAME="win32"
+></A
+>4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
@@ -150,7 +152,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2
+NAME="wininstall"
+></A
+>4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
@@ -385,7 +389,9 @@ CLASS="command"
><DIV
CLASS="example"
><A
-NAME="AEN989"><P
+NAME="AEN861"
+></A
+><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
@@ -443,7 +449,9 @@ TARGET="_top"
<DIV
CLASS="example"
><A
-NAME="AEN1002"><P
+NAME="AEN874"
+></A
+><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
@@ -1557,7 +1565,9 @@ CLASS="section"
><H2
CLASS="section"
><A
-NAME="addlwintips">4.3.2. Additional Windows Tips</H2
+NAME="addlwintips"
+></A
+>4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
@@ -1581,7 +1591,9 @@ VALIGN="TOP"
><P
>From Andrew Pearson:
<A
-NAME="AEN1172"><BLOCKQUOTE
+NAME="AEN1044"
+></A
+><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
@@ -1660,11 +1672,13 @@ VALIGN="TOP"
>
for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla &bz-ver;.
+ Bugzilla 2.16.3.
<DIV
CLASS="example"
><A
-NAME="AEN1184"><P
+NAME="AEN1056"
+></A
+><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
diff --git a/docs/images/CVS/Entries b/docs/images/CVS/Entries
index 49d954b96e50e0011a51d171852e1b8143622367..cfc8c909600699c3a8141c2047bdc8cb5d57a8fa 100644
--- a/docs/images/CVS/Entries
+++ b/docs/images/CVS/Entries
@@ -1,7 +1,7 @@
-/caution.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_2
-/dbschema.jpg/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_16_2
-/dbschema.ps/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_16_2
-/note.gif/1.1/Thu Aug 23 14:30:18 2001/-kb/TBUGZILLA-2_16_2
-/tip.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_2
-/warning.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_2
+/caution.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_3
+/dbschema.jpg/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_16_3
+/dbschema.ps/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_16_3
+/note.gif/1.1/Thu Aug 23 14:30:18 2001/-kb/TBUGZILLA-2_16_3
+/tip.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_3
+/warning.gif/1.2/Wed May 8 21:16:44 2002/-kb/TBUGZILLA-2_16_3
D
diff --git a/docs/images/CVS/Tag b/docs/images/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/docs/images/CVS/Tag
+++ b/docs/images/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/docs/makedocs.pl b/docs/makedocs.pl
new file mode 100644
index 0000000000000000000000000000000000000000..18fdf0a620e5dd41ed14440da094b202e02a5374
--- /dev/null
+++ b/docs/makedocs.pl
@@ -0,0 +1,78 @@
+#!/usr/bin/perl -w
+# -*- Mode: perl; indent-tabs-mode: nil -*-
+#
+# The contents of this file are subject to the Mozilla Public
+# License Version 1.1 (the "License"); you may not use this file
+# except in compliance with the License. You may obtain a copy of
+# the License at http://www.mozilla.org/MPL/
+#
+# Software distributed under the License is distributed on an "AS
+# IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+# implied. See the License for the specific language governing
+# rights and limitations under the License.
+#
+# The Original Code is the Bugzilla Bug Tracking System.
+#
+# The Initial Developer of the Original Code is Netscape Communications
+# Corporation. Portions created by Netscape are
+# Copyright (C) 1998 Netscape Communications Corporation. All
+# Rights Reserved.
+#
+# Contributor(s): Matthew Tuck <matty@chariot.net.au>
+
+# This script compiles all the documentation.
+
+use diagnostics;
+use strict;
+
+use File::Basename;
+
+###############################################################################
+# Environment Variable Checking
+###############################################################################
+
+my ($JADE_PUB, $LDP_HOME);
+
+if (defined $ENV{JADE_PUB} && $ENV{JADE_PUB} ne '') {
+ $JADE_PUB = $ENV{JADE_PUB};
+}
+else {
+ die "You need to set the JADE_PUB environment variable first.";
+}
+
+if (defined $ENV{LDP_HOME} && $ENV{LDP_HOME} ne '') {
+ $LDP_HOME = $ENV{LDP_HOME};
+}
+else {
+ die "You need to set the LDP_HOME environment variable first.";
+}
+
+###############################################################################
+# Subs
+###############################################################################
+
+sub MakeDocs($$) {
+
+ my ($name, $cmdline) = @_;
+
+ print "Creating $name documentation ...\n";
+ print "$cmdline\n\n";
+ system $cmdline;
+ print "\n";
+
+}
+
+###############################################################################
+# Make the docs ...
+###############################################################################
+
+chdir dirname($0);
+chdir 'html';
+
+MakeDocs('separate HTML', "jade -t sgml -i html -d $LDP_HOME/ldp.dsl\#html " .
+ "$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml");
+MakeDocs('big HTML', "jade -V nochunks -t sgml -i html -d " .
+ "$LDP_HOME/ldp.dsl\#html $JADE_PUB/xml.dcl " .
+ "../xml/Bugzilla-Guide.xml > Bugzilla-Guide.html");
+MakeDocs('big text', "lynx -dump -justify=off -nolist Bugzilla-Guide.html " .
+ "> ../txt/Bugzilla-Guide.txt");
diff --git a/docs/rel_notes.txt b/docs/rel_notes.txt
index 41d1ab29709e18d7ff811b15a3347d5b68ed14ba..a7306c109c43587014711bf1893a2a587fcc687c 100644
--- a/docs/rel_notes.txt
+++ b/docs/rel_notes.txt
@@ -1,4 +1,4 @@
-The 2.16.2 release fixes some minor issues in 2.16.1.
+The 2.16.3 release fixes several security issues and bugs in 2.16.2.
**************************
*** ABOUT THIS VERSION ***
@@ -24,7 +24,7 @@ mean there are more errors in your database, as additional
tests are added to the sanity check over time, and it is likely
those errors weren't being checked for in the old version.
-Failure to do this may mean that bugzilla will not
+Failure to do this may mean that Bugzilla will not
work correctly.
Administrators must make sure that certain files are
@@ -43,24 +43,83 @@ AppConfig v1.52
Template Toolkit v2.07
Text::Wrap v20001.0131
File::Spec v0.82
+File::Temp (any) *** NEW in 2.16.3 ***
Data::Dumper, Date::Parse, CGI::Carp (any)
GD v1.19 (optional)
Chart::Base v0.99 (optional)
-XML::Parser (any)
+XML::Parser (any, optional)
+
+*********************************************************
+*** USERS UPGRADING FROM ALL VERSIONS PRIOR TO 2.16.3 ***
+*********************************************************
+
+*** SECURITY ISSUES RESOLVED ***
+
+- A cross site scripting (XSS) vulnerability was fixed in which bug
+ summaries were not properly filtered when a user viewed a dependency graph
+ allowing JavaScript to be embedded on that page.
+ (bug 192661)
+
+- Several XSS vulnerabilities were fixed in which user
+ input was not escaped when being displayed. A new
+ test has been added to warn about unfiltered data in template
+ files (t/008filter.t)
+ (bug 192677)
+
+- An issue was fixed in which the QA contact was still treated as the QA
+ contact even after the 'useqacontact' setting was turned off. This also
+ allowed the QA contact to edit the security groups and view secured bugs that
+ he/she was allowed to access prior to the 'useqacontact' setting being
+ deactivated.
+ (bug 194394)
+
+- Fixed a situation where an attacker (with local access to the webserver)
+ could overwrite any file on the webserver to which the webserver user
+ has write access by creating appropriately named symbolic links in the
+ data and webdot directories (world-writable in many configurations).
+ Bugzilla now uses File::Temp to create secure temporary files. File::Temp
+ is part of the Perl distribution for Perl 5.6.1 and later, but if you're
+ using an older version of Perl you'll need to install it with CPAN.
+ (bug 197153)
+
+*** Bug fixes of note ***
+
+- An issue was fixed in which administrator rights could be removed from an
+ administrator who deleted a product while the 'usebuggroups' setting is
+ activated.
+ (bug 157704)
+
+- Fixed an issue in which importxml.pl would fail the test suite when running
+ under perl 5.8.0 with the optional XML::Parse module.
+ (bug 172331)
+
+- There was previously a bug in CGI.pl in which the following warning
+ would be given under certain conditions:
+ "Character in "c" format wrapped at CGI.pl..."
+ This is now fixed. In some cases the warning was filling up web server log
+ files.
+ (bug 194125)
+
+- Fixed a bug in which long component names (in excess of 50 characters) would
+ be accepted when creating the component but would cause problems when trying
+ to use that component on a bug because it would get truncated. It is now no
+ longer possible to create components with names in excess of 50 characters.
+ (bug 197180)
+
+- Fixed a bug in checksetup.pl in which permissions were not being fixed
+ on the 'data/comments' file, the quip file.
+ (bug 160279)
*** Deprecated Features ***
-- This is possibly the last stable release that will work with
- MySQL version 3.22. Development versions of Bugzilla currently
- require at least version 3.23.6.
+- 2.16 is the last major release that will work with MySQL version 3.22.x.
+ Development versions of Bugzilla currently require at least version 3.23.41.
(bug 87958)
-- This is possibly the last stable release to support the
- shadow database. Support for it has already been removed
- in CVS. The replacement (using MySQL's built in replication)
- is not present in 2.16.2, but we expect that very few sites use
- this feature, so we are not planning a transition period. If
- this would cause a problem for you, please comment on the below bug.
+- 2.16 is the last major release to support the shadow database. Support for
+ it has already been removed in CVS. The replacement (using MySQL's built in
+ replication) is not present in 2.16.x, but we expect that very few sites use
+ this feature, so we are not planning a transition period.
(bug 124589)
- Placing comments in localconfig is deprecated. If you have done
diff --git a/docs/sgml/CVS/Entries b/docs/sgml/CVS/Entries
deleted file mode 100644
index 036b2761e043f3d9de9f33c211e60d9d40badadc..0000000000000000000000000000000000000000
--- a/docs/sgml/CVS/Entries
+++ /dev/null
@@ -1,18 +0,0 @@
-/Bugzilla-Guide.sgml/1.11.2.4/Thu Jul 25 21:03:27 2002//TBUGZILLA-2_16_2
-/about.sgml/1.6.2.2/Sun May 12 16:15:29 2002//TBUGZILLA-2_16_2
-/administration.sgml/1.13.2.5/Thu Jul 25 21:03:28 2002//TBUGZILLA-2_16_2
-/conventions.sgml/1.4.2.4/Thu Jul 25 21:03:28 2002//TBUGZILLA-2_16_2
-/database.sgml/1.7.2.1/Sat May 25 15:36:06 2002//TBUGZILLA-2_16_2
-/dbschema.mysql/1.2/Wed May 8 23:19:09 2002//TBUGZILLA-2_16_2
-/faq.sgml/1.8.2.2/Sat Jul 13 07:53:28 2002//TBUGZILLA-2_16_2
-/gd-makefile.patch/1.1.2.1/Sun May 12 13:16:48 2002//TBUGZILLA-2_16_2
-/gfdl.sgml/1.4.2.1/Sun May 12 16:15:29 2002//TBUGZILLA-2_16_2
-/glossary.sgml/1.5.2.2/Sun May 12 16:15:29 2002//TBUGZILLA-2_16_2
-/index.sgml/1.3/Wed May 8 23:19:09 2002//TBUGZILLA-2_16_2
-/installation.sgml/1.18.2.5/Thu Jul 25 21:03:29 2002//TBUGZILLA-2_16_2
-/integration.sgml/1.7.2.2/Sat May 25 15:36:08 2002//TBUGZILLA-2_16_2
-/introduction.sgml/1.1.2.2/Thu Jul 25 21:03:29 2002//TBUGZILLA-2_16_2
-/patches.sgml/1.13.2.3/Sat May 25 15:36:10 2002//TBUGZILLA-2_16_2
-/using.sgml/1.10.2.5/Thu Jul 25 21:03:29 2002//TBUGZILLA-2_16_2
-/variants.sgml/1.6.2.5/Thu Jul 25 21:03:30 2002//TBUGZILLA-2_16_2
-D
diff --git a/docs/sgml/CVS/Repository b/docs/sgml/CVS/Repository
deleted file mode 100644
index 7f128f54eedb7a4be0985191c38739e69f30edaf..0000000000000000000000000000000000000000
--- a/docs/sgml/CVS/Repository
+++ /dev/null
@@ -1 +0,0 @@
-mozilla/webtools/bugzilla/docs/sgml
diff --git a/docs/sgml/CVS/Tag b/docs/sgml/CVS/Tag
deleted file mode 100644
index 7e397d800d56db36f5d0dbb288351253afffee08..0000000000000000000000000000000000000000
--- a/docs/sgml/CVS/Tag
+++ /dev/null
@@ -1 +0,0 @@
-NBUGZILLA-2_16_2
diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt
index 090154f99756dedcc769dbce62ed6805b2dc06ca..089c0cda3946315a7a28cdbcd7e570313f11819b 100644
--- a/docs/txt/Bugzilla-Guide.txt
+++ b/docs/txt/Bugzilla-Guide.txt
@@ -1,5 +1,11 @@
-The Bugzilla GuideMatthew P. BarnsonThe Bugzilla Team
+The Bugzilla Guide - 2.16.3 Release
+
+Matthew P. Barnson
+
+The Bugzilla Team
+
+ 2003-04-23
This is the documentation for Bugzilla, the mozilla.org bug-tracking
system. Bugzilla is an enterprise-class piece of software that powers
@@ -7,9 +13,9 @@ The Bugzilla GuideMatthew P. BarnsonThe Bugzilla Team
tracking millions of bugs.
This documentation is maintained in DocBook 4.1.2 XML format. Changes
- are best submitted as plain text or SGML diffs, attached to a bug
- filed in mozilla.org's Bugzilla.
- _______________________________________________________________________
+ are best submitted as plain text or XML diffs, attached to a bug filed
+ in mozilla.org's Bugzilla.
+ _________________________________________________________________
Table of Contents
1. About This Guide
@@ -71,13 +77,36 @@ The Bugzilla GuideMatthew P. BarnsonThe Bugzilla Team
D.5. Perforce SCM
D.6. SourceForge
+ E. GNU Free Documentation License
+
+ 0. PREAMBLE
+ 1. APPLICABILITY AND DEFINITIONS
+ 2. VERBATIM COPYING
+ 3. COPYING IN QUANTITY
+ 4. MODIFICATIONS
+ 5. COMBINING DOCUMENTS
+ 6. COLLECTIONS OF DOCUMENTS
+ 7. AGGREGATION WITH INDEPENDENT WORKS
+ 8. TRANSLATION
+ 9. TERMINATION
+ 10. FUTURE REVISIONS OF THIS LICENSE
+ How to use this License for your documents
+
Glossary
+ List of Figures
+ 4-1. Other File::Temp error messages
+ 4-2. Patch for File::Temp in Perl 5.6.0
+
List of Examples
4-1. Installing ActivePerl ppd Modules on Microsoft Windows
4-2. Installing OpenInteract ppd Modules manually on Microsoft Windows
4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier
+
+ 5-1. Upgrading using CVS
+ 5-2. Upgrading using the tarball
+ 5-3. Upgrading using patches
_________________________________________________________________
Chapter 1. About This Guide
@@ -90,454 +119,126 @@ Chapter 1. About This Guide
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and with no Back-Cover
- Texts. A copy of the license is included below.
+ Texts. A copy of the license is included in Appendix E.
---Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team
+ --Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team
If you have any questions regarding this document, its copyright, or
publishing this document in non-electronic form, please contact The
Bugzilla Team.
_________________________________________________________________
-1.1.1. GNU Free Documentation License
-
-Version 1.1, March 2000
-
- Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
- Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy
- and distribute verbatim copies of this license document, but
- changing it is not allowed.
- _________________________________________________________________
-
-0. PREAMBLE
-
-The purpose of this License is to make a manual, textbook, or other written
-document "free" in the sense of freedom: to assure everyone the effective
-freedom to copy and redistribute it, with or without modifying it, either
-commercially or noncommercially. Secondarily, this License preserves for the
-author and publisher a way to get credit for their work, while not being
-considered responsible for modifications made by others.
-
-This License is a kind of "copyleft", which means that derivative works of
-the document must themselves be free in the same sense. It complements the
-GNU General Public License, which is a copyleft license designed for free
-software.
-
-We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free program
-should come with manuals providing the same freedoms that the software does.
-But this License is not limited to software manuals; it can be used for any
-textual work, regardless of subject matter or whether it is published as a
-printed book. We recommend this License principally for works whose purpose
-is instruction or reference.
- _________________________________________________________________
-
-1. APPLICABILITY AND DEFINITIONS
-
-This License applies to any manual or other work that contains a notice
-placed by the copyright holder saying it can be distributed under the terms
-of this License. The "Document", below, refers to any such manual or work.
-Any member of the public is a licensee, and is addressed as "you".
-
-A "Modified Version" of the Document means any work containing the Document
-or a portion of it, either copied verbatim, or with modifications and/or
-translated into another language.
-
-A "Secondary Section" is a named appendix or a front-matter section of the
-Document that deals exclusively with the relationship of the publishers or
-authors of the Document to the Document's overall subject (or to related
-matters) and contains nothing that could fall directly within that overall
-subject. (For example, if the Document is in part a textbook of mathematics,
-a Secondary Section may not explain any mathematics.) The relationship could
-be a matter of historical connection with the subject or with related
-matters, or of legal, commercial, philosophical, ethical or political
-position regarding them.
-
-The "Invariant Sections" are certain Secondary Sections whose titles are
-designated, as being those of Invariant Sections, in the notice that says
-that the Document is released under this License.
-
-The "Cover Texts" are certain short passages of text that are listed, as
-Front-Cover Texts or Back-Cover Texts, in the notice that says that the
-Document is released under this License.
-
-A "Transparent" copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the general
-public, whose contents can be viewed and edited directly and
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or for
-automatic translation to a variety of formats suitable for input to text
-formatters. A copy made in an otherwise Transparent file format whose markup
-has been designed to thwart or discourage subsequent modification by readers
-is not Transparent. A copy that is not "Transparent" is called "Opaque".
-
-Examples of suitable formats for Transparent copies include plain ASCII
-without markup, Texinfo input format, LaTeX input format, SGML or XML using
-a publicly available DTD, and standard-conforming simple HTML designed for
-human modification. Opaque formats include PostScript, PDF, proprietary
-formats that can be read and edited only by proprietary word processors,
-SGML or XML for which the DTD and/or processing tools are not generally
-available, and the machine-generated HTML produced by some word processors
-for output purposes only.
-
-The "Title Page" means, for a printed book, the title page itself, plus such
-following pages as are needed to hold, legibly, the material this License
-requires to appear in the title page. For works in formats which do not have
-any title page as such, "Title Page" means the text near the most prominent
-appearance of the work's title, preceding the beginning of the body of the
-text.
- _________________________________________________________________
-
-2. VERBATIM COPYING
-
-You may copy and distribute the Document in any medium, either commercially
-or noncommercially, provided that this License, the copyright notices, and
-the license notice saying this License applies to the Document are
-reproduced in all copies, and that you add no other conditions whatsoever to
-those of this License. You may not use technical measures to obstruct or
-control the reading or further copying of the copies you make or distribute.
-However, you may accept compensation in exchange for copies. If you
-distribute a large enough number of copies you must also follow the
-conditions in section 3.
-
-You may also lend copies, under the same conditions stated above, and you
-may publicly display copies.
- _________________________________________________________________
-
-3. COPYING IN QUANTITY
-
-If you publish printed copies of the Document numbering more than 100, and
-the Document's license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover Texts:
-Front-Cover Texts on the front cover, and Back-Cover Texts on the back
-cover. Both covers must also clearly and legibly identify you as the
-publisher of these copies. The front cover must present the full title with
-all words of the title equally prominent and visible. You may add other
-material on the covers in addition. Copying with changes limited to the
-covers, as long as they preserve the title of the Document and satisfy these
-conditions, can be treated as verbatim copying in other respects.
-
-If the required texts for either cover are too voluminous to fit legibly,
-you should put the first ones listed (as many as fit reasonably) on the
-actual cover, and continue the rest onto adjacent pages.
-
-If you publish or distribute Opaque copies of the Document numbering more
-than 100, you must either include a machine-readable Transparent copy along
-with each Opaque copy, or state in or with each Opaque copy a
-publicly-accessible computer-network location containing a complete
-Transparent copy of the Document, free of added material, which the general
-network-using public has access to download anonymously at no charge using
-public-standard network protocols. If you use the latter option, you must
-take reasonably prudent steps, when you begin distribution of Opaque copies
-in quantity, to ensure that this Transparent copy will remain thus
-accessible at the stated location until at least one year after the last
-time you distribute an Opaque copy (directly or through your agents or
-retailers) of that edition to the public.
-
-It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give them
-a chance to provide you with an updated version of the Document.
- _________________________________________________________________
-
-4. MODIFICATIONS
-
-You may copy and distribute a Modified Version of the Document under the
-conditions of sections 2 and 3 above, provided that you release the Modified
-Version under precisely this License, with the Modified Version filling the
-role of the Document, thus licensing distribution and modification of the
-Modified Version to whoever possesses a copy of it. In addition, you must do
-these things in the Modified Version:
-
- A. Use in the Title Page (and on the covers, if any) a title distinct
- from that of the Document, and from those of previous versions
- (which should, if there were any, be listed in the History section
- of the Document). You may use the same title as a previous version
- if the original publisher of that version gives permission.
- B. List on the Title Page, as authors, one or more persons or
- entities responsible for authorship of the modifications in the
- Modified Version, together with at least five of the principal
- authors of the Document (all of its principal authors, if it has
- less than five).
- C. State on the Title page the name of the publisher of the Modified
- Version, as the publisher.
- D. Preserve all the copyright notices of the Document.
- E. Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.
- F. Include, immediately after the copyright notices, a license notice
- giving the public permission to use the Modified Version under the
- terms of this License, in the form shown in the Addendum below.
- G. Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's license
- notice.
- H. Include an unaltered copy of this License.
- I. Preserve the section entitled "History", and its title, and add to
- it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.
- J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the "History" section. You
- may omit a network location for a work that was published at least
- four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.
- K. In any section entitled "Acknowledgements" or "Dedications",
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements
- and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document, unaltered in
- their text and in their titles. Section numbers or the equivalent
- are not considered part of the section titles.
- M. Delete any section entitled "Endorsements". Such a section may not
- be included in the Modified Version.
- N. Do not retitle any existing section as "Endorsements" or to
- conflict in title with any Invariant Section.
-
- If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all
- of these sections as invariant. To do this, add their titles to the
- list of Invariant Sections in the Modified Version's license notice.
- These titles must be distinct from any other section titles.
-
- You may add a section entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various
- parties--for example, statements of peer review or that the text has
- been approved by an organization as the authoritative definition of a
- standard.
-
- You may add a passage of up to five words as a Front-Cover Text, and a
- passage of up to 25 words as a Back-Cover Text, to the end of the list
- of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document already
- includes a cover text for the same cover, previously added by you or
- by arrangement made by the same entity you are acting on behalf of,
- you may not add another; but you may replace the old one, on explicit
- permission from the previous publisher that added the old one.
-
- The author(s) and publisher(s) of the Document do not by this License
- give permission to use their names for publicity for or to assert or
- imply endorsement of any Modified Version.
- _________________________________________________________________
-
-5. COMBINING DOCUMENTS
-
-You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified versions,
-provided that you include in the combination all of the Invariant Sections
-of all of the original documents, unmodified, and list them all as Invariant
-Sections of your combined work in its license notice.
-
-The combined work need only contain one copy of this License, and multiple
-identical Invariant Sections may be replaced with a single copy. If there
-are multiple Invariant Sections with the same name but different contents,
-make the title of each such section unique by adding at the end of it, in
-parentheses, the name of the original author or publisher of that section if
-known, or else a unique number. Make the same adjustment to the section
-titles in the list of Invariant Sections in the license notice of the
-combined work.
-
-In the combination, you must combine any sections entitled "History" in the
-various original documents, forming one section entitled "History"; likewise
-combine any sections entitled "Acknowledgements", and any sections entitled
-"Dedications". You must delete all sections entitled "Endorsements."
- _________________________________________________________________
-
-6. COLLECTIONS OF DOCUMENTS
-
-You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in the
-collection, provided that you follow the rules of this License for verbatim
-copying of each of the documents in all other respects.
-
-You may extract a single document from such a collection, and distribute it
-individually under this License, provided you insert a copy of this License
-into the extracted document, and follow this License in all other respects
-regarding verbatim copying of that document.
- _________________________________________________________________
-
-7. AGGREGATION WITH INDEPENDENT WORKS
-
-A compilation of the Document or its derivatives with other separate and
-independent documents or works, in or on a volume of a storage or
-distribution medium, does not as a whole count as a Modified Version of the
-Document, provided no compilation copyright is claimed for the compilation.
-Such a compilation is called an "aggregate", and this License does not apply
-to the other self-contained works thus compiled with the Document, on
-account of their being thus compiled, if they are not themselves derivative
-works of the Document.
-
-If the Cover Text requirement of section 3 is applicable to these copies of
-the Document, then if the Document is less than one quarter of the entire
-aggregate, the Document's Cover Texts may be placed on covers that surround
-only the Document within the aggregate. Otherwise they must appear on covers
-around the whole aggregate.
- _________________________________________________________________
-
-8. TRANSLATION
-
-Translation is considered a kind of modification, so you may distribute
-translations of the Document under the terms of section 4. Replacing
-Invariant Sections with translations requires special permission from their
-copyright holders, but you may include translations of some or all Invariant
-Sections in addition to the original versions of these Invariant Sections.
-You may include a translation of this License provided that you also include
-the original English version of this License. In case of a disagreement
-between the translation and the original English version of this License,
-the original English version will prevail.
- _________________________________________________________________
-
-9. TERMINATION
-
-You may not copy, modify, sublicense, or distribute the Document except as
-expressly provided for under this License. Any other attempt to copy,
-modify, sublicense or distribute the Document is void, and will
-automatically terminate your rights under this License. However, parties who
-have received copies, or rights, from you under this License will not have
-their licenses terminated so long as such parties remain in full compliance.
- _________________________________________________________________
-
-10. FUTURE REVISIONS OF THIS LICENSE
-
-The Free Software Foundation may publish new, revised versions of the GNU
-Free Documentation License from time to time. Such new versions will be
-similar in spirit to the present version, but may differ in detail to
-address new problems or concerns. See http://www.gnu.org/copyleft/ .
-
-Each version of the License is given a distinguishing version number. If the
-Document specifies that a particular numbered version of this License "or
-any later version" applies to it, you have the option of following the terms
-and conditions either of that specified version or of any later version that
-has been published (not as a draft) by the Free Software Foundation. If the
-Document does not specify a version number of this License, you may choose
-any version ever published (not as a draft) by the Free Software Foundation.
- _________________________________________________________________
-
-How to use this License for your documents
-
-To use this License in a document you have written, include a copy of the
-License in the document and put the following copyright and license notices
-just after the title page:
-
- Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
- distribute and/or modify this document under the terms of the GNU
- Free Documentation License, Version 1.1 or any later version
- published by the Free Software Foundation; with the Invariant
- Sections being LIST THEIR TITLES, with the Front-Cover Texts being
- LIST, and with the Back-Cover Texts being LIST. A copy of the
- license is included in the section entitled "GNU Free Documentation
- License".
-
- If you have no Invariant Sections, write "with no Invariant Sections"
- instead of saying which ones are invariant. If you have no Front-Cover
- Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts
- being LIST"; likewise for Back-Cover Texts.
-
- If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of
- free software license, such as the GNU General Public License, to
- permit their use in free software.
- _________________________________________________________________
-
1.2. Disclaimer
-No liability for the contents of this document can be accepted. Use the
-concepts, examples, and other content at your own risk. This document may
-contain errors and inaccuracies that may damage your system, cause your
-partner to leave you, your boss to fire you, your cats to pee on your
-furniture and clothing, and global thermonuclear war. Proceed with caution.
-
-All copyrights are held by their respective owners, unless specifically
-noted otherwise. Use of a term in this document should not be regarded as
-affecting the validity of any trademark or service mark.
-
-Naming of particular products or brands should not be seen as endorsements,
-with the exception of the term "GNU/Linux". We wholeheartedly endorse the
-use of GNU/Linux in every situation where it is appropriate. It is an
-extremely versatile, stable, and robust operating system that offers an
-ideal operating environment for Bugzilla.
-
-You are strongly recommended to make a backup of your system before
-installing Bugzilla and at regular intervals thereafter. If you implement
-any suggestion in this Guide, implement this one!
-
-Although the Bugzilla development team has taken great care to ensure that
-all easily-exploitable bugs or options are documented or fixed in the code,
-security holes surely exist. 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. The Bugzilla development
-team members, Netscape Communications, America Online Inc., and any
-affiliated developers or sponsors assume no liability for your use of this
-product. You have the source code to this product, and are responsible for
-auditing it yourself to ensure your security needs are met.
+ No liability for the contents of this document can be accepted. Use
+ the concepts, examples, and other content at your own risk. This
+ document may contain errors and inaccuracies that may damage your
+ system, cause your partner to leave you, your boss to fire you, your
+ cats to pee on your furniture and clothing, and global thermonuclear
+ war. Proceed with caution.
+
+ All copyrights are held by their respective owners, unless
+ specifically noted otherwise. Use of a term in this document should
+ not be regarded as affecting the validity of any trademark or service
+ mark.
+
+ Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". We
+ wholeheartedly endorse the use of GNU/Linux in every situation where
+ it is appropriate. It is an extremely versatile, stable, and robust
+ operating system that offers an ideal operating environment for
+ Bugzilla.
+
+ You are strongly recommended to make a backup of your system before
+ installing Bugzilla and at regular intervals thereafter. If you
+ implement any suggestion in this Guide, implement this one!
+
+ Although the Bugzilla development team has taken great care to ensure
+ that all easily-exploitable bugs or options are documented or fixed in
+ the code, security holes surely exist. 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. The
+ Bugzilla development team members, Netscape Communications, America
+ Online Inc., and any affiliated developers or sponsors assume no
+ liability for your use of this product. You have the source code to
+ this product, and are responsible for auditing it yourself to ensure
+ your security needs are met.
_________________________________________________________________
1.3. New Versions
-This is the 2.16 version of The Bugzilla Guide. It is so named to match the
-current version of Bugzilla. If you are reading this from any source other
-than those below, please check one of these mirrors to make sure you are
-reading an up-to-date version of the Guide.
+ This is the 2.16.3 version of The Bugzilla Guide. It is so named to
+ match the version of Bugzilla it is disributed with. If you are
+ reading this from any source other than those below, please check one
+ of these mirrors to make sure you are reading an up-to-date version of
+ the Guide.
-This document can be found in the following places:
+ The newest version of this guide can always be found at bugzilla.org;
+ including documentation for past releases and the current development
+ version.
- * bugzilla.org
- * The Linux Documentation Project
+ The documentation for the most recent stable release of Bugzilla can
+ also be found at The Linux Documentation Project.
The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at the Mozilla CVS page, and
+ Please follow the instructions available at the Mozilla CVS page, and
check out the mozilla/webtools/bugzilla/docs/ subtree.
- The Bugzilla Guide is currently only available in English. If you
+ The Bugzilla Guide is currently only available in English. If you
would like to volunteer to translate it, please contact Dave Miller.
_________________________________________________________________
1.4. Credits
-The people listed below have made enormous contributions to the creation of
-this Guide, through their writing, dedicated hacking efforts, numerous
-e-mail and IRC support sessions, and overall excellent contribution to the
-Bugzilla community:
-
-Matthew P. Barnson for the Herculaean task of pulling together the Bugzilla
-Guide and shepherding it to 2.14.
-
-Terry Weissman for initially writing Bugzilla and creating the README upon
-which the UNIX installation documentation is largely based.
-
-Tara Hernandez for keeping Bugzilla development going strong after Terry
-left mozilla.org
-
-Dave Lawrence for providing insight into the key differences between Red
-Hat's customized Bugzilla, and being largely responsible for the "Red Hat
-Bugzilla" appendix
-
-Dawn Endico for being a hacker extraordinaire and putting up with my
-incessant questions and arguments on irc.mozilla.org in #mozwebtools
-
-Last but not least, all the members of the netscape.public.mozilla.webtools
-newsgroup. Without your discussions, insight, suggestions, and patches, this
-could never have happened.
-
-Thanks also go to the following people for significant contributions to this
-documentation (in no particular order):
-
-Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
-Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
+ The people listed below have made enormous contributions to the
+ creation of this Guide, through their writing, dedicated hacking
+ efforts, numerous e-mail and IRC support sessions, and overall
+ excellent contribution to the Bugzilla community:
+
+ Matthew P. Barnson <mbarnson@sisna.com>
+ for the Herculaean task of pulling together the Bugzilla Guide
+ and shepherding it to 2.14.
+
+ Terry Weissman <terry@mozilla.org>
+ for initially writing Bugzilla and creating the README upon
+ which the UNIX installation documentation is largely based.
+
+ Tara Hernandez <tara@tequilarists.org>
+ for keeping Bugzilla development going strong after Terry left
+ mozilla.org and for running landfill.
+
+ Dave Lawrence <dkl@redhat.com>
+ for providing insight into the key differences between Red
+ Hat's customized Bugzilla, and being largely responsible for
+ Section D.1.
+
+ Dawn Endico <endico@mozilla.org>
+ for being a hacker extraordinaire and putting up with Matthew's
+ incessant questions and arguments on irc.mozilla.org in
+ #mozwebtools
+
+ Jacob Steenhagen <jake@bugzilla.org>
+ for taking over documentation during the 2.17 development
+ period and backporting relevent docs changes to this 2.16
+ branch.
+
+ Last but not least, all the members of the
+ news://news.mozilla.org/netscape/public/mozilla/webtools newsgroup.
+ Without your discussions, insight, suggestions, and patches, this
+ could never have happened.
+
+ Thanks also go to the following people for significant contributions
+ to this documentation (in alphabetical order): Andrew Pearson, Ben
+ FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen,
+ Ron Teitelbaum, Spencer Smith, Zach Liption .
_________________________________________________________________
1.5. Document Conventions
-This document uses the following conventions:
+ This document uses the following conventions:
Descriptions Appearance
- Warnings
+ Use caution
Caution
@@ -552,7 +253,7 @@ This document uses the following conventions:
Note
Dear John...
- Information requiring special attention
+ Warnings
Warning
@@ -566,6 +267,7 @@ This document uses the following conventions:
Prompt of user command under tcsh shell tcsh$
Environment Variables VARIABLE
Emphasized word word
+ Term found in the glossary Bugzilla
Code Example
<para>
Beginning and end of paragraph
@@ -576,19 +278,20 @@ Chapter 2. Introduction
2.1. What is Bugzilla?
-Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow
-individual or groups of developers effectively to keep track of outstanding
-problems with their product. Bugzilla was originally written by Terry
-Weissman in a programming language called TCL, to replace a rudimentary
-bug-tracking database used internally by Netscape Communications. Terry
-later ported Bugzilla to Perl from TCL, and in Perl it remains to this day.
-Most commercial defect-tracking software vendors 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 boasts many advanced features. These include:
+ Bugzilla is a bug- or issue-tracking system. Bug-tracking systems
+ allow individual or groups of developers effectively to keep track of
+ outstanding problems with their product. Bugzilla was originally
+ written by Terry Weissman in a programming language called TCL, to
+ replace a rudimentary bug-tracking database used internally by
+ Netscape Communications. Terry later ported Bugzilla to Perl from TCL,
+ and in Perl it remains to this day. Most commercial defect-tracking
+ software vendors 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 boasts many advanced features. These include:
* Powerful searching
* User-configurable email notifications of bug changes
@@ -606,63 +309,68 @@ Bugzilla boasts many advanced features. These include:
2.2. Why Should We Use Bugzilla?
-For many years, defect-tracking software has remained principally the domain
-of large software development houses. Even then, most shops never bothered
-with bug-tracking software, and instead simply relied on shared lists and
-email to monitor the status of defects. This procedure is error-prone and
-tends to cause those bugs judged least significant by developers to be
-dropped or ignored.
-
-These days, many companies are finding that integrated defect-tracking
-systems reduce downtime, increase productivity, and raise customer
-satisfaction with their systems. Along with full disclosure, an open
-bug-tracker allows manufacturers to keep in touch with their clients and
-resellers, to communicate about problems effectively throughout the data
-management chain. Many corporations have also discovered that
-defect-tracking helps reduce costs by providing IT support accountability,
-telephone support knowledge bases, and a common, well-understood system for
-accounting for unusual system or software issues.
-
-But why should you use 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 and hardware bug tracking for luminaries such as
-Redhat, NASA, 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 positive
-feedback for good performance. How many times do you wake up in the morning,
-remembering that you were supposed to do something today, but you just can't
-quite remember? Put it in Bugzilla, and you have a record of it from which
-you can extrapolate milestones, predict product versions for integration,
-and follow the discussion trail that led to critical decisions.
-
-Ultimately, Bugzilla puts the power in your hands to improve your value to
-your employer or business while providing a usable framework for your
-natural attention to detail and knowledge store to flourish.
+ For many years, defect-tracking software has remained principally the
+ domain of large software development houses. Even then, most shops
+ never bothered with bug-tracking software, and instead simply relied
+ on shared lists and email to monitor the status of defects. This
+ procedure is error-prone and tends to cause those bugs judged least
+ significant by developers to be dropped or ignored.
+
+ These days, many companies are finding that integrated defect-tracking
+ systems reduce downtime, increase productivity, and raise customer
+ satisfaction with their systems. Along with full disclosure, an open
+ bug-tracker allows manufacturers to keep in touch with their clients
+ and resellers, to communicate about problems effectively throughout
+ the data management chain. Many corporations have also discovered that
+ defect-tracking helps reduce costs by providing IT support
+ accountability, telephone support knowledge bases, and a common,
+ well-understood system for accounting for unusual system or software
+ issues.
+
+ But why should you use 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 and hardware bug tracking for
+ luminaries such as Redhat, NASA, 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
+ positive feedback for good performance. How many times do you wake up
+ in the morning, remembering that you were supposed to do something
+ today, but you just can't quite remember? Put it in Bugzilla, and you
+ have a record of it from which you can extrapolate milestones, predict
+ product versions for integration, and follow the discussion trail that
+ led to critical decisions.
+
+ Ultimately, Bugzilla puts the power in your hands to improve your
+ value to your employer or business while providing a usable framework
+ for your natural attention to detail and knowledge store to flourish.
_________________________________________________________________
Chapter 3. Using Bugzilla
3.1. How do I use Bugzilla?
-This section contains information for end-users of Bugzilla. There is a
-Bugzilla test installation, called Landfill, which you are welcome to play
-with (if it's up.) However, it does not necessarily have all Bugzilla
-features enabled, and often runs cutting-edge versions of Bugzilla for
-testing, so some things may work slightly differently than mentioned here.
+ This section contains information for end-users of Bugzilla. There is
+ a Bugzilla test installation, called Landfill, which you are welcome
+ to play with (if it's up.) However, it does not necessarily have all
+ Bugzilla features enabled, and often runs cutting-edge versions of
+ Bugzilla for testing, so some things may work slightly differently
+ than mentioned here.
_________________________________________________________________
3.1.1. Create a Bugzilla Account
-If you want to use Bugzilla, first you need to create an account. Consult
-with the administrator responsible for your installation of Bugzilla for the
-URL you should use to access it. If you're test-driving Bugzilla, use this
-URL: http://landfill.bugzilla.org/bugzilla-tip/
+ If you want to use Bugzilla, first you need to create an account.
+ Consult with the administrator responsible for your installation of
+ Bugzilla for the URL you should use to access it. If you're
+ test-driving Bugzilla, use this URL:
+ http://landfill.bugzilla.org/bugzilla-tip/
1. Click the "Open a new Bugzilla account" link, enter your email
address and, optionally, your name in the spaces provided, then
@@ -682,11 +390,12 @@ URL: http://landfill.bugzilla.org/bugzilla-tip/
3.1.2. Anatomy of a Bug
-The core of Bugzilla is the screen which displays a particular bug. It's a
-good place to explain some Bugzilla concepts. Bug 1 on Landfill is a good
-example. Note that the labels for most fields are hyperlinks; clicking them
-will take you to context-sensitive help on that particular field. Fields
-marked * may not be present on every installation of Bugzilla.
+ The core of Bugzilla is the screen which displays a particular bug.
+ It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill
+ is a good example. Note that the labels for most fields are
+ hyperlinks; clicking them will take you to context-sensitive help on
+ that particular field. Fields marked * may not be present on every
+ installation of Bugzilla.
1. Product and Component: Bugs are divided up by Product and
Component, with a Product having one or more Components in it. For
@@ -757,32 +466,32 @@ marked * may not be present on every installation of Bugzilla.
3.1.3. Searching for Bugs
-The Bugzilla Search page is is the interface where you can find any bug
-report, comment, or patch currently in the Bugzilla system. You can play
-with it here: landfill.bugzilla.org/bugzilla-tip/query.cgi .
+ The Bugzilla Search page is is the interface where you can find any
+ bug report, comment, or patch currently in the Bugzilla system. You
+ can play with it here: landfill.bugzilla.org/bugzilla-tip/query.cgi .
-The Search page has controls for selecting different possible values for all
-of the fields in a bug, as described above. Once you've defined a search,
-you can either run it, or save it as a Remembered Query, which can
-optionally appear in the footer of your pages.
+ The Search page has controls for selecting different possible values
+ for all of the fields in a bug, as described above. Once you've
+ defined a search, you can either run it, or save it as a Remembered
+ Query, which can optionally appear in the footer of your pages.
-Highly advanced querying is done using Boolean Charts, which have their own
-context-sensitive help .
+ Highly advanced querying is done using Boolean Charts, which have
+ their own context-sensitive help .
_________________________________________________________________
3.1.4. Bug Lists
-If you run a search, a list of matching bugs will be returned. The default
-search is to return all open bugs on the system - don't try running this
-search on a Bugzilla installation with a lot of bugs!
+ If you run a search, a list of matching bugs will be returned. The
+ default search is to return all open bugs on the system - don't try
+ running this search on a Bugzilla installation with a lot of bugs!
-The format of the list is configurable. For example, it can be sorted by
-clicking the column headings. Other useful features can be accessed using
-the links at the bottom of the list:
+ The format of the list is configurable. For example, it can be sorted
+ by clicking the column headings. Other useful features can be accessed
+ using the links at the bottom of the list:
Long Format: this gives you a large page with a non-editable summary
of the fields of each bug.
-Change Columns: change the bug attributes which appear in the list.
+ Change Columns: change the bug attributes which appear in the list.
Change several bugs at once: If your account is sufficiently
empowered, you can make the same change to all the bugs in the list -
for example, changing their owner.
@@ -796,15 +505,16 @@ Change Columns: change the bug attributes which appear in the list.
3.1.5. Filing Bugs
-Years of bug writing experience has been distilled for your reading pleasure
-into the Bug Writing Guidelines. While some of the advice is
-Mozilla-specific, the basic principles of reporting Reproducible, Specific
-bugs, isolating the Product you are using, the Version of the Product, the
-Component which failed, the Hardware Platform, and Operating System you were
-using at the time of the failure go a long way toward ensuring accurate,
-responsible fixes for the bug that bit you.
+ Years of bug writing experience has been distilled for your reading
+ pleasure into the Bug Writing Guidelines. While some of the advice is
+ Mozilla-specific, the basic principles of reporting Reproducible,
+ Specific bugs, isolating the Product you are using, the Version of the
+ Product, the Component which failed, the Hardware Platform, and
+ Operating System you were using at the time of the failure go a long
+ way toward ensuring accurate, responsible fixes for the bug that bit
+ you.
-The procedure for filing a test bug is as follows:
+ The procedure for filing a test bug is as follows:
1. Go to Landfill in your browser and click Enter a new bug report.
2. Select a product - any one will do.
@@ -816,26 +526,26 @@ The procedure for filing a test bug is as follows:
3.2. Hints and Tips
-This section distills some Bugzilla tips and best practices that have been
-developed.
+ This section distills some Bugzilla tips and best practices that have
+ been developed.
_________________________________________________________________
3.2.1. Autolinkification
-Bugzilla comments are plain text - so posting HTML will result in literal
-HTML tags rather than being interpreted by a browser. However, Bugzilla will
-automatically make hyperlinks out of certain sorts of text in comments. For
-example, the text http://www.bugzilla.org will be turned into
-http://www.bugzilla.org. Other strings which get linkified in the obvious
-manner are:
-
-bug 12345
-bug 23456, comment 53
-attachment 4321
-mailto:george@example.com
-george@example.com
-ftp://ftp.mozilla.org
-Most other sorts of URL
+ Bugzilla comments are plain text - so posting HTML will result in
+ literal HTML tags rather than being interpreted by a browser. However,
+ Bugzilla will automatically make hyperlinks out of certain sorts of
+ text in comments. For example, the text http://www.bugzilla.org will
+ be turned into http://www.bugzilla.org. Other strings which get
+ linkified in the obvious manner are:
+
+ bug 12345
+ bug 23456, comment 53
+ attachment 4321
+ mailto:george@example.com
+ george@example.com
+ ftp://ftp.mozilla.org
+ Most other sorts of URL
A corollary here is that if you type a bug number in a comment, you
should put the word "bug" before it, so it gets autolinkified for the
@@ -844,90 +554,94 @@ Most other sorts of URL
3.2.2. Quicksearch
-Quicksearch is a single-text-box query tool which uses metacharacters to
-indicate what is to be searched. For example, typing "foo|bar" into
-Quicksearch would search for "foo" or "bar" in the summary and status
-whiteboard of a bug; adding ":BazProduct" would search only in that product.
+ Quicksearch is a single-text-box query tool which uses metacharacters
+ to indicate what is to be searched. For example, typing "foo|bar" into
+ Quicksearch would search for "foo" or "bar" in the summary and status
+ whiteboard of a bug; adding ":BazProduct" would search only in that
+ product.
-You'll find the Quicksearch box on Bugzilla's front page, along with a Help
-link which details how to use it.
+ You'll find the Quicksearch box on Bugzilla's front page, along with a
+ Help link which details how to use it.
_________________________________________________________________
3.2.3. Comments
-If you are changing the fields on a bug, only comment if either you have
-something pertinent to say, or Bugzilla requires it. Otherwise, you may spam
-people unnecessarily with bug mail. To take an example: a user can set up
-their account to filter out messages where someone just adds themselves to
-the CC field of a bug (which happens a lot.) If you come along, add yourself
-to the CC field, and add a comment saying "Adding self to CC", then that
-person gets a pointless piece of mail they would otherwise have avoided.
-
-Don't use sigs in comments. Signing your name ("Bill") is acceptable,
-particularly if you do it out of habit, but full mail/news-style four line
-ASCII art creations are not.
+ If you are changing the fields on a bug, only comment if either you
+ have something pertinent to say, or Bugzilla requires it. Otherwise,
+ you may spam people unnecessarily with bug mail. To take an example: a
+ user can set up their account to filter out messages where someone
+ just adds themselves to the CC field of a bug (which happens a lot.)
+ If you come along, add yourself to the CC field, and add a comment
+ saying "Adding self to CC", then that person gets a pointless piece of
+ mail they would otherwise have avoided.
+
+ Don't use sigs in comments. Signing your name ("Bill") is acceptable,
+ particularly if you do it out of habit, but full mail/news-style four
+ line ASCII art creations are not.
_________________________________________________________________
3.2.4. Attachments
-Use attachments, rather than comments, for large chunks of ASCII data, such
-as trace, debugging output files, or log files. That way, it doesn't bloat
-the bug for everyone who wants to read it, and cause people to receive fat,
-useless mails.
+ Use attachments, rather than comments, for large chunks of ASCII data,
+ such as trace, debugging output files, or log files. That way, it
+ doesn't bloat the bug for everyone who wants to read it, and cause
+ people to receive fat, useless mails.
-Trim screenshots. There's no need to show the whole screen if you are
-pointing out a single-pixel problem.
+ Trim screenshots. There's no need to show the whole screen if you are
+ pointing out a single-pixel problem.
-Don't attach simple test cases (e.g. one HTML file, one CSS file and an
-image) as a ZIP file. Instead, upload them in reverse order and edit the
-referring file so that they point to the attached files. This way, the test
-case works immediately out of the bug.
+ Don't attach simple test cases (e.g. one HTML file, one CSS file and
+ an image) as a ZIP file. Instead, upload them in reverse order and
+ edit the referring file so that they point to the attached files. This
+ way, the test case works immediately out of the bug.
_________________________________________________________________
3.2.5. Filing Bugs
-Try to make sure that everything said in the summary is also said in the
-first comment. Summaries are often updated and this will ensure your
-original information is easily accessible.
+ Try to make sure that everything said in the summary is also said in
+ the first comment. Summaries are often updated and this will ensure
+ your original information is easily accessible.
-You do not need to put "any" or similar strings in the URL field. If there
-is no specific URL associated with the bug, leave this field blank.
+ You do not need to put "any" or similar strings in the URL field. If
+ there is no specific URL associated with the bug, leave this field
+ blank.
-If you feel a bug you filed was incorrectly marked as a DUPLICATE of
-another, please question it in your bug, not the bug it was duped to. Feel
-free to CC the person who duped it if they are not already CCed.
+ If you feel a bug you filed was incorrectly marked as a DUPLICATE of
+ another, please question it in your bug, not the bug it was duped to.
+ Feel free to CC the person who duped it if they are not already CCed.
_________________________________________________________________
3.3. User Preferences
-Once you have logged in, you can customise various aspects of Bugzilla via
-the "Edit prefs" link in the page footer. The preferences are split into
-four tabs:
+ Once you have logged in, you can customise various aspects of Bugzilla
+ via the "Edit prefs" link in the page footer. The preferences are
+ split into four tabs:
_________________________________________________________________
3.3.1. Account Settings
-On this tab, you can change your basic account information, including your
-password, email address and real name. For security reasons, in order to
-change anything on this page you must type your current password into the
-"Password" field at the top of the page. If you attempt to change your email
-address, a confirmation email is sent to both the old and new addresses,
-with a link to use to confirm the change. This helps to prevent account
-hijacking.
+ On this tab, you can change your basic account information, including
+ your password, email address and real name. For security reasons, in
+ order to change anything on this page you must type your current
+ password into the "Password" field at the top of the page. If you
+ attempt to change your email address, a confirmation email is sent to
+ both the old and new addresses, with a link to use to confirm the
+ change. This helps to prevent account hijacking.
_________________________________________________________________
3.3.2. Email Settings
-On this tab you can reduce or increase the amount of email sent you from
-Bugzilla, opting in our out depending on your relationship to the bug and
-the change that was made to it. (Note that you can also do client-side
-filtering using the X-Bugzilla-Reason header which Bugzilla adds to all
-bugmail.)
+ On this tab you can reduce or increase the amount of email sent you
+ from Bugzilla, opting in our out depending on your relationship to the
+ bug and the change that was made to it. (Note that you can also do
+ client-side filtering using the X-Bugzilla-Reason header which
+ Bugzilla adds to all bugmail.)
-By entering user email names, delineated by commas, into the "Users to
-watch" text entry box you can receive a copy of all the bugmail of other
-users (security settings permitting.) This powerful functionality enables
-seamless transitions as developers change projects or users go on holiday.
+ By entering user email names, delineated by commas, into the "Users to
+ watch" text entry box you can receive a copy of all the bugmail of
+ other users (security settings permitting.) This powerful
+ functionality enables seamless transitions as developers change
+ projects or users go on holiday.
Note
@@ -937,17 +651,18 @@ seamless transitions as developers change projects or users go on holiday.
3.3.3. Page Footer
-On the Search page, you can store queries in Bugzilla, so if you regularly
-run a particular query it is just a drop-down menu away. Once you have a
-stored query, you can come here to request that it also be displayed in your
-page footer.
+ On the Search page, you can store queries in Bugzilla, so if you
+ regularly run a particular query it is just a drop-down menu away.
+ Once you have a stored query, you can come here to request that it
+ also be displayed in your page footer.
_________________________________________________________________
3.3.4. Permissions
-This is a purely informative page which outlines your current permissions on
-this installation of Bugzilla - what product groups you are in, and whether
-you can edit bugs or perform various administration functions.
+ This is a purely informative page which outlines your current
+ permissions on this installation of Bugzilla - what product groups you
+ are in, and whether you can edit bugs or perform various
+ administration functions.
_________________________________________________________________
Chapter 4. Installation
@@ -956,10 +671,10 @@ Chapter 4. Installation
4.1.1. Introduction
-Bugzilla has been successfully installed under Solaris, Linux, and Win32.
-Win32 is not yet officially supported, but many people have got it working
-fine. Please see the Win32 Installation Notes for further advice on getting
-Bugzilla to work on Microsoft Windows.
+ Bugzilla has been successfully installed under Solaris, Linux, and
+ Win32. Win32 is not yet officially supported, but many people have got
+ it working fine. Please see the Win32 Installation Notes for further
+ advice on getting Bugzilla to work on Microsoft Windows.
_________________________________________________________________
4.1.2. Package List
@@ -1021,8 +736,8 @@ Bugzilla to work on Microsoft Windows.
4.1.3. MySQL
-Visit the MySQL homepage at www.mysql.com to grab and install the latest
-stable release of the server.
+ Visit the MySQL homepage at www.mysql.com to grab and install the
+ latest stable release of the server.
Note
@@ -1052,11 +767,12 @@ stable release of the server.
4.1.4. Perl
-Any machine that doesn't have Perl on it is a sad machine indeed. Perl can
-be got in source form from perl.com for the rare *nix systems which don't
-have it. Although Bugzilla runs with all post-5.005 versions of Perl, it's a
-good idea to be up to the very latest version if you can when running
-Bugzilla. As of this writing, that is Perl version 5.6.1.
+ Any machine that doesn't have Perl on it is a sad machine indeed. Perl
+ can be got in source form from perl.com for the rare *nix systems
+ which don't have it. Although Bugzilla runs with all post-5.005
+ versions of Perl, it's a good idea to be up to the very latest version
+ if you can when running Bugzilla. As of this writing, that is Perl
+ version 5.6.1.
Tip
@@ -1074,21 +790,22 @@ Bugzilla. As of this writing, that is Perl version 5.6.1.
4.1.5. Perl Modules
-All Perl modules can be found on the Comprehensive Perl Archive Network
-(CPAN). The CPAN servers have a real tendency to bog down, so please use
-mirrors.
+ All Perl modules can be found on the Comprehensive Perl Archive
+ Network (CPAN). The CPAN servers have a real tendency to bog down, so
+ please use mirrors.
-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 a module:
+ 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 a module:
-bash# perl -MCPAN -e 'install "<modulename>"'
+ bash# perl -MCPAN -e 'install "<modulename>"'
-To do it the hard way:
+ To do it the hard way:
-Untar the module tarball -- it should create its own directory
+ Untar the module tarball -- it should create its own directory
-CD to the directory just created, and enter the following commands:
+ CD to the directory just created, and enter the following commands:
1. bash# perl Makefile.PL
2. bash# make
@@ -1110,55 +827,56 @@ CD to the directory just created, and enter the following commands:
4.1.5.1. DBI
-The DBI module is a generic Perl module used 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.
+ The DBI module is a generic Perl module used 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.
_________________________________________________________________
4.1.5.2. Data::Dumper
-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.
+ 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.
_________________________________________________________________
4.1.5.3. MySQL-related modules
-The Perl/MySQL interface requires a few mutually-dependent Perl modules.
-These modules are grouped together into the the Msql-Mysql-modules package.
-
-The MakeMaker process will ask you a few questions about the desired
-compilation target and your MySQL installation. For most of the questions
-the provided default will be adequate, but when asked if your desired target
-is the MySQL or mSQL packages, you should select the MySQL related ones.
-Later you will be asked if you wish to provide backwards compatibility with
-the older MySQL packages; you should answer YES to this question. The
-default is NO.
-
-A host of 'localhost' should be fine and a testing user of 'test' with a
-null password should find itself with sufficient access to run tests on the
-'test' database which MySQL created upon installation.
+ The Perl/MySQL interface requires a few mutually-dependent Perl
+ modules. These modules are grouped together into the the
+ Msql-Mysql-modules package.
+
+ The MakeMaker process will ask you a few questions about the desired
+ compilation target and your MySQL installation. For most of the
+ questions the provided default will be adequate, but when asked if
+ your desired target is the MySQL or mSQL packages, you should select
+ the MySQL related ones. Later you will be asked if you wish to provide
+ backwards compatibility with the older MySQL packages; you should
+ answer YES to this question. The default is NO.
+
+ A host of 'localhost' should be fine and a testing user of 'test' with
+ a null password should find itself with sufficient access to run tests
+ on the 'test' database which MySQL created upon installation.
_________________________________________________________________
4.1.5.4. TimeDate modules
-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. The component module we're most
-interested in is the Date::Format module, but installing all of them is
-probably a good idea anyway.
+ 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. The component
+ module we're most interested in is the Date::Format module, but
+ installing all of them is probably a good idea anyway.
_________________________________________________________________
4.1.5.5. GD (optional)
-The GD library was written by Thomas Boutell a long while ago to
-programatically generate images in C. Since then it's become the defacto
-standard for programatic image construction. The Perl bindings to it found
-in the GD library are used on millions of web pages to generate graphs on
-the fly. That's what Bugzilla will be using it for so you must install it if
-you want any of the graphing to work.
+ The GD library was written by Thomas Boutell a long while ago to
+ programatically generate images in C. Since then it's become the
+ defacto standard for programatic image construction. The Perl bindings
+ to it found in the GD library are used on millions of web pages to
+ generate graphs on the fly. That's what Bugzilla will be using it for
+ so you must install it if you want any of the graphing to work.
Note
@@ -1170,27 +888,28 @@ you want any of the graphing to work.
4.1.5.6. Chart::Base (optional)
-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.
-Note that earlier versions that 0.99c used GIFs, which are no longer
-supported by the latest versions of GD.
+ 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. Note that earlier versions that 0.99c used GIFs, which are
+ no longer supported by the latest versions of GD.
_________________________________________________________________
4.1.5.7. Template Toolkit
-When you install Template Toolkit, you'll get asked various questions about
-features to enable. The defaults are fine, except that it is recommended you
-use the high speed XS Stash of the Template Toolkit, in order to achieve
-best performance. However, there are known problems with XS Stash and Perl
-5.005_02 and lower. If you wish to use these older versions of Perl, please
-use the regular stash.
+ When you install Template Toolkit, you'll get asked various questions
+ about features to enable. The defaults are fine, except that it is
+ recommended you use the high speed XS Stash of the Template Toolkit,
+ in order to achieve best performance. However, there are known
+ problems with XS Stash and Perl 5.005_02 and lower. If you wish to use
+ these older versions of Perl, please use the regular stash.
_________________________________________________________________
4.1.6. HTTP Server
-You have a freedom of choice here - Apache, Netscape or any other server on
-UNIX would do. You can run the web server on a different machine than MySQL,
-but need to adjust the MySQL "bugs" user permissions accordingly.
+ You have a freedom of choice here - Apache, Netscape or any other
+ server on UNIX would do. You can run the web server on a different
+ machine than MySQL, but need to adjust the MySQL "bugs" user
+ permissions accordingly.
Note
@@ -1207,7 +926,8 @@ but need to adjust the MySQL "bugs" user permissions accordingly.
With Apache you'll also want to make sure that within the httpd.conf
file the line:
- Options ExecCGI AllowOverride Limit
+Options ExecCGI
+AllowOverride Limit
is in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
@@ -1233,11 +953,11 @@ but need to adjust the MySQL "bugs" user permissions accordingly.
4.1.7. Bugzilla
-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 in the main web space for your web server or perhaps
-in /usr/local with a symbolic link in the web space that points to the
-Bugzilla directory.
+ 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 in the main web space for
+ your web server or perhaps in /usr/local with a symbolic link in the
+ web space that points to the Bugzilla directory.
Tip
@@ -1267,21 +987,21 @@ perl -pi -e
4.1.8. 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 the back end to a high quality
-bug tracker.
+ After you've gotten all the software installed and working you're
+ ready to start preparing the database for its life as the back end to
+ 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.
+ 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.
-Begin by giving the MySQL root user a password. MySQL passwords are limited
-to 16 characters.
+ Begin by giving the MySQL root user a password. MySQL passwords are
+ limited to 16 characters.
-bash# mysql -u root mysql
+ bash# mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD('<new_password'>) WHERE
user='root';
-mysql> FLUSH PRIVILEGES;
+ 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 <new_password>.
@@ -1301,17 +1021,23 @@ mysql> FLUSH PRIVILEGES;
ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
'<bugs_password>';
mysql> FLUSH PRIVILEGES;
+
+ Note
+
+ If you are using MySQL 4, the bugs user also needs to be granted the
+ LOCK TABLES and CREATE TEMPORARY TABLES permissions.
_________________________________________________________________
4.1.9. checksetup.pl
-Next, run the magic checksetup.pl script. (Many thanks to Holger Schurig for
-writing this script!) This script is designed to make sure your MySQL
-database and other configuration options are consistent with the Bugzilla
-CGI files. It will make sure Bugzilla files and directories have reasonable
-permissions, set up the data directory, and create all the MySQL tables.
+ Next, run the magic checksetup.pl script. (Many thanks to Holger
+ Schurig for writing this script!) This script is designed to make sure
+ your MySQL database and other configuration options are consistent
+ with the Bugzilla CGI files. 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
+ bash# ./checksetup.pl
The first time you run it, it will create a file called localconfig.
@@ -1339,85 +1065,21 @@ bash# ./checksetup.pl
Bugzilla.
_________________________________________________________________
-4.1.10. Securing MySQL
-
-If you followed the installation instructions 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. running MySQL in a chroot jail
- 4. running the httpd in a chroot 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 ;-)
- _________________________________________________________________
-
-4.1.11. Configuring Bugzilla
+4.1.10. Configuring Bugzilla
-You should run through the parameters on the Edit Parameters page (link in
-the footer) and set them all to appropriate values. They key parameters are
-documented in Section 5.1.
+ You should run through the parameters on the Edit Parameters page
+ (link in the footer) and set them all to appropriate values. They key
+ parameters are documented in Section 5.1.
_________________________________________________________________
4.2. Optional Additional Configuration
4.2.1. Dependency Charts
-As well as the text-based dependency graphs, Bugzilla also supports
-dependency graphing, using a package called 'dot'. Exactly how this works is
-controlled by the 'webdotbase' parameter, which can have one of three
-values:
+ As well as the text-based dependency graphs, Bugzilla also supports
+ dependency graphing, using a package called 'dot'. Exactly how this
+ works is controlled by the 'webdotbase' parameter, which can have one
+ of three values:
1. A complete file path to the command 'dot' (part of GraphViz) will
generate the graphs locally
@@ -1434,34 +1096,35 @@ values:
4.2.2. Bug Graphs
-As long as you installed the GD and Graph::Base Perl modules you might as
-well turn on the nifty Bugzilla bug reporting graphs.
+ 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.pl daily at 5 after midnight:
+ Add a cron entry like this to run collectstats.pl daily at 5 after
+ midnight:
-bash# crontab -e
-5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
+ 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
+ After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
_________________________________________________________________
4.2.3. The Whining Cron
-By now you have a fully functional Bugzilla, but what good are bugs if
-they're not annoying? To help make those bugs more annoying you can set up
-Bugzilla's automatic whining system to complain at engineers which leave
-their bugs in the NEW state without triaging them.
+ By now you have a fully functional Bugzilla, but what good are bugs if
+ they're not annoying? To help make those bugs more annoying you can
+ set up Bugzilla's automatic whining system to complain at engineers
+ which leave their bugs in the NEW state without triaging them.
-This can be done by adding the following command as a daily crontab entry
-(for help on that see that crontab man page):
+ 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
+ cd <your-bugzilla-directory> ; ./whineatnews.pl
Tip
- Depending on your system, crontab may have several manpages. The
- following command should lead you to the most useful page for this
+ Depending on your system, crontab may have several manpages. The
+ following command should lead you to the most useful page for this
purpose:
man 5 crontab
_________________________________________________________________
@@ -1474,81 +1137,82 @@ cd <your-bugzilla-directory> ; ./whineatnews.pl
Bugzilla is old, and the authors do not know of anyone who has tested
it. Approach with caution.
- The existing authentication scheme for Bugzilla uses email addresses
- as the primary user ID, and a password to authenticate that user. All
- places within Bugzilla where you need to deal with user ID (e.g
+ The existing authentication scheme for Bugzilla uses email addresses
+ as the primary user ID, and a password to authenticate that user. All
+ places within Bugzilla where you need to deal with user ID (e.g
assigning a bug) use the email address. The LDAP authentication builds
on top of this scheme, rather than replacing it. The initial log in is
- done with a username and password for the LDAP directory. This then
- fetches the email address from LDAP and authenticates seamlessly in
- the standard Bugzilla authentication scheme using this email address.
+ done with a username and password for the LDAP directory. This then
+ fetches the email address from LDAP and authenticates seamlessly in
+ the standard Bugzilla authentication scheme using this email address.
If an account for this address already exists in your Bugzilla system,
- it will log in to that account. If no account for that email address
- exists, one is created at the time of login. (In this case, Bugzilla
- will attempt to use the "displayName" or "cn" attribute to determine
- the user's full name.) After authentication, all other user-related
+ it will log in to that account. If no account for that email address
+ exists, one is created at the time of login. (In this case, Bugzilla
+ will attempt to use the "displayName" or "cn" attribute to determine
+ the user's full name.) After authentication, all other user-related
tasks are still handled by email address, not LDAP username. You still
assign bugs by email address, query on users by email address, etc.
Using LDAP for Bugzilla authentication requires the Mozilla::LDAP (aka
- PerLDAP) Perl module. The Mozilla::LDAP module in turn requires
+ PerLDAP) Perl module. The Mozilla::LDAP module in turn requires
Netscape's Directory SDK for C. After you have installed the SDK, then
- install the PerLDAP module. Mozilla::LDAP and the Directory SDK for C
+ install the PerLDAP module. Mozilla::LDAP and the Directory SDK for C
are both available for download from mozilla.org.
- Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
- directory for authentication. Be very careful when setting up this
- parameter; if you set LDAP authentication, but do not have a valid
+ Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
+ directory for authentication. Be very careful when setting up this
+ parameter; if you set LDAP authentication, but do not have a valid
LDAP directory set up, you will not be able to log back in to Bugzilla
- once you log out. (If this happens, you can get back in by manually
+ once you log out. (If this happens, you can get back in by manually
editing the data/params file, and setting useLDAP back to 0.)
- If using LDAP, you must set the three additional parameters: Set
- LDAPserver to the name (and optionally port) of your LDAP server. If
- no port is specified, it defaults to the default port of 389. (e.g
- "ldap.mycompany.com" or "ldap.mycompany.com:1234") Set LDAPBaseDN to
- the base DN for searching for users in your LDAP directory. (e.g.
- "ou=People,o=MyCompany") uids must be unique under the DN specified
- here. Set LDAPmailattribute to the name of the attribute in your LDAP
- directory which contains the primary email address. On most directory
+ If using LDAP, you must set the three additional parameters: Set
+ LDAPserver to the name (and optionally port) of your LDAP server. If
+ no port is specified, it defaults to the default port of 389. (e.g
+ "ldap.mycompany.com" or "ldap.mycompany.com:1234") Set LDAPBaseDN to
+ the base DN for searching for users in your LDAP directory. (e.g.
+ "ou=People,o=MyCompany") uids must be unique under the DN specified
+ here. Set LDAPmailattribute to the name of the attribute in your LDAP
+ directory which contains the primary email address. On most directory
servers available, this is "mail", but you may need to change this.
_________________________________________________________________
4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code
-It is possible for a Bugzilla to execute malicious Javascript code. Due to
-internationalization concerns, we are unable to incorporate the code changes
-necessary to fulfill the CERT advisory requirements mentioned in
-http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. Executing
-the following code snippet from a UNIX command shell will rectify the
-problem if your Bugzilla installation is intended for an English-speaking
-audience. As always, be sure your Bugzilla installation has a good backup
-before making changes, and I recommend you understand what the script is
-doing before executing it.
+ It is possible for a Bugzilla to execute malicious Javascript code.
+ Due to internationalization concerns, we are unable to incorporate the
+ code changes necessary to fulfill the CERT advisory requirements
+ mentioned in
+ http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3.
+ Executing the following code snippet from a UNIX command shell will
+ rectify the problem if your Bugzilla installation is intended for an
+ English-speaking audience. As always, be sure your Bugzilla
+ installation has a good backup before making changes, and I recommend
+ you understand what the script is doing before executing it.
bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; char
set=ISO-8859-1/i" *.cgi *.pl
- All this one-liner command does is search for all instances of
- "Content-type: text/html" and replaces it with "Content-Type:
- text/html; charset=ISO-8859-1" . This specification prevents possible
- Javascript attacks on the browser, and is suggested for all
- English-speaking sites. For non-English-speaking Bugzilla sites, I
+ All this one-liner command does is search for all instances of
+ "Content-type: text/html" and replaces it with "Content-Type:
+ text/html; charset=ISO-8859-1" . This specification prevents possible
+ Javascript attacks on the browser, and is suggested for all
+ English-speaking sites. For non-English-speaking Bugzilla sites, I
suggest changing "ISO-8859-1", above, to "UTF-8".
- Note: using <meta> tags to set the charset is not recommended, as
+ Note: using <meta> tags to set the charset is not recommended, as
there's a bug in Netscape 4.x which causes pages marked up in this way
to load twice.
_________________________________________________________________
4.2.6. .htaccess files and security
-To enhance the security of your Bugzilla installation, Bugzilla's
-checksetup.pl script will generate .htaccess files which the Apache
-webserver can use to restrict access to the bugzilla data files. These
-.htaccess files will not work with Apache 1.2.x - but this has security
-holes, so you shouldn't be using it anyway.
+ To enhance the security of your Bugzilla installation, Bugzilla's
+ checksetup.pl script will generate .htaccess files which the Apache
+ webserver can use to restrict access to the bugzilla data files. These
+ .htaccess files will not work with Apache 1.2.x - but this has
+ security holes, so you shouldn't be using it anyway.
Note
@@ -1557,12 +1221,12 @@ holes, so you shouldn't be using it anyway.
will need to change the ip address in data/webdot/.htaccess to the ip
address of the webdot server that you are using.
- The default .htaccess file may not provide adequate access
- restrictions, depending on your web server configuration. Be sure to
- check the <Directory> entries for your Bugzilla directory so that the
- .htaccess file is allowed to override web server defaults. For
- instance, let's assume your installation of Bugzilla is installed to
- /usr/local/bugzilla . You should have this <Directory> entry in your
+ The default .htaccess file may not provide adequate access
+ restrictions, depending on your web server configuration. Be sure to
+ check the <Directory> entries for your Bugzilla directory so that the
+ .htaccess file is allowed to override web server defaults. For
+ instance, let's assume your installation of Bugzilla is installed to
+ /usr/local/bugzilla . You should have this <Directory> entry in your
httpd.conf file:
<Directory /usr/local/bugzilla/>
@@ -1570,38 +1234,39 @@ holes, so you shouldn't be using it anyway.
AllowOverride All
</Directory>
- The important part above is "AllowOverride All" . Without that, the
- .htaccess file created by checksetup.pl will not have sufficient
+ The important part above is "AllowOverride All" . Without that, the
+ .htaccess file created by checksetup.pl will not have sufficient
permissions to protect your Bugzilla installation.
- If you are using Internet Information Server (IIS) or another web
- server which does not observe .htaccess conventions, you can disable
+ If you are using Internet Information Server (IIS) or another web
+ server which does not observe .htaccess conventions, you can disable
their creation by editing localconfig and setting the $create_htaccess
variable to 0.
_________________________________________________________________
4.2.7. mod_throttle and Security
-It is possible for a user, by mistake or on purpose, to access the database
-many times in a row which can result in very slow access speeds for other
-users. If your Bugzilla installation is experiencing this problem , you may
-install the Apache module mod_throttle which can limit connections by
-ip-address. You may download this module at
-http://www.snert.com/Software/Throttle/. Follow the instructions to install
-into your Apache install. This module only functions with the Apache web
-server! You may use the ThrottleClientIP command provided by this module to
-accomplish this goal. See the Module Instructions for more information.
+ It is possible for a user, by mistake or on purpose, to access the
+ database many times in a row which can result in very slow access
+ speeds for other users. If your Bugzilla installation is experiencing
+ this problem , you may install the Apache module mod_throttle which
+ can limit connections by ip-address. You may download this module at
+ http://www.snert.com/Software/Throttle/. Follow the instructions to
+ install into your Apache install. This module only functions with the
+ Apache web server! You may use the ThrottleClientIP command provided
+ by this module to accomplish this goal. See the Module Instructions
+ for more information.
_________________________________________________________________
4.3. Win32 Installation Notes
-This section covers installation on Microsoft Windows. Bugzilla has been
-made to work on Win32 platforms, but the Bugzilla team wish to emphasise
-that The easiest way to install Bugzilla on Intel-archiecture machines is to
-install some variant of GNU/Linux, then follow the UNIX installation
-instructions in this Guide. If you have any influence in the platform choice
-for running this system, please choose GNU/Linux instead of Microsoft
-Windows.
+ This section covers installation on Microsoft Windows. Bugzilla has
+ been made to work on Win32 platforms, but the Bugzilla team wish to
+ emphasise that The easiest way to install Bugzilla on
+ Intel-archiecture machines is to install some variant of GNU/Linux,
+ then follow the UNIX installation instructions in this Guide. If you
+ have any influence in the platform choice for running this system,
+ please choose GNU/Linux instead of Microsoft Windows.
Warning
@@ -1613,11 +1278,11 @@ Windows.
pleasant than it is now.
If you still want to try this, to have any hope of getting it to work,
- you'll need to apply the mail patch from bug 124174. After that,
- you'll need to read the (outdated) installation instructions below,
- some (probably a lot better) more recent ones kindly provided by Toms
+ you'll need to apply the mail patch from bug 124174. After that,
+ you'll need to read the (outdated) installation instructions below,
+ some (probably a lot better) more recent ones kindly provided by Toms
Baugis and Jean-Sebastien Guay, and also check the Bugzilla 2.16 Win32
- update page . If we get time, we'll write some better installation
+ update page . If we get time, we'll write some better installation
instructions for 2.16 and put them up there. But no promises.
_________________________________________________________________
@@ -1637,75 +1302,74 @@ Windows.
source code and implementing some advanced utilities. What follows is
the recommended installation procedure for Win32; additional
suggestions are provided in Appendix A .
-
1. Install Apache Web Server for Windows, and copy the Bugzilla files
- somewhere Apache can serve them. Please follow all the
- instructions referenced in Bugzilla Installation regarding your
- Apache configuration, particularly instructions regarding the
+ somewhere Apache can serve them. Please follow all the
+ instructions referenced in Bugzilla Installation regarding your
+ Apache configuration, particularly instructions regarding the
"AddHandler" parameter and "ExecCGI" .
Note
- You may also use Internet Information Server or Personal Web Server
- for this purpose. However, setup is quite different. If ActivePerl
- doesn't seem to handle your file associations correctly (for .cgi and
+ You may also use Internet Information Server or Personal Web Server
+ for this purpose. However, setup is quite different. If ActivePerl
+ doesn't seem to handle your file associations correctly (for .cgi and
.pl files), please consult Appendix A .
- If you are going to use IIS, if on Windows NT you must be updated to
- at least Service Pack 4. Windows 2000 ships with a sufficient version
+ If you are going to use IIS, if on Windows NT you must be updated to
+ at least Service Pack 4. Windows 2000 ships with a sufficient version
of IIS.
2. Install ActivePerl for Windows. Check
- http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a
+ http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a
current compiled binary.
- Please also check the following links to fully understand the
- status of ActivePerl on Win32: Perl Porting , and Perl on Win32
+ Please also check the following links to fully understand the
+ status of ActivePerl on Win32: Perl Porting , and Perl on Win32
FAQ
- 3. Use ppm from your perl\bin directory to install the following
+ 3. Use ppm from your perl\bin directory to install the following
packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
- AppConfig, and Template. You may need to extract them from .zip
- format using Winzip or other unzip program first. Most of these
- additional ppm modules can be downloaded from ActiveState, but
- AppConfig and Template should be obtained from OpenInteract using
+ AppConfig, and Template. You may need to extract them from .zip
+ format using Winzip or other unzip program first. Most of these
+ additional ppm modules can be downloaded from ActiveState, but
+ AppConfig and Template should be obtained from OpenInteract using
the instructions on the Template Toolkit web site .
Note
You can find a list of modules at
- http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or
+ http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or
http://www.activestate.com/PPMPackages/5.6plus
The syntax for ppm is: C:> ppm <modulename>
- Example 4-1. Installing ActivePerl ppd Modules on Microsoft
+ Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows
C:> ppm DBD-Mysql
Watch your capitalization!
ActiveState's 5.6Plus directory also contains an AppConfig ppm, so
- you might see the following error when trying to install the
+ you might see the following error when trying to install the
version at OpenInteract:
- Error installing package 'AppConfig': Read a PPD for 'AppConfig',
- but it is not intended for this build of Perl
+ Error installing package 'AppConfig': Read a PPD for 'AppConfig',
+ but it is not intended for this build of Perl
(MSWin32-x86-multi-thread)
- If so, download both the tarball and the ppd directly from
+ If so, download both the tarball and the ppd directly from
OpenInteract, then run ppm from within the same directory to which
- you downloaded those files and install the package by referencing
+ you downloaded those files and install the package by referencing
the ppd file explicitly via in the install command, f.e.:
- Example 4-2. Installing OpenInteract ppd Modules manually on
+ Example 4-2. Installing OpenInteract ppd Modules manually on
Microsoft Windows
install C:\AppConfig.ppd
4. Install MySQL for NT.
Note
- You can download MySQL for Windows NT from MySQL.com . Some find it
- helpful to use the WinMySqlAdmin utility, included with the download,
+ You can download MySQL for Windows NT from MySQL.com . Some find it
+ helpful to use the WinMySqlAdmin utility, included with the download,
to set up the database.
5. Setup MySQL
a. C:> C:\mysql\bin\mysql -u root mysql
b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
- c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
+ c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
WHERE user='root';
- "new_password" , above, indicates whatever password you wish
+ "new_password" , above, indicates whatever password you wish
to use for your "root" user.
- d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
- CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
+ d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
+ CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
IDENTIFIED BY 'bugs_password';
"bugs_password" , above, indicates whatever password you wish
to use for your "bugs" user.
@@ -1729,35 +1393,35 @@ my $webservergid =
'Administrators'
7. Run checksetup.pl from the Bugzilla directory.
- 8. Edit localconfig to suit your requirements. Set $db_pass to your
+ 8. Edit localconfig to suit your requirements. Set $db_pass to your
"bugs_password" from step 5.d , and $webservergroup to "8" .
Note
- Not sure on the "8" for $webservergroup above. If it's wrong, please
+ Not sure on the "8" for $webservergroup above. If it's wrong, please
send corrections.
- 9. Edit defparams.pl to suit your requirements. Particularly, set
- DefParam("maintainer") and DefParam("urlbase") to match your
+ 9. Edit defparams.pl to suit your requirements. Particularly, set
+ DefParam("maintainer") and DefParam("urlbase") to match your
install.
Note
This is yet another step I'm not sure of, since the maintainer of this
- documentation does not maintain Bugzilla on NT. If you can confirm or
+ documentation does not maintain Bugzilla on NT. If you can confirm or
deny that this step is required, please let me know.
10.
Note
- There are several alternatives to Sendmail that will work on Win32.
+ There are several alternatives to Sendmail that will work on Win32.
The one mentioned here is a suggestion , not a requirement. Some other
mail packages that can work include BLAT , Windmail , Mercury Sendmail
, and the CPAN Net::SMTP Perl module (available in .ppm). Every option
- requires some hacking of the Perl scripts for Bugzilla to make it
+ requires some hacking of the Perl scripts for Bugzilla to make it
work. The option here simply requires the least.
- 1. Download NTsendmail, available from www.ntsendmail.com . You
- must have a "real" mail server which allows you to relay off
- it in your $ENV{"NTsendmail"} (which you should probably
+ 1. Download NTsendmail, available from www.ntsendmail.com . You
+ must have a "real" mail server which allows you to relay off
+ it in your $ENV{"NTsendmail"} (which you should probably
place in globals.pl)
2. Put ntsendmail.pm into your .\perl\lib directory.
3. Add to globals.pl:
@@ -1770,12 +1434,12 @@ my $webservergid =
Note
- Some mention to also edit $db_pass in globals.pl to be your
- "bugs_password" . Although this may get you around some problem
- authenticating to your database, since globals.pl is not normally
+ Some mention to also edit $db_pass in globals.pl to be your
+ "bugs_password" . Although this may get you around some problem
+ authenticating to your database, since globals.pl is not normally
restricted by .htaccess , your database password is exposed to whoever
uses your web server.
- 4. Find and comment out all occurences of " open(SENDMAIL " in
+ 4. Find and comment out all occurences of " open(SENDMAIL " in
your Bugzilla directory. Then replace them with:
# new sendmail functionality my $mail=new
@@ -1785,26 +1449,26 @@ my $webservergid =
Note
- Some have found success using the commercial product, Windmail . You
+ Some have found success using the commercial product, Windmail . You
could try replacing your sendmail calls with:
open SENDMAIL,
"|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
mail.log";
or something to that effect.
- 11. Change all references in all files from processmail to
+ 11. Change all references in all files from processmail to
processmail.pl , and rename processmail to processmail.pl .
Note
- Many think this may be a change we want to make for main-tree
- Bugzilla. It's painless for the UNIX folks, and will make the Win32
+ Many think this may be a change we want to make for main-tree
+ Bugzilla. It's painless for the UNIX folks, and will make the Win32
people happier.
Note
- Some people have suggested using the Net::SMTP Perl module instead of
- NTsendmail or the other options listed here. You can change
+ Some people have suggested using the Net::SMTP Perl module instead of
+ NTsendmail or the other options listed here. You can change
processmail.pl to make this work.
my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
@@ -1845,20 +1509,20 @@ exit;
Note
This step is optional if you are using IIS or another web server which
- only decides on an interpreter based upon the file extension (.pl),
+ only decides on an interpreter based upon the file extension (.pl),
rather than the "shebang" line (#/usr/bonsaitools/bin/perl)
- Modify the path to perl on the first line (#!) of all files to
- point to your Perl installation, and add "perl" to the beginning
- of all Perl system calls that use a perl script as an argument.
- This may take you a while. There is a "setperl.csh" utility to
- speed part of this procedure, available in the Useful Patches and
- Utilities for Bugzilla section of The Bugzilla Guide. However, it
+ Modify the path to perl on the first line (#!) of all files to
+ point to your Perl installation, and add "perl" to the beginning
+ of all Perl system calls that use a perl script as an argument.
+ This may take you a while. There is a "setperl.csh" utility to
+ speed part of this procedure, available in the Useful Patches and
+ Utilities for Bugzilla section of The Bugzilla Guide. However, it
requires the Cygwin GNU-compatible environment for Win32 be set up
- in order to work. See http://www.cygwin.com/ for details on
+ in order to work. See http://www.cygwin.com/ for details on
obtaining Cygwin.
13. Modify the invocation of all system() calls in all perl scripts in
- your Bugzilla directory. You should specify the full path to perl
- for each system() call. For instance, change this line in
+ your Bugzilla directory. You should specify the full path to perl
+ for each system() call. For instance, change this line in
processmail:
@@ -1870,9 +1534,9 @@ system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
14. Add binmode() calls so attachments will work ( bug 62000 ).
- Because Microsoft Windows based systems handle binary files
- different than Unix based systems, you need to add the following
- lines to createattachment.cgi and showattachment.cgi before the
+ Because Microsoft Windows based systems handle binary files
+ different than Unix based systems, you need to add the following
+ lines to createattachment.cgi and showattachment.cgi before the
require 'CGI.pl'; line.
binmode(STDIN);
@@ -1882,17 +1546,17 @@ binmode(STDOUT);
Note
- According to bug 62000 , the perl documentation says that you should
- always use binmode() when dealing with binary files, but never when
- dealing with text files. That seems to suggest that rather than
- arbitrarily putting binmode() at the beginning of the attachment
- files, there should be logic to determine if binmode() is needed or
+ According to bug 62000 , the perl documentation says that you should
+ always use binmode() when dealing with binary files, but never when
+ dealing with text files. That seems to suggest that rather than
+ arbitrarily putting binmode() at the beginning of the attachment
+ files, there should be logic to determine if binmode() is needed or
not.
Tip
- If you are using IIS or Personal Web Server, you must add cgi
- relationships to Properties -> Home directory (tab) -> Application
+ If you are using IIS or Personal Web Server, you must add cgi
+ relationships to Properties -> Home directory (tab) -> Application
Settings (section) -> Configuration (button), such as:
.cgi to: <perl install directory>\perl.exe %s
@@ -1927,12 +1591,12 @@ rs\ScriptMap
Tip
- If attempting to run Bugzilla 2.12 or older, you will need to remove
- encrypt() calls from the Perl source. This is not necessary for
- Bugzilla 2.13 and later, which includes the current release, Bugzilla
- &bz-ver;.
+ If attempting to run Bugzilla 2.12 or older, you will need to remove
+ encrypt() calls from the Perl source. This is not necessary for
+ Bugzilla 2.13 and later, which includes the current release, Bugzilla
+ 2.16.3.
- Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12
+ Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12
or earlier
Replace this:
@@ -1948,74 +1612,74 @@ SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
4.4. Mac OS X Installation Notes
-There are a lot of common libraries and utilities out there that Apple did
-not include with Mac OS X, but which run perfectly well on it. The GD
-library, which Bugzilla needs to do bug graphs, is one of these.
-
-The easiest way to get a lot of these is with a program called Fink, which
-is similar in nature to the CPAN installer, but installs common GNU
-utilities. Fink is available from <http://sourceforge.net/projects/fink/>.
-
-Follow the instructions for setting up Fink. Once it's installed, you'll
-want to run the following as root: fink install gd
-
-It will prompt you for a number of dependencies, type 'y' and hit enter to
-install all of the dependencies. Then watch it work.
-
-To prevent creating conflicts with the software that Apple installs by
-default, Fink creates its own directory tree at /sw where it installs most
-of the software that it installs. This means your libraries and headers for
-libgd will be at /sw/lib and /sw/include instead of /usr/lib and
-/usr/local/include. Because of these changed locations for the libraries,
-the Perl GD module will not install directly via CPAN, because it looks for
-the specific paths instead of getting them from your environment. But
-there's a way around that :-)
-
-Instead of typing "install GD" at the cpan> prompt, type look GD. This
-should go through the motions of downloading the latest version of the GD
-module, then it will open a shell and drop you into the build directory.
-Apply this patch to the Makefile.PL file (save the patch into a file and use
-the command patch < patchfile.)
-
-Then, run these commands to finish the installation of the GD module:
-
-perl Makefile.PL
-make
-make test
-make install
-And don't forget to run exit to get back to CPAN.
+ There are a lot of common libraries and utilities out there that Apple
+ did not include with Mac OS X, but which run perfectly well on it. The
+ GD library, which Bugzilla needs to do bug graphs, is one of these.
+
+ The easiest way to get a lot of these is with a program called Fink,
+ which is similar in nature to the CPAN installer, but installs common
+ GNU utilities. Fink is available from
+ <http://sourceforge.net/projects/fink/>.
+
+ Follow the instructions for setting up Fink. Once it's installed,
+ you'll want to run the following as root: fink install gd
+
+ It will prompt you for a number of dependencies, type 'y' and hit
+ enter to install all of the dependencies. Then watch it work.
+
+ To prevent creating conflicts with the software that Apple installs by
+ default, Fink creates its own directory tree at /sw where it installs
+ most of the software that it installs. This means your libraries and
+ headers for libgd will be at /sw/lib and /sw/include instead of
+ /usr/lib and /usr/local/include. Because of these changed locations
+ for the libraries, the Perl GD module will not install directly via
+ CPAN, because it looks for the specific paths instead of getting them
+ from your environment. But there's a way around that :-)
+
+ Instead of typing "install GD" at the cpan> prompt, type look GD. This
+ should go through the motions of downloading the latest version of the
+ GD module, then it will open a shell and drop you into the build
+ directory. Apply this patch to the Makefile.PL file (save the patch
+ into a file and use the command patch < patchfile.)
+
+ Then, run these commands to finish the installation of the GD module:
+
+ perl Makefile.PL
+ make
+ make test
+ make install
+ And don't forget to run exit to get back to CPAN.
_________________________________________________________________
4.5. Troubleshooting
-This section gives solutions to common Bugzilla installation problems.
+ This section gives solutions to common Bugzilla installation problems.
_________________________________________________________________
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
-Try executing perl -MCPAN -e 'install CPAN' and then continuing.
+ Try executing perl -MCPAN -e 'install CPAN' and then continuing.
-Certain older versions of the CPAN toolset were somewhat naive about how to
-upgrade Perl modules. When a couple of modules got rolled into the core Perl
-distribution for 5.6.1, CPAN thought that the best way to get those modules
-up to date was to haul down the Perl distribution itself and build it.
-Needless to say, this has caused headaches for just about everybody.
-Upgrading to a newer version of CPAN with the commandline above should fix
-things.
+ Certain older versions of the CPAN toolset were somewhat naive about
+ how to upgrade Perl modules. When a couple of modules got rolled into
+ the core Perl distribution for 5.6.1, CPAN thought that the best way
+ to get those modules up to date was to haul down the Perl distribution
+ itself and build it. Needless to say, this has caused headaches for
+ just about everybody. Upgrading to a newer version of CPAN with the
+ commandline above should fix things.
_________________________________________________________________
4.5.2. DBD::Sponge::db prepare failed
-The following error message may appear due to a bug in DBD::mysql (over
-which the Bugzilla team have no control):
-
+ The following error message may appear due to a bug in DBD::mysql
+ (over which the Bugzilla team have no control):
DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site
/lib/DBD/mysql.pm line 248.
SV = NULL(0x0) at 0x20fc444
REFCNT = 1
FLAGS = (PADBUSY,PADMY)
- To fix this, go to <path-to-perl>/lib/DBD/sponge.pm in your Perl
+ To fix this, go to <path-to-perl>/lib/DBD/sponge.pm in your Perl
installation and replace
my $numFields;
if ($attribs->{'NUM_OF_FIELDS'}) {
@@ -2035,26 +1699,65 @@ which the Bugzilla team have no control):
4.5.3. cannot chdir(/var/spool/mqueue)
-If you are installing Bugzilla on SuSE Linux, or some other distributions
-with "paranoid" security options, it is possible that the checksetup.pl
-script may fail with the error:
+ If you are installing Bugzilla on SuSE Linux, or some other
+ distributions with "paranoid" security options, it is possible that
+ the checksetup.pl script may fail with the error:
+ cannot chdir(/var/spool/mqueue): Permission denied
-cannot chdir(/var/spool/mqueue): Permission denied
-
- This is because your /var/spool/mqueue directory has a mode of
- "drwx------". Type chmod 755 /var/spool/mqueue as root to fix this
+ This is because your /var/spool/mqueue directory has a mode of
+ "drwx------". Type chmod 755 /var/spool/mqueue as root to fix this
problem.
_________________________________________________________________
+4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
+
+ This is caused by a bug in the version of File::Temp that is
+ distributed with perl 5.6.0. Many minor variations of this error have
+ been reported. Examples can be found in Figure 4-1.
+
+ Figure 4-1. Other File::Temp error messages
+Your vendor has not defined Fcntl macro O_NOINHERIT, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
+
+Your vendor has not defined Fcntl macro O_EXLOCK, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
+
+Your vendor has not defined Fcntl macro O_TEMPORARY, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
+
+ Numerous people have reported that upgrading to version 5.6.1 or
+ higher solved the problem for them. A less involved fix is to apply
+ the patch in Figure 4-2. The patch is also available as a patch file.
+
+ Figure 4-2. Patch for File::Temp in Perl 5.6.0
+--- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
++++ File/Temp.pm Thu Feb 6 16:26:23 2003
+@@ -205,6 +205,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+@@ -226,6 +227,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+ _________________________________________________________________
+
Chapter 5. Administering Bugzilla
5.1. Bugzilla Configuration
-Bugzilla is configured by changing various parameters, accessed from the
-"Edit parameters" link in the page footer. Here are some of the key
-parameters on that page. You should run down this list and set them
-appropriately after installing Bugzilla.
-
+ Bugzilla is configured by changing various parameters, accessed from
+ the "Edit parameters" link in the page footer. Here are some of the
+ key parameters on that page. You should run down this list and set
+ them appropriately after installing Bugzilla.
1. maintainer: The maintainer parameter is the email address of the
person responsible for maintaining this Bugzilla installation. The
address need not be that of a valid Bugzilla account.
@@ -2158,11 +1861,11 @@ appropriately after installing Bugzilla.
5.2.1. Creating the Default User
-When you first run checksetup.pl after installing Bugzilla, it will prompt
-you for the administrative username (email address) and password for this
-"super user". If for some reason you delete the "super user" account,
-re-running checksetup.pl will again prompt you for this username and
-password.
+ When you first run checksetup.pl after installing Bugzilla, it will
+ prompt you for the administrative username (email address) and
+ password for this "super user". If for some reason you delete the
+ "super user" account, re-running checksetup.pl will again prompt you
+ for this username and password.
Tip
@@ -2181,10 +1884,10 @@ password.
5.2.2.1. Creating new users
-Your users can create their own user accounts by clicking the "New Account"
-link at the bottom of each page (assuming they aren't logged in as someone
-else already.) However, should you desire to create user accounts ahead of
-time, here is how you do it.
+ Your users can create their own user accounts by clicking the "New
+ Account" link at the bottom of each page (assuming they aren't logged
+ in as someone else already.) However, should you desire to create user
+ accounts ahead of time, here is how you do it.
1. After logging in, click the "Users" link at the footer of the
query page, and then click "Add a new user".
@@ -2204,16 +1907,18 @@ time, here is how you do it.
5.2.2.2. Modifying Users
-To see a specific user, search for their login name in the box provided on
-the "Edit Users" page. To see all users, leave the box blank.
+ To see a specific user, search for their login name in the box
+ provided on the "Edit Users" page. To see all users, leave the box
+ blank.
-You can search in different ways the listbox to the right of the text entry
-box. You can match by case-insensitive substring (the default), regular
-expression, or a reverse regular expression match, which finds every user
-name which does NOT match the regular expression. (Please see the man regexp
-manual page for details on regular expression syntax.)
+ You can search in different ways the listbox to the right of the text
+ entry box. You can match by case-insensitive substring (the default),
+ regular expression, or a reverse regular expression match, which finds
+ every user name which does NOT match the regular expression. (Please
+ see the man regexp manual page for details on regular expression
+ syntax.)
-Once you have found your user, you can change the following fields:
+ Once you have found your user, you can change the following fields:
* Login Name: This is generally the user's full email address.
However, if you have are using the emailsuffix Param, this may
@@ -2278,18 +1983,18 @@ Once you have found your user, you can change the following fields:
5.3.1. Products
-Products are the broadest category in Bugzilla, and tend to represent
-real-world shipping products. E.g. if your company makes computer games, you
-should have one product per game, perhaps a "Common" product for units of
-technology used in multiple games, and maybe a few special products
-(Website, Administration...)
+ Products are the broadest category in Bugzilla, and tend to represent
+ real-world shipping products. E.g. if your company makes computer
+ games, you should have one product per game, perhaps a "Common"
+ product for units of technology used in multiple games, and maybe a
+ few special products (Website, Administration...)
-Many of Bugzilla's settings are configurable on a per-product basis. The
-number of "votes" available to users is set per-product, as is the number of
-votes required to move a bug automatically from the UNCONFIRMED status to
-the NEW status.
+ Many of Bugzilla's settings are configurable on a per-product basis.
+ The number of "votes" available to users is set per-product, as is the
+ number of votes required to move a bug automatically from the
+ UNCONFIRMED status to the NEW status.
-To create a new product:
+ To create a new product:
1. Select "products" from the footer
2. Select the "Add" link in the bottom right
@@ -2305,22 +2010,23 @@ To create a new product:
5.3.2. Components
-Components are subsections of a Product. E.g. the computer game you are
-designing may have a "UI" component, an "API" component, a "Sound System"
-component, and a "Plugins" component, each overseen by a different
-programmer. It often makes sense to divide Components in Bugzilla according
-to the natural divisions of responsibility within your Product or company.
+ Components are subsections of a Product. E.g. the computer game you
+ are designing may have a "UI" component, an "API" component, a "Sound
+ System" component, and a "Plugins" component, each overseen by a
+ different programmer. It often makes sense to divide Components in
+ Bugzilla according to the natural divisions of responsibility within
+ your Product or company.
-Each component has a owner and (if you turned it on in the parameters), a QA
-Contact. The owner should be the primary person who fixes bugs in that
-component. The QA Contact should be the person who will ensure these bugs
-are completely fixed. The Owner, QA Contact, and Reporter will get email
-when new bugs are created in this Component and when these bugs change.
-Default Owner and Default QA Contact fields only dictate the default
-assignments; these can be changed on bug submission, or at any later point
-in a bug's life.
+ Each component has a owner and (if you turned it on in the
+ parameters), a QA Contact. The owner should be the primary person who
+ fixes bugs in that component. The QA Contact should be the person who
+ will ensure these bugs are completely fixed. The Owner, QA Contact,
+ and Reporter will get email when new bugs are created in this
+ Component and when these bugs change. Default Owner and Default QA
+ Contact fields only dictate the default assignments; these can be
+ changed on bug submission, or at any later point in a bug's life.
-To create a new Component:
+ To create a new Component:
1. Select the "Edit components" link from the "Edit product" page
2. Select the "Add" link in the bottom right.
@@ -2333,11 +2039,12 @@ To create a new Component:
5.3.3. Versions
-Versions are the revisions of the product, such as "Flinders 3.1", "Flinders
-95", and "Flinders 2000". Version is not a multi-select field; the usual
-practice is to select the most recent version with the bug.
+ Versions are the revisions of the product, such as "Flinders 3.1",
+ "Flinders 95", and "Flinders 2000". Version is not a multi-select
+ field; the usual practice is to select the most recent version with
+ the bug.
-To create and edit Versions:
+ To create and edit Versions:
1. From the "Edit product" screen, select "Edit Versions"
2. You will notice that the product already has the default version
@@ -2348,47 +2055,48 @@ To create and edit Versions:
5.3.4. Milestones
-Milestones are "targets" that you plan to get a bug fixed by. For example,
-you have a bug that you plan to fix for your 3.0 release, it would be
-assigned the milestone of 3.0.
+ Milestones are "targets" that you plan to get a bug fixed by. For
+ example, you have a bug that you plan to fix for your 3.0 release, it
+ would be assigned the milestone of 3.0.
Note
Milestone options will only appear for a Product if you turned on the
"usetargetmilestone" Param in the "Edit Parameters" screen.
- To create new Milestones, set Default Milestones, and set Milestone
+ To create new Milestones, set Default Milestones, and set Milestone
URL:
1. Select "Edit milestones" from the "Edit product" page.
2. Select "Add" in the bottom right corner. text
- 3. Enter the name of the Milestone in the "Milestone" field. You can
- optionally set the "sortkey", which is a positive or negative
- number (-255 to 255) that defines where in the list this
- particular milestone appears. This is because milestones often do
- not occur in alphanumeric order For example, "Future" might be
+ 3. Enter the name of the Milestone in the "Milestone" field. You can
+ optionally set the "sortkey", which is a positive or negative
+ number (-255 to 255) that defines where in the list this
+ particular milestone appears. This is because milestones often do
+ not occur in alphanumeric order For example, "Future" might be
after "Release 1.2". Select "Add".
- 4. From the Edit product screen, you can enter the URL of a page
+ 4. From the Edit product screen, you can enter the URL of a page
which gives information about your milestones and what they mean.
Tip
- If you want your milestone document to be restricted so that it can
- only be viewed by people in a particular Bugzilla group, the best way
+ If you want your milestone document to be restricted so that it can
+ only be viewed by people in a particular Bugzilla group, the best way
is to attach the document to a bug in that group, and make the URL the
URL of that attachment.
_________________________________________________________________
5.4. Voting
-Voting allows users to be given a pot of votes which they can allocate to
-bugs, to indicate that they'd like them fixed. This allows developers to
-gauge user need for a particular enhancement or bugfix. By allowing bugs
-with a certain number of votes to automatically move from "UNCONFIRMED" to
-"NEW", users of the bug system can help high-priority bugs garner attention
-so they don't sit for a long time awaiting triage.
+ Voting allows users to be given a pot of votes which they can allocate
+ to bugs, to indicate that they'd like them fixed. This allows
+ developers to gauge user need for a particular enhancement or bugfix.
+ By allowing bugs with a certain number of votes to automatically move
+ from "UNCONFIRMED" to "NEW", users of the bug system can help
+ high-priority bugs garner attention so they don't sit for a long time
+ awaiting triage.
-To modify Voting settings:
+ To modify Voting settings:
1. Navigate to the "Edit product" screen for the Product you wish to
modify
@@ -2407,21 +2115,22 @@ To modify Voting settings:
5.5. Groups and Group Security
-Groups allow the administrator to isolate bugs or products that should only
-be seen by certain people. There are two types of group - Generic Groups,
-and Product-Based Groups.
+ Groups allow the administrator to isolate bugs or products that should
+ only be seen by certain people. There are two types of group - Generic
+ Groups, and Product-Based Groups.
-Product-Based Groups are matched with products, and allow you to restrict
-access to bugs on a per-product basis. They are enabled using the
-usebuggroups Param. Turning on the usebuggroupsentry Param will mean bugs
-automatically get added to their product group when filed.
+ Product-Based Groups are matched with products, and allow you to
+ restrict access to bugs on a per-product basis. They are enabled using
+ the usebuggroups Param. Turning on the usebuggroupsentry Param will
+ mean bugs automatically get added to their product group when filed.
-Generic Groups have no special relationship to products; you create them,
-and put bugs in them as required. One example of the use of Generic Groups
-is Mozilla's "Security" group, into which security-sensitive bugs are placed
-until fixed. Only the Mozilla Security Team are members of this group.
+ Generic Groups have no special relationship to products; you create
+ them, and put bugs in them as required. One example of the use of
+ Generic Groups is Mozilla's "Security" group, into which
+ security-sensitive bugs are placed until fixed. Only the Mozilla
+ Security Team are members of this group.
-To create Generic Groups:
+ To create Generic Groups:
1. Select the "groups" link in the footer.
2. Take a moment to understand the instructions on the "Edit Groups"
@@ -2433,32 +2142,32 @@ To create Generic Groups:
To use Product-Based Groups:
- 1. Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
+ 1. Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
Parameters" screen.
Warning
- XXX is this still true? "usebuggroupsentry" has the capacity to
+ XXX is this still true? "usebuggroupsentry" has the capacity to
prevent the administrative user from directly altering bugs because of
- conflicting group permissions. If you plan on using
- "usebuggroupsentry", you should plan on restricting administrative
- account usage to administrative duties only. In other words, manage
- bugs with an unpriveleged user account, and manage users, groups,
+ conflicting group permissions. If you plan on using
+ "usebuggroupsentry", you should plan on restricting administrative
+ account usage to administrative duties only. In other words, manage
+ bugs with an unpriveleged user account, and manage users, groups,
Products, etc. with the administrative account.
- 2. In future, when you create a Product, a matching group will be
- automatically created. If you need to add a Product Group to a
- Product which was created before you turned on usebuggroups, then
- simply create a new group, as outlined above, with the same name
+ 2. In future, when you create a Product, a matching group will be
+ automatically created. If you need to add a Product Group to a
+ Product which was created before you turned on usebuggroups, then
+ simply create a new group, as outlined above, with the same name
as the Product.
Warning
- Bugzilla currently has a limit of 64 groups per installation. If you
+ Bugzilla currently has a limit of 64 groups per installation. If you
have more than about 50 products, you should consider running multiple
- Bugzillas. Ask in the newsgroup for other suggestions for working
+ Bugzillas. Ask in the newsgroup for other suggestions for working
around this restriction.
- Note that group permissions are such that you need to be a member of
+ Note that group permissions are such that you need to be a member of
all the groups a bug is in, for whatever reason, to see that bug.
_________________________________________________________________
@@ -2474,136 +2183,186 @@ To create Generic Groups:
Note
- These instructions must, of necessity, be somewhat vague since
- Bugzilla runs on so many different platforms. If you have refinements
- of these directions for specific platforms, please submit them to
- mozilla-webtools@mozilla.org
-
- To secure your installation:
-
- 1. Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and (from a security
- point of view) poor default configuration choices.
- 2. There is no substitute for understanding the tools on your system!
- Read The MySQL Privilege System until you can recite it from
- memory!
- 3. Lock down /etc/inetd.conf. Heck, disable inet entirely on this
- box. It should only listen to port 25 for Sendmail and port 80 for
- Apache.
- 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.
+ These instructions must, of necessity, be somewhat vague since
+ Bugzilla runs on so many different platforms. If you have refinements
+ of these directions, please submit a bug to Bugzilla.
+
+ Warning
+
+ This is not meant to be a comprehensive list of every possible
+ security issue regarding the tools mentioned in this section. There is
+ no subsitute for reading the information written by the authors of any
+ software running on your system.
+ _________________________________________________________________
+
+5.6.1. TCP/IP Ports
+
+ TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only
+ needs 1... 2 if you need to use features that require e-mail such as
+ bug moving or the e-mail interface from contrib. You should audit your
+ server and make sure that you aren't listening on any ports you don't
+ need to be. You may also wish to use some kind of firewall software to
+ be sure that trafic can only be recieved on ports you specify.
+ _________________________________________________________________
+
+5.6.2. MySQL
+
+ MySQL ships by default with many settings that should be changed. By
+ defaults it allows anybody to connect from localhost without a
+ password and have full administrative capabilities. It also defaults
+ to not have a root password (this is not the same as the system root).
+ Also, many installations default to running mysqld as the system root.
+
+ 1. Make sure you are running at least version 3.22.32 of MySQL as
+ earlier versions had notable security holes.
+ 2. Consult the documentation that came with your system for
+ information on making mysqld run as an unprivleged user.
+ 3. You should also be sure to disable the anonymous user account and
+ set a password for the root user. This is accomplished using the
+ following commands:
+
+bash$ mysql mysql
+mysql> DELETE FROM user WHERE user = '';
+mysql> UPDATE user SET password = password('new_password') WHERE user = 'root';
+mysql> FLUSH PRIVILEGES;
- Note
- "nobody" is a real user on UNIX systems. Having a process run as user
- id "nobody" is absolutely no protection against system crackers versus
- using any other user account. As a general security measure, I
- recommend you create unique user ID's for each daemon running on your
- system and, if possible, use "chroot" to jail that process away from
- the rest of your system.
- 5. Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ directory, as well as the
- $BUGZILLA_HOME/localconfig file. The localconfig file stores your
- "bugs" database account password. In addition, some files under
- $BUGZILLA_HOME/data/ store sensitive information.
- Bugzilla provides default .htaccess files to protect the most
- common Apache installations. However, you should verify these are
- adequate according to the site-wide security policy of your web
- server, and ensure that the .htaccess files are allowed to
- "override" default permissions set in your Apache configuration
- files. Covering Apache security is beyond the scope of this Guide;
- please consult the Apache documentation for details.
- If you are using a web server that does not support the .htaccess
- control method, you are at risk! After installing, check to see if
- you can view the file "localconfig" in your web browser (e.g.:
- http://bugzilla.mozilla.org/localconfig ). If you can read the
- contents of this file, your web server has not secured your
- bugzilla directory properly and you must fix this problem before
- deploying Bugzilla. If, however, it gives you a "Forbidden" error,
- then it probably respects the .htaccess conventions and you are
- good to go.
- When you run checksetup.pl, the script will attempt to modify
- various permissions on files which Bugzilla uses. If you do not
- have a webservergroup set in the localconfig file, then Bugzilla
- will have to make certain files world readable and/or writable.
- THIS IS INSECURE! . This means that anyone who can get access to
- your system can do whatever they want to your Bugzilla
- installation.
+ From this point forward you will need to use mysql -u root -p and
+ enter new_password when prompted when using the mysql client.
+ 4. If you run MySQL on the same machine as your httpd server, you
+ should consider disabling networking from within MySQL by adding
+ the following to your /etc/my.conf:
+
+[myslqd]
+# Prevent network access to MySQL.
+skip-networking
+
+
+ 5. You may also consider running MySQL, or even all of Bugzilla in a
+ chroot jail; however, instructions for doing that are beyond the
+ scope of this document.
+ _________________________________________________________________
+
+5.6.3. Daemon Accounts
+
+ Many daemons, such as Apache's httpd and MySQL's mysqld default to
+ running as either "root" or "nobody". Running as "root" introduces
+ obvious security problems, but the problems introduced by running
+ everything as "nobody" may not be so obvious. Basically, if you're
+ running every daemon as "nobody" and one of them gets comprimised,
+ they all get comprimised. For this reason it is recommended that you
+ create a user account for each daemon.
Note
- This also means that if your webserver runs all cgi scripts as the
- same user/group, anyone on the system who can run cgi scripts will be
- able to take control of your Bugzilla installation.
- On Apache, you can use .htaccess files to protect access to these
- directories, as outlined in Bug 57161 for the localconfig file,
- and Bug 65572 for adequate protection in your data/ directory.
- Note the instructions which follow are Apache-specific. If you use
- IIS, Netscape, or other non-Apache web servers, please consult
- your system documentation for how to secure these files from being
- transmitted to curious users.
- Place the following text into a file named ".htaccess", readable
- by your web server, in your $BUGZILLA_HOME/data directory.
- <Files comments> allow from all </Files>
- deny from all
- Place the following text into a file named ".htaccess", readable
- by your web server, in your $BUGZILLA_HOME/ directory.
- <Files localconfig> deny from all </Files>
- allow from all
+ You will need to set the webservergroup to the group you created for
+ your webserver to run as in localconfig. This will allow
+ ./checksetup.pl to better adjust the file permissions on your Bugzilla
+ install so as to not require making anything world-writable.
+ _________________________________________________________________
+
+5.6.4. Web Server Access Controls
+
+ There are many files that are placed in the Bugzilla directory area
+ that should not be accessable from the web. Because of the way
+ Bugzilla is currently layed out, the list of what should and should
+ not be accessible is rather complicated. A new installation method is
+ currently in the works which should solve this by allowing files that
+ shouldn't be accessible from the web to be placed in directory outside
+ the webroot. See bug 44659 for more information.
+
+ * In the main Bugzilla directory, you should:
+ + Block: *.pl, *localconfig*, runtests.sh, processmail,
+ syncshadowdb
+ + But allow: localconfig.js, localconfig.rdf
+ * In data:
+ + Block everything
+ + But allow: duplicates.rdf
+ * In data/webdot:
+ + If you use a remote webdot server:
+ o Block everything
+ o But allow *.dot only for the remote webdot server
+ + Otherwise, if you use a local GraphViz:
+ o Block everything
+ o But allow: *.png, *.gif, *.jpg, *.map
+ + And if you don't use any dot:
+ o Block everything
+ * In Bugzilla:
+ + Block everything
+ * In template:
+ + Block everything
+
+ Tip
+
+ Bugzilla ships with the ability to generate .htaccess files
+ instructing Apache which files should and should not be accessible.
+
+ You should test to make sure that the files mentioned above are not
+ accessible from the Internet, especially your localconfig file which
+ contains your database password. To test, simply point your web
+ browser at the file; for example, to test mozilla.org's installation,
+ we'd try to access http://bugzilla.mozilla.org/localconfig. You should
+ get a 403 Forbidden error.
+
+ Caution
+
+ Not following the instructions in this section, including testing, may
+ result in sensitive information being globally accessible.
_________________________________________________________________
5.7. Template Customisation
-One of the large changes for 2.16 was the templatisation of the entire
-user-facing UI, using the Template Toolkit. Administrators can now configure
-the look and feel of Bugzilla without having to edit Perl files or face the
-nightmare of massive merge conflicts when they upgrade to a newer version in
-the future.
+ One of the large changes for 2.16 was the templatisation of the entire
+ user-facing UI, using the Template Toolkit. Administrators can now
+ configure the look and feel of Bugzilla without having to edit Perl
+ files or face the nightmare of massive merge conflicts when they
+ upgrade to a newer version in the future.
-Templatisation also makes localised versions of Bugzilla possible, for the
-first time. In the future, a Bugzilla installation may have templates
-installed for multiple localisations, and select which ones to use based on
-the user's browser language setting.
+ Templatisation also makes localised versions of Bugzilla possible, for
+ the first time. In the future, a Bugzilla installation may have
+ templates installed for multiple localisations, and select which ones
+ to use based on the user's browser language setting.
_________________________________________________________________
5.7.1. What to Edit
-There are two different ways of editing of Bugzilla's templates, and which
-you use depends mainly on how you upgrade Bugzilla. The template directory
-structure is that there's a top level directory, template, which contains a
-directory for each installed localisation. The default English templates are
-therefore in en. Underneath that, there is the default directory and
-optionally the custom directory. The default directory contains all the
-templates shipped with Bugzilla, whereas the custom directory does not exist
-at first and must be created if you want to use it.
-
-The first method of making customisations is to directly edit the templates
-in template/en/default. This is probably the best method for small changes
-if you are going to use the CVS method of upgrading, because if you then
-execute a cvs update, any template fixes will get automagically merged into
-your modified versions.
-
-If you use this method, your installation will break if CVS conflicts occur.
-
-The other method is to copy the templates into a mirrored directory
-structure under template/en/custom. The templates in this directory
-automatically override those in default. This is the technique you need to
-use if you use the overwriting method of upgrade, because otherwise your
-changes will be lost. This method is also better if you are using the CVS
-method of upgrading and are going to make major changes, because it is
-guaranteed that the contents of this directory will not be touched during an
-upgrade, and you can then decide whether to continue using your own
-templates, or make the effort to merge your changes into the new versions by
-hand.
-
-If you use this method, your installation may break if incompatible changes
-are made to the template interface. If such changes are made they will be
-documented in the release notes, provided you are using a stable release of
-Bugzilla. If you use using unstable code, you will need to deal with this
-one yourself, although if possible the changes will be mentioned before they
-occur in the deprecations section of the previous stable release's release
-notes.
+ There are two different ways of editing of Bugzilla's templates, and
+ which you use depends mainly on how you upgrade Bugzilla. The template
+ directory structure is that there's a top level directory, template,
+ which contains a directory for each installed localisation. The
+ default English templates are therefore in en. Underneath that, there
+ is the default directory and optionally the custom directory. The
+ default directory contains all the templates shipped with Bugzilla,
+ whereas the custom directory does not exist at first and must be
+ created if you want to use it.
+
+ The first method of making customisations is to directly edit the
+ templates in template/en/default. This is probably the best method for
+ small changes if you are going to use the CVS method of upgrading,
+ because if you then execute a cvs update, any template fixes will get
+ automagically merged into your modified versions.
+
+ If you use this method, your installation will break if CVS conflicts
+ occur.
+
+ The other method is to copy the templates into a mirrored directory
+ structure under template/en/custom. The templates in this directory
+ automatically override those in default. This is the technique you
+ need to use if you use the overwriting method of upgrade, because
+ otherwise your changes will be lost. This method is also better if you
+ are using the CVS method of upgrading and are going to make major
+ changes, because it is guaranteed that the contents of this directory
+ will not be touched during an upgrade, and you can then decide whether
+ to continue using your own templates, or make the effort to merge your
+ changes into the new versions by hand.
+
+ If you use this method, your installation may break if incompatible
+ changes are made to the template interface. If such changes are made
+ they will be documented in the release notes, provided you are using a
+ stable release of Bugzilla. If you use using unstable code, you will
+ need to deal with this one yourself, although if possible the changes
+ will be mentioned before they occur in the deprecations section of the
+ previous stable release's release notes.
Note
@@ -2613,33 +2372,34 @@ notes.
5.7.2. How To Edit Templates
-The syntax of the Template Toolkit language is beyond the scope of this
-guide. It's reasonably easy to pick up by looking at the current templates;
-or, you can read the manual, available on the Template Toolkit home page.
-However, you should particularly remember (for security reasons) to always
-HTML filter things which come from the database or user input, to prevent
-cross-site scripting attacks.
-
-However, one thing you should take particular care about is the need to
-properly HTML filter data that has been passed into the template. This means
-that if the data can possibly contain special HTML characters such as <, and
-the data was not intended to be HTML, they need to be converted to entity
-form, ie <. You use the 'html' filter in the Template Toolkit to do this.
-If you fail to do this, you may open up your installation to cross-site
-scripting attacks.
-
-Also note that Bugzilla adds a few filters of its own, that are not in
-standard Template Toolkit. In particular, the 'url_quote' filter can convert
-characters that are illegal or have special meaning in URLs, such as &, to
-the encoded form, ie %26. This actually encodes most characters (but not the
-common ones such as letters and numbers and so on), including the
-HTML-special characters, so there's never a need to HTML filter afterwards.
-
-Editing templates is a good way of doing a "poor man's custom fields". For
-example, if you don't use the Status Whiteboard, but want to have a
-free-form text entry box for "Build Identifier", then you can just edit the
-templates to change the field labels. It's still be called status_whiteboard
-internally, but your users don't need to know that.
+ The syntax of the Template Toolkit language is beyond the scope of
+ this guide. It's reasonably easy to pick up by looking at the current
+ templates; or, you can read the manual, available on the Template
+ Toolkit home page. However, you should particularly remember (for
+ security reasons) to always HTML filter things which come from the
+ database or user input, to prevent cross-site scripting attacks.
+
+ However, one thing you should take particular care about is the need
+ to properly HTML filter data that has been passed into the template.
+ This means that if the data can possibly contain special HTML
+ characters such as <, and the data was not intended to be HTML, they
+ need to be converted to entity form, ie <. You use the 'html'
+ filter in the Template Toolkit to do this. If you fail to do this, you
+ may open up your installation to cross-site scripting attacks.
+
+ Also note that Bugzilla adds a few filters of its own, that are not in
+ standard Template Toolkit. In particular, the 'url_quote' filter can
+ convert characters that are illegal or have special meaning in URLs,
+ such as &, to the encoded form, ie %26. This actually encodes most
+ characters (but not the common ones such as letters and numbers and so
+ on), including the HTML-special characters, so there's never a need to
+ HTML filter afterwards.
+
+ Editing templates is a good way of doing a "poor man's custom fields".
+ For example, if you don't use the Status Whiteboard, but want to have
+ a free-form text entry box for "Build Identifier", then you can just
+ edit the templates to change the field labels. It's still be called
+ status_whiteboard internally, but your users don't need to know that.
Note
@@ -2650,178 +2410,291 @@ internally, but your users don't need to know that.
5.7.3. Template Formats
-Some CGIs have the ability to use more than one template. For example,
-buglist.cgi can output bug lists as RDF or two different forms of HTML
-(complex and simple). (Try this out by appending &format=simple to a
-buglist.cgi URL on your Bugzilla installation.) This mechanism, called
-template 'formats', is extensible.
-
-To see if a CGI supports multiple output formats, grep the CGI for
-"ValidateOutputFormat". If it's not present, adding multiple format support
-isn't too hard - see how it's done in other CGIs.
+ Some CGIs have the ability to use more than one template. For example,
+ buglist.cgi can output bug lists as RDF or two different forms of HTML
+ (complex and simple). (Try this out by appending &format=simple to a
+ buglist.cgi URL on your Bugzilla installation.) This mechanism, called
+ template 'formats', is extensible.
+
+ To see if a CGI supports multiple output formats, grep the CGI for
+ "ValidateOutputFormat". If it's not present, adding multiple format
+ support isn't too hard - see how it's done in other CGIs.
+
+ To make a new format template for a CGI which supports this, open a
+ current template for that CGI and take note of the INTERFACE comment
+ (if present.) This comment defines what variables are passed into this
+ template. If there isn't one, I'm afraid you'll have to read the
+ template and the code to find out what information you get.
+
+ Write your template in whatever markup or text style is appropriate.
+
+ You now need to decide what content type you want your template served
+ as. Open up the localconfig file and find the $contenttypes variable.
+ If your content type is not there, add it. Remember the three- or
+ four-letter tag assigned to you content type. This tag will be part of
+ the template filename.
+
+ Save the template as <stubname>-<formatname>.<contenttypetag>.tmpl.
+ Try out the template by calling the CGI as
+ <cginame>.cgi?format=<formatname> .
+ _________________________________________________________________
-To make a new format template for a CGI which supports this, open a current
-template for that CGI and take note of the INTERFACE comment (if present.)
-This comment defines what variables are passed into this template. If there
-isn't one, I'm afraid you'll have to read the template and the code to find
-out what information you get.
+5.7.4. Particular Templates
-Write your template in whatever markup or text style is appropriate.
+ There are a few templates you may be particularly interested in
+ customising for your installation.
+
+ index.html.tmpl: This is the Bugzilla front page.
+
+ global/header.html.tmpl: This defines the header that goes on all
+ Bugzilla pages. The header includes the banner, which is what appears
+ to users and is probably what you want to edit instead. However the
+ header also includes the HTML HEAD section, so you could for example
+ add a stylesheet or META tag by editing the header.
+
+ global/banner.html.tmpl: This contains the "banner", the part of the
+ header that appears at the top of all Bugzilla pages. The default
+ banner is reasonably barren, so you'll probably want to customise this
+ to give your installation a distinctive look and feel. It is
+ recommended you preserve the Bugzilla version number in some form so
+ the version you are running can be determined, and users know what
+ docs to read.
+
+ global/footer.html.tmpl: This defines the footer that goes on all
+ Bugzilla pages. Editing this is another way to quickly get a
+ distinctive look and feel for your Bugzilla installation.
+
+ bug/create/user-message.html.tmpl: This is a message that appears near
+ the top of the bug reporting page. By modifying this, you can tell
+ your users how they should report bugs.
+
+ bug/create/create.html.tmpl and bug/create/comment.txt.tmpl: You may
+ wish to get bug submitters to give certain bits of structured
+ information, each in a separate input widget, for which there is not a
+ field in the database. The bug entry system has been designed in an
+ extensible fashion to enable you to define arbitrary fields and
+ widgets, and have their values appear formatted in the initial
+ Description, rather than in database fields. An example of this is the
+ mozilla.org guided bug submission form.
+
+ To make this work, create a custom template for enter_bug.cgi (the
+ default template, on which you could base it, is create.html.tmpl),
+ and either call it create.html.tmpl or use a format and call it
+ create-<formatname>.html.tmpl. Put it in the custom/bug/create
+ directory. In it, add widgets for each piece of information you'd like
+ collected - such as a build number, or set of steps to reproduce.
+
+ Then, create a template like custom/bug/create/comment.txt.tmpl, also
+ named after your format if you are using one, which references the
+ form fields you have created. When a bug report is submitted, the
+ initial comment attached to the bug report will be formatted according
+ to the layout of this template.
+
+ For example, if your enter_bug template had a field
+ <input type="text" name="buildid" size="30">
+
+ and then your comment.txt.tmpl had
+ BuildID: [% form.buildid %]
-You now need to decide what content type you want your template served as.
-Open up the localconfig file and find the $contenttypes variable. If your
-content type is not there, add it. Remember the three- or four-letter tag
-assigned to you content type. This tag will be part of the template
-filename.
+ then
+ BuildID: 20020303
-Save the template as <stubname>-<formatname>.<contenttypetag>.tmpl. Try out
-the template by calling the CGI as <cginame>.cgi?format=<formatname> .
+ would appear in the initial checkin comment.
_________________________________________________________________
-5.7.4. Particular Templates
+5.8. Upgrading to New Releases
-There are a few templates you may be particularly interested in customising
-for your installation.
+ Upgrading Bugzilla is something we all want to do from time to time,
+ be it to get new features or pick up the latest security fix. How easy
+ it is to update depends on a few factors.
-index.html.tmpl: This is the Bugzilla front page.
+ * If the new version is a revision or a new point release
+ * How many, if any, local changes have been made
-global/header.html.tmpl: This defines the header that goes on all Bugzilla
-pages. The header includes the banner, which is what appears to users and is
-probably what you want to edit instead. However the header also includes the
-HTML HEAD section, so you could for example add a stylesheet or META tag by
-editing the header.
+ There are also three different methods to upgrade your installation.
-global/banner.html.tmpl: This contains the "banner", the part of the header
-that appears at the top of all Bugzilla pages. The default banner is
-reasonably barren, so you'll probably want to customise this to give your
-installation a distinctive look and feel. It is recommended you preserve the
-Bugzilla version number in some form so the version you are running can be
-determined, and users know what docs to read.
+ 1. Using CVS (Example 5-1)
+ 2. Downloading a new tarball (Example 5-2)
+ 3. Applying the relevant patches (Example 5-3)
-global/footer.html.tmpl: This defines the footer that goes on all Bugzilla
-pages. Editing this is another way to quickly get a distinctive look and
-feel for your Bugzilla installation.
+ Which options are available to you may depend on how large a jump you
+ are making and/or your network configuration.
-bug/create/user-message.html.tmpl: This is a message that appears near the
-top of the bug reporting page. By modifying this, you can tell your users
-how they should report bugs.
+ Revisions are normally released to fix security vulnerabilities and
+ are distinguished by an increase in the third number. For example,
+ when 2.16.2 was released, it was a revision to 2.16.1.
-bug/create/create.html.tmpl and bug/create/comment.txt.tmpl: You may wish to
-get bug submitters to give certain bits of structured information, each in a
-separate input widget, for which there is not a field in the database. The
-bug entry system has been designed in an extensible fashion to enable you to
-define arbitrary fields and widgets, and have their values appear formatted
-in the initial Description, rather than in database fields. An example of
-this is the mozilla.org guided bug submission form.
+ Point releases are normally released when the Bugzilla team feels that
+ there has been a significant amount of progress made between the last
+ point release and the current time. These are often proceeded by a
+ stabilization period and release candidates, however the use of
+ development versions or release candidates is beyond the scope of this
+ document. Point releases can be distinguished by an increase in the
+ second number, or minor version. For example, 2.16.2 is a newer point
+ release than 2.14.5.
-To make this work, create a custom template for enter_bug.cgi (the default
-template, on which you could base it, is create.html.tmpl), and either call
-it create.html.tmpl or use a format and call it
-create-<formatname>.html.tmpl. Put it in the custom/bug/create directory. In
-it, add widgets for each piece of information you'd like collected - such as
-a build number, or set of steps to reproduce.
+ The examples in this section are written as if you were updating to
+ version 2.16.2. The procedures are the same regardless if you are
+ updating to a new point release or a new revision. However, the chance
+ of running into trouble increases when upgrading to a new point
+ release, escpecially if you've made local changes.
-Then, create a template like custom/bug/create/comment.txt.tmpl, also named
-after your format if you are using one, which references the form fields you
-have created. When a bug report is submitted, the initial comment attached
-to the bug report will be formatted according to the layout of this
-template.
+ These examples also assume that your Bugzilla installation is at
+ /var/www/html/bugzilla. If that is not the case, simply substitute the
+ proper paths where appropriate.
-For example, if your enter_bug template had a field
+ Example 5-1. Upgrading using CVS
-<input type="text" name="buildid" size="30">
+ Every release of Bugzilla, whether it is a revision or a point
+ release, is tagged in CVS. Also, every tarball we have distributed
+ since version 2.12 has been primed for using CVS. This does, however,
+ require that you are able to access cvs-mirror.mozilla.org on port
+ 2401.
-and then your comment.txt.tmpl had
+ Tip
- BuildID: [% form.buildid %]
+ If you can do this, updating using CVS is probably the most painless
+ method, especially if you have a lot of local changes.
+bash$ cd /var/www/html/bugzilla
+bash$ cvs login
+Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
+CVS password: anonymous
+bash$ cvs -q update -r BUGZILLA-2_16_2 -dP
+P checksetup.pl
+P collectstats.pl
+P globals.pl
+P docs/rel_notes.txt
+P template/en/default/list/quips.html.tmpl
- then
- BuildID: 20020303
+ Caution
- would appear in the initial checkin comment.
- _________________________________________________________________
+ If a line in the output from cvs update begins with a C that
+ represents a file with local changes that CVS was unable to properly
+ merge. You need to resolve these conflicts manually before Bugzilla
+ (or at least the portion using that file) will be usable.
-5.8. Upgrading to New Releases
+ Note
+
+ You also need to run ./checksetup.pl before your Bugzilla upgrade will
+ be complete.
+
+ Example 5-2. Upgrading using the tarball
+
+ If you are unable or unwilling to use CVS, another option that's
+ always available is to download the latest tarball. This is the most
+ difficult option to use, especially if you have local changes.
+bash$ cd /var/www/html
+bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz
+Output omitted
+bash$ tar xzvf bugzilla-2.16.2.tar.gz
+bugzilla-2.16.2/
+bugzilla-2.16.2/.cvsignore
+bugzilla-2.16.2/1x1.gif
+Output truncated
+bash$ cd bugzilla-2.16.2
+bash$ cp ../bugzilla/localconfig* .
+bash$ cp -r ../bugzilla/data .
+bash$ cd ..
+bash$ mv bugzilla bugzilla.old
+bash$ mv bugzilla-2.16.2 bugzilla
+bash$ cd bugzilla
+bash$ ./checksetup.pl
+Output omitted
+
+ Warning
+
+ The cp commands both end with periods which is a very important
+ detail, it tells the shell that the destination directory is the
+ current working directory. Also, the period at the beginning of the
+ ./checksetup.pl is important and can not be omitted.
+
+ Note
+
+ You will now have to reapply any changes you have made to your local
+ installation manually.
+
+ Example 5-3. Upgrading using patches
+
+ The Bugzilla team will normally make a patch file available for
+ revisions to go from the most recent revision to the new one. You
+ could also read the release notes and grab the patches attached to the
+ mentioned bug, but it is safer to use the released patch file as
+ sometimes patches get changed before they get checked in (for minor
+ spelling fixes and the like). It is also theorectically possible to
+ scour the fixed bug list and pick and choose which patches to apply
+ from a point release, but this is not recommended either as what
+ you'll end up with is a hodge podge Bugzilla that isn't really any
+ version. This would also make it more difficult to upgrade in the
+ future.
+bash$ cd /var/www/html/bugzilla
+bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz
+Output omitted
+bash$ gunzip bugzilla-2.16.1-to-2.16.2.diff.gz
+bash$ patch -p1 < bugzilla-2.16.1-to-2.16.2.diff
+patching file checksetup.pl
+patching file collectstats.pl
+patching file globals.pl
+
+ Caution
-A plain Bugzilla is fairly easy to upgrade from one version to a newer one.
-Always read the release notes to see if there are any issues that you might
-need to take note of. It is recommended that you take a backup of your
-database and your entire Bugzilla installation before attempting an upgrade.
-You can upgrade a 'clean' installation by untarring a new tarball over the
-old installation. If you are upgrading from 2.12 or later, and have cvs
-installed, you can type cvs -z3 update, and resolve conflicts if there are
-any.
-
-However, things get a bit more complicated if you've made changes to
-Bugzilla's code. In this case, you may have to re-make or reapply those
-changes. One good method is to take a diff of your customised version
-against the original, so you can survey all that you've changed. Hopefully,
-templatisation will reduce the need for this in the future.
-
-From version 2.8 onwards, Bugzilla databases can be automatically carried
-forward during an upgrade. However, because the developers of Bugzilla are
-constantly adding new tables, columns and fields, you'll probably get SQL
-errors if you just update the code and attempt to use Bugzilla. Always run
-the checksetup.pl script whenever you upgrade your installation.
-
-If you are running Bugzilla version 2.8 or lower, and wish to upgrade to the
-latest version, please consult the file, "UPGRADING-pre-2.8" in the Bugzilla
-root directory after untarring the archive.
+ If you do this, beware that this doesn't change the entires in your
+ CVS directory so it may make updates using CVS (Example 5-1) more
+ difficult in the future.
_________________________________________________________________
5.9. Integrating Bugzilla with Third-Party Tools
5.9.1. Bonsai
-Bonsai is a web-based tool for managing CVS, the Concurrent Versioning
-System . Using Bonsai, administrators can control open/closed status of
-trees, query a fast relational database back-end for change, branch, and
-comment information, and view changes made since the last time the tree was
-closed. Bonsai also integrates with Tinderbox, the Mozilla automated build
-management system.
+ Bonsai is a web-based tool for managing CVS, the Concurrent Versioning
+ System . Using Bonsai, administrators can control open/closed status
+ of trees, query a fast relational database back-end for change,
+ branch, and comment information, and view changes made since the last
+ time the tree was closed. Bonsai also integrates with Tinderbox, the
+ Mozilla automated build management system.
_________________________________________________________________
5.9.2. CVS
-CVS integration is best accomplished, at this point, using the Bugzilla
-Email Gateway.
+ CVS integration is best accomplished, at this point, using the
+ Bugzilla Email Gateway.
-Follow the instructions in this Guide for enabling Bugzilla e-mail
-integration. Ensure that your check-in script sends an email to your
-Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can have
-CVS check-in comments append to your Bugzilla bug. If you have your check-in
-script include an @resolution field, you can even change the Bugzilla bug
-state.
+ Follow the instructions in this Guide for enabling Bugzilla e-mail
+ integration. Ensure that your check-in script sends an email to your
+ Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
+ have CVS check-in comments append to your Bugzilla bug. If you want to
+ have the bug be closed automatically, you'll have to modify the
+ contrib/bugzilla_email_append.pl script.
-There is also a CVSZilla project, based upon somewhat dated Bugzilla code,
-to integrate CVS and Bugzilla through CVS' ability to email. Check it out
-at: http://homepages.kcbbs.gen.nz/~tonyg/.
+ There is also a CVSZilla project, based upon somewhat dated Bugzilla
+ code, to integrate CVS and Bugzilla through CVS' ability to email.
+ Check it out at: http://homepages.kcbbs.gen.nz/~tonyg/.
_________________________________________________________________
5.9.3. Perforce SCM
-You can find the project page for Bugzilla and Teamtrack Perforce
-integration (p4dti) 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
-seamless. Perforce replication information will appear below the comments of
-each bug. Be certain you have a matching set of patches for the Bugzilla
-version you are installing. p4dti is designed to support multiple defect
-trackers, and maintains its own documentation for it. Please consult the
-pages linked above for further information.
+ You can find the project page for Bugzilla and Teamtrack Perforce
+ integration (p4dti) 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
+ seamless. Perforce replication information will appear below the
+ comments of each bug. Be certain you have a matching set of patches
+ for the Bugzilla version you are installing. p4dti is designed to
+ support multiple defect trackers, and maintains its own documentation
+ for it. Please consult the pages linked above for further information.
_________________________________________________________________
5.9.4. Tinderbox/Tinderbox2
-We need Tinderbox integration information.
+ We need Tinderbox integration information.
_________________________________________________________________
Appendix A. The Bugzilla FAQ
-This FAQ includes questions not covered elsewhere in the Guide.
+ This FAQ includes questions not covered elsewhere in the Guide.
1. General Questions
@@ -2836,13 +2709,13 @@ This FAQ includes questions not covered elsewhere in the Guide.
databases?
A.1.7. Why doesn't Bugzilla offer this or that feature or
- compatability with this other tracking software?
+ compatibility with this other tracking software?
A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- A.1.9. Why do the scripts say "/usr/bonsaitools/bin/perl" instead
- of "/usr/bin/perl" or something else?
+ A.1.9. Why do the scripts say /usr/bonsaitools/bin/perl instead
+ of /usr/bin/perl or something else?
A.1.10. Is there an easy way to change the Bugzilla cookie name?
@@ -2960,13 +2833,10 @@ This FAQ includes questions not covered elsewhere in the Guide.
entries. What do I do?
A.5.3. I want to manually edit some entries in my database. How?
- A.5.4. I try to add myself as a user, but Bugzilla always tells
- me my password is wrong.
-
- A.5.5. I think I've set up MySQL permissions correctly, but
+ A.5.4. I think I've set up MySQL permissions correctly, but
Bugzilla still can't connect.
- A.5.6. How do I synchronize bug information among multiple
+ A.5.5. How do I synchronize bug information among multiple
different Bugzilla databases?
6. Bugzilla and Win32
@@ -2994,10 +2864,7 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.7.4. I can't upload anything into the database via the "Create
Attachment" link. What am I doing wrong?
- A.7.5. Email submissions to Bugzilla that have attachments end up
- asking me to save it as a "cgi" file.
-
- A.7.6. How do I change a keyword in Bugzilla, once some bugs are
+ A.7.5. How do I change a keyword in Bugzilla, once some bugs are
using it?
8. Bugzilla Hacking
@@ -3024,6 +2891,9 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.1.3. How do I get commercial support for Bugzilla?
+ http://bugzilla.org/consulting.html is a list of people and companies
+ who have asked us to list them as consultants for Bugzilla.
+
www.collab.net offers Bugzilla as part of their standard offering to
large projects. They do have some minimum fees that are pretty hefty,
and generally aren't interested in small projects.
@@ -3036,13 +2906,12 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.1.4. What major companies or projects are currently using Bugzilla
for bug-tracking?
- There are dozens of major comapanies with public Bugzilla sites to
+ There are dozens of major companies with public Bugzilla sites to
track bugs in their products. A few include:
Netscape/AOL
Mozilla.org
NASA
- AtHome Corporation
Red Hat Software
SuSe Corp
The Horde Project
@@ -3062,7 +2931,7 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.1.5. Who maintains Bugzilla?
- A core team, led by Dave Miller (justdave@syndicomm.com).
+ A core team, led by Dave Miller (justdave@netscape.com).
A.1.6. How does Bugzilla stack up against other bug-tracking
databases?
@@ -3081,7 +2950,7 @@ This FAQ includes questions not covered elsewhere in the Guide.
be happy to include it in the "Competitors" section.
A.1.7. Why doesn't Bugzilla offer this or that feature or
- compatability with this other tracking software?
+ compatibility with this other tracking software?
It may be that the support has not been built yet, or that you have
not yet found it. Bugzilla is making tremendous strides in usability,
@@ -3098,19 +2967,27 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
- There is DB-independence work afoot. PostgreSQL support is planned for
- 2.18, and full DB-independence can't be far further on.
+ MySQL was originally chosen because it is free, easy to install, and
+ was available for the hardware Netscape intended to run it on.
+
+ There is currently work in progress to make Bugzilla work on
+ PostgreSQL and Sybase in the default distribution. You can track the
+ progress of these initiatives in bugs 98304 and 173130 respectively.
- A.1.9. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
+ Once both of these are done, adding support for additional database
+ servers should be trivial.
- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally Terry
+ A.1.9. Why do the scripts say /usr/bonsaitools/bin/perl instead of
+ /usr/bin/perl or something else?
+
+ Mozilla.org used /usr/bonsaitools/bin/perl, because originally Terry
wanted a place to put a version of Perl and other tools that was
strictly under his control.
- We always recommend that, if possible, you keep the path as
- /usr/bonsaitools/bin/perl, and simply add symlink. This will make
- upgrading your Bugzilla much easier in the future.
+ Note
+
+ This convention was abonded during the 2.17 development cycle so it
+ will no longer be an issue when 2.18 comes out.
A.1.10. Is there an easy way to change the Bugzilla cookie name?
@@ -3136,9 +3013,15 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.2.3. Does Bugzilla allow the user to track multiple projects?
- Absolutely! You can track any number of Products (although you are
- limited to about 55 or so if you are using Product-Based Groups), that
- can each be composed of any number of Components.
+ Absolutely! You can track any number of Products that can each be
+ composed of any number of Components.
+
+ Note
+
+ There are only 55 groups available in version 2.16 of Bugzilla. If you
+ are using product groups, this will also limit the number of products
+ you can have. This limit does not exist in the current 2.17
+ development releases and will not exist in 2.18.
A.2.4. 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,
@@ -3150,9 +3033,9 @@ This FAQ includes questions not covered elsewhere in the Guide.
If yes, are there any that are NOT allowed?
Yes - any sort of attachment is allowed, although administrators can
- configure a maximum size. There are many specific MIME-types that are
- pre-defined by Bugzilla, but you may specify any arbitrary MIME-type
- you need when you upload the file.
+ configure a maximum size. Bugzilla gives the user the option of either
+ using the MIME-type supplied by the browser, choosing from a
+ pre-defined list or manually typing any arbitrary MIME-type.
A.2.6. Does Bugzilla allow us to define our own priorities and levels?
Do we have complete freedom to change the labels of fields and format
@@ -3164,20 +3047,26 @@ This FAQ includes questions not covered elsewhere in the Guide.
There is no GUI for adding fields to Bugzilla at this time. You can
follow development of this feature at
- http://bugzilla.mozilla.org/show_bug.cgi?id=91037
+ http://bugzilla.mozilla.org/show_bug.cgi?id=91037.
A.2.7. Does Bugzilla provide any reporting features, metrics, graphs,
etc? You know, the type of stuff that management likes to see. :)
- Yes. Look at http://bugzilla.mozilla.org/reports.cgi for basic
- reporting and graphing facilities.
+ Yes. Look at http://bugzilla.mozilla.org/reports.cgi for samples of
+ what Bugzilla can do in reporting and graphing.
- For more advanced reporting, I recommend hooking up a professional
- reporting package, such as Crystal Reports, and use ODBC to access the
- MySQL database. You can do a lot through the Query page of Bugzilla as
- well, but right now Advanced Reporting is much better accomplished
- through third-party utilities that can interface with the database
- directly.
+ If you can not get the reports you want from the included reporting
+ scripts, it is possible to hook up a professional reporting package
+ such as Crystal Reports using ODBC. If you choose to do this, beware
+ that giving direct access to the database does contain some security
+ implications. Even if you give read-only access to the bugs database
+ it will bypass the secure bugs features of Bugzilla.
+
+ Note
+
+ Bugzilla's current development versions can do a lot more in the way
+ of reporting. To see examples, check out
+ http://bugzilla.mozilla.org/report.cgi.
A.2.8. Is there email notification and if so, what do you see when you
get an email?
@@ -3212,34 +3101,35 @@ This FAQ includes questions not covered elsewhere in the Guide.
the results of a query and export that data to MS Excel, could I do
that?
- Mozilla allows data export through a custom DTD in XML format. It does
- not, however, export to specific formats other than the XML Mozilla
- DTD. Importing the data into Excel or any other application is left as
- an exercise for the reader.
+ Bugzilla can only output buglists as HTML in version 2.16. There are
+ other formats available (CSV and RDF) in the newer development
+ versions.
+
+ Bugzilla can export bugs using xml.cgi with either a bug number or
+ list of bug numbers.
- If you create import filters to other applications from Mozilla's XML,
- please submit your modifications for inclusion in future Bugzilla
- distributions.
+ Currently the only script included with Bugzilla that can import data
+ is importxml.pl which is intended to be used for importing the data
+ generated by xml.cgi in association with bug moving. Any other use is
+ left as an exercise for the user.
- As for data import, any application can send data to Bugzilla through
- the HTTP protocol, or through Mozilla's XML API. However, it seems
- kind of silly to put another front-end in front of Bugzilla; it makes
- more sense to create a simplified bug submission form in HTML. You can
- find an excellent example at
- http://www.mozilla.org/quality/help/bugzilla-helper.html
+ There are also scripts included in the contrib/ directory for using
+ e-mail to import information into Bugzilla, but these scripts are not
+ currently supported and included for educational purposes.
A.2.12. Has anyone converted Bugzilla to another language to be used
in other countries? Is it localizable?
- To a certain extent, yes. 2.16's templates mean that you can localise
- the user-facing UI (and several projects are doing exactly that.)
- However, error messages and the admin interface are currently not
- localisable. This should be achieved by 2.18.
+ Yes. For more information including available translated templates,
+ see http://www.bugzilla.org/download.html#localizations. The admin
+ interfaces are still not included in these translated templates and is
+ therefore still English only. Also, there may be issues with the
+ charset not being declared. See bug 126226 for more information.
A.2.13. Can a user create and save reports? Can they do this in Word
format? Excel format?
- Yes. No. No.
+ Yes. No. Not in 2.16.
A.2.14. Does Bugzilla have the ability to search by word, phrase,
compound search?
@@ -3332,13 +3222,13 @@ This FAQ includes questions not covered elsewhere in the Guide.
Bugzilla. How do I stop it entirely for this user?
The user should be able to set this in user email preferences (uncheck
- all boxes.)
+ all boxes) or you can add their email address to the data/nomail file.
A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send
email to anyone but me. How do I do it?
- Edit the "changedmail" Param. Replace "To:" with "X-Real-To:", replace
- "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
+ Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
+ replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
A.4.3. I want whineatnews.pl to whine at something more, or other
than, only new bugs. How do I do it?
@@ -3393,10 +3283,11 @@ This FAQ includes questions not covered elsewhere in the Guide.
A.5.1. I've heard Bugzilla can be used with Oracle?
- Red Hat Bugzilla works with Oracle. The current version from
- Mozilla.org does not have this capability. Unfortunately, though you
- will sacrifice a lot of the really great features available in
- Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+ Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. Red
+ Hat's newer version (based on 2.17.1 and soon to be merged into the
+ main distribution) runs on PostgreSQL. At this time we know of no
+ recent ports of Bugzilla to Oracle but do intend to support it in the
+ future (possibly the 2.20 time-frame).
A.5.2. I think my database might be corrupted, or contain invalid
entries. What do I do?
@@ -3417,30 +3308,28 @@ This FAQ includes questions not covered elsewhere in the Guide.
There is no facility in Bugzilla itself to do this. It's also
generally not a smart thing to do if you don't know exactly what
- you're doing. However, if you understand SQL you can use the
- mysqladmin utility to manually insert, delete, and modify table
- information. Personally, I use "phpMyAdmin". You have to compile a PHP
- module with MySQL support to make it work, but it's very clean and
- easy to use.
+ you're doing. However, if you understand SQL you can use the mysql
+ command line utility to manually insert, delete and modify table
+ information. There are also more intuitive GUI clients available.
+ Personal favorites of the Bugzilla team are phpMyAdmin and MySQL
+ Control Center.
- A.5.4. I try to add myself as a user, but Bugzilla always tells me my
- password is wrong.
-
- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally
- disabled the "crypt()" function. This prevented MySQL from storing
- encrypted passwords. Upgrade to the "3.23 stable" version of MySQL and
- you should be good to go.
-
- A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla
+ A.5.4. I think I've set up MySQL permissions correctly, but Bugzilla
still can't connect.
Try running MySQL from its binary: "mysqld --skip-grant-tables". This
will allow you to completely rule out grant tables as the cause of
- your frustration. However, I do not recommend you run it this way on a
- regular basis, unless you really want your web site defaced and your
- machine cracked.
+ your frustration. If this Bugzilla is able to connect at this point
+ then you need to check that you have granted proper permission to the
+ user password combo defined in localconfig.
+
+ Warning
- A.5.6. How do I synchronize bug information among multiple different
+ Running MySQL with this command line option is very insecure and
+ should only be done when not connected to the external network as a
+ troubleshooting step.
+
+ A.5.5. How do I synchronize bug information among multiple different
Bugzilla databases?
Well, you can synchronize or you can move bugs. Synchronization will
@@ -3540,14 +3429,7 @@ This FAQ includes questions not covered elsewhere in the Guide.
incompatible with file upload via POST. Download the latest Netscape,
Microsoft, or Mozilla browser to handle uploads correctly.
- A.7.5. Email submissions to Bugzilla that have attachments end up
- asking me to save it as a "cgi" file.
-
- Yup. Just rename it once you download it, or save it under a different
- filename. This will not be fixed anytime soon, because it would
- cripple some other functionality.
-
- A.7.6. How do I change a keyword in Bugzilla, once some bugs are using
+ A.7.5. How do I change a keyword in Bugzilla, once some bugs are using
it?
In the Bugzilla administrator UI, edit the keyword and it will let you
@@ -3618,67 +3500,70 @@ B.1. Database Schema Chart
B.2. MySQL Bugzilla Database Introduction
-This information comes straight from my life. I was forced to learn how
-Bugzilla organizes database because of nitpicky requests from users for tiny
-changes in wording, rather than having people re-educate themselves or
-figure out how to work our procedures around the tool. It sucks, but it can
-and will happen to you, so learn how the schema works and deal with it when
-it comes.
-
-So, here you are with your brand-new installation of Bugzilla. You've got
-MySQL set up, Apache working right, Perl DBI and DBD talking to the database
-flawlessly. Maybe you've even entered a few test bugs to make sure email's
-working; people seem to be notified of new bugs and changes, and you can
-enter and edit bugs to your heart's content. Perhaps you've gone through the
-trouble of setting up a gateway for people to submit bugs to your database
-via email, have had a few people test it, and received rave reviews from
-your beta testers.
-
-What's the next thing you do? Outline a training strategy for your
-development team, of course, and bring them up to speed on the new tool
-you've labored over for hours.
-
-Your first training session starts off very well! You have a captive
-audience which seems enraptured by the efficiency embodied in this thing
-called "Bugzilla". You are caught up describing the nifty features, how
-people can save favorite queries in the database, set them up as headers and
-footers on their pages, customize their layouts, generate reports, track
-status with greater efficiency than ever before, leap tall buildings with a
-single bound and rescue Jane from the clutches of Certain Death!
-
-But Certain Death speaks up -- a tiny voice, from the dark corners of the
-conference room. "I have a concern," the voice hisses from the darkness,
-"about the use of the word 'verified'.
-
-The room, previously filled with happy chatter, lapses into reverential
-silence as Certain Death (better known as the Vice President of Software
-Engineering) continues. "You see, for two years we've used the word
-'verified' to indicate that a developer or quality assurance engineer has
-confirmed that, in fact, a bug is valid. I don't want to lose two years of
-training to a new software product. You need to change the bug status of
-'verified' to 'approved' as soon as possible. To avoid confusion, of
-course."
-
-Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
-don't think that would be a problem," You review the changes with Certain
-Death, and continue to jabber on, "no, it's not too big a change. I mean, we
-have the source code, right? You know, 'Use the Source, Luke' and all
-that... no problem," All the while you quiver inside like a beached
-jellyfish bubbling, burbling, and boiling on a hot Jamaican sand dune...
-
-Thus begins your adventure into the heart of Bugzilla. You've been forced to
-learn about non-portable enum() fields, varchar columns, and tinyint
-definitions. The Adventure Awaits You!
+ This information comes straight from my life. I was forced to learn
+ how Bugzilla organizes database because of nitpicky requests from
+ users for tiny changes in wording, rather than having people
+ re-educate themselves or figure out how to work our procedures around
+ the tool. It sucks, but it can and will happen to you, so learn how
+ the schema works and deal with it when it comes.
+
+ So, here you are with your brand-new installation of Bugzilla. You've
+ got MySQL set up, Apache working right, Perl DBI and DBD talking to
+ the database flawlessly. Maybe you've even entered a few test bugs to
+ make sure email's working; people seem to be notified of new bugs and
+ changes, and you can enter and edit bugs to your heart's content.
+ Perhaps you've gone through the trouble of setting up a gateway for
+ people to submit bugs to your database via email, have had a few
+ people test it, and received rave reviews from your beta testers.
+
+ What's the next thing you do? Outline a training strategy for your
+ development team, of course, and bring them up to speed on the new
+ tool you've labored over for hours.
+
+ Your first training session starts off very well! You have a captive
+ audience which seems enraptured by the efficiency embodied in this
+ thing called "Bugzilla". You are caught up describing the nifty
+ features, how people can save favorite queries in the database, set
+ them up as headers and footers on their pages, customize their
+ layouts, generate reports, track status with greater efficiency than
+ ever before, leap tall buildings with a single bound and rescue Jane
+ from the clutches of Certain Death!
+
+ But Certain Death speaks up -- a tiny voice, from the dark corners of
+ the conference room. "I have a concern," the voice hisses from the
+ darkness, "about the use of the word 'verified'.
+
+ The room, previously filled with happy chatter, lapses into
+ reverential silence as Certain Death (better known as the Vice
+ President of Software Engineering) continues. "You see, for two years
+ we've used the word 'verified' to indicate that a developer or quality
+ assurance engineer has confirmed that, in fact, a bug is valid. I
+ don't want to lose two years of training to a new software product.
+ You need to change the bug status of 'verified' to 'approved' as soon
+ as possible. To avoid confusion, of course."
+
+ Oh no! Terror strikes your heart, as you find yourself mumbling "yes,
+ yes, I don't think that would be a problem," You review the changes
+ with Certain Death, and continue to jabber on, "no, it's not too big a
+ change. I mean, we have the source code, right? You know, 'Use the
+ Source, Luke' and all that... no problem," All the while you quiver
+ inside like a beached jellyfish bubbling, burbling, and boiling on a
+ hot Jamaican sand dune...
+
+ Thus begins your adventure into the heart of Bugzilla. You've been
+ forced to learn about non-portable enum() fields, varchar columns, and
+ tinyint definitions. The Adventure Awaits You!
_________________________________________________________________
B.2.1. Bugzilla Database Basics
-If you were like me, at this point you're totally clueless about the
-internals of MySQL, and if it weren't for this executive order from the Vice
-President you couldn't care less about the difference between a "bigint" and
-a "tinyint" entry in MySQL. I recommend you refer to the MySQL
-documentation, available at MySQL.com . Below are the basics you need to
-know about the Bugzilla database. Check the chart above for more details.
+ If you were like me, at this point you're totally clueless about the
+ internals of MySQL, and if it weren't for this executive order from
+ the Vice President you couldn't care less about the difference between
+ a "bigint" and a "tinyint" entry in MySQL. I recommend you refer to
+ the MySQL documentation, available at MySQL.com . Below are the basics
+ you need to know about the Bugzilla database. Check the chart above
+ for more details.
1. To connect to your database:
bash# mysql -u root
@@ -3697,17 +3582,16 @@ know about the Bugzilla database. Check the chart above for more details.
B.2.1.1. Bugzilla Database Tables
-Imagine your MySQL database as a series of spreadsheets, and you won't be
-too far off. If you use this command:
+ Imagine your MySQL database as a series of spreadsheets, and you won't
+ be too far off. If you use this command:
-mysql> show tables from bugs;
+ mysql> show tables from bugs;
-you'll be able to see the names of all the "spreadsheets" (tables) in your
-database.
-
-From the command issued above, ou should have some output that looks like
-this:
+ you'll be able to see the names of all the "spreadsheets" (tables) in
+ your database.
+ From the command issued above, ou should have some output that looks
+ like this:
+-------------------+
| Tables in bugs |
+-------------------+
@@ -3928,14 +3812,14 @@ this:
Appendix C. Useful Patches and Utilities for Bugzilla
-Are you looking for a way to put your Bugzilla into overdrive? Catch some of
-the niftiest tricks here in this section.
+ Are you looking for a way to put your Bugzilla into overdrive? Catch
+ some of the niftiest tricks here in this section.
_________________________________________________________________
C.1. Apache mod_rewrite magic
-Apache's mod_rewrite module lets you do some truly amazing things with URL
-rewriting. Here are a couple of examples of what you can do.
+ Apache's mod_rewrite module lets you do some truly amazing things with
+ URL rewriting. Here are a couple of examples of what you can do.
1. Make it so if someone types http://www.foo.com/12345 , Bugzilla
spits back http://www.foo.com/show_bug.cgi?id=12345. Try setting
@@ -3953,93 +3837,475 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
C.2. Command-line Bugzilla Queries
-There are a suite of Unix utilities for querying Bugzilla from the command
-line. They live in the contrib/cmdline directory. However, they have not yet
-been updated to work with 2.16 (post-templatisation.). There are three files
-- query.conf, buglist and bugs.
-
-query.conf contains the mapping from options to field names and comparison
-types. Quoted option names are "grepped" for, so it should be easy to edit
-this file. Comments (#) have no effect; you must make sure these lines do
-not contain any quoted "option".
-
-buglist is a shell script which submits a Bugzilla query and writes the
-resulting HTML page to stdout. It supports both short options, (such as
-"-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
-"--reporter=bar"). If the first character of an option is not "-", it is
-treated as if it were prefixed with "--default=".
-
-The column list is taken from the COLUMNLIST environment variable. This is
-equivalent to the "Change Columns" option when you list bugs in buglist.cgi.
-If you have already used Bugzilla, grep for COLUMNLIST in your cookies file
-to see your current COLUMNLIST setting.
-
-bugs is a simple shell script which calls buglist and extracts the bug
-numbers from the output. Adding the prefix
-"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into a
-working link if any bugs are found. Counting bugs is easy. Pipe the results
-through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
-
-Akkana Peck says she has good results piping buglist output through w3m -T
-text/html -dump
+ There are a suite of Unix utilities for querying Bugzilla from the
+ command line. They live in the contrib/cmdline directory. However,
+ they have not yet been updated to work with 2.16
+ (post-templatisation.). There are three files - query.conf, buglist
+ and bugs.
+
+ query.conf contains the mapping from options to field names and
+ comparison types. Quoted option names are "grepped" for, so it should
+ be easy to edit this file. Comments (#) have no effect; you must make
+ sure these lines do not contain any quoted "option".
+
+ buglist is a shell script which submits a Bugzilla query and writes
+ the resulting HTML page to stdout. It supports both short options,
+ (such as "-Afoo" or "-Rbar") and long options (such as
+ "--assignedto=foo" or "--reporter=bar"). If the first character of an
+ option is not "-", it is treated as if it were prefixed with
+ "--default=".
+
+ The column list is taken from the COLUMNLIST environment variable.
+ This is equivalent to the "Change Columns" option when you list bugs
+ in buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
+ in your cookies file to see your current COLUMNLIST setting.
+
+ bugs is a simple shell script which calls buglist and extracts the bug
+ numbers from the output. Adding the prefix
+ "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list
+ into a working link if any bugs are found. Counting bugs is easy. Pipe
+ the results through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
+
+ Akkana Peck says she has good results piping buglist output through
+ w3m -T text/html -dump
_________________________________________________________________
Appendix D. Bugzilla Variants and Competitors
-I created this section to answer questions about Bugzilla competitors and
-variants, then found a wonderful site which covers an awful lot of what I
-wanted to discuss. Rather than quote it in its entirety, I'll simply refer
-you here: http://linas.org/linux/pm.html
+ I created this section to answer questions about Bugzilla competitors
+ and variants, then found a wonderful site which covers an awful lot of
+ what I wanted to discuss. Rather than quote it in its entirety, I'll
+ simply refer you here: http://linas.org/linux/pm.html
_________________________________________________________________
D.1. Red Hat Bugzilla
-Red Hat Bugzilla is a fork of Bugzilla 2.8. One of its major benefits is the
-ability to work with Oracle, MySQL, and PostGreSQL databases serving as the
-back-end, instead of just MySQL. Dave Lawrence of Red Hat is active in the
-Bugzilla community, and we hope to see a reunification of the fork before
-too long.
+ Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+ obsolete. The newest version in use is based on version 2.17.1 and is
+ in the process of being integrated into the main Bugzilla source tree.
+ The back-end is modified to work with PostgreSQL instead of MySQL and
+ they have custom templates to get their desired look and feel, but
+ other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put
+ forth a great deal of effort to make sure that the changes he made
+ could be integrated back into the main tree. Bug 98304 exists to track
+ this integration.
+
+ URL: http://bugzilla.redhat.com/bugzilla/
-URL: http://bugzilla.redhat.com/bugzilla/
+ This section last updated 24 Dec 2002
_________________________________________________________________
D.2. Loki Bugzilla (Fenris)
-Fenris was a fork from Bugzilla made by Loki Games; when Loki went into
-receivership, it died. While Loki's other code lives on, its custodians
-recommend Bugzilla for future bug-tracker deployments.
+ Fenris was a fork from Bugzilla made by Loki Games; when Loki went
+ into receivership, it died. While Loki's other code lives on, its
+ custodians recommend Bugzilla for future bug-tracker deployments.
+
+ This section last updated 27 Jul 2002
_________________________________________________________________
D.3. Issuezilla
-Issuezilla was another fork from Bugzilla, made by collab.net and hosted at
-tigris.org. It is also dead; the primary focus of bug-tracking at tigris.org
-is their Java-based bug-tracker, Scarab.
+ Issuezilla was another fork from Bugzilla, made by collab.net and
+ hosted at tigris.org. It is also dead; the primary focus of
+ bug-tracking at tigris.org is their Java-based bug-tracker, Section
+ D.4.
+
+ This section last updated 27 Jul 2002
_________________________________________________________________
D.4. Scarab
-Scarab is a new open source bug-tracking system built using Java Serlet
-technology. It is currently at version 1.0 beta 8.
+ Scarab is a new open source bug-tracking system built using Java
+ Servlet technology. It is currently at version 1.0 beta 13.
-URL: http://scarab.tigris.org
+ URL: http://scarab.tigris.org
+
+ This section last updated 18 Jan 2003
_________________________________________________________________
D.5. Perforce SCM
-Although Perforce isn't really a bug tracker, it can be used as such through
-the "jobs" functionality.
+ Although Perforce isn't really a bug tracker, it can be used as such
+ through the "jobs" functionality.
+
+ URL: http://www.perforce.com/perforce/technotes/note052.html
-URL: http://www.perforce.com/perforce/technotes/note052.html
+ This section last updated 27 Jul 2002
_________________________________________________________________
D.6. SourceForge
-SourceForge is a way of coordinating geographically distributed free
-software and open source projects over the Internet. It has a built-in bug
-tracker, but it's not highly thought of.
+ SourceForge is a way of coordinating geographically distributed free
+ software and open source projects over the Internet. It has a built-in
+ bug tracker, but it's not highly thought of.
+
+ URL: http://www.sourceforge.net
-URL: http://www.sourceforge.net
+ This section last updated 27 Jul 2002
+ _________________________________________________________________
+
+Appendix E. GNU Free Documentation License
+
+ Version 1.1, March 2000
+
+ Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
+ Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy
+ and distribute verbatim copies of this license document, but
+ changing it is not allowed.
+ _________________________________________________________________
+
+0. PREAMBLE
+
+ The purpose of this License is to make a manual, textbook, or other
+ written document "free" in the sense of freedom: to assure everyone
+ the effective freedom to copy and redistribute it, with or without
+ modifying it, either commercially or noncommercially. Secondarily,
+ this License preserves for the author and publisher a way to get
+ credit for their work, while not being considered responsible for
+ modifications made by others.
+
+ This License is a kind of "copyleft", which means that derivative
+ works of the document must themselves be free in the same sense. It
+ complements the GNU General Public License, which is a copyleft
+ license designed for free software.
+
+ We have designed this License in order to use it for manuals for free
+ software, because free software needs free documentation: a free
+ program should come with manuals providing the same freedoms that the
+ software does. But this License is not limited to software manuals; it
+ can be used for any textual work, regardless of subject matter or
+ whether it is published as a printed book. We recommend this License
+ principally for works whose purpose is instruction or reference.
+ _________________________________________________________________
+
+1. APPLICABILITY AND DEFINITIONS
+
+ This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be distributed
+ under the terms of this License. The "Document", below, refers to any
+ such manual or work. Any member of the public is a licensee, and is
+ addressed as "you".
+
+ A "Modified Version" of the Document means any work containing the
+ Document or a portion of it, either copied verbatim, or with
+ modifications and/or translated into another language.
+
+ A "Secondary Section" is a named appendix or a front-matter section of
+ the Document that deals exclusively with the relationship of the
+ publishers or authors of the Document to the Document's overall
+ subject (or to related matters) and contains nothing that could fall
+ directly within that overall subject. (For example, if the Document is
+ in part a textbook of mathematics, a Secondary Section may not explain
+ any mathematics.) The relationship could be a matter of historical
+ connection with the subject or with related matters, or of legal,
+ commercial, philosophical, ethical or political position regarding
+ them.
+
+ The "Invariant Sections" are certain Secondary Sections whose titles
+ are designated, as being those of Invariant Sections, in the notice
+ that says that the Document is released under this License.
+
+ The "Cover Texts" are certain short passages of text that are listed,
+ as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+ the Document is released under this License.
+
+ A "Transparent" copy of the Document means a machine-readable copy,
+ represented in a format whose specification is available to the
+ general public, whose contents can be viewed and edited directly and
+ straightforwardly with generic text editors or (for images composed of
+ pixels) generic paint programs or (for drawings) some widely available
+ drawing editor, and that is suitable for input to text formatters or
+ for automatic translation to a variety of formats suitable for input
+ to text formatters. A copy made in an otherwise Transparent file
+ format whose markup has been designed to thwart or discourage
+ subsequent modification by readers is not Transparent. A copy that is
+ not "Transparent" is called "Opaque".
+
+ Examples of suitable formats for Transparent copies include plain
+ ASCII without markup, Texinfo input format, LaTeX input format, SGML
+ or XML using a publicly available DTD, and standard-conforming simple
+ HTML designed for human modification. Opaque formats include
+ PostScript, PDF, proprietary formats that can be read and edited only
+ by proprietary word processors, SGML or XML for which the DTD and/or
+ processing tools are not generally available, and the
+ machine-generated HTML produced by some word processors for output
+ purposes only.
+
+ The "Title Page" means, for a printed book, the title page itself,
+ plus such following pages as are needed to hold, legibly, the material
+ this License requires to appear in the title page. For works in
+ formats which do not have any title page as such, "Title Page" means
+ the text near the most prominent appearance of the work's title,
+ preceding the beginning of the body of the text.
+ _________________________________________________________________
+
+2. VERBATIM COPYING
+
+ You may copy and distribute the Document in any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License applies
+ to the Document are reproduced in all copies, and that you add no
+ other conditions whatsoever to those of this License. You may not use
+ technical measures to obstruct or control the reading or further
+ copying of the copies you make or distribute. However, you may accept
+ compensation in exchange for copies. If you distribute a large enough
+ number of copies you must also follow the conditions in section 3.
+
+ You may also lend copies, under the same conditions stated above, and
+ you may publicly display copies.
+ _________________________________________________________________
+
+3. COPYING IN QUANTITY
+
+ If you publish printed copies of the Document numbering more than 100,
+ and the Document's license notice requires Cover Texts, you must
+ enclose the copies in covers that carry, clearly and legibly, all
+ these Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also clearly and
+ legibly identify you as the publisher of these copies. The front cover
+ must present the full title with all words of the title equally
+ prominent and visible. You may add other material on the covers in
+ addition. Copying with changes limited to the covers, as long as they
+ preserve the title of the Document and satisfy these conditions, can
+ be treated as verbatim copying in other respects.
+
+ If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto adjacent
+ pages.
+
+ If you publish or distribute Opaque copies of the Document numbering
+ more than 100, you must either include a machine-readable Transparent
+ copy along with each Opaque copy, or state in or with each Opaque copy
+ a publicly-accessible computer-network location containing a complete
+ Transparent copy of the Document, free of added material, which the
+ general network-using public has access to download anonymously at no
+ charge using public-standard network protocols. If you use the latter
+ option, you must take reasonably prudent steps, when you begin
+ distribution of Opaque copies in quantity, to ensure that this
+ Transparent copy will remain thus accessible at the stated location
+ until at least one year after the last time you distribute an Opaque
+ copy (directly or through your agents or retailers) of that edition to
+ the public.
+
+ It is requested, but not required, that you contact the authors of the
+ Document well before redistributing any large number of copies, to
+ give them a chance to provide you with an updated version of the
+ Document.
+ _________________________________________________________________
+
+4. MODIFICATIONS
+
+ You may copy and distribute a Modified Version of the Document under
+ the conditions of sections 2 and 3 above, provided that you release
+ the Modified Version under precisely this License, with the Modified
+ Version filling the role of the Document, thus licensing distribution
+ and modification of the Modified Version to whoever possesses a copy
+ of it. In addition, you must do these things in the Modified Version:
+
+ A. Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+ B. List on the Title Page, as authors, one or more persons or
+ entities responsible for authorship of the modifications in the
+ Modified Version, together with at least five of the principal
+ authors of the Document (all of its principal authors, if it has
+ less than five).
+ C. State on the Title page the name of the publisher of the Modified
+ Version, as the publisher.
+ D. Preserve all the copyright notices of the Document.
+ E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+ F. Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+ G. Preserve in that license notice the full lists of Invariant
+ Sections and required Cover Texts given in the Document's license
+ notice.
+ H. Include an unaltered copy of this License.
+ I. Preserve the section entitled "History", and its title, and add to
+ it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+ J. Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the "History" section. You
+ may omit a network location for a work that was published at least
+ four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+ K. In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+ L. Preserve all the Invariant Sections of the Document, unaltered in
+ their text and in their titles. Section numbers or the equivalent
+ are not considered part of the section titles.
+ M. Delete any section entitled "Endorsements". Such a section may not
+ be included in the Modified Version.
+ N. Do not retitle any existing section as "Endorsements" or to
+ conflict in title with any Invariant Section.
+
+ If the Modified Version includes new front-matter sections or
+ appendices that qualify as Secondary Sections and contain no material
+ copied from the Document, you may at your option designate some or all
+ of these sections as invariant. To do this, add their titles to the
+ list of Invariant Sections in the Modified Version's license notice.
+ These titles must be distinct from any other section titles.
+
+ You may add a section entitled "Endorsements", provided it contains
+ nothing but endorsements of your Modified Version by various
+ parties--for example, statements of peer review or that the text has
+ been approved by an organization as the authoritative definition of a
+ standard.
+
+ You may add a passage of up to five words as a Front-Cover Text, and a
+ passage of up to 25 words as a Back-Cover Text, to the end of the list
+ of Cover Texts in the Modified Version. Only one passage of
+ Front-Cover Text and one of Back-Cover Text may be added by (or
+ through arrangements made by) any one entity. If the Document already
+ includes a cover text for the same cover, previously added by you or
+ by arrangement made by the same entity you are acting on behalf of,
+ you may not add another; but you may replace the old one, on explicit
+ permission from the previous publisher that added the old one.
+
+ The author(s) and publisher(s) of the Document do not by this License
+ give permission to use their names for publicity for or to assert or
+ imply endorsement of any Modified Version.
+ _________________________________________________________________
+
+5. COMBINING DOCUMENTS
+
+ You may combine the Document with other documents released under this
+ License, under the terms defined in section 4 above for modified
+ versions, provided that you include in the combination all of the
+ Invariant Sections of all of the original documents, unmodified, and
+ list them all as Invariant Sections of your combined work in its
+ license notice.
+
+ The combined work need only contain one copy of this License, and
+ multiple identical Invariant Sections may be replaced with a single
+ copy. If there are multiple Invariant Sections with the same name but
+ different contents, make the title of each such section unique by
+ adding at the end of it, in parentheses, the name of the original
+ author or publisher of that section if known, or else a unique number.
+ Make the same adjustment to the section titles in the list of
+ Invariant Sections in the license notice of the combined work.
+
+ In the combination, you must combine any sections entitled "History"
+ in the various original documents, forming one section entitled
+ "History"; likewise combine any sections entitled "Acknowledgements",
+ and any sections entitled "Dedications". You must delete all sections
+ entitled "Endorsements."
+ _________________________________________________________________
+
+6. COLLECTIONS OF DOCUMENTS
+
+ You may make a collection consisting of the Document and other
+ documents released under this License, and replace the individual
+ copies of this License in the various documents with a single copy
+ that is included in the collection, provided that you follow the rules
+ of this License for verbatim copying of each of the documents in all
+ other respects.
+
+ You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you insert a
+ copy of this License into the extracted document, and follow this
+ License in all other respects regarding verbatim copying of that
+ document.
+ _________________________________________________________________
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+ A compilation of the Document or its derivatives with other separate
+ and independent documents or works, in or on a volume of a storage or
+ distribution medium, does not as a whole count as a Modified Version
+ of the Document, provided no compilation copyright is claimed for the
+ compilation. Such a compilation is called an "aggregate", and this
+ License does not apply to the other self-contained works thus compiled
+ with the Document, on account of their being thus compiled, if they
+ are not themselves derivative works of the Document.
+
+ If the Cover Text requirement of section 3 is applicable to these
+ copies of the Document, then if the Document is less than one quarter
+ of the entire aggregate, the Document's Cover Texts may be placed on
+ covers that surround only the Document within the aggregate. Otherwise
+ they must appear on covers around the whole aggregate.
+ _________________________________________________________________
+
+8. TRANSLATION
+
+ Translation is considered a kind of modification, so you may
+ distribute translations of the Document under the terms of section 4.
+ Replacing Invariant Sections with translations requires special
+ permission from their copyright holders, but you may include
+ translations of some or all Invariant Sections in addition to the
+ original versions of these Invariant Sections. You may include a
+ translation of this License provided that you also include the
+ original English version of this License. In case of a disagreement
+ between the translation and the original English version of this
+ License, the original English version will prevail.
+ _________________________________________________________________
+
+9. TERMINATION
+
+ You may not copy, modify, sublicense, or distribute the Document
+ except as expressly provided for under this License. Any other attempt
+ to copy, modify, sublicense or distribute the Document is void, and
+ will automatically terminate your rights under this License. However,
+ parties who have received copies, or rights, from you under this
+ License will not have their licenses terminated so long as such
+ parties remain in full compliance.
+ _________________________________________________________________
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+ The Free Software Foundation may publish new, revised versions of the
+ GNU Free Documentation License from time to time. Such new versions
+ will be similar in spirit to the present version, but may differ in
+ detail to address new problems or concerns. See
+ http://www.gnu.org/copyleft/ .
+
+ Each version of the License is given a distinguishing version number.
+ If the Document specifies that a particular numbered version of this
+ License "or any later version" applies to it, you have the option of
+ following the terms and conditions either of that specified version or
+ of any later version that has been published (not as a draft) by the
+ Free Software Foundation. If the Document does not specify a version
+ number of this License, you may choose any version ever published (not
+ as a draft) by the Free Software Foundation.
+ _________________________________________________________________
+
+How to use this License for your documents
+
+ To use this License in a document you have written, include a copy of
+ the License in the document and put the following copyright and
+ license notices just after the title page:
+
+ Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
+ distribute and/or modify this document under the terms of the GNU
+ Free Documentation License, Version 1.1 or any later version
+ published by the Free Software Foundation; with the Invariant
+ Sections being LIST THEIR TITLES, with the Front-Cover Texts being
+ LIST, and with the Back-Cover Texts being LIST. A copy of the
+ license is included in the section entitled "GNU Free Documentation
+ License".
+
+ If you have no Invariant Sections, write "with no Invariant Sections"
+ instead of saying which ones are invariant. If you have no Front-Cover
+ Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts
+ being LIST"; likewise for Back-Cover Texts.
+
+ If your document contains nontrivial examples of program code, we
+ recommend releasing these examples in parallel under your choice of
+ free software license, such as the GNU General Public License, to
+ permit their use in free software.
Glossary
@@ -4063,6 +4329,27 @@ A
fact that it was "a patchy" version of the original NCSA
world-wide-web server.
+ Useful Directives when configuring Bugzilla
+
+ AddHandler
+ Tell Apache that it's OK to run CGI scripts.
+
+ AllowOverride, Options
+ These directives are used to tell Apache many things
+ about the directory they apply to. For Bugzilla's
+ purposes, we need them to allow script execution and
+ .htaccess overrides.
+
+ DirectoryIndex
+ Used to tell Apache what files are indexes. If you can
+ not add index.cgi to the list of valid files, you'll need
+ to set $index_html to 1 in localconfig so ./checksetup.pl
+ will create an index.html that redirects to index.cgi.
+
+ ScriptInterpreterSource
+ Used when running Apache on windows so the shebang line
+ doesn't have to be changed in every Bugzilla script.
+
B
Bug
@@ -4081,6 +4368,13 @@ B
Bugzilla is the world-leading free software bug tracking
system.
+C
+
+ Common Gateway Interface (CGI)
+ CGI is an acronym for Common Gateway Interface. This is a
+ standard for interfacing an external application with a web
+ server. Bugzilla is an example of a CGI application.
+
Component
A Component is a subsection of a Product. It should be a narrow
category, tailored to your organization. All Products must
@@ -4102,6 +4396,8 @@ D
mysqld, the MySQL server, and apache, a web server, are
generally run as daemons.
+G
+
Groups
The word "Groups" has a very special meaning to Bugzilla.
Bugzilla's main security mechanism comes by placing users in
@@ -4110,12 +4406,21 @@ D
M
- mysqld
- mysqld is the name of the daemon for the MySQL database. In
- general, it is invoked automatically through the use of the
- System V init scripts on GNU/Linux and AT&T System V-based
- systems, such as Solaris and HP/UX, or through the RC scripts
- on BSD-based systems.
+ Message Transport Agent (MTA)
+ A Message Transport Agent is used to control the flow of email
+ on a system. Many unix based systems use sendmail which is what
+ Bugzilla expects to find by default at /usr/sbin/sendmail. Many
+ other MTA's will work, but they all require that the
+ sendmailnow param be set to on.
+
+ MySQL
+ MySQL is currently the required RDBMS for Bugzilla. MySQL can
+ be downloaded from http://www.mysql.com. While you should
+ familiarize yourself with all of the documentation, some high
+ points are:
+
+ + MySQL Privilege System - Much more detailed information about
+ the suggestions in Section 5.6.2.
P
@@ -4143,6 +4448,13 @@ Q
progress of bugs over their life cycle, thus the need for the
"QA Contact" field in a bug.
+R
+
+ Relational DataBase Managment System (RDBMS)
+ A relational database management system is a database system
+ that stores information in tables that are related to each
+ other.
+
S
SGML
@@ -4166,9 +4478,31 @@ T
to declare by which milestone a bug will be fixed, or an
enhancement will be implemented.
+ Tool Command Language (TCL)
+ TCL is an open source scripting language available for Windows,
+ Macintosh, and Unix based systems. Bugzilla 1.0 was written in
+ TCL but never released. The first release of Bugzilla was 2.0,
+ which was when it was ported to perl.
+
Z
Zarro Boogs Found
- This is the cryptic response sent by Bugzilla when a query
- returned no results. It is just a goofy way of saying "Zero
- Bugs Found".
+ This is just a goofy way of saying that there were no bugs
+ found matching your query. When asked to explain this message,
+ Terry had the following to say:
+
+
+
+ I've been asked to explain this ... way back when, when Netscape
+ released version 4.0 of its browser, we had a release party.
+ Naturally, there had been a big push to try and fix every known bug
+ before the release. Naturally, that hadn't actually happened. (This is
+ not unique to Netscape or to 4.0; the same thing has happened with
+ every software project I've ever seen.) Anyway, at the release party,
+ T-shirts were handed out that said something like "Netscape 4.0: Zarro
+ Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh.
+ So, when you query for a list of bugs, and it gets no results, you can
+ think of this as a friendly reminder. Of *course* there are bugs
+ matching your query, they just aren't in the bugsystem yet...
+
+ --Terry Weissman
diff --git a/docs/txt/CVS/Entries b/docs/txt/CVS/Entries
index 07ab1543ee0d77782c49606a3cbfaf3322676d53..2455a9b715b610c1d3998461a23e606933387577 100644
--- a/docs/txt/CVS/Entries
+++ b/docs/txt/CVS/Entries
@@ -1,2 +1,2 @@
-/Bugzilla-Guide.txt/1.14.2.1/Thu Jul 25 21:10:06 2002//TBUGZILLA-2_16_2
+/Bugzilla-Guide.txt/1.14.2.7/Wed Apr 23 02:34:37 2003//TBUGZILLA-2_16_3
D
diff --git a/docs/txt/CVS/Tag b/docs/txt/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/docs/txt/CVS/Tag
+++ b/docs/txt/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/xml/Bugzilla-Guide.xml
similarity index 76%
rename from docs/sgml/Bugzilla-Guide.sgml
rename to docs/xml/Bugzilla-Guide.xml
index b8868a618da52612ccb324cd1b49d627954b3cee..486223086bab1d2026b972650d35f8981600683c 100644
--- a/docs/sgml/Bugzilla-Guide.sgml
+++ b/docs/xml/Bugzilla-Guide.xml
@@ -1,30 +1,30 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" [
<!-- Include macros -->
-<!ENTITY about SYSTEM "about.sgml">
-<!ENTITY conventions SYSTEM "conventions.sgml">
-<!ENTITY doc-index SYSTEM "index.sgml">
-<!ENTITY faq SYSTEM "faq.sgml">
-<!ENTITY gfdl SYSTEM "gfdl.sgml">
-<!ENTITY glossary SYSTEM "glossary.sgml">
-<!ENTITY installation SYSTEM "installation.sgml">
-<!ENTITY administration SYSTEM "administration.sgml">
-<!ENTITY using SYSTEM "using.sgml">
-<!ENTITY integration SYSTEM "integration.sgml">
-<!ENTITY future SYSTEM "future.sgml">
-<!ENTITY index SYSTEM "index.sgml">
-<!ENTITY database SYSTEM "database.sgml">
-<!ENTITY patches SYSTEM "patches.sgml">
-<!ENTITY variants SYSTEM "variants.sgml">
-<!ENTITY introduction SYSTEM "introduction.sgml">
-<!ENTITY revhistory SYSTEM "revhistory.sgml">
+<!ENTITY about SYSTEM "about.xml">
+<!ENTITY conventions SYSTEM "conventions.xml">
+<!ENTITY doc-index SYSTEM "index.xml">
+<!ENTITY faq SYSTEM "faq.xml">
+<!ENTITY gfdl SYSTEM "gfdl.xml">
+<!ENTITY glossary SYSTEM "glossary.xml">
+<!ENTITY installation SYSTEM "installation.xml">
+<!ENTITY administration SYSTEM "administration.xml">
+<!ENTITY using SYSTEM "using.xml">
+<!ENTITY integration SYSTEM "integration.xml">
+<!ENTITY future SYSTEM "future.xml">
+<!ENTITY index SYSTEM "index.xml">
+<!ENTITY database SYSTEM "database.xml">
+<!ENTITY patches SYSTEM "patches.xml">
+<!ENTITY variants SYSTEM "variants.xml">
+<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY revhistory SYSTEM "revhistory.xml">
<!ENTITY bz "http://www.bugzilla.org/">
-<!ENTITY bz-ver "2.16">
+<!ENTITY bz-ver "2.16.3">
+<!ENTITY bz-date "2003-04-23">
<!ENTITY bz-cvs-ver "2.17">
-<!ENTITY bzg-date "April 2nd, 2002">
-<!ENTITY bzg-ver "2.16">
-<!ENTITY bzg-cvs-ver "2.17.0">
+<!ENTITY bzg-ver "2.16.3">
+<!ENTITY bzg-cvs-ver "2.17.4">
<!ENTITY bzg-auth "The Bugzilla Team">
<!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation'>Bugzilla</ulink>">
<!ENTITY mysql "http://www.mysql.com/">
@@ -36,7 +36,7 @@
<!-- Coding standards for this document
* Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
-* Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
+* Use Entities to include files for new chapters in Bugzilla-Guide.xml.
* Try to use Entities for frequently-used passages of text as well.
* Ensure all documents compile cleanly to HTML after modification.
The warning, "DTDDECL catalog types not supported" is normal.
@@ -58,7 +58,7 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- Header -->
<bookinfo>
- <title>The Bugzilla Guide</title>
+ <title>The Bugzilla Guide - &bzg-ver; Release</title>
<authorgroup>
<author>
@@ -73,6 +73,8 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</author>
</authorgroup>
+ <pubdate>&bz-date;</pubdate>
+
<abstract>
<para>
This is the documentation for Bugzilla, the mozilla.org
@@ -84,7 +86,7 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
- Changes are best submitted as plain text or SGML diffs, attached
+ Changes are best submitted as plain text or XML diffs, attached
to a bug filed in
<ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation">mozilla.org's Bugzilla</ulink>.
</para>
@@ -130,6 +132,9 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- Appendix: Major Bugzilla Variants -->
&variants;
+<!-- Appendix: GNU Free Documentation License -->
+&gfdl;
+
<!-- Glossary -->
&glossary;
@@ -154,7 +159,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/xml/CVS/Entries b/docs/xml/CVS/Entries
new file mode 100644
index 0000000000000000000000000000000000000000..80e40a125361e4f8a8c411bb72658b13b4e859ba
--- /dev/null
+++ b/docs/xml/CVS/Entries
@@ -0,0 +1,19 @@
+/Bugzilla-Guide.xml/1.11.2.8/Wed Apr 23 02:28:00 2003//TBUGZILLA-2_16_3
+/about.xml/1.6.2.5/Wed Apr 23 02:24:11 2003//TBUGZILLA-2_16_3
+/administration.xml/1.13.2.8/Wed Apr 23 02:24:11 2003//TBUGZILLA-2_16_3
+/conventions.xml/1.4.2.6/Wed Apr 23 02:24:13 2003//TBUGZILLA-2_16_3
+/database.xml/1.7.2.2/Wed Apr 23 02:24:13 2003//TBUGZILLA-2_16_3
+/dbschema.mysql/1.2/Wed May 8 23:19:09 2002//TBUGZILLA-2_16_3
+/faq.xml/1.8.2.6/Wed Apr 23 02:24:14 2003//TBUGZILLA-2_16_3
+/filetemp.patch/1.1.2.1/Wed Apr 2 00:44:11 2003//TBUGZILLA-2_16_3
+/gd-makefile.patch/1.1.2.1/Sun May 12 13:16:48 2002//TBUGZILLA-2_16_3
+/gfdl.xml/1.4.2.3/Wed Apr 23 02:24:14 2003//TBUGZILLA-2_16_3
+/glossary.xml/1.5.2.5/Wed Apr 23 02:24:15 2003//TBUGZILLA-2_16_3
+/index.xml/1.3.2.1/Wed Apr 23 02:24:16 2003//TBUGZILLA-2_16_3
+/installation.xml/1.18.2.10/Wed Apr 23 02:24:16 2003//TBUGZILLA-2_16_3
+/integration.xml/1.7.2.4/Wed Apr 23 02:24:19 2003//TBUGZILLA-2_16_3
+/introduction.xml/1.1.2.4/Wed Apr 23 02:24:19 2003//TBUGZILLA-2_16_3
+/patches.xml/1.13.2.4/Wed Apr 23 02:24:20 2003//TBUGZILLA-2_16_3
+/using.xml/1.10.2.6/Wed Apr 23 02:24:20 2003//TBUGZILLA-2_16_3
+/variants.xml/1.6.2.7/Wed Apr 23 02:24:20 2003//TBUGZILLA-2_16_3
+D
diff --git a/docs/xml/CVS/Repository b/docs/xml/CVS/Repository
new file mode 100644
index 0000000000000000000000000000000000000000..ee5efb57d5a11cd3771ae1a71dc0bd1e61e4e862
--- /dev/null
+++ b/docs/xml/CVS/Repository
@@ -0,0 +1 @@
+mozilla/webtools/bugzilla/docs/xml
diff --git a/docs/sgml/CVS/Root b/docs/xml/CVS/Root
similarity index 100%
rename from docs/sgml/CVS/Root
rename to docs/xml/CVS/Root
diff --git a/docs/xml/CVS/Tag b/docs/xml/CVS/Tag
new file mode 100644
index 0000000000000000000000000000000000000000..6406b9811aa41c52e7340d365f79f5cb0c82ed59
--- /dev/null
+++ b/docs/xml/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_16_3
diff --git a/docs/sgml/about.sgml b/docs/xml/about.xml
similarity index 60%
rename from docs/sgml/about.sgml
rename to docs/xml/about.xml
index b4349644a96e3b365694de784b96c8bee7471172..dd99e95affa65a5ad6eb1423619dae4f35f31ddf 100644
--- a/docs/sgml/about.sgml
+++ b/docs/xml/about.xml
@@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
+<!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
<chapter id="about">
<title>About This Guide</title>
@@ -7,14 +7,14 @@
<section id="copyright">
<title>Copyright Information</title>
<blockquote>
- <attribution>Copyright (c) 2000-2002 Matthew P. Barnson and &bzg-auth;</attribution>
+ <attribution>Copyright (c) 2000-2003 Matthew P. Barnson and &bzg-auth;</attribution>
<para>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included below.
+ the license is included in <xref linkend="gfdl"/>.
</para>
</blockquote>
<para>
@@ -23,10 +23,6 @@
please contact &bzg-auth;.
</para>
-
- <!-- The GNU Free Documentation License -->
- &gfdl;
-
</section>
<section id="disclaimer">
@@ -80,29 +76,22 @@
<title>New Versions</title>
<para>
This is the &bzg-ver; version of The Bugzilla Guide. It is so named
- to match the current version of Bugzilla. If you are
+ to match the version of Bugzilla it is disributed with. If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
</para>
<para>
- This document can be found in the following places:
+ The newest version of this guide can always be found at <ulink
+ url="http://www.bugzilla.org">bugzilla.org</ulink>; including
+ documentation for past releases and the current development version.
</para>
<para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://www.bugzilla.org/">bugzilla.org</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://www.linuxdoc.org/">The Linux
- Documentation Project</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ The documentation for the most recent stable release of Bugzilla can also
+ be found at
+ <ulink url="http://www.tldp.org">The Linux Documentation Project</ulink>.
</para>
+
<para>
The latest version of this document can always be checked out via CVS.
Please follow the instructions available at
@@ -125,44 +114,87 @@
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</para>
- <para>
- <ulink url="mailto://mbarnson@sisna.com">Matthew P. Barnson</ulink>
- for the Herculaean task of pulling together the Bugzilla Guide and
- shepherding it to 2.14.
- </para>
- <para>
- <ulink url="mailto://terry@mozilla.org">Terry Weissman</ulink>
- for initially writing Bugzilla and creating the
- README upon which the UNIX installation documentation is largely based.
- </para>
- <para>
- <ulink url="mailto://tara@tequilarista.org">Tara Hernandez</ulink>
- for keeping Bugzilla development going
- strong after Terry left mozilla.org
- </para>
- <para>
- <ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink>
- for providing insight into the key differences between Red Hat's
- customized Bugzilla, and being largely responsible for the "Red
- Hat Bugzilla" appendix
- </para>
- <para>
- <ulink url="mailto://endico@mozilla.org">Dawn Endico</ulink> for
- being a hacker extraordinaire and putting up with my incessant
- questions and arguments on irc.mozilla.org in #mozwebtools
- </para>
+ <!-- TODO: This is evil... there has to be a valid way to get this look -->
+ <variablelist>
+ <varlistentry>
+ <term>Matthew P. Barnson <email>mbarnson@sisna.com</email></term>
+ <listitem>
+ <para>for the Herculaean task of pulling together the Bugzilla Guide
+ and shepherding it to 2.14.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Terry Weissman <email>terry@mozilla.org</email></term>
+ <listitem>
+ <para>for initially writing Bugzilla and creating the README upon
+ which the UNIX installation documentation is largely based.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Tara Hernandez <email>tara@tequilarists.org</email></term>
+ <listitem>
+ <para>for keeping Bugzilla development going strong after Terry left
+ mozilla.org and for running landfill.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Dave Lawrence <email>dkl@redhat.com</email></term>
+ <listitem>
+ <para>for providing insight into the key differences between Red
+ Hat's customized Bugzilla, and being largely responsible for
+ <xref linkend="variant-redhat"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Dawn Endico <email>endico@mozilla.org</email></term>
+ <listitem>
+ <para>for being a hacker extraordinaire and putting up with Matthew's
+ incessant questions and arguments on irc.mozilla.org in #mozwebtools
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Jacob Steenhagen <email>jake@bugzilla.org</email></term>
+ <listitem>
+ <para>for taking over documentation during the 2.17 development
+ period and backporting relevent docs changes to this 2.16 branch.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
<para>
Last but not least, all the members of the
- <ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"> netscape.public.mozilla.webtools</ulink> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
+ <ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"/>
+ newsgroup. Without your discussions, insight, suggestions, and patches,
+ this could never have happened.
</para>
<para>
Thanks also go to the following people for significant contributions
- to this documentation (in no particular order):
- </para>
- <para>
- Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
- Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
- </para>
+ to this documentation (in alphabetical order):
+ <simplelist type="inline">
+ <member>Andrew Pearson</member>
+ <member>Ben FrantzDale</member>
+ <member>Eric Hanson</member>
+ <member>Gervase Markham</member>
+ <member>Joe Robins</member>
+ <member>Kevin Brannen</member>
+ <member>Ron Teitelbaum</member>
+ <member>Spencer Smith</member>
+ <member>Zach Liption</member>
+ </simplelist>
+ .
+ </para>
</section>
<!-- conventions used here (didn't want to give it a chapter of its own) -->
@@ -184,7 +216,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: -->
diff --git a/docs/sgml/administration.sgml b/docs/xml/administration.xml
similarity index 71%
rename from docs/sgml/administration.sgml
rename to docs/xml/administration.xml
index f932beb25a45b4b011665a711ce6322ca7906a15..e50a6857466ed3ccdfa20c760c640ac4e90ea5e7 100644
--- a/docs/sgml/administration.sgml
+++ b/docs/xml/administration.xml
@@ -748,7 +748,6 @@
</para>
</section>
-
<section id="security">
<title>Bugzilla Security</title>
@@ -763,140 +762,271 @@
<note>
<para>These instructions must, of necessity, be somewhat vague since
Bugzilla runs on so many different platforms. If you have refinements
- of these directions for specific platforms, please submit them to
- <ulink url="mailto://mozilla-webtools@mozilla.org">
- mozilla-webtools@mozilla.org</ulink>
+ of these directions, please submit a bug to &bzg-bugs;.
</para>
</note>
- <para>To secure your installation:
-
- <orderedlist>
- <listitem>
- <para>Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and (from a security
- point of view) poor default configuration choices.</para>
- </listitem>
+ <warning>
+ <para>This is not meant to be a comprehensive list of every possible
+ security issue regarding the tools mentioned in this section. There is
+ no subsitute for reading the information written by the authors of any
+ software running on your system.
+ </para>
+ </warning>
- <listitem>
- <para>
- <emphasis>There is no substitute for understanding the tools on your
- system!</emphasis>
+ <section id="security-networking">
+ <title>TCP/IP Ports</title>
+
+ <!-- TODO: Make this make sense (TCP/IP) -->
+ <para>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
+ only needs 1... 2 if you need to use features that require e-mail such
+ as bug moving or the e-mail interface from contrib. You should audit
+ your server and make sure that you aren't listening on any ports you
+ don't need to be. You may also wish to use some kind of firewall
+ software to be sure that trafic can only be recieved on ports you
+ specify.
+ </para>
+ </section>
- Read
- <ulink url="http://www.mysql.com/doc/P/r/Privilege_system.html">
- The MySQL Privilege System</ulink>
- until you can recite it from memory!</para>
- </listitem>
+ <section id="security-mysql">
+ <title>MySQL</title>
- <listitem>
- <para>Lock down /etc/inetd.conf. Heck, disable inet entirely on this
- box. It should only listen to port 25 for Sendmail and port 80 for
- Apache.</para>
- </listitem>
+ <para>MySQL ships by default with many settings that should be changed.
+ By defaults it allows anybody to connect from localhost without a
+ password and have full administrative capabilities. It also defaults to
+ not have a root password (this is <emphasis>not</emphasis> the same as
+ the system root). Also, many installations default to running
+ <application>mysqld</application> as the system root.
+ </para>
- <listitem>
- <para>Do not run Apache as
- <quote>nobody</quote>
+ <orderedlist>
+ <listitem>
+ <para>Make sure you are running at least version 3.22.32 of MySQL
+ as earlier versions had notable security holes.
+ </para>
+ </listitem>
- . 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.
- <note>
- <para>
- <quote>nobody</quote>
+ <listitem>
+ <para>Consult the documentation that came with your system for
+ information on making <application>mysqld</application> run as an
+ unprivleged user.
+ </para>
+ </listitem>
- is a real user on UNIX systems. Having a process run as user id
- <quote>nobody</quote>
+ <listitem>
+ <para>You should also be sure to disable the anonymous user account
+ and set a password for the root user. This is accomplished using the
+ following commands:
+ </para>
+ <programlisting>
+<prompt>bash$</prompt> mysql mysql
+<prompt>mysql></prompt> DELETE FROM user WHERE user = '';
+<prompt>mysql></prompt> UPDATE user SET password = password('<replaceable>new_password</replaceable>') WHERE user = 'root';
+<prompt>mysql></prompt> FLUSH PRIVILEGES;
+ </programlisting>
+ <para>From this point forward you will need to use
+ <command>mysql -u root -p</command> and enter
+ <replaceable>new_password</replaceable> when prompted when using the
+ mysql client.
+ </para>
+ </listitem>
- is absolutely no protection against system crackers versus using
- any other user account. As a general security measure, I recommend
- you create unique user ID's for each daemon running on your system
- and, if possible, use "chroot" to jail that process away from the
- rest of your system.</para>
- </note>
- </para>
- </listitem>
+ <listitem>
+ <para>If you run MySQL on the same machine as your httpd server, you
+ should consider disabling networking from within MySQL by adding
+ the following to your <filename>/etc/my.conf</filename>:
+ </para>
+ <programlisting>
+[myslqd]
+# Prevent network access to MySQL.
+skip-networking
+ </programlisting>
+ </listitem>
- <listitem>
- <para>Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ directory, as well as the
- $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" database account password.
- In addition, some
- files under $BUGZILLA_HOME/data/ store sensitive information.
+ <listitem>
+ <para>You may also consider running MySQL, or even all of Bugzilla
+ in a chroot jail; however, instructions for doing that are beyond
+ the scope of this document.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </section>
+
+ <section id="security-daemon">
+ <title>Daemon Accounts</title>
+
+ <para>Many daemons, such as Apache's httpd and MySQL's mysqld default to
+ running as either <quote>root</quote> or <quote>nobody</quote>. Running
+ as <quote>root</quote> introduces obvious security problems, but the
+ problems introduced by running everything as <quote>nobody</quote> may
+ not be so obvious. Basically, if you're running every daemon as
+ <quote>nobody</quote> and one of them gets comprimised, they all get
+ comprimised. For this reason it is recommended that you create a user
+ account for each daemon.
+ </para>
+
+ <note>
+ <para>You will need to set the <varname>webservergroup</varname> to
+ the group you created for your webserver to run as in
+ <filename>localconfig</filename>. This will allow
+ <command>./checksetup.pl</command> to better adjust the file
+ permissions on your Bugzilla install so as to not require making
+ anything world-writable.
</para>
+ </note>
- <para>Bugzilla provides default .htaccess files to protect the most
- common Apache installations. However, you should verify these are
- adequate according to the site-wide security policy of your web
- server, and ensure that the .htaccess files are allowed to
- "override" default permissions set in your Apache configuration
- files. Covering Apache security is beyond the scope of this Guide;
- please consult the Apache documentation for details.</para>
-
- <para>If you are using a web server that does not support the
- .htaccess control method,
- <emphasis>you are at risk!</emphasis>
-
- After installing, check to see if you can view the file
- "localconfig" in your web browser (e.g.:
- <ulink url="http://bugzilla.mozilla.org/localconfig">
- http://bugzilla.mozilla.org/localconfig</ulink>
-
- ). If you can read the contents of this file, your web server has
- not secured your bugzilla directory properly and you must fix this
- problem before deploying Bugzilla. If, however, it gives you a
- "Forbidden" error, then it probably respects the .htaccess
- conventions and you are good to go.</para>
-
- <para>When you run checksetup.pl, the script will attempt to modify
- various permissions on files which Bugzilla uses. If you do not have
- a webservergroup set in the localconfig file, then Bugzilla will have
- to make certain files world readable and/or writable.
- <emphasis>THIS IS INSECURE!</emphasis>
-
- . This means that anyone who can get access to your system can do
- whatever they want to your Bugzilla installation.</para>
+ </section>
- <note>
- <para>This also means that if your webserver runs all cgi scripts
- as the same user/group, anyone on the system who can run cgi
- scripts will be able to take control of your Bugzilla
- installation.</para>
- </note>
+ <section id="security-access">
+ <title>Web Server Access Controls</title>
+
+ <para>There are many files that are placed in the Bugzilla directory
+ area that should not be accessable from the web. Because of the way
+ Bugzilla is currently layed out, the list of what should and should
+ not be accessible is rather complicated. A new installation method
+ is currently in the works which should solve this by allowing files
+ that shouldn't be accessible from the web to be placed in directory
+ outside the webroot. See
+ <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=44659">bug
+ 44659</ulink> for more 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>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>In the main Bugzilla directory, you should:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block:
+ <simplelist type="inline">
+ <member><filename>*.pl</filename></member>
+ <member><filename>*localconfig*</filename></member>
+ <member><filename>runtests.sh</filename></member>
+ <member><filename>processmail</filename></member>
+ <member><filename>syncshadowdb</filename></member>
+ </simplelist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>But allow:
+ <simplelist type="inline">
+ <member><filename>localconfig.js</filename></member>
+ <member><filename>localconfig.rdf</filename></member>
+ </simplelist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
- for the localconfig file, and
- <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">Bug
- 65572</ulink>
+ <listitem>
+ <para>In <filename class="directory">data</filename>:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ <listitem>
+ <para>But allow:
+ <simplelist type="inline">
+ <member><filename>duplicates.rdf</filename></member>
+ </simplelist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
- for adequate protection in your data/ directory.</para>
+ <listitem>
+ <para>In <filename class="directory">data/webdot</filename>:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>If you use a remote webdot server:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ <listitem>
+ <para>But allow
+ <simplelist type="inline">
+ <member><filename>*.dot</filename></member>
+ </simplelist>
+ only for the remote webdot server</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Otherwise, if you use a local GraphViz:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ <listitem>
+ <para>But allow:
+ <simplelist type="inline">
+ <member><filename>*.png</filename></member>
+ <member><filename>*.gif</filename></member>
+ <member><filename>*.jpg</filename></member>
+ <member><filename>*.map</filename></member>
+ </simplelist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>And if you don't use any dot:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
- <para>Note the instructions which follow are Apache-specific. If you
- use IIS, Netscape, or other non-Apache web servers, please consult
- your system documentation for how to secure these files from being
- transmitted to curious users.</para>
+ <listitem>
+ <para>In <filename class="directory">Bugzilla</filename>:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
- <para>Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/data directory.
- <literallayout><Files comments> allow from all </Files>
- deny from all</literallayout>
+ <listitem>
+ <para>In <filename class="directory">template</filename>:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para>Block everything</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+ <tip>
+ <para>Bugzilla ships with the ability to generate
+ <filename>.htaccess</filename> files instructing Apache which files
+ should and should not be accessible.
</para>
+ </tip>
- <para>Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/ directory.
- <literallayout><Files localconfig> deny from all </Files>
- allow from all</literallayout>
+ <para>You should test to make sure that the files mentioned above are
+ not accessible from the Internet, especially your
+ <filename>localconfig</filename> file which contains your database
+ password. To test, simply point your web browser at the file; for
+ example, to test mozilla.org's installation, we'd try to access
+ <ulink url="http://bugzilla.mozilla.org/localconfig"/>. You should
+ get a <errorcode>403</errorcode> <errorname>Forbidden</errorname>
+ error.
+ </para>
+
+ <caution>
+ <para>Not following the instructions in this section, including
+ testing, may result in sensitive information being globally
+ accessible.
</para>
+ </caution>
+
+ </section>
- </listitem>
- </orderedlist>
- </para>
</section>
<section id="cust-templates">
@@ -1179,35 +1309,196 @@
<section id="upgrading">
<title>Upgrading to New Releases</title>
- <para>A plain Bugzilla is fairly easy to upgrade from one version to a
- newer one. Always read the release notes to see if there are any issues
- that you might need to take note of. It is recommended that you take a
- backup of your database and your entire Bugzilla installation before attempting an
- upgrade. You can upgrade a 'clean' installation by untarring a new
- tarball over the old installation. If you are upgrading from 2.12 or
- later, and have cvs installed, you can type <filename>cvs -z3 update</filename>,
- and resolve conflicts if there are any.
+ <para>Upgrading Bugzilla is something we all want to do from time to time,
+ be it to get new features or pick up the latest security fix. How easy
+ it is to update depends on a few factors.
</para>
-
- <para>However, things get a bit more complicated if you've made
- changes to Bugzilla's code. In this case, you may have to re-make or
- reapply those changes. One good method is to take a diff of your customised
- version against the original, so you can survey all that you've changed.
- Hopefully, templatisation will reduce the need for
- this in the future.</para>
-
- <para>From version 2.8 onwards, Bugzilla databases can be automatically
- carried forward during an upgrade. However, because the developers of
- Bugzilla are constantly adding new
- tables, columns and fields, you'll probably get SQL errors if you just
- update the code and attempt to use Bugzilla. Always run the
- <filename>checksetup.pl</filename>
- script whenever you upgrade your installation.</para>
-
- <para>If you are running Bugzilla version 2.8 or lower, and wish to
- upgrade to the latest version, please consult the file,
- "UPGRADING-pre-2.8" in the Bugzilla root directory after untarring the
- archive.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>If the new version is a revision or a new point release</para>
+ </listitem>
+ <listitem>
+ <para>How many, if any, local changes have been made</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>There are also three different methods to upgrade your installation.
+ </para>
+
+ <orderedlist>
+ <listitem>
+ <para>Using CVS (<xref linkend="upgrade-cvs"/>)</para>
+ </listitem>
+ <listitem>
+ <para>Downloading a new tarball (<xref linkend="upgrade-tarball"/>)</para>
+ </listitem>
+ <listitem>
+ <para>Applying the relevant patches (<xref linkend="upgrade-patches"/>)</para>
+ </listitem>
+ </orderedlist>
+
+ <para>Which options are available to you may depend on how large a jump
+ you are making and/or your network configuration.
+ </para>
+
+ <para>Revisions are normally released to fix security vulnerabilities
+ and are distinguished by an increase in the third number. For example,
+ when 2.16.2 was released, it was a revision to 2.16.1.
+ </para>
+
+ <para>Point releases are normally released when the Bugzilla team feels
+ that there has been a significant amount of progress made between the
+ last point release and the current time. These are often proceeded by a
+ stabilization period and release candidates, however the use of
+ development versions or release candidates is beyond the scope of this
+ document. Point releases can be distinguished by an increase in the
+ second number, or minor version. For example, 2.16.2 is a newer point
+ release than 2.14.5.
+ </para>
+
+ <para>The examples in this section are written as if you were updating
+ to version 2.16.2. The procedures are the same regardless if you are
+ updating to a new point release or a new revision. However, the chance
+ of running into trouble increases when upgrading to a new point release,
+ escpecially if you've made local changes.
+ </para>
+
+ <para>These examples also assume that your Bugzilla installation is at
+ <filename>/var/www/html/bugzilla</filename>. If that is not the case,
+ simply substitute the proper paths where appropriate.
+ </para>
+
+ <example id="upgrade-cvs">
+ <title>Upgrading using CVS</title>
+
+ <para>Every release of Bugzilla, whether it is a revision or a point
+ release, is tagged in CVS. Also, every tarball we have distributed
+ since version 2.12 has been primed for using CVS. This does, however,
+ require that you are able to access cvs-mirror.mozilla.org on port
+ 2401.
+
+ <tip>
+ <para>If you can do this, updating using CVS is probably the most
+ painless method, especially if you have a lot of local changes.
+ </para>
+ </tip>
+ </para>
+
+ <programlisting>
+bash$ <command>cd /var/www/html/bugzilla</command>
+bash$ <command>cvs login</command>
+Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
+CVS password: <command>anonymous</command>
+bash$ <command>cvs -q update -r BUGZILLA-2_16_2 -dP</command>
+P checksetup.pl
+P collectstats.pl
+P globals.pl
+P docs/rel_notes.txt
+P template/en/default/list/quips.html.tmpl
+ </programlisting>
+
+ <para>
+ <caution>
+ <para>If a line in the output from <command>cvs update</command>
+ begins with a <computeroutput>C</computeroutput> that represents a
+ file with local changes that CVS was unable to properly merge. You
+ need to resolve these conflicts manually before Bugzilla (or at
+ least the portion using that file) will be usable.
+ </para>
+ </caution>
+
+ <note>
+ <para>You also need to run <command>./checksetup.pl</command>
+ before your Bugzilla upgrade will be complete.
+ </para>
+ </note>
+ </para>
+ </example>
+
+ <example id="upgrade-tarball">
+ <title>Upgrading using the tarball</title>
+
+ <para>If you are unable or unwilling to use CVS, another option that's
+ always available is to download the latest tarball. This is the most
+ difficult option to use, especially if you have local changes.
+ </para>
+
+ <programlisting>
+bash$ <command>cd /var/www/html</command>
+bash$ <command>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</command>
+<emphasis>Output omitted</emphasis>
+bash$ <command>tar xzvf bugzilla-2.16.2.tar.gz</command>
+bugzilla-2.16.2/
+bugzilla-2.16.2/.cvsignore
+bugzilla-2.16.2/1x1.gif
+<emphasis>Output truncated</emphasis>
+bash$ <command>cd bugzilla-2.16.2</command>
+bash$ <command>cp ../bugzilla/localconfig* .</command>
+bash$ <command>cp -r ../bugzilla/data .</command>
+bash$ <command>cd ..</command>
+bash$ <command>mv bugzilla bugzilla.old</command>
+bash$ <command>mv bugzilla-2.16.2 bugzilla</command>
+bash$ <command>cd bugzilla</command>
+bash$ <command>./checksetup.pl</command>
+<emphasis>Output omitted</emphasis>
+ </programlisting>
+
+ <para>
+ <warning>
+ <para>The <command>cp</command> commands both end with periods which
+ is a very important detail, it tells the shell that the destination
+ directory is the current working directory. Also, the period at the
+ beginning of the <command>./checksetup.pl</command> is important and
+ can not be omitted.
+ </para>
+ </warning>
+
+ <note>
+ <para>You will now have to reapply any changes you have made to your
+ local installation manually.
+ </para>
+ </note>
+ </para>
+ </example>
+
+ <example id="upgrade-patches">
+ <title>Upgrading using patches</title>
+
+ <para>The Bugzilla team will normally make a patch file available for
+ revisions to go from the most recent revision to the new one. You could
+ also read the release notes and grab the patches attached to the
+ mentioned bug, but it is safer to use the released patch file as
+ sometimes patches get changed before they get checked in (for minor
+ spelling fixes and the like). It is also theorectically possible to
+ scour the fixed bug list and pick and choose which patches to apply
+ from a point release, but this is not recommended either as what you'll
+ end up with is a hodge podge Bugzilla that isn't really any version.
+ This would also make it more difficult to upgrade in the future.
+ </para>
+
+ <programlisting>
+bash$ <command>cd /var/www/html/bugzilla</command>
+bash$ <command>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</command>
+<emphasis>Output omitted</emphasis>
+bash$ <command>gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</command>
+bash$ <command>patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</command>
+patching file checksetup.pl
+patching file collectstats.pl
+patching file globals.pl
+ </programlisting>
+
+ <para>
+ <caution>
+ <para>If you do this, beware that this doesn't change the entires in
+ your <filename id="dir">CVS</filename> directory so it may make
+ updates using CVS (<xref linkend="upgrade-cvs"/>) more difficult in the
+ future.
+ </para>
+ </caution>
+ </para>
+ </example>
+
</section>
<!-- Integrating Bugzilla with Third-Party Tools -->
@@ -1230,7 +1521,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/conventions.sgml b/docs/xml/conventions.xml
similarity index 92%
rename from docs/sgml/conventions.sgml
rename to docs/xml/conventions.xml
index 7334b02b8b9dc350e1d73eb5c6dadf8058472d28..7efce1a1eb72a51ef7fb5219e2d3622ed7cd5de9 100644
--- a/docs/sgml/conventions.sgml
+++ b/docs/xml/conventions.xml
@@ -20,7 +20,7 @@
<tbody>
<row>
- <entry>Warnings</entry>
+ <entry>Use caution</entry>
<entry>
<caution>
@@ -50,7 +50,7 @@
</row>
<row>
- <entry>Information requiring special attention</entry>
+ <entry>Warnings</entry>
<entry>
<warning>
@@ -134,6 +134,14 @@
</entry>
</row>
+ <row>
+ <entry>Term found in the glossary</entry>
+
+ <entry>
+ <glossterm linkend="gloss-bugzilla">Bugzilla</glossterm>
+ </entry>
+ </row>
+
<row>
<entry>Code Example</entry>
@@ -163,7 +171,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/database.sgml b/docs/xml/database.xml
similarity index 99%
rename from docs/sgml/database.sgml
rename to docs/xml/database.xml
index d758259da2938945e77e5d101e12b8a29a4965dc..7291c4e42a99d6e4483d9e9c5ff05eb7a317f64a 100644
--- a/docs/sgml/database.sgml
+++ b/docs/xml/database.xml
@@ -385,7 +385,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/dbschema.mysql b/docs/xml/dbschema.mysql
similarity index 100%
rename from docs/sgml/dbschema.mysql
rename to docs/xml/dbschema.mysql
diff --git a/docs/sgml/faq.sgml b/docs/xml/faq.xml
similarity index 77%
rename from docs/sgml/faq.sgml
rename to docs/xml/faq.xml
index 91380863fa39d92b663821f2ae6b2bb3a3e1fe05..3944ff0eba29ac488aadf4a6bfd2cdb0911e9b09 100644
--- a/docs/sgml/faq.sgml
+++ b/docs/xml/faq.xml
@@ -14,7 +14,7 @@
<title>General Questions</title>
<qandaentry>
- <question>
+ <question id="faq-general-information">
<para>
Where can I find information about Bugzilla?</para>
</question>
@@ -28,7 +28,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-license">
<para>
What license is Bugzilla distributed under?
</para>
@@ -43,12 +43,17 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-support">
<para>
How do I get commercial support for Bugzilla?
</para>
</question>
<answer>
+ <para>
+ <ulink url="http://bugzilla.org/consulting.html"/>
+ is a list of people and companies who have asked us to list them
+ as consultants for Bugzilla.
+ </para>
<para>
<ulink url="http://www.collab.net/">www.collab.net</ulink> offers
Bugzilla as part of their standard offering to large projects.
@@ -65,7 +70,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-companies">
<para>
What major companies or projects are currently using Bugzilla
for bug-tracking?
@@ -73,13 +78,12 @@
</question>
<answer>
<para>
- There are <emphasis>dozens</emphasis> of major comapanies with public
+ There are <emphasis>dozens</emphasis> of major companies with public
Bugzilla sites to track bugs in their products. A few include:
<simplelist>
<member>Netscape/AOL</member>
<member>Mozilla.org</member>
<member>NASA</member>
- <member>AtHome Corporation</member>
<member>Red Hat Software</member>
<member>SuSe Corp</member>
<member>The Horde Project</member>
@@ -103,7 +107,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-maintainers">
<para>
Who maintains Bugzilla?
</para>
@@ -112,13 +116,13 @@
<para>
A
<ulink url="http://www.bugzilla.org/who_we_are.html">core team</ulink>,
- led by Dave Miller (justdave@syndicomm.com).
+ led by Dave Miller (justdave@netscape.com).
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-compare">
<para>
How does Bugzilla stack up against other bug-tracking databases?
</para>
@@ -145,9 +149,9 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-bzmissing">
<para>
- Why doesn't Bugzilla offer this or that feature or compatability
+ Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</para>
</question>
@@ -170,7 +174,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-mysql">
<para>
Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
@@ -178,37 +182,51 @@
</question>
<answer>
<para>
- There is DB-independence work afoot. PostgreSQL support is planned
- for 2.18, and full DB-independence can't be far further on.
- </para>
+ MySQL was originally chosen because it is free, easy to install,
+ and was available for the hardware Netscape intended to run it on.
+ </para>
+ <para>
+ There is currently work in progress to make Bugzilla work on
+ PostgreSQL and Sybase in the default distribution. You can track
+ the progress of these initiatives in bugs <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=98304">98304</ulink>
+ and <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=173130">173130</ulink>
+ respectively.
+ </para>
+ <para>
+ Once both of these are done, adding support for additional
+ database servers should be trivial.
+ </para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-bonsaitools">
<para>
- Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
- "/usr/bin/perl" or something else?
+ Why do the scripts say
+ <filename>/usr/bonsaitools/bin/perl</filename> instead of
+ <filename>/usr/bin/perl</filename> or something else?
</para>
</question>
<answer>
<para>
- Mozilla.org uses /usr/bonsaitools/bin/perl, because originally
- Terry wanted a place to put a version of Perl and other tools
- that was strictly under his control.
- </para>
- <para>
- We always recommend that, if possible, you keep the path
- as /usr/bonsaitools/bin/perl, and simply add symlink.
- This will make upgrading
- your Bugzilla much easier in the future.
- </para>
+ Mozilla.org used <filename>/usr/bonsaitools/bin/perl</filename>,
+ because originally Terry wanted a place to put a version of Perl
+ and other tools that was strictly under his control.
+ </para>
+ <note>
+ <para>
+ This convention was abonded during the 2.17 development cycle so
+ it will no longer be an issue when 2.18 comes out.
+ </para>
+ </note>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-general-cookie">
<para>
Is there an easy way to change the Bugzilla cookie name?
</para>
@@ -233,7 +251,7 @@
</para>
<qandaentry>
- <question>
+ <question id="faq-phb-client">
<para>
Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
@@ -248,7 +266,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-integration">
<para>
Can Bugzilla integrate with
Perforce (SCM software)?
@@ -263,23 +281,28 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-projects">
<para>
Does Bugzilla allow the user to track multiple projects?
</para>
</question>
<answer>
<para>
- Absolutely! You can track any number of Products (although you
- are limited to about 55 or so if
- you are using Product-Based Groups), that can each be composed of any
- number of Components.
+ Absolutely! You can track any number of Products that can each be
+ composed of any number of Components.
</para>
+ <note>
+ <para>There are only 55 groups available in version 2.16 of
+ Bugzilla. If you are using product groups, this will also limit
+ the number of products you can have. This limit does not exist in
+ the current 2.17 development releases and will not exist in 2.18.
+ </para>
+ </note>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-sorting">
<para>
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?
@@ -293,7 +316,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-attachments">
<para>
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
@@ -303,15 +326,15 @@
<para>
Yes - any sort of attachment is allowed, although administrators can
configure a maximum size.
- There are many specific MIME-types that are pre-defined by Bugzilla,
- but you may specify any arbitrary MIME-type you need when you
- upload the file.
+ Bugzilla gives the user the option of either using the MIME-type
+ supplied by the browser, choosing from a pre-defined list or
+ manually typing any arbitrary MIME-type.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-priorities">
<para>
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
@@ -327,14 +350,13 @@
<para>
There is no GUI for adding fields to Bugzilla at this
time. You can follow development of this feature at
- <ulink
- url="http://bugzilla.mozilla.org/show_bug.cgi?id=91037">http://bugzilla.mozilla.org/show_bug.cgi?id=91037</ulink>
+ <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"/>.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-reporting">
<para>
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
@@ -342,23 +364,29 @@
</question>
<answer>
<para>
- Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi">
- http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting
- and graphing facilities.
+ Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi"/>
+ for samples of what Bugzilla can do in reporting and graphing.
</para>
<para>
- For more advanced reporting, I recommend hooking up a professional
- reporting package, such as Crystal Reports, and use ODBC to access
- the MySQL database. You can do a lot through the Query page of
- Bugzilla as well, but right now Advanced Reporting is much
- better accomplished through third-party utilities that can
- interface with the database directly.
+ If you can not get the reports you want from the included reporting
+ scripts, it is possible to hook up a professional reporting package
+ such as Crystal Reports using ODBC. If you choose to do this,
+ beware that giving direct access to the database does contain some
+ security implications. Even if you give read-only access to the
+ bugs database it will bypass the secure bugs features of Bugzilla.
</para>
+ <note>
+ <para>
+ Bugzilla's current development versions can do a lot more in the
+ way of reporting. To see examples, check out
+ <ulink url="http://bugzilla.mozilla.org/report.cgi"/>.
+ </para>
+ </note>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-email">
<para>
Is there email notification and if so, what do you see when you get an
email?
@@ -374,7 +402,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-cclist">
<para>
Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
@@ -388,7 +416,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-emailapp">
<para>
Do users have to have any particular
type of email application?
@@ -413,7 +441,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-data">
<para>
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
@@ -422,31 +450,33 @@
</para>
</question>
<answer>
- <para>
- Mozilla allows data export through a custom DTD in XML format.
- It does not, however, export to specific formats other than the
- XML Mozilla DTD. Importing the data into Excel or any other application
- is left as an exercise for the reader.
- </para>
- <para>
- If you create import filters to other applications from Mozilla's XML,
- please submit your modifications for inclusion in future Bugzilla
- distributions.
- </para>
- <para>
- As for data import, any application can send data to Bugzilla through
- the HTTP protocol, or through Mozilla's XML API. However, it seems
- kind of silly to put another front-end in front of Bugzilla;
- it makes more sense to create a simplified bug submission form in
- HTML. You can find an excellent example at
- <ulink url="http://www.mozilla.org/quality/help/bugzilla-helper.html">
- http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink>
- </para>
+ <para>
+ Bugzilla can only output buglists as HTML in version 2.16. There
+ are other formats available (CSV and RDF) in the newer development
+ versions.
+ </para>
+ <para>
+ Bugzilla can export bugs using <filename>xml.cgi</filename> with
+ either a bug number or list of bug numbers.
+ </para>
+ <para>
+ Currently the only script included with Bugzilla that can import
+ data is <filename>importxml.pl</filename> which is intended to be
+ used for importing the data generated by <filename>xml.cgi</filename>
+ in association with bug moving. Any other use is left as an
+ exercise for the user.
+ </para>
+ <para>
+ There are also scripts included in the <filename>contrib/</filename>
+ directory for using e-mail to import information into Bugzilla,
+ but these scripts are not currently supported and included for
+ educational purposes.
+ </para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-l10n">
<para>
Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
@@ -454,16 +484,20 @@
</question>
<answer>
<para>
- To a certain extent, yes. 2.16's templates mean that you can localise
- the user-facing UI (and several projects are doing exactly that.) However,
- error messages and the admin interface are currently not localisable.
- This should be achieved by 2.18.
+ Yes. For more information including available translated templates,
+ see <ulink
+ url="http://www.bugzilla.org/download.html#localizations"/>.
+ The admin interfaces are still not included in these translated
+ templates and is therefore still English only. Also, there may be
+ issues with the charset not being declared. See <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=126266">bug 126226</ulink>
+ for more information.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-reports">
<para>
Can a user create and save reports? Can they do this in Word format?
Excel format?
@@ -471,13 +505,13 @@
</question>
<answer>
<para>
- Yes. No. No.
+ Yes. No. Not in 2.16.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-searching">
<para>
Does Bugzilla have the ability to search by word, phrase, compound
search?
@@ -492,7 +526,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-midair">
<para>
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
@@ -508,7 +542,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-backup">
<para>
Are there any backup features provided?
</para>
@@ -524,7 +558,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-livebackup">
<para>
Can users be on the system while a backup is in progress?
</para>
@@ -539,7 +573,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-maintenance">
<para>
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
@@ -563,7 +597,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-installtime">
<para>
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
@@ -585,7 +619,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-phb-cost">
<para>
Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
@@ -604,7 +638,7 @@
<title>Bugzilla Security</title>
<qandaentry>
- <question>
+ <question id="faq-security-mysql">
<para>
How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide)?
@@ -620,7 +654,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-security-knownproblems">
<para>
Are there any security problems with Bugzilla?
</para>
@@ -638,7 +672,7 @@
<qandaentry>
- <question>
+ <question id="faq-security-mysqluser">
<para>
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
@@ -659,7 +693,7 @@
<title>Bugzilla Email</title>
<qandaentry>
- <question>
+ <question id="faq-email-nomail">
<para>
I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
@@ -668,13 +702,14 @@
<answer>
<para>
The user should be able to set
- this in user email preferences (uncheck all boxes.)
+ this in user email preferences (uncheck all boxes) or you can add
+ their email address to the <filename>data/nomail</filename> file.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-testing">
<para>
I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
@@ -682,14 +717,14 @@
</question>
<answer>
<para>
- Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
+ Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-whine">
<para>
I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
@@ -698,8 +733,8 @@
<answer>
<para>
Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
- You can find it at<ulink url=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679">
- http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This
+ You can find it at <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"/>. This
patch is against an older version of Bugzilla, so you must apply
the diffs manually.
</para>
@@ -707,7 +742,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-procmail">
<para>
I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
@@ -730,7 +765,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-mailif">
<para>
How do I set up the email interface to submit/change bugs via email?
</para>
@@ -744,7 +779,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-sendmailnow">
<para>
Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
@@ -765,7 +800,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-email-nonreceived">
<para>
How come email from Bugzilla changes never reaches me?
</para>
@@ -790,23 +825,24 @@
<title>Bugzilla Database</title>
<qandaentry>
- <question>
+ <question id="faq-db-oracle">
<para>
I've heard Bugzilla can be used with Oracle?
</para>
</question>
<answer>
<para>
- Red Hat Bugzilla works with Oracle. The current version
- from Mozilla.org does not have this capability. Unfortunately, though
- you will sacrifice a lot of the really great features available in
- Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+ Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
+ Red Hat's newer version (based on 2.17.1 and soon to be merged into
+ the main distribution) runs on PostgreSQL. At this time we know of
+ no recent ports of Bugzilla to Oracle but do intend to support it
+ in the future (possibly the 2.20 time-frame).
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-db-corrupted">
<para>
I think my database might be corrupted, or contain invalid entries. What
do I do?
@@ -834,7 +870,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-db-manualedit">
<para>
I want to manually edit some entries in my database. How?
</para>
@@ -843,31 +879,19 @@
<para>
There is no facility in Bugzilla itself to do this. It's also generally
not a smart thing to do if you don't know exactly what you're doing.
- However, if you understand SQL you can use the mysqladmin utility to
- manually insert, delete, and modify table information. Personally, I
- use "phpMyAdmin". You have to compile a PHP module with MySQL
- support to make it work, but it's very clean and easy to use.
- </para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>
- I try to add myself as a user, but Bugzilla always tells me my password is wrong.
- </para>
- </question>
- <answer>
- <para>
- Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
- the "crypt()" function. This prevented MySQL from storing encrypted passwords.
- Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+ However, if you understand SQL you can use the <command>mysql</command>
+ command line utility to manually insert, delete and modify table
+ information. There are also more intuitive GUI clients available.
+ Personal favorites of the Bugzilla team are <ulink
+ url="http://www.phpmyadmin.net/">phpMyAdmin</ulink> and <ulink
+ url="http://www.mysql.com/downloads/gui-mycc.html">MySQL Control
+ Center</ulink>.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-db-permissions">
<para>
I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
@@ -877,15 +901,22 @@
<para>
Try running MySQL from its binary: "mysqld --skip-grant-tables". This
will allow you to completely rule out grant tables as the cause of your
- frustration. However, I do not recommend you run it this way on a regular
- basis, unless you really want your web site defaced and your machine
- cracked.
- </para>
+ frustration. If this Bugzilla is able to connect at this point then
+ you need to check that you have granted proper permission to the user
+ password combo defined in <filename>localconfig</filename>.
+ </para>
+ <warning>
+ <para>
+ Running MySQL with this command line option is very insecure and
+ should only be done when not connected to the external network
+ as a troubleshooting step.
+ </para>
+ </warning>
</answer>
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-db-synchronize">
<para>
How do I synchronize bug information among multiple different Bugzilla
databases?
@@ -916,7 +947,7 @@
<title>Bugzilla and Win32</title>
<qandaentry>
- <question>
+ <question id="faq-nt-easiest">
<para>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</para>
@@ -930,7 +961,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-nt-bundle">
<para>
Is there a "Bundle::Bugzilla" equivalent for Win32?
</para>
@@ -945,7 +976,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-nt-mappings">
<para>
CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
@@ -977,7 +1008,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-nt-dbi">
<para>
I'm having trouble with the perl modules for NT not being able to talk to
to the database.
@@ -1027,7 +1058,7 @@
<title>Bugzilla Usage</title>
<qandaentry>
- <question>
+ <question id="faq-use-changeaddress">
<para>
How do I change my user name (email address) in Bugzilla?
</para>
@@ -1041,7 +1072,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-use-query">
<para>
The query page is very confusing. Isn't there a simpler way to query?
</para>
@@ -1056,7 +1087,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-use-accept">
<para>
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?
@@ -1080,7 +1111,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-use-attachment">
<para>
I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
@@ -1096,23 +1127,7 @@
</qandaentry>
<qandaentry>
- <question>
- <para>
- Email submissions to Bugzilla that have attachments end up asking me to
- save it as a "cgi" file.
- </para>
- </question>
- <answer>
- <para>
- Yup. Just rename it once you download it, or save it under a different
- filename. This will not be fixed anytime soon, because it would
- cripple some other functionality.
- </para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
+ <question id="faq-use-keyword">
<para>
How do I change a keyword in Bugzilla, once some bugs are using it?
</para>
@@ -1132,7 +1147,7 @@
<title>Bugzilla Hacking</title>
<qandaentry>
- <question>
+ <question id="faq-hacking-bugzillabugs">
<para>
What bugs are in Bugzilla right now?
</para>
@@ -1148,7 +1163,7 @@
<ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18">here</ulink>.
This list includes bugs for the 2.18 release that have already
been fixed and checked into CVS. Please consult the
- <ulink url="http://www.mozilla.org/projects/bugzilla/">
+ <ulink url="http://www.bugzilla.org/">
Bugzilla Project Page</ulink> for details on how to
check current sources out of CVS so you can have these
bug fixes early!
@@ -1157,7 +1172,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-hacking-priority">
<para>
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
@@ -1175,7 +1190,7 @@
</qandaentry>
<qandaentry>
- <question>
+ <question id="faq-hacking-patches">
<para>
What's the best way to submit patches? What guidelines should I follow?
</para>
@@ -1252,7 +1267,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/xml/filetemp.patch b/docs/xml/filetemp.patch
new file mode 100644
index 0000000000000000000000000000000000000000..9fb70adcea26ef40bca2c7f6ae458c66c2364898
--- /dev/null
+++ b/docs/xml/filetemp.patch
@@ -0,0 +1,18 @@
+--- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
++++ File/Temp.pm Thu Feb 6 16:26:23 2003
+@@ -205,6 +205,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+@@ -226,6 +227,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
diff --git a/docs/sgml/gd-makefile.patch b/docs/xml/gd-makefile.patch
similarity index 100%
rename from docs/sgml/gd-makefile.patch
rename to docs/xml/gd-makefile.patch
diff --git a/docs/sgml/gfdl.sgml b/docs/xml/gfdl.xml
similarity index 99%
rename from docs/sgml/gfdl.sgml
rename to docs/xml/gfdl.xml
index 04764641105d70b354b1240431ed5687d40c2536..ae19501d28131db2f7e16602910083a1098c754f 100644
--- a/docs/sgml/gfdl.sgml
+++ b/docs/xml/gfdl.xml
@@ -1,5 +1,5 @@
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
-<section id="gfdl">
+<appendix id="gfdl">
<title>GNU Free Documentation License</title>
<!-- - GNU Project - Free Software Foundation (FSF) -->
@@ -423,7 +423,7 @@
software license, such as the GNU General Public License, to permit their
use in free software.</para>
</section>
-</section>
+</appendix>
<!-- Keep this comment at the end of the file
Local variables:
@@ -440,7 +440,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/glossary.sgml b/docs/xml/glossary.xml
similarity index 57%
rename from docs/sgml/glossary.sgml
rename to docs/xml/glossary.xml
index cc5d4fb6940e3759e52c03887e47b0efa0db97ce..c4278898fc173714ab8ae79c3df6bcf1ef9cd6d1 100644
--- a/docs/sgml/glossary.sgml
+++ b/docs/xml/glossary.xml
@@ -41,6 +41,50 @@
<acronym>NCSA</acronym>
world-wide-web server.</para>
+
+ <variablelist>
+ <title>Useful Directives when configuring Bugzilla</title>
+
+ <varlistentry>
+ <term><computeroutput><ulink url="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler">AddHandler</ulink></computeroutput></term>
+ <listitem>
+ <para>Tell Apache that it's OK to run CGI scripts.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><computeroutput><ulink url="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride">AllowOverride</ulink></computeroutput></term>
+ <term><computeroutput><ulink url="http://httpd.apache.org/docs-2.0/mod/core.html#options">Options</ulink></computeroutput></term>
+ <listitem>
+ <para>These directives are used to tell Apache many things about
+ the directory they apply to. For Bugzilla's purposes, we need
+ them to allow script execution and <filename>.htaccess</filename>
+ overrides.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><computeroutput><ulink url="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex">DirectoryIndex</ulink></computeroutput></term>
+ <listitem>
+ <para>Used to tell Apache what files are indexes. If you can
+ not add <filename>index.cgi</filename> to the list of valid files,
+ you'll need to set <computeroutput>$index_html</computeroutput> to
+ 1 in <filename>localconfig</filename> so
+ <command>./checksetup.pl</command> will create an
+ <filename>index.html</filename> that redirects to
+ <filename>index.cgi</filename>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><computeroutput><ulink url="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource">ScriptInterpreterSource</ulink></computeroutput></term>
+ <listitem>
+ <para>Used when running Apache on windows so the shebang line
+ doesn't have to be changed in every Bugzilla script.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
</glossdef>
</glossentry>
</glossdiv>
@@ -75,7 +119,7 @@
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gloss-bugzilla">
<glossterm>Bugzilla</glossterm>
<glossdef>
@@ -86,8 +130,19 @@
</glossdiv>
<glossdiv id="gloss-c">
- <title>
- </title>
+ <title>C</title>
+
+ <glossentry id="gloss-cgi">
+ <glossterm>Common Gateway Interface</glossterm>
+ <acronym>CGI</acronym>
+ <glossdef>
+ <para><acronym>CGI</acronym> is an acronym for Common Gateway Interface.
+ This is a standard for interfacing an external application with a web
+ server. Bugzilla is an example of a <acronym>CGI</acronym> application.
+ </para>
+ </glossdef>
+ </glossentry>
+
<glossentry id="gloss-component">
<glossterm>Component</glossterm>
@@ -138,8 +193,7 @@
</glossdiv>
<glossdiv id="gloss-g">
- <title>
- </title>
+ <title>G</title>
<glossentry>
<glossterm>Groups</glossterm>
@@ -162,17 +216,39 @@
<glossdiv id="gloss-m">
<title>M</title>
- <glossentry>
- <glossterm>mysqld</glossterm>
+ <glossentry id="gloss-mta">
+ <glossterm>Message Transport Agent</glossterm>
+ <acronym>MTA</acronym>
<glossdef>
- <para>mysqld is the name of the
- <glossterm>daemon</glossterm>
+ <para>A Message Transport Agent is used to control the flow of email
+ on a system. Many unix based systems use
+ <ulink url="http://www.sendmail.org">sendmail</ulink> which is what
+ Bugzilla expects to find by default at <filename>/usr/sbin/sendmail</filename>.
+ Many other MTA's will work, but they all require that the
+ <option>sendmailnow</option> param be set to <literal>on</literal>.
+ </para>
+ </glossdef>
+ </glossentry>
- for the MySQL database. In general, it is invoked automatically
- through the use of the System V init scripts on GNU/Linux and
- AT&T System V-based systems, such as Solaris and HP/UX, or
- through the RC scripts on BSD-based systems.</para>
+ <glossentry id="gloss-mysql">
+ <glossterm>MySQL</glossterm>
+
+ <glossdef>
+ <para>MySQL is currently the required
+ <glossterm linkend="gloss-rdbms">RDBMS</glossterm> for Bugzilla. MySQL
+ can be downloaded from <ulink url="http://www.mysql.com"/>. While you
+ should familiarize yourself with all of the documentation, some high
+ points are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><ulink url="http://www.mysql.com/doc/P/r/Privilege_system.html">MySQL
+ Privilege System</ulink> - Much more detailed information about
+ the suggestions in <xref linkend="security-mysql"/>.
+ </para>
+ </listitem>
+ </itemizedlist>
</glossdef>
</glossentry>
</glossdiv>
@@ -231,6 +307,21 @@
</glossentry>
</glossdiv>
+ <glossdiv id="gloss-r">
+ <title>R</title>
+
+ <glossentry id="gloss-rdbms">
+ <glossterm>Relational DataBase Managment System</glossterm>
+ <acronym>RDBMS</acronym>
+
+ <glossdef>
+ <para>A relational database management system is a database system
+ that stores information in tables that are related to each other.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
<glossdiv id="gloss-s">
<title>S</title>
@@ -291,20 +382,54 @@
fixed, or an enhancement will be implemented.</para>
</glossdef>
</glossentry>
+
+ <glossentry id="gloss-tcl">
+ <glossterm>Tool Command Language</glossterm>
+ <acronym>TCL</acronym>
+ <glossdef>
+ <para>TCL is an open source scripting language available for Windows,
+ Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
+ never released. The first release of Bugzilla was 2.0, which was when
+ it was ported to perl.
+ </para>
+ </glossdef>
+ </glossentry>
</glossdiv>
<glossdiv id="gloss-z">
<title>Z</title>
- <glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
+ <glossentry id="gloss-zarro">
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
- <para>This is the cryptic response sent by Bugzilla when a query
- returned no results. It is just a goofy way of saying "Zero Bugs
- Found".</para>
+ <para>This is just a goofy way of saying that there were no bugs
+ found matching your query. When asked to explain this message,
+ Terry had the following to say:
+ </para>
+
+ <blockquote>
+ <attribution>Terry Weissman</attribution>
+ <para>I've been asked to explain this ... way back when, when
+ Netscape released version 4.0 of its browser, we had a release
+ party. Naturally, there had been a big push to try and fix every
+ known bug before the release. Naturally, that hadn't actually
+ happened. (This is not unique to Netscape or to 4.0; the same thing
+ has happened with every software project I've ever seen.) Anyway,
+ at the release party, T-shirts were handed out that said something
+ like "Netscape 4.0: Zarro Boogs". Just like the software, the
+ T-shirt had no known bugs. Uh-huh.
+ </para>
+
+ <para>So, when you query for a list of bugs, and it gets no results,
+ you can think of this as a friendly reminder. Of *course* there are
+ bugs matching your query, they just aren't in the bugsystem yet...
+ </para>
+ </blockquote>
+
</glossdef>
</glossentry>
+
</glossdiv>
</glossary>
@@ -323,7 +448,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/index.sgml b/docs/xml/index.xml
similarity index 87%
rename from docs/sgml/index.sgml
rename to docs/xml/index.xml
index 3b3516e1438a77be2c10cbceff78659dc4d023cb..7fc1a4c14d3c963c445b596a884d8967b64cceac 100644
--- a/docs/sgml/index.sgml
+++ b/docs/xml/index.xml
@@ -13,7 +13,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/installation.sgml b/docs/xml/installation.xml
similarity index 93%
rename from docs/sgml/installation.sgml
rename to docs/xml/installation.xml
index 0433b4b520f0c9193136b9a2353d0dca92dccdd6..d1aacd62f7d1c89521a5c1a6b60d6e5c810c4780 100644
--- a/docs/sgml/installation.sgml
+++ b/docs/xml/installation.xml
@@ -526,7 +526,10 @@
<para>With Apache you'll also want to make sure that within the
httpd.conf file the line:
- <programlisting>Options ExecCGI AllowOverride Limit</programlisting>
+ <programlisting>
+Options ExecCGI
+AllowOverride Limit
+ </programlisting>
is in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
@@ -686,6 +689,12 @@
</member>
</simplelist>
</para>
+
+ <note>
+ <para>If you are using MySQL 4, the bugs user also needs to be granted
+ the LOCK TABLES and CREATE TEMPORARY TABLES permissions.
+ </para>
+ </note>
</section>
<section>
@@ -762,152 +771,6 @@
</note>
</section>
- <section>
- <title>Securing MySQL</title>
-
- <para>If you followed the installation instructions 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>running MySQL in a chroot jail</para>
- </listitem>
-
- <listitem>
- <para>running the httpd in a chroot 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>Configuring Bugzilla</title>
<para>
@@ -1953,7 +1816,7 @@ binmode(STDOUT);
<emphasis>not necessary</emphasis>
for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla &bz-ver;.
+ Bugzilla &bz-ver;.
<example>
<title>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</title>
@@ -2011,7 +1874,7 @@ binmode(STDOUT);
<command>look GD</command>.
This should go through the motions of downloading the latest version of
the GD module, then it will open a shell and drop you into the build
- directory. Apply <ulink url="../sgml/gd-makefile.patch">this patch</ulink>
+ directory. Apply <ulink url="../xml/gd-makefile.patch">this patch</ulink>
to the Makefile.PL file (save the
patch into a file and use the command
<command>patch < patchfile</command>.)
@@ -2138,6 +2001,62 @@ binmode(STDOUT);
as root to fix this problem.
</para>
</section>
+
+ <section id="trouble-filetemp">
+ <title>Your vendor has not defined Fcntl macro O_NOINHERIT</title>
+
+ <para>This is caused by a bug in the version of
+ <productname>File::Temp</productname> that is distributed with perl
+ 5.6.0. Many minor variations of this error have been reported. Examples
+ can be found in <xref linkend="trouble-filetemp-errors"/>.
+ </para>
+
+ <figure id="trouble-filetemp-errors">
+ <title>Other File::Temp error messages</title>
+
+ <programlisting>
+Your vendor has not defined Fcntl macro O_NOINHERIT, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
+
+Your vendor has not defined Fcntl macro O_EXLOCK, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
+
+Your vendor has not defined Fcntl macro O_TEMPORARY, used
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
+ </programlisting>
+ </figure>
+
+ <para>Numerous people have reported that upgrading to version 5.6.1
+ or higher solved the problem for them. A less involved fix is to apply
+ the patch in <xref linkend="trouble-filetemp-patch"/>. The patch is also
+ available as a <ulink url="../xml/filetemp.patch">patch file</ulink>.
+ </para>
+
+ <figure id="trouble-filetemp-patch">
+ <title>Patch for File::Temp in Perl 5.6.0</title>
+
+ <programlisting><![CDATA[
+--- File/Temp.pm.orig Thu Feb 6 16:26:00 2003
++++ File/Temp.pm Thu Feb 6 16:26:23 2003
+@@ -205,6 +205,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+@@ -226,6 +227,7 @@
+ # eg CGI::Carp
+ local $SIG{__DIE__} = sub {};
+ local $SIG{__WARN__} = sub {};
++ local *CORE::GLOBAL::die = sub {};
+ $bit = &$func();
+ 1;
+ };
+ ]]></programlisting>
+ </figure>
+ </section>
</section>
</chapter>
@@ -2156,7 +2075,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/integration.sgml b/docs/xml/integration.xml
similarity index 93%
rename from docs/sgml/integration.sgml
rename to docs/xml/integration.xml
index 68054ee1377c0bc00e8ee501b35065f82490b0f9..514064d26ef9c0ed2e8c0304037ea60539402ba3 100644
--- a/docs/sgml/integration.sgml
+++ b/docs/xml/integration.xml
@@ -30,8 +30,9 @@
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</para>
+ you want to have the bug be closed automatically, you'll have to modify
+ the <filename>contrib/bugzilla_email_append.pl</filename> script.
+ </para>
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
@@ -92,7 +93,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/introduction.sgml b/docs/xml/introduction.xml
similarity index 96%
rename from docs/sgml/introduction.sgml
rename to docs/xml/introduction.xml
index 33907552b5b39c3ce463b50b66edbe9868e1d334..8b5ce80f99e12315e43cf6cc7453f78bee24403f 100644
--- a/docs/sgml/introduction.sgml
+++ b/docs/xml/introduction.xml
@@ -8,8 +8,8 @@
Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
of outstanding problems with their product.
- Bugzilla was originally
- written by Terry Weissman in a programming language called TCL, to
+ Bugzilla was originally written by Terry Weissman in a programming language
+ called <glossterm linkend="gloss-tcl">TCL</glossterm>, to
replace a rudimentary bug-tracking database used internally by Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
it remains to this day. Most commercial defect-tracking software vendors
@@ -142,7 +142,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/patches.sgml b/docs/xml/patches.xml
similarity index 96%
rename from docs/sgml/patches.sgml
rename to docs/xml/patches.xml
index 43f81675828e491662ac3016ee77cc53a65ef87b..84d83d3337d617a6b8b89f15344d43ba8d4ed3dc 100644
--- a/docs/sgml/patches.sgml
+++ b/docs/xml/patches.xml
@@ -1,4 +1,4 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
@@ -105,7 +105,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/using.sgml b/docs/xml/using.xml
similarity index 99%
rename from docs/sgml/using.sgml
rename to docs/xml/using.xml
index a3986c27d2c74b25a6acdef8f5e3fd412a81f388..b5dab9d0a983aef168495ef6917ff16ffa62f6ca 100644
--- a/docs/sgml/using.sgml
+++ b/docs/xml/using.xml
@@ -572,7 +572,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/docs/sgml/variants.sgml b/docs/xml/variants.xml
similarity index 66%
rename from docs/sgml/variants.sgml
rename to docs/xml/variants.xml
index 73f6822fbd1bf4172dd4cbda75959704cb36f30b..690b5098776778dcc13fc41c832a1ac562c4a400 100644
--- a/docs/sgml/variants.sgml
+++ b/docs/xml/variants.xml
@@ -10,52 +10,65 @@
http://linas.org/linux/pm.html</ulink>
</para>
- <section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
+ <section id="variant-redhat">
<title>Red Hat Bugzilla</title>
- <para>Red Hat Bugzilla is a fork of Bugzilla 2.8.
- One of its major benefits is the ability
- to work with Oracle, MySQL, and PostGreSQL databases serving as the
- back-end, instead of just MySQL. Dave Lawrence of Red Hat is
- active in the Bugzilla community, and we hope to see a reunification
- of the fork before too long.</para>
+ <para>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+ obsolete. The newest version in use is based on version 2.17.1 and is in
+ the process of being integrated into the main Bugzilla source tree. The
+ back-end is modified to work with PostgreSQL instead of MySQL and they have
+ custom templates to get their desired look and feel, but other than that it
+ is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
+ effort to make sure that the changes he made could be integrated back into
+ the main tree.
+ <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=98304">Bug
+ 98304</ulink> exists to track this integration.
+ </para>
<para>URL:
<ulink url="http://bugzilla.redhat.com/bugzilla/">
http://bugzilla.redhat.com/bugzilla/</ulink>
</para>
+
+ <para>This section last updated 24 Dec 2002</para>
</section>
- <section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
+ <section id="variant-fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
its custodians recommend Bugzilla for future bug-tracker deployments.
</para>
+
+ <para>This section last updated 27 Jul 2002</para>
</section>
- <section id="variant-issuezilla" xreflabel="Issuezilla">
+ <section id="variant-issuezilla">
<title>Issuezilla</title>
<para>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
at tigris.org is their Java-based bug-tracker,
<xref linkend="variant-scarab"/>.</para>
+
+ <para>This section last updated 27 Jul 2002</para>
</section>
- <section id="variant-scarab" xreflabel="Scarab">
+ <section id="variant-scarab">
<title>Scarab</title>
<para>Scarab is a new open source bug-tracking system built using Java
- Serlet technology. It is currently at version 1.0 beta 8.</para>
+ Servlet technology. It is currently at version 1.0 beta 13.</para>
<para>URL:
<ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink>
</para>
+
+ <para>This section last updated 18 Jan 2003</para>
</section>
- <section id="variant-perforce" xreflabel="Using Perforce to track bugs">
+ <section id="variant-perforce">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used as
@@ -67,9 +80,11 @@
http://www.perforce.com/perforce/technotes/note052.html
</ulink>
</para>
+
+ <para>This section last updated 27 Jul 2002</para>
</section>
- <section id="variant-sourceforge" xreflabel="SourceForge">
+ <section id="variant-sourceforge">
<title>SourceForge</title>
<para>SourceForge is a way of coordinating geographically
@@ -80,6 +95,8 @@
<ulink url="http://www.sourceforge.net">
http://www.sourceforge.net</ulink>
</para>
+
+ <para>This section last updated 27 Jul 2002</para>
</section>
</appendix>
@@ -98,7 +115,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
diff --git a/duplicates.cgi b/duplicates.cgi
index 50affa6df8d25966d8aca3269af3f4c7f7839c30..7172fa6f9974cdf4aba01f182baaa4454de08408 100644
--- a/duplicates.cgi
+++ b/duplicates.cgi
@@ -57,7 +57,7 @@ my $sortby = formvalue("sortby");
my $changedsince = formvalue("changedsince", 7);
my $maxrows = formvalue("maxrows", 100);
my $openonly = formvalue("openonly");
-my $reverse = formvalue("reverse");
+my $reverse = formvalue("reverse") ? 1 : 0;
my $product = formvalue("product");
my $sortvisible = formvalue("sortvisible");
my @buglist = (split(/[:,]/, formvalue("bug_id")));
@@ -147,6 +147,18 @@ my $generic_query = "
# Limit to a single product if requested
$generic_query .= (" product = " . SqlQuote($product) . " AND ") if $product;
+my $origmaxrows = $maxrows;
+detaint_natural($maxrows)
+ || ThrowUserError("The maximum number of rows, '" . html_quote($origmaxrows) .
+ "', must be a positive integer.",
+ "Invalid Max Rows");
+
+my $origchangedsince = $changedsince;
+detaint_natural($changedsince)
+ || ThrowUserError("The 'changed since' value, '" . html_quote($origchangedsince) .
+ "', must be an integer >= 0.",
+ "Invalid Changed Since");
+
my @bugs;
my @bug_ids;
my $loop = 0;
diff --git a/editcomponents.cgi b/editcomponents.cgi
index 4f76593df6679b4c9283577d4176ed75925e9c66..1dc89925f0c6f6d11791e36ee1d9021c97d40683 100755
--- a/editcomponents.cgi
+++ b/editcomponents.cgi
@@ -123,7 +123,7 @@ sub EmitFormElements ($$$$$)
$initialqacontactid ? DBID_to_name ($initialqacontactid) : '');
print " <TH ALIGN=\"right\">Component:</TH>\n";
- print " <TD><INPUT SIZE=64 MAXLENGTH=255 NAME=\"component\" VALUE=\"" .
+ print " <TD><INPUT SIZE=64 MAXLENGTH=50 NAME=\"component\" VALUE=\"" .
value_quote($component) . "\">\n";
print " <INPUT TYPE=HIDDEN NAME=\"product\" VALUE=\"" .
value_quote($product) . "\"></TD>\n";
@@ -385,6 +385,11 @@ if ($action eq 'new') {
PutTrailer($localtrailer);
exit;
}
+ if (length($component) > 50) {
+ print "Sorry, the name of a component is limited to 50 characters.";
+ PutTrailer($localtrailer);
+ exit;
+ }
my $description = trim($::FORM{description} || '');
@@ -709,6 +714,12 @@ if ($action eq 'update') {
CheckComponent($product,$componentold);
+ if (length($component) > 50) {
+ print "Sorry, the name of a component is limited to 50 characters.";
+ PutTrailer($localtrailer);
+ exit;
+ }
+
# Note that the order of this tests is important. If you change
# them, be sure to test for WHERE='$component' or WHERE='$componentold'
diff --git a/editproducts.cgi b/editproducts.cgi
index 932c9a1b388aa7668dd50bf93eec91c58ae24783..8ef01ebe15757da8de7214e214f35006b163e10c 100755
--- a/editproducts.cgi
+++ b/editproducts.cgi
@@ -40,6 +40,7 @@ require "globals.pl";
sub sillyness {
my $zz;
$zz = $::unconfirmedstate;
+ $zz = $::superusergroupset;
}
@@ -687,7 +688,7 @@ if ($action eq 'delete') {
SendSQL("UPDATE profiles " .
"SET groupset = groupset - $bit " .
"WHERE (groupset & $bit) " .
- "AND (groupset != 9223372036854710271)");
+ "AND (groupset != $::superusergroupset)");
print "Users dropped from group '$group_desc'.<BR>\n";
SendSQL("DELETE FROM groups " .
diff --git a/globals.pl b/globals.pl
index c36ffd51e45886f9c84516b64490c5d116f55a69..cbb44b60f8e9f5cebc3a7eda9ce97b07fa29cedc 100644
--- a/globals.pl
+++ b/globals.pl
@@ -98,7 +98,7 @@ $::SIG{TERM} = 'IGNORE';
$::SIG{PIPE} = 'IGNORE';
# Contains the version string for the current running Bugzilla.
-$::param{'version'} = '2.16.2';
+$::param{'version'} = '2.16.3';
$::dontchange = "--do_not_change--";
$::chooseone = "--Choose_one:--";
@@ -517,18 +517,19 @@ sub GenerateVersionTable {
my @list = sort { uc($a) cmp uc($b)} keys(%::versions);
@::legal_product = @list;
- my $tmpname = "data/versioncache.$$";
- open(FID, ">$tmpname") || die "Can't create $tmpname";
+ require File::Temp;
+ my ($fh, $tmpname) = File::Temp::tempfile("versioncache.XXXXX",
+ DIR=>'data');
- print FID "#\n";
- print FID "# DO NOT EDIT!\n";
- print FID "# This file is automatically generated at least once every\n";
- print FID "# hour by the GenerateVersionTable() sub in globals.pl.\n";
- print FID "# Any changes you make will be overwritten.\n";
- print FID "#\n";
+ print $fh "#\n";
+ print $fh "# DO NOT EDIT!\n";
+ print $fh "# This file is automatically generated at least once every\n";
+ print $fh "# hour by the GenerateVersionTable() sub in globals.pl.\n";
+ print $fh "# Any changes you make will be overwritten.\n";
+ print $fh "#\n";
- print FID GenerateCode('@::log_columns');
- print FID GenerateCode('%::versions');
+ print $fh GenerateCode('@::log_columns');
+ print $fh GenerateCode('%::versions');
foreach my $i (@list) {
if (!defined $::components{$i}) {
@@ -536,18 +537,18 @@ sub GenerateVersionTable {
}
}
@::legal_versions = sort {uc($a) cmp uc($b)} keys(%varray);
- print FID GenerateCode('@::legal_versions');
- print FID GenerateCode('%::components');
+ print $fh GenerateCode('@::legal_versions');
+ print $fh GenerateCode('%::components');
@::legal_components = sort {uc($a) cmp uc($b)} keys(%carray);
- print FID GenerateCode('@::legal_components');
+ print $fh GenerateCode('@::legal_components');
foreach my $i('product', 'priority', 'severity', 'platform', 'opsys',
'bug_status', 'resolution') {
- print FID GenerateCode('@::legal_' . $i);
+ print $fh GenerateCode('@::legal_' . $i);
}
- print FID GenerateCode('@::settable_resolution');
- print FID GenerateCode('%::proddesc');
- print FID GenerateCode('@::enterable_products');
- print FID GenerateCode('%::prodmaxvotes');
+ print $fh GenerateCode('@::settable_resolution');
+ print $fh GenerateCode('%::proddesc');
+ print $fh GenerateCode('@::enterable_products');
+ print $fh GenerateCode('%::prodmaxvotes');
if ($dotargetmilestone) {
# reading target milestones in from the database - matthew@zeroknowledge.com
@@ -567,9 +568,9 @@ sub GenerateVersionTable {
}
}
- print FID GenerateCode('%::target_milestone');
- print FID GenerateCode('@::legal_target_milestone');
- print FID GenerateCode('%::milestoneurl');
+ print $fh GenerateCode('%::target_milestone');
+ print $fh GenerateCode('@::legal_target_milestone');
+ print $fh GenerateCode('%::milestoneurl');
}
SendSQL("SELECT id, name FROM keyworddefs ORDER BY name");
@@ -579,11 +580,11 @@ sub GenerateVersionTable {
$name = lc($name);
$::keywordsbyname{$name} = $id;
}
- print FID GenerateCode('@::legal_keywords');
- print FID GenerateCode('%::keywordsbyname');
+ print $fh GenerateCode('@::legal_keywords');
+ print $fh GenerateCode('%::keywordsbyname');
- print FID "1;\n";
- close FID;
+ print $fh "1;\n";
+ close $fh;
rename $tmpname, "data/versioncache" || die "Can't rename $tmpname to versioncache";
ChmodDataFile('data/versioncache', 0666);
}
diff --git a/importxml.pl b/importxml.pl
index 3670609a462f892978c933799063f37e002dc8c8..7401e09c54093cf8b8664cb9cd6f196bbad79f69 100755
--- a/importxml.pl
+++ b/importxml.pl
@@ -229,7 +229,7 @@ if (defined $tree->[1][0]->{'urlbase'}) {
}
-my $bugqty = ($#{@{$tree}->[1]} +1 -3) / 4;
+my $bugqty = ($#{$tree->[1]} +1 -3) / 4;
my $log = "Imported $bugqty bug(s) from $urlbase,\n sent by $exporter.\n\n";
for (my $k=1 ; $k <= $bugqty ; $k++) {
my $cur = $k*4;
@@ -263,7 +263,7 @@ for (my $k=1 ; $k <= $bugqty ; $k++) {
my %bug_fields;
my $err = "";
- for (my $i=3 ; $i < $#{@{$tree}->[1][$cur]} ; $i=$i+4) {
+ for (my $i=3 ; $i < $#{$tree->[1][$cur]} ; $i=$i+4) {
if (defined $multiple_fields{$tree->[1][$cur][$i]}) {
if (defined $bug_fields{$tree->[1][$cur][$i]}) {
$bug_fields{$tree->[1][$cur][$i]} .= " " . $tree->[1][$cur][$i+1][2];
@@ -279,7 +279,7 @@ for (my $k=1 ; $k <= $bugqty ; $k++) {
$err .= "<$tree->[1][$cur][$i]>";
if (defined $tree->[1][$cur][$i+1][3]) {
$err .= "\n";
- for (my $j=3 ; $j < $#{@{$tree}->[1][$cur][$i+1]} ; $j=$j+4) {
+ for (my $j=3 ; $j < $#{$tree->[1][$cur][$i+1]} ; $j=$j+4) {
$err .= " <". $tree->[1][$cur][$i+1][$j] . ">";
$err .= " $tree->[1][$cur][$i+1][$j+1][2] ";
$err .= "</". $tree->[1][$cur][$i+1][$j] . ">\n";
@@ -292,7 +292,7 @@ for (my $k=1 ; $k <= $bugqty ; $k++) {
}
my @long_descs;
- for (my $i=3 ; $i < $#{@{$tree}->[1][$cur]} ; $i=$i+4) {
+ for (my $i=3 ; $i < $#{$tree->[1][$cur]} ; $i=$i+4) {
if ($tree->[1][$cur][$i] =~ /long_desc/) {
my %long_desc;
$long_desc{'who'} = $tree->[1][$cur][$i+1][4][2];
@@ -406,9 +406,9 @@ for (my $k=1 ; $k <= $bugqty ; $k++) {
push (@query, "version");
} else {
push (@query, "version");
- push (@values, SqlQuote(@{$::versions{$product[0]}}->[0]));
+ push (@values, SqlQuote($::versions{$product[0]}->[0]));
$err .= "Unknown version $bug_fields{'version'} in product $product[0]. ";
- $err .= "Setting version to \"@{$::versions{$product[0]}}->[0]\".\n";
+ $err .= "Setting version to \"$::versions{$product[0]}->[0]\".\n";
}
if (defined ($bug_fields{'priority'}) &&
diff --git a/process_bug.cgi b/process_bug.cgi
index 43c926867fd4f8d21e677496806977714513ae17..aa8b668db7d970a1a4f05e1eb6463577a5b0dcde 100755
--- a/process_bug.cgi
+++ b/process_bug.cgi
@@ -304,7 +304,7 @@ sub CheckCanChangeField {
return 1;
}
} elsif ($reporterid eq $whoid || $ownerid eq $whoid ||
- $qacontactid eq $whoid) {
+ (Param('useqacontact') && $qacontactid eq $whoid)) {
return 1;
}
SendSQL("UNLOCK TABLES");
diff --git a/runtests.pl b/runtests.pl
new file mode 100755
index 0000000000000000000000000000000000000000..376a4a1e4717cd5bf222ef6bd45e9f7e064b2207
--- /dev/null
+++ b/runtests.pl
@@ -0,0 +1,42 @@
+#!/usr/bonsaitools/bin/perl -w
+# -*- Mode: perl; indent-tabs-mode: nil -*-
+#
+# The contents of this file are subject to the Mozilla Public
+# License Version 1.1 (the "License"); you may not use this file
+# except in compliance with the License. You may obtain a copy of
+# the License at http://www.mozilla.org/MPL/
+#
+# Software distributed under the License is distributed on an "AS
+# IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+# implied. See the License for the specific language governing
+# rights and limitations under the License.
+#
+# The Original Code is the Bugzilla Bug Tracking System.
+#
+# The Initial Developer of the Original Code is Mike Norton.
+# Portions created by the Initial Developer are Copyright (C) 2002
+# the Initial Developer. All Rights Reserved.
+#
+# Contributor(s):
+#
+
+# Make it harder for us to do dangerous things in Perl.
+use diagnostics;
+use strict;
+
+use Test::Harness qw(&runtests $verbose);
+
+$verbose = 0;
+my $onlytest = "";
+
+foreach (@ARGV) {
+ if (/^(?:-v|--verbose)$/) {
+ $verbose = 1;
+ }
+ else {
+ $onlytest = $_;
+ }
+}
+
+runtests(glob("t/$onlytest*.t"));
+
diff --git a/showdependencygraph.cgi b/showdependencygraph.cgi
index 857075cb60f118c8e5c19ddef81b88feedee193d..57098c783801727d562bdc3771de24c50af26c99 100755
--- a/showdependencygraph.cgi
+++ b/showdependencygraph.cgi
@@ -26,6 +26,8 @@ use strict;
use lib qw(.);
+use File::Temp;
+
require "CGI.pl";
ConnectToDatabase();
@@ -48,7 +50,8 @@ sub CreateImagemap {
$default = qq{<area shape="default" href="$1">\n};
}
if ($line =~ /^rectangle \((.*),(.*)\) \((.*),(.*)\) (http[^ ]*)(.*)?$/) {
- $map .= qq{<area name="bug$6" shape="rect" href="$5" coords="$1,$4,$3,$2">\n};
+ my $bugsummary = value_quote($6);
+ $map .= qq{<area alt="bug$bugsummary" name="bug$bugsummary" shape="rect" href="$5" coords="$1,$4,$3,$2">\n};
}
}
close MAP;
@@ -58,11 +61,11 @@ sub CreateImagemap {
}
sub AddLink {
- my ($blocked, $dependson) = (@_);
+ my ($blocked, $dependson, $fh) = (@_);
my $key = "$blocked,$dependson";
if (!exists $edgesdone{$key}) {
$edgesdone{$key} = 1;
- print DOT "$blocked -> $dependson\n";
+ print $fh "$blocked -> $dependson\n";
$seen{$blocked} = 1;
$seen{$dependson} = 1;
}
@@ -75,12 +78,13 @@ if (!defined($::FORM{'id'}) && !defined($::FORM{'doall'})) {
exit;
}
-my $filename = "data/webdot/$$.dot";
+my ($fh, $filename) = File::Temp::tempfile("XXXXXXXXXX",
+ SUFFIX => '.dot',
+ DIR => "data/webdot");
my $urlbase = Param('urlbase');
-open(DOT, ">$filename") || die "Can't create $filename";
-print DOT "digraph G {";
-print DOT qq{
+print $fh "digraph G {";
+print $fh qq{
graph [URL="${urlbase}query.cgi", rankdir=$::FORM{'rankdir'}, size="64,64"]
node [URL="${urlbase}show_bug.cgi?id=\\N", style=filled, color=lightgrey]
};
@@ -92,7 +96,7 @@ if ($::FORM{'doall'}) {
while (MoreSQLData()) {
my ($blocked, $dependson) = FetchSQLData();
- AddLink($blocked, $dependson);
+ AddLink($blocked, $dependson, $fh);
}
} else {
foreach my $i (split('[\s,]+', $::FORM{'id'})) {
@@ -116,7 +120,7 @@ if ($::FORM{'doall'}) {
push @stack, $dependson;
}
- AddLink($blocked, $dependson);
+ AddLink($blocked, $dependson, $fh);
}
}
@@ -156,15 +160,15 @@ foreach my $k (keys(%seen)) {
}
if (@params) {
- print DOT "$k [" . join(',', @params) . "]\n";
+ print $fh "$k [" . join(',', @params) . "]\n";
} else {
- print DOT "$k\n";
+ print $fh "$k\n";
}
}
-print DOT "}\n";
-close DOT;
+print $fh "}\n";
+close $fh;
chmod 0777, $filename;
@@ -177,11 +181,23 @@ if ($webdotbase =~ /^https?:/) {
$vars->{'map_url'} = $url . ".map";
} else {
# Local dot installation
- my $pngfilename = "data/webdot/$$.png";
- my $mapfilename = "data/webdot/$$.map";
- system("$webdotbase","-Tpng","-o","$pngfilename","$filename");
+ my $dotfh;
+ my ($pngfh, $pngfilename) = File::Temp::tempfile("XXXXXXXXXX",
+ SUFFIX => '.png',
+ DIR => 'data/webdot');
+ open (DOT, '-|') or exec ($webdotbase, "-Tpng", $filename);
+ print $pngfh $_ while <DOT>;
+ close DOT;
+ close $pngfh;
$vars->{'image_url'} = $pngfilename;
- system("$webdotbase","-Tismap","-o","$mapfilename","$filename");
+
+ my ($mapfh, $mapfilename) = File::Temp::tempfile("XXXXXXXXXX",
+ SUFFIX => '.map',
+ DIR => 'data/webdot');
+ open (DOT, '-|') or exec ($webdotbase, "-Tismap", $filename);
+ print $mapfh $_ while <DOT>;
+ close DOT;
+ close $mapfh;
$vars->{'image_map'} = CreateImagemap($mapfilename);
}
diff --git a/t/004template.t b/t/004template.t
index 730aafc8626e1d97eb149a1904bdd67481a6e956..8429b774f8e80697d5548c85ed70224367f7d9b2 100644
--- a/t/004template.t
+++ b/t/004template.t
@@ -17,9 +17,10 @@
# Copyright (C) 2001 Jacob Steenhagen. All
# Rights Reserved.
#
-# Contributor(s): Jacob Steenhagen <jake@acutex.net>
+# Contributor(s): Jacob Steenhagen <jake@bugzilla.org>
# Zach Lipton <zach@zachlipton.com>
# David D. Kilzer <ddkilzer@kilzer.net>
+# Tobias Burnus <burnus@net-b.de>
#
#################
@@ -37,8 +38,7 @@ use CGI qw(-no_debug);
use File::Spec 0.82;
use Template;
-use Test::More tests => ( scalar(@Support::Templates::referenced_files)
- + scalar(@Support::Templates::actual_files) * 2);
+use Test::More tests => ( scalar(@referenced_files) + $num_actual_files * 2 );
# Capture the TESTOUT from Test::More or Test::Builder for printing errors.
# This will handle verbosity for us automatically.
@@ -54,73 +54,84 @@ my $fh;
}
}
-my $include_path = $Support::Templates::include_path;
+# Checks whether one of the passed files exists
+sub existOnce {
+ foreach my $file (@_) {
+ return $file if -e $file;
+ }
+ return 0;
+}
# Check to make sure all templates that are referenced in
# Bugzilla exist in the proper place.
-foreach my $file(@Support::Templates::referenced_files) {
- my $path = File::Spec->catfile($include_path, $file);
- if (-e $path) {
- ok(1, "$path exists");
- } else {
- ok(0, "$path does not exist --ERROR");
+foreach my $lang (@languages) {
+ foreach my $file (@referenced_files) {
+ my @path = map(File::Spec->catfile($_, $file),
+ split(':', $include_path{$lang}));
+ if (my $path = existOnce(@path)) {
+ ok(1, "$path exists");
+ } else {
+ ok(0, "$file cannot be located --ERROR");
+ print $fh "Looked in:\n " . join("\n ", @path);
+ }
}
}
-# Processes all the templates to make sure they have good syntax
-my $template = Template->new(
-{
- INCLUDE_PATH => $include_path ,
- # Need to define filters used in the codebase, they don't
- # actually have to function in this test, just be defined.
- # See globals.pl for the actual codebase definitions.
- FILTERS =>
+foreach my $include_path (@include_paths) {
+ # Processes all the templates to make sure they have good syntax
+ my $provider = Template::Provider->new(
{
- html_linebreak => sub { return $_; },
- js => sub { return $_ } ,
- strike => sub { return $_ } ,
- url_quote => sub { return $_ } ,
- },
-}
-);
-
-open SAVEOUT, ">&STDOUT"; # stash the original output stream
-open SAVEERR, ">&STDERR";
-open STDOUT, "> /dev/null"; # discard all output
-open STDERR, "> /dev/null";
-foreach my $file(@Support::Templates::actual_files) {
- my $path = File::Spec->catfile($include_path, $file);
- if (-e $path) {
- if ($template->process($file)) {
- ok(1, "$file syntax ok");
+ INCLUDE_PATH => $include_path ,
+ # Need to define filters used in the codebase, they don't
+ # actually have to function in this test, just be defined.
+ # See globals.pl for the actual codebase definitions.
+ FILTERS =>
+ {
+ html_linebreak => sub { return $_; },
+ js => sub { return $_ } ,
+ strike => sub { return $_ } ,
+ url_quote => sub { return $_ } ,
+ xml => sub { return $_ } ,
+ quoteUrls => sub { return $_ } ,
+ bug_link => [ sub { return sub { return $_; } }, 1] ,
+ csv => sub { return $_ } ,
+ time => sub { return $_ } ,
+ },
+ }
+ );
+
+ foreach my $file (@{$actual_files{$include_path}}) {
+ my $path = File::Spec->catfile($include_path, $file);
+ if (-e $path) {
+ my ($data, $err) = $provider->fetch($file);
+
+ if (!$err) {
+ ok(1, "$file syntax ok");
+ }
+ else {
+ ok(0, "$file has bad syntax --ERROR");
+ print $fh $data . "\n";
+ }
}
else {
- ok(0, "$file has bad syntax --ERROR");
- print $fh $template->error() . "\n";
+ ok(1, "$path doesn't exist, skipping test");
}
}
- else {
- ok(1, "$path doesn't exist, skipping test");
- }
-}
-open STDOUT, ">&SAVEOUT"; # redirect back to original stream
-open STDERR, ">&SAVEERR";
-close SAVEOUT;
-close SAVEERR;
-
-# check to see that all templates have a version string:
-
-foreach my $file(@Support::Templates::actual_files) {
- my $path = File::Spec->catfile($include_path, $file);
- open(TMPL, $path);
- my $firstline = <TMPL>;
- if ($firstline =~ /\d+\.\d+\@[\w\.-]+/) {
- ok(1,"$file has a version string");
- } else {
- ok(0,"$file does not have a version string --ERROR");
+
+ # check to see that all templates have a version string:
+
+ foreach my $file (@{$actual_files{$include_path}}) {
+ my $path = File::Spec->catfile($include_path, $file);
+ open(TMPL, $path);
+ my $firstline = <TMPL>;
+ if ($firstline =~ /\d+\.\d+\@[\w\.-]+/) {
+ ok(1,"$file has a version string");
+ } else {
+ ok(0,"$file does not have a version string --ERROR");
+ }
+ close(TMPL);
}
- close(TMPL);
}
exit 0;
diff --git a/t/008filter.t b/t/008filter.t
new file mode 100644
index 0000000000000000000000000000000000000000..10d7fc62c2028ed9e8a1c6756ea78a135fa81559
--- /dev/null
+++ b/t/008filter.t
@@ -0,0 +1,182 @@
+# -*- Mode: perl; indent-tabs-mode: nil -*-
+#
+# The contents of this file are subject to the Mozilla Public
+# License Version 1.1 (the "License"); you may not use this file
+# except in compliance with the License. You may obtain a copy of
+# the License at http://www.mozilla.org/MPL/
+#
+# Software distributed under the License is distributed on an "AS
+# IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+# implied. See the License for the specific language governing
+# rights and limitations under the License.
+#
+# The Original Code are the Bugzilla tests.
+#
+# The Initial Developer of the Original Code is Jacob Steenhagen.
+# Portions created by Jacob Steenhagen are
+# Copyright (C) 2001 Jacob Steenhagen. All
+# Rights Reserved.
+#
+# Contributor(s): Gervase Markham <gerv@gerv.net>
+
+#################
+#Bugzilla Test 8#
+#####filter######
+
+# This test scans all our templates for every directive. Having eliminated
+# those which cannot possibly cause XSS problems, it then checks the rest
+# against the safe list stored in the filterexceptions.pl file.
+
+# Sample exploit code: '>"><script>alert('Oh dear...')</script>
+
+use strict;
+use lib 't';
+
+use vars qw(%safe);
+
+use Support::Templates;
+use File::Spec 0.82;
+use Test::More tests => $Support::Templates::num_actual_files;
+use Cwd;
+
+# Undefine the record separator so we can read in whole files at once
+my $oldrecsep = $/;
+$/ = undef;
+my $topdir = cwd;
+
+foreach my $path (@Support::Templates::include_paths) {
+ $path =~ m|template/([^/]+)/|;
+ my $lang = $1;
+ chdir $topdir; # absolute path
+ my @testitems = Support::Templates::find_actual_files($path);
+
+ next unless @testitems;
+
+ # Some people require this, others don't. No-one knows why.
+ chdir $path; # relative path
+
+ # We load a %safe list of acceptable exceptions.
+ if (!-r "filterexceptions.pl") {
+ ok(0, "$path has templates but no filterexceptions.pl file. --ERROR");
+ next;
+ }
+ else {
+ do "filterexceptions.pl";
+ }
+
+ # We preprocess the %safe hash of lists into a hash of hashes. This allows
+ # us to flag which members were not found, and report that as a warning,
+ # thereby keeping the lists clean.
+ foreach my $file (keys %safe) {
+ my $list = $safe{$file};
+ $safe{$file} = {};
+ foreach my $directive (@$list) {
+ $safe{$file}{$directive} = 0;
+ }
+ }
+
+ foreach my $file (@testitems) {
+ # There are some files we don't check, because there is no need to
+ # filter their contents due to their content-type.
+ if ($file =~ /\.(txt|png)\.tmpl$/) {
+ ok(1, "($lang) $file is filter-safe");
+ next;
+ }
+
+ # Read the entire file into a string
+ open (FILE, "<$file") || die "Can't open $file: $!\n";
+ my $slurp = <FILE>;
+ close (FILE);
+
+ my @unfiltered;
+
+ # /g means we execute this loop for every match
+ # /s means we ignore linefeeds in the regexp matches
+ while ($slurp =~ /\[%(.*?)%\]/gs) {
+ my $directive = $1;
+
+ my @lineno = ($` =~ m/\n/gs);
+ my $lineno = scalar(@lineno) + 1;
+
+ # Comments
+ next if $directive =~ /^[+-]?#/;
+
+ # Remove any leading/trailing + or - and whitespace.
+ $directive =~ s/^[+-]?\s*//;
+ $directive =~ s/\s*[+-]?$//;
+
+ # Directives
+ next if $directive =~ /^(IF|END|UNLESS|FOREACH|PROCESS|INCLUDE|
+ BLOCK|USE|ELSE|NEXT|LAST|DEFAULT|FLUSH|
+ ELSIF|SET|SWITCH|CASE)/x;
+
+ # Simple assignments
+ next if $directive =~ /^[\w\.\$]+\s+=\s+/;
+
+ # Conditional literals with either sort of quotes
+ # There must be no $ in the string for it to be a literal
+ next if $directive =~ /^(["'])[^\$]*[^\\]\1/;
+
+ # Special values always used for numbers
+ next if $directive =~ /^[ijkn]$/;
+ next if $directive =~ /^count$/;
+
+ # Params
+ next if $directive =~ /^Param\(/;
+
+ # Other functions guaranteed to return OK output
+ next if $directive =~ /^(time2str|GetBugLink)\(/;
+
+ # Safe Template Toolkit virtual methods
+ next if $directive =~ /\.(size)$/;
+
+ # Special Template Toolkit loop variable
+ next if $directive =~ /^loop\.(index|count)$/;
+
+ # Things which are already filtered
+ # Note: If a single directive prints two things, and only one is
+ # filtered, we may not catch that case.
+ next if $directive =~ /FILTER\ (html|csv|js|url_quote|quoteUrls|
+ time|uri|xml)/x;
+
+ # Exclude those on the nofilter list
+ if (defined($safe{$file}{$directive})) {
+ $safe{$file}{$directive}++;
+ next;
+ };
+
+ # This intentionally makes no effort to eliminate duplicates; to do
+ # so would merely make it more likely that the user would not
+ # escape all instances when attempting to correct an error.
+ push(@unfiltered, "$lineno:$directive");
+ }
+
+ my $fullpath = File::Spec->catfile($path, $file);
+
+ if (@unfiltered) {
+ my $uflist = join("\n ", @unfiltered);
+ ok(0, "($lang) $fullpath has unfiltered directives:\n $uflist\n--ERROR");
+ }
+ else {
+ # Find any members of the exclusion list which were not found
+ my @notfound;
+ foreach my $directive (keys %{$safe{$file}}) {
+ push(@notfound, $directive) if ($safe{$file}{$directive} == 0);
+ }
+
+ if (@notfound) {
+ my $nflist = join("\n ", @notfound);
+ ok(0, "($lang) $fullpath - FEL has extra members:\n $nflist\n" .
+ "--WARNING");
+ }
+ else {
+ # Don't use the full path here - it's too long and unwieldy.
+ ok(1, "($lang) $file is filter-safe");
+ }
+ }
+ }
+}
+
+$/ = $oldrecsep;
+
+exit 0;
diff --git a/t/CVS/Entries b/t/CVS/Entries
index 66c9c40cde50c518d70ea7f2e01d6b1e122b0393..ffb1f5a080334a96784ac755874fae004d65f301 100644
--- a/t/CVS/Entries
+++ b/t/CVS/Entries
@@ -1,6 +1,7 @@
-/001compile.t/1.8/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_2
-/002goodperl.t/1.7/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_2
-/003safesys.t/1.4/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_2
-/004template.t/1.15.2.2/Fri Jul 19 14:04:12 2002//TBUGZILLA-2_16_2
-/005no_tabs.t/1.10/Wed May 8 23:49:32 2002//TBUGZILLA-2_16_2
+/001compile.t/1.8/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_3
+/002goodperl.t/1.7/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_3
+/003safesys.t/1.4/Wed May 8 23:49:31 2002//TBUGZILLA-2_16_3
+/004template.t/1.15.2.3/Mon Feb 17 02:35:54 2003//TBUGZILLA-2_16_3
+/005no_tabs.t/1.10/Wed May 8 23:49:32 2002//TBUGZILLA-2_16_3
+/008filter.t/1.1.2.1/Thu Apr 24 20:45:11 2003//TBUGZILLA-2_16_3
D/Support////
diff --git a/t/CVS/Tag b/t/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/t/CVS/Tag
+++ b/t/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/t/Support/CVS/Entries b/t/Support/CVS/Entries
index 75989cddd1fdc81a9b731534b5e5b2a0b9133f5e..10824cbbcd85c855271dccbf46bac75be9ae0852 100644
--- a/t/Support/CVS/Entries
+++ b/t/Support/CVS/Entries
@@ -1,4 +1,4 @@
-/Files.pm/1.9/Wed Oct 31 01:06:31 2001//TBUGZILLA-2_16_2
-/Systemexec.pm/1.2/Fri Oct 19 22:39:51 2001//TBUGZILLA-2_16_2
-/Templates.pm/1.9/Tue May 7 09:45:32 2002//TBUGZILLA-2_16_2
+/Files.pm/1.9.6.2/Mon Feb 17 02:50:58 2003//TBUGZILLA-2_16_3
+/Systemexec.pm/1.2/Fri Oct 19 22:39:51 2001//TBUGZILLA-2_16_3
+/Templates.pm/1.9.2.1/Mon Feb 17 02:35:57 2003//TBUGZILLA-2_16_3
D
diff --git a/t/Support/CVS/Tag b/t/Support/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/t/Support/CVS/Tag
+++ b/t/Support/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/t/Support/Files.pm b/t/Support/Files.pm
index 63c55ce86bef133d3e9b73b89a002fca395f468a..700dcbfd7f7f5b234f55d91f47e6932eb58d933f 100644
--- a/t/Support/Files.pm
+++ b/t/Support/Files.pm
@@ -18,49 +18,60 @@
# Rights Reserved.
#
# Contributor(s): Zach Lipton <zach@zachlipton.com>
-#
-# Alternatively, the contents of this file may be used under the
-# terms of the GNU General Public License Version 2 or later (the
-# "GPL"), in which case the provisions of the GPL are applicable
-# instead of those above. If you wish to allow use of your
-# version of this file only under the terms of the GPL and not to
-# allow others to use your version of this file under the MPL,
-# indicate your decision by deleting the provisions above and
-# replace them with the notice and other provisions required by
-# the GPL. If you do not delete the provisions above, a recipient
-# may use your version of this file under either the MPL or the
-# GPL.
-#
+# Joel Peshkin <bugreport@peshkin.net>
+
package Support::Files;
-@additional_files = ('syncshadowdb','processmail');
-@exclude_files = ('importxml.pl');
+# exclude_deps is a hash of arrays listing the files to be excluded
+# if a module is not available
+#
+@additional_files = ('processmail','syncshadowdb');
+%exclude_deps = (
+ 'XML::Parser' => ['importxml.pl'],
+);
+
+# XXX - this file should be rewritten to use File::Find or similar
$file = '*';
-@files = glob($file);
+@files = (glob($file), glob('Bugzilla/*.pm'));
+
+sub have_pkg {
+ my ($pkg) = @_;
+ my ($msg, $vnum, $vstr);
+ no strict 'refs';
+ eval { my $p; ($p = $pkg . ".pm") =~ s!::!/!g; require $p; };
+ return !($@);
+}
+
+@exclude_files = ();
+foreach $dep (keys(%exclude_deps)) {
+ if (!have_pkg($dep)) {
+ push @exclude_files, @{$exclude_deps{$dep}};
+ }
+}
sub isTestingFile {
- my ($file) = @_;
- my $exclude;
- foreach $exclude (@exclude_files) {
+ my ($file) = @_;
+ my $exclude;
+ foreach $exclude (@exclude_files) {
if ($file eq $exclude) { return undef; } # get rid of excluded files.
- }
+ }
- if ($file =~ /\.cgi$|\.pl$|\.pm$/) {
- return 1;
- }
- my $additional;
- foreach $additional (@additional_files) {
- if ($file eq $additional) { return 1; }
- }
- return undef;
+ if ($file =~ /\.cgi$|\.pl$|\.pm$/) {
+ return 1;
+ }
+ my $additional;
+ foreach $additional (@additional_files) {
+ if ($file eq $additional) { return 1; }
+ }
+ return undef;
}
foreach $currentfile (@files) {
- if (isTestingFile($currentfile)) {
- push(@testitems,$currentfile);
- }
+ if (isTestingFile($currentfile)) {
+ push(@testitems,$currentfile);
+ }
}
diff --git a/t/Support/Templates.pm b/t/Support/Templates.pm
index 07f46f7004c2c4a7d7bb7b3d3b93ae28c772ef77..e9056539249ae313c6cbc9ef370102c5622f771a 100644
--- a/t/Support/Templates.pm
+++ b/t/Support/Templates.pm
@@ -17,28 +17,70 @@
# Copyright (C) 2001 Jacob Steenhagen. All
# Rights Reserved.
#
-# Contributor(s): Jacob Steenhagen <jake@acutex.net>
+# Contributor(s): Jacob Steenhagen <jake@bugzilla.org>
# David D. Kilzer <ddkilzer@kilzer.net>
+# Tobias Burnus <burnus@net-b.de>
#
package Support::Templates;
-use diagnostics;
use strict;
use lib 't';
-use vars qw($include_path @referenced_files @actual_files);
+use base qw(Exporter);
+@Support::Templates::EXPORT =
+ qw(@languages @include_paths %include_path @referenced_files
+ %actual_files $num_actual_files);
+use vars qw(@languages @include_paths %include_path @referenced_files
+ %actual_files $num_actual_files);
use Support::Files;
use File::Find;
use File::Spec 0.82;
-# Note that $include_path is assumed to only contain ONE path, not
-# a list of colon-separated paths.
-$include_path = File::Spec->catdir('template', 'en', 'default');
+# The available template languages
+@languages = ();
+
+# The colon separated includepath per language
+%include_path = ();
+
+# All include paths
+@include_paths = ();
+
+# Files which are referenced in the cgi files
@referenced_files = ();
-@actual_files = ();
+
+# All files sorted by include_path
+%actual_files = ();
+
+# total number of actual_files
+$num_actual_files = 0;
+
+# Scan for the template available languages and include paths
+{
+ opendir(DIR, "template") || die "Can't open 'template': $!";
+ my @files = grep { /^[a-z-]+$/i } readdir(DIR);
+ closedir DIR;
+
+ foreach my $langdir (@files) {
+ next if($langdir =~ /^CVS$/i);
+
+ my $path = File::Spec->catdir('template', $langdir, 'custom');
+ my @dirs = ();
+ push(@dirs, $path) if(-d $path);
+ $path = File::Spec->catdir('template', $langdir, 'default');
+ push(@dirs, $path) if(-d $path);
+
+ next if(scalar(@dirs) == 0);
+ push(@languages, $langdir);
+ push(@include_paths, @dirs);
+ $include_path{$langdir} = join(":",@dirs);
+ }
+}
+
+
+my @files;
# Local subroutine used with File::Find
sub find_templates {
@@ -60,13 +102,23 @@ sub find_templates {
$filename = $_;
}
- push(@actual_files, $filename);
+ push(@files, $filename);
}
}
-# Scan the template include path for templates then put them in
-# in the @actual_files array to be used by various tests.
-map(find(\&find_templates, $_), split(':', $include_path));
+# Scan the given template include path for templates
+sub find_actual_files {
+ my $include_path = $_[0];
+ @files = ();
+ find(\&find_templates, $include_path);
+ return @files;
+}
+
+
+foreach my $include_path (@include_paths) {
+ $actual_files{$include_path} = [ find_actual_files($include_path) ];
+ $num_actual_files += scalar(@{$actual_files{$include_path}});
+}
# Scan Bugzilla's perl code looking for templates used and put them
# in the @referenced_files array to be used by the 004template.t test.
diff --git a/template/CVS/Entries b/template/CVS/Entries
index 2efd35eb7971fd4653885881ba086b851f94fab4..1d01be73abf1de659f6a70f267de8edef706a475 100644
--- a/template/CVS/Entries
+++ b/template/CVS/Entries
@@ -1,2 +1,2 @@
-/.cvsignore/1.3/Tue May 7 21:33:53 2002//TBUGZILLA-2_16_2
+/.cvsignore/1.3/Tue May 7 21:33:53 2002//TBUGZILLA-2_16_3
D/en////
diff --git a/template/CVS/Tag b/template/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/CVS/Tag
+++ b/template/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/CVS/Entries b/template/en/CVS/Entries
index 6ba79b7461d5d1665d9c21448fe7a3521bcdf349..0ca12bdefa714e0a6b6f32ae64846a4368901978 100644
--- a/template/en/CVS/Entries
+++ b/template/en/CVS/Entries
@@ -1,2 +1,2 @@
-/.cvsignore/1.1/Wed Apr 24 07:29:49 2002//TBUGZILLA-2_16_2
+/.cvsignore/1.1/Wed Apr 24 07:29:49 2002//TBUGZILLA-2_16_3
D/default////
diff --git a/template/en/CVS/Tag b/template/en/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/CVS/Tag
+++ b/template/en/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/CVS/Entries b/template/en/default/CVS/Entries
index c3dd9edfdee1fa390d2bc484f88c359f2fab2054..161b35b26638314ef2fe94a801e1b1404b32b09e 100644
--- a/template/en/default/CVS/Entries
+++ b/template/en/default/CVS/Entries
@@ -1,5 +1,6 @@
-/index.html.tmpl/1.4.2.2/Sun Jun 23 17:36:05 2002//TBUGZILLA-2_16_2
-/sidebar.xul.tmpl/1.3.2.1/Wed Jul 10 00:05:58 2002//TBUGZILLA-2_16_2
+/filterexceptions.pl/1.1.2.1/Thu Apr 24 20:45:15 2003//TBUGZILLA-2_16_3
+/index.html.tmpl/1.4.2.2/Sun Jun 23 17:36:05 2002//TBUGZILLA-2_16_3
+/sidebar.xul.tmpl/1.3.2.1/Wed Jul 10 00:05:58 2002//TBUGZILLA-2_16_3
D/account////
D/admin////
D/attachment////
diff --git a/template/en/default/CVS/Tag b/template/en/default/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/CVS/Tag
+++ b/template/en/default/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/account/CVS/Entries b/template/en/default/account/CVS/Entries
index 7f45467b3456f69e32feafa4829170e45d71020f..185c7089357faea0df207a4dc1882b52ecdb4a0c 100644
--- a/template/en/default/account/CVS/Entries
+++ b/template/en/default/account/CVS/Entries
@@ -1,7 +1,7 @@
-/cancel-token.txt.tmpl/1.1/Thu Apr 18 18:56:15 2002//TBUGZILLA-2_16_2
-/create.html.tmpl/1.3/Tue Apr 23 23:27:32 2002//TBUGZILLA-2_16_2
-/created.html.tmpl/1.4/Mon May 6 19:16:50 2002//TBUGZILLA-2_16_2
-/exists.html.tmpl/1.4.2.1/Thu May 23 08:13:49 2002//TBUGZILLA-2_16_2
+/cancel-token.txt.tmpl/1.1/Thu Apr 18 18:56:15 2002//TBUGZILLA-2_16_3
+/create.html.tmpl/1.3/Tue Apr 23 23:27:32 2002//TBUGZILLA-2_16_3
+/created.html.tmpl/1.4/Mon May 6 19:16:50 2002//TBUGZILLA-2_16_3
+/exists.html.tmpl/1.4.2.1/Thu May 23 08:13:49 2002//TBUGZILLA-2_16_3
D/email////
D/password////
D/prefs////
diff --git a/template/en/default/account/CVS/Entries.Log b/template/en/default/account/CVS/Entries.Log
new file mode 100644
index 0000000000000000000000000000000000000000..4191cb47c2d027152164e1b8343704ea5c8ed56c
--- /dev/null
+++ b/template/en/default/account/CVS/Entries.Log
@@ -0,0 +1,2 @@
+A D/auth////
+R D/auth////
diff --git a/template/en/default/account/CVS/Tag b/template/en/default/account/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/account/CVS/Tag
+++ b/template/en/default/account/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/account/email/CVS/Entries b/template/en/default/account/email/CVS/Entries
index bf0afba57f9c6c681ec29b24b97a01cbdfa69724..fc7a2ba45b8c2230726e475ce68fcda94a40540a 100644
--- a/template/en/default/account/email/CVS/Entries
+++ b/template/en/default/account/email/CVS/Entries
@@ -1,4 +1,4 @@
-/change-new.txt.tmpl/1.3/Fri May 3 06:37:42 2002//TBUGZILLA-2_16_2
-/change-old.txt.tmpl/1.4/Mon May 6 19:16:46 2002//TBUGZILLA-2_16_2
-/confirm.html.tmpl/1.4.2.1/Thu May 23 08:13:51 2002//TBUGZILLA-2_16_2
+/change-new.txt.tmpl/1.3/Fri May 3 06:37:42 2002//TBUGZILLA-2_16_3
+/change-old.txt.tmpl/1.4/Mon May 6 19:16:46 2002//TBUGZILLA-2_16_3
+/confirm.html.tmpl/1.4.2.1/Thu May 23 08:13:51 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/account/email/CVS/Tag b/template/en/default/account/email/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/account/email/CVS/Tag
+++ b/template/en/default/account/email/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/account/password/CVS/Entries b/template/en/default/account/password/CVS/Entries
index 2c9efbe90487dff0654b5ee64bfaddcdc8920635..c188ed47689697ca3069dd0a71fa81e19206e0b6 100644
--- a/template/en/default/account/password/CVS/Entries
+++ b/template/en/default/account/password/CVS/Entries
@@ -1,3 +1,3 @@
-/forgotten-password.txt.tmpl/1.2/Fri May 3 06:37:47 2002//TBUGZILLA-2_16_2
-/set-forgotten-password.html.tmpl/1.3.2.1/Thu May 23 08:13:56 2002//TBUGZILLA-2_16_2
+/forgotten-password.txt.tmpl/1.2/Fri May 3 06:37:47 2002//TBUGZILLA-2_16_3
+/set-forgotten-password.html.tmpl/1.3.2.1/Thu May 23 08:13:56 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/account/password/CVS/Tag b/template/en/default/account/password/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/account/password/CVS/Tag
+++ b/template/en/default/account/password/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/account/prefs/CVS/Entries b/template/en/default/account/prefs/CVS/Entries
index c568a6b15c9c7a067992000d06cae5fe1dfa8b51..9b942a7028dd705247e0c8e1e37f9626210b8c3a 100644
--- a/template/en/default/account/prefs/CVS/Entries
+++ b/template/en/default/account/prefs/CVS/Entries
@@ -1,6 +1,6 @@
-/account.html.tmpl/1.1.2.1/Thu May 23 08:13:58 2002//TBUGZILLA-2_16_2
-/email.html.tmpl/1.1.2.3/Wed Jul 17 18:28:37 2002//TBUGZILLA-2_16_2
-/footer.html.tmpl/1.1.2.1/Thu May 23 08:13:59 2002//TBUGZILLA-2_16_2
-/permissions.html.tmpl/1.1.2.1/Thu May 23 08:13:59 2002//TBUGZILLA-2_16_2
-/prefs.html.tmpl/1.4.2.2/Tue Aug 13 06:57:03 2002//TBUGZILLA-2_16_2
+/account.html.tmpl/1.1.2.1/Thu May 23 08:13:58 2002//TBUGZILLA-2_16_3
+/email.html.tmpl/1.1.2.3/Wed Jul 17 18:28:37 2002//TBUGZILLA-2_16_3
+/footer.html.tmpl/1.1.2.1/Thu May 23 08:13:59 2002//TBUGZILLA-2_16_3
+/permissions.html.tmpl/1.1.2.1/Thu May 23 08:13:59 2002//TBUGZILLA-2_16_3
+/prefs.html.tmpl/1.4.2.2/Tue Aug 13 06:57:03 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/account/prefs/CVS/Tag b/template/en/default/account/prefs/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/account/prefs/CVS/Tag
+++ b/template/en/default/account/prefs/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/admin/CVS/Tag b/template/en/default/admin/CVS/Tag
index 96c74837dccac49d7268476419d9ea5c1fbd44e6..93d39262b22ec4837a3343d7bfae5b6148f29cf8 100644
--- a/template/en/default/admin/CVS/Tag
+++ b/template/en/default/admin/CVS/Tag
@@ -1 +1 @@
-TBUGZILLA-2_16_2
+TBUGZILLA-2_16_3
diff --git a/template/en/default/admin/attachstatus/CVS/Entries b/template/en/default/admin/attachstatus/CVS/Entries
index b7e97347c8d01b42b9948b7c80e60f434a0ec272..e10dd1d6ad9c62527a8beeda90e6bc60033c3c77 100644
--- a/template/en/default/admin/attachstatus/CVS/Entries
+++ b/template/en/default/admin/attachstatus/CVS/Entries
@@ -1,5 +1,5 @@
-/create.html.tmpl/1.3/Tue Apr 23 23:27:26 2002//TBUGZILLA-2_16_2
-/delete.html.tmpl/1.3/Tue Apr 23 23:27:25 2002//TBUGZILLA-2_16_2
-/edit.html.tmpl/1.4/Mon May 6 19:16:58 2002//TBUGZILLA-2_16_2
-/list.html.tmpl/1.4/Mon May 6 19:16:58 2002//TBUGZILLA-2_16_2
+/create.html.tmpl/1.3/Tue Apr 23 23:27:26 2002//TBUGZILLA-2_16_3
+/delete.html.tmpl/1.3/Tue Apr 23 23:27:25 2002//TBUGZILLA-2_16_3
+/edit.html.tmpl/1.4/Mon May 6 19:16:58 2002//TBUGZILLA-2_16_3
+/list.html.tmpl/1.4/Mon May 6 19:16:58 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/admin/attachstatus/CVS/Tag b/template/en/default/admin/attachstatus/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/admin/attachstatus/CVS/Tag
+++ b/template/en/default/admin/attachstatus/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/attachment/CVS/Entries b/template/en/default/attachment/CVS/Entries
index 02dc704753b05720ec6add3ef6b3501599bbdd43..5a11241b012ecd01ad02894803f96c276bcad77f 100644
--- a/template/en/default/attachment/CVS/Entries
+++ b/template/en/default/attachment/CVS/Entries
@@ -1,8 +1,8 @@
-/content-types.html.tmpl/1.1/Thu Apr 18 18:56:29 2002//TBUGZILLA-2_16_2
-/create.html.tmpl/1.5.2.2/Tue Jun 4 22:56:38 2002//TBUGZILLA-2_16_2
-/created.html.tmpl/1.4.2.1/Thu May 23 08:14:02 2002//TBUGZILLA-2_16_2
-/edit.html.tmpl/1.4.2.2/Tue Jun 11 09:27:21 2002//TBUGZILLA-2_16_2
-/list.html.tmpl/1.1/Thu Apr 18 18:56:30 2002//TBUGZILLA-2_16_2
-/show-multiple.html.tmpl/1.3.2.1/Thu May 23 08:14:03 2002//TBUGZILLA-2_16_2
-/updated.html.tmpl/1.4.2.1/Thu May 23 08:14:03 2002//TBUGZILLA-2_16_2
+/content-types.html.tmpl/1.1/Thu Apr 18 18:56:29 2002//TBUGZILLA-2_16_3
+/create.html.tmpl/1.5.2.2/Tue Jun 4 22:56:38 2002//TBUGZILLA-2_16_3
+/created.html.tmpl/1.4.2.1/Thu May 23 08:14:02 2002//TBUGZILLA-2_16_3
+/edit.html.tmpl/1.4.2.3/Thu Apr 24 20:45:18 2003//TBUGZILLA-2_16_3
+/list.html.tmpl/1.1/Thu Apr 18 18:56:30 2002//TBUGZILLA-2_16_3
+/show-multiple.html.tmpl/1.3.2.1/Thu May 23 08:14:03 2002//TBUGZILLA-2_16_3
+/updated.html.tmpl/1.4.2.1/Thu May 23 08:14:03 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/attachment/CVS/Tag b/template/en/default/attachment/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/attachment/CVS/Tag
+++ b/template/en/default/attachment/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/attachment/edit.html.tmpl b/template/en/default/attachment/edit.html.tmpl
index 873f73b59eedf0fb97f14121520ffb80f503b40e..8c4eae569cfbe4971ffad28733b4ffec179a0a87 100644
--- a/template/en/default/attachment/edit.html.tmpl
+++ b/template/en/default/attachment/edit.html.tmpl
@@ -50,7 +50,7 @@
// If this is a plaintext document, remove cruft that Mozilla adds
// because it treats it as an HTML document with a big PRE section.
// http://bugzilla.mozilla.org/show_bug.cgi?id=86012
- var contentType = '[% contenttype %]';
+ var contentType = '[% contenttype FILTER js %]';
if ( contentType == 'text/plain' )
{
theContent = theContent.replace( /^<html><head\/><body><pre>/i , "" );
diff --git a/template/en/default/bug/CVS/Entries b/template/en/default/bug/CVS/Entries
index 2c35db958e005f6f82deca667ccfcbf37e7f69a8..0296ae0d4f6a188e00296aa3ce5e9a15c61d3e80 100644
--- a/template/en/default/bug/CVS/Entries
+++ b/template/en/default/bug/CVS/Entries
@@ -1,11 +1,11 @@
-/choose-xml.html.tmpl/1.4.2.1/Thu May 23 08:14:05 2002//TBUGZILLA-2_16_2
-/choose.html.tmpl/1.3/Tue Apr 23 23:27:50 2002//TBUGZILLA-2_16_2
-/comments.html.tmpl/1.1.2.1/Sat Jun 22 21:03:21 2002//TBUGZILLA-2_16_2
-/dependency-graph.html.tmpl/1.5.2.1/Thu May 23 08:14:05 2002//TBUGZILLA-2_16_2
-/dependency-tree.html.tmpl/1.4.2.1/Mon May 13 06:24:20 2002//TBUGZILLA-2_16_2
-/edit.html.tmpl/1.7.2.5/Tue Jul 9 01:17:59 2002//TBUGZILLA-2_16_2
-/navigate.html.tmpl/1.1.2.1/Thu May 9 23:15:05 2002//TBUGZILLA-2_16_2
-/show-multiple.html.tmpl/1.3.2.1/Thu May 23 08:14:05 2002//TBUGZILLA-2_16_2
+/choose-xml.html.tmpl/1.4.2.1/Thu May 23 08:14:05 2002//TBUGZILLA-2_16_3
+/choose.html.tmpl/1.3/Tue Apr 23 23:27:50 2002//TBUGZILLA-2_16_3
+/comments.html.tmpl/1.1.2.1/Sat Jun 22 21:03:21 2002//TBUGZILLA-2_16_3
+/dependency-graph.html.tmpl/1.5.2.1/Thu May 23 08:14:05 2002//TBUGZILLA-2_16_3
+/dependency-tree.html.tmpl/1.4.2.1/Mon May 13 06:24:20 2002//TBUGZILLA-2_16_3
+/edit.html.tmpl/1.7.2.5/Tue Jul 9 01:17:59 2002//TBUGZILLA-2_16_3
+/navigate.html.tmpl/1.1.2.1/Thu May 9 23:15:05 2002//TBUGZILLA-2_16_3
+/show-multiple.html.tmpl/1.3.2.2/Thu Apr 24 20:45:20 2003//TBUGZILLA-2_16_3
D/activity////
D/create////
D/process////
diff --git a/template/en/default/bug/CVS/Tag b/template/en/default/bug/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/bug/CVS/Tag
+++ b/template/en/default/bug/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/bug/activity/CVS/Entries b/template/en/default/bug/activity/CVS/Entries
index 2af8b018e0688d57793f1b6321fac9ae0581fd6a..ef0deaa15ab3927af9652f80054761146e4a308d 100644
--- a/template/en/default/bug/activity/CVS/Entries
+++ b/template/en/default/bug/activity/CVS/Entries
@@ -1,3 +1,3 @@
-/show.html.tmpl/1.3.2.1/Thu May 23 08:14:07 2002//TBUGZILLA-2_16_2
-/table.html.tmpl/1.1/Thu Apr 18 18:56:38 2002//TBUGZILLA-2_16_2
+/show.html.tmpl/1.3.2.1/Thu May 23 08:14:07 2002//TBUGZILLA-2_16_3
+/table.html.tmpl/1.1/Thu Apr 18 18:56:38 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/bug/activity/CVS/Tag b/template/en/default/bug/activity/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/bug/activity/CVS/Tag
+++ b/template/en/default/bug/activity/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/bug/create/CVS/Entries b/template/en/default/bug/create/CVS/Entries
index 3273b2f757f18a940adfe213029a802d2fbc1e73..91bef8653d48074b2cbc49a9f4adf10e90ce9678 100644
--- a/template/en/default/bug/create/CVS/Entries
+++ b/template/en/default/bug/create/CVS/Entries
@@ -1,6 +1,6 @@
-/comment.txt.tmpl/1.2/Mon May 6 19:17:06 2002//TBUGZILLA-2_16_2
-/create.html.tmpl/1.6.2.4/Sun Jun 30 04:24:51 2002//TBUGZILLA-2_16_2
-/created.html.tmpl/1.4/Wed May 1 19:00:46 2002//TBUGZILLA-2_16_2
-/make-template.html.tmpl/1.3/Tue Apr 23 23:27:48 2002//TBUGZILLA-2_16_2
-/user-message.html.tmpl/1.1.2.1/Wed Jun 5 03:42:23 2002//TBUGZILLA-2_16_2
+/comment.txt.tmpl/1.2/Mon May 6 19:17:06 2002//TBUGZILLA-2_16_3
+/create.html.tmpl/1.6.2.5/Thu Apr 24 20:45:22 2003//TBUGZILLA-2_16_3
+/created.html.tmpl/1.4/Wed May 1 19:00:46 2002//TBUGZILLA-2_16_3
+/make-template.html.tmpl/1.3.2.1/Thu Apr 24 20:45:24 2003//TBUGZILLA-2_16_3
+/user-message.html.tmpl/1.1.2.1/Wed Jun 5 03:42:23 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/bug/create/CVS/Tag b/template/en/default/bug/create/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/bug/create/CVS/Tag
+++ b/template/en/default/bug/create/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/bug/create/create.html.tmpl b/template/en/default/bug/create/create.html.tmpl
index 259f2ea8e1d51d8bd4b1b8341521c003bbd8fe38..9afd5b2774916d59658149ecf4bd477eea68fb24 100644
--- a/template/en/default/bug/create/create.html.tmpl
+++ b/template/en/default/bug/create/create.html.tmpl
@@ -107,7 +107,8 @@
[% sel = { description => 'Priority', name => 'priority' } %]
[% INCLUDE select %]
[% ELSE %]
- <input type="hidden" name="priority" value="[% default.priority %]">
+ <input type="hidden" name="priority"
+ value="[% default.priority FILTER html %]">
[% END %]
[% sel = { description => 'Severity', name => 'bug_severity' } %]
diff --git a/template/en/default/bug/create/make-template.html.tmpl b/template/en/default/bug/create/make-template.html.tmpl
index 1e2495ff86fbd1d2f91ca8a5452862654a2497e5..958d183cc9840b14e4aa11b1b31c86d6a3b77c02 100644
--- a/template/en/default/bug/create/make-template.html.tmpl
+++ b/template/en/default/bug/create/make-template.html.tmpl
@@ -25,7 +25,7 @@
%]
<p>
-If you bookmark <a href="enter_bug.cgi?[% url %]">this link</a>,
+If you bookmark <a href="enter_bug.cgi?[% url FILTER html %]">this link</a>,
going to the bookmark will bring up the enter bug page with the fields
initialized as you've requested.
</p>
diff --git a/template/en/default/bug/process/CVS/Entries b/template/en/default/bug/process/CVS/Entries
index 37fb8841fefb1dcbbb7afa6b53a3071f7a360e34..873edd68b094883f24518b20ff48cba4430cf258 100644
--- a/template/en/default/bug/process/CVS/Entries
+++ b/template/en/default/bug/process/CVS/Entries
@@ -1,6 +1,6 @@
-/confirm-duplicate.html.tmpl/1.2.2.1/Tue Sep 3 07:24:57 2002//TBUGZILLA-2_16_2
-/midair.html.tmpl/1.3.2.1/Tue Sep 3 07:24:58 2002//TBUGZILLA-2_16_2
-/next.html.tmpl/1.1/Sun Apr 21 21:30:21 2002//TBUGZILLA-2_16_2
-/results.html.tmpl/1.3/Wed May 1 19:00:49 2002//TBUGZILLA-2_16_2
-/verify-new-product.html.tmpl/1.3.2.5/Tue Sep 3 07:24:58 2002//TBUGZILLA-2_16_2
+/confirm-duplicate.html.tmpl/1.2.2.1/Tue Sep 3 07:24:57 2002//TBUGZILLA-2_16_3
+/midair.html.tmpl/1.3.2.1/Tue Sep 3 07:24:58 2002//TBUGZILLA-2_16_3
+/next.html.tmpl/1.1/Sun Apr 21 21:30:21 2002//TBUGZILLA-2_16_3
+/results.html.tmpl/1.3/Wed May 1 19:00:49 2002//TBUGZILLA-2_16_3
+/verify-new-product.html.tmpl/1.3.2.5/Tue Sep 3 07:24:58 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/bug/process/CVS/Tag b/template/en/default/bug/process/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/bug/process/CVS/Tag
+++ b/template/en/default/bug/process/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/bug/show-multiple.html.tmpl b/template/en/default/bug/show-multiple.html.tmpl
index 0e73f4ad72cc272aa981915f64a2cd7460cbddf3..60d23ce059e6a4831382583a362abccc0e1f7bb6 100644
--- a/template/en/default/bug/show-multiple.html.tmpl
+++ b/template/en/default/bug/show-multiple.html.tmpl
@@ -104,7 +104,8 @@
<tr>
<td colspan="4">
<b>URL:</b>
- <a href="[% bug.bug_file_loc %]">[% bug.bug_file_loc FILTER html %]</a>
+ <a href="[% bug.bug_file_loc FILTER html %]">
+ [% bug.bug_file_loc FILTER html %]</a>
</tr>
<tr>
diff --git a/template/en/default/bug/votes/CVS/Entries b/template/en/default/bug/votes/CVS/Entries
index 0cd2b55c96c48f9b4b282c1e8ad1bbe1ab730fdf..a7563551935ace5c93e9c8b259e16b388f5271b0 100644
--- a/template/en/default/bug/votes/CVS/Entries
+++ b/template/en/default/bug/votes/CVS/Entries
@@ -1,4 +1,4 @@
-/delete-all.html.tmpl/1.4/Mon May 6 19:17:09 2002//TBUGZILLA-2_16_2
-/list-for-bug.html.tmpl/1.4.2.3/Sat Jun 22 10:35:09 2002//TBUGZILLA-2_16_2
-/list-for-user.html.tmpl/1.6.2.1/Thu May 23 08:14:16 2002//TBUGZILLA-2_16_2
+/delete-all.html.tmpl/1.4/Mon May 6 19:17:09 2002//TBUGZILLA-2_16_3
+/list-for-bug.html.tmpl/1.4.2.3/Sat Jun 22 10:35:09 2002//TBUGZILLA-2_16_3
+/list-for-user.html.tmpl/1.6.2.1/Thu May 23 08:14:16 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/bug/votes/CVS/Tag b/template/en/default/bug/votes/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/bug/votes/CVS/Tag
+++ b/template/en/default/bug/votes/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/filterexceptions.pl b/template/en/default/filterexceptions.pl
new file mode 100644
index 0000000000000000000000000000000000000000..08a021bb298e04060a6975caec665e23eecce2da
--- /dev/null
+++ b/template/en/default/filterexceptions.pl
@@ -0,0 +1,407 @@
+# -*- Mode: perl; indent-tabs-mode: nil -*-
+#
+# The contents of this file are subject to the Mozilla Public
+# License Version 1.1 (the "License"); you may not use this file
+# except in compliance with the License. You may obtain a copy of
+# the License at http://www.mozilla.org/MPL/
+#
+# Software distributed under the License is distributed on an "AS
+# IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+# implied. See the License for the specific language governing
+# rights and limitations under the License.
+#
+# The Original Code are the Bugzilla tests.
+#
+# The Initial Developer of the Original Code is Jacob Steenhagen.
+# Portions created by Jacob Steenhagen are
+# Copyright (C) 2001 Jacob Steenhagen. All
+# Rights Reserved.
+#
+# Contributor(s): Gervase Markham <gerv@gerv.net>
+
+# Important! The following classes of directives are excluded in the test,
+# and so do not need to be added here. Doing so will cause warnings.
+# See 008filter.t for more details.
+#
+# Comments - [%#...
+# Directives - [% IF|ELSE|UNLESS|FOREACH...
+# Assignments - [% foo = ...
+# Simple literals - [% " selected" ...
+# Values always used for numbers - [% (i|j|k|n|count) %]
+# Params - [% Param(...
+# Safe functions - [% (time2str|GetBugLink)...
+# Safe vmethods - [% foo.size %]
+# TT loop variables - [% loop.count %]
+# Already-filtered stuff - [% wibble FILTER html %]
+# where the filter is one of html|csv|js|url_quote|quoteUrls|time|uri|xml
+
+# Key:
+#
+# "#": directive should be filtered, but not doing so is not a security hole
+# The plan is to come back and add filtering for all those marked "#" after
+# the security release.
+#
+# "# Email": as above; but noting that it's an email address.
+# Other sorts of comments denote cleanups noticed while doing this work;
+# they should be fixed in the very short term.
+
+%::safe = (
+
+'sidebar.xul.tmpl' => [
+ 'template_version',
+],
+
+'search/boolean-charts.html.tmpl' => [
+ '"field${chartnum}-${rownum}-${colnum}"',
+ '"value${chartnum}-${rownum}-${colnum}"',
+ '"type${chartnum}-${rownum}-${colnum}"',
+ 'field.name',
+ 'field.description',
+ 'type.name',
+ 'type.description',
+ '"${chartnum}-${rownum}-${newor}"',
+ '"${chartnum}-${newand}-0"',
+ 'newchart',
+ '$jsmagic', #
+],
+
+'search/form.html.tmpl' => [
+ 'qv.value',
+ 'qv.name',
+ 'qv.description',
+ 'field.name',
+ 'field.description',
+ 'sel.name',
+ 'button_name', #
+],
+
+'search/knob.html.tmpl' => [
+ 'button_name', #
+],
+
+'reports/components.html.tmpl' => [
+ 'numcols',
+ 'numcols - 1',
+ 'comp.description',
+ 'comp.initialowner', # email address
+ 'comp.initialqacontact', # email address
+],
+
+'reports/duplicates-simple.html.tmpl' => [
+ 'title', #
+],
+
+'reports/duplicates-table.html.tmpl' => [
+ '"&maxrows=$maxrows" IF maxrows',
+ '"&changedsince=$changedsince" IF changedsince',
+ '"&product=$product" IF product', #
+ '"&format=$format" IF format', #
+ '"&bug_id=$bug_ids_string&sortvisible=1" IF sortvisible',
+ 'column.name',
+ 'column.description',
+ 'vis_bug_ids.push(bug.id)',
+ 'bug.id',
+ 'bug.count',
+ 'bug.delta',
+ 'bug.component', #
+ 'bug.bug_severity', #
+ 'bug.op_sys', #
+ 'bug.target_milestone', #
+],
+
+'reports/duplicates.html.tmpl' => [
+ 'bug_ids_string',
+ 'maxrows',
+ 'changedsince',
+ 'reverse',
+],
+
+'reports/keywords.html.tmpl' => [
+ 'keyword.description',
+ 'keyword.bugcount',
+],
+
+'list/change-columns.html.tmpl' => [
+ 'column',
+ 'desc.${column}', #
+],
+
+'list/edit-multiple.html.tmpl' => [
+ 'group.bit',
+ 'group.description',
+ 'group.description FILTER strike',
+ 'knum',
+ 'menuname',
+ 'selected IF resolution == "FIXED"', #
+],
+
+'list/list-rdf.rdf.tmpl' => [
+ 'template_version',
+ 'bug.id',
+ 'column',
+],
+
+'list/list-simple.html.tmpl' => [
+ 'title',
+],
+
+'list/list.html.tmpl' => [
+ 'currenttime', #
+ 'buglist',
+ 'bugowners', # email address
+],
+
+'list/table.html.tmpl' => [
+ 'id',
+ 'splitheader ? 2 : 1',
+ 'abbrev.$id.title || column.title', #
+ 'tableheader',
+ 'bug.severity', #
+ 'bug.priority', #
+ 'bug.id',
+],
+
+'global/choose-product.html.tmpl' => [
+ 'target',
+ 'proddesc.$p',
+],
+
+'global/code-error.html.tmpl' => [
+ 'error',
+],
+
+'global/footer.html.tmpl' => [
+ 'CALL SyncAnyPendingShadowChanges() IF SyncAnyPendingShadowChanges',
+],
+
+'global/header.html.tmpl' => [
+ 'header_html',
+ 'javascript',
+ 'style',
+ 'style_url',
+ 'bgcolor',
+ 'onload',
+ 'h1',
+ 'h2',
+ 'message',
+],
+
+'global/hidden-fields.html.tmpl' => [
+ 'mvalue | html | html_linebreak', # Need to eliminate | usage
+ 'field.value | html | html_linebreak',
+],
+
+'global/select-menu.html.tmpl' => [
+ 'options',
+],
+
+'global/useful-links.html.tmpl' => [
+ 'user.login', # Email address
+],
+
+'global/user-error.html.tmpl' => [
+ 'error', # can contain HTML in 2.16.x
+],
+
+'bug/comments.html.tmpl' => [
+ 'comment.time',
+ 'quoteUrls(comment.body)',
+],
+
+'bug/dependency-graph.html.tmpl' => [
+ 'image_map', # We need to continue to make sure this is safe in the CGI
+ 'image_url',
+ 'map_url',
+ 'bug_id',
+],
+
+'bug/dependency-tree.html.tmpl' => [
+ 'hide_resolved ? "Open b" : "B"',
+ 'bugid',
+ 'maxdepth',
+ 'dependson_ids.join(",")',
+ 'blocked_ids.join(",")',
+ 'dep_id',
+ 'hide_resolved ? 0 : 1',
+ 'hide_resolved ? "Show" : "Hide"',
+ 'realdepth < 2 || maxdepth == 1 ? "disabled" : ""',
+ 'hide_resolved',
+ 'realdepth < 2 ? "disabled" : ""',
+ 'maxdepth + 1',
+ 'maxdepth == 0 || maxdepth == realdepth ? "disabled" : ""',
+ 'realdepth < 2 || ( maxdepth && maxdepth < 2 ) ? "disabled" : ""',
+ 'maxdepth > 0 && maxdepth <= realdepth ? maxdepth : ""',
+ 'maxdepth == 1 ? 1
+ : ( maxdepth ? maxdepth - 1 : realdepth - 1 )',
+ 'realdepth < 2 || ! maxdepth || maxdepth >= realdepth ?
+ "disabled" : ""',
+],
+
+'bug/edit.html.tmpl' => [
+ 'bug.delta_ts',
+ 'bug.bug_id',
+ 'bug.votes',
+ 'group.bit',
+ 'group.description',
+ 'knum',
+ 'dep.title',
+ 'dep.fieldname',
+ 'bug.${dep.fieldname}.join(\', \')',
+ 'selname',
+ 'bug.longdesclength',
+ 'bug.creation_ts',
+],
+
+'bug/navigate.html.tmpl' => [
+ 'this_bug_idx + 1',
+ 'bug_list.first',
+ 'bug_list.last',
+ 'bug_list.$prev_bug',
+ 'bug_list.$next_bug',
+],
+
+'bug/show-multiple.html.tmpl' => [
+ 'bug.bug_id',
+ 'bug.component', #
+ 'attr.description', #
+],
+
+'bug/votes/list-for-bug.html.tmpl' => [
+ 'voter.count',
+ 'total',
+],
+
+'bug/votes/list-for-user.html.tmpl' => [
+ 'product.maxperbug',
+ 'bug.id',
+ 'bug.count',
+ 'product.total',
+ 'product.maxvotes',
+],
+# h2 = voting_user.name # Email
+
+'bug/process/confirm-duplicate.html.tmpl' => [
+ 'original_bug_id',
+ 'duplicate_bug_id',
+],
+
+'bug/process/midair.html.tmpl' => [
+ 'bug_id',
+],
+
+'bug/process/next.html.tmpl' => [
+ 'next_id',
+],
+
+'bug/process/results.html.tmpl' => [
+ 'title.$type',
+ 'id',
+ 'mail',
+],
+
+'bug/process/verify-new-product.html.tmpl' => [
+ 'form.product', #
+],
+
+'bug/create/create.html.tmpl' => [
+ 'default.bug_status', #
+ 'g.bit',
+ 'g.description',
+ 'sel.name',
+ 'sel.description',
+],
+
+'bug/activity/show.html.tmpl' => [
+ 'bug_id',
+],
+
+'bug/activity/table.html.tmpl' => [
+ 'operation.who', # Email
+ 'operation.when',
+ 'change.attachid',
+ 'change.field',
+],
+
+'attachment/create.html.tmpl' => [
+ 'bugid',
+ 'attachment.id',
+],
+
+'attachment/created.html.tmpl' => [
+ 'attachid',
+ 'bugid',
+ 'contenttype',
+ 'mailresults',
+],
+
+'attachment/edit.html.tmpl' => [
+ 'attachid',
+ 'bugid',
+ 'def.id',
+ 'a',
+],
+
+'attachment/list.html.tmpl' => [
+ 'attachment.attachid',
+ 'attachment.date',
+ 'bugid',
+],
+
+'attachment/show-multiple.html.tmpl' => [
+ 'a.attachid',
+ 'a.date',
+],
+
+'attachment/updated.html.tmpl' => [
+ 'attachid',
+ 'bugid',
+ 'mailresults',
+],
+
+'admin/attachstatus/create.html.tmpl' => [
+ 'id',
+],
+
+'admin/attachstatus/delete.html.tmpl' => [
+ 'attachcount',
+ 'id',
+ 'name',
+],
+
+'admin/attachstatus/edit.html.tmpl' => [
+ 'id',
+ 'sortkey',
+],
+
+'admin/attachstatus/list.html.tmpl' => [
+ 'statusdef.sortkey',
+ 'statusdef.id',
+ 'statusdef.attachcount',
+],
+
+'account/prefs/account.html.tmpl' => [
+ 'login_change_date', #
+],
+
+'account/prefs/email.html.tmpl' => [
+ 'watchedusers', # Email
+ 'useqacontact ? \'5\' : \'4\'',
+ 'role',
+ 'reason.name',
+ 'reason.description',
+],
+
+'account/prefs/permissions.html.tmpl' => [
+ 'bit_description',
+],
+
+'account/prefs/prefs.html.tmpl' => [
+ 'tab.name',
+ 'tab.description',
+ 'changes_saved',
+ 'current_tab.name',
+ 'current_tab.description',
+ 'current_tab.description FILTER lower',
+],
+
+);
diff --git a/template/en/default/global/CVS/Entries b/template/en/default/global/CVS/Entries
index 047ec39e878afcb3ef9698c9e92d75e02a638535..e6c78c035501ec07cb3f8e5240e2d82a31fae8e1 100644
--- a/template/en/default/global/CVS/Entries
+++ b/template/en/default/global/CVS/Entries
@@ -1,11 +1,11 @@
-/banner.html.tmpl/1.1.2.1/Tue Jun 4 05:56:34 2002//TBUGZILLA-2_16_2
-/choose-product.html.tmpl/1.6/Mon May 6 19:17:11 2002//TBUGZILLA-2_16_2
-/code-error.html.tmpl/1.4/Mon May 6 19:17:11 2002//TBUGZILLA-2_16_2
-/footer.html.tmpl/1.6/Tue May 7 21:56:40 2002//TBUGZILLA-2_16_2
-/header.html.tmpl/1.5.2.7/Thu Jul 4 11:21:00 2002//TBUGZILLA-2_16_2
-/hidden-fields.html.tmpl/1.2.2.3/Tue Sep 3 07:25:01 2002//TBUGZILLA-2_16_2
-/message.html.tmpl/1.3/Mon May 6 19:17:11 2002//TBUGZILLA-2_16_2
-/select-menu.html.tmpl/1.1.2.1/Mon Jun 3 22:34:12 2002//TBUGZILLA-2_16_2
-/useful-links.html.tmpl/1.2.2.6/Wed Jul 10 00:06:00 2002//TBUGZILLA-2_16_2
-/user-error.html.tmpl/1.4/Mon May 6 19:17:12 2002//TBUGZILLA-2_16_2
+/banner.html.tmpl/1.1.2.1/Tue Jun 4 05:56:34 2002//TBUGZILLA-2_16_3
+/choose-product.html.tmpl/1.6.2.1/Thu Apr 24 20:45:26 2003//TBUGZILLA-2_16_3
+/code-error.html.tmpl/1.4.2.1/Thu Apr 24 20:45:26 2003//TBUGZILLA-2_16_3
+/footer.html.tmpl/1.6/Tue May 7 21:56:40 2002//TBUGZILLA-2_16_3
+/header.html.tmpl/1.5.2.7/Thu Jul 4 11:21:00 2002//TBUGZILLA-2_16_3
+/hidden-fields.html.tmpl/1.2.2.4/Thu Apr 24 20:45:26 2003//TBUGZILLA-2_16_3
+/message.html.tmpl/1.3.2.1/Thu Apr 24 20:45:26 2003//TBUGZILLA-2_16_3
+/select-menu.html.tmpl/1.1.2.1/Mon Jun 3 22:34:12 2002//TBUGZILLA-2_16_3
+/useful-links.html.tmpl/1.2.2.6/Wed Jul 10 00:06:00 2002//TBUGZILLA-2_16_3
+/user-error.html.tmpl/1.4/Mon May 6 19:17:12 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/global/CVS/Tag b/template/en/default/global/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/global/CVS/Tag
+++ b/template/en/default/global/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/global/choose-product.html.tmpl b/template/en/default/global/choose-product.html.tmpl
index e8d9aaf5c0f596485fb106e623844d3c8b702ff7..530413de65d9102e6e6cee75c2c2ee2c03a80151 100644
--- a/template/en/default/global/choose-product.html.tmpl
+++ b/template/en/default/global/choose-product.html.tmpl
@@ -33,7 +33,7 @@
<tr>
<th align="right" valign="top">
<a href="[% target %]?product=[% p FILTER url_quote %]
- [%- "&format=$format" IF format %]">
+ [% IF format %]&format=[% format FILTER url_quote %][% END %]">
[% p FILTER html %]</a>:
</th>
diff --git a/template/en/default/global/code-error.html.tmpl b/template/en/default/global/code-error.html.tmpl
index 637fba6b1bb3dedb87513c4a37e3e9acceb64254..cab4f44b8a6fe586819794e5a51a56b56a2b4e9e 100644
--- a/template/en/default/global/code-error.html.tmpl
+++ b/template/en/default/global/code-error.html.tmpl
@@ -56,7 +56,7 @@
<pre>
Variables:
[% FOREACH key = variables.keys %]
- [%+ key %]: [%+ variables.$key %]
+ [%+ key FILTER html %]: [%+ variables.$key FILTER html %]
[% END %]
</pre>
[% END %]
diff --git a/template/en/default/global/hidden-fields.html.tmpl b/template/en/default/global/hidden-fields.html.tmpl
index f968fab200d78217c94adea21febff65a4ac8945..a824c3489cb689c382d3290822a1c276bb2afcb1 100644
--- a/template/en/default/global/hidden-fields.html.tmpl
+++ b/template/en/default/global/hidden-fields.html.tmpl
@@ -32,11 +32,11 @@
[% NEXT IF exclude && field.key.search(exclude) %]
[% IF mform.${field.key}.size > 1 %]
[% FOREACH mvalue = mform.${field.key} %]
- <input type="hidden" name="[% field.key %]"
+ <input type="hidden" name="[% field.key FILTER html %]"
value="[% mvalue | html | html_linebreak %]">
[% END %]
[% ELSE %]
- <input type="hidden" name="[% field.key %]"
+ <input type="hidden" name="[% field.key FILTER html %]"
value="[% field.value | html | html_linebreak %]">
[% END %]
[% END %]
diff --git a/template/en/default/global/message.html.tmpl b/template/en/default/global/message.html.tmpl
index 14e1f10d0343784f1bdd1657ed0fb78cb8cebb9f..f1f77fdb214dec62e023bbb002429e63a90e4aa9 100644
--- a/template/en/default/global/message.html.tmpl
+++ b/template/en/default/global/message.html.tmpl
@@ -35,7 +35,7 @@
[%# Display a URL if the calling script has included one. %]
[% IF url && link %]
<p>
- <a href="[% url %]">[% link %]</a>
+ <a href="[% url FILTER html %]">[% link FILTER html %]</a>
</p>
[% END %]
diff --git a/template/en/default/list/CVS/Entries b/template/en/default/list/CVS/Entries
index 91915cd6110bc228de73abcc4a13b2e0a7f4edf3..7bfcd68eefeb9bfcf22b824b4fecf108f2d5ae21 100644
--- a/template/en/default/list/CVS/Entries
+++ b/template/en/default/list/CVS/Entries
@@ -1,9 +1,9 @@
-/change-columns.html.tmpl/1.3/Tue Apr 23 23:27:34 2002//TBUGZILLA-2_16_2
-/edit-multiple.html.tmpl/1.4.2.2/Sun Jun 30 04:24:57 2002//TBUGZILLA-2_16_2
-/list-rdf.rdf.tmpl/1.1/Thu Apr 18 18:56:55 2002//TBUGZILLA-2_16_2
-/list-simple.html.tmpl/1.4.2.1/Thu May 23 08:14:22 2002//TBUGZILLA-2_16_2
-/list.html.tmpl/1.3.2.2/Wed Jun 5 02:23:12 2002//TBUGZILLA-2_16_2
-/quips.html.tmpl/1.4.2.2/Tue Nov 26 20:32:00 2002//TBUGZILLA-2_16_2
-/server-push.html.tmpl/1.2/Mon May 6 19:17:19 2002//TBUGZILLA-2_16_2
-/table.html.tmpl/1.4.2.2/Mon Jul 1 03:30:23 2002//TBUGZILLA-2_16_2
+/change-columns.html.tmpl/1.3.2.1/Thu Apr 24 20:45:29 2003//TBUGZILLA-2_16_3
+/edit-multiple.html.tmpl/1.4.2.2/Sun Jun 30 04:24:57 2002//TBUGZILLA-2_16_3
+/list-rdf.rdf.tmpl/1.1/Thu Apr 18 18:56:55 2002//TBUGZILLA-2_16_3
+/list-simple.html.tmpl/1.4.2.1/Thu May 23 08:14:22 2002//TBUGZILLA-2_16_3
+/list.html.tmpl/1.3.2.3/Thu Apr 24 20:45:29 2003//TBUGZILLA-2_16_3
+/quips.html.tmpl/1.4.2.2/Tue Nov 26 20:32:00 2002//TBUGZILLA-2_16_3
+/server-push.html.tmpl/1.2/Mon May 6 19:17:19 2002//TBUGZILLA-2_16_3
+/table.html.tmpl/1.4.2.3/Thu Apr 24 20:45:30 2003//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/list/CVS/Tag b/template/en/default/list/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/list/CVS/Tag
+++ b/template/en/default/list/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/list/change-columns.html.tmpl b/template/en/default/list/change-columns.html.tmpl
index 96e56e8eb95c1e9555970f372842fe29b76bf8fa..a7c5f6e2351605dc460bceee28de6f2d23f32688 100644
--- a/template/en/default/list/change-columns.html.tmpl
+++ b/template/en/default/list/change-columns.html.tmpl
@@ -27,7 +27,7 @@ Check which columns you wish to appear on the list, and then click
on submit. (Cookies are required.)
<p>
<form action="colchange.cgi">
-<input type="hidden" name="rememberedquery" value="[% buffer %]">
+<input type="hidden" name="rememberedquery" value="[% buffer FILTER html %]">
[% FOREACH column = masterlist %]
<input type="checkbox" id="[% column %]" name="column_[% column %]" [% "CHECKED" IF lsearch(collist, column) != -1 %]>
<label for="[% column %]">[% desc.${column} %]</label><br>
@@ -41,7 +41,7 @@ on submit. (Cookies are required.)
<input type="submit" value="Submit">
</form>
<form action="colchange.cgi">
-<input type="hidden" name="rememberedquery" value="[% buffer %]">
+<input type="hidden" name="rememberedquery" value="[% buffer FILTER html %]">
<input type="hidden" name="resetit" value="1">
<input type="submit" value="Reset to Bugzilla default">
</form>
diff --git a/template/en/default/list/list.html.tmpl b/template/en/default/list/list.html.tmpl
index 8ffba004fb16f332382deaeee1172ad306e328a1..dab76666fce2687839cdc5209f7c6513ea212091 100644
--- a/template/en/default/list/list.html.tmpl
+++ b/template/en/default/list/list.html.tmpl
@@ -94,7 +94,7 @@
<p>
<a href="query.cgi">Query Page</a>
<a href="enter_bug.cgi">Enter New Bug</a>
- <a href="query.cgi?[% urlquerypart %]">Edit this query</a>
+ <a href="query.cgi?[% urlquerypart FILTER html %]">Edit this query</a>
</p>
[% ELSIF bugs.size == 1 %]
@@ -134,10 +134,10 @@
<a href="query.cgi">Query Page</a>
<a href="enter_bug.cgi">Enter New Bug</a>
- <a href="colchange.cgi?[% urlquerypart %]">Change Columns</a>
+ <a href="colchange.cgi?[% urlquerypart FILTER html %]">Change Columns</a>
[% IF bugs.size > 1 && caneditbugs && !dotweak %]
- <a href="buglist.cgi?[% urlquerypart %]
+ <a href="buglist.cgi?[% urlquerypart FILTER html %]
[%- "&order=$qorder" FILTER html IF order %]&tweak=1">Change Several
Bugs at Once</a>
@@ -147,7 +147,7 @@
<a href="mailto:[% bugowners %]">Send Mail to Bug Owners</a>
[% END %]
- <a href="query.cgi?[% urlquerypart %]">Edit this Query</a>
+ <a href="query.cgi?[% urlquerypart FILTER html %]">Edit this Query</a>
</form>
diff --git a/template/en/default/list/table.html.tmpl b/template/en/default/list/table.html.tmpl
index 6d5ee0d6cc11397f13761b5cb86e53a3aa9ab521..f14784f65c23b2f02b1ad7b236b488db46c8d4f8 100644
--- a/template/en/default/list/table.html.tmpl
+++ b/template/en/default/list/table.html.tmpl
@@ -69,7 +69,7 @@
<tr align="left">
<th colspan="[% splitheader ? 2 : 1 %]">
- <a href="buglist.cgi?[% urlquerypart %]&order=bugs.bug_id">ID</a>
+ <a href="buglist.cgi?[% urlquerypart FILTER html %]&order=bugs.bug_id">ID</a>
</th>
[% IF splitheader %]
@@ -102,7 +102,7 @@
[% BLOCK columnheader %]
<th colspan="[% splitheader ? 2 : 1 %]">
- <a href="buglist.cgi?[% urlquerypart %]&order=
+ <a href="buglist.cgi?[% urlquerypart FILTER html %]&order=
[% column.name FILTER url_quote FILTER html %]
[% ",$qorder" FILTER html IF order %]">
[%- abbrev.$id.title || column.title -%]</a>
diff --git a/template/en/default/reports/CVS/Entries b/template/en/default/reports/CVS/Entries
index 216e831d7ca43bdf46ab2ca10e4d148471f31ec4..34eef57bce679c8331ed28c12f3c022336dcd904 100644
--- a/template/en/default/reports/CVS/Entries
+++ b/template/en/default/reports/CVS/Entries
@@ -1,6 +1,6 @@
-/components.html.tmpl/1.4.2.2/Thu May 30 19:38:22 2002//TBUGZILLA-2_16_2
-/duplicates-simple.html.tmpl/1.1/Fri Apr 26 23:18:53 2002//TBUGZILLA-2_16_2
-/duplicates-table.html.tmpl/1.1.2.2/Thu Jun 13 22:22:32 2002//TBUGZILLA-2_16_2
-/duplicates.html.tmpl/1.4.2.1/Thu May 23 08:14:26 2002//TBUGZILLA-2_16_2
-/keywords.html.tmpl/1.4/Wed Apr 24 18:27:43 2002//TBUGZILLA-2_16_2
+/components.html.tmpl/1.4.2.2/Thu May 30 19:38:22 2002//TBUGZILLA-2_16_3
+/duplicates-simple.html.tmpl/1.1/Fri Apr 26 23:18:53 2002//TBUGZILLA-2_16_3
+/duplicates-table.html.tmpl/1.1.2.2/Thu Jun 13 22:22:32 2002//TBUGZILLA-2_16_3
+/duplicates.html.tmpl/1.4.2.2/Thu Apr 24 20:45:33 2003//TBUGZILLA-2_16_3
+/keywords.html.tmpl/1.4/Wed Apr 24 18:27:43 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/reports/CVS/Tag b/template/en/default/reports/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/reports/CVS/Tag
+++ b/template/en/default/reports/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3
diff --git a/template/en/default/reports/duplicates.html.tmpl b/template/en/default/reports/duplicates.html.tmpl
index 64ba5e120d56eb02b40b551f4d12931bd322b618..da218d7c55af6cfebb8b549a2ecfab35d9d1d177 100644
--- a/template/en/default/reports/duplicates.html.tmpl
+++ b/template/en/default/reports/duplicates.html.tmpl
@@ -59,7 +59,7 @@
<h3><a name="params">Change Parameters</a></h3>
<form method="get" action="duplicates.cgi">
- <input type="hidden" name="sortby" value="[% sortby %]">
+ <input type="hidden" name="sortby" value="[% sortby FILTER html %]">
<input type="hidden" name="reverse" value="[% reverse %]">
<input type="hidden" name="bug_id" value="[% bug_ids_string %]">
<table>
@@ -83,8 +83,8 @@
<td rowspan="4" valign="top">
<select name="product" size="5" multiple="multiple">
[% FOREACH p = products %]
- <option name="[% p %]"
- [% " selected" IF product == p %]>[% p %]</option>
+ <option name="[% p FILTER html %]"
+ [% " selected" IF product == p %]>[% p FILTER html %]</option>
[% END %]
</select>
</td>
diff --git a/template/en/default/search/CVS/Entries b/template/en/default/search/CVS/Entries
index fe8b0dfc71388b8800c2d1c0b07f689365a9b4ad..8f8d8c4f306588279e1cc6443a838cda2176eb49 100644
--- a/template/en/default/search/CVS/Entries
+++ b/template/en/default/search/CVS/Entries
@@ -1,5 +1,5 @@
-/boolean-charts.html.tmpl/1.1/Fri Apr 26 20:03:08 2002//TBUGZILLA-2_16_2
-/form.html.tmpl/1.2.2.5/Thu Jul 11 19:28:05 2002//TBUGZILLA-2_16_2
-/knob.html.tmpl/1.2.2.2/Sat Jun 22 23:56:00 2002//TBUGZILLA-2_16_2
-/search.html.tmpl/1.8.2.1/Tue Jun 4 22:56:40 2002//TBUGZILLA-2_16_2
+/boolean-charts.html.tmpl/1.1/Fri Apr 26 20:03:08 2002//TBUGZILLA-2_16_3
+/form.html.tmpl/1.2.2.5/Thu Jul 11 19:28:05 2002//TBUGZILLA-2_16_3
+/knob.html.tmpl/1.2.2.2/Sat Jun 22 23:56:00 2002//TBUGZILLA-2_16_3
+/search.html.tmpl/1.8.2.1/Tue Jun 4 22:56:40 2002//TBUGZILLA-2_16_3
D
diff --git a/template/en/default/search/CVS/Tag b/template/en/default/search/CVS/Tag
index 7e397d800d56db36f5d0dbb288351253afffee08..6406b9811aa41c52e7340d365f79f5cb0c82ed59 100644
--- a/template/en/default/search/CVS/Tag
+++ b/template/en/default/search/CVS/Tag
@@ -1 +1 @@
-NBUGZILLA-2_16_2
+NBUGZILLA-2_16_3